Bug #7647
closedpgsql: empty request logged if password message disabled
Description
https://redmine.openinfosecfoundation.org/issues/6603 introduced, still, the possibility of requests being logged empy if there is no password message nor any other frontend message for a given transaction.
Can be seen in the pgsql-copy-done suricata-verify test output.
Updated by Juliana Fajardini Reichow about 1 month ago
- Related to Task #6603: pgsql: don't log password msg if password disabled added
Updated by Juliana Fajardini Reichow 22 days ago
- Related to Optimization #7650: pgsql: clean up logging added
Updated by Juliana Fajardini Reichow 19 days ago
PR for review: https://github.com/OISF/suricata/pull/13094
Updated by Juliana Fajardini Reichow 19 days ago
- Status changed from New to In Review
Updated by Shivani Bhardwaj 18 days ago
- Subject changed from pgsql: fix logging of empty request to pgsql: empty request logged if no frontend message
Updated by Juliana Fajardini Reichow 17 days ago
- Subject changed from pgsql: empty request logged if no frontend message to pgsql: empty request logged if disabled password message
This only happens if there is a password message from the frontend, but password logging is disabled.
So,changing the title a bit :P
Updated by Juliana Fajardini Reichow 17 days ago
- Subject changed from pgsql: empty request logged if disabled password message to pgsql: empty request logged if password message disabled
Updated by Philippe Antoine 9 days ago
I think this should belong to a bigger task of adding minProperties
to all objects in jsonschema
Updated by Juliana Fajardini Reichow 2 days ago
Philippe Antoine wrote in #note-8:
I think this should belong to a bigger task of adding
minProperties
to all objects in jsonschema
Ticket created for tracking work around this: https://redmine.openinfosecfoundation.org/issues/7695
Updated by Juliana Fajardini Reichow 2 days ago
- Status changed from In Review to Closed
Merged with https://github.com/OISF/suricata/pull/13211