Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Christopher Faylor <me@cgf.cx>
To: gdb-patches@sourceware.org
Subject: Re: RFC: Check permissions of .gdbinit files
Date: Tue, 31 May 2005 21:03:00 -0000	[thread overview]
Message-ID: <20050531175433.GA7386@trixie.casa.cgf.cx> (raw)
In-Reply-To: <uzmuc6j8k.fsf@gnu.org>

On Tue, May 31, 2005 at 08:46:03AM +0300, Eli Zaretskii wrote:
>> Date: Mon, 30 May 2005 18:42:00 -0400
>> From: Daniel Jacobowitz <drow@false.org>
>> Cc: gdb-patches@sourceware.org
>> 
>> Bother; I thought about the portability for a while, but didn't quite
>> consider this.  We're still OK though - the whole thing is surrounded
>> by HAVE_GETUID, and MinGW does not have GETUID, if I understand
>> correctly.
>
>Maybe, I don't know.  Isn't the MinGW port linked against some
>library, such as libgw32c.a, that implements more Posix stuff?

MinGW does not have getuid().  Or, at least the version that I have
checked out doesn't have it.  It is possible to emulate getuid on WinNT+
and it is possible to fill in all of the fields in st_mode with
reasonable things but, AFAIK, Mingw's implementation doesn't do this.

>In any case, the other issue still remains: if they do have getuid and
>S_IWOTH, non-readonly files will be reported world-writable.  So I'd
>suggest to either disable this feature entirely on Windows platforms,
>or write a Windows specific code that uses the Win32 API to get file
>ownership (GetSecurityInfo or some such).

Did anyone read Ulrich Drepper's recent rant about this kind of thing?  :-)

Are you implying that we should defend against the day when mingw starts
exporting getuid?  If we're postulating that getuid might exist someday
can't we just postulate that st_mode has been fixed at the same time?

cgf


  reply	other threads:[~2005-05-31 17:54 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-30 19:41 Daniel Jacobowitz
2005-05-30 19:46 ` Nathan J. Williams
2005-05-30 19:53   ` Daniel Jacobowitz
2005-05-30 19:54     ` Nathan J. Williams
2005-05-30 19:55       ` Daniel Jacobowitz
2005-05-30 21:28       ` Jason Molenda
2005-05-30 22:29 ` Eli Zaretskii
2005-05-30 23:00   ` Daniel Jacobowitz
2005-05-31 13:52     ` Eli Zaretskii
2005-05-31 21:03       ` Christopher Faylor [this message]
     [not found]         ` <umzqb9kha.fsf@gnu.org>
     [not found]           ` <20050531222233.GF9864@trixie.casa.cgf.cx>
2005-06-02  3:51             ` Eli Zaretskii
2005-06-02  4:26               ` Christopher Faylor
2005-06-02 21:54                 ` Eli Zaretskii
2005-05-30 22:42 ` Andreas Schwab
2005-05-30 22:49   ` Daniel Jacobowitz
2005-05-31  2:27     ` Andreas Schwab
2005-05-31  2:50       ` Daniel Jacobowitz
2005-05-31 14:42         ` Bob Rossi
2005-05-31 17:54           ` Stan Shebs
2005-06-11 22:35 ` Mark Kettenis

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=20050531175433.GA7386@trixie.casa.cgf.cx \
    --to=me@cgf.cx \
    --cc=gdb-patches@sourceware.org \
    /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