If there is a security policy in place that prevents you from running sudo commands without a password, then I would suggest changing the policy, rather than going with the option below. Setting the setuid bit is probably more of a securty risk than running a sudo command without a password. Of course, both can be exploited if the permissions on the executable are not restricted.
-Rob A > -----Original Message----- > From: Alexey N. Solofnenko [mailto:[EMAIL PROTECTED] > Sent: Wednesday, November 03, 2004 10:03 PM > To: Ant Users List > Subject: Re: How do I execute a sudo ssh command? > > > There are also other ways: > > * set setuid bit on executable you want to execute under different > credentials; > * execute ssh [EMAIL PROTECTED] and copy authorized keys from your account > into that user account - in that case ssh will not ask > for a password. > > - Alexey. > > Colin Harris wrote: > > >Is that really the only way. I find it hard to believe that > there is no > >other way to achieve this. > >Unfortunetely it is not possible for me to configure sudo to > allow me to run > >commands without entering the password. > > > >col. > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
