libgocryptfs/internal
Jakob Unterwurzacher 9ab11aa4d7 fusefrontend: drop writeOnly flag
We do not have to track the writeOnly status because the kernel
will not forward read requests on a write-only FD to us anyway.

I have verified this behavoir manually on a 4.10.8 kernel and also
added a testcase.
2017-05-01 17:49:37 +02:00
..
configfile Add -forcedecode 2017-04-23 23:11:56 +02:00
contentenc forcedecode: tighten checks 2017-04-24 00:25:02 +02:00
cryptocore fix golint complaints 2017-04-29 14:50:58 +02:00
ctlsock ctlsock: handle non-canonical empty paths 2017-02-05 18:17:30 +01:00
exitcodes fix golint complaints 2017-04-29 14:50:58 +02:00
fusefrontend fusefrontend: drop writeOnly flag 2017-05-01 17:49:37 +02:00
fusefrontend_reverse fix golint complaints 2017-04-29 14:50:58 +02:00
nametransform nametransform: WriteDirIV: replace ioutil.WriteFile 2017-04-29 14:15:13 +02:00
openfiletable fusefronted, openfiletable: move the open file table to its own package 2017-05-01 17:26:50 +02:00
prefer_openssl prefer_openssl: default to Go GCM on OSX 2016-12-10 21:04:17 +01:00
readpassword readpassword: increase max password size to 2048 2017-04-29 15:15:11 +02:00
serialize_reads fix golint complaints 2017-04-29 14:50:58 +02:00
siv_aead fix golint complaints 2017-04-29 14:50:58 +02:00
speed fix golint complaints 2017-04-29 14:50:58 +02:00
stupidgcm forcedecode: tighten checks 2017-04-24 00:25:02 +02:00
syscallcompat syscallcompat: OSX compat: fix variable warnings 2017-02-16 19:23:17 +01:00
tlog Drop Go 1.4 compatability code everywhere 2017-03-05 17:44:14 +01:00