#XPENOLOGY DSM 6.2 UPDATE#
This update will restart your Synology NAS.Fixed a security vulnerability ( Synology-SA-18:36).Fixed an issue where iSCSI Manager might not open for the incompatible format of iSCSI LUN configuration files set up before DSM 5.2.Fixed multiple security vulnerabilities regarding Linux kernel ( Synology-SA-18:01).Adjusted power saving mechanism to improve PCIe compatibility.This update will restart your Synology NAS if you are using the models listed below.The update is expected to be available for all regions within the next few days, although the time of release in each region may vary slightly.It is recommended to grant the SE_SECURITY_NAME permission, also known as SeSecurityPrivilege, to your own program only as long as this permission is actually needed, and then revoke this permission from your own program.įreeFileSync needs this permission only during synchronization and probably only if the option "Copy DACL, SACL, Owner, Group" is enabled.īoth the dynamic granting of the permission and the dynamic revoking of the permission can be done using the two functions LookupPrivilegeValue and AdjustTokenPrivileges, as implemented in the SetPrivilege function on. The ProcessExplorer does not list the SeSecurityPrivilege permission for the FreeFileSync program on my computer. This user is member of the group domainname\Administrators. Here I do not use the account domainname\Administrator, but the account domainname\username. An Update to FreeFileSync 11.14 did not help.įinally, I installed FreeFileSync 11.14 on my own computer.
#XPENOLOGY DSM 6.2 SOFTWARE#
After updating the DSM software to version "DSM 6.2.4-25556 Update 2" on our Synology NAS, FreeFileSync 11.13 was not able to work as long as the option "Copy DACL, SACL, Owner, Group" was enabled. This update contains many security related changes. Using ProcessExplorer, I found that the SE_SECURITY_NAME permission, referred to here as SeSecurityPrivilege, has a value of " Disabled" on the FreeFileSync program.īefore updating the DSM software to version "DSM 6.2.4-25556 Update 2" on our Synology NAS, FreeFileSync 11.13 worked fine here. I connect using the account domainname\Administrator.
#XPENOLOGY DSM 6.2 WINDOWS 10#
I use the FreeFileSync 11.14 program in a Windows domain on another Windows 10 machine to which I connect via RemoteDesktop. To enable the SE_SECURITY_NAME privilege the functions LookupPrivilegeValue and AdjustTokenPrivileges can be used. The fact, that the FreeFileSync error message contains the expression ERROR_PRIVILEGE_NOT_HELD, indicates, that this is exactly, what is no longer fulfilled, after the DSM software update was installed on the Synology NAS.
To read the SACL of a file or directory, the SE_SECURITY_NAME privilege must be enabled for the calling process. To read the owner, group, or DACL from the security descriptor for the specified file or directory, the DACL for the file or directory must grant READ_CONTROL access to the caller, or the caller must be the owner of the file or directory. The information obtained is constrained by the caller's access rights and privileges. The GetFileSecurity function obtains specified information about the security of a file or directory. The FreeFileSync error message indicates that the error occurs when calling the GetFileSecurity function. Hints for solving the compatibility problem:
0 kommentar(er)
