Opened 2 years ago
Closed 2 years ago
#18145 closed bug (no change required)
No sshd_keymaker.sh run on first boot?
| Reported by: | humdinger | Owned by: | waddlesplash |
|---|---|---|---|
| Priority: | normal | Milestone: | Unscheduled |
| Component: | - General | Version: | R1/beta4 |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
This is with the r1beta4, RC, 64bit.
I downloaded the r1beta4 RC image and installed it on a BFS formatted partition with Installer.
On a first bootup, I'm normally greeted with a notification saying "Generating ssh keys...". Not this time.
Change History (6)
comment:1 by , 2 years ago
comment:2 by , 2 years ago
Did you install overtop of an existing install?
Nope. Empty BFSformatted partition.
if there are SSH keys present in ~/config/settings/ssh,
There is not.
comment:3 by , 2 years ago
You can try and run the script manually and see what happens. Perhaps it failed for some reason?
comment:4 by , 2 years ago
When invoking manually, I do see the notification showing the progress. There is still no ~/config/settings/ssh, but there are keys at /system/settings/ssh/ . And from the modification time, they were created on first boot-up.
Questions remain:
- Is the location under /system/settings/ssh OK?
- Why was there no progress notification on first boot-up?
- Why was there a progress notification when I manually invoked the script, though no new keys were generated (all files had the older modification time from first boot-up)?
comment:5 by , 2 years ago
Is the location under /system/settings/ssh OK?
Yes. This is probably the per-machine keys, not the per-user keys. I should have realized that initially.
Why was there no progress notification on first boot-up?
No idea.
Why was there a progress notification when I manually invoked the script, though no new keys were generated (all files had the older modification time from first boot-up)?
The script just invokes SSH to do the real work, I think, and SSH probably sees the keys already exist and are valid and decides nothing needs to be done.
comment:6 by , 2 years ago
| Resolution: | → no change required |
|---|---|
| Status: | assigned → closed |
Since things seem to be working, I think we can close this as "no change required".
I think the "Generating SSH keys..." likely does not need to run if you've installed with Installer?
Did you install overtop of an existing install?
Either way, if there are SSH keys present in
~/config/settings/ssh, I don't think we need to worry about this too much and can probably close it.