keybase/gpg doesn't ask for password

Since my first issue was solved so easily and since I can't find anything on this either, I'm going to open my second one today.

Basically when I'm expecting keybase/gpg to ask for a password it doesn't; specifically with `keybase track `. However I have not experienced this issue in other situations, where I use gpg.

```
% echo "bla bla bla\nbla bla bla\nbla horse bla" > message
% gpg --clearsign message
+------------------------------------------------------------------------------------+
| Please enter the passphrase to unlock the secret key for the OpenPGP certificate: |
| "Henrik Boegh " |
| 4096-bit RSA key, ID AB100A37, |
| created 2014-05-29. |
| |
| |
| Passphrase _______________________________________________________________________ |
| |
| |
+------------------------------------------------------------------------------------+
```

That part is all good.

But if I try to track someone:

```
% keybase login
% keybase track max
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
✔ 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
Is this the max you wanted? [y/N] y
Permanently track this user, and write proof to server? [Y/n] y

You need a passphrase to unlock the secret key for
user: "Henrik Boegh "
4096-bit RSA key, ID 5D713EAEAB100A37, created 2014-05-29

```

(the `keybase login` is mostly for kicks - it shouldn't change anything as far as I know?)

GPG is 2.0.22 from FreeBSD ports:

```
% 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
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
%
```

Reproduce the issue with `keybase track ` after running `keybase login`, and compare it with `gpg --clearsign message` using the reported GnuPG 2.0.22 environment. Trace the keybase tracking flow and its passphrase interaction; done means tracking prompts for the passphrase and completes successfully.

Written by the indexing model from the issue text.