ssh-agent autostart?

[Mike Michel]

Hi,

following the Howto http://coreos.com/blog/coreos-clustering-with-vagrant/ im wondering why i have to start ssh-agent manually via eval `ssh-agent -s` so i can do the mentioned ssh based fleetctl commands. After a reboot i also have to do ssh-add  ~/.ssh/insecure_private_key again. Is this by design?

Best,

Mike

[Seán C. McCord]

This is not a CoreOS-related issue.

http://stackoverflow.com/questions/18880024/start-ssh-agent-on-login

--
You received this message because you are subscribed to the Google Groups "CoreOS User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to coreos-user...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
Seán C. McCord

ule...@gmail.com

CyCore Systems

[Brian Waldon]

On Jun 10, 2014, at 3:31 AM, Mike Michel <mike.mi...@gmail.com> wrote:

> Hi,
>
> following the Howto http://coreos.com/blog/coreos-clustering-with-vagrant/ im wondering why i have to start ssh-agent manually via eval `ssh-agent -s` so i can do the mentioned ssh based fleetctl commands.

We’re using ssh-agent as a keyring manager so we don’t risk getting it wrong in the fleetctl tool. The “eval `ssh-agent -s`` simply starts an instance of ssh-agent and sets the appropriate environment variables (SSH_AUTH_SOCK, being the important one).

> After a reboot i also have to do ssh-add ~/.ssh/insecure_private_key again. Is this by design?

This is adding the necessary SSH private key to your new instance of ssh-agent. Since you have not created any configuration for ssh-agent, you’re essentially starting from a blank slate every time you boot up.

[Mike Michel]

Ok, i was under the impression that the coreos nodes also need this to communicate to each other for internal stuff. If it is only needed when admins start fleet commands manually, i will check the .bash_profile way  or something else.

Thanks,

Mike