> What does your implementation do differently, and which platforms does it
> work on?
It is still an early prototype, but it already allows dynamic expansion of the
secure heap (as well as shrinking) and I hope to add support for Microsoft
Windows after the POSIX / Linux implementation.
On May 5, 2019, at 7:13 PM, Dr. Pala wrote:
> small question - I was playing around with the CMS interface and I was
> wondering what is the right way to generate a signed and encrypted CMS. In
> particular, for PKCS#7, you could use the signed_and_encrypted choice... but
> in CMS, there is
The intent is that you replace the upper layer, CRYPTO_secure_x
What does your implementation do differently, and which platforms does it work
on?
Hello,
I'm trying to use EVP_aes_128_cbc_hmac_sha256() for encryption on an iOS
device with arm64 architecture. I was able to get it working with the
x86_64 architecture when running the iOS device simulator on an iMac. Is
this just not capable of working on an arm64 platform?
Looking at the