In case of "command get_passphrase failed: Inappropriate ioctl for device"

pstadler / keybase-gpg-github

Step-by-step guide on how to create a GPG key on keybase.io, adding it to a local GPG setup and using it with Git and GitHub.

2.64k stars 182 forks source link

In case of "command get_passphrase failed: Inappropriate ioctl for device" #11

Closed 0xjjpa closed 7 years ago

0xjjpa commented 8 years ago

For some reason I had to setup the GPG TTY variable on my bash when I tried to sign my commit (i.e. -S flag) because of passphrase, which is new to me since I usually have the passphrase prompt within my terminal, so who knows, might be a new GPG version.

Anyway, fixed it with:

GPG_TTY=$(tty)
export GPG_TTY

Might be worth adding it to the README.md under common issues and/or what not.

benbieler commented 7 years ago

Jup. Just had the same Problem. Fixed it as mentioned here. Thx

pstadler commented 7 years ago

Care to open a pull request? 🍻

0xjjpa commented 7 years ago

@pstadler #13

johnmathews commented 7 years ago

I have this problem also. Thanks for the fix.

rayrutjes commented 7 years ago

Still accurate ;) Is there an easy way to remember the passphrase on OSX?

roln commented 7 years ago

thanks a lot ! Fixed it

kavdev commented 7 years ago

I ran into this when attempting to use gpg2 (with gpg-agent) when signing commits in git on WSL bash. Thanks for the solution.

Git's error output:

gpg: signing failed: Inappropriate ioctl for device
gpg: signing failed: Inappropriate ioctl for device
error: gpg failed to sign the data
fatal: failed to write commit object

chenxiaojie commented 7 years ago

thks

zw201913 commented 7 years ago

thanks a lot ! Fixed it

jgillich commented 6 years ago

Also getting this in WSL after every system restart. Does anyone know what could be causing it?