mirror of
https://github.com/rclone/rclone.git
synced 2024-12-04 14:26:42 +01:00
01ccf204f4
Before this change, if writing to a local backend with --metadata and --links, if the incoming metadata contained mode or ownership information then rclone would apply the mode/ownership to the destination of the link not the link itself. This fixes the problem by using the link safe sycall variants lchown/fchmodat when --links and --metadata is in use. Note that Linux does not support setting permissions on symlinks, so rclone emits a debug message in this case. This also fixes setting times on symlinks on Windows which wasn't implemented for atime, mtime and was incorrectly setting the target of the symlink for btime. See: https://github.com/rclone/rclone/security/advisories/GHSA-hrxh-9w67-g4cv
17 lines
438 B
Go
17 lines
438 B
Go
//go:build windows || plan9 || js || linux
|
|
|
|
package local
|
|
|
|
import "os"
|
|
|
|
const haveLChmod = false
|
|
|
|
// lChmod changes the mode of the named file to mode. If the file is a symbolic
|
|
// link, it changes the link, not the target. If there is an error,
|
|
// it will be of type *PathError.
|
|
func lChmod(name string, mode os.FileMode) error {
|
|
// Can't do this safely on this OS - chmoding a symlink always
|
|
// changes the destination.
|
|
return nil
|
|
}
|