This is the mail archive of the
mailing list for the Cygwin project.
Re: winln for native symlinks
- From: Thomas Wolff <towo at towo dot net>
- To: cygwin at cygwin dot com
- Date: Thu, 04 Apr 2013 19:12:25 +0200
- Subject: Re: winln for native symlinks
- References: <515BD718 dot 8080605 at dancol dot org> <515BE1BF dot 5010803 at towo dot net> <515BE36F dot 6030701 at dancol dot org> <515DA0D9 dot 7050209 at towo dot net> <515DA8F9 dot 9000208 at openafs dot org>
Am 04.04.2013 18:23, schrieb Jeffrey Altman:
So I guess I had the right before anyway and the editrights didn't make
any difference - the more useless this hint is in many cases.
On 4/4/2013 11:48 AM, Thomas Wolff wrote:
It shows this error message:
winln: you don't permission to create symbolic links. Run, as
winln: editrights -a SeCreateSymbolicLinkPrivilege -a $YOUR_USER
which should be fixed somehow like this:
You don't have permission to create symbolic links. Run, as administrator,
editrights -a SeCreateSymbolicLinkPrivilege -u $USER
Moreover, this advice does not help. Even after having issued this
command as administrator, winln -s still works as administrator only.
The SeCreateSymbolicLinkPrivilege privilege is filtered by User Account
Control (UAC). If your account is a member of the "Administrators"
group, then the process needs to be run with your elevated credentials
in order to make use of the SeCreateSymbolicLinkPrivilege privilege.
Since winln can also create hard links (and by default), this would
require too much.
The "Administrator" account always runs in an elevated state and
accounts that are not members of the "Administrators" group do not have
their security tokens filtered by UAC.
Does Cygwin permit binaries to be built with manifests? If so,
winln.exe could include an embedded manifest that indicates that
elevated status is required. The user would then be prompted by UAC
whenever the command is used.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple