Your message dated Thu, 07 Apr 2022 12:13:35 -0600
with message-id <[email protected]>
and subject line Overtaken by events
has caused the Debian Bug report #974531,
regarding krb5: Please include upstream fix "Unregister thread key in SPNEGO
finalization"
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
974531: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974531
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: krb5
Version: 1.17-10
Hi maintainers,
We're affected by the bug fixed in this upstream krb5 commit:
https://github.com/krb5/krb5/commit/07ff54d0
I'm mostly filing this because we want this patch in Stretch LTS, but I think
the process for that is including it in Sid and Buster first. I see that the
patch is included in the latest 1.18 upload to experimental. It was backported
to upstream's 1.17 branch here:
https://github.com/krb5/krb5/commit/994f5f51
but 1.17.2 hasn't been released yet.
I'd be happy to help by providing debdiffs or packages to sponsor or whatever
if that's useful, but I'm guessing I should just wait for 1.17.2 to be released
and reach unstable, and then file bugs for Buster and Stretch LTS?
Thanks,
--
Geoffrey Thomas
[email protected]
--- End Message ---
--- Begin Message ---
This is definitely fixed in bullseye, and at this point I'd be unlikely
to backport for buster.
--Sam
--- End Message ---
