RFR: 8208583: Better management of internal KeyStore buffers

[Weijun Wang]

Some comments:

1. Is it possible to let rename PBEKey::clearKey to PNEKey::destroy?

2. I am not sure if the newly added "Arrays.fill(thatEncoded, (byte)0x00)" line in PBEKey::equals is safe. What if that key does not return a cloned copy when getEncode() is called? This is possible if the class is only used internally and never escape.

3. You would need to modify the spec of s.s.p.KeyProtector::<init> since password is of a new type. In fact, is this change necessary? Just to prevent the duplication of code in convertToBytes()?

4. I found the last line of PBEKey::<init> might be modified to

   CleanerFactory.cleaner().register(this, this::clearKey);

I have never been a lambda expert so forgive me if this is not correct.

Thanks
Max

> On Aug 1, 2018, at 3:11 AM, Seán Coffey <sean.coffey at oracle.com> wrote:
> 
> Looking to improve management of internal buffers in KeyStore. The com.sun.crypto.provider.KeyProtector class uses the PBEKey class to protect some keys. Buffers can be freed up earlier if the caller takes responsibility for lifecycle of PBEKey object. (hence no reliance on Cleaner). Some other minor improvements made while visiting this area.
> 
> Other improvements in sun.security.provider.KeyProtector where I believe the password buffer can be managed by the caller.  I only found 2 instances of where this class is used.
> 
> https://bugs.openjdk.java.net/browse/JDK-8208583
> http://cr.openjdk.java.net/~coffeys/webrev.8208583.v1/webrev/index.html
> 
> regards,
> Sean.
>