Bug #22570 - AES-GCM should provide distinct inputs/outputs for tag

At this point, am I correct in assuming that the only issue for this bug is
to do the edits in the document that the decision to make the tag and nonce
separate items?

 

If not then can we start the discussion on this issue.

 

I would also like to point out that the JOSE working group decided that the
data encryption and key encryption versions of AES-GCM would have different
names.  Thus there is A128GCM and A128GCMKW.  This decision was made for
cryptographic purity reasons (don't mix different types of input).  I don't
know if we want to follow that decision here as well.

 

Jim

 

Received on Saturday, 25 January 2014 00:39:04 UTC