From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0000064]: ldd segfault when uclibc is build with security options enabled
Date: Mon, 12 Feb 2007 05:48:00 -0800 [thread overview]
Message-ID: <03d55c3fd424c24a05b776643e49e599@bugs.busybox.net> (raw)
The following issue has been ASSIGNED.
======================================================================
http://busybox.net/bugs/view.php?id=64
======================================================================
Reported By: babel
Assigned To: buildroot
======================================================================
Project: buildroot
Issue ID: 64
Category: Security
Reproducibility: always
Severity: crash
Priority: normal
Status: assigned
======================================================================
Date Submitted: 01-27-2005 00:18 PST
Last Modified: 02-12-2007 05:47 PST
======================================================================
Summary: ldd segfault when uclibc is build with security
options enabled
Description:
I've used the attached dot-config files to build a complete buildroot with
ldd. Enabling the security options in uClibc gives the result shown below.
Just disabling the uClibc security options and rebuild result in a working
ldd.
======================================================================
----------------------------------------------------------------------
psm - 02-06-05 11:20
----------------------------------------------------------------------
I wonder why BUILD_SSP is selected, that is only allowed for specially
patched
gcc, that is not supported by buildroot (HAS_SSP maybe be left in)
if you have patched your buildroot's gcc with the propolice patch, and
enable HAS_SSP, you'll have 2 __guard/__stack_smash_handler, one living in
libc
the other in libgcc_s.so
Currently the *SSP*/*PROPOLICE* options are only usable in gentoo distro
----------------------------------------------------------------------
prpplague - 01-25-06 12:36
----------------------------------------------------------------------
resolved in latest build
Issue History
Date Modified Username Field Change
======================================================================
01-27-05 00:18 babel New Issue
01-27-05 00:18 babel File Added: dot-config.tar.bz2
01-27-05 00:18 babel Issue Monitored: babel
02-06-05 11:20 psm Note Added: 0000043
03-16-05 12:13 andersen Status new => assigned
03-16-05 12:13 andersen Assigned To => uClibc
01-25-06 12:36 prpplague Note Added: 0001004
01-25-06 12:36 prpplague Status assigned => resolved
01-25-06 12:36 prpplague Resolution open => fixed
03-08-06 16:52 vapier Status resolved => closed
02-12-07 05:47 vapier Status closed => assigned
02-12-07 05:47 vapier Assigned To uClibc => buildroot
======================================================================
reply other threads:[~2007-02-12 13:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=03d55c3fd424c24a05b776643e49e599@bugs.busybox.net \
--to=bugs@busybox.net \
--cc=buildroot@busybox.net \
/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