Wow! That finally explains why I could never get gnome-keyring to manage my ssh key: I renamed id_rsa.pub to something useful for being scp'd over to other hosts. I created a symlink and it works great now! Fantastic!
So with seahorse/keyring properly recognizing my SSH key now I care a lot less about this bug, but it is still a bug. It should get fixed at some point. Here's a totally different issue I would like fixed (maybe I should file a bug directly with Seahorse?): Seahorse should update their documentation to properly explain what the criteria are for getting your SSH key to work. Saying that id_rsa is auto-detected would be a good start, and mentioning the hard requirement that id_rsa.pub be present would be good too. Currently the info I was going on is based on a l.g.o page which give me this BS about expecting a certain mime type for the file. Nothing about it being auto-loaded. Just to be clear though, this bug is officially about the fact that the mimetype data for x-pem-key is not being registered properly. That's the bug I wanted fixed here. -- id_rsa not detected as x-pem-key https://bugs.launchpad.net/bugs/397145 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
