NTS AEEF extension confusion

[Daniel Franke]

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 <devel at ntpsec.org> 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.
>
> According to the code the AEEF "CMAC" field which is in the same spot
> looks like a fixed length data blob with a very specific meaning.
>
> These do not match up, and I do not know what I am missing.
>
> --
> *"In the end; what separates a Man, from a Slave? Money? Power? No. A Man
> Chooses, a Slave Obeys."* -- Andrew Ryan
>
> *"Utopia cannot precede the Utopian. It will exist the moment we are fit
> to occupy it."* -- Sophia Lamb
> _______________________________________________
> devel mailing list
> devel at ntpsec.org
> http://lists.ntpsec.org/mailman/listinfo/devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ntpsec.org/pipermail/devel/attachments/20190623/83702911/attachment.htm>