JL Jeff Lucovsky
- Login: Jlucovsky
- Registered on: 02/18/2019
- Last sign in: 04/17/2026
Issues
| open | closed | Total | |
|---|---|---|---|
| Assigned issues | 30 | 484 | 514 |
| Reported issues | 42 | 521 | 563 |
Projects
| Project | Roles | Registered on |
|---|---|---|
| Suricata | Developer, OISF Team | 02/18/2019 |
| Suricata-Update | Developer, OISF Team | 02/18/2019 |
Activity
04/29/2026
- JL 12:52 PM Suricata Feature #7672 (Closed): detect/transforms: subslice transform
- Merged in https://github.com/OISF/suricata/pull/15278
04/24/2026
- JL 02:36 PM Suricata Bug #4898 (In Review): detect: Ensure detection events are logged
- https://github.com/OISF/suricata/pull/15257
- JL 02:36 PM Suricata Bug #4482 (In Review): detect: detect events not in rules, not tested (and not working?)
- https://github.com/OISF/suricata/pull/15257
04/23/2026
- JL 01:40 PM Suricata Bug #8489 (In Review): ftp: the "too many transactions" event isn't raised
- https://github.com/OISF/suricata/pull/15247
04/22/2026
- JL 02:10 PM Suricata Bug #8489 (In Progress): ftp: the "too many transactions" event isn't raised
04/20/2026
- JL 12:19 PM Suricata Feature #7313: transforms: have option on how to handle failure
- Yes -- it'd be a breaking change.
I discussed this with @vjulien and we decided to leave the buffer unmodified for transform errors.
04/19/2026
- JL 01:40 PM Suricata Feature #7313: transforms: have option on how to handle failure
- The transform output is used during pre-filtering. Maintaining the buffer on transform error allows that prefiltering to continue to operate as before so that the remainder of the rule can be evaluated.
04/16/2026
- JL 01:44 PM Suricata Bug #8489 (In Review): ftp: the "too many transactions" event isn't raised
- FTP has a configured max-transaction limit; unlike other parsers, it's not raising the event when the limit is exceeded.
04/15/2026
- JL 02:21 PM Suricata Feature #7313: transforms: have option on how to handle failure
- passthrough on error is necessary to maintain pre-filter semantics.
04/13/2026
- JL 02:07 PM Suricata Feature #8470 (New): detect/transform: Create anomaly log on transform failure
- Issue #7114 introduces a way to flag transform errors. Transform errors should also result in an anomaly log with as much contextual information as possible, including specific reasons why the transform failed.