summaryrefslogtreecommitdiff
path: root/doc/bugs/Possible_data-loss_if_WORM_keys_do_not_encode_relative_paths/comment_3_bda1e0d3569a6becf374d0e820219469._comment
blob: 54fe869c555613d2415c61bb92d1f1325867fd74 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
[[!comment format=mdwn
 username="zardoz"
 ip="78.48.163.229"
 subject="comment 3"
 date="2014-08-16T13:58:28Z"
 content="""
One scenario where the above guarantee would be violated is when one
moves a new file of identical size, basename, and mtime, into a path
where a key-colliding file has been kept before. Still, I’d consider
this a scenario one could reasonably control for (especially in the
archive usecase); plus, even without manual control such a
move-induced collision would be much more unlikely than a collision of
basenames only.

"""]]