You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TLDR:
Current implementation expects & reuses the IV with each call. I need to to work more like OpenSSL where it can mutate the IV for subsequent calls.
Details:
The current implementation of aes256GcmEncrypt & aes256GcmDecrypt are single shot functions unsuitable for implementing OpenSSL compliant encryption on successive blocks of data. They behave similar to aes_gcm_encrypt & aes_gcm_decrypt in https://github.com/openssl/openssl/blob/OpenSSL_1_1_1-stable/demos/evp/aesgcm.c
I need them to work like EVP_EncryptUpdate & EVP_DecryptUpdate in OpenSSL
Here is my production tested wrapper code:
Reference:
https://github.com/Xilinx/Vitis_Libraries/blob/main/security/L1/include/xf_security/gcm.hpp
TLDR:
Current implementation expects & reuses the IV with each call. I need to to work more like OpenSSL where it can mutate the IV for subsequent calls.
Details:
The current implementation of aes256GcmEncrypt & aes256GcmDecrypt are single shot functions unsuitable for implementing OpenSSL compliant encryption on successive blocks of data. They behave similar to aes_gcm_encrypt & aes_gcm_decrypt in https://github.com/openssl/openssl/blob/OpenSSL_1_1_1-stable/demos/evp/aesgcm.c
I need them to work like EVP_EncryptUpdate & EVP_DecryptUpdate in OpenSSL
Here is my production tested wrapper code:
The text was updated successfully, but these errors were encountered: