composite algorithms and
hybrid certificates. 😊 So the JCA has stood up well after so many years.
I’m looking forward to the new KEM API’s that you are adding for us.
Cheers,
John Gray
From: Eirik Bjørsnøs
Sent: Monday, April 17, 2023 10:58 AM
To: John Gray
Cc: security-dev
our toolkit because this
change will break things in a number of areas in Java 19.I guess we have
until the next LTS to do all this work… ☹
John Gray
Entrust
From: security-dev On Behalf Of Eirik Bjørsnøs
Sent: Monday, April 17, 2023 4:00 AM
To: security-dev@openjdk.org
Subject: [EXTERNAL
Thanks for this update.
It is possible future KEMs could have variable length shared-secret sizes, so
having the ability to be flexible is needed. Looks like you have covered all
possible cases here.
Thanks for these additions!
Cheers,
John Gray
Entrust
-Original Message-
From
now David is in Australia, I am in Canada (Eastern Time).
Cheers,
John Gray
-Original Message-
From: Franco Nieddu
Sent: Thursday, August 25, 2022 2:33 AM
To: John Gray ; David Hook ;
Michael StJohns
Cc: security-dev@openjdk.org
Subject: Re: [EXTERNAL] Re: Is there a KEM (Key Encapsul
ateKey);
byte[] ss = KEM.decapsulate(cipherText)
or maybe even better:
KEM.init(publicKey);
byte[] cipherText = KEM.encapsulate()
byte[] sharedSecret = KEM.getSharedSecret()
And then
KEM.init(privateKey);
byte[] ss = KEM.decapsulate(cipherText)
Cheers,
John Gray
From: David Hook
Sent:
NIST standardization process, so it makes sense for us to implement a
proper KEM interface in Java now.
Cheers,
John Gray
From: David Hook
Sent: Friday, August 19, 2022 6:38 PM
To: Mike StJohns ; John Gray
Cc: security-dev@openjdk.org
Subject: [EXTERNAL] Re: Is there a KEM (Key Encapsulation Mech
ot have to
worry about incompatibility issues down the road...
Cheers,
John Gray
Any email and files/attachments transmitted with it are confidential and are
intended solely for the use of the individual or entity to whom they are
addressed. If this message has been sent to you in error, you mu
