hardcoresushi/libgocryptfs
1
0
Fork 0
Code Issues Pull Requests Releases Activity

Update README for v1.7.1

Browse Source
This commit is contained in:
Jakob Unterwurzacher 2019-10-06 22:35:27 +02:00
parent 65bc006a78
commit 8cb104f004
1 changed files with 6 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
README.md
View File

@ -187,7 +187,7 @@ RM: 3.379
Changelog Changelog
--------- ---------
vNEXT, in progress v1.7.1, in progress
* Support wild cards in reverse mode via `--exclude-wildcard` * Support wild cards in reverse mode via `--exclude-wildcard`
([#367](https://github.com/rfjakob/gocryptfs/pull/367)). Thanks @ekalin! ([#367](https://github.com/rfjakob/gocryptfs/pull/367)). Thanks @ekalin!
* Create `gocryptfs.diriv` files with 0440 permissions to make it easier to * Create `gocryptfs.diriv` files with 0440 permissions to make it easier to
@ -200,6 +200,11 @@ vNEXT, in progress
([#400](https://github.com/rfjakob/gocryptfs/issues/400)) ([#400](https://github.com/rfjakob/gocryptfs/issues/400))
* Fix `-idle` unmounting the filesystem despite recent activity * Fix `-idle` unmounting the filesystem despite recent activity
([#421](https://github.com/rfjakob/gocryptfs/issues/421)) ([#421](https://github.com/rfjakob/gocryptfs/issues/421))
* **Fix a race condition related to inode number reuse
([#363](https://github.com/rfjakob/gocryptfs/issues/363))**.
It could be triggered by concurrently creating and deleting files and can lead to data loss
in the affected file. This bug was found by the automated tests on Travis
and was very hard to trigger locally.
v1.7, 2019-03-17 v1.7, 2019-03-17
* **Fix possible symlink race attacks in forward mode** when using allow_other + plaintextnames * **Fix possible symlink race attacks in forward mode** when using allow_other + plaintextnames