Shivani Bhardwaj
- Login: unixia
- Registered on: 09/29/2018
- Last connection: 01/25/2024
Issues
open | closed | Total | |
---|---|---|---|
Assigned issues | 45 | 349 | 394 |
Reported issues | 76 | 229 | 305 |
Projects
Project | Roles | Registered on |
---|---|---|
Suricata | Developer, OISF Team, OISF Manager | 08/17/2023 |
Suricata-Update | Developer, OISF Team, OISF Manager | 08/17/2023 |
Activity
03/15/2024
- 12:09 PM Suricata Bug #6859: fast_pattern specification in base64_data shouldn't be allowed (7.0.x backport)
- Victor Julien wrote in #note-6:
> No, in 8 we can be strict. Just don't want to introduce errors/warnings for otherw... - 11:52 AM Suricata Bug #6859: fast_pattern specification in base64_data shouldn't be allowed (7.0.x backport)
- > We've seen that new warnings are often seen as too "severe" by integrators. So perhaps we should just give an info...
- 11:44 AM Suricata Bug #6859: fast_pattern specification in base64_data shouldn't be allowed (7.0.x backport)
- Victor Julien wrote in #note-2:
> I wonder how we should handle the backport. We can't starting rejecting these rule...
03/11/2024
- 11:20 AM Suricata Bug #6845 (In Review): coverity: warning in port grouping code (7.0.x backport)
- In Review PR: https://github.com/OISF/suricata/pull/10612
- 11:20 AM Suricata Bug #6844 (In Review): detect/port: port ranges are incorrect when a port is single as well as a part of range (7.0.x backport)
- In Review PR: https://github.com/OISF/suricata/pull/10612
- 04:58 AM Suricata Bug #6839 (Resolved): coverity: warning in port grouping code
- 04:56 AM Suricata Bug #6843 (Resolved): detect/port: port ranges are incorrect when a port is single as well as a part of range
- 04:56 AM Suricata Bug #6843 (Closed): detect/port: port ranges are incorrect when a port is single as well as a part of range
03/09/2024
- 05:35 AM Suricata Bug #6843 (In Review): detect/port: port ranges are incorrect when a port is single as well as a part of range
- Closed by: https://github.com/OISF/suricata/pull/10602
- 04:17 AM Suricata Bug #6843 (Resolved): detect/port: port ranges are incorrect when a port is single as well as a part of range
Also available in: Atom