Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: "Nathan J. Williams" <nathanw@wasabisystems.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: Check permissions of .gdbinit files
Date: Mon, 30 May 2005 19:53:00 -0000	[thread overview]
Message-ID: <20050530194115.GA30980@nevyn.them.org> (raw)
In-Reply-To: <mtu7jhgfshj.fsf@scrubbing-bubbles.mit.edu>

On Mon, May 30, 2005 at 03:01:28PM -0400, Nathan J. Williams wrote:
> Daniel Jacobowitz <drow@false.org> writes:
> 
> > Gentoo recently published a security update for GDB, citing the fact that
> > GDB would load .gdbinit from the current directory even if that was owned by
> > another user.  I'm not sure how I feel about running GDB in an untrusted
> > directory or on untrusted binaries and expecting it to behave sensibly, but
> > this particular issue is easy to fix.  Here's my suggested fix; it's not the
> > same as Gentoo's.  If .gdbinit is world writable or owned by a different
> > user, refuse to open it (and warn the user).
> > 
> > Anyone have opinions on this change?
> 
> I think the "owned by a different user" change is problematic. I've
> used build systems that autogenerated .gdbinit files in the build
> tree, and it would be entirely sensible for one developer to go and
> debug another developer's build.

Well that's the whole point.  You'll get a warning; would you be
happier if the warning explicitly suggested "source .gdbinit"?

-- 
Daniel Jacobowitz
CodeSourcery, LLC


  reply	other threads:[~2005-05-30 19:41 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 [this message]
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
     [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=20050530194115.GA30980@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=nathanw@wasabisystems.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