Dropping Pound | was: Upgrading to OpenSSL 1.1.0

Hi,

I don't understand why the pound addon was dropped without any discussion. The debian team solved the build problem with openssl-1.1.0

https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=828511;filename=poun...

Are there any more reasons dropping pound?

I'm really pissed off, because I'm the author of the addon and it's the most important addon in my installation environment.

- Dirk

Michael Tremer hat am 29. November 2017 um 14:12 geschrieben:

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