> Earlier code will trigger NPE if the certificate does not contain the
> extensions or if the requested extensions does not exist. The better approach
> for hardening **getExtensionValue** here is to to check for NULL explicitly
> before calling **getExtensionValue()** and avoding try-catch blo
On Sat, 15 Feb 2025 22:33:46 GMT, Bradford Wetmore wrote:
>> The example code in the JEP was much clearer than that in the current `KEM`
>> class. It's easier to keep the various nested classes straight, rather than
>> using `var`s which require scrolling to see what the return types are.
>>
On Sat, 15 Feb 2025 05:02:44 GMT, Bradford Wetmore wrote:
> The example code in the JEP was much clearer than that in the current `KEM`
> class. It's easier to keep the various nested classes straight, rather than
> using `var`s which require scrolling to see what the return types are.
>
> A
> The example code in the JEP was much clearer than that in the current `KEM`
> class. It's easier to keep the various nested classes straight, rather than
> using `var`s which require scrolling to see what the return types are.
>
> Added/tweaked example for clarity.
>
> Generated/checked jav
> The example code in the JEP was much clearer than that in the current `KEM`
> class. It's easier to keep the various nested classes straight, rather than
> using `var`s which require scrolling to see what the return types are.
>
> Added/tweaked example for clarity.
>
> Generated/checked jav
On Sat, 15 Feb 2025 14:28:04 GMT, Weijun Wang wrote:
>> The example code in the JEP was much clearer than that in the current `KEM`
>> class. It's easier to keep the various nested classes straight, rather than
>> using `var`s which require scrolling to see what the return types are.
>>
>> A
On Sat, 15 Feb 2025 14:28:04 GMT, Weijun Wang wrote:
>> The example code in the JEP was much clearer than that in the current `KEM`
>> class. It's easier to keep the various nested classes straight, rather than
>> using `var`s which require scrolling to see what the return types are.
>>
>> A
On Thu, 13 Feb 2025 16:27:03 GMT, Sean Mullan wrote:
> This change adds an API note to these methods recommending that the caller
> should perform further validation steps on the code signers that signed the
> JAR file, such as validating the code signer's certificate chain, and
> determining
On Sat, 15 Feb 2025 05:02:44 GMT, Bradford Wetmore wrote:
> The example code in the JEP was much clearer than that in the current `KEM`
> class. It's easier to keep the various nested classes straight, rather than
> using `var`s which require scrolling to see what the return types are.
>
> A
