Changes
This release includes the following changes from v0.15.1:
- Modified templated rendering to include session status even when paused
- Thanks to @rfay for reporting
- Fixed detection of
mutagen-agentabsence on tcsh (#366)- Thanks to @mkoennecke for reporting
- Switched to using
defaultFileModeinstead ofdefaultDirectoryModefor base symbolic link permissions (see below)
Symbolic link permissions changes
This release contains a minor change for symbolic link permissions bits. While no existing behavior is documented and most POSIX systems don't respect symbolic link permission bits in any case, the original intention was for Mutagen to use defaultFileMode as the basis for symbolic link permission bits. In earlier releases, the defaultDirectoryMode setting was being used as the basis for symbolic link permissions instead of defaultFileMode. The cases in which this change will have any effect are uncommon and the effects are minimal.
Specifically, the following conditions are necessary for there to be any difference:
- Non-default settings are used for
defaultDirectoryModeand/ordefaultFileMode
AND
- (Case 1) macOS is being used and
defaultDirectoryModehas read bits that differ from those indefaultFileMode, OR - (Case 2) Windows is being used and
defaultDirectoryModediffers fromdefaultFileModein its setting of the0200bit
In Case 1, the differing read bit(s) will have an effect on corresponding entities' ability to invoke readlink on the symbolic link. They have no impact on the accessibility of the link's target. No other POSIX platforms use symlink permission bits to enforce access control, instead allowing readlink unconditionally, and thus this change has no visible impact on those platforms other than the (unused) permission bits set on the symlink being different. On platforms such as Linux, which don't allow the association of permission bits with symlinks, there is no effect whatsoever.
In Case 2, the differing 0200 bit only affects owner writability for the symbolic link.