Thanks for the detailed replies.
I will make the leap to v2.1 shortly.
Post by s***@gmail.comI am asking since I would prefer to create new repo's with sha3 now
using fossil 2.1.
Thatâs what you will get by default. You have to go out of your way with
Fossil 2.1+ to get a new SHA-1 based repo.
Post by s***@gmail.comThen figure how to update/rebuild my older repo's using sha3?
Upgrade to Fossil 2.1+, then say âfossil set hash-policy sha3â in each
repo where you want new content to be hashed with SHA-3.
If all your local repos either need to be converted or are clones of
remote repos that will soon be shipping SHA-3 hashed artifacts (e.g. Fossil
itself), you can say âfossil all set hash-policy sha3â instead, upgrading
them all at once.
Fossil 2.1+ will purposely not rewrite all the old artifacts with SHA-3
hashes because that would break any intra-repository links, such as between
checkin comments and tickets, wiki articles and mentioned checkins, etc.
Only new content gets hashed with SHA-3 once its hash policy has been
switched to SHA-3, whether explicitly or implicitly.
See the âfirewallâ thread if youâre worried about the consequences of
leaving the old content hashed with SHA-1. (Executive summary: relax.)
Maybe someone will write a tool that rebuilds an old repo with all-SHA-3
for those who arenât worried about the intra-repository links.
_______________________________________________
fossil-users mailing list
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users