ed we can enhance
ChaCha20 classes to support it.
--Jamil
Original message From: Bernd Eckenfels
Date: 1/27/18 9:42 AM (GMT-08:00) To: Jamil Nimeh
, OpenJDK Dev list
Subject: Re: Proposal: ChaCha20 and ChaCha20-Poly1305 Cipher implementations
Hello Jamil, thanks BTW for bri
wonder,
do we need tp provide it at all?
Gruss
Bernd
--
http://bernd.eckenfels.net
Von: Jamil Nimeh
Gesendet: Freitag, 26. Januar 2018 22:57
An: Bernd Eckenfels; OpenJDK Dev list
Betreff: Re: Proposal: ChaCha20 and ChaCha20-Poly1305 Cipher implementations
Hi Bernd, thank you for the feedback!
On 01
Hi Bernd, thank you for the feedback!
On 01/25/2018 12:30 PM, Bernd Eckenfels wrote:
You Hello,
The spec should most likely mention AAD data as well and the 12 Byte
size of the nonce. And that the plaintext Limit is in blocks (and the
AAD Limit is a 64Bit counter)
Good point about AAD. My c
You Hello,
The spec should most likely mention AAD data as well and the 12 Byte size of
the nonce. And that the plaintext Limit is in blocks (and the AAD Limit is a
64Bit counter)
(And yes there is no wrapping to be found, not even in RFC 8103 which discusses
key transport,)
Does it need to d
On 1/25/2018 11:45 AM, Adam Petcher wrote:
On 1/25/2018 12:20 PM, Jamil Nimeh wrote:
Wrap and Unwrap: I have not been able to find a standardized
wrap/unwrap format for ChaCha20 similar to RFC 3394 for AES. Right
now the wrap() and unwrap() methods just take the encoding of the key
to be wrap
On 1/25/2018 12:20 PM, Jamil Nimeh wrote:
Wrap and Unwrap: I have not been able to find a standardized
wrap/unwrap format for ChaCha20 similar to RFC 3394 for AES. Right now
the wrap() and unwrap() methods just take the encoding of the key to
be wrapped and encrypts or decrypts them respective
