Howdy,
I noticed that your initial report claims that you're running buster, but the
version you are comparing the buster backport to is from oldstable. This means
that rather than linking against the same version of openssl, the older version
of alpine you're running is linked against openssl1.0 which is no longer in
Debian.
If you really are on buster, can you also try alpine 2.21 from the buster repos?
One larger change with buster was that openssl changed the default minimum TLS
version from TLSv1 to TLSv1.2. For full information see
/usr/share/doc/libssl1.1/NEWS.Debian.gz
~Unit 193
Unit193 @ freenode
Unit193 @ OFTC
On Mon, 11 May 2020, Eduardo Chappa wrote:
On Mon, 11 May 2020, Βασίλειος A. Ζοῦκος wrote:
Thanks for the informative responses.
More information on the subject:
1. The variable Encryption Protocol Range appears only in alpine
ver. 2.22 with the assignment:
Encryption Protocol Range = <No Value Set: using "no_min,no_max">
Yes, and since you have not modified it, nor Debian did, that means that your
version of Alpine supports all the encryption protocols supported by the
underlying version of openssl.
Now it is the job of the Debian maintainer to investigate which protocols
were used to compile each of the versions of Openssl that were used to link
against each version of Alpine.
Let us wait for that report, and we can figure out what the next action will
be.
~Unit 193
Unit193 @ freenode
Unit193 @ OFTC
