Snort now blocking chisel
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 16.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
New Snort rule (https://www.snort.org/advisories/talos-rules-2024-02-20)
- 1:63050 <-> DISABLED <-> POLICY-OTHER Chisel proxy tunnel outbound connection attempt (policy-other.rules)
I had a tunnel blocked at a customer, had them whitelist for now but if anyone's taken a look at the rule, what is Chisel being blocked on? i would guess the Chisel header which as far as i know, can't be changed from command line (you can add headers, but if you try to "overwrite" one, chisel fails to start).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Talos Snort advisory and rule 1:63050, then inspect Chisel's outbound HTTP request and header handling, including the command-line header options described in the issue. Determine which request characteristic triggers the rule and whether Chisel can change it without breaking startup; document the finding and any actionable compatibility change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100