Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org, Tom Tromey <tromey@redhat.com>
Subject: Re: [RFA] Add $pdir as entry for libthread-db-search-path.
Date: Fri, 29 Apr 2011 17:08:00 -0000	[thread overview]
Message-ID: <20110429170824.GA6107@host1.jankratochvil.net> (raw)
In-Reply-To: <BANLkTinAR8yLHhR7KF8ROLTVQskA6fLQdg@mail.gmail.com>

On Fri, 29 Apr 2011 18:49:09 +0200, Doug Evans wrote:
> On Fri, Apr 29, 2011 at 5:36 AM, Jan Kratochvil <jan.kratochvil@redhat.com> wrote:
> > This is insecure default.  It is something like the FSF GDB insecure .gdbinit
> > behavior which many distros (at least Fedora but even others) have to patch.
> 
> Does Fedora turn off the autoloading of python?

No.

> How do your pretty printers Just Work?
> [Or maybe you only autoload if the directory is in $prefix/lib/debug
> or some such?]

You are right it is a security hole, I have not tracked to Python autoloading
much.  It should get CVE and security errata assigned as it is the same
category of a security breach as was:
	http://cve.mitre.org/cgi-bin/cvename.cgi?name=2006-4146


> Plus I wonder how easy it would be to build a program that used an
> accompanying libpthread that didn't match the system libthread_db -
> gdb would then pick the accompanying libthread_db.  Or does Fedora not
> ever look in the directory of libpthread for its libthread_db?

This may be also a security exploit I did not catch.


Thanks,
Jan


  reply	other threads:[~2011-04-29 17:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-29  3:59 Doug Evans
2011-04-29 12:36 ` Jan Kratochvil
2011-04-29 16:49   ` Doug Evans
2011-04-29 17:08     ` Jan Kratochvil [this message]
     [not found]       ` <BANLkTinagVcXZqvOg80eoFMnyaw9T0OYUw@mail.gmail.com>
2011-05-01 18:34         ` Doug Evans
2011-05-02 19:15           ` Jan Kratochvil
2011-05-02 19:51             ` Doug Evans
2011-05-06 18:40               ` Tom Tromey
2011-05-09 22:30                 ` 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=20110429170824.GA6107@host1.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@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