A little background: I'm adminning a KUbuntu box which runs our in-house server software. This software runs as a non-root service account (actually, two different ones) for security. Mostly it's administered remotely, but occasionally I have to use a (graphical) config tool running on the server itself, running as one of these service accounts.
In Hoary, this was easy. I disabled logins to the service accounts, logged in as me (a sudoer), then used
to run the config tool. kdesu asked me for my password, and it Just Worked.
In Dapper, kdesu asks me for the password for the service account instead. Which is a problem, since it doesn't have one, being disabled. I can work round this by enabling logins to the service accounts, but that means more passwords to manage and it does seem to be a less secure option. Alternatively I can su to the correct account before starting X, but that's a nuisance.
Does anyone know if there's a way to make Dapper kdesu behave like Hoary kdesu did?
TIA
Will.
In Hoary, this was easy. I disabled logins to the service accounts, logged in as me (a sudoer), then used
Code:
kdesu -u <foo> konsole
In Dapper, kdesu asks me for the password for the service account instead. Which is a problem, since it doesn't have one, being disabled. I can work round this by enabling logins to the service accounts, but that means more passwords to manage and it does seem to be a less secure option. Alternatively I can su to the correct account before starting X, but that's a nuisance.
Does anyone know if there's a way to make Dapper kdesu behave like Hoary kdesu did?
TIA
Will.