reopen 787860 kthxbye On Sun, Apr 11, 2021 at 04:03:19PM +0000, Debian Bug Tracking System wrote:
> On Fri, 05 Jun 2015 at 16:45:28 -0400, Daniel Kahn Gillmor wrote: > > I've now filed a more extensive changeset at seahorse upstream, as noted > > above. > This seems to have been applied a long time ago: since version 3.20.0, > seahorse upstream only has what was formerly the GnuPG 2 code path, and > does not support use of GnuPG 1.4. This bug appears to have drifted well away from the initial report (which was about GNOME forcing itself as the SSH agent even if one is already set) - I don't understand how this discussion would be relevant to the reported issue and I've never seen any acknowledgement that GNOME sees this as a problem. You can see in the bug log that at one point the discussion switches from discussions of gpg-agent providing SSH_AUTH_SOCK to discussions of interactions between gpg and gpg-agent which is a separate issue.
signature.asc
Description: PGP signature