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

Does Bouncy Castle support AES native instructions (AES-NI)? #221

Closed
wschlich opened this issue Sep 4, 2017 · 2 comments
Closed

Does Bouncy Castle support AES native instructions (AES-NI)? #221

wschlich opened this issue Sep 4, 2017 · 2 comments

Comments

@wschlich
Copy link

wschlich commented Sep 4, 2017

This document suggests that BC does not:

• Provider library choice significantly impacts results. The choice of encryption provider library and AES mode had the largest impact on performance. While Bouncy Castle showed no appreciable improvement with respect to Intel® AES-NI, the NSS library with Intel® AES-NI enabled performed more than 78% faster than Bouncy Castle and is the obvious choice for encryption. For decryption, NSS was approximately 96% faster than Bouncy Castle and 90% faster than SunJCE.

https://www.intel.com/content/www/us/en/healthcare-it/solutions/documents/aes-ni-boosts-security-and-performance-genospace-study.html

@bcgit
Copy link
Collaborator

bcgit commented Sep 5, 2017

Correct, we don't at the moment, either in the FIPS or general stream. We are a pure Java solution.

There's no reason we couldn't (I guess) dealing with it is simply a time/funding problem.

@wschlich
Copy link
Author

wschlich commented Sep 5, 2017

Too bad :( Thanks for responding!

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

No branches or pull requests

1 participant