Tag Info

New answers tagged

1

Even better would be to gen a separate support account, provide it to the person-to-be-later-named, and provide that account (or even better the group that account is in) the ability to impersonate you with SUDO, so what they do will be logged and can be controlled without giving them your account. That said, the default setup of OpenSSH (the most common ...


2

Yes, absolutely. It's the default config on most systems: If a key is presented at login, use it. Ask for a password otherwise. If it's a good idea to allow password-based login at all is another topic.


0

Use Userify to create corrected user accounts. Shut down your instance. Right click and choose "View/edit UserData script" Paste either the CloudInit or Shell Script deployments for Userify Paste your SSH Public key into your Userify Account Boot your instance Grant yourself root access by clicking "root" in Userify Wait 30 seconds and then log in and fix ...


0

After I was able to ssh via Google web console, I did the following steps to resolve this. Generate ssh key using ssh-keygen Copy the key.pub file contents Append the contents to ~/.ssh/authorized_keys file sudo nano ~/.ssh/authorized_keys


5

If your shop uses a configuration management tool such as Puppet, CFEngine, Chef, etc, that would be the easiest way. If not, but you have an directory service that does LDAP, there is an extension to OpenSSH to store public keys in the directory. Lastly, you can wrap the public keys into an RPM and distribute them like you would software. This would ...



Top 50 recent answers are included