CoC signing for 1.1 fails with 'Bad Signature'

Bug #833194 reported by Zack
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
High
Unassigned

Bug Description

I tried using --clearsign to sign the v1.1 CoC with a 3072 bit key using both versions 1.4 and 2.0.18. I receive two error dialogs. One reads "(7, 8, u'Bad signature')" and the other "There is 1 error." For me, this is reproduceable 100% of the time. I have verified that I am using the correct and validated key.

tags: added: codeofconduct
Brad Crittenden (bac)
Changed in launchpad:
status: New → Triaged
importance: Undecided → High
Revision history for this message
Robert Collins (lifeless) wrote :

please attach your signed coc to this bug so we can manually verify whats going on.

Changed in launchpad:
status: Triaged → Incomplete
Revision history for this message
Zack (zack-gilburd) wrote :

I downloaded the CoC once using Chrome and once using wget with the same outcome.

Best,

Zack

[19:54:23 zgilburd ztp ~] $ gpg2 --verify Downloads/UbuntuCodeofConduct-1.1.txt.asc
gpg: Signature made Wed 24 Aug 2011 09:54:30 AM MST using RSA key ID 1A366879
gpg: Good signature from "Zack Gilburd <REDACTED EMAIL>"

et al key UIDs.

Zack (zack-gilburd)
Changed in launchpad:
status: Incomplete → Confirmed
Revision history for this message
Robert Collins (lifeless) wrote :

ack - verifies fine for me(natty host), keys are on the public keyring.

Changed in launchpad:
status: Confirmed → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.