On 2021-03-17 at 21:16 +0100, Andreas K. Huettel wrote: > > OK now it's getting very strange. > > On a second PC with the same reader hardware model, the same gpg > version, and > the same chipcard, things work perfectly fine. > > Could this be a hardware defect (i.e., reader was too long in the > sun)?
I don't think so. You report that the first program which uses the card (either gpg or ssh) "keeps" it, and the other is unable to (btw, would e.g. a second sign work?). This looks like the first one locks use of the card. May gpg and ssh be launchihng separete scdaemon instances? Does it help if you use --card-timeout on scdaemon config? _______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users