On Tue, 07 Feb 2017 15:17:04 +0900 NIIBE Yutaka wrote:
Hello,
Hello,
On GNU/Linux, use of PC/SC service is not recommended for OpenPGP card
Why is that exactly?
(installing PC/SC is OK) and the use of different smartcards with PC/SC
(OpenPGP card together with other
On 2017-02-08 10:24:59, Antoine Beaupré wrote:
> any ideas? should this be a separate bug report? it doesn't *look* like
> it's the same issue because the workaround fails...
i have filed a separate bug report against scdaemon regarding this, to
see if we can make it work without pcscd (it
On 2017-02-07 09:28:33, Antoine Beaupré wrote:
>> does this line of thinking make sense?
>
> yes, it makes sense. i'll try to figure out if pcscd had crashed - but I
> don't understand how reinstalling the package could have possibly fixed
> this.
so here's what i could find. my first (traumatic)
On 2017-02-06 23:01:16, Daniel Kahn Gillmor wrote:
> On Mon 2017-02-06 19:55:58 -0500, Antoine Beaupré wrote:
>> the daemon stopped working again - even with disable-ccid:
>>
>> $ LANG=C gpg --card-status
>> gpg: selecting openpgp failed: No such device
>> gpg: OpenPGP card not available: No such
On Mon, 6 Feb 2017 07:04, gni...@fsij.org said:
> simultaneously/interchangeably on a system. scdaemon is not a system-
> wide service for all smartcards, but it's specific to OpenPGP card and
> it's per user service for gpg-agent.
FWIW: Scdaemon supports several smartcards and certain other
Hello,
Thank you very much for the discussion. I appreciate the viewpoints
from users. No, it's not frustrating at all.
Daniel Kahn Gillmor wrote:
> Can we offer a user experience that doesn't involve them making a choice
> between two indistinguishable options?
>
> A
On Mon 2017-02-06 19:55:58 -0500, Antoine Beaupré wrote:
> the daemon stopped working again - even with disable-ccid:
>
> $ LANG=C gpg --card-status
> gpg: selecting openpgp failed: No such device
> gpg: OpenPGP card not available: No such device
>
> i got a different error now:
>
> fév 06
On Mon 2017-02-06 14:39:34 -0500, NIIBE Yutaka wrote:
> I think that an explanation like following is good.
>
> If you want to use PC/SC service, please add
>
> disable-ccid
>
> in .gnupg/scdaemon.conf. Or do:
>
> echo disable-ccid:0:1 | gpgconf --change-options
the daemon stopped working again - even with disable-ccid:
$ LANG=C gpg --card-status
gpg: selecting openpgp failed: No such device
gpg: OpenPGP card not available: No such device
i got a different error now:
fév 06 19:45:29 curie gpg-agent[1643]: gpg-agent (GnuPG) 2.1.18 starting in
Daniel Kahn Gillmor wrote:
> On Mon 2017-02-06 01:04:44 -0500, NIIBE Yutaka wrote:
>> This works. Actually, this is not mandatory. It is OK to have pcscd
>> package installed **if not used**.
>
> I take it you mean that the system-wide pcscd service
On Mon 2017-02-06 06:40:07 -0500, Wouter Verhelst wrote:
> On Mon, Feb 06, 2017 at 02:13:25AM -0500, Daniel Kahn Gillmor wrote:
>> On Mon 2017-02-06 01:04:44 -0500, NIIBE Yutaka wrote:
>> > This works. Actually, this is not mandatory. It is OK to have pcscd
>> > package
On Mon, Feb 06, 2017 at 02:13:25AM -0500, Daniel Kahn Gillmor wrote:
> On Mon 2017-02-06 01:04:44 -0500, NIIBE Yutaka wrote:
> > This works. Actually, this is not mandatory. It is OK to have pcscd
> > package installed **if not used**.
>
> I take it you mean that the
hi gniibe--
thanks for the thoughtful followup!
On Mon 2017-02-06 01:04:44 -0500, NIIBE Yutaka wrote:
> This works. Actually, this is not mandatory. It is OK to have pcscd
> package installed **if not used**.
I take it you mean that the system-wide pcscd service itself needs
Daniel Kahn Gillmor wrote:
> To be concrete, i believe the two proposed solutions for users are:
[...]
> Do not use CCID
> ---
>
> echo disable-ccid:0:1 | gpgconf --change-options scdaemon
>
Correct.
The things for PCSC is a bit complicated. Let me
On Sun 2017-02-05 06:20:38 -0500, Wouter Verhelst wrote:
> I concur; the workaround is relatively easy (choose one option, where
> "CCID" is probably the most common and certainly the most tested by
> the developers themselves, and disable the other method), and after
> that the problem is gone.
So, for clarity,
On Sat, Feb 04, 2017 at 12:37:52PM -0500, Antoine Beaupre wrote:
> This seems like an important regression, however. If "disable-ccid"
> should absolutely be added by users, this should be noted in the
> NEWS.Debian file. Alternatively, this should "just work" regardless of
>
On Fri, Feb 03, 2017 at 09:40:35AM +0900, NIIBE Yutaka wrote:
> Hello,
>
> Thanks to dkg to explicitly CC me.
>
> On Thu 2017-02-02 17:54:26 -0500, Wouter Verhelst wrote:
> > Since a recent upgrade, gnupg-agent no longer finds the authentication
> > (SSH) key on my OpenPGP smartcard:
> >
> >
On Sat, Feb 04, 2017 at 01:56:08AM +0900, NIIBE Yutaka wrote:
> NIIBE Yutaka wrote:
> > Ah... I think that I enbugged a bug for PC/SC, and scdaemon with PC/SC
> > is somehow broken in 2.1.18. Please try with internal CCID driver of
> > GnuPG. I mean, don't use PC/SC service.
>
On Sat, Feb 04, 2017 at 01:30:52AM +0900, NIIBE Yutaka wrote:
> Wouter Verhelst wrote:
> > wouter@gangtai:~$ cat .gnupg/scdaemon.conf
> > reader-port O2 Micro Oz776 01 00
> > log-file /home/wouter/.gnupg/scdaemon.log
> > pcsc-driver libpcsclite.so
>
> Ah... I think that I enbugged
NIIBE Yutaka wrote:
> Ah... I think that I enbugged a bug for PC/SC, and scdaemon with PC/SC
> is somehow broken in 2.1.18. Please try with internal CCID driver of
> GnuPG. I mean, don't use PC/SC service.
Or, please add:
disable-ccid
in your scdaemon.conf if you
Wouter Verhelst wrote:
> wouter@gangtai:~$ cat .gnupg/scdaemon.conf
> reader-port O2 Micro Oz776 01 00
> log-file /home/wouter/.gnupg/scdaemon.log
> pcsc-driver libpcsclite.so
Ah... I think that I enbugged a bug for PC/SC, and scdaemon with PC/SC
is somehow broken in 2.1.18.
On Fri, Feb 03, 2017 at 09:40:35AM +0900, NIIBE Yutaka wrote:
> Hello,
>
> Thanks to dkg to explicitly CC me.
>
> On Thu 2017-02-02 17:54:26 -0500, Wouter Verhelst wrote:
> > Since a recent upgrade, gnupg-agent no longer finds the authentication
> > (SSH) key on my OpenPGP smartcard:
> >
> >
Hello,
Thanks to dkg to explicitly CC me.
On Thu 2017-02-02 17:54:26 -0500, Wouter Verhelst wrote:
> Since a recent upgrade, gnupg-agent no longer finds the authentication
> (SSH) key on my OpenPGP smartcard:
>
> wouter@gangtai:~$ gpg --card-status
It should be an issue of scdaemon. For
Control: reassign 854005 scdaemon
Hi Wouter--
On Thu 2017-02-02 17:54:26 -0500, Wouter Verhelst wrote:
> Since a recent upgrade, gnupg-agent no longer finds the authentication
> (SSH) key on my OpenPGP smartcard:
>
> wouter@gangtai:~$ gpg --card-status
>
> Reader ...: ACS ACR38U 00 00
>
Package: gnupg-agent
Version: 2.1.18-3
Severity: normal
Hi,
Since a recent upgrade, gnupg-agent no longer finds the authentication
(SSH) key on my OpenPGP smartcard:
wouter@gangtai:~$ gpg --card-status
Reader ...: ACS ACR38U 00 00
Application ID ...: D27600012401020100054736
25 matches
Mail list logo