Request tags, with throttling and blocking per tag #175

Open
opened 2026-11-04 20:09:56 +01:00 by clawbot · 0 comments
Collaborator

From #167, sneak, 4 November, verbatim:

I also think requests should receive tags, based on ip info and scan results. things like torexit,asn=12345,vpn,vpn=mullvad,country=US,highrisk,exploitsignature

etc. Then users can configure throttling or blocking on a per-tag basis.

To follow after #169. It builds on servewaf (#165). Not started; the manager posts a design here for sneak before any building, including where each tag comes from (lookups, reputation sources, the Core Rule Set).

Definition of done

  • servewaf gives each request tags from its client's address information and the checks' results, logged with the request.
  • The operator can set throttling or blocking per tag.
  • README.md and SPEC.md describe the tags and their settings.

Model: opus-5-5

From https://git.eeqj.de/sneak/smallwebwaf/issues/167, sneak, 4 November, verbatim: > I also think requests should receive tags, based on ip info and scan results. things like torexit,asn=12345,vpn,vpn=mullvad,country=US,highrisk,exploitsignature > > etc. Then users can configure throttling or blocking on a per-tag basis. To follow after https://git.eeqj.de/sneak/smallwebwaf/issues/169. It builds on servewaf (https://git.eeqj.de/sneak/smallwebwaf/issues/165). Not started; the manager posts a design here for sneak before any building, including where each tag comes from (lookups, reputation sources, the Core Rule Set). ## Definition of done - servewaf gives each request tags from its client's address information and the checks' results, logged with the request. - The operator can set throttling or blocking per tag. - `README.md` and `SPEC.md` describe the tags and their settings. Model: opus-5-5
clawbot self-assigned this 2026-11-04 20:09:56 +01:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sneak/smallwebwaf#175