WinFsp 2021
CHANGES SINCE WINFSP 2020.2
-
[NEW] WinFsp now supports file change notifications and cache invalidations. This functionality is offered via the following new API's:
- Native API:
FspFileSystemNotify
- FUSE API:
fuse_notify
- .NET API:
FileSystemHost.Notify
. (Some fixes to the .NET API functionality were contributed by @alonsohki. Thank you.)
- Native API:
-
[NEW] A native file system (notifyfs) and a .NET file system (notifyfs-dotnet) have been added to showcase the new file change notification API.
-
[NEW] A new WinFsp-FUSE option
FileSecurity
has been added that allows the complete specification of file security descriptors using SDDL. (See GitHub issue rclone/rclone#4717 (comment).) -
[FIX] The FSD now correctly handles a rare situation where receiving too many CLOSE calls from the OS (e.g. when caching thousands of files) could result in a bogus "insufficient resources" error. (See commit 0af0bfb.)
-
[FIX] WinFsp-FUSE correctly maps SID's from trusted domains to POSIX UID's in a multi-domain environment (using the "trustPosixOffset" attribute). Previously WinFsp-FUSE only handled SID's from the primary domain correctly.
-
[FIX] WinFsp-FUSE options such as
volname
,VolumePrefix
,FileSystemName
,ExactFileSystemName
are now truncated when too long. (See GitHub issue #311.) -
[FIX] The WinFsp driver is now started in a thread-safe manner if it is not already running. (See GitHub issue winfsp/cgofuse#51.)
-
[FIX] Credentials entered in the Credentials dialog (when mapping network drives) are no longer saved by default. (See GitHub PR #342. Thanks @gaotxg.)