Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

detect/tls.certs: fix direction handling #10265

Closed
wants to merge 1 commit into from

Conversation

victorjulien
Copy link
Member

Direction flag was checked against wrong field, leading to undefined behavior.

Spotted this by accident, no ticket or test case made.

Direction flag was checked against wrong field, leading to undefined behavior.
Copy link

codecov bot commented Jan 27, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (c3b3c11) 82.28% compared to head (1304ed5) 82.31%.

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #10265      +/-   ##
==========================================
+ Coverage   82.28%   82.31%   +0.02%     
==========================================
  Files         977      977              
  Lines      271950   271950              
==========================================
+ Hits       223784   223846      +62     
+ Misses      48166    48104      -62     
Flag Coverage Δ
fuzzcorpus 63.48% <100.00%> (+0.08%) ⬆️
suricata-verify 61.50% <100.00%> (-0.03%) ⬇️
unittests 62.82% <100.00%> (ø)

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

@suricata-qa
Copy link

Information: QA ran without warnings.

Pipeline 17800

@jufajardini
Copy link
Contributor

@jasonish
Copy link
Member

Backport required? If would, would be nice to have the ticket ID in the commit.

@victorjulien
Copy link
Member Author

Backport required? If would, would be nice to have the ticket ID in the commit.

Ya, done in #10405

@victorjulien victorjulien deleted the tlscerts-fixup/v1 branch February 20, 2024 12:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
4 participants