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

Improved path challenge handling. #483

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

rthalley
Copy link
Contributor

  1. We are willing to reply to up to 5 outstanding challenges on a connection, as it is legal for a client to send more than one. We limit to 5 to prevent excessive challenging.

  2. We now accept path challege responses on any network path, in accordance with RFC 9000 section 8.2.3.

Copy link

codecov bot commented Mar 10, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (ae282aa) to head (f8eee22).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #483   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           25        25           
  Lines         4966      4978   +12     
=========================================
+ Hits          4966      4978   +12     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@rthalley
Copy link
Contributor Author

This patch addresses the issue raised by [#189], though with a different implementation. It also addresses another issue, which is that we may need to reply to more than one remote challenge on the same path. Both sides are bounded, currently to 5 items, to avoid any possible resource attack. There are tests and coverage remains at 100%.

@rthalley
Copy link
Contributor Author

I will lint this one further and push an update tonight or tomorrow morning

1) We are willing to reply to up to 5 outstanding challenges
on a connection, as it is legal for a client to send more than
one.  We limit to 5 to prevent excessive challenging.

2) We now accept path challege responses on any network path,
in accordance with RFC 9000 section 8.2.3.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant