Viktor writes:
> pppconfig is not mentioned in the HOWTO, so it's obviously something
> Debian-specific.
It's only available in Debian, but it isn't really Debian-specific. The
way pppconfig sets up ppp is in line with the recommendations of the
upstream ppp maintainers.
> I had to modify the cr
John Hasler wrote:
> No. Each user would have his own chatscript in /etc/chatscripts and his
> own provider file in /etc/ppp/peers, with names like
> /etc/chatscripts/viktors-ppp and /etc/ppp/peers/viktors-ppp. The
> administrator would set these up using pppconfig in the normal fashion and
> the
I wrote:
> You can, however, give each user her own chatscript and put it in her group
> so that only she and root can read it.
Viktor Rosenfeld writes:
> So each user would have its own ppp-on-script, or better yet: A global
> ppp-on-script in /usr/local/bin, which uses $HOME to access the user's
John Hasler wrote:
> You can, however, give each user her own chatscript and put it in her group
> so that only she and root can read it.
So each user would have its own ppp-on-script, or better yet: A global
ppp-on-script in /usr/local/bin, which uses $HOME to access the user's
private chatscrip
John Hasler wrote:
> You can, however, give each user her own chatscript and put it in her group
> so that only she and root can read it.
So each user would have its own ppp-on-script, or better yet: A global
ppp-on-script in /usr/local/bin, which uses $HOME to access the user's
private chatscrip
Viktor writes:
> So root can give users on the system access to a PPP connection without
> letting them know, what the user name and password for that account is.
> Makes sense, although it's not aplicable to my situation, because I can't
> use PAP/CHAP and it wouldn't work with a chat script.
You
John Hasler wrote:
> Setuid root also makes it possible for the secrets
> files to be readable only by root, and for pppd to use the serial ports
> without the user having access to them. Pppd drops root privileges as soon
> as it doesn't need them.
So root can give users on the system access to
Viktor Rosenfeld writes:
> In the standard Debian (slink) install, the groups "dip" and "dialout"
> are created. dialout is used for dialout-devices (eg /dev/ttyS*,
> /dev/isdn*, ...) while dip is used for a couple of pppd files
> (/etc/ppp/*, /usr/sbin/pppd, ...).
Under the Debian system (it is
Hi there,
I recently configured PPP and everything works well. However, I do have
a question:
In the standard Debian (slink) install, the groups "dip" and "dialout"
are created.
dialout is used for dialout-devices (eg /dev/ttyS*, /dev/isdn*, ...)
while dip is used for a couple of pppd files (/et
9 matches
Mail list logo
