Your message dated Mon, 03 Oct 2016 17:58:05 -0400
with message-id <[email protected]>
and subject line Re: [pkg-gnupg-maint] Bug#839614: gnupg2: what happened to
scdaemon?
has caused the Debian Bug report #839614,
regarding gnupg2: what happened to scdaemon?
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
839614: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839614
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gnupg2
Version: 2.1.15-3
Severity: important
Tags: newcomer
Dear Maintainer,
I updated packages at some point and now my smartcards don't work,
because scdaemon has disappeared.
$ gpg --card-status
gpg: error getting version from 'scdaemon': No SmartCard daemon
gpg: OpenPGP card not available: No SmartCard daemon
$ ls /usr/lib/gnupg2/
gpg-preset-passphrase gpg-protect-tool
$ apt-show-versions | grep scdaemon
scdaemon:amd64/stretch 2.1.15-3 uptodate
$ cat ~/.gnupg/gpg-agent.conf
pinentry-program /usr/local/bin/pinentry-qt
keep-display
display :0.0
enable-ssh-support
default-cache-ttl 14400
max-cache-ttl 14400
scdaemon-program /usr/lib/gnupg2/scdaemon
sh
debug-level none
homedir /home/kevin/.gnupg
After restarting gpg-agent:
$ gpg --card-status
gpg-agent[1667]: can't connect to the SCdaemon: IPC connect call failed
gpg: error getting version from 'scdaemon': No SmartCard daemon
gpg: OpenPGP card not available: No SmartCard daemon
$ zcat /usr/share/doc/gnupg2/changelog.Debian.gz | grep scdaemon
- minor cleanup to scdaemon dealing with removed cards
* remove scdaemon.service; it will be managed by gpg-agent.service
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.6.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages gnupg2 depends on:
ii gnupg 2.1.15-3
gnupg2 recommends no packages.
gnupg2 suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
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
[email protected].
> 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
--- End Message ---
