<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Thanks Mike. Both those classes were extended, as you suggest, for JDK 8:<div> <a href="http://hg.openjdk.java.net/jdk8/jdk8/jdk/rev/8ee6d45348ba">http://hg.openjdk.java.net/jdk8/jdk8/jdk/rev/8ee6d45348ba</a></div><div><br></div><div>A separate effort is also underway to enhance the classes that implement</div><div>SecretKey and PrivateKey.</div><div><br></div><div><font class="Apple-style-span" face="sans-serif">Applications may first check whether a key class is an instance of Destroyable</font></div><div><font class="Apple-style-span" face="sans-serif">or they may call the key's destroy method and handle the possible exception.</font></div><div><font class="Apple-style-span" face="sans-serif"><br></font></div><div><font class="Apple-style-span" face="sans-serif"><br></font><div><div><div>On 14 Jun 2013, at 17:42, Michael StJohns wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Generic questions for possible future work:<br><br>As a general guideline, would it make sense to add javax.security.auth.Destroyable to the set of interfaces for SecretKey and PrivateKey implementation objects where possible?<br><br>Should the methods that use secret and private keys check to see if those keys implement the Destroyable interface to see if they should call isDestroyed() from that interface prior to using the key?<br><br>Mike<br><br></div></blockquote></div><br></div></div></body></html>