-
-
Notifications
You must be signed in to change notification settings - Fork 26
fix(dtls): replace panicking unwrap/expect in crypto hot paths #68
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
Open
nightness
wants to merge
7
commits into
webrtc-rs:master
Choose a base branch
from
Brainwires:fix/dtls-crypto-panics
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
8f5f19b
fix(dtls): replace panicking unwrap/expect in crypto hot paths
nightness 85a4167
style: cargo fmt
nightness 313c067
address review feedback for PR #68
nightness 2e7018a
fix: address new Copilot review comments (pass 2)
nightness 569d512
test: improve patch coverage for dtls crypto changes
nightness 68783e6
fix: make CryptoPrivateKey fields fully private, fix unreachable code…
nightness 137fe6d
fix: restore graceful error return instead of expect() in flight5
nightness File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
HandshakeConfig::default()now installs aPlaceholderServerCertVerifierthat always errors. SinceHandshakeConfigispub(public API), this makesHandshakeConfig::default()effectively unusable and changes behavior from the previous realWebPkiServerVerifierdefault. Consider keeping a real verifier inDefaultand handling build failures without panicking (e.g.,build().unwrap_or_else(|e| ...)/ logging + fallback), or makeHandshakeConfigconstruction go throughConfigBuilderonly.