Ubuntu
seahorse package

seahorse permits to sign public key even if already signed

Bug #328771 reported by marco.pallotta on 2009-02-12

This bug report is a duplicate of: Bug #304551: seahorse: signing should be disabled when key is already signed. Edit Remove

Affects		Status	Importance	Assigned to	Milestone
	seahorse (Ubuntu)	Incomplete	Low	Ubuntu Desktop Bugs

Bug Description

Seahorse permits to sign public key even if it is already signed.
If you open the properties of your own personal key and you go to "name and signes" tab you will see all the name/emails associated to your key with the ability to sign them. The issue is that you can sign it even if it is already signed. Moreover the "sign ID" is not showed near the key in the key list (always in the same tab).

Revision history for this message

Sebastien Bacher (seb128) wrote on 2009-02-12:

thank you for your bug report, how is that a bug? there is no reason you couldn't sign a key again using different settings

Changed in seahorse:
assignee:	nobody → desktop-bugs
importance:	Undecided → Low
status:	New → Incomplete

Revision history for this message

marco.pallotta (marco-pallotta) wrote on 2009-02-13:

Well, once a key is signed you souldn't have the ability to sign it again, is misleading.
If you want to revoke a sign you should only press the button "revoke a signature".

For seahorse the only valid reason that you could have to sign a key again is to change some parameter as "how carefully have you checked this key? How other will see this signature"?
But why not to place these options outside the signature window?
Why have I to select how carefully have I checked the key? If I sign a key it means that I have verified the ownership of that key (I think the options "not at all" "casually" "very carefully" are only a personal memo that don't affect the signing process).

Revision history for this message

marco.pallotta (marco-pallotta) wrote on 2009-02-13:

Sebastien, I think this bug is a duplicate of #304551 (already opened by me:-)). This issue if related to personal key while #304551 is related to other public keys. The bug is the same for me.
Excuse me but I forgot that I already posted a similar issue.