This PR ensures AES-GCM seal and open empty inputs are initialized.
Uninitialized inputs did not trigger any test failure until now because most of OpenSSL compilations seem to handle them correctly.
Strangely, the OpenSSL binary packed in mcr.microsoft.com/dotnet-buildtools/prereqs:ubuntu-18.04-20211022152710-047508b can't handle them, even though it uses OpenSSL 1.1.1, which causes this failure when running Go crypto tests.
This PR ensures AES-GCM seal and open empty inputs are initialized.
Uninitialized inputs did not trigger any test failure until now because most of OpenSSL compilations seem to handle them correctly.
Strangely, the OpenSSL binary packed in
mcr.microsoft.com/dotnet-buildtools/prereqs:ubuntu-18.04-20211022152710-047508bcan't handle them, even though it uses OpenSSL 1.1.1, which causes this failure when running Go crypto tests.I found this now thanks to https://github.com/microsoft/go/pull/655, which forces the OpenSSL backend even if FIPS is not enabled.