- GFpECSetPointHash, GFpECSetPointHashBackCompatible, GFpECSetPointHash_rmf, GFpECSetPointHashBackCompatible_rmf
The Galois/Counter Mode (GCM) is a mode of operation of the AES algorithm. GCM [NIST SP 800-38D] uses a variation of the Counter mode of operation for encryption. GCM assures authenticity of the confidential data (of up to about 64 GB per invocation) using a universal hash function defined over a binary finite field (the Galois field).
GCM can also provide authentication assurance for additional data (of practically unlimited length per invocation) that is not encrypted. If the GCM input contains only data that is not to be encrypted, the resulting specialization of GCM, called GMAC, is simply an authentication mode for the input data.
GCM provides stronger authentication assurance than a (non-cryptographic) checksum or error detecting code. In particular, GCM can detect both accidental modifications of the data and intentional, unauthorized modifications.
The AES-GCM function set includes incremental functions, which enable authenticated encryption/decryption of several messages using one key. The application code for conducting a typical AES-GCM authenticated encryption should follow the sequence of operations as outlined below:
- Get the size required to configure the context IppsAES_GCMState by calling the function AES_GCMGetSize.
- Call the system memory-allocation service function to allocate a buffer whose size is not less than the function AES_GCMGetSize specifies.
- Initialize the context IppsAES_GCMState*pCtx by calling the function AES_GCMInit with the allocated buffer and the respective AES key.
- Call AES_GCMStart to start authenticated encryption of the first/next message.
- Keep calling AES_GCMEncrypt until the entire message is processed.
- Request the authentication tag by calling AES_GCMGetTag.
- Proceed to the next message, if any, that is, go to step 4.
- Clean up secret data stored in the context.
- Call the system memory free service function to release the buffer allocated for the context IppsAES_GCMState, if needed.
If the size of the initial vector and/or additional authenticated data (IV and AAD parameters of the AES_GCMStart function, respectively) is large or any of these parameters is placed in a disconnected memory buffer, replace step 4 above with the following sequence:
Call AES_GCMReset to prepare the IppsAES_GCMState context for authenticated encryption of the first/new message.
Keep calling AES_GCMProcessIV for successive parts of IV until the entire IV is processed.
Keep calling AES_GCMProcessAAD for successive parts of AAD until the entire AAD is processed.
Gets the size of the IppsAES_GCMState context for use of the AES-GCM implementation with the specified characteristics.
Initializes user-supplied memory as the IppsAES_GCMState context for future use.
Starts the process of authenticated encryption/decryption for new message.
Resets the IppsAES_GCMState context for authenticated encryption/decryption of a new message.
Processes an initial vector of a given length according to the GCM specification.
Processes additional authenticated data of a given length according to the GCM specification.
Encrypts a data buffer in the GCM mode.
Decrypts a data buffer in the GCM mode.
Generates the authentication tag in the GCM mode.
Did you find the information on this page useful?