yadm encrypt: inappropriate ioctl for device

[thelocehiliosan]

yadm encrypt: inappropriate ioctl for device

[TheLocehiliosan]

@sooheon Not sure if you are still having this issue, but it seems that you need to have GPG_TTY exported in your shell for GNUPG to work properly.

Solution:

export GPG_TTY=$(tty)

https://twitter.com/xianpants/status/822532532226953217

Hat-tip to @christiannelson

Cheers

[TheLocehiliosan]

I suspect this is an issue with your general gpg configuration. (possibly gpg-agent).

Are you able to encrypt and decrypt a simple string like this:

    echo testing | gpg -c | gpg

[sooheon]

You're right, the above fails with the same message. gpg-agent says "no gpg-agent running in this session". Will read through the GPG how-to, feel free to close if you think it's out of scope.

[TheLocehiliosan]

@sooheon I'm closing this issue, but feel free to reach out to me if you're still having this problem. Maybe I can help figure it out.

[TheLocehiliosan]

Opening this issue to track adding the info to the FAQ

[faelin]

export GPG_TTY=$(tty)

This did not solve the problem for me! In fact, it made it worse because, after running that export, GPG would just hang until I used an escape-sequence to terminate the shell.

Instead, I was able to resolve the issue using this suggestion from stack overflow (running on Mac OS 10.14.6, GPG v2.2.27 managed by Homebrew):

add this to ~/.gnupg/gpg.conf:

use-agent 
pinentry-mode loopback

Then add this to ~/.gnupg/gpg-agent.conf

allow-loopback-pinentry

Then restart the agent with echo RELOADAGENT | gpg-connect-agent.

For convenience, here is a copy/paste block (will only add the appropriate lines if they aren't already in your config):

grep -qsxF "pinentry-mode loopback" ~/.gnupg/gpg.conf || echo "use-agent\npinentry-mode loopback" >> ~/.gnupg/gpg.conf
grep -qsxF "allow-loopback-pinentry" ~/.gnupg/gpg-agent.conf || echo "allow-loopback-pinentry" >> ~/.gnupg/gpg-agent.conf
echo RELOADAGENT | gpg-connect-agent

[duhd1993]

@faelin This workaround will cause other commands depending on pinentry fail. Just read some issues on homebrew, the best way seems to be using pinentry-mac instead of pinentry on a mac machine.

brew install pinentry-mac

and add

pinentry-program /usr/local/bin/pinentry-mac

to ~/.gnupg/gpg-agent.conf

[jcburley]

@faelin This workaround will cause other commands depending on pinentry fail. Just read some issues on homebrew, the best way seems to be using pinentry-mac instead of pinentry on a mac machine.

brew install pinentry-mac

and add

pinentry-program /usr/local/bin/pinentry-mac

to ~/.gnupg/gpg-agent.conf

Doesn't work for me; I get the pinentry window, but all typing continues to go into the shell, even after clicking in the entry field. (Should there be more than just that one line in gpg-agent.conf? Was empty on my Mac.)