Author eryksun
Recipients eryksun, izbyshev, paul.moore, steve.dower, tim.golden, zach.ware
Date 2018-03-05.19:46:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1520279171.79.0.467229070634.issue33001@psf.upfronthosting.co.za>
In-reply-to
Content
>> As os.symlink requires administrative privileges on most versions 
>> of Windows
>
> The current implementation requires SeCreateSymbolicLinkPrivilege on 
> ALL versions of Windows because users must pass an additional flag to 
> CreateSymbolicLink to enable non-privileged symlinks on recent Windows
> 10, which os.symlink() doesn't do (see #31512).

The change in Windows 10 to allow unprivileged creation of links will be supported implicitly in 3.7, but this change is more for convenience than necessity. SeCreateSymbolicLinkPrivilege can be granted to standard users and groups. On my own systems, I grant this privilege to the "Authenticated Users" (S-1-5-11) well-known group. This even allows administrators to create symbolic links without having to elevate.
History
Date User Action Args
2018-03-05 19:46:11eryksunsetrecipients: + eryksun, paul.moore, tim.golden, zach.ware, steve.dower, izbyshev
2018-03-05 19:46:11eryksunsetmessageid: <1520279171.79.0.467229070634.issue33001@psf.upfronthosting.co.za>
2018-03-05 19:46:11eryksunlinkissue33001 messages
2018-03-05 19:46:11eryksuncreate