From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9485 invoked by alias); 19 Mar 2019 16:57:55 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 9476 invoked by uid 89); 19 Mar 2019 16:57:55 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-101.6 required=5.0 tests=AWL,BAYES_00,GOOD_FROM_CORINNA_CYGWIN,KAM_NUMSUBJECT,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 spammy=nativestrict, winsymlinks, symlinks, Administrators X-HELO: mout.kundenserver.de Received: from mout.kundenserver.de (HELO mout.kundenserver.de) (217.72.192.73) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 19 Mar 2019 16:57:54 +0000 Received: from calimero.vinschen.de ([24.134.7.25]) by mrelayeu.kundenserver.de (mreue107 [212.227.15.183]) with ESMTPSA (Nemesis) id 1Md66H-1gXV8e2Sfr-00aFVQ for ; Tue, 19 Mar 2019 17:57:51 +0100 Received: by calimero.vinschen.de (Postfix, from userid 500) id C4338A80970; Tue, 19 Mar 2019 17:57:50 +0100 (CET) Date: Tue, 19 Mar 2019 16:57:00 -0000 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: winsymlinks:nativestrict and Windows 10 Message-ID: <20190319165750.GP3908@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <1039329494.20190319152358@yandex.ru> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="ytoMbUMiTKPMT3hY" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.11.3 (2019-02-01) X-SW-Source: 2019-03/txt/msg00489.txt.bz2 --ytoMbUMiTKPMT3hY Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-length: 1160 On Mar 19 16:16, Frank Redeker wrote: > Am 19.03.2019 um 15:23 schrieb LRN: > > ... SNIP ... > >=20 > > 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. >=20 > On Windows 10 Pro (1809) this works for me for with a non-administrator > account. >=20 > 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-canno= t-be-followed-because-its-type-is-disabled/ Corinna --=20 Corinna Vinschen Cygwin Maintainer --ytoMbUMiTKPMT3hY Content-Type: application/pgp-signature; name="signature.asc" Content-length: 833 -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEoVYPmneWZnwT6kwF9TYGna5ET6AFAlyRH44ACgkQ9TYGna5E T6BOJRAAlF0ybIA4hq5Vz682jvaEa2ozRUhqCAukUeMt2XEjOOhjmVMmSbB4rDj1 QDSgUXiD7fZXtRpqHIoeNx3/kKQeJLDX6LbJJq0si/k1wdaPNaK3lJN7+RWfrQGD hgbnE4IfNqaamRMVyXHVQErBA62IUTuI31XaYnKgyBcBwsy99ETo7sWfzrKJUaBn 92QR/KTUpUmdBM2+5/s1aSYY77bcHXLBsK3U/03XEZ9Cxk6FkRLNFy2+LLnB5aDB xIBk9AwGEoOPSOenhlNUxdaGmjG3zx9P9gu3fz91+4eO3pfhPaZ0zyCEm3A3HHOy 2rrkWCHBVTKAQE1BaVTrrywJ/AqCb1ch9Ez1i60G5/XDp4fc6MrXR9rakOZrciqt slrzhV0U9YoLh34nYUcUxCP20vcPjvIqnGNBkAs6OUXB+Aw5wHsjJ9UGoQ1fg4Wy VWyOdGSzB9bvzbbGYLCXmY6pYeDpTRplKjch5zTW+dTYL6Mx+v9W23G6LWwSt0Mz RVVsG47z9CNJOP/O7WWk9IvnsRR4bTeQSZGdQ64ni6GprQ21VyvP69uT0mSVwjlZ Fhq7sn+1/hdiqxyhRnkT8r7poepoIDgDZkoXWa3/d1M1f3H45r2hv6qJbS4i5Uqm zcZA8vSDIQkH2jxmusydu0kH7TWE6f4ksK1UfeyVWKW7YIb/PKU= =8n/6 -----END PGP SIGNATURE----- --ytoMbUMiTKPMT3hY--