Awesome.
I just posted in another thread to the mailing list with some examples
where more flexibility would be needed. "PKCS#11 provider issues with
min and max size".
Another example would be to add flexibility to be more crypto "agile".
I.e. when new algorithms come out, for example SHA3. It
Hi Tomas,
As Andrew said, I've been working on some SunPKCS11 improvements related to
native memory leaking. You can find details of this work here [1]. Feedback
is always welcomed.
What do you mean with "more flexibility"?
--
[1] -
On 24/01/18 10:39, Tomas Gustavsson wrote:
> Imho the P11 layer always needs attention. To work properly we're
> relying on some patches, where parts was recently merged into OpenJDK.
> We just started testing the Amazon CloudHSM, and that requires changes
> to SunPKCS11 as well to work. Not
Sorry for jumping in :-)
Imho the P11 layer always needs attention. To work properly we're
relying on some patches, where parts was recently merged into OpenJDK.
We just started testing the Amazon CloudHSM, and that requires changes
to SunPKCS11 as well to work. Not always bad in SunPKCS11 as
Thanks Sean, I've filled out the OCA and sent it in. I'll take a gander
around after reading up on the link you posted and see where we might be
able to jump in and assist.
Leo
On 1/17/2018 7:53 AM, Sean Mullan wrote:
Hi Leo,
Thanks for the offer to help and contribute! I would suggest you
Hi Leo,
Thanks for the offer to help and contribute! I would suggest you start
by reading the OpenJDK contribution page (if you have not done so already):
http://openjdk.java.net/contribute/
which has some tips and other helpful advice. You will also need to sign
an OCA (Oracle Contributor
Hello Everyone,
I'd like to introduce myself. I'm Leo Grove, founder of SSL.com and also
Java Certified Programmer ('98). Although I'm not so much into coding
these days, I'm always looking for ways to contribute to internet
security and the public WebPKI. We do have some very sharp java
