On 1/26/22 11:56, Sebastian Andrzej Siewior wrote:
On 2022-01-25 22:10:00 [-0500], Anders Kaseorg wrote:
The fix is trivial, swapping two lines of assembly. I’ve attached it as a
debdiff, and tested it in a Debian 10 container on an M1 MacBook. Can it
be considered for oldstable?
Yes. My plan is to get m into o-stable and oo-stable. The o-stable
update is tracked in #1003484.
Any progress on this fix, via either my targeted debdiff or a full
update to ≥ 1.1.1i?
I see that https://bugs.debian.org/1003484 is for 1.1.1k → 1.1.1m in
bullseye (stable); that’s not directly relevant here as neither version
is affected. There’s https://bugs.debian.org/959469 for 1.1.1d → 1.1.1k
in buster (oldstable), which would resolve this, but it’s seen no
activity in a year. Perhaps the intention is to wait for 1.1.1m in
stable before updating the oldstable backport to 1.1.1m as well? I’m
just concerned that if we keep blocking this on newer and newer openssl
versions, it will be delayed for infinite time…
Anders
