Keybase client hangs waiting on key entry

[tel]

Here's a log

$ keybase track max                                                  [18:14:11]
info: ...checking identity proofs
✔ public key fingerprint: 8EFB E2E4 DD56 B352 7363 4E8F 6052 B2AD 31A6 631C
✔ "maxtaco" on twitter: https://twitter.com/maxtaco/status/433688676975927296
✔ "maxtaco" on github: https://gist.github.com/8847250
✔ "maxtaco" on reddit: https://www.reddit.com/r/KeybaseProofs/comments/2clf9c/my_keybase_proof_redditmaxtaco_keybasemax/
✔ "maxtaco" on coinbase: https://coinbase.com/maxtaco/public-key
✔ "maxtaco" on hackernews: https://news.ycombinator.com/user?id=maxtaco
✔ admin of keybase.io via HTTPS: https://keybase.io/.well-known/keybase.txt
✔ admin of oneshallpass.com via HTTPS: https://oneshallpass.com/.well-known/keybase.txt
✔ admin of the DNS zone for oneshallpass.com
✔ admin of the DNS zone for maxk.org
✔ admin of the DNS zone for nutflex.com
Is this the max you wanted? [y/N] y
Permanently track this user, and write proof to server? [Y/n]

You need a passphrase to unlock the secret key for
user: "keybase.io/tel <tel@keybase.io>"
2048-bit RSA key, ID _, created 2014-09-23
         (subkey on main key ID _)

and then it hangs indefinitely. This happens for most keybase requests.

Installed via npm and brew install gpg2

$ keybase version                                                    [18:17:23]
keybase (keybase.io CLI) v0.7.1
- node.js v0.10.28
- gpg (GnuPG) 2.0.26
- libgcrypt 1.6.2
Identifies as: 'keybase.io node.js client v0.7.1 darwin'

[ghost]

Normally pinentry should open at that time to ask for your passphrase. Is this the case?

[tel]

Ah, I was expecting a command line interface. I now note that the active process (as recorded by iTerm's menu bar name) changes to keybase track max (pinentry-curses) but no further action occurs.

[ghost]

That is strange, curses is CLI... With curses it shouldn't matter, but I don't trust pinentry since tried some scripting with it. What happens, when you first remove the DISPLAY-variable and then try tracking?

unset DISPLAY
kaybase track max

[chrissearle]

I'm seeing the same. Unsetting DISPLAY doesn't help. In fact - when I get to the hanging point - I can type - but it appears in the terminal so we're not talking to the CLI pinentry (or pinentry-curses - the titlebar of the shell does update to this).

ps shows a pinentry process running.

[chrissearle]

The GPG_TTY suggestion from https://github.com/keybase/keybase-issues/issues/110 does however seem to work.

[tel]

110 worked for me as well