> -----Original Message----- > From: Kusztal, ArkadiuszX <[email protected]> > Sent: Wednesday, July 29, 2020 3:22 PM > To: [email protected] > Cc: [email protected]; Trahe, Fiona <[email protected]>; > [email protected]; [email protected]; Doherty, Declan > <[email protected]>; Zhang, Roy Fan <[email protected]>; > Ananyev, Konstantin <[email protected]>; Kusztal, ArkadiuszX > <[email protected]> > Subject: [PATCH] [RFC] cryptodev: move AES-GMAC to aead algorithms > > This is proposal to move AES-GMAC algorithm to AEAD set > of algorithms. It is however not 100% conformant GMAC as instead of aad > pointer > data to be authenticated is passed normally and aead.data.length field > is used to specify length of data to be authenticated. > Reason behind this move is that GMAC is variant of GCM so it may > simplify implementations that are using these algorithms (mainly IPsec). > AES-GMAC therefore needs to be removed from auth algorithms. > > Signed-off-by: Arek Kusztal <[email protected]>
Acked-by: Fan Zhang <[email protected]>
