Justin Wells writes:
> A good middle ground might be to read the password from an environment
> variable.
Never ever put a password in an environment variable.
> Then I could write the script that sets the environment variable and
> calls your script
What script are you referring to? pppconfig sets up provider files and
chatscripts and edits the secrets files but does nothing at run time. pon
is just '/usr/sbin/pppd call ${1:-provider}'. The way I would support
dynamic passwords is by having pppconfig generate a script and call it from
the connect line in the provider file instead of chat.
> Of course there is a security consideration here, but on a home machine
> it's unlikely to be a big issue.
Never ever put a password in an environment variable.
--
John Hasler
[EMAIL PROTECTED] (John Hasler)
Dancing Horse Hill
Elmwood, WI
