Hi, Can anyone cast any light on the following please ? I have been using ppp on this 7.0 system since last November without changing any permissions in /dev or /sbin/pppd. I just used YAST to setup the modem to be accessed by my user name. Over the past couple of days it is fair to say that I have done some heavy updating - changing to xfree86 4.1 and installing the new vanilla kernel 2.4.8. So far as I know, however, I have not touched anything that affects the modem or ppp - and the kernel upgrade was just the latest in a long line. After I had finished the kernel work this morning I was able to log on to my ISP as usual - no problems (using wvdial as always). I then reinstalled vmware and alsa (as I have on at least 8 previous occasions). I tried to log to the ISP again shortly afterwards (there was no intermediate reboot), and got "permission denied" when I tried to access /dev/modem. /dev/modem is, of course, just a link to /dev/ttyS0. After much fiddling around I found that the only way to cure the permission problem was to change the permissions on /dev/ttyS0 to make it world-writeable. After that I got access to the modem, but ppp immediately died with the message "must be root to run /usr/sbin/pppd, since it is not setuid-root". So I set pppd suid-root and now I can connect as before. As I said, I have *never* previously modified /dev/ttyS0 or /usr/sbin/pppd. I even tried going back to my backup kernel 2.4.7, but it made no difference. Have I accidentally activated some security script ? Any thoughts will be gratefully received. Regards, Geoff _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
On Sat, 11 Aug 2001 18:09:21 +0100 quintaq@yahoo.co.uk wrote:
Hi,
Can anyone cast any light on the following please ? ... etc
Replying (in part), to my own post, I found an old article on the support database which suggests that (for reasons the SuSE people do not fully understand), wvdial can sometimes leave /dev/ttyS0 locked. They don't say anything about the suid problem with pppd though - so I would still appreciate any thoughts / experiences you all may have. Regards, Geoff _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
quintaq@yahoo.co.uk wrote:
On Sat, 11 Aug 2001 18:09:21 +0100 quintaq@yahoo.co.uk wrote:
Hi,
Can anyone cast any light on the following please ? ... etc
Replying (in part), to my own post, I found an old article on the support database which suggests that (for reasons the SuSE people do not fully understand), wvdial can sometimes leave /dev/ttyS0 locked. They don't say anything about the suid problem with pppd though - so I would still appreciate any thoughts / experiences you all may have.
Regards,
Geoff
Hi Geoff, one thought is that you ran SuSEConfig by working on your system. SuSEConfig resets permissions as "granted" in /etc/permissions.[local|secure|...]. If you changed permissions by hand long time back, that might be the problem. (Or, I am completely wrong. Some memory tells me that (re)setting permissions is also called by cron-dayly). It's worth to be looked at anyway. Juergen -- =========================================== __ _ Juergen Braukmann juergen.braukmann@gmx.de| -o)/ / (_)__ __ ____ __ Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu | /\\ /__/ / _ \/ // /\ \/ / ===========================================_\_v __/_/_//_/\_,_/ /_/\_\
On Sun, 12 Aug 2001 09:33:37 +0200
Juergen Braukmann
one thought is that you ran SuSEConfig by working on your system. SuSEConfig resets permissions as "granted" in /etc/permissions.[local|secure|...]. If you changed permissions by hand long time back, that might be the problem.
Hi Juergen, Thanks for that idea. I don't recall ever hand editing any permissions files, but after the permission denied problem with /dev/modem arose I did go back into YAST to check that my user name still had permission to access the modem. Maybe I caused some problems along the way.
(Or, I am completely wrong. Some memory tells me that (re)setting permissions is also called by cron-dayly). It's worth to be looked at anyway.
It had occurred to me that some cron process might be the culprit - because after I sent my first post yesterday the /dev/modem permission denied problem actually recurred. I checked, however, and cannot see anything in my cron setup that would cause it. Regards, Geoff _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
quintaq@yahoo.co.uk wrote:
On Sun, 12 Aug 2001 09:33:37 +0200 Juergen Braukmann
wrote: one thought is that you ran SuSEConfig by working on your system. SuSEConfig resets permissions as "granted" in /etc/permissions.[local|secure|...]. If you changed permissions by hand long time back, that might be the problem.
Hi Juergen,
Thanks for that idea. I don't recall ever hand editing any permissions files, but after the permission denied problem with /dev/modem arose I did go back into YAST to check that my user name still had permission to access the modem. Maybe I caused some problems along the way.
(Or, I am completely wrong. Some memory tells me that (re)setting permissions is also called by cron-dayly). It's worth to be looked at anyway.
It had occurred to me that some cron process might be the culprit - because after I sent my first post yesterday the /dev/modem permission denied problem actually recurred. I checked, however, and cannot see anything in my cron setup that would cause it.
Regards,
Geoff
Hi Geoff, it would be hard to find, something called somwhere. I am currently fiddling with a script that calles awk from a pipe no clue what it does... for your problem, /dev/modem is a link to the real modem device (the port the modem is connected to, like /dev/ttyS0). The permissions must be correct for that device. If permissions changed, set it in /etc/permissions.local like it's done in the other permission files. There were also issues to set the dialout user into group dialout, to enable use of the dialer. I do not remember that stuff, I'm on ISDN and refused to reboot for 153 days now to prevent trouble. ;-) Juergen -- =========================================== __ _ Juergen Braukmann juergen.braukmann@gmx.de| -o)/ / (_)__ __ ____ __ Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu | /\\ /__/ / _ \/ // /\ \/ / ===========================================_\_v __/_/_//_/\_,_/ /_/\_\
On Sun, 12 Aug 2001 16:11:13 +0200
Juergen Braukmann
quintaq@yahoo.co.uk wrote: Hi Geoff,
it would be hard to find, something called somwhere. True.
for your problem, /dev/modem is a link to the real modem device (the port the modem is connected to, like /dev/ttyS0). The permissions must be correct for that device. Yes, that is how I eventually fixed the permission denied problem.
If permissions changed, set it in /etc/permissions.local like it's done in the other permission files. There were also issues to set the dialout user into group dialout, to enable use of the dialer. I do not remember that stuff, I'm on ISDN and refused to reboot for 153 days now to prevent trouble. ;-)
I have logged on many times since yesterday. So far the problem has not recurred and so I am going to wait and see what happens before I change anything else. I will, however, do as you suggest if I find myself having to deal with the problem again. Thanks again, Geoff _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
participants (2)
-
Juergen Braukmann
-
quintaq@yahoo.co.uk