2011-11-09 04:51:59 +01:00
|
|
|
o Code simplification and refactoring:
|
|
|
|
- Unconditionally use OpenSSL's AES implementation instead of our
|
|
|
|
old built-in one. OpenSSL's AES has been better for a while, and
|
|
|
|
relatively few servers should still be on any version of OpenSSL
|
|
|
|
that doesn't have good optimized assembly AES.
|
|
|
|
|
2011-11-21 03:43:14 +01:00
|
|
|
o Major features (AES performance):
|
2011-11-09 04:51:59 +01:00
|
|
|
- Use OpenSSL's EVP interface for AES encryption, so that all
|
|
|
|
AES operations can use hardware acceleration (if present).
|
|
|
|
Resolves issue #4442.
|
2011-11-21 03:20:31 +01:00
|
|
|
- But only use the EVP interface when AES acceleration is enabled,
|
|
|
|
to avoid a performance regression. Resolves issue #4525.
|
2011-11-21 03:43:14 +01:00
|
|
|
- When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
|
|
|
|
implementation; it makes AES_CTR about 7% faster than our old one
|
|
|
|
(which was about 10% faster than the one OpenSSL used to provide).
|
|
|
|
Resolves issue #4526.
|