[16328] in Kerberos-V5-bugs
Re: [krbdev.mit.edu #8814] Listing third-party KDC modules
daemon@ATHENA.MIT.EDU (行感谎薪 行靶恍把蟹芯胁 via RT)
Fri Jun 21 16:02:54 2019
Mail-followup-to: rt@krbdev.mit.edu
mail-copies-to: never
From: "行感谎薪 行靶恍把蟹芯胁 via RT" <rt-comment@KRBDEV-PROD-APP-1.mit.edu>
In-Reply-To: <rt-8814@krbdev.mit.edu>
Message-ID: <rt-8814-49496.13.1079977924639@krbdev.mit.edu>
To: "'AdminCc of krbdev.mit.edu Ticket #8814'":;
Date: Fri, 21 Jun 2019 16:02:48 -0400
MIME-Version: 1.0
Reply-To: rt-comment@KRBDEV-PROD-APP-1.mit.edu
Content-Type: multipart/mixed; boundary="===============8762282338134283833=="
Errors-To: krb5-bugs-bounces@mit.edu
--===============8762282338134283833==
Content-Type: text/plain
Hello,
I tried to get information on the Samba roadmap. In order to get access to the bugzilla, one has to write motivation,
and after my email from 10 June (attached), nothing happened.
Nevertheless, please document the known third-party modules, that work to any extend mit MIT Kerberos.
Kind regards
袛懈谢褟薪 袩邪谢邪褍蟹芯胁
On Mon, 2019-06-10 at 00:21 -0400, Greg Hudson via RT wrote:
> I am not sure what the Samba roadmap entry is referring to. The MIT
> KDC has supported within-realm S4U2Self since release 1.8. In release
> 1.17, the KDC supports cross-realm S4U2Self, if the KDB module issues
> appropriate realm referrals. This KDC work was done by a Samba
> developer, so it is my understanding that the Samba KDB module can
> issue those referrals.
>
> (There is another S4U2Self case where the client is identified by X.509
> certificate instead of principal name. This case will be supported in
> release 1.18, provided that the KDB module implements a new lookup
> function.)
--===============8762282338134283833==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
krb5-bugs mailing list
krb5-bugs@mit.edu
https://mailman.mit.edu/mailman/listinfo/krb5-bugs
--===============8762282338134283833==--
