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

Quic crypto reassembly 7556 v4 #12615

Closed

Conversation

catenacyber
Copy link
Contributor

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

Describe changes:

  • quic: handle fragment reassembly

SV_BRANCH=OISF/suricata-verify#2301

#12597 with needed rebase better checks for reassembly completeness (in the case we get a packet not bringing in new crypto fragment)

Will alow to have decode_frames accept one additional parameter
with past fragment data
Ticket: 7556

To do so, we need to add 2 buffers (one for each direction)
to the QuicState structure, so that on parsing the second packet
with hello/crypto fragment, we still have the data of the first
hello/crypto fragment.

Use a hardcoded limit so that these buffers cannot grow indefinitely
and set an event when reaching the limit
cf rfc9000 section 19.3. ACK Frames

Ticket: 7556
@catenacyber catenacyber requested a review from a team as a code owner February 18, 2025 20:16
Copy link

codecov bot commented Feb 18, 2025

Codecov Report

Attention: Patch coverage is 85.71429% with 11 lines in your changes missing coverage. Please review.

Project coverage is 80.74%. Comparing base (10ede91) to head (0a80dee).

Additional details and impacted files
@@           Coverage Diff           @@
##           master   #12615   +/-   ##
=======================================
  Coverage   80.74%   80.74%           
=======================================
  Files         931      931           
  Lines      259144   259208   +64     
=======================================
+ Hits       209242   209309   +67     
+ Misses      49902    49899    -3     
Flag Coverage Δ
fuzzcorpus 56.97% <61.33%> (+<0.01%) ⬆️
livemode 19.38% <0.00%> (-0.01%) ⬇️
pcap 44.22% <85.33%> (+0.07%) ⬆️
suricata-verify 63.44% <85.33%> (+0.01%) ⬆️
unittests 58.33% <28.57%> (-0.01%) ⬇️

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

@catenacyber
Copy link
Contributor Author

Next in #12617

@victorjulien
Copy link
Member

Passed my QA. Ran this PR with SV PR OISF/suricata-verify#2301. Local pipeline 5253, run 732.

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.

2 participants