cross our toolkits? We could also do it over email if time-zones
don't work out. I know 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 ;
riginal reasons for doing so no longer apply).
Regards,
David
On 21/8/22 13:52, Michael StJohns wrote:
On 8/20/2022 2:08 PM, David Hook wrote:
Hi Michael,
I don't know anything about bureaucrats, I am an engineer. You may
need to consult someone else on bureaucrats.
I apologize for my a
(encapsulation);
As I said, "could look like", I'm not saying "should", but it's really
much cleaner, simpler, and less confusing than the first two, and I
really think the above demonstrates that these new algorithms are really
not properly covered in the existing
t should return UnsupportedOperationException for all
operations execept wrap/unwrap and the appropriate init methods.
Later, Mike
On 8/19/2022 6:38 PM, David Hook wrote:
Hi Mike,
KEMs can be used for key wrapping - we've actually implemented
support for this too. But they are not
Hi Mike,
KEMs can be used for key wrapping - we've actually implemented support
for this too. But they are not actually key wrapping ciphers.
Here's a simple example of using Kyber for key wrapping in BC:
SecretKey key =new SecretKeySpec(keyBytes,"AES");
w1.init(Cipher.WRAP_MODE, kp.getPubli
I'd like to just add a supporting comment on this by showing what we've
currently done.
At the moment KEM usage in the JCA is provided in the BC API by doing
the following:
// key pair generation
KeyPairGenerator kpg = KeyPairGenerator.getInstance("Kyber",
"BCPQC");
kpg.i
