Remove Log4potExtractionStrategy

[regulartim]

The Log4potExtractionStrategy class (currently only present in develop) contains a lot of legacy code which is not very testable. It should be considered to refactor this class and write a comprehensive set of tests for it.

[regulartim]

It may also be sensible to just remove the special treatment for this honeypot, as it is no longer relevant. What do you think @mlodic ?

[mlodic]

yes, we can remove everything about it.

[regulartim]

Ok. But I think we should wait until #637 is closed.

[shivraj1182]

Hi @regulartim, @mlodic,
I would like to work on this issue. Since you confirmed that everything related to Log4potExtractionStrategy can be removed, this seems like a good fit for me. Could you please assign this issue to me? , with the understanding that I will start working on it once #637 is closed? Also, are there any specific parts of the codebase (files, modules, or tests) you would like me to focus on or any particular expectations for the cleanup?
Thanks, looking forward to your thoughts.

[regulartim]

Hey @shivraj1182 ! I would suggest to choose another issue to get assigned until #637 is fixed. I don't know when it will happen, it might take a while. I don't feel like it's a good idea to assign an issue to someone and that person can not immediately work on it.

[shivraj1182]

Thanks for the quick response, That makes sense and I understand the concern about assigning issues that are currently not accessible! For now I'll look for another issue that's available. When #637 gets resolved and this issue becomes available again, I would still be interested in picking it up if it is not yet assigned.