From: Doug Henderson <djndnbvg@gmail.com>
To: cygwin <cygwin@cygwin.com>
Subject: Re: Type of symlink file and readshortcut
Date: Wed, 23 Jun 2021 18:32:10 -0600 [thread overview]
Message-ID: <CAJ1FpuMTbgiWJZKjNdmO_zyx9gB6cTKy=Npk0obm4BPmS+SiwA@mail.gmail.com> (raw)
In-Reply-To: <462e4a4c-8648-c7b2-267a-db63851dba4b@maxrnd.com>
On Wed, 23 Jun 2021 at 16:28, Mark Geisert <mark@maxrnd.com> wrote:
> Håkon Hægland via Cygwin wrote:
> > I am on Windows 10 Home, 21H1. I am trying to understand what type of files
> > are generated by the "ln -s" command. According to this blog:
> >
> > https://blogs.windows.com/windowsdeveloper/2016/12/02/symlinks-windows-10/
> >
> > starting with Windows 10 Insiders build 14972, native symlinks can be
> > created without needing to elevate the console as administrator.
> >
> > To enable this feature, go to "Windows Security" -> "For developers", and
> > turn on "Developer mode".
I expect Developer Mode grants a lot of unnecessary permissions.
In the interest of minimal changes to security policy,
the following process worked for me.
I don't know how to do this through settings, but
open Control Panel
open Administrative Tools
open Local Security Policy
Using the tree in the left panel:
open Local Policies
open User Rights Assignment
In the right panel:
Right-click on Create symbolic links -> Properties
add the user id(s) that should be able to create symbolic links
This allows the added user(s) to set
CYGWIN=winsymlinks:nativestrict
and create native windows symbolic links in cygwin.
This process grants 1 permission which is surely frantin fewer than
Developer Mode.
I have
CYGWIN_NT-10.0 mars 3.2.0(0.340/5/3) 2021-03-29 08:42 x86_64 Cygwin
on
Microsoft Windows [Version 10.0.19043.1055]
Windows Pro, now with 21H1 installed.
HTH
Doug
--
Doug Henderson, Calgary, Alberta, Canada - from gmail.com
prev parent reply other threads:[~2021-06-24 0:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 13:47 Håkon Hægland
2021-06-23 22:24 ` Mark Geisert
2021-06-24 0:32 ` Doug Henderson [this message]
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='CAJ1FpuMTbgiWJZKjNdmO_zyx9gB6cTKy=Npk0obm4BPmS+SiwA@mail.gmail.com' \
--to=djndnbvg@gmail.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).