You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: