Re: OpenSSL version 3.0.0-alpha1 published

2020-04-23 Thread Sam Roberts
Fwiw, took a quick run at building and testing Node.js against the 3.x beta. It was API compatible enough to build. The DH_, ECDH_, HMAC_, etc. deprecations make sense, will look at those. My assumption is that EVP versions of these exist in openssl 1.1.1, and that if we switch our openssl 1.1.1

Re: [openssl-security] FreeBSD Port: security/openssl

2020-04-23 Thread Viktor Dukhovni
> https://bugs.php.net/bug.php?id=79513 [ This is not an OpenSSL security issue, please move this discussion to the openssl-users list. Moved "openssl-security" to Bcc. ] On Thu, Apr 23, 2020 at 03:24:15PM +0200, Jason de Cordoba wrote: > Starting php_fpm. > Segmentation fault (core dumped)

Re: questions on using ed25519

2020-04-23 Thread Viktor Dukhovni
On Thu, Apr 23, 2020 at 11:23:35AM +0200, Nicola Tuveri wrote: > > On 22/04/2020 18:12, Viktor Dukhovni wrote: > > > sadly the > > > EVP_PKEY_METHOD for ed25519 has a NULL sign() member, instead, somewhat > > > ironically, it has a digestsign() method. This is presumably to > > > distinguish betw

Re: OpenSSL version 3.0.0-alpha1 published

2020-04-23 Thread Matt Caswell
On 23/04/2020 18:01, Sam Roberts wrote: > Resending to -users. > > On Thu, Apr 23, 2020 at 9:58 AM Sam Roberts wrote: >> >> Seems to be something wrong with the way config is generating the >> version strings: >> gcc -Icrypto -I. -Iinclude -Iproviders/common/include >> -Iproviders/implementati

Re: OpenSSL version 3.0.0-alpha1 published

2020-04-23 Thread Sam Roberts
Resending to -users. On Thu, Apr 23, 2020 at 9:58 AM Sam Roberts wrote: > > Seems to be something wrong with the way config is generating the > version strings: > gcc -Icrypto -I. -Iinclude -Iproviders/common/include > -Iproviders/implementations/include -Icrypto/include -DAES_ASM > -DBSAES_ASM

Re: Have new release published in /source/old directory too?

2020-04-23 Thread Yann Ylavic
On Thu, Apr 23, 2020 at 5:12 PM Dr. Matthias St. Pierre wrote: > > > For each new release, it seems that the tarball is published in the > > "/source" directory (website) while the previous one is moved to > > "/source/old/". > > > > Would it be possible that all releases land in "/source/old", >

RE: Have new release published in /source/old directory too?

2020-04-23 Thread Dr. Matthias St. Pierre
> For each new release, it seems that the tarball is published in the > "/source" directory (website) while the previous one is moved to > "/source/old/". > > Would it be possible that all releases land in "/source/old", > including the new one when published? After all anything is more or > less

OpenSSL version 3.0.0-alpha1 published

2020-04-23 Thread OpenSSL
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 OpenSSL version 3.0 alpha 1 released OpenSSL - The Open Source toolkit for SSL/TLS https://www.openssl.org/ OpenSSL 3.0 is currently in alpha. OpenSSL 3.0 alpha 1 has now been made available.

Have new release published in /source/old directory too?

2020-04-23 Thread Yann Ylavic
Hi team, For each new release, it seems that the tarball is published in the "/source" directory (website) while the previous one is moved to "/source/old/". Would it be possible that all releases land in "/source/old", including the new one when published? After all anything is more or less old,

Re: questions on using ed25519

2020-04-23 Thread Nicola Tuveri
On Thu, 23 Apr 2020 at 11:02, Matt Caswell wrote: > > > On 22/04/2020 18:12, Viktor Dukhovni wrote: > > sadly the > > EVP_PKEY_METHOD for ed25519 has a NULL sign() member, instead, somewhat > > ironically, it has a digestsign() method. This is presumably to > > distinguish between the pure and p

Re: questions on using ed25519

2020-04-23 Thread Matt Caswell
On 22/04/2020 18:12, Viktor Dukhovni wrote: > sadly the > EVP_PKEY_METHOD for ed25519 has a NULL sign() member, instead, somewhat > ironically, it has a digestsign() method. This is presumably to > distinguish between the pure and prehash variants. Therefore, presently > pkeyutl(1) indeed appe

Re: Generating and checking SM2 signatures

2020-04-23 Thread Matt Caswell
On 23/04/2020 03:36, Billy Brumley wrote: >> I'm tasked to implement certain cryptographic functions (chiefly >> signature creation/validation) using the SM2 algorithm for a >> communication testing application. My problem is that the standard which >> I need to follow (which is, unfortunately,