After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 429509 - Doesn't handle BEGIN ENCRYPTED PRIVATE KEY
Doesn't handle BEGIN ENCRYPTED PRIVATE KEY
Status: RESOLVED FIXED
Product: seahorse
Classification: Applications
Component: general
0.9.x
Other Linux
: Normal normal
: 2.20.0
Assigned To: Seahorse Maintainer
Seahorse Maintainer
Depends on:
Blocks:
 
 
Reported: 2007-04-13 21:26 UTC by Benoît Dejean
Modified: 2007-04-13 22:56 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Benoît Dejean 2007-04-13 21:26:56 UTC 
Hello,

the VCS monotone use ssh-agent and the gnome-keyring in the notification area which uses seahorse AFAIK doesn't recognize the key. It instead shows "Unknow Key: ..."

BEGIN ENCRYPTED PRIVATE KEY are AFAIK RSA key and should handled the same way. Thanks
Comment 1 Stef Walter 2007-04-13 22:17:55 UTC 
Good catch. Fixed. Will be included in 1.0.2

2007-04-13  Nate Nielsen  <nielsen@memberwebs.com>

    * plugins/nautilus/seahorse.xml: Recognize encrypted private
    keys properly. Fixes bug #429509

Commit: 1728
Comment 2 Benoît Dejean 2007-04-13 22:39:29 UTC 
Are you sure this enough ? I don't understand how is it related to a nautilus plugin.

I was talking about this http://lists.gnu.org/archive/html/monotone-devel/2007-04/pngUIt8pjjARK.png
Comment 3 Stef Walter 2007-04-13 22:56:17 UTC 
Yeah the files are in the wrong places in the seahorse tree. Now that we've moved to SVN it's something I hope to fix this cycle. 

But basically that's the file by which seahorse registers it's known mime types. It then uses those mimetypes to detect how to import something.