Skip to content

pgsql: low hanging fruits - v1#10830

Closed
jufajardini wants to merge 2 commits into
OISF:masterfrom
jufajardini:pgsql-3827-logger/v1
Closed

pgsql: low hanging fruits - v1#10830
jufajardini wants to merge 2 commits into
OISF:masterfrom
jufajardini:pgsql-3827-logger/v1

Conversation

@jufajardini
Copy link
Copy Markdown
Contributor

While starting review for the LDAP protocol parser, noticed that we had a TODO for adding a simpler logger function for PGSQL, following up #9851.

Link to redmine ticket:
https://redmine.openinfosecfoundation.org/issues/6092

Describe changes:

  • Add a simpler caller to pgsql's logger, that could be used with the "new" simple_lson_applayer_loggers used MQTT style as example for this
  • Handle eof when parsing a response the same way as done when parsing a request - no ticket for this one

It was brought to my attention by GLongo that Pgsql parser handled eof
diffrently for requests and responses, and apparently there isn't a good
reason for such a difference therefore, apply same logic used for
rs_pgsql_parse_request for checking for eof when parsing a response.
@codecov
Copy link
Copy Markdown

codecov Bot commented Apr 13, 2024

Codecov Report

Attention: Patch coverage is 50.00000% with 3 lines in your changes are missing coverage. Please review.

Project coverage is 82.67%. Comparing base (172b55c) to head (92baded).

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #10830      +/-   ##
==========================================
- Coverage   82.75%   82.67%   -0.09%     
==========================================
  Files         928      928              
  Lines      247913   247918       +5     
==========================================
- Hits       205162   204966     -196     
- Misses      42751    42952     +201     
Flag Coverage Δ
fuzzcorpus 64.00% <16.66%> (-0.24%) ⬇️
suricata-verify 62.01% <50.00%> (+<0.01%) ⬆️
unittests 62.17% <0.00%> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

@victorjulien
Copy link
Copy Markdown
Member

This is mostly about alert enrichment, right? If so, can you add an SV test for it?

@suricata-qa
Copy link
Copy Markdown

Information: QA ran without warnings.

Pipeline 20039

@jufajardini
Copy link
Copy Markdown
Contributor Author

Replaced by: #10853

@jufajardini jufajardini deleted the pgsql-3827-logger/v1 branch April 16, 2024 17:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants