Confused a bit reading this...will Fossil 2.1 default to sha3 or sha1 hardened?http://www.fossil-scm.org/index.html/doc/trunk/www/hashpolicy.wiki"A Pure SHA3 FutureAt some point in the future, years from now, after everybody has finally upgraded to Fossil 2.0 or later, the default hash policy will probably change to "sha3", or maybe even "shun-sha1". By the time that happens, you will probably already be using SHA3 on all your projects and so you are unlikely to notice."
I am asking since I would prefer to create new repo's with sha3 now using fossil 2.1. Then figure how to update/rebuild my older repo's using sha3? Is that even possible? On Thu, Mar 9, 2017 at 5:03 PM, Warren Young <war...@etr-usa.com> wrote: > On Mar 9, 2017, at 3:00 PM, Warren Young <war...@etr-usa.com> wrote: > > > > Maybe then just a notice in Admin > Configuration or similar: “Hey, you > know you’ve got a repo that Fossil 1.x can’t read, right? Just checking.” > > It could be conditional based on the repository age, disappearing after a > week or a month. And the code to generate it can be removed once Fossil > 2.x is old enough that the chances of running into Fossil 1.x is tiny. > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
