ffdhe branch: tracking PR to run CI #28
Conversation
* Implement FFDHE support in mbedcrypto-provider * Add test for bad FFDHE public keys * Address review comments * Update rustls dependency to one based on 0.22.1 in Cargo.lock --------- Co-authored-by: Arash Sahebolamri <[email protected]>
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #28 +/- ##
==========================================
- Coverage 94.58% 94.28% -0.31%
==========================================
Files 17 16 -1
Lines 2272 2169 -103
==========================================
- Hits 2149 2045 -104
- Misses 123 124 +1 ☔ View full report in Codecov by Sentry. |
…s-list Avoid sending empty root hints list
Export types enable user to create customized cipher suites.
Export hash types
+ Update rustls dep to `ffdhe-r3`
…nce)
- Apply suggestions from code review
- Co-authored-by: YX Cao <[email protected]>
- Signed-off-by: Arash Sahebolamri <[email protected]>
…ion (#38) Co-authored-by: Arash Sahebolamri <[email protected]>
Upgrade rustls to add support of new config option for requiring peer support of extended master secret extension.
Upgrade rustls to tag `ffdhe-r4` for new config support: Upgrade rustls to add support of new config option for requiring peer support of extended master secret extension.
This PR merges `master` into `ffdhe` which results following changes: - Update `mbedtls` version to `0.12.2` - Bump some dependencies version in Cargo.lock file.
- Add a Known answer Cryptographic Algorithm Self Test for FFDHE cipher suites.
Add ffdhe self-test
|
Not needed anymore, as FFDHE was upstreamed. |
|
Note: I should create a PR to merge ffdhe into master based on the upstream rustls. |
|
@s-arash , Yes, are you going to create PR recently? |
|
@Taowyoo on second thought, maybe we should wait for rustls to make a new release with ffdhe support included. Because if we do that now, we cannot target the crates.io rustls. |
|
Make sense! |
No description provided.