El día viernes, mayo 17, 2024 a las 01:39:55 +0900, NIIBE Yutaka escribió:
> Hello,
>
> Matthias Apitz wrote:
> > This isn't that easy. The pcscd is running (when needed) as:
> >
> > purism@pureos:~$ ps ax | grep pcscd
> >2151 ?Ssl0:00 /usr/sbin/pcscd --foreground --auto-exit
> >
Hello,
Matthias Apitz wrote:
> This isn't that easy. The pcscd is running (when needed) as:
>
> purism@pureos:~$ ps ax | grep pcscd
>2151 ?Ssl0:00 /usr/sbin/pcscd --foreground --auto-exit
>
> it is launched by a system service:
I see. IIUC, PureOS is Debian based. There should
El día jueves, mayo 16, 2024 a las 04:09:44 +0900, NIIBE Yutaka escribió:
> Hello,
>
> Matthias Apitz wrote:
> > It seems that the first time is longer. I will increase the debug-level
> > for scdaemon.
>
> Thank you for the information. I think that it's better to debug how
> PC/SC goes.
>
>
Hello,
Matthias Apitz wrote:
> It seems that the first time is longer. I will increase the debug-level
> for scdaemon.
Thank you for the information. I think that it's better to debug how
PC/SC goes.
To get full debug log in lower level, you can invoke pcscd manually with
root:
# LIBCCID_
Hello,
I wonder if it taks always 8-9 secs, or it's only for the first time.
Matthias Apitz wrote:
> /tmp/scdaemon-debug.log:
[...]
> 2024-05-15 11:07:58 scdaemon[16983] DBG: chan_7 <- SERIALNO
>
> It takes 8 secs until scdaemon detects the reader, waht does this maen?
>
> 2024-05-15 11:08:06 sc
El día jueves, mayo 16, 2024 a las 03:00:52 +0900, NIIBE Yutaka escribió:
> Hello,
>
> I wonder if it taks always 8-9 secs, or it's only for the first time.
>
> Matthias Apitz wrote:
> > /tmp/scdaemon-debug.log:
> [...]
> > 2024-05-15 11:07:58 scdaemon[16983] DBG: chan_7 <- SERIALNO
> >
> > It
Hello,
I'm using an OpenPGP card in my cellphone Puris L5 for GnuPG
actions (password-store, SSH, ...). It mostly takes some 8-9 seconds
until the PIN entry dialog pops up. I enabled debug log for the
gpg-agent and the scdaemon, see below, and the time is consumed
by the scdaemon waitinng for some
