[ec2-beta] document: EC2 Ubuntu sudo Guide

[Michael Greenly]

What I'm currently doing is exactly what Eric mentioned above.  My scripts
go something like this....

sudo cp /home/ubuntu/.ssh/authorized_keys /root/.ssh/
/* do installation (this includes rsync push to root) */
sudo rm /root/.ssh/authorized_keys
/* bundle image & register AMI */

I guess the reason I ask about a script to do it is because /etc/ssh/sshd
config should have PermitRootLogin=no and the root password should be
disabled if the user mistakenly set it.

Is there anythign else that should be set that I'm not aware of?

On Wed, Mar 11, 2009 at 8:08 AM, Neale Rudd <neale at metawerx.net> wrote:

>  Michael Greenly said:
> > The advantage is that rsync as root would work and that's an extremely
> likely activity given what this AMI is and how it will be used.
> Hi Michael,
>
> Since setup scripts for the kind of worker-machine you are discussing would
> probably be automated anyway, is it much of a problem to get them to issue a
> sudo command first then run rsync as root?
>
> If the remote system is feeding commands to the ssh session, this should be
> quite easy.
>
> As I stated in my last email, I haven't personally tried this yet, but if
> you have, can you provide some tips on why it doesn't work?  If it does,
> that's great, if it doesn't, I'd be interested as to why, because I'm going
> to attempt exactly this type of setup shortly.
>
> Best Regards,
> Neale
>
>



-- 
Michael Greenly
http://blog.michaelgreenly.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/mailman/private/ec2/attachments/20090311/26d2730a/attachment-0002.htm