From 8ab0dcf0aa0ff2c09dfa32b33913e20a864e83e9 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 27 Apr 2016 13:11:50 -0400 Subject: comment --- ...ent_1_a3111068628efcfe8c5dbbe653805481._comment | 26 ++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 doc/bugs/encfs_support_--_shouldn__39__t_it_be_treated_as_crippled_already__63__/comment_1_a3111068628efcfe8c5dbbe653805481._comment diff --git a/doc/bugs/encfs_support_--_shouldn__39__t_it_be_treated_as_crippled_already__63__/comment_1_a3111068628efcfe8c5dbbe653805481._comment b/doc/bugs/encfs_support_--_shouldn__39__t_it_be_treated_as_crippled_already__63__/comment_1_a3111068628efcfe8c5dbbe653805481._comment new file mode 100644 index 000000000..98455e1ae --- /dev/null +++ b/doc/bugs/encfs_support_--_shouldn__39__t_it_be_treated_as_crippled_already__63__/comment_1_a3111068628efcfe8c5dbbe653805481._comment @@ -0,0 +1,26 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2016-04-27T16:59:51Z" + content=""" +git-annex does not these days treat lack of of hard link support as a crippled +filesystem. It just falls back to copying files where it would make hard +links. + +encfs is coming up crippled because it ignores lack of write bits on files; +writing to a mode 444 file on an encfs filesystem by the owner of the file +is allowed. + +That breaks an important safeguard that git-annex relies on; +for example this would work in a non-direct mode repository on an encfs +filesystem, even though file permissions don't allow writing to annexed +file contents: + + joey@darkstar:/tmp/encfs/d> echo corrupt > bar + +So, you're really better off using direct mode on encfs. + +encfs has tons of other problems that make it not work well with +git-annex, and generally insecure. I heartily recommend you reconsider +using it. +"""]] -- cgit v1.2.3