Alpha2 blog post
Nicola has kindly written another blog post for us - this time on the alpha 2 release. I've just published it, and you can read it here: https://www.openssl.org/blog/blog/2020/05/16/OpenSSL3.0Alpha2/ Matt
OpenSSL version 3.0.0-alpha2 published
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 OpenSSL version 3.0 alpha 2 released OpenSSL - The Open Source toolkit for SSL/TLS https://www.openssl.org/ OpenSSL 3.0 is currently in alpha. OpenSSL 3.0 alpha 2 has now been made available. Note: This OpenSSL pre-release has been provided for testing ONLY. It should NOT be used for security critical purposes. Specific notes on upgrading to OpenSSL 3.0 from previous versions, as well as known issues are available on the OpenSSL Wiki, here: https://wiki.openssl.org/index.php/OpenSSL_3.0 The alpha release is available for download via HTTPS and FTP from the following master locations (you can find the various FTP mirrors under https://www.openssl.org/source/mirror.html): * https://www.openssl.org/source/ * ftp://ftp.openssl.org/source/ The distribution file name is: o openssl-3.0.0-alpha2.tar.gz Size: 9601205 SHA1 checksum: 9224a8957232db61b1e9cf1a80b3a19165f47236 SHA256 checksum: 9077d53d889f9708c261ee8a698df10575e2fd191de6924d89136b97dc8bc0c0 The checksums were calculated using the following commands: openssl sha1 openssl-3.0.0-alpha2.tar.gz openssl sha256 openssl-3.0.0-alpha2.tar.gz Please download and check this alpha release as soon as possible. To report a bug, open an issue on GitHub: https://github.com/openssl/openssl/issues Please check the release notes and mailing lists to avoid duplicate reports of known issues. (Of course, the source is also available on GitHub.) Yours, The OpenSSL Project Team. -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEhlersmDwVrHlGQg52cTSbQ5gRJEFAl6+miwACgkQ2cTSbQ5g RJFqZggAhQGdzxbmbIa6aKeaX3sNpIYEpnu1W3htP/d2tMuqUlv31qG+IKZEnqHy kk/rhpHj9XU08MurpZ9caALayA3WNSpZXCwzpG85pgIm/KlwM2YN2CdmFCuh/G4K sMyU8UgSEcuEfF7BpYNgmfifYxDdRJjlrnrHwBPpFRJ0MdvS+8GN0a9n9b3o2eOm u2Dnub85W7NUH4St4YdKqDfxUF3rIPg+hvgOllb8JjZAqbrnCkeFek2SL9fVYJBM ORy3QODr2ahOo5sOYi61y7qe/MpcLdyjr5btm0L/xggWjBJ+EOo7m1iG2eQdzE88 AvcvALAtph/vmvfU3uPGWL7ms3z9Jg== =ixcT -END PGP SIGNATURE-
Re: Alpha2
On Wed, 13 May 2020 18:00:35 +0200, Matt Caswell wrote: > > On 08/05/2020 09:55, Matt Caswell wrote: > > Various OpenSSL 3.0 developers met (virtually) on Tuesday to discuss > > current progress. It was proposed that we should do the Alpha 2 release > > next week (on Thursday 14th May). Unless I hear objections otherwise, I > > plan to go with that. > > I'm currently thinking that we're not quite ready for alpha2 and I would > like to push it by a day. Any objections? Not from me... among others, I want to see #11758 in there... Cheers, Richard -- Richard Levitte levi...@openssl.org OpenSSL Project http://www.openssl.org/~levitte/
Re: Alpha2
We're ok with regularly scheduled alpha releases. -Original Message- From: openssl-project on behalf of "Salz, Rich" Date: Wednesday, May 13, 2020 at 12:03 PM To: Matt Caswell , "openssl-project@openssl.org" Subject: Re: Alpha2 NetApp Security WARNING: This is an external email. Do not click links or open attachments unless you recognize the sender and know the content is safe. >releases - we would simply do them every 3 weeks or so. I'd like to hear opinions on that proposal too. I am in favor of this, but you HAVE to keep the cadence regular: no slipping.
Re: Alpha2
>releases - we would simply do them every 3 weeks or so. I'd like to hear opinions on that proposal too. I am in favor of this, but you HAVE to keep the cadence regular: no slipping.
Re: Alpha2
On 08/05/2020 09:55, Matt Caswell wrote: > Various OpenSSL 3.0 developers met (virtually) on Tuesday to discuss > current progress. It was proposed that we should do the Alpha 2 release > next week (on Thursday 14th May). Unless I hear objections otherwise, I > plan to go with that. I'm currently thinking that we're not quite ready for alpha2 and I would like to push it by a day. Any objections? At the dev meeting on Tuesday we discussed a slight change of approach with the alpha releases, i.e. rather than have a set number of alpha releases - we would simply do them every 3 weeks or so. I'd like to hear opinions on that proposal too. Matt
Re: Alpha2
You might want to consider reviewing #11630, an reminding me what else needs to get fixed in there. On Fri, 08 May 2020 10:55:19 +0200, Matt Caswell wrote: > > Various OpenSSL 3.0 developers met (virtually) on Tuesday to discuss > current progress. It was proposed that we should do the Alpha 2 release > next week (on Thursday 14th May). Unless I hear objections otherwise, I > plan to go with that. > > Matt > -- Richard Levitte levi...@openssl.org OpenSSL Project http://www.openssl.org/~levitte/
Re: Alpha2
Dear Matt, The workaround for the 11763 is implemented, 11764 seems to be fixed now, so no objections from my side. Happy weekend! On Fri, May 8, 2020 at 11:58 AM Dmitry Belyavsky wrote: > Dear Matt, > > I kindly ask not to make release until issues raised in #11763 and #11764 > are fixed. > > On Fri, May 8, 2020 at 11:55 AM Matt Caswell wrote: > >> Various OpenSSL 3.0 developers met (virtually) on Tuesday to discuss >> current progress. It was proposed that we should do the Alpha 2 release >> next week (on Thursday 14th May). Unless I hear objections otherwise, I >> plan to go with that. >> >> Matt >> > > > -- > SY, Dmitry Belyavsky > -- SY, Dmitry Belyavsky
Re: Alpha2
Dear Matt, I kindly ask not to make release until issues raised in #11763 and #11764 are fixed. On Fri, May 8, 2020 at 11:55 AM Matt Caswell wrote: > Various OpenSSL 3.0 developers met (virtually) on Tuesday to discuss > current progress. It was proposed that we should do the Alpha 2 release > next week (on Thursday 14th May). Unless I hear objections otherwise, I > plan to go with that. > > Matt > -- SY, Dmitry Belyavsky
Alpha2
Various OpenSSL 3.0 developers met (virtually) on Tuesday to discuss current progress. It was proposed that we should do the Alpha 2 release next week (on Thursday 14th May). Unless I hear objections otherwise, I plan to go with that. Matt
