On Mon 2016-10-03 13:20:00 -0400, Kevin Gallagher wrote: > Thanks for pointing out what changed! I should've looked harder and > would've found the new path. I consider this resolved.
thanks, i'm closing this debian bug report then by mailing 839614-d...@bugs.debian.org. > On 10/03/2016 05:21 AM, Daniel Kahn Gillmor wrote: > >> I also wonder about that. If it's a common misconfiguration, perhaps we >> should provide a symlink in the scdaemon package? I'd rather avoid this >> sort of cruft if possible. >> >> Kevin, do you have any memory or notes of what caused you to add this >> configuration option? > > I don't remember exactly, but I'm something of a power user and have > spent a lot of time debugging gpg-agent and working with various > smartcards, even writing guides > <https://gist.github.com/ageis/5b095b50b9ae6b0aa9bf> on how to set them > up. I very vaguely recall at one point my gpg-agent was having trouble > communicating with scdaemon, or throwing errors related to scdaemon or > perhaps showing some version incompatibility, so I added that line for > good measure. > > A Google search for that option shows that it's relatively uncommon. > It's certainly much less likely for others without custom gpg-agent > configurations to run into this issue, but a symlink still might be nice. if anyone really wants a symlink, they can open a separate ticket about it. if there's no other interest i'd just as soon not perpetuate the cruft :) --dkg
signature.asc
Description: PGP signature
