Andre ten Bohmer
- Login: atbohmer
- Registered on: 05/13/2023
- Last sign in: 09/25/2024
Issues
open | closed | Total | |
---|---|---|---|
Assigned issues | 0 | 0 | 0 |
Reported issues | 3 | 3 | 6 |
Activity
09/25/2024
- 01:16 PM Suricata Bug #7256: ja3: Error: ja3: Buffer should not be NULL
- # suricatasc -c version
{"message": "8.0.0-dev (45eb7e488 2024-09-24)", "return": "OK"}
Problem seems to be resol...
09/17/2024
- 11:58 AM Suricata Bug #7256 (Closed): ja3: Error: ja3: Buffer should not be NULL
- ...
08/08/2024
- 01:41 PM Suricata Bug #7201: Thread 178 "W#21-84:00.0" received signal SIGSEGV, Segmentation fault.
- ]# suricata -V
This is Suricata version 8.0.0-dev (564a6c9a2 2024-08-07)
Running smooth again. Also modified suri...
08/06/2024
- 02:34 PM Suricata Bug #7201: Thread 178 "W#21-84:00.0" received signal SIGSEGV, Segmentation fault.
- Probably by default:
]# grep -i ldap /etc/suricata/suricata.yaml -c
0 - 01:50 PM Suricata Bug #7201: Thread 178 "W#21-84:00.0" received signal SIGSEGV, Segmentation fault.
- See attached file, full script session of gdb with bt at the end.
- 01:21 PM Suricata Bug #7201: Thread 178 "W#21-84:00.0" received signal SIGSEGV, Segmentation fault.
- ldap is not enabled due to older suricata.yaml config (so also time to update this ;)
- 11:33 AM Suricata Bug #7201: Thread 178 "W#21-84:00.0" received signal SIGSEGV, Segmentation fault.
- Prio can be lowered: working fallback to
~]# suricatasc -c version
{"message": "7.0.6 RELEASE", "return": "OK"} - 11:25 AM Suricata Bug #7201: Thread 178 "W#21-84:00.0" received signal SIGSEGV, Segmentation fault.
- ...
- 11:21 AM Suricata Bug #7201 (New): Thread 178 "W#21-84:00.0" received signal SIGSEGV, Segmentation fault.
- ...
- 08:54 AM Suricata Bug #7200 (In Progress): Suricata[239866]: Error: byte: Extra characters following numeric value [ByteExtractString:util-byte.c:227]
- Logging to suricata.log:...
Also available in: Atom