diff options
| author |  zardoz <zardoz@web> | 2014-08-16 13:58:28 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2014-08-16 13:58:28 +0000 |
| commit | 4778cf220a8fe41a93a6e7f7b2dc37709fc57dff (patch) | |
| tree | 850c16bd6c4fb9bf5c340f2d8bb15ca9346926f0 | |
| parent | 68d0c4872952406535e5f8fb145464790faf44bc (diff) | |
Added a comment
| -rw-r--r-- | doc/bugs/Possible_data-loss_if_WORM_keys_do_not_encode_relative_paths/comment_3_bda1e0d3569a6becf374d0e820219469._comment | 15 |
1 files changed, 15 insertions, 0 deletions
diff --git a/doc/bugs/Possible_data-loss_if_WORM_keys_do_not_encode_relative_paths/comment_3_bda1e0d3569a6becf374d0e820219469._comment b/doc/bugs/Possible_data-loss_if_WORM_keys_do_not_encode_relative_paths/comment_3_bda1e0d3569a6becf374d0e820219469._comment new file mode 100644 index 000000000..54fe869c5 --- /dev/null +++ b/doc/bugs/Possible_data-loss_if_WORM_keys_do_not_encode_relative_paths/comment_3_bda1e0d3569a6becf374d0e820219469._comment @@ -0,0 +1,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. + +"""]] |