Switch from OpenSSL to LibreSSL #203
Conversation
|
That was fast. 😁 Thanks 🍰 I'm not really sure what the LibreSSL vs OpenSSL policy is with Alpine official images. But it seems to me that if LibreSSL is the Alpine default then that is what we should use, especially if other packages are installed that depend on LibreSSL and that then conflicts with OpenSSL. But I'm sure @tianon will have an answer for us as always :) |
|
In past conversions (when Alpine 3.5 switched from OpenSSL-by-default to LibreSSL-by-default) we only switched if packages we installed caused conflicts at build-time or run-time, but if this compiles and works, I'm +1 (especially since Alpine 3.5+ does use LibreSSL-by-default, so it makes sense for us to follow suit even/especially to ensure that compatibility works properly and packages can install). |
|
LGTM, in other words 👍 |
- `bash`: update git.savannah.gnu.org URLs - `gcc`: update git.savannah.gnu.org URLs - `httpd`: update git.savannah.gnu.org URLs - `memcached`: 1.4.37 - `nextcloud`: add 12.0 (nextcloud/docker#85) - `postgres`: update git.savannah.gnu.org URLs - `python`: add Alpine 3.6 variants (docker-library/python#201, docker-library/python#203) - `rabbitmq`: fix "unbound variable" error (docker-library/rabbitmq#161)
Switch from OpenSSL to LibreSSL
This was suggested by @JayH5 on PR #201 after it was merged.