gocryptfs - Mirror of gocryptfs source code on Github

Age	Commit message (Collapse)	Author
2017-07-29	fusefronted_reverse: fix ino collision between .name and .diriv files	Jakob Unterwurzacher
	A directory with a long name has two associated virtual files: the .name file and the .diriv files. These used to get the same inode number: $ ls -di1 * / 33313535 gocryptfs.longname.2togDFouca9mrTwtfF1RNW5DZRAQY8alaR7wO_Xd5Zw 1000000000033313535 gocryptfs.longname.2togDFouca9mrTwtfF1RNW5DZRAQY8alaR7wO_Xd5Zw/gocryptfs.diriv 1000000000033313535 gocryptfs.longname.2togDFouca9mrTwtfF1RNW5DZRAQY8alaR7wO_Xd5Zw.name With this change we use another prefix (2 instead of 1) for .name files. $ ls -di1 * / 33313535 gocryptfs.longname.2togDFouca9mrTwtfF1RNW5DZRAQY8alaR7wO_Xd5Zw 1000000000033313535 gocryptfs.longname.2togDFouca9mrTwtfF1RNW5DZRAQY8alaR7wO_Xd5Zw/gocryptfs.diriv 2000000000033313535 gocryptfs.longname.2togDFouca9mrTwtfF1RNW5DZRAQY8alaR7wO_Xd5Zw.name
2017-05-30	fusefrontend_reverse: move pathiv to its own package	Jakob Unterwurzacher
	We will also need it in forward mode.
2017-04-01	fusefrontend_reverse: add comment to newVirtualFile	Jakob Unterwurzacher
	...and improve and comment variable naming in findLongnameParent. No semantic changes.
2017-03-28	fusefrontend_reverse: consistent file owners for .diriv, .name files	danim7
	This PR addresses the Issue #95, about "Confusing file owner for longname files in reverse mode". It affects only the reverse mode, and introduces two modifications: 1) The "gocryptfs.longname.XXXX.name" files are assigned the owner and group of the underlying plaintext file. Therefore it is consistent with the file "gocryptfs.longname.XXXX" that has the encrypted contents of the plaintext file. 2) The two virtual files mentioned above are given -r--r--r-- permissions. This is consistent with the behavior described in function Access in internal/fusefrontend_reverse/rfs.go where all virtual files are always readable. Behavior also observed in point c) in #95 . Issue #95 URL: https://github.com/rfjakob/gocryptfs/issues/95 Pull request URL: https://github.com/rfjakob/gocryptfs/pull/97
2017-03-05	nametransform: fix Raw64 not affecting longnames	Jakob Unterwurzacher
	HashLongName() incorrectly hardcoded the call to base64.URLEncoding.
2016-12-10	Replace all calls to naked panic() with log.Panic()	Jakob Unterwurzacher
	We want all panics to show up in the syslog.
2016-11-10	reverse: fix longname decoding bug	Jakob Unterwurzacher
	This could have caused spurious ENOENT errors. That it did not cause these errors all the time is interesting and probably because an earlier readdir would place the entry in the cache. This masks the bug.
2016-11-10	Fix golint warnings	Jakob Unterwurzacher
	$ golint ./... \| grep -v underscore \| grep -v ALL_CAPS internal/fusefrontend_reverse/rfs.go:52:36: exported func NewFS returns unexported type *fusefrontend_reverse.reverseFS, which can be annoying to use internal/nametransform/raw64_go1.5.go:10:2: exported const HaveRaw64 should have comment (or a comment on this block) or be unexported
2016-10-05	reverse: initialize the longname cache only when reverse mode is used	Jakob Unterwurzacher
	Gets rid of the idling longnameCacheCleaner thread in "normal" mode.
2016-10-04	lint fixes	Valient Gough

2016-09-29	reverse: use per-purpose nonce generation	Jakob Unterwurzacher
	Also pull all the deterministic nonce code into fusefrontend_reverse to greatly simplify the normal code path.
2016-09-25	Implement changes proposed by gosimple.	Jakob Unterwurzacher
	Also delete the unused "dirIVNameStruct", found by deadcode.
2016-09-25	reverse: derive file ID and block IVs from file paths	Jakob Unterwurzacher

2016-09-25	reverse: add longnameParentCache	Jakob Unterwurzacher
	findLongnameParent has to read the whole directory to find the right file; add a simple cache to avoid most directory scans.
2016-09-25	reverse: resolve long names in Open and GetAttr	Jakob Unterwurzacher
	The last patch added functionality for generating gocryptfs.longname.* files, this patch adds support for mapping them back to the full filenames. Note that resolving a long name needs a full readdir. A cache will be implemented later on to improve performance.