gocryptfs/internal/fusefrontend_reverse, branch detMirror of gocryptfs source code on Githubhttp://nuetzlich.net/cgit/gocryptfs/atom?h=det2017-05-28T18:43:48+00:00pathiv: move block IV algorithm into this package2017-05-28T18:43:48+00:00Jakob Unterwurzacher2017-05-28T18:43:48+00:00urn:sha1:e2341c93d5b113457905b338b414e41892113ec4
This was implemented in fusefrontend_reverse, but we need it
in fusefrontend as well. Move the algorithm into pathiv.BlockIV().
pathiv: move derivedIVContainer into the package2017-05-28T16:33:05+00:00Jakob Unterwurzacher2017-05-28T16:33:05+00:00urn:sha1:35f4f8af56ec4da9952df4feba4981f5d148b2cf
...under the new name "FileIVs".
This will also be used by forward mode.
fusefrontend_reverse: move pathiv to its own package2017-05-28T16:09:02+00:00Jakob Unterwurzacher2017-05-28T16:09:02+00:00urn:sha1:ab10cf63ed21d09e239986ac125b990fe06b5572
We will also need it in forward mode.
fusefrontend_reverse: store derived values for hard-linked files2017-05-25T19:33:16+00:00Jakob Unterwurzacher2017-05-25T19:33:16+00:00urn:sha1:9ecf2d1a3f69e3d995012073afe3fc664bd928f2
With hard links, the path to a file is not unique. This means
that the ciphertext data depends on the path that is used to access
the files.
Fix that by storing the derived values when we encounter a hard-linked
file. This means that the first path wins.
fix golint complaints2017-04-29T12:50:58+00:00Jakob Unterwurzacher2017-04-29T12:50:58+00:00urn:sha1:edb3e19cb5543c580261052395d461fa47c7cf58Add -forcedecode2017-04-23T21:11:56+00:00danim72017-04-08T00:09:28+00:00urn:sha1:f1945c4daae65074cfca8f0ab5b97ac5a50c24a0
Force decode of encrypted files even if the integrity check fails, instead of
failing with an IO error. Warning messages are still printed to syslog if corrupted
files are encountered.
It can be useful to recover files from disks with bad sectors or other corrupted
media.
Closes https://github.com/rfjakob/gocryptfs/pull/102 .
fusefrontend_reverse: switch to stable inode numbers2017-04-01T15:19:15+00:00Jakob Unterwurzacher2017-04-01T15:19:15+00:00urn:sha1:778c955eea1fdc16666f51f6f0a2fab0f580dbf0
The volatile inode numbers that we used before cause "find" to complain and error out.
Virtual inode numbers are derived from their parent file inode number by adding 10^19,
which is hopefully large enough no never cause problems in practice.
If the backing directory contains inode numbers higher than that, stat() on these files
will return EOVERFLOW.
Example directory lising after this change:
$ ls -i
926473 gocryptfs.conf
1000000000000926466 gocryptfs.diriv
944878 gocryptfs.longname.hmZojMqC6ns47eyVxLlH2ailKjN9bxfosi3C-FR8mjA
1000000000000944878 gocryptfs.longname.hmZojMqC6ns47eyVxLlH2ailKjN9bxfosi3C-FR8mjA.name
934408 Tdfbf02CKsTaGVYnAsSypA
fusefrontend_reverse: drop unused dirIVAttr function2017-04-01T15:05:55+00:00Jakob Unterwurzacher2017-04-01T15:05:55+00:00urn:sha1:e87aebb835b91ba66f288030ee3510df42b860a9
This has long been replaced by virtualFile.GetAttr().
fusefrontend_reverse: convert fmt.Printf calls to tlog2017-04-01T13:49:53+00:00Jakob Unterwurzacher2017-04-01T13:49:53+00:00urn:sha1:acb73ca4363a8fbf3e0be1907a9b26689d879d73
The fmt.Printfs output would end up in the paniclog.
fusefrontend_reverse: add comment to newVirtualFile2017-04-01T12:17:54+00:00Jakob Unterwurzacher2017-04-01T12:17:54+00:00urn:sha1:3cd18f288f487f0dfc8bd8de1288ed3b92cc5ca5
...and improve and comment variable naming in findLongnameParent.
No semantic changes.