Quote:
Originally posted by xbill311x
Being curious, I looked up this problem online and got this fix:
su (to root)
chown root:root $KDEDIR/bin/kpp
chmod +s $KDEDIR/bin/kppp
exit
|
Yes, you were right to issue the 2nd command (bit strange it is not done by default) This will allow a normal user to be able to access configuration files of ppp, access the modem, access the Ip<->Name resolution (aka DNS)
But if it is like on my debian, kppp has these rights:
-rwsr-xr-- root dialout kppp
Which means only root and member of group dialout can execute it.
So by isuing chown root:root you have change it to:
-rwsr-xr-- root root kppp
then only root OR MEMBER OF ROOT group can execute it (x), which is too restrictive.
What you should do:
Set back the group of kppp to dialout :
Code:
su
chown root:dialout $KDEDIR/bin/kpp
addgroup <your_user> dialout (add <your_user> to group dialout)
Then from here, <your user> will be able to execute kppp, and due to the 's' bit, it will appear as root user so he will have access to the resources I've mentionned before.
In case you also want to undo the second command (kppp will no longer work for a normal user):
Code:
chmod -s $KDEDIR/bin/kpp
Quote:
So I did this. I know very little about permissions, so I wasn't aware of any repercussions.
Anyway, I can't get KPPP or my Network Device Control to open at all under KDE. When I try to open them, I get an our glass for about 15 seconds, then nothing. When I issue a command in the terminal I get:
for kppp...
[root@localhost bill]# kppp
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
and for network...
[root@localhost bill]# system-config-network
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
ERROR: Unable to initialize graphical environment. Most likely cause of failure is that the tool was not run using a graphical environment. Please either start your graphical user interface or set your DISPLAY variable.
|
Here you try to start kppp as root, which is bad!
You should always try to use the less privilege user (so that if something goes wrong, the system is secure from break due to permissions)
So, now that user is in group dialout, do it as user:
do not su,
and
$kppp
Quote:
I KNOW it has something to do with the commands I issued to get kppp working. I am still a newbie. Can someone please tell me how to reverse what I've done?
Bill
|
No its something else, it is the x window security. Root can not directly open window if you logged in as <user>. Only <user> can.
To be able to open window as root: