Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Different levels of action based on different match strings (for e.g. non-open proxies) #40

Open
Kufat opened this issue Dec 10, 2020 · 0 comments

Comments

@Kufat
Copy link

Kufat commented Dec 10, 2020

We've recently seen a few cases where users have been connecting from proxies that aren't open but appear to be poorly-secured, judging by the low-quality troll traffic that's passing through them. We can't go around trying common usernames and passwords, so it's difficult to programmatically distinguish between well-secured and poorly-secured proxies through hopm.

I'd like to be able to continue k-lining for open proxies while also being able to set up lesser actions for any user whose port 443/80/etc output contains "Proxy" or "squid", like sending a message to a staff channel containing the user's nick and IP. Running two instances of hopm with different parameters is an obvious solution, but less than ideal because it would scan each user twice.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant