Re: Custom secure heap implementation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Tobias Nießen <tniessen@xxxxxxx>, "openssl-users@xxxxxxxxxxx" <openssl-users@xxxxxxxxxxx>
Subject: Re: Custom secure heap implementation
From: "Salz, Rich via openssl-users" <openssl-users@xxxxxxxxxxx>
Date: Mon, 6 May 2019 14:52:05 +0000
Accept-language: en-US
In-reply-to: <855e685d-8470-3a02-3fb1-e2d5ba7c6ce5@tnie.de>
References: <855e685d-8470-3a02-3fb1-e2d5ba7c6ce5@tnie.de>
Reply-to: "Salz, Rich" <rsalz@xxxxxxxxxx>
User-agent: Microsoft-MacOutlook/10.19.0.190502

The intent is that you replace the upper layer, CRYPTO_secure_xxxxx

What does your implementation do differently, and which platforms does it work on?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Follow-Ups:
- Re: Custom secure heap implementation
  - From: Tobias Nießen

References:
- Custom secure heap implementation
  - From: Tobias Nießen

Prev by Date: Re: Custom secure heap implementation
Next by Date: EVP_aes_128_cbc_hmac_sha256() not working on arm64 architecture
Previous by thread: Re: Custom secure heap implementation
Next by thread: Re: Custom secure heap implementation
Index(es):
- Date
- Thread

[Index of Archives] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Security] [Bugtraq] [Linux] [Linux OMAP] [Linux MIPS] [ECOS] [Asterisk Internet PBX] [Linux API]

Powered by Linux