Skip to content

Add an open challenge to break LogShield - #14

Merged
TurlaFSB merged 1 commit into
mainfrom
break-logshield-challenge
Oct 17, 2026
Merged

TurlaFSB merged 1 commit into
mainfrom
break-logshield-challenge

Conversation

@TurlaFSB

Copy link
Copy Markdown
Owner

States what counts as a bypass, how to test an idea in five minutes with logshield check, how to confirm it against real Log4j in the lab, and what a reporter receives.

What and why

Checklist

  • make check passes (vet, lint, race tests, coverage floor)
  • New behavior has table-driven tests; a bypass fix adds a regression entry to the corpus
  • Any new payload is inert (reserved names only: example.com, *.invalid, 192.0.2.0/24)
  • The engine stays pure (no I/O, clock, randomness, or global state) and bounded
  • Docs and CHANGELOG updated where behavior changed
  • No secrets, tokens, or real hostnames in code, tests, or fixtures

States what counts as a bypass, how to test an idea in five minutes with logshield check, how to confirm it against real Log4j in the lab, and what a reporter receives.
@TurlaFSB
TurlaFSB merged commit 0be16a3 into main Oct 17, 2026
21 checks passed
@TurlaFSB
TurlaFSB deleted the break-logshield-challenge branch October 17, 2026 16:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant