Mirror of gocryptfs source code on Github http://nuetzlich.net/cgit/gocryptfs/atom?h=xattr_user_buffer 2020-08-01T19:14:10+00:00 2020-08-01T19:14:10+00:00 Jakob Unterwurzacher 2020-08-01T18:47:59+00:00 urn:sha1:13dc7657ba0aac4da3f4b80ba231a919fdfae0f5 fusefrontend_reverse -> fusefrontend_reverse_v1api 2020-05-17T12:23:47+00:00 Jakob Unterwurzacher 2020-05-17T12:18:23+00:00 urn:sha1:ec74d1d2f4217a9a337d1db9902f32ae2aecaf33 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-03T13:22:10+00:00 Jakob Unterwurzacher 2020-05-03T13:22:10+00:00 urn:sha1:518771e4e247762f60c5594de427a8c86f19bd57 Gets rid of static inode number value limitations. Fixes https://github.com/rfjakob/gocryptfs/issues/457 2019-04-08T18:18:45+00:00 Jakob Unterwurzacher 2019-04-08T18:18:45+00:00 urn:sha1:fe06e9f45646893dc88ebe9e657e2e991f6f5fbb CheckTrailingGarbage was called even when "-passfile" was used, which is stupid, and causes false positives: https://github.com/rfjakob/gocryptfs/issues/391 (false error "Received trailing garbage after the password" when using -passfile in .bash_profile) Instead of trying to improve the logic to handle that case and make everything even more complicated, delete the function. It is unclear if actually helps in some cases, and it definitely harms as shown by the above bug report. 2019-03-26T19:56:37+00:00 Eduardo M KALINOWSKI 2019-02-16T20:55:54+00:00 urn:sha1:3bc100aeb3f0763f78c8b3a70165b9f8aaa52db5 This adds support for gitignore-like wildcards and exclude patters in reverse mode. It (somewhat) fixes #273: no regexp support, but the syntax should be powerful enough to satisfy most needs. Also, since adding a lot of --exclude options can be tedious, it adds the --exclude-from option to read patterns from a file (or files). 2018-09-08T16:06:33+00:00 Jakob Unterwurzacher 2018-09-08T16:06:33+00:00 urn:sha1:930c37e03d5ff80e7cdc9f0ca2cd35d80a06d5c0 This fixes the "0100 directory" problem in reverse mode, and should be slightly faster. 2018-09-08T15:41:17+00:00 Jakob Unterwurzacher 2018-09-08T15:41:17+00:00 urn:sha1:9ec9d0c49cfbdc9ceba10d7534b77e527c0a3cdc 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-02-01T22:50:11+00:00 Jakob Unterwurzacher 2018-02-01T22:46:02+00:00 urn:sha1:9f8d0d8e5734e3771b52c8a8784ef5a76b0f9ca8 For some reason the syscall.NAME_MAX constant does not exist on gccgo, and it does not hurt us to use unix.NAME_MAX instead. https://github.com/rfjakob/gocryptfs/issues/201 2018-01-17T20:36:38+00:00 Jakob Unterwurzacher 2018-01-17T20:36:38+00:00 urn:sha1:a2677bce2a632d80850fabb1e397558d8a07742b Makes it robust against symlink races. Final piece, closes https://github.com/rfjakob/gocryptfs/issues/165 2018-01-17T19:54:05+00:00 Jakob Unterwurzacher 2018-01-17T19:52:52+00:00 urn:sha1:959e1fc1e2f531480ad1353179fc94f56ff76dce Protects findLongnameParent against symlink races. Also add comments to several functions along the way. Reported at https://github.com/rfjakob/gocryptfs/issues/165