Skip to content

Conversation

@catenacyber
Copy link
Contributor

Ticket: 3220

DetectSslVersionMatch did not handle properly negation.
It could never match on a signatrue with ssl_version: !tls1.3
That is because, if we had such a signature and network traffic
with tls1.1, we were looking into DetectSslVersionData field
for tls1.1, which was not set, instead of looking at field
for tls1.3 which was set with negated flag.

Previous DetectSslVersionData was holding redundant information.
It did not need to have it for each ssl version, but just globally.
Also, it did not need to hold the version as a value in the array,
as it was redundant with the index of the array.

(cherry picked from commit c93e698)
@codecov
Copy link

codecov bot commented Dec 8, 2025

Codecov Report

❌ Patch coverage is 60.00000% with 10 lines in your changes missing coverage. Please review.
✅ Project coverage is 83.60%. Comparing base (92dae73) to head (a8c8dd1).

Additional details and impacted files
@@              Coverage Diff               @@
##           main-8.0.x   #14444      +/-   ##
==============================================
+ Coverage       83.58%   83.60%   +0.01%     
==============================================
  Files            1011     1010       -1     
  Lines          265829   265817      -12     
==============================================
+ Hits           222199   222230      +31     
+ Misses          43630    43587      -43     
Flag Coverage Δ
fuzzcorpus 63.42% <25.00%> (+0.01%) ⬆️
livemode 18.68% <0.00%> (+0.03%) ⬆️
pcap 44.56% <0.00%> (-0.01%) ⬇️
suricata-verify 64.87% <50.00%> (+0.04%) ⬆️
unittests 58.90% <40.00%> (-0.01%) ⬇️

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

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@suricata-qa
Copy link

Information: QA ran without warnings.

Pipeline = 28618

@victorjulien victorjulien added this to the 8.0 milestone Dec 9, 2025
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