Ssh – Default SSH credentials for CoreOS

coreosopenstack-novassh

I am trying to play around with CoreOS, and I just went to their ISO download site and downloaded the latest stable ISO. I then created a new VM instance with that ISO, and it looks like the instance is up and running beautifully.

I would now like to SSH into this machine, but it just dawned on me that I don't have a username/password. Any ideas as to what the default/root passwords would be? I checked the CoreOS site and can't seem to find any.

Nitty gritty details: I actually uploaded the ISO to a local OpenStack cluster, which took care of creating the image for me, but I don't think that matters.

Best Answer

I don't have the rep to comment, but Micheal Hampton is correct, CoreOS has a root user and a core user, neither of which have passwords.

If you have the Openstack CLI set up, you can issue nova keypair-list to see your keys and nova keypair-add --pub-key ~/.ssh/id_rsa.pub <keyname> to add a new one. You should then be able to SSH in as the core user, with that key. (Though you may have to cycle the VM - not sure.) Note that this is passed through the openstack metadata service.

As Brian Redbeard points out, you can also put ssh-keys in the cloud-config yaml file. That can be passed through either the metadata service or the cloud drive as the user-data flag.

Related Solutions

Ubuntu – Connecting to Amazon EC2 over SSH from Ubuntu

To use your EC2-priv.ppk key from your Ubuntu desktop you will have to convert it into a format that OpenSSH will understand. You can go this with the PutTTYgen program.

Run PuTTYgen and click on Conversions->Import key. Import your EC2-priv.ppk private key. Then click Conversions->Export OpenSSH key. Save the converted key.

PuTTYgen will also show the public key associated with the private key. This should be added to the $HOME/.ssh/authorized_keys file on your ec2 instance.

Now you have a key in a format that ssh on your Ubuntu system will understand. copy this key to $HOME/.ssh/identity. Ensure that the permissions are 600 on the identity file.

You should now be good to go.

Regarding the use of public key authentication. This really is the way that you should authenticate to your system. It is extremely unlikely that any brute force attack will succeed and is far more secure than simple passwords.

Ssh – How to automate SSH login with password

Don't use a password. Generate a passphrase-less SSH key and push it to your VM.

If you already have an SSH key, you can skip this step… Just hit Enter for the key and both passphrases:

$ ssh-keygen -t rsa -b 2048
Generating public/private rsa key pair.
Enter file in which to save the key (/home/username/.ssh/id_rsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /home/username/.ssh/id_rsa.
Your public key has been saved in /home/username/.ssh/id_rsa.pub.

Copy your keys to the target server:

$ ssh-copy-id id@server
id@server's password:

Now try logging into the machine, with ssh 'id@server', and check-in:

.ssh/authorized_keys

Note: If you don't have .ssh dir and authorized_keys file, you need to create it first

to make sure we haven’t added extra keys that you weren’t expecting.

Finally, check to log in…

$ ssh id@server

id@server:~$

You may also want to look into using ssh-agent if you want to try keeping your keys protected with a passphrase.

Best Answer

Related Solutions

Ubuntu – Connecting to Amazon EC2 over SSH from Ubuntu

Ssh – How to automate SSH login with password

Related Topic