On Mon, 21 Aug 1995, Calvin wrote:

> On Mon, 21 Aug 1995, John Shardlow wrote:
> 
> > #!/bin/csh
> > 
> > /usr/sbin/pppd /dev/tty00 38400 defaultroute connect 'chat "" ATZ OK ATDT{1}
> >  ogin: {2} assword: {3} otocol: PPP HELLO' {4}:
> 
> This isn't the most secure way of doing it.  Suppose a user logs in and 
> does:
> 
> ps auxww | grep pppd
> 
> ?  They'll grab your password!  
> 
> The way I do it is to put all the pppd settings into its configuration 
> file and to put the connect script (chat) into a separate executable 
> script that the connect option referrs to.  Nothing vital appears under 
> ps except for time of dialing.
> 
> So what I have is:
> 
> /etc/ppp/options
> 
> which contains
> /dev/tty00 19200 crtscts modem defaultroute
> 
> and I have another file called "auth" which contains
> 
> sh -c 'chat -v "" at OK atdtNUMBER ..connection..stuff... '

I don't think that's much more secure because the password is visible on both
the shell's command line and the chat command line at the time of connect. 
What I do is use chat -f <file> so none of the chat script is ever visible on
a command line. 

Eduardo