Thanks for the answer, I will use those params. Is your platform using Bouncy Castle under the hood or is it using another type of lib?
Benoit De : Sid Shetye <s...@crypteron.com> Envoyé : 16 octobre 2019 16:46 À : Benoit Laforest <benoit.lafor...@ubisoft.com> Cc : dev-crypto-csharp@bouncycastle.org Objet : Re: [dev-crypto-csharp] About the size of the IV vector for AES GCM Go with 96 bits for IV and 128 bits for the tag/mac. Also, if you're looking for an key management and data security platform that integrates in minutes, check us out at crypteron.com<https://www.crypteron.com> -- Sid Shetye C: (858) 342-1617<tel:8583421617> [http://cdn.crypteron.com/assets/crypteron-email-logo.png?v=4]<https://www.crypteron.com> On Wed, Oct 16, 2019 at 10:30 AM Benoit Laforest <benoit.lafor...@ubisoft.com<mailto:benoit.lafor...@ubisoft.com>> wrote: Hi, According to the NIST recommendation, 96 bit would be the ideal size of the IV vector for AES GCM. What about the MAC size? Should it be 96 bits also or 128? I ask because in the file GCMTests.cs I noticed that all the tests are made with a IV size of 128 bits and a Max Size of 128 bits also. Any help is welcome. 😊 Benoit
