Your message dated Fri, 2 Sep 2022 11:37:32 +1000
with message-id <[email protected]>
and subject line Re: Bug#527468: heimdal-kdc: Sends TGS-REP encrypted in
session key not authenticator subkey
has caused the Debian Bug report #527468,
regarding heimdal-kdc: Sends TGS-REP encrypted in session key not authenticator
subkey
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.)
--
527468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=527468
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: heimdal-kdc
Version: 1.2.dfsg.1-4
Severity: important
Tags: upstream
Hi.As discussed in bug #527353, Heimdal fails to follow the
requirement at the top of page 35 of RFC 4120 that when an
authenticator subkey is used in the TGS request, the response needs to
be encrypted in that subkey, not in the ticket session key.
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable'), (40, 'unstable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.25-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash
--- End Message ---
--- Begin Message ---
On Thu, May 07, 2009 at 03:07:26PM -0400, Sam Hartman wrote:
> Hi.As discussed in bug #527353, Heimdal fails to follow the
> requirement at the top of page 35 of RFC 4120 that when an
> authenticator subkey is used in the TGS request, the response needs to
> be encrypted in that subkey, not in the ticket session key.
This bug is so old, and upstream bug report was most likely lost (no
ticket system back then). Not sure there is anything we can do with it.
Unless we can confirm it is still and issue and create a new upstream
bug report.
Closing...
--
Brian May <[email protected]>
--- End Message ---
