From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: winsymlinks:nativestrict and Windows 10
Date: Tue, 19 Mar 2019 16:57:00 -0000 [thread overview]
Message-ID: <20190319165750.GP3908@calimero.vinschen.de> (raw)
In-Reply-To: <e564b698-4347-56fb-6d36-5e305df3c361@razorcat.de>
[-- Attachment #1: Type: text/plain, Size: 1174 bytes --]
On Mar 19 16:16, Frank Redeker wrote:
> Am 19.03.2019 um 15:23 schrieb LRN:
> > ... SNIP ...
> >
> > Devmode + SYMBOLIC_LINK_FLAG_ALLOW_UNPRIVILEGED_CREATE is the only way to
> > create symlinks without being Administrator (that i know of). You can't just
> > give some extra privileges to your non-administrator account. I know, i've tried.
>
> On Windows 10 Pro (1809) this works for me for with a non-administrator
> account.
>
> I just added the SeCreateSymbolicLinkPrivilege to my normal user account
> and was able to use mklink without any problems.
This is indeed a solution since the permission to create native symlinks
is coupled to this privilege and the Administrators group is the only
one having this privilege by default. Unfortunately not everyone has
the luxury to enable this privilege for the own account (domain users).
Btw, there is another restriction with native symlinks, independent from
user privileges, which is pretty puzzeling at first:
https://blogs.msdn.microsoft.com/junfeng/2012/05/07/the-symbolic-link-cannot-be-followed-because-its-type-is-disabled/
Corinna
--
Corinna Vinschen
Cygwin Maintainer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-03-19 16:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 12:35 Andrey Repin
2019-03-19 14:23 ` LRN
2019-03-19 15:16 ` Frank Redeker
2019-03-19 16:57 ` Corinna Vinschen [this message]
2019-03-19 17:20 ` Andrey Repin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190319165750.GP3908@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).