Re: krb5 mechanism OID; Was: Re: FW: memory leak in some KerberosAPIs?

[Love <lha@stacken.kth.se>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Buck Huppmann <buckh@pobox.com> writes:

>> mechanism instead of GSS_C_NO_OID in. The mechanism OID
>> for Kerberos is "1.2.840.113554.1.2.2", of course before
>> passing this argument to gss_init_sec_context() I need to
>> transfer it into a gss_OID object.
>
> can't you just pass it GSS_KRB5_MECHANISM?

The way that will work for both mit kerberos and heimdal is gss_mech_krb5

But there is alsy gss_mech_krb5_v2 that I don't know what it is, maybe
someone more clueful about the gss-krb5 mess might now.

Love

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (NetBSD)

iQIVAwUBPu6WNBZyDLTSep3UAQLwSg/+J69O+hlc7RZl6oSNAl4m+Hj70Sb07qnp
TCeDIfq+poaJRTu0oQLcEh+PJw5SuQKmjZSqdNcwzcKxUiiCgih+IzdD3tTEj8J9
a50PBXvZMcRWeiFGRz8iVnIHhXpxYB4x7jyC5zbvVAw5Zb7JgO+lBYmeTTgJ3Obk
4i6GAY3fOkLe3FEN+XqQn0i8Q3oDbiUq/wccb+AGKTdxv+6/Hxk788o2pFXwbYgP
KWUOdGAMlqS6L9UQ+0cKD2lXtju6LbSbCIHF6HeFcLOqaaKjO+PdykY1bypJUMt4
mmnZUul2ua6fQ/v52KzdP5NeCl+xSdTycKMPugfwGLdePWwOdHJ9kZMf0yYZGi8j
cGH9Bnf4Lsj4Yv5fJ94Gr0RxY4Djz8pAMLd23AzhtWJnDufWSNkKRJcCDl8+ZZ7O
DPa/W4Gl9+hF8nzaNpLdAHxyGgsmZsvV9urNy3Ymjznl+VPRTXFpSiZUCVOnwU36
wowbWqjGXQ6eN/Tn7KcHvTm0vMq/4zif5YkK4UBpTgZHa+1SKWiPKWgPESxeRUH2
lfIJbMp2iubtiAEk1hlsPFTNVWDdl0ylzz+dLYLIAUhy4MBvoM4+CzKF/NimHjz9
P0FvO4E7tDUNUwpqf1zgWQfqxyFf6eJia22qvH9yPbqqPmn84CpbGDa5NsIYPfPP
lxQEorIeSnc=
=NnDB
-----END PGP SIGNATURE-----