From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Doug Evans <dje@google.com>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sourceware.org
Subject: Re: [patch#2 3/6] set auto-load local-gdbinit warn-and-*
Date: Fri, 30 Mar 2012 06:45:00 -0000 [thread overview]
Message-ID: <20120330064517.GA24719@host2.jankratochvil.net> (raw)
In-Reply-To: <CADPb22QZFOaZ=cePDjJgE=m-y6QyOY04nTM1_+h2hwbTbLu-5A@mail.gmail.com>
On Fri, 30 Mar 2012 08:33:29 +0200, Doug Evans wrote:
> On Thu, Mar 29, 2012 at 11:26 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> >> And are we *really* sure we want to deprecate them?
> >
> > Looks like we are. Â FWIW, I would suggest polling at least some of the
> > projects that provide .gdbinit as part of their distribution. Â Even if
> > there's only one such project (Emacs), its developers should be
> > polled, IMO, before making this move.
>
> I'd reword that to say that before we hear from some significant
> representative users we should not be sure we're ready.
OK; to restate that .gdbinit loading is not a security part of this patchset.
"set autoload safepath" is.
I also made a mistake stating I will change the default in downstream
(Fedora), it does not need to be done, "safepath" is the part fixing the
security hole, "local-gdbinit" is unrelated.
Thanks,
Jan
next prev parent reply other threads:[~2012-03-30 6:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 9:13 Jan Kratochvil
2012-03-29 20:58 ` Doug Evans
2012-03-30 6:28 ` Eli Zaretskii
2012-03-30 6:33 ` Doug Evans
2012-03-30 6:45 ` Jan Kratochvil [this message]
2012-03-30 18:08 ` suspend: " Jan Kratochvil
2012-03-30 7:26 ` Eli Zaretskii
2012-04-02 20:31 ` [doc patch] objfile -> @var{objfile} [Re: [patch#2 3/6] set auto-load local-gdbinit warn-and-*] Jan Kratochvil
2012-04-02 21:10 ` Eli Zaretskii
2012-04-02 21:13 ` Jan Kratochvil
2012-04-02 21:19 ` Eli Zaretskii
2012-04-03 18:33 ` [patch#2 3/6] set auto-load local-gdbinit warn-and-* Jan Kratochvil
2012-04-05 16:15 ` Eli Zaretskii
2012-04-05 21:00 ` Jan Kratochvil
2012-04-05 16:28 ` Doug Evans
2012-04-05 16:53 ` Jan Kratochvil
2012-04-05 17:03 ` Doug Evans
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=20120330064517.GA24719@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=dje@google.com \
--cc=eliz@gnu.org \
--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