-
Notifications
You must be signed in to change notification settings - Fork 103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sshd isn't auto generating keys on startup #25
Comments
Watch the journal, it should be generated within a minute, is longer now as we try to generate some entropy before hand... |
Not seeing it ubuntu@arm:/etc/ssh$ uptime |
Weird, remove the SSH.regenerate file, then it'll keep you new keys, I'll take a look at it later tomorrow when I get back home. |
Keys aren't generated at all. After flashing and booting i could not connect through ssh / ethernet. This is because the |
@julianhille missing context, whhat "image" are you talking about? |
@RobertCNelson about the image from the author of this issue (https://rcn-ee.com/rootfs/2016-02-11/flasher/BBB-eMMC-flasher-ubuntu-14.04.3-console-armhf-2016-02-11-2gb.img.xz) |
Oh, i'm done with 14.04's.. http://elinux.org/BeagleBoardUbuntu Regards, |
Ah ok, you may close then. But maybe there should be any info about that. :) |
Not sure if this is the write project to put this in. I downloaded the eMMC image (https://rcn-ee.com/rootfs/2016-02-11/flasher/BBB-eMMC-flasher-ubuntu-14.04.3-console-armhf-2016-02-11-2gb.img.xz) and got it installed onto the MMC. When it booted up, the SSH was reporting Connection reset by xxx.xxx.xxx.xxx. I found that the sshd keys weren't there. Running sudo ssh-keygen -A fixed it, but they aren't preserved across reboots. I'm not sure what is removing them as the filesystem looks like it is read/write.
/dev/disk/by-uuid/f4bf46ba-aa1e-4fbe-81c7-3e8269c0bf59 / ext4 rw,noatime,errors=remount-ro,data=ordered 0 0
The text was updated successfully, but these errors were encountered: