[23225] in Kerberos
Re: Krb5 API vs. GSSAPI
daemon@ATHENA.MIT.EDU (Kirill Mendelev)
Wed Jan 19 13:19:18 2005
Date: Wed, 19 Jan 2005 11:54:47 +0200
From: Kirill Mendelev <kirill.mendelev@gmail.com>
Message-ID: <41ee2f16$1@news.012.net.il>
To: kerberos@mit.edu
Errors-To: kerberos-bounces@mit.edu
Hi,
Speaking of mechanisms. I may sound silly, but I'm only beginning to dig
into all this Kerberos/GSSAPI/SPNEGO/SPNEGO via HTTP stuff (lots of
reading done, tons of material ahead).
Still, I've built a couple of small programs, which use GSSAPI as
provided by MIT distribution, and it seems that the mechanisms supported
by default do not include SPNEGO 1.3.6.1.5.5.2. I'm using the
gss_indicate_mechs to obtain available mechanisms, and I can't find it
inside of the set returned.
Do I miss something real important, or should I just go ahead and
implement the SPNEGO mech by myself?
Kirill
Luke Howard wrote:
>>Is that so? I've only ever seen Kerberos being carried out over GSSAPI.
>>What others are there?
>
>
> Here is a list that Martin Rex of SAP posted to the ietf-kitten mailing
> list (to which I would add SPNEGO and NTLM):
>
> ietf mechanism: Company (Country)
>
> Kerberos 5 MIT, CyberSafe, CA/Platinum, Microsoft, heimdal
> SPKM Entrust (CA), Shym (US), Baltimore (US)
>
> proprietary mechanisms:
>
> AM-DCE Bull (FR)
> (propr.) Sagem (FR)
> sdti,rsakeon,trustnet TFS-Tech (SE) former RSA/SDTI
> safelayer Safelayer (SP)
> NEC Secureware NEC (JP)
> itsec UBS/ITsec (CH)
> Adnovum GSSv2 UBS/Adnovum (CH)
> ISign/secui Penta Security Systems (South Korea)
> Sisler Siemens India (India)
> cpro Mecomp (RU)
> lissi Lissi (RU)
> kobil Kobil GmbH (DE)
> T-Secure secunet/Telekom (DE)
>
> -- Luke
>
> --
> ________________________________________________
> Kerberos mailing list Kerberos@mit.edu
> https://mailman.mit.edu/mailman/listinfo/kerberos
>
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
