'core' default password is not documented.

[bartonski]

In docs/using-coreos/index.md the default user is shown to be core

NOTE: the user for ssh is core.

When I try to log in via ssh, I am prompted for a password -- the default password is neither empty nor core -- the obvious choices. What is the default password?

[philips]

@bartonski There is no default password. You need to use ssh key auth. On vagrant you can use vagrant ssh, on ec2 you can use the key pair, on qemu you can use the scripts we provide http://coreos.com/docs/qemu/#ssh-keys

[jasonk000]

This assumes the network comes up cleanly, which if it doesn't, how does one log in to the host?

[polvi]

Which environment are you trying to boot with?

[jasonk000]

Production environment; see here - https://groups.google.com/forum/#!topic/coreos-dev/Ynm9URNTM74

[kunthar]

@jasonk000 +1

[marineam]

Yeah, sorry about the bnx2 driver being broken. I'm half way through fixing the firmware situation in our builds so the next release should fix that. The ability to set a password for the 'core' user is also in progress but that is part of a larger restructuring of the whole filesystem. That should land this month though.

[philips]

@marineam Most of the trouble with the core password is on real hardware where network doesn't come up. I was thinking of adding an 'no_passwd' parameter to the kernel that would remove the login from the getty.

[marineam]

@philips or a 'setup' option that replaces getty on tty1 (or setup=ttyS0 for others) that prompts the user to set a password and maybe optionally asks for other things like hostname or timezone. Those things people expect from a normal installer. :) After the usr switch I also intend to add password setup to the install script.

Caffeinated and will be hacking like crazy today, seriously need to get this filesystem fixed.

[Telmo]

any updates on this? In my vCenter the CoreOS image wont come up with an IP so I can't login to it.

[robszumski]

@Telmo We're really close to finishing up new images that support cloud-config. With those images you'll be able to create and modify users, including the core user: https://github.com/coreos/coreos-cloudinit/blob/master/Documentation/cloud-config.md#users Stay tuned.

[marineam]

For the record in case someone is following along, there is a coreos.autologin kernel option to enable passwordless login on a console and config-drive is supported on all VM platforms. I'd generally recommend using config-drive if you don't have any other way to install a cloud config rather than dealing with kernel options.

kernel options documented here: http://coreos.com/docs/running-coreos/bare-metal/booting-with-pxe/
config drive: https://github.com/coreos/coreos-cloudinit/blob/master/Documentation/config-drive.md

[seemsindie]

I have no idea what to do. To confusing for me :)

I followed the vagrant setup guide, and i did all the steps and all went ok. But the last one is displaying this when i try to ssh to it:

λ vagrant ssh core-01 -- -A                                              
Enter passphrase for key 'C:/Users/Ivan/.vagrant.d/insecure_private_key':
core@127.0.0.1's password:                                               
core@127.0.0.1's password:                                               
core@127.0.0.1's password:                                               
Permission denied (publickey,password,keyboard-interactive).

for ssh passphrase i just press enter and it asks me fore core password. Shouldn't this be passwordless login?

[crawford]

@peacemaker94 I'm guessing you have a password on your private key. When you hit enter instead of entering your password, it fails to authenticate with the key and falls back to password authentication (which, of course, will fail).

[seemsindie]

@crawford Well that is weird, cuz i don't remember choosing any passphrase for that key...