On Wed, Jun 03, 2015 at 10:50:30PM -0400, Daniel Kahn Gillmor wrote: > On Wed 2015-06-03 21:44:31 -0400, brian m. carlson wrote: > > Trying to sign any file fails with the following: > > > > vauxhall no % gpg2 -b foo > > gpg: signing failed: No passphrase given > > gpg: signing failed: No passphrase given > > > > I'm prompted using pinentry-gtk2, and whether or not I select the option > > to integrate with the password manager, gpg produces the above error > > message. I've killed all existing gpg-agent and dirmngr processes, but > > it still doesn't help. I've also moved the gpg-agent.conf out of the > > way, which also doesn't help. > > What version of gpg2 are you running? which version of gnupg-agent? > I'm unable to reproduce this report with gpg2 version 2.1.4-1 (from > debian experimental) or with 2.0.28-1 from sid.
I have some more debugging information. I've rebuilt the package with debugging statements and have determined that the return value from gtk_secure_entry_get_text (around pinentry-gtk-2.c:189) is a string consisting of literally 0 characters (entry line s): want_pass: 1 s 0x7fc1a343ea28 (len 0) passphrase_ok: 1 pin 0x7fc1a343e188 (len 0) So gpg-agent is correct when it says "No passphrase given". I'm not clear on why this is happening. This is completely reproducible with a passphrase of 32 characters or more. Apparently my passphrase is unreasonably secure. Typing a passphrase of "passwordpasswordpasswordabcdefgh" (exactly 32 characters, but not my passphrase, of course) causes a failure, while leaving off the last character (resulting in 31 characters) results in a bad passphrase error. -- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187
signature.asc
Description: Digital signature
