New answers tagged ssh-keys
When your instance is first created, it will not have any SSH keys in it by default, so you have to transfer them there, e.g., by using gcloud to connect to it the first time as described in this SO answer or by manually creating SSH keys and manually adding them to your instance as described in another SO answer.
Using the salt command salt '*application-server-*' cmd.run \ "ssh-keygen -q -N '' -f /home/helen/.ssh/id_rsa" \ runas=helen http://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.cmdmod.html#salt.modules.cmdmod.run Using a state You can specify the user when using the cmd state: generate_ssh_key_helen: cmd.run: - name: ...
Per https://help.github.com/articles/working-with-ssh-key-passphrases/#platform-mac it seems that Mac OSX caches the key in its own keychain. This in turn becomes an alternate data-source for ssh-agent.
The port number shown is the ephemeral client-side port number, corresponding to the source port as seen by the SSH server. Server-side, all ssh connections are to port 22. Here's me sshing into my colo'ed server, and confirming the port listed in the relevant syslog file: odessa% ssh www.teaparty.net [...] [me@lory ~]$ tail -2 /var/log/facility/authpriv ...
See the AuthenticationMethods setting in man sshd. If you're managing ssh servers, you need to be familiar with that contents of that man page.
Top 50 recent answers are included