Steps to replicate the issue (include links if applicable):
- $wgSecurePollShowErrorDetail=true;
- create an encrypted poll
- wait for it to start
- vote
- wait for it to finish
- Special:SecurePoll -> Dump (XML) to download a dump
- Special:SecurePoll -> Tallies -> fill out decryption key, verification key, and pick the downloaded encrypted dump file -> Create tally
What happens?:
- "Error tallying dump file: No decryption key is configured. Cannot decrypt."
What should have happened instead?:
- successful decryption and tallying
Software version (on Special:Version page; skip for WMF-hosted wikis like Wikipedia):
Other information (browser name/version, screenshots, etc.):
- I think this is broken, per my testing just now and per Dom's comment in T403308#11162664
- Let's decide if we want to fix this, or decide it's an unused feature and remove it to reduce maintenance burden. I'm leaning towards removal.
- I think keeping it might have some security implications. The idea of an election administrator being able to upload whatever data they want and make it show up as a tally and trick scrutineers into certifying it could be problematic. If kept, may need to double check / rethink the security of this feature.
- matrix of upload types and their errors:
- encrypted XML - "Error tallying dump file: No decryption key is configured. Cannot decrypt." - this ticket
- decrypted XML - "Error tallying dump file: Error interpreting vote record, cannot produce a tally." - it's good that trying to upload unencrypted dumps produces an error, but this is not a good error message. may want to improve this error message.
- encrypted BLT - no such thing
- decrypted BLT - "The dump file is corrupt and cannot be processed." (plus some uncaught PHP warnings) - it's good that trying to upload unencrypted dumps produces an error, but this is not a good error message. may want to improve this error message, and catch/fix/suppress the PHP warnings.
