-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gpg: signing failed: Inappropriate ioctl for device #2798
Comments
I cannot tell you how grateful I am to you! |
@dryvenn You are a life saver! THX! |
You're a saviour! Helped me on Fedora. |
really thanks a lot |
Wow, you are so cool, helped me a lot! Thank you so so much!!! |
Thanks a tonne man!!. Helped me on debian 9. |
helped me a lot also! thank you |
GPG_TTY needs to be set to the value in tty ($(tty)) in order for GPG to work properly with mutt. keybase/keybase-issues#2798
Cheers!. |
You're truly rockstar man! 🥇 |
Amazing |
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. |
works inside a docker container Deian stretch both host and container |
Sadly, no tty on travis-ci or appveyor. |
This doesn't work for me because when I add that setting GPG doesn't sign some artefacts properly anymore. |
@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 |
@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 |
worked for me on Ubuntu 18... thanks |
I cannot thank you enough! ❤️ Hours were lost debugging this 🙈 |
Wow, can't believe how many thumbs this issue has. I had a half a mind to update the website to fill in |
It also works on OSX using |
@dryvenn nice, works on nixos. |
It works! Thank you so much! |
@dryvenn thank you, works on ubuntu subsystem.
|
Thank you! |
Kudos!!!! This saves me a lot of time. Appreciated. |
Thank you so much! I had this problem where I had my
This fixed that right up. Thanks again! |
Thanks!!! You have helped me with this solution in WSL 2 |
imagine |
@Skeeve more like «A Lb[ii$5Cƹ4iU0*Zp~oʰ_x%i |
It's a beautiful thing when the top result is the fix. |
Over six years later and this helped me out, thank you yveoch! |
I found another way to sovle it. ~/.gnupg/gpg.conf ~/.gnupg/gpg-agent.conf Resource: https://d.sb/2016/11/gpg-inappropriate-ioctl-for-device-errors |
cant express how grateful i am to encounter this post, thank you very much |
Obrigado 🫡💘 |
thank you very much |
The GOAT |
Thank you so much! Saved my ass. |
keybase/keybase-issues#2798 Signed-off-by: Mike Ball <mikedball@gmail.com>
I really wasn't expecting that this would solve my problem, thanks! |
I think I've already gotten this error message like 12938901832 times before. I keep debugging it for like 3 hours. And always this issue post saves me. You have saved our lives. We are eternally grateful. |
This issue post has gained a meta level of helpfulness, an evergreen of uplift: Thanks everyone! <3 |
Thank you so much...Life Saver |
my saviour! :D |
Suddenly, this doesn't seem to be working. I'm trying to get a copy of my GPG keys to my new laptop with:
I've added the magic words to .profile, .bashrc, and .bash_profile in both user@server and locally, including restarting the terminal. Not sure what's going on. |
Man... you are absolutely an amazing savior. Awesome. Thank you so much! |
Thanks @yveoch you save mee.. |
Thanks @yveoch worked for me |
2024 and still kicking! Thank you ❤️ |
When trying to use the bash+curl verifying method on a server, this cryptic error message might happen:
Since this is a fatal error and also quite difficult to debug, maybe the fix could be put somewhere (in the provided command line?):
source
The text was updated successfully, but these errors were encountered: