Nevermind: I figured out what I failed to understand.
The handlers that use CMAC and are size locked are on the client to
server path. The server to client path *does* allow for additional data.
Nothing to see here, move along.
--
/"In the end; what separates a Man, from a Slave? Money? Powe
On 6/23/19 4:09 PM, Daniel Franke wrote:
The translation of the AEEF ciphertext into corresponding plaintext is
given by the negotiated AEAD algorithm; for AES-SIV, by RFC 5297. The
structure of the plaintext is defined in the draft, as a concatenation
of RFC 7822 extension fields.
This mat
The translation of the AEEF ciphertext into corresponding plaintext is
given by the negotiated AEAD algorithm; for AES-SIV, by RFC 5297. The
structure of the plaintext is defined in the draft, as a concatenation of
RFC 7822 extension fields.
On Sun, Jun 23, 2019, 16:42 Ian Bruene via devel wrote:
While working on the NTS test code I have reached a point where I know
that I am misunderstanding *something*, but do now know what.
According to the RFC the AEEF "ciphertext" field looks like it is a
generally usable data blob for extension data. Variable size, no
specific data, etc.
Acco
