Quoting Paul Mackerras <[EMAIL PROTECTED]>:

> Well, using the `auth' option means that you want the peer (your ISP)
> to authenticate itself to you.  In that case pppd checks to see if
> there is any way that the peer could authenticate itself, before it
> goes and wastes your money by dialling the peer.

Well I try to fiddle around making my own scripts but it
doesn't hurt to look at others and this is a comment to to
"auth" option from a sample (usernet?) options file - and
this option is enabled in there by default:

# Require the peer to authenticate itself before allowing
# network packets to be sent or received. Please do not 
# disable this setting. It is expected to be standard in
# future releases of pppd. Use the call option (see
# manpage) to disable authentication for specific peers.

So judging from this I thought it would be a wise thing to
have ?


> > Same thing happens if I use "noauth" or "require-pap" etc.    
> 
> It's very strange if you really do still get the message when you use
> the `noauth' option, since it explicitly says that the peer doesn't
> have to authenticate itself and can use any IP address it likes.  (I
> try to discourage its use since it can open up vulnerabilities if it
> isn't used carefully.)


Sorry for the inaccuracy, it was my mistake - I just tried to put it 
in again and no problem.



Morten



-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to [EMAIL PROTECTED]

Reply via email to