Mailinglist Archive: opensuse (720 mails)

[zentara@xxxxxxxxxxxxxx (zentara)]

Ron Lavoie wrote:
> 
> ezppp worked like a charm.  I've tried 3-4 packages and had no success.  I
> *was* a bit concerned about setting:
> 
> chmod 666 /dev/ttyS0 and
> chmod 666 /etc/resolv.conf
> 
> Do either of these settings present a security risk?  I don't know what 666
> stands for, but it has "diabolical" associations for me ;^).
> 
> 
Hi, some of the experts have reservations about putting
666 on resolv.conf; however I have found that
you can get around this; at least on my system.

Ezppp must be allowed to write to resolv.conf
to enter the settings that you enter for your
ISP. But once it has done that initial configuration,
it seems to work the next time if Suseconfig
changes them back to the secure setting.

I think this will only work with a single
ISP entry in Ezppp. If you have multiple
entries, then Ezppp must be allowed to change
them.

Also, if your user is in the DIALOUT group,
you should be able to get the modem to work,
without it changed to 666. Set the modem
to /dev/modem in ezppp, and set up your
default modem with Yast.

I also have gotten better results by 
copying the ezppp binary to the home directory
of my dialout user, and giving ownership
to him. That way it is not running as root.

This works for me , but may be a flawed strategy.

zentara


--
To get out of this list, please send email to majordomo@xxxxxxxx with
this text in its body: unsubscribe suse-linux-e