Command line `prove` command doesn't allow unlocking private key

[mountainpenguin]

I've just installed keybase and I'm trying it out, I've had a browse through the issues, but this doesn't seem to be reported. Sorry if it is.

I've generated a key, and pushed the public key (but not the private key) to the server.

When I try on the command-line keybase prove github, it doesn't allow input of the passphrase to unlock the secret key

~ keybase prove github
Your username on GitHub: mountainpenguin

You need a passphrase to unlock the secret key for
user: "keybase.io/mountainpenguin <mountainpenguin@keybase.io>"
4096-bit RSA key, ID 3C02E***********, created 2014-04-10
         (subkey on main key ID D75433**********)

Someone suggested that it may be trying to open a dialog, however this is running on my server so it will not be able to do so (at least not visibly over SSH).

~ keybase version
keybase (keybase.io CLI) v0.2.19
- node.js v0.10.21
- gpg (GnuPG) 2.0.22
- libgcrypt 1.5.3
Identifies as: 'keybase.io node.js client v0.2.19 linux'

~ node --version
v0.10.21

~ gpg --version
gpg (GnuPG) 2.0.22
libgcrypt 1.5.3
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Home: ~/.gnupg
Supported algorithms:
Pubkey: RSA, ELG, DSA, ?, ?
Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
        CAMELLIA128, CAMELLIA192, CAMELLIA256
Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2

Running on Gentoo Linux x86_64, kernel version 3.8.13,

[mountainpenguin]

Worked this out, it was an issue with GNUPG rather than keybase

export GPG_TTY=tty``

Allows GNUPG to open a dialog to enter the passphrase

[bobberb]

If I may point to this issue again:

Arch Linux x64, keybase 0.4.7, gpg 2.0.23, nodejs v.0.10.29

I run every command over SSH and gnuscreen. I cannot get pinentry to open through keybase. If I drop out of screen to just the vanilla terminal after SSH login, this follows when 'keybase decrypt' is run with the "export GPG_TTY='tty' command above:

warn: gpg: no valid OpenPGP data found. warn: [GNUPG:] NODATA 1 warn: [GNUPG:] NODATA 2 warn: gpg: decrypt_message failed: Unknown system error error: gpg exited with code 2

gpg --list-secret-keys runs just fine.

[maxtaco]

Seems like you're having a different problem. Can you paste the output of keybase -d <whatever your command was> ? Thanks

[bobberb]

... debug: '-a', debug: '--keyid-format', debug: 'long' ], debug: quiet: true }

You need a passphrase to unlock the secret key for user: "Joshua Brikman (10th Nov. 2013) josh@half-done.org" 8192-bit RSA key, ID 386F456CE82CEB12, created 2013-11-11

warn: pinentry-curses: no LC_CTYPE known - assuming UTF-8 warn: pinentry-curses: no LC_CTYPE known - assuming UTF-8 warn: pinentry-curses: no LC_CTYPE known - assuming UTF-8 warn: pinentry-curses: no LC_CTYPE known - assuming UTF-8 warn: pinentry-curses: no LC_CTYPE known - assuming UTF-8 warn: pinentry-curses: Assuan processing failed: write error warn: gpg-agent[8568]: command get_passphrase failed: Line passed to IPC too long warn: gpg: problem with the agent: Line passed to IPC too long warn: gpg: skipped "386F456CE82CEB12": Operation cancelled warn: gpg: signing failed: Operation cancelled error: gpg exited with code 2

On Fri, Jun 20, 2014 at 8:41 AM, Maxwell Krohn notifications@github.com wrote:

Seems like you're having a different problem. Can you paste the output of keybase -d ? Thanks

— Reply to this email directly or view it on GitHub https://github.com/keybase/keybase-issues/issues/562#issuecomment-46673796 .