How we might best mitigate this vulnerability is better discussed in a more private mailing list.
btw. The SHA1 collision was described in episode 600 of the weekly Security Now! podcast that was broadcast on Tuesday last week. It can be seen on twit.tv Best regards, David -- View this message in context: http://sword-dev.350566.n4.nabble.com/Subversion-tp4656825p4656827.html Sent from the SWORD Dev mailing list archive at Nabble.com. _______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page