paulhoule
authorized_keys corrupted
I threw ami-4a57b522 over the wall to the AWS Marketplace people and they couldn't log in as "Ubuntu".
I was able to replicate the problem myself. I unmounted the root volume and mounted it on a t1.micro in us-east-1c to
When I looked at the authorized keys files I saw a bunch of binary data in the file; at the end of all the binary data, I see what looks like a line from a real authorized_keys file.
My hunch right now is that when the shred command was used just before shutting the system down, and we got some kind of file corruption. A possible fix is to have some time delay after the shred and also to call sync. When I look at the manual page, however, it seems I need to use the '-u' option if I actually want the file deleted.
I could try to mount the snapshot to get confirming evidence but I believe enough that I've found the right answer that I am inclined to just try and fix it directly.
