Jakob Unterwurzacher 3062de6187 fusefronted: enable writing to write-only files ...

Due to RMW, we always need read permissions on the backing file. This is a
problem if the file permissions do not allow reading (i.e. 0200 permissions).
This patch works around that problem by chmod'ing the file, obtaining a fd,
and chmod'ing it back.

Test included.

Issue reported at: https://github.com/rfjakob/gocryptfs/issues/125

2017-07-11 23:19:58 +02:00

..

args.go

Implement force_owner option to display ownership as a specific user.

2017-06-01 00:26:17 +02:00

ctlsock_interface.go

fusefrontend: implement path decryption via ctlsock

2017-05-07 21:01:39 +02:00

file_allocate_truncate.go

fusefrontend: Read: use provided buffer

2017-06-30 23:11:38 +02:00

file_holes.go

fusefrontend: truncateGrowFile: avoid createHeader() call

2017-03-12 21:06:59 +01:00

file.go

fusefrontend: doRead: skip decryption for an empty read

2017-07-02 16:02:13 +02:00

fs_dir.go

nametransform: harden name decryption against invalid input

2017-05-23 21:26:38 +02:00

fs.go

fusefronted: enable writing to write-only files

2017-07-11 23:19:58 +02:00

names.go

nametransform: delete unused function DecryptPathDirIV

2016-09-25 18:56:23 +02:00