Date: Tue, 29 Jul 2008 10:27:58 -0400 (EDT) From: Rick Macklem <rmacklem@uoguelph.ca> To: =?utf-8?B?RGFnLUVybGluZyBTbcO4cmdyYXY=?= <des@des.no> Cc: freebsd-fs@freebsd.org Subject: Re: Which GSSAPI library does FreeBSD use? Message-ID: <Pine.GSO.4.63.0807291020260.12515@muncher.cs.uoguelph.ca> In-Reply-To: <86myk06e18.fsf@ds4.des.no> References: <Pine.GSO.4.63.0807161832470.5025@muncher.cs.uoguelph.ca> <86myk06e18.fsf@ds4.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. ---559023410-851401618-1217341678=:12515 Content-Type: TEXT/PLAIN; charset=utf-8; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Tue, 29 Jul 2008, Dag-Erling Sm=C3=B8rgrav wrote: > Rick Macklem <rmacklem@uoguelph.ca> writes: >> Hope this isn't too simplistic for this list, but I need to know which >> GSSAPI library sources are being used. They don't appear to be 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 willing to work on fixing this? Thanks again, rick ---559023410-851401618-1217341678=:12515--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.63.0807291020260.12515>