Re: trouble with pkinit
Nico Williams <[email protected]> Fri, 17 Apr 2026 17:57:53 -0500
| Newsgroups | gmane.comp.encryption.kerberos.devel |
|---|---|
| Message-ID | <aeK68Z4E3JdNKI2K@ubby> |
On Fri, Apr 17, 2026 at 06:21:53PM -0400, Ken Hornstein via krbdev wrote: > >Any ideas? If there's a way to increase the debugging (or even > >instrument the mit code directly), I'm happy to try out any suggestions. > > Oh, I realized I should have answered this part as well: > > - The KDC logs are helpful as well (but they would have told you the > exact same thing). > > - If you set the KRB5_TRACE environment variable, a lot of debugging output > will be generated. You want that to be set to the name of an output > file; you can use /dev/stdout on most operating systems to get it > printed directly to the terminal. However, in this case it > would have also told you the same thing, just more verbosely. E.g.: Yes, this. I bet this is going to show MIT kinit doing a look-before- jumping AS-REQ w/o pre-auth, but then the Heimdal KDC will not synthesize the client principal since there will be no evidence that it might exist. Nico -- _______________________________________________ krbdev mailing list [email protected] https://mailman.mit.edu/mailman/listinfo/krbdev