Actions
Optimization #569
open
VJ
CT
display syntax requirement on keyword parsing error
Optimization #569:
display syntax requirement on keyword parsing error
Added by Victor Julien about 14 years ago. Updated 4 months ago.
Effort:
high
Difficulty:
low
Label:
VJ Updated by Victor Julien about 14 years ago Actions #1
- Priority changed from Normal to Low
VJ Updated by Victor Julien about 14 years ago Actions #2
- Target version changed from 1.4beta3 to 1.4rc1
VJ Updated by Victor Julien almost 14 years ago Actions #3
- Target version changed from 1.4rc1 to 2.0rc2
VJ Updated by Victor Julien almost 13 years ago Actions #4
- Target version changed from 2.0rc2 to 3.0RC2
VJ Updated by Victor Julien over 11 years ago Actions #5
- Target version changed from 3.0RC2 to 70
VJ Updated by Victor Julien almost 11 years ago Actions #6
- Priority changed from Low to Normal
- Target version changed from 70 to TBD
VJ Updated by Victor Julien over 8 years ago Actions #7
- Assignee changed from OISF Dev to Anonymous
- Effort set to high
- Difficulty set to low
AH Updated by Andreas Herz over 7 years ago Actions #8
- Assignee set to Community Ticket
JT Updated by Jason Taylor about 7 years ago Actions #9
- Assignee changed from Community Ticket to Jason Taylor
JT Updated by Jason Taylor about 5 years ago Actions #10
It looks like the last discussion that was had around this was in https://github.com/OISF/suricata/pull/4251. Are there any update thoughts or ideas around this? I was going to take another look at this but wanted to see if anyone else had or was.
JT Updated by Jason Taylor over 4 years ago Actions #11
- Assignee changed from Jason Taylor to Community Ticket
PA Updated by Philippe Antoine over 3 years ago Actions #12
Side-note: We want to move away from pcre for keywords, and we still need meaningful error messages
PA Updated by Philippe Antoine over 3 years ago Actions #13
- Tracker changed from Bug to Optimization
PA Updated by Philippe Antoine 4 months ago Actions #14
- Status changed from New to Triaged
Actions