From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Keith Seitz <keiths@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] .gdbinit security (revived) [incl doc]
Date: Wed, 24 Nov 2010 21:23:00 -0000 [thread overview]
Message-ID: <20101124212331.GA18195@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <4CEC0757.6000503@redhat.com>
On Tue, 23 Nov 2010 19:26:31 +0100, Keith Seitz wrote:
> + /* If our group ID matches the file, read it in
> + without warning/querying the user. */
> +#ifdef HAVE_GETGID
> + if (statbuf.st_gid != getgid ())
> +#endif
So currently on `chmod 666 .gdbinit' it no longer traps...
BTW do people really need this feature? I always use my alias gdbn to force
-nx to not load any .gdbinit, as I generally do not expect which project which
way changes my GDB behavior.
src/gdb/.gdbinit is the most invasive one, it breaks GDB completely. :-)
Other projects incl. bash could also use such `$PWD/.*rc' reading policies.
They do not.
Thanks,
Jan
next prev parent reply other threads:[~2010-11-24 21:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 23:10 Keith Seitz
2010-11-20 2:50 ` Jan Kratochvil
2010-11-23 17:15 ` Keith Seitz
2010-11-20 9:45 ` Eli Zaretskii
2010-11-23 18:31 ` Keith Seitz
2010-11-23 19:19 ` Eli Zaretskii
2010-11-23 23:19 ` Doug Evans
2010-11-30 0:23 ` Keith Seitz
2010-11-24 21:23 ` Jan Kratochvil [this message]
2010-11-24 21:27 ` Keith Seitz
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=20101124212331.GA18195@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=keiths@redhat.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