Skip to content

Instantly share code, notes, and snippets.

@mjul

mjul/GPG-FIX.md

Created November 18, 2022 19:02
Show Gist options
  • Star 1 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save mjul/56aa1494f65b7f9f38f1aba5b143f579 to your computer and use it in GitHub Desktop.
Save mjul/56aa1494f65b7f9f38f1aba5b143f579 to your computer and use it in GitHub Desktop.
Download ZIP
gpg: signing failed: Inappropriate ioctl for device
Raw
GPG-FIX.md

Fixing GPG "Inappropriate ioctl for device" errors

6th November 2016 Linux 24 Comments https://d.sb/B5N 

    Error: gpg: using "D5673F3E" as default secret key for signing 
    Error: gpg: signing failed: Inappropriate ioctl for device 
    Error: gpg: [stdin]: sign+encrypt failed: Inappropriate ioctl for device

It turns out this error is due to changes in GnuPG 2.1, which only recently landed in Debian Testing. The error occurs because GnuPG 2.1 by default ignores passphrases passed in via environment variables or stdin, and is trying to show a pinentry prompt. "Inappropriate ioctl for device" is thrown because the Backupninja script is not running through a TTY, so there's no way to actually render the prompt.

To solve the problem, you need to enable loopback pinentry mode. Add this to ~/.gnupg/gpg.conf:

    use-agent 
    pinentry-mode loopback

And add this to ~/.gnupg/gpg-agent.conf, creating the file if it doesn't already exist:

    allow-loopback-pinentry

Then restart the agent with echo RELOADAGENT | gpg-connect-agent and you should be good to go!

Source: https://d.sb/2016/11/gpg-inappropriate-ioctl-for-device-errors

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment