[Monotone-devel] Re: Rosterify and certificate keys

[Lapo Luchini]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

address@hidden wrote:
> That would change the revision IDs again, woudn't it?
That's for sure: different hash algorithm, different hash value.
> Or we could recognise both sets of revision IDs -- the old ones for
> old revisions, the new ones for new ones.  Perhaps some syntactic
> marker could distinguish them.
Their length will be sufficient to distinguish them, as the "next hash
of choice" will probably be at least 256 bit in length, and more than
160 bit for sure, as those are beginning to be "too few bits" today
already, even not counting the theoretical attacks that reduce them
further.

    Lapo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQIcBAEBAgAGBQJEPX7lAAoJELBiMTth2oCDNJwP/1VgCzpTL9ZtvRaz9oLdThHK
cf+bXUUAZ+a6DKg4//iHwDZYPGFkazN/z/gxFzhNZME6lNSrlh3GJdGjXJUBQqdk
LO0knG41s1Hwf4MkK1ocpKA3M4rW52EoVu4u3633IOEhp+pA5zL5u5GySK+qe9MW
93sNZX6Mf5yNcu/s7jNsd3J4w+OLfDFNIvePfgm84LGvAVaOB4oaXAyDuOIQK2bJ
7Tv3IDX1dDHaITm46PbMB1PGAal5CnbP5RibnOOs/CqA2FPU2OtBiej73RyVsO/X
hrupf3VfCH1KUktzKcG7JjE/gHxc8n+W2wiNql85SeKFUnkkhm6HgJRmTB5BSG/s
OMLIKLbchkx7ZTjbq/EFZY9Dbnxn9JKRhsvGBPXf3C/2/kUdHiDDEzOFUBuP6lUk
Zl++AJX+Pe6GZe4EtbpSR5L3kZbctK/VTZJd1UKrorBUesnxexcHn0oPvZ9Nm7g2
u4eoz1EdmBDQ9BIg6pJzD4L4G1agNl3136eJXiaUWNyWWXujbnkAGdjFyCQK0MUD
rkJwtOHatqo5AOrjTbUYF5TOJsnkTZfW/Q1hr/ikpR4rO3Kkpit4g9E15XHcFJBa
VrI7l7NYsTL9Aifpa5jN2jiqaJ+D2wddq7tlwdulDciCOIjRvCc5x0wsGyKT0P86
WrzxGMaBmXXZhDSoYh04
=PVqx
-----END PGP SIGNATURE-----