-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
Thank you for your continued follow-up. I executed commands. Here are
the results:
C:\>gpgconf -V
* GnuPG 2.4.5 (cbff323b3)
MingW32
Windows 10.0 build 19045
* Libgcrypt 1.10.3 (aa161086)
version:1.10.3:10a03:1.48:13000:
cc:10:gcc:10-win32
On Tue, Apr 09, 2024 at 12:11:31PM +0200, Werner Koch wrote:
> By default we are not using PC/SC on Linux but direct access to the
> reader via USB. Now if pcscd is already running and has access to the
> reader scdaemon won't be able to access the reader via USB.
>
> 2.2 falls back to PC/SC if
Hi!
On Tue, 9 Apr 2024 12:21, Moses said:
> C:\>gpgconf -L
which merely shows that you installed the software on d:\software and
kep the user data at the usual C: directories. I see nothing strange.
To recap your problem was:
c:\> gpg --import private-keys.asc
gpg: enabled compatibility
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Returns as follows:
(just blacked out the username...)
C:\>gpgconf -L
sysconfdir:C%3a\ProgramData\GNU\etc\gnupg
bindir:D%3a\software\GNU\Gpg4win\..\GnuPG\bin
libexecdir:D%3a\software\GNU\Gpg4win\..\GnuPG\bin
Running "gpg --card-status" with a configured Yubikey plugged in on an x86_64
Linux machine just gives me these errors when running 2.4.5:
gpg: selecting card failed: No such device
gpg: OpenPGP card not available: No such device
However, leaving everything else the same and just running 2.2.42
On Mon, 8 Apr 2024 21:50, Dan Fandrich said:
> Running "echo SERIALNO | scd/scdaemon --server" is enough. I've tried both
> pcsc-lite 1.9.9 and 2.0.3 without a difference. I'm not sure how to drill
By default we are not using PC/SC on Linux but direct access to the
reader via USB. Now if
On Mon, 8 Apr 2024 11:42, Moses said:
> C:\> gpg-connect-agent -v
>> getinfo version
> D 2.4.5
Okay, that works.
>> gpgconf -L
> ERR 67109139 Unknown IPC command
Please enter this on the command line not at the gpg-connect-agent
prompt.
Salam-Shalom,
Werner
--
The pioneers of a
