seahorse

seahorse agent doesn't work with gnupg smartcard readers

Bug #185563 reported by Stephan Rügamer
66
This bug affects 10 people
Affects Status Importance Assigned to Milestone
seahorse
Confirmed
Wishlist
seahorse (Ubuntu)
Won't Fix
Wishlist
Ubuntu Desktop Bugs

Bug Description

Binary package hint: seahorse

Dear Colleagues,

as I'm using for gpg signing a smartcard reader and a signing key on this smartcard, I checked with seahorse if this is working.
It's not.

Seahorse can't cache smartcard pins (which is the default "passphrase" when using cards).
So the behaviour of seahorse is different then the behaviour of gpg-agent, which works with smartcards.

Seahorse and gpg-agent will work nicely together when you start gpg-agent before seahorse but then passphrase caching is disabled in seahorse.

I wonder how we can fix this.

Regards,

\sh

Revision history for this message
Reinhard Tartler (siretart) wrote : Re: [hardy] seahorse agent doesn't work with gnupg smartcard readers

I can confirm this bug. It most probably needs forwarding upstream (or someone to implement this feature).

Changed in seahorse:
status: New → Triaged
Bug Watch Updater (bug-watch-updater)
Changed in seahorse:
status: Unknown → Confirmed
Stephan Rügamer (sruegamer)
Changed in seahorse:
status: Triaged → Confirmed
Andreas Moog (ampelbein)
Changed in seahorse:
assignee: nobody → desktop-bugs
importance: Undecided → Wishlist
status: Confirmed → Triaged
Revision history for this message
Stephan Rügamer (sruegamer) wrote :

I wonder why the status is now "triaged" even if there are two people confirming this mis-behaviour...

a) I don't understand the meaning of triaged and confirmed
b) I don't understand the meaning of triaged and confirmed

As the bug is even in gnome upstream, and we all know it's an upstream bug, and yes it's confirmed...why not leaving this to confirmed, and don't touch it...
I understand the assignment to desktop team, but don't understand any status change...

Andreas, please explain an old man your reason for this?

Revision history for this message
Stephan Rügamer (sruegamer) wrote :

setting back to confirmed

Changed in seahorse:
status: Triaged → Confirmed
Revision history for this message
Andreas Moog (ampelbein) wrote :

From https://wiki.ubuntu.com/Bugs/Status

Triaged:

    * A member of UbuntuBugControl believes that the report describes a genuine bug in enough detail that
          a developer could start working on a fix
    * Use this when you are confident that it should be looked at by a developer and has enough information

So triaged means that upstream is aware of the bug and the developers can start working on a fix.

Changed in seahorse:
status: Confirmed → Triaged
Revision history for this message
Stephan Rügamer (sruegamer) wrote :

well,

ok then...I wonder who came up with this description, but

* upstream is aware that seahorse is not mature enough to be a full fledged replacement for gpg-agent
* upstream doesn't have the money to by a 15 euro gpg card reader
* their is no starting code for seahorse...and I wonder if we in ubuntu have the men-power to work on that bug...

But I could be wrong and didn't read the upstream bug correctly.

even if this bug is either confirmed (which is in my eyes the correct status with a higher prio then triaged, because we know already that this doesn't work and is a missing feature) or triaged, it will rot a long time from now.

Well, I just wonder what prio confirmed vs. triaged has

Revision history for this message
Phil-Taylor.com (phil-phil-taylor) wrote :

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I can confirm that this is an issue as I had the same thing

I did a pkill seahorse-agent and then gpg card reading worked again...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: http://getfiregpg.org

iJwEAQECAAYFAkkN/L0ACgkQ91k+uzVYzy7YfwQAmHGZRzF1qavrA+7+NlJpsGoS
ZULCp2EKnU8Et8NELWUtE/Cwm5HZdGYIkYtz7Uh2FZJlrfP4nxPmv71C9HxgQMUN
CHhQw4IFvwPnofaoRhfZtPtky8dt/H+oW8ABLXW0hLKpZfnMbNESJDdF51FVM2uh
P6DHyJ0t4mLXBptx9HQ=
=QA1P
-----END PGP SIGNATURE-----

Revision history for this message
timaba (timaba) wrote :

still exists in jaunty

Sebastien Bacher (seb128)
summary: - [hardy] seahorse agent doesn't work with gnupg smartcard readers
+ seahorse agent doesn't work with gnupg smartcard readers
Bug Watch Updater (bug-watch-updater)
Changed in seahorse:
importance: Unknown → Wishlist
Revision history for this message
Hugo Roy (hugoroy) wrote :

I consider this a very annoying bug, not a "wish"

Revision history for this message
Aaron C. de Bruyn (darkpixel2k) wrote :

Upgraded from 10.04 to 10.10 and got nailed by this bug.

tags: added: regression-proposed
Revision history for this message
Mario Limonciello (superm1) wrote :

Closing this bug per https://mail.gnome.org/archives/distributor-list/2015-August/msg00000.html and https://bugzilla.gnome.org/show_bug.cgi?id=644415

Changed in seahorse (Ubuntu):
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.