New answers tagged

6

For that key, the organization don't have non-repudiation. IE, if someone does something abusive or destructive to that system using 'your' key, the admin can't point the blame at you for being solely responsible for it. Since the person that gave it to you also had the key. It probably isn't that bad for you, since it gives you a defense, but horrible ...


10

It is exactly as you say: The whole concept of public key authentication is that the private key should only be known to the owner, while the corresponding public key can be widely disseminated. The security of your authentication depends on the security of the private key, not of the security of the public key. The fact that somebody else provides you ...


0

There're lots of similar ways to (do) this: ssh root@SomeHost 'tar cpBf - .ssh/authorized_keys | sudo -iu postgres tar xpBf -' in fact, this very command copies the whole root's authorized keys to postgres' user, but usually there's no problem with that since root's access is always superior and it means that anyone with root's access can gain access to ...


0

Well, if you can login passwordlessly as root you could do something like this I guess: scp pub_key root@<host>: ssh root@<host> 'mkdir -p ~postgres/.ssh; cat pub_key >> ~postgres/.ssh/authorized_keys; chown -R postgres.postgres ~postgres/.ssh; chmod 644 ~postgres/.ssh/authorized_keys; chmod 700 ~postgres/.ssh; rm -f pub_key' which will ...


0

You could do something like: for f in list_of_servers; do ssh root@${f} "mkdir -p ~postgres/.ssh; echo $KEY >> ~postgres/.ssh/authorized_keys; chown -R postgres:postgres ~postgres/.ssh; chmod 400 ~postgres/.ssh/authorized_keys; chmod 700 ~postgres/.ssh"; done or if you have these machines in automation using something like Puppet or Salt, this would be ...


1

To connect server using quick fix command: ssh -o IdentitiesOnly=yes -i ~/.ssh/private_key_or_pem_file_name server_user_name@ip_OR_hostname echo ok Recommended Way is mentioned below: But if you have capistrano receipes or other softwares which are connecting your ssh server then you have to fix in proper way as mentioned below: In ~/.ssh/config file ...


4

ssh-keygen, the OpenSSH command used to generate keys, uses the OpenSSL library, so there's really no difference between the two methods. You can safely use ssh-keygen which is the default and more immediate tool to create a key pair for SSH pubkey authentication.



Top 50 recent answers are included