Page MenuHomePhabricator

GPG not executing for SecurePoll election
Closed, InvalidPublic

Description

Currently getting an error after voting for an encrypted SecurePoll election:

Welcome Jamesofur!

Failed to encrypt your vote record. Your vote has not been recorded!

Error executing GPG. Use $wgSecurePollShowErrorDetail=true; in LocalSettings.php to show more detail.

English Wikipedia Test Vote on enWiki/voteWii. I'm going to try flipping errorDetail on to troubleshoot and see if this is an issue on SecurePolls side or the server.


Version: master
Severity: normal

Details

Reference
bz73626

Event Timeline

bzimport raised the priority of this task from to Needs Triage.Nov 22 2014, 3:55 AM
bzimport set Reference to bz73626.
bzimport added a subscriber: Unknown Object (MLST).

Change 174603 had a related patch set uploaded by Jalexander:
Enable SecurePoll error detail for debugging

https://gerrit.wikimedia.org/r/174603

Change 174603 merged by jenkins-bot:
Enable SecurePoll error detail for debugging

https://gerrit.wikimedia.org/r/174603

Error executing GPG:

Command: 'gpg' --homedir '/tmp/securepoll-ec4c9077c8ce738c2669118ff9472e16308a6931' --trust-model always --batch --yes --encrypt --armor --compress-level 0 --recipient '6A2D12BB' --sign --local-user FBEC1C99 --output '/tmp/securepoll-ec4c9077c8ce738c2669118ff9472e16308a6931/output' '/tmp/securepoll-ec4c9077c8ce738c2669118ff9472e16308a6931/input' 2>&1 2>&1

Error:

gpg: can't query passphrase in batch mode

I know the keys used did not have a password... (on purpose, I think because of this) so not sure why it's trying to query passphrase.

(In reply to James Alexander from comment #4)

I know the keys used did not have a password... (on purpose, I think because
of this) so not sure why it's trying to query passphrase.

The signing key you provided *does* have a passphrase set. Apparently whatever tool you used to generate the key doesn't set "no passphrase" when you enter a zero-length passphrase, but instead actually sets the zero-length passphrase as the passphrase.

(In reply to Brad Jorsch from comment #5)

(In reply to James Alexander from comment #4)

I know the keys used did not have a password... (on purpose, I think because
of this) so not sure why it's trying to query passphrase.

The signing key you provided *does* have a passphrase set. Apparently
whatever tool you used to generate the key doesn't set "no passphrase" when
you enter a zero-length passphrase, but instead actually sets the
zero-length passphrase as the passphrase.

Great..... Will create it using cli then and retry.