public inbox for cygwin-developers@cygwin.com
 help / color / mirror / Atom feed
From: David Macek <david.macek.0@gmail.com>
To: cygwin-developers@cygwin.com
Subject: Root directory being a junction fools realpath()
Date: Sun, 14 Feb 2021 12:56:22 +0100	[thread overview]
Message-ID: <CAH2Hv8++XJ67t3Zyf=G3TOkhejC3nxbOZfRxB9M=g_WQW0Scmg@mail.gmail.com> (raw)

Greetings.

I think I found a way to fool Cygwin into misplacing its root
directory. Given recent Cygwin with GCC and a simple test program:

```
#include <stdio.h>
#include <limits.h>
#include <stdlib.h>
int main() {
char real[PATH_MAX];
realpath("/", real);
printf("/ -> %s\n", real);
return 0;
}
```

... compiled with:

$ gcc -D_DEFAULT_SOURCE -o new.exe -Wall -Wextra -std=c11 new.c

... and my set-up with a junction (`mklink /j link target`) realpath()
result is dependent on which path I use to invoke the Cygwin root
process:

> dir C:\ | findstr cygwin64
10. 02. 2021  12:13    <DIR>          cygwin64

> dir D:\ | findstr cygwin64
14. 02. 2021  12:19    <JUNCTION>     cygwin64 [C:\cygwin64]

> C:\cygwin64\bin\bash -lc /cygdrive/w/new
/ -> /

> D:\cygwin64\bin\bash -lc /cygdrive/w/new
/ -> /cygdrive/c/cygwin64

It seems the current working directory doesn't matter at all, same as
the directory where the test program resides. Regular substs don't
seem to have the same effect. I can do more tests if requested.

I assume this is not intended behavior, because the root should always
be the root for Cygwin processes, no matter how they're invoked.

If possible ping me on IRC if anything because I don't check my mail too often.

-- 
David Macek

             reply	other threads:[~2021-02-14 11:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-14 11:56 David Macek [this message]
2021-02-15 12:25 ` Corinna Vinschen
2021-02-15 13:20   ` Corinna Vinschen
2021-02-18 11:46     ` David Macek
2021-02-18 13:09       ` Corinna Vinschen
2021-02-19 18:24         ` Corinna Vinschen
2021-03-07 13:15           ` David Macek

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='CAH2Hv8++XJ67t3Zyf=G3TOkhejC3nxbOZfRxB9M=g_WQW0Scmg@mail.gmail.com' \
    --to=david.macek.0@gmail.com \
    --cc=cygwin-developers@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).