-
Enhancement
-
Resolution: Fixed
-
P4
-
8
-
b55
-
generic
-
generic
-
Not verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8018568 | 7u45 | Sean Coffey | P4 | Closed | Fixed | b01 |
| JDK-2228876 | 7u40 | Sean Coffey | P3 | Closed | Fixed | b08 |
| JDK-8000367 | 7u10 | Sean Coffey | P4 | Closed | Fixed | b12 |
Consider an application which holds on to a Cipher object for AES and keeps the same key but calls Cipher.init to change the Cipher between encryption and decryption. The current code in AESCrypt.java recomputes the expanded key (which is an expensive operation) with each call to init.
One possible optimization is to save the key and, if it has not changed, skip recomputation on subsequent calls to Cipher.init. It'd also benefit the performance if the key expansion which currently is done in the method setSubKey() is moved to the same time when the keys are recomputed.
One possible optimization is to save the key and, if it has not changed, skip recomputation on subsequent calls to Cipher.init. It'd also benefit the performance if the key expansion which currently is done in the method setSubKey() is moved to the same time when the keys are recomputed.
- backported by
-
JDK-2228876 Avoid key expansion when AES cipher is re-init w/ the same key
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- relates to
-
-
- Resolved
-
-
JDK-8046154 JEP 164: Leverage CPU Instructions for AES Cryptography
-
- Closed
-