Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 4 Aug 2008 14:25:22 +0100
From:      Doug Rabson <dfr@rabson.org>
To:        Rick Macklem <rmacklem@uoguelph.ca>
Cc:        freebsd-fs@freebsd.org, =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= <des@des.no>
Subject:   Re: Which GSSAPI library does FreeBSD use?
Message-ID:  <326AF658-D96D-4410-9E32-0001FF8264AA@rabson.org>
In-Reply-To: <Pine.GSO.4.63.0807291020260.12515@muncher.cs.uoguelph.ca>
References:  <Pine.GSO.4.63.0807161832470.5025@muncher.cs.uoguelph.ca> <86myk06e18.fsf@ds4.des.no> <Pine.GSO.4.63.0807291020260.12515@muncher.cs.uoguelph.ca>

next in thread | previous in thread | raw e-mail | index | archive | help

On 29 Jul 2008, at 15:27, Rick Macklem wrote:

>
>
> On Tue, 29 Jul 2008, Dag-Erling Sm=F8rgrav wrote:
>
>> Rick Macklem <rmacklem@uoguelph.ca> writes:
>>> Hope this isn't too simplistic for this list, but I need to know =20
>>> which
>>> GSSAPI library sources are being used. They don't appear to be =20
>>> either
>>> vanilla MIT nor Heimdal.
>>
>> Homegrown (by Doug Rabson, dfr@) with portions borrowed from Heimdal.
>>
> Ok, thanks. I was able to work around my problem by statically linking
> my gssd against libraries built from vanilla Heimdal sources. It looks
> like it inherited the heimdal-0.6 bug, which ignores the lack of the
> GSS_C_SEQUENCE_FLAG and checks it even if it wasn't specified. This
> breaks the client side of RPCSEC_GSS, since somewhat out-of-order
> Sun RPCs, is normal. (RPCSEC_GSS uses a window of recent seq#s to
> protect against replay attempts.)
>
> Should I email Doug or submit a bug report, to see if someone is =20
> willing
> to work on fixing this?

Try using current - I updated heimdal to 1.1 in current.

The GSS-API implementation in 7.x and current is a plugin system which =20=

heimdal's krb5 code plugs into as a GSS-API mechanism provider. With =20
heimdal 1.1, it also supports spnego and ntlm as plugins.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?326AF658-D96D-4410-9E32-0001FF8264AA>