JF Juliana Fajardini Reichow
- Login: jufajardini
- Registered on: 10/11/2020
- Last sign in: 07/13/2026
Issues
| open | closed | Total | |
|---|---|---|---|
| Assigned issues | 66 | 199 | 265 |
| Reported issues | 180 | 291 | 471 |
Projects
| Project | Roles | Registered on |
|---|---|---|
| Suricata | Developer, OISF Team, OISF Manager | 10/13/2020 |
| Suricata-Update | Developer, OISF Team, OISF Manager | 10/13/2020 |
Activity
09/03/2026
- JF 08:01 PM Suricata Bug #8349 (In Review): pgsql: disable parser by default
- PR for review: https://github.com/OISF/suricata/pull/16175
- JF 01:39 PM Suricata Bug #8349 (In Progress): pgsql: disable parser by default
08/24/2026
- JF 09:12 PM Suricata Feature #8943 (Triaged): firewall: properly support rules thresholding
- Rule tables interactions may lead to rule actions being ignored in certain
action scopes in combination with the @thresdhold@ keyword.
Initially, the keyword was banned from firewall mode, but we want to support
@threshold@ in firew... - JF 04:10 PM Suricata Documentation #7298: schema/netflow: add missing field
- Omar Merroun wrote in #note-3:
> s a false positive on sensor_id because the emitting code is behind #if 0 /
Wouldn't this suffice, for tracking them? https://redmine.openinfosecfoundation.org/issues/6478 - JF 03:09 PM Suricata Feature #6350 (Assigned): detect/analyzer: add more details for the tcp.flags keyword
- ILIAS AGORITSAS wrote in #note-9:
> Hi! I’d like to work on this community ticket if it is still available.
> ...
Hi, I have assigned the ticket to you, thanks for wanting to contribute to our project!
As for guidelines, please chec... - JF 12:43 PM Suricata Feature #7391: detect/config: 'scope' can't be applied to 'flow'
- Philippe Antoine wrote in #note-2:
> This is not a bug, just a feature for support of @scope flow@. am I getting it right ?
To me, it's either a bug, or the doc needs improvement. Because from the documentation, I if I see that the `...
08/20/2026
- JF 01:45 PM Suricata Documentation #8899 (In Review): misc: improve suricata code documentation)
- PR for review: https://github.com/OISF/suricata/pull/16051
08/19/2026
- JF 01:42 AM Suricata Bug #8886 (In Review): pgsql: use message type for transaction actions
- As part of a bigger fix, in GL.
- JF 01:38 AM Suricata Bug #8905 (Assigned): pgsql: NoticeResponse and NotificationResponse never pushed to tx
- Due to #8886, some pgsql message types were not covered by the branch where the app-layer parser
actually pushed them to the responses vector.
This also implies that they could never get logged.