Topic: AES_GCM additional data must not be NULL?
Hello,
I migrated my current project to the latest stable version 3.11.0 and now some of my AES_GCM tests are failing. I found that the cause for this are the new varaible checks in wc_AesGcmDecrypt
if (aes == NULL || out == NULL || in == NULL || sz == 0 || iv == NULL ||
authTag == NULL || authIn == NULL || authTagSz > AES_BLOCK_SIZE) {
return BAD_FUNC_ARG;
}
With these checks, additional data (authIn) is not permitted to be NULL anymore. I know that it can be avoided by passing an empty dummy instead, but shouldn't it be permitted to call the function without any additional data to authenticate?
Best Regards
telina