4 ms·
I fixed most of my problem with the following command after plugging the key (Win and Linux): `gpg --card-status` then wait for key status That command starts
by alibert 9y ago
I fixed most of my problem with the following command after plugging the key (Win and Linux):
`gpg --card-status` then wait for key status
That command starts everything related to GPG/SSH (daemon/agent).
- drdaeman 9y agoThis is essentially a diagnostic command, not really a fix ;) For me, when gpg-agent gets "stuck", this command just fails. I forgot the exact message but it tells me that it can't find the device. `gpg-connect-agent KILLAGENT /bye` and then `gpg --card-status` (will automatically start a new gpg-agent daemon in the background) does the trick for me, but it's the first command that matters. (Could be just `killall gpg-agent`, I guess) Oh, I think on Windows, once I had to restart the Smartcards service, as restarting the agent haven't helped. Don't know what it was - I've experimented with OpenSC around that time so could be just about anything.