Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Replace P-256 arithmetic with BoringSSL's P-256 arithmetic. #1011

Merged
merged 2 commits into from
Feb 10, 2021

Conversation

briansmith
Copy link
Owner

Use Fiat Crypto for non-x86_64 platforms, like BoringSSL. Continue using the nistz256 code on Windows, differently from BoringSSL.

Make ring more consistent with BoringSSL.

@briansmith briansmith self-assigned this Jun 15, 2020
@briansmith briansmith force-pushed the b/use-boringssl-p256 branch 5 times, most recently from 1874cbb to b058727 Compare June 17, 2020 16:18
@briansmith briansmith changed the title Replace *ring*'s P-256 arithmetic with BoringSSL's P-256 arithmetic. Replace P-256 arithmetic with BoringSSL's P-256 arithmetic. Jun 17, 2020
@briansmith briansmith changed the base branch from master to main November 30, 2020 20:10
@briansmith briansmith force-pushed the b/use-boringssl-p256 branch 3 times, most recently from 87048ad to 5c60c43 Compare December 1, 2020 18:12
@briansmith briansmith force-pushed the b/use-boringssl-p256 branch from 5c60c43 to 94b542a Compare February 5, 2021 20:49
@codecov
Copy link

codecov bot commented Feb 5, 2021

Codecov Report

Merging #1011 (415dee1) into main (46d4362) will increase coverage by 1.34%.
The diff coverage is 99.61%.

Impacted file tree graph

@@            Coverage Diff             @@
##             main    #1011      +/-   ##
==========================================
+ Coverage   92.22%   93.56%   +1.34%     
==========================================
  Files         106      111       +5     
  Lines       14232    17337    +3105     
==========================================
+ Hits        13125    16221    +3096     
- Misses       1107     1116       +9     
Impacted Files Coverage Δ
crypto/fipsmodule/ec/gfp_p384.c 100.00% <ø> (ø)
crypto/internal.h 94.91% <ø> (ø)
src/ec/suite_b/ops/p384.rs 100.00% <ø> (ø)
src/ec/suite_b/ops.rs 96.39% <52.63%> (-0.68%) ⬇️
crypto/fipsmodule/ec/p256-x86_64.c 97.18% <97.18%> (ø)
crypto/fipsmodule/ec/gfp_p256.c 100.00% <100.00%> (ø)
crypto/fipsmodule/ec/p256-x86_64.h 100.00% <100.00%> (ø)
crypto/fipsmodule/ec/p256.c 100.00% <100.00%> (ø)
crypto/fipsmodule/ec/p256_shared.h 100.00% <100.00%> (ø)
crypto/fipsmodule/ec/util.h 100.00% <100.00%> (ø)
... and 17 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 46d4362...415dee1. Read the comment docs.

Don't require a specialized implementation of field element addition for
each curve; instead share an implementation between RSA and ECC.

Refactor the code to avoid needing `elem_sum`.
Use Fiat Crypto for non-x86_64 platforms, like BoringSSL. Continue
using the nistz256 code on Windows, differently from BoringSSL.

Make *ring* more consistent with BoringSSL.
@briansmith briansmith force-pushed the b/use-boringssl-p256 branch from 94b542a to 415dee1 Compare February 8, 2021 18:54
@briansmith briansmith merged commit 501fc4e into main Feb 10, 2021
@briansmith briansmith deleted the b/use-boringssl-p256 branch February 10, 2021 20:20
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant