-
-
Notifications
You must be signed in to change notification settings - Fork 3
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
Add BoringSSL based native HPKE implementation #19
Conversation
10a3c53
to
5ce3de1
Compare
107f126
to
c8c8824
Compare
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
56af50e
to
133ed69
Compare
Motivation: While we already have a BouncyCastle based HPKE implementation that we can use we should also offer an implementation which is faster and so reduce the performance overhead. Modifications: Add native implementation based on BoringSSL. Result: Fixes #5
133ed69
to
263831d
Compare
40b1228
to
4a24831
Compare
2e48a6c
to
8045912
Compare
Motivation:
While we already have a BouncyCastle based HPKE implementation that we can use we should also offer an implementation which is faster and so reduce the performance overhead.
Modifications:
Add native implementation based on BoringSSL.
Result:
Fixes #5