From: Stan Shebs <shebs@apple.com>
To: Bob Rossi <bob@brasko.net>
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: Check permissions of .gdbinit files
Date: Tue, 31 May 2005 17:54:00 -0000 [thread overview]
Message-ID: <429C7DE7.5070709@apple.com> (raw)
In-Reply-To: <20050531132742.GA12857@white>
Bob Rossi wrote:
>
>What if we had GDB prompt the user to determine if they wanted to read
>the .gdbinit file in? Then we could add another configuration variable
>to GDB that allowed it to always read in the files. That way, by
>default GDB would be more safe, but for the rest of us, it would work
>the way it always has.
>
I like this idea, or some variation. A developer working in a
less-secure environment can set the variable (env var?) to ask
first before doing, while in an environment like Apple where you
have a thousand engineers sharing files in all kinds of weird ways,
you can set it to "if an intruder gets this far in, .gdbinit is the
least of our worries."
Stan
next prev parent reply other threads:[~2005-05-31 15:08 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
[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 [this message]
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=429C7DE7.5070709@apple.com \
--to=shebs@apple.com \
--cc=bob@brasko.net \
--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