comment
authorJoey Hess <joeyh@joeyh.name>
Wed, 21 Sep 2016 17:17:03 +0000 (13:17 -0400)
committerJoey Hess <joeyh@joeyh.name>
Wed, 21 Sep 2016 17:17:03 +0000 (13:17 -0400)
doc/todo/Allow_globally_limiting_filename_length/comment_1_e38f78a1263b15258d2aa4472e7bc31b._comment [new file with mode: 0644]

diff --git a/doc/todo/Allow_globally_limiting_filename_length/comment_1_e38f78a1263b15258d2aa4472e7bc31b._comment b/doc/todo/Allow_globally_limiting_filename_length/comment_1_e38f78a1263b15258d2aa4472e7bc31b._comment
new file mode 100644 (file)
index 0000000..0d718bf
--- /dev/null
@@ -0,0 +1,23 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2016-09-21T17:11:06Z"
+ content="""
+Standard encfs warning: It's buggy and insecure. Don't use it.
+
+You can find many other problems caused by encfs on this site, and 
+<https://defuse.ca/audits/encfs.htm> has described security problems with
+encfs for years.
+
+It would not help for `git-annex add` to check some kind of filename limit,
+because it would not prevent you doing this:
+
+       git annex add smallenough
+       git mv smallenough oh-oops-my-name-is-too-long-for-encfs
+       git commit -m haha
+
+A git pre-commit hook can of course be written that blocks such commits.
+
+I am not inclined to complicate git-annex just to handle encfs given how
+broken encfs is.
+"""]]