Derrick E Barbour wrote:
>
> FWIW,
>
> I'm currently using the 'unpatched' version of PPP 2.3.5 on RHL with Kernel
> 2.0.36-3, and so far it is working fine.
>
> I have seen numerous references to a "small bug in PPPD 2.3.5, however I have
> not encountered any problems myself.
>
> Would you mind bringing me 'up to speed' on the problem with 2.3.5?
>
There is probably more than one. It is, after all, software. The one I
found is in upap.c. Actually it's not quite fair to call it a bug, but
it caused me months of frustration until I found it. It turns out that
whatever my ISP uses for PPP sends the Authenticate Acknowledge without
the final message length byte of 0 (they don't include the optional
message at the end, so it should be 0). According to the RFC, this byte
is required and the baseline pppd 2.3.5 aborts the entire authentication
when it is not present. The fix was to make it slightly more permissive
and accept the fact that the authentication has succeeded. Since it is
known unambiguously at this point that the peer has authenticated me,
there is no security issue. I believe that James Carlson has called this
to the attention of the maintainers, and so I expect that it will be
fixed in the next version.
-- David
-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to [EMAIL PROTECTED]
