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
By trying to encrypt/decrypt data using the OpenSSL API like we do with the TPM2 OpenSSL provider, which is making the encryption that uses public key by the default OpenSSL provider and the decryption by the Trust M one.
It did not work and from times to time OpenSSL detected a defect in the exported public key. By introducing several printf() we could see that the key "stream" order was reversed in the export. It appears that some OpenSSL API do endianness wizardry which OSSL_PARAM_construct_BN() does not. We implemented the following to make things work:
Hi,
By trying to encrypt/decrypt data using the OpenSSL API like we do with the TPM2 OpenSSL provider, which is making the encryption that uses public key by the default OpenSSL provider and the decryption by the Trust M one.
It did not work and from times to time OpenSSL detected a defect in the exported public key. By introducing several printf() we could see that the key "stream" order was reversed in the export. It appears that some OpenSSL API do endianness wizardry which
OSSL_PARAM_construct_BN()
does not. We implemented the following to make things work:Notes:
The text was updated successfully, but these errors were encountered: