[8] Code review request for 6263419: No way to clean the memory for a java.security.Key (original) (raw)
Vincent Ryan vincent.x.ryan at oracle.com
Tue Jan 22 21:17:07 UTC 2013
- Previous message (by thread): [8] Code review request for 6263419: No way to clean the memory for a java.security.Key
- Next message (by thread): [8] Code review request for 6263419: No way to clean the memory for a java.security.Key
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Last call on this. And an updated webrev containing a minor javadoc change to the Implementer's Note in PrivateKey and SecretKey.
Webrev: http://cr.openjdk.java.net/~vinnie/6263419/webrev.01/
Thanks.
On 17/01/2013 17:04, Vincent Ryan wrote:
Hello,
Please review the fix for 6263419. It introduces a mechanism to destroy the sensitive data associated with private keys and secret keys. It is a component of the JEP-166 delivery. Webrev: http://cr.openjdk.java.net/~vinnie/6263419/webrev.00/ Implementers of JCE security providers can override the default method implementations in the Destroyable interface to allow applications to take advantage of this new facility. We intend to update our key implementation classes soon. Thanks.
- Previous message (by thread): [8] Code review request for 6263419: No way to clean the memory for a java.security.Key
- Next message (by thread): [8] Code review request for 6263419: No way to clean the memory for a java.security.Key
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]