On Thu, Apr 04, 2019 at 01:26:01PM +0200, Enrico Scholz via openssl-users wrote:
> What is the recommended way to create an X509 REQ with OpenSSL 1.1 when
> all the crypto has been done in the outside and I need only the ASN.1
> structure?
See also the related:
Dear Users,
I have released version 5.51 of stunnel.
Version 5.51, 2019.04.04, urgency: MEDIUM
* New features
- Hexadecimal PSK keys are automatically converted to binary.
- Session ticket support (requires OpenSSL 1.1.1 or later).
"connect" address persistence is currently unsupported
On 4/4/19 3:32 AM, ramakrushna mishra wrote:
> Hi,
>
> Could anyone please help me get the following information.
>
> -- How to verify that the openssl is using the assembly code ( when asm
> is enabled) instead of the c code for the algorithms ?
> -- I m observing a small degradation (2 %
On Wed, Apr 03, 2019 at 06:09:59PM -0400, Viktor Dukhovni wrote:
> > Ah, right. Unlike GnuTLS, the STEK is tied to the SSL_CTX and,
> > as you say, Exim initialises that fresh per connection.
> > Rearchitecting that is more effort than it's worth spending
> > on TLS 1.2, I think.
>
> Well, the
Hi
is there any standard/rfc for EVP_SealInit .
Regards
Manish
Hello,
I want to use OpenSSL to create an X509 request where the signature has
been calculated by an external device (ATMEL ATECC508A). With OpenSSL
1.0 I used
X509_REQ *req;
req = X509_REQ_new();
algor = X509_ALGOR_new();
algor->algorithm =
Hi,
Could anyone please help me get the following information.
-- How to verify that the openssl is using the assembly code ( when asm is
enabled) instead of the c code for the algorithms ?
-- I m observing a small degradation (2 % for 16 byte size) for des-ede3 on
openssl1.1.1 for Solaris.
