[37003] in Kerberos
RE: PKINIT cert chains
daemon@ATHENA.MIT.EDU (Nordgren, Bryce L -FS)
Thu May 21 19:57:57 2015
From: "Nordgren, Bryce L -FS" <bnordgren@fs.fed.us>
To: Tom Yu <tlyu@mit.edu>
Date: Thu, 21 May 2015 23:57:27 +0000
Message-ID: <82E7C9A01FD0764CACDD35D10F5DFB6E7DE699@001FSN2MPN1-046.001f.mgd2.msft.net>
In-Reply-To: <ldvoaldy1nc.fsf@sarnath.mit.edu>
Content-Language: en-US
MIME-Version: 1.0
Cc: "kerberos@mit.edu" <kerberos@mit.edu>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: kerberos-bounces@mit.edu
> Thanks. I think you're missing the "OU=Entrust Managed Services Root CA"
> root from that set of certs.
You've prompted me to draw a picture. The collection of "intermediate" certificates is no such thing. I appear to have been given a bag of unrelated fragments of CA chains. Many apologies for lack of due diligence. PKI tools are still pretty awkward for me to use.
However, I do have the cert for the CA which signed my card (LincPass.cer), even though it's not a self-signed root CA. I specified it directly in my pkinit_anchors, but this did not resolve the issue. Does openssl (and thus MIT Kerberos) require all the certs up to a self signed root certificate, even when I want to anchor somewhat lower than that? Does this mean the anchor is really all the way at the root cert, or is it where I want it to be?
Pam_pkcs11 is authenticating with these certs for sudo, possibly because it's using Mozilla nssdb instead of openssl? Thus was I lulled into complacency.
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
