On Fri, Dec 04, 2009 at 05:31:43PM +0100, Tobias Brunner wrote:
This patch adds the RFC4543 (GMAC) wrapper for GCM similar to the
existing RFC4106 wrapper. The main differences between GCM and GMAC are
the contents of the AAD and that the plaintext is empty for the latter.
Signed-off-by:
+u8 auth_tag[16];
This field needs to be aligned to whatever alignment needed by
the underlying cipher algorithm (currently the biggest is padlock
which needs 16-byte alignment).
Didn't realize that, thanks. I fixed the aligning according to
how it's done in GCM.
Regards,
Tobias
On Tue, Dec 01, 2009 at 05:49:28PM +0100, Tobias Brunner wrote:
This patch adds the RFC4543 (GMAC) wrapper for GCM similar to the
existing RFC4106 wrapper. The main differences between GCM and GMAC are
the contents of the AAD and that the plaintext is empty for the latter.
Signed-off-by:
From: Tobias Brunner tob...@strongswan.org
Date: Tue, 01 Dec 2009 17:49:28 +0100
This patch adds the RFC4543 (GMAC) wrapper for GCM similar to the
existing RFC4106 wrapper. The main differences between GCM and GMAC are
the contents of the AAD and that the plaintext is empty for the latter.
On Tue, Dec 01, 2009 at 03:51:41PM -0800, David Miller wrote:
From: Tobias Brunner tob...@strongswan.org
Date: Tue, 01 Dec 2009 17:49:28 +0100
This patch adds the RFC4543 (GMAC) wrapper for GCM similar to the
existing RFC4106 wrapper. The main differences between GCM and GMAC are
the
