CoC signing for 1.1 fails with 'Bad Signature'
Bug #833194 reported by
Zack
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 |
Changed in launchpad: | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in launchpad: | |
status: | Incomplete → Confirmed |
To post a comment you must log in.
please attach your signed coc to this bug so we can manually verify whats going on.