On Saturday 27 Sep 2003 12:25 pm, robin wrote:Sorry, I probably phrased the question badly - the problem is that KDE is not storing the password I use to connect to a remote server; it's nothing to do with permissions on this machine.
What I'd like to do is a little less drastic than previous posts. I use korganizer to access a calendar stored on a remote server, but this means that whenever I login, KDE presents me with a password request. The KDE Control Centre (or Konqueror configuration) insists that I set a timeout on stored passwords, which is silly considering that I have the same password stored permanently by other apps (e.g. ncftp, wvdial). I know this is a security feature to stop users doing silly things, but there should also be a workaround for people who are willing to take risks and sensible enough to take precautions (this is, after all, a one-user workstation, not a server controlling a nuclear power station). So is there a workaround?
Sir Robin
Thats what sudo is for. With sudo you can allow a specific user or group of users to execute commands they would not normally have permission for, either without a password, or giving their own user password.
All you need to do is edit /etc/sudoers using the special editor visudo (as root)
man sudoers describes the syntax (which is pretty tricky)
Then you can call up the command with
'sudo command parameters'
To save having to type sudo every time you can create an alias in your ~/.bash_profile
For example
command=sudo command
Sir Robin
-- "I can say: 'Thank these bees for their honey as though they were kind people who have prepared it for you'; that is intelligible and describes how I should like you to conduct yourself. But I cannot say: 'Thank them because, look, how kind they are!'--since the next moment they may sting you. - Wittgenstein
Robin Turner IDMYO Bilkent Univeritesi Ankara 06533 Turkey
www.bilkent.edu.tr/~robin
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
