Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

unquoted pcre values fail

Open
#251 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
65/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
go
Domain
backend

Research direction

Start with the rule parsing and validation path for unquoted pcre values; the issue does not name a file or test, so locate those entry points and add a regression case using the example rule. Check that parsing succeeds and that errors identify the correct option. Done when the example is accepted and the regression test passes.

Written by the indexing model from the issue text.

Description

A rule with an unquoted pcre value like alert udp $HOME_NET any -> $EXTERNAL_NET any (msg:"foo"; content:"AA"; pcre:/filename=".*\.php"/i ; sid:1337; rev:1;) fails with the error invalid type '\v' for option content. Suricata happily accepts these.

Also, not sure if it will be relevant after a fix but "content" in the error is probably a mistake.

Slopfix™ here: https://github.com/kallen-vc/gonids/commit/6805d58c56bd220e7f6859b96d03170aac88f513

Dominant language
Go
Stars
197
Forks
52
Avg merge
1d 1h
Merged PRs (30d)
21

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from google/gonids

All issues in google/gonids

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.