gocryptfs - Mirror of gocryptfs source code on Github

Age	Commit message (Collapse)	Author
2020-05-17	Update go-fuse import path to github.com/hanwen/go-fuse/v2	Jakob Unterwurzacher
	We need https://github.com/hanwen/go-fuse/commit/fd7328faf9fdf75709f7ba7df7072aaf4eeb18b3 to fix a crash reported in https://github.com/rfjakob/gocryptfs/issues/430 : 2019/10/30 17:14:16 Unknown opcode 2016 panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x20 pc=0x508d38] This patch is only in the v2.x.x branch. Upgrade to v2, as the old API is also supported there. Running git grep hanwen/go-fuse \| grep -v hanwen/go-fuse/v2 to check for forgotten references comes back clean.
2020-05-03	fusefrontend_reverse: use inomap for inode number translation	Jakob Unterwurzacher
	Gets rid of static inode number value limitations. Fixes https://github.com/rfjakob/gocryptfs/issues/457
2018-09-08	syscallcompat: untangle OpenNofollow and rename to OpenDirNofollow	Jakob Unterwurzacher
	The function used to do two things: 1) Walk the directory tree in a manner safe from symlink attacks 2) Open the final component in the mode requested by the caller This change drops (2), which was only used once, and lets the caller handle it. This simplifies the function and makes it fit for reuse in forward mode in openBackingPath(), and for using O_PATH on Linux.
2018-01-17	fusefrontend_reverse: use OpenNofollow in virtualFile.GetAttr	Jakob Unterwurzacher
	Makes it robust against symlink races. Final piece, closes https://github.com/rfjakob/gocryptfs/issues/165
2017-08-06	nametransform: add Dir() function	Jakob Unterwurzacher
	Dir is like filepath.Dir but returns "" instead of ".". This was already implemented in fusefrontend_reverse as saneDir(). We will need it in nametransform for the improved diriv caching.
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: switch to stable inode numbers	Jakob Unterwurzacher
	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
2017-04-01	fusefrontend_reverse: convert fmt.Printf calls to tlog	Jakob Unterwurzacher
	The fmt.Printfs output would end up in the paniclog.
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
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-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-28	reverse: move newDirIVFile into virtualfile.go	Jakob Unterwurzacher
	After all, is's a virtual file.
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.