In message <[EMAIL PROTECTED]> on Tue, 11 Apr 2006 10:14:48 +0200, Wim Oudshoorn <[EMAIL PROTECTED]> said:
woudshoo> For me the ideal situation would be that during the woudshoo> conversion all the certificates that contain a string of 40 woudshoo> hex digits that equal an existing hash should be replaced woudshoo> with the new, post upgrading hash. Hmm, interesting thought... woudshoo> Also, if the private key is know, it should try to preserve woudshoo> the private key, otherwise fallback to a default private key woudshoo> when resigning the certificates. You know, if someone else rebuilds a database, I would be quite worried if anything was signed with my key. To me, that's a breach of security, and would lead to an immediate revokation of my key, if that was at all possible. Cheers, Richard ----- Please consider sponsoring my work on free software. See http://www.free.lp.se/sponsoring.html for details. -- Richard Levitte [EMAIL PROTECTED] http://richard.levitte.org/ "When I became a man I put away childish things, including the fear of childishness and the desire to be very grown up." -- C.S. Lewis _______________________________________________ Monotone-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/monotone-devel
