1

I'm using a GPG Personal Access token to sign my commits. The token is not expired (I checked this first), and has all the right repo scopes to allow for a commit.

When I pull using git pull <branch> --rebase, I get prompted by a GPG Password Screen as usual. I'm usually able to input my password here and submit, but now not only can I not submit my password (by hitting Enter), the password is also not obfuscated with asterisks.

I've tried running export GPG_TTY=$(tty), this does not fix the problem. I've included a screenshot below:

Any ideas why this is happening?

screenshot of GPG GUI

3
  • 2
    What terminal or emulator do you use? Try a different one. For example, use local console, ssh client, or different terminal UI. Commented Jun 18 at 21:01
  • Check redirects. If some kind of wrapper script is used to start git, it may use the input steam for a different purpose. When input or output redirect happens, password prompts are supposed to stop working. Commented Jun 18 at 21:02
  • @Basilevs do you know specifically what program prevents the password prompt from working if input/output are redirected? Commented Jun 24 at 2:08

1 Answer 1

0

I solved the problem by switching my pinentry program to pinentry-mac . I installed pinentry-mac using homebrew and then changed my ~/.gnupg/gpg-agent.conf config to

use-standard-socket
enable-ssh-support
default-cache-ttl 600
max-cache-ttl 7200
pinentry-program /opt/homebrew/bin/pinentry-mac

I still don't know why the original problem happened. I think it might be some bug that pinentry-curses has on mac, but I have no idea how to be sure. Running pinentry-curses didn't reproduce the issue :shrug:

Sign up to request clarification or add additional context in comments.

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.