From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: WSL symbolic links
Date: Thu, 26 Mar 2020 13:12:32 -0600 [thread overview]
Message-ID: <901e1c08-46cb-555b-c0d0-5bf9c726b3ca@SystematicSw.ab.ca> (raw)
In-Reply-To: <20200326110059.GG3261@calimero.vinschen.de>
On 2020-03-26 05:00, Corinna Vinschen wrote:
> On Mar 26 10:00, Thomas Wolff wrote:
>> A symbolic link created with WSL is neither interpreted in cygwin nor can it
>> be deleted:
>>> touch file
>>> wsl ln -s file link
>>> wsl ls -l link
>> lrwxrwxrwx 1 towo towo 1 Mar 26 08:56 link -> file
>>> ls -l link
>> -rw-r----- 1 Unknown+User Unknown+Group 0 Mar 26 00:00 link
> What kind of file are they in the real world? Reparse points? If so,
> what content do they have? I attached a Q&D source from my vault
> of old test apps to check on reparse point content. Please compile with
> gcc -g ../src/rd-reparse.c -o rd-reparse -lntdll
> It takes a single native NT path as parameter, kind of like this:
> ./rd-reparse '\??\C:\cygwin64\home\corinna\link'
They should be WSL or Windows mklink (soft) links, and the reason why mklink was
allowed unelevated in Windows 10 with Developer mode.
In an *elevated* shell:
$ ls -dln u
-rw-r----- 1 4294967295 4294967295 0 Nov 9 06:09 u
$ getfacl u
getfacl: u: Permission denied
$ icacls u
u NULL SID:(DENY)(Rc,S,REA,WEA,X,DC)
$HOSTNAME\$USER:(F)
$HOSTNAME\$USER:(RX,W,DC)
BUILTIN\Users:(Rc,S,RA)
BUILTIN\Administrators:(RX,W,DC)
BUILTIN\Users:(DENY)(S,RD,REA,X)
Everyone:(RX)
NT AUTHORITY\SYSTEM:(I)(F)
BUILTIN\Administrators:(I)(F)
$HOSTNAME\$USER:(I)(F)
Successfully processed 1 files; Failed processing 0 files
$ ./rd-reparse '\??\C:\...\u'
ReparseTag: 0xa000001d
ReparseDataLength: 5
Reserved: 0
02 00 00 00 75
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
next prev parent reply other threads:[~2020-03-26 19:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 9:00 Thomas Wolff
2020-03-26 11:00 ` Corinna Vinschen
2020-03-26 16:15 ` Thomas Wolff
2020-03-26 19:12 ` Brian Inglis [this message]
2020-03-26 19:56 ` Corinna Vinschen
2020-03-26 23:52 ` Thomas Wolff
2020-03-27 5:46 ` ASSI
2020-03-27 11:21 ` Corinna Vinschen
2020-03-27 12:24 ` Thomas Wolff
2020-03-27 13:01 ` Corinna Vinschen
2020-03-27 14:43 ` Thomas Wolff
2020-03-26 20:05 ` Corinna Vinschen
2020-03-27 17:58 ` Brian Inglis
2020-03-27 18:53 ` Corinna Vinschen
2020-03-28 3:32 ` Brian Inglis
2020-03-28 10:31 ` Henry S. Thompson
2020-03-28 11:30 ` Thomas Wolff
2020-03-28 11:59 ` Andrey Repin
2020-03-28 20:45 ` Brian Inglis
2020-03-29 11:52 ` Andrey Repin
2020-03-30 8:46 ` Corinna Vinschen
2020-04-04 14:32 ` Denis Excoffier
2020-04-05 15:22 ` Corinna Vinschen
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=901e1c08-46cb-555b-c0d0-5bf9c726b3ca@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).