From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Upgrading to OpenSSL 1.1.0
Date: Wed, 29 Nov 2017 13:12:05 +0000 [thread overview]
Message-ID: <1511961125.2571.98.camel@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1655 bytes --]
Hello,
I have started working on upgrading the entire distribution to OpenSSL 1.1.0.
This is however not the easiest task since many packages are just incompatible
with the API changes of OpenSSL.
Therefore, I started this in an own branch, upgraded all sorts of packages that
won't build and patched those who could be patched. However, this is still quite
chaotic and I need some help of the maintainers of some of the packages to do
this for their own packages.
I have already dropped some packages in this process that a) were incompatible
with OpenSSL 1.1.0, b) where no patches were available and c) that are not
maintained upstream any longer. I also cherry-picked those commits to the
current next tree. If someone disagrees, please open a separate discussion.
The packages dropped are:
* Pound
* vsftp
* sslscan
Packages which currently don't build and I could not patch very easily:
* php
* asterisk
* openvpn
I suppose Erik is best to upgrade to openvpn 2.4, Dirk upgrades asterisk and I
am quite sure that there is a few people out there who have been working on php.
Please raise your hands.
I would like to have the openssl 1.1 branch ready for merge into next at the end
of December. Please make sure that any patches have been submitted until then.
Please work on top of this branch:
https://git.ipfire.org/pub/git/people/ms/ipfire-2.x.git openssl-11
https://git.ipfire.org/?p=people/ms/ipfire-2.x.git;a=shortlog;h=refs/heads/openssl-11
Please also submit improvements of other packages that we can make sure of (i.e.
better cipher suites for Apache, etc.)...
Best,
-Michael
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2017-11-29 13:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 13:12 Michael Tremer [this message]
2017-12-03 7:34 ` ummeegge
2017-12-07 11:21 ` ummeegge
2018-01-10 17:08 ` Michael Tremer
2018-01-12 11:02 ` ummeegge
2018-01-13 12:17 ` Michael Tremer
2018-01-14 10:59 ` ummeegge
2018-01-15 11:58 ` Michael Tremer
2018-01-16 11:36 ` ummeegge
2018-01-16 12:34 ` Jeffrey Walton
2018-01-16 13:02 ` Michael Tremer
2018-01-16 12:56 ` Michael Tremer
2018-01-16 14:28 ` Horace Michael
2018-01-18 10:07 ` ummeegge
2018-01-13 12:30 ` Jeffrey Walton
2018-01-15 11:59 ` Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1511961125.2571.98.camel@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox