Skip to content
This repository has been archived by the owner on Dec 12, 2022. It is now read-only.

Stock install GPG doesn't recognise yubikey #19

Closed
clumbo opened this issue Nov 20, 2021 · 4 comments
Closed

Stock install GPG doesn't recognise yubikey #19

clumbo opened this issue Nov 20, 2021 · 4 comments
Labels
invalid This doesn't seem right question Further information is requested

Comments

@clumbo
Copy link

clumbo commented Nov 20, 2021

I am doing the following in the command line after installing via scoop

gpg --card-status

This results in the following

gpg: can't connect to the gpg-agent: IPC connect call failed
gpg: OpenPGP card not available: No agent running
@rupor-github
Copy link
Owner

rupor-github commented Nov 20, 2021

I am sorry, this is not a GnuPG support forum and not a proper place to ask about basic GnuPG operations. Documentation clearly states that:

image

You need to go to https://gnupg.org/documentation/index.html where proper support channels are listed.

@rupor-github rupor-github added invalid This doesn't seem right question Further information is requested labels Nov 20, 2021
@clumbo
Copy link
Author

clumbo commented Nov 21, 2021

I setup the smartcard it was working.

The trick is not to use the bundled portable version when installing scoop.

With the portable version > 2.3.1 it will not work due to a bug that references a missing gnupg folder> 2.3.1 if you create the gnupg folder next to home you can get the agent to connect via command line but it will not work with win-gpg-agent.

Posting this in case someone else has the problem in the future

ScoopInstaller/Main#2599

thanks

@rupor-github
Copy link
Owner

rupor-github commented Nov 21, 2021

Assuming by bundled you mead scoop install of gnupg (as oposite to any other gnupg installation) I believe you could still use win-gpg-agent with work around suggested in the scoop ticket by changing agent-gui configuration as it has separate config value to point to a socket directory. I also of opinion that change in 2.3.2 is strange and unnecessary, but do not think it is going to be reverted.

@clumbo
Copy link
Author

clumbo commented Nov 21, 2021

Thanks for the reply,

Yes I did try this and it still didn't work

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
invalid This doesn't seem right question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants