diff options
| author | Jakob Unterwurzacher | 2019-01-05 18:34:22 +0100 |
|---|---|---|
| committer | Jakob Unterwurzacher | 2019-01-05 18:34:22 +0100 |
| commit | bd055ed7de77b2e16c391a5bfe714bb5b07d5787 (patch) | |
| tree | 5c056dea597563b6dc230b514ea15700ecdb321c | |
| parent | fb705f99782f222e72c42b23be9263bbd302a4d4 (diff) | |
Update changelog
| -rw-r--r-- | README.md | 6 |
1 files changed, 5 insertions, 1 deletions
@@ -161,7 +161,7 @@ RM: 3.379 Changelog --------- -v1.7, in progress (v1.7-beta1 released 2019-01-03) +v1.7, in progress (v1.7-beta1: 2019-01-03, v1.7-rc1: 2019-01-04) * **Fix possible symlink race attacks in forward mode** when using allow_other + plaintextnames * If you use *both* `-allow_other` *and* `-plaintextnames`, you should upgrade. Malicious users could trick gocryptfs into modifying files outside of `CIPHERDIR`, @@ -178,6 +178,10 @@ v1.7, in progress (v1.7-beta1 released 2019-01-03) [#286](https://github.com/rfjakob/gocryptfs/issues/286)) * gocryptfs-xray: add `-aessiv` flag for correctly parsing AES-SIV format files ([#299](https://github.com/rfjakob/gocryptfs/issues/299)) +* Ensure that standard fds 0,1,2 are always initialized + ([#320](https://github.com/rfjakob/gocryptfs/issues/320)). + Prevents trouble in the unlikely case that gocryptfs is called with + stdin,stdout and/or stderr closed. v1.6.1, 2018-12-12 * Fix "Operation not supported" chmod errors on Go 1.11 |