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

websocket: fix opcodes values for ping/pong #11065

Closed

Conversation

catenacyber
Copy link
Contributor

@catenacyber catenacyber commented May 14, 2024

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

Describe changes:

  • websocket: fix opcodes values for ping/pong and also set close

SV_BRANCH=OISF/suricata-verify#1829

And also set close

Ticket: 7025
@victorjulien
Copy link
Member

Can we add tests somehow so we would have caught this?

@catenacyber
Copy link
Contributor Author

Can we add tests somehow so we would have caught this?

Finaly found a pcap : OISF/suricata-verify#1829

Copy link

codecov bot commented May 14, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 83.62%. Comparing base (cb56752) to head (d8d4ed1).

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #11065      +/-   ##
==========================================
- Coverage   83.63%   83.62%   -0.01%     
==========================================
  Files         922      922              
  Lines      250321   250321              
==========================================
- Hits       209349   209327      -22     
- Misses      40972    40994      +22     
Flag Coverage Δ
fuzzcorpus 64.20% <ø> (-0.03%) ⬇️
livemode 18.46% <ø> (+0.03%) ⬆️
suricata-verify 62.76% <ø> (+<0.01%) ⬆️
unittests 62.26% <ø> (ø)

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

@victorjulien victorjulien added this to the 8.0 milestone May 14, 2024
@victorjulien
Copy link
Member

Merged in #11072, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants