portmaster strange implementation of LCP (pap/chap) (fwd)

MegaZone (megazone@livingston.com)
Tue, 15 Apr 1997 20:16:13 -0700 (PDT)

Once upon a time Alexei Krivenkov shaped the electrons to say...
>-------
>Received LCP_CONFIGURE_REQUEST on port S21 of 4 bytes containing:
>01 01 00 08 03 04 c0 23
>Fixed #bytes to match #found...
>Recvd from port S21: 10 bytes LCP Request-1
> Authentication-Protocol = PAP

They dial into us and want US to auth to THEM with PAP.

No way.

>Sending LCP_CONFIGURE_NAK to port S21 of 9 bytes containing:
>03 01 00 09 03 05 c2 23 05
>Sent to port S21: 11 bytes LCP Refuse-1
> Authentication-Protocol = CHAP 0x05
>
>/* It's really weird Portmaster send this. It looks like it refuses
> CHAP which has not been offered. */

No, we are saying "Forget it, I will not PAP to you. But I can do CHAP
if you want."

>Sending LCP_CONFIGURE_REQUEST to port S21 of 14 bytes containing:
>01 01 00 0e 05 06 a5 bd ea 8d 03 04 c0 23
>Sent to port S21: 16 bytes LCP Request-1
> Magic-Number = 0xa5bdea8d
> Authentication-Protocol = PAP

And they insist on PAP.

We will NEVER PAP to someone dialing into us - we're not stupid enough
to send an unknown entity a PASSWORD!

>It seems like portmaster is doing something wrong.

No, we're acting perfectly normal.

-MZ

--
Livingston Enterprises - Chair, Department of Interstitial Affairs
Phone: 800-458-9966 510-426-0770 FAX: 510-426-8951 megazone@livingston.com
For support requests: support@livingston.com  <http://www.livingston.com/> 
Snail mail: 4464 Willow Road, Pleasanton, CA 94588