Skip to content

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

@Kufat

Description

@Kufat

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions