Comment 4 for bug 150654
Revision history for this message
| nine (niin-deactivatedaccount-deactivatedaccount) wrote | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
From the Seahorse help I understand that importing is done for public keys only: "To import keys choose Key > Import and select, from the file chooser, a file containing at least one ASCII armored public key.".
From that I would not expect importing private SSH keys to work anymore. And it would indeed be an indication that some mime info is not needed by Seahorse. You can ask the Seahorse developers for confirmation if you like (some ubuntu developers from the changelog file might know too).
Public ASCII armored keys are recognized in the file chooser when importing. Can you confirm that?
Importing public SSH keys gives an error message, but I'd say that should be fixed in the help text by excluding them there. Do you agree with that? If so, I will file a separate bug for that.