On 2017-04-11 10:02, Mark Janssen wrote:
That's not a security hole at all. Once a file was added, ignoring it
will not remove past version from the repository. History in fossil is
immutable. If you inadvertently added a file which shouldn't be there
you should shun it instead.
The way I understand shunning works is that it won't add that particular
version of the file anymore.
https://www.fossil-scm.org/xfer/doc/trunk/www/shunning.wiki
"Every Fossil repository maintains a list of the hash names of "shunned"
artifacts. Fossil will refuse to push or pull any shunned artifact.
Furthermore, all shunned artifacts (but not the shunning list itself)
are removed from the repository whenever the repository is reconstructed
using the "rebuild" command."
A hash changes as soon as the file's content changes, or am I wrong?
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
