Hi Zack Weinberg wrote: > What I think this calls for is a new cert type, which I'm going to > call "voucher". A voucher cert places a new-form signature on a > particular set of old-form certs for a revision. The data I think we > need to sign is > > revision_id || ( cert_hash || old_keypair_id || new_keypair_hash )*
All of this reminds me of the atomic cert (or super cert) thingie. Wouldn't that be the absolute perfect combination for a common flag day? Well, despite the fact that we don't have atomic certs implemented... :-( Regards Markus Wanner _______________________________________________ Monotone-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/monotone-devel
