Bryan Kadzban <[EMAIL PROTECTED]> writes:

> After some looking at the upstream bug database, this appears to be the
> same as their bug #5802:
>
> http://krbdev.mit.edu/rt/Ticket/Display.html?id=5802
>
> and that page says the bug was fixed in 1.6.3.  And indeed, the source
> for 1.6.3 (from upstream) handles the flags differently: it passes the
> address of a local variable to the mechanism-specific accept_sec_context
> function, then copies it back to the address that the user passed in if
> non-NULL.  It also uses the local variable in the bitfield comparison.
>
> So upgrading to upstream version 1.6.3 (or adopting this part of the
> code, at least) should fix this as well.

Oh, in that case, it should already be fixed; 1.6.3 is already in Debian
unstable.

-- 
Russ Allbery ([EMAIL PROTECTED])               <http://www.eyrie.org/~eagle/>



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to