-
-
Notifications
You must be signed in to change notification settings - Fork 555
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade: OpenSSL 3.0.0.beta2 #32311
Comments
Commit: |
Author: Samuel Lelièvre |
comment:1
Setting to critical as this takes this security New commits:
|
Branch: u/slelievre/32311 |
comment:2
Please review. |
This comment has been minimized.
This comment has been minimized.
Changed branch from u/slelievre/32311 to public/32311 |
comment:3
Rebased on Sage 9.4.rc0. New commits:
|
comment:4
Launched github-actions by pushing a tag to my fork on github: |
comment:5
LGTM |
Reviewer: Matthias Koeppe |
comment:6
Thanks! |
Changed branch from public/32311 to |
Ticket #29555 made openssl a standard package and
upgraded to OpenSSL 3.0.0-alpha11, still in alpha
stage but now under Apache license while OpenSSL
1.x versions were not GPL compatible.
Since #30557 added an spkg-configure.m4 file
for openssl, that prerelease version only gets
installed if no system version is detected.
Ticket #31439 upgraded to OpenSSL 3.0.0-alpha12.
OpenSSL 3.0.0 has now entered beta stage, and the
release announcement for OpenSSL 3.0.0-beta1 says
this should be considered a release candidate,
and invites to test widely.
OpenSSL 3.0.0-beta2 was released 2021-07-29.
We upgrade to that version.
CC: @dimpase @mkoeppe @slel @sagetrac-tmonteil @vbraun
Component: packages: standard
Keywords: upgrade, openssl
Author: Samuel Lelièvre
Branch/Commit:
c374ffc
Reviewer: Matthias Koeppe
Issue created by migration from https://trac.sagemath.org/ticket/32311
The text was updated successfully, but these errors were encountered: