gpg does not have fallback non-graphical pinentry on macOS

amckinlay commented 6 years ago

Issue description

Without configuration, any gpg command that requires pinentry fails either explicitly or silently when invoked from a non-graphical session.

E.g., if logged in both via SSH and a local graphical session, invoking gpg through SSH appears to hang while waiting for a graphical pinentry dialogue displayed in the other session. It is not apparent to the SSH user what is happening at first, since the user might not be in physical proximity to the remote machine, or the user's graphical session is in the background (i.e., fast user switching).

E.g., if logged in only via SSH, gpg explicitly fails with error sending to agent: No pinentry.

gpg should ship with a textual pinentry fallback by default.

Steps to reproduce

(over SSH)

someones-imac:~ someone$ gpg --import secret.asc
gpg: directory '/Users/someone/.gnupg' created
gpg: keybox '/Users/someone/.gnupg/pubring.kbx' created
gpg: /Users/someone/.gnupg/trustdb.gpg: trustdb created
gpg: key 7F0E3A2FA4778096: public key "Sir Example <example@example.com>" imported
^C
gpg: signal Interrupt caught ... exiting

Technical details

system: "x86_64-darwin"
host os: Darwin 17.5.0, macOS 10.13.4
multi-user?: yes
sandbox: no
version: nix-env (Nix) 2.0.2
channels(root): "nixpkgs-18.09pre139198.9d0b6b9dfc9"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixpkgs

matthewbauer commented 6 years ago

This is a bug in pinentry-mac, but something that I would like to fix. See this comment from pinentry-mac:

https://github.com/GPGTools/pinentry-mac/blob/master/Source/main.m#L52-L82

stale[bot] commented 4 years ago

Thank you for your contributions.

This has been automatically marked as stale because it has had no activity for 180 days.

If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity.

Here are suggestions that might help resolve this more quickly:

Search for maintainers and people that previously touched the related code and @ mention them in a comment.
Ask on the NixOS Discourse.
Ask on the #nixos channel on irc.freenode.net.

NixOS / nixpkgs