local environment broken with root perms

[John A Meinel]

Currently using trunk (r2207) I see several failures wrt ssh and files/dirs owned by root.

After doing "sudo juju bootstrap -e local --debug"

I end up having a new
~/.ssh/authorized_keys file which is owned "root:root"

Trying to deploy something fails:
$ juju deploy -e local ubuntu --debug
error: cannot load ssh client keys: open /home/jameinel/.juju/ssh: permission denied

This is extra bad, because 'deploy' doesn't need to SSH into anything, so I don't quite see why it would break.
If I chown -R jameinel: ~/.juju/ssh then things seems to work.

But:
a) I don't think we want to mutate/write the host's ~/.ssh/authorized_keys file (if we did, then we should probably only do that on an 'ubuntu' user

b) The ~/.juju/ssh directory ends up owned by root rather than the user, and then it can't be read by future commands

[Tim Penhey (thumper)]

OK, there are two issues here.

a) modifying ~/.ssh/authorized_keys is wrong, and the worker that was messing with that has been stopped.

... r2207? that really shouldn't be modifying the host authorized_keys...

b) the ~/.juju/ssh directory owned by root is a problem.

[Tim Penhey (thumper)]

Now I'm confused...

I just bootstrapped a new local environ, with r2210, and had neither of the issues you mention above.

[Tim Penhey (thumper)]

Ahh... got it now...