Set up authorized_keys earlier in the boot process
Bug #370628 reported by
Eric Hammond
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ubuntu on EC2 |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
When I (or an automated process) attempts to ssh to the ubuntu user right after sshd starts accepting connections, I always get "Permission denied (publickey)." If I wait a few seconds more and try again, I generally get in cleanly.
Please set up the authorized_keys file for the ubuntu user a bit earlier in the boot process.
Note: sshd seems to be started at S16. The official Ubuntu images set up authorized_keys at S90. On the Ubuntu images I build, I do the authorized_keys setup at S70ec2... and it seems to get in soon enough that my automated ssh is never rejected.
Related branches
Revision history for this message
| Chuck Short (zulcss) wrote | #1 |
| Changed in ubuntu-on-ec2: | |
| status: | New → Fix Committed |
| Changed in ubuntu-on-ec2: | |
| status: | Fix Committed → Fix Released |
Revision history for this message
| Scott Moser (smoser) wrote | #2 |
To post a comment you must log in.
This is fixed for the next version of ec2-init.