From: "\"Paweł Hajdan, Jr.\"" <phajdan.jr@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] hardened glibc and gcc dependencies
Date: Thu, 27 Oct 2011 11:03:58 +0200 [thread overview]
Message-ID: <4EA91E7E.4000902@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 843 bytes --]
As a part of my earlier threads I tried to figure out the migration plan
from not hardened glibc and not hardened gcc to both of them hardened.
That of course raises questions like - what we compile first, and what
are dependencies here?
Here's what I have figured out - by _experimenting_ not speculation:
1. Building glibc with USE=hardened works, no matter whether the
toolchain is hardened or not.
2. However, glibc won't apply one hardening-related patch if the used
toolchain is not pie-enabled.
3. Interestingly, gcc with USE=hardened compiles fine even if glibc is
-hardened. The vanilla spec works. I haven't tested the hardened spec.
Based on that, I suggest the following dependency changes (conceptually):
In glibc: DEPEND="gcc[hardened?]"
In gcc: PDEPEND="elibc_glibc? glibc[hardened?]"
Thoughts?
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 203 bytes --]
next reply other threads:[~2011-10-27 9:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-27 9:03 "Paweł Hajdan, Jr." [this message]
2011-10-27 16:08 ` [gentoo-dev] hardened glibc and gcc dependencies "Paweł Hajdan, Jr."
2011-10-27 16:49 ` [gentoo-dev] " Duncan
2011-10-27 17:33 ` [gentoo-dev] " Nirbheek Chauhan
2011-10-27 23:47 ` [gentoo-dev] " Ryan Hill
2011-10-27 23:50 ` Mike Frysinger
2011-10-28 11:36 ` Anthony G. Basile
2011-10-28 17:20 ` Nirbheek Chauhan
2011-10-30 22:24 ` Petteri Räty
2011-10-31 1:04 ` Ryan Hill
2011-10-28 3:03 ` Nirbheek Chauhan
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=4EA91E7E.4000902@gentoo.org \
--to=phajdan.jr@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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