[Monotone-devel] cause of bad cert signatures and how to prevent them?

[Marcel van der Boom]

A monotone db got, somehow, certs on a revision which had bad  
signatures. This happened during a learning session where a person  
had probably mixed several keys.

After him pushing, which apparently went well, the messages with  
"warning: ignoring bad signature on...." appeared.

How come this revision was accepted with a bad signature?
More important, how can this be prevented from ever happening again?

I could not find another way to repair the database than:

1. mtn db rebuild (this makes the invalid certs disappear, leading to  
a missing cert error)
2. mtn cert <ID> author <VALUE>
3. <.. repeat 2. for date, changelog and branch >

This repairs the database, but the id's have obviously all changed  
now, so clients would need to re-create their (parts in their) local  
databases, right?
Is there a better procedure for handling this?

thx,

marcel

--
Marcel van der Boom
HS-Development BV               --   http://www.hsdev.com
So! webapplicatie framework  --   http://make-it-so.info

smime.p7s
Description: S/MIME cryptographic signature