You are not logged in.
Pages: 1
I encountered werid bug with gnupg couple of days ago. After update it just refused to sign anything with most generic timeout error. I checked gpg.conf, gpg-agent.conf, I reinstalled it. Nothing worked.
I found solution which is so bizzare that I thought I would share it with you.
echo "test" | gpg --clearsign - timeout error
I aliased gpg="gpg2"
echo "test" | gpg --clearsign - signs normally
I removed alias - signs normally
Can someone explain this? I am dumbfounded right now, especially because gpg2 is just symbolic link to gpg
Offline
Followup, I have suspicion that some install script made alias to gpg command. I admit I was too lazy to read every user script so it's most probable for me. If anyone have weird problems with gpg, better check if command is not aliased with some bad parameters. Even if shell history says you certainly did not alias gpg.
Offline
Pages: 1