On 17/08/15 16:47, Stephan Beal wrote: > > Fossil does not shun by filename, but my hash value, so you'll need to > find all hashes of all versions of those files and shun those. I counted 71 versions of the most frequently changed of those files.... a lot easier to recreate. > It is likely far simpler to recreate your repo without the compromised > data (and count it as a "lesson learned" for future repos). It was my first or second fossil repo. Lesson definitely learned. > > That said, i have never used shunning, and it is possible (not sure!) > that shunning the first version of a file will affect (shun) following > versions, as they derive from it and it's conceptually impossible to > derive from something which is no longer in the repository. Perhaps > someone who's better-versed in shunning can enlighten us on that. If anyone can confirm either way it would help a lot - at least I would know the worst.
I also think it needs to be clearly documented on the wiki page - someone could easily leak secrets by getting this wrong. > > -- > ----- stephan beal > http://wanderinghorse.net/home/stephan/ > http://gplus.to/sgbeal > "Freedom is sloppy. But since tyranny's the only guaranteed byproduct > of those who insist on a perfect world, freedom will have to do." -- > Bigby Wolf > > > _______________________________________________ > fossil-users mailing list > [email protected] > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- Graeme Pietersz http://moneyterms.co.uk/ http://pietersz.net/
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
