gpg: signing failed: Inappropriate ioctl for device

[yveoch]

When trying to use the bash+curl verifying method on a server, this cryptic error message might happen:

gpg: signing failed: Inappropriate ioctl for device

Since this is a fatal error and also quite difficult to debug, maybe the fix could be put somewhere (in the provided command line?):

export GPG_TTY=$(tty)

source

[diego898]

I cannot tell you how grateful I am to you!

[cfig]

@dryvenn You are a life saver! THX!

[dminca]

You're a saviour! Helped me on Fedora.

[danduk82]

really thanks a lot

[boltzjf]

Wow, you are so cool, helped me a lot!

Thank you so so much!!!

[kenvac]

Thanks a tonne man!!. Helped me on debian 9.

[Turini]

helped me a lot also! thank you

[TheOpenDevProject]

Cheers!.

[tejasmob]

You're truly rockstar man! 🥇 Thanks!

[ivy-dong]

Amazing really thanks a lot

[abhi-jha]

Oh wow. And I was pulling my hair that my key has expired which it definitely didn't. I don't know why I was thinking its 2019 for some reason. Thank you.

[netsafe]

works inside a docker container Deian stretch both host and container

[hlzhang]

Sadly, no tty on travis-ci or appveyor. GPG 2.1.11 comes with ubuntu 16.04 throw out a invalid error if I add 'pinentry-mode loopback' into ~/.gnupg/gpg.conf. Various versions of gpg wasted lot of my time and I think it is a piece of shit, they don't test it on different environments?

[jamesdbloom]

This doesn't work for me because when I add that setting GPG doesn't sign some artefacts properly anymore.

[netsafe]

@chshawkn Travis-CI - in my opinion - is a very questionable CI solution... Call me classy, but I'm still using Jenkins and it never ever failed me regardless of the task and environment I used. With Windows slave all the problems were gone when I used WinSSHD - just write your scripts properly and have fun

[hlzhang]

@netsafe Thanks for your advice. I use Gitlab CI/CD and Jenkins on private projects. Travis-CI is for public repositories.

I've solved the GPG issues on Gitlab CI/CD, Travis-CI and AppVeyor, one script works on all CI platforms.

see: https://github.com/ci-and-cd/maven-build/blob/develop/src/main/ci-script/lib_ci.sh#L702

[rootVIII]

worked for me on Ubuntu 18... thanks

[svenluijten]

I cannot thank you enough! ❤️ Hours were lost debugging this 🙈

[maxtaco]

Wow, can't believe how many thumbs this issue has. I had a half a mind to update the website to fill in GPG_TTY=$(tty) as suggested in this issue, but that only works in bash, and the current command line seems to work in tcsh too. Looks like we need a flow here to: (1) have users select their shell; and (2) to give you the right command to setenv given the shell. I guess alternatively we can always run bash -c 'lots of commands | other commands', but we'd need another level of quoting.

[josefigueroa-nedap]

It also works on OSX using zsh. Thanks!

[dmjio]

@dryvenn nice, works on nixos.

[dadiyang]

It works! Thank you so much!

[jamalkaksouri]

@dryvenn thank you, works on ubuntu subsystem.

zsh support

[teddybear]

Thank you!

[stevenchen3]

Kudos!!!! This saves me a lot of time. Appreciated.

[ghost]

Thank you so much!

I had this problem where I had my user.signingKey set to the correct value in Git on Ubuntu 18.04 after following this tutorial, but I was still unable to sign commits. Every time I tried, I got this error:

error: gpg failed to sign the data
fatal: failed to write commit object

This fixed that right up. Thanks again!

[fgvenegas]

You saved my life and my semester :')

[Bryan-Cee]

Thanks a lot @dryvenn 👍

[akhilesharora]

👍Nice find!

[MahikanthNag]

Couldn't thank you enough!! Scratching my head since 2 hours trying to understand what is happening!