public inbox for gentoo-hardened@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Anthony G. Basile" <blueness@gentoo.org>
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] Re: Tips for upgrading to the current stable gentoo hardened?
Date: Wed, 29 Jun 2011 21:21:23 -0400	[thread overview]
Message-ID: <4E0BCF93.9090001@gentoo.org> (raw)
In-Reply-To: <4E0B9BA4.3060707@whyscream.net>

On 06/29/2011 05:39 PM, Tom Hendrikx wrote:
> On 29/06/11 16:47, 7v5w7go9ub0o wrote:
>> On 06/29/11 07:19, Anthony G. Basile wrote:
>>
>> [snip]
>>
>>>
>>> The safest approach in either switching or recompiling everything
>>> is:
>>>
>>> 1. Make the profile is set "eselect profile list" and pick your
>>> hardened box.  Careful on amd64 about changing multilib/nomultilib.
>>> Stick with your mutilib-edness (if such a word exists :)
>>>
>>> 2. Rebuild the tool chain: emerge binutils glibc gcc
>>>
>>> 3. Rebuild system: emerge --keep-going -eq system (note anything
>>> that fails you might want to file a bug)
>>>
>>> 4. Rebuild world: emerge --keep-going -eq world (again not any
>>> failures, shouldn't happen else we're not doing our job)
>>>
>>> system vs world = system is just the bare minimum packages that any
>>> box running that profile needs.  world = system + what you've added.
>>> You can skip step 3, but there might be a chance of mixing
>>> unhardened/hardened stuff if you do, but I'm not 100% sure.
>>>
>>
>> Thank You!
>>
>> 1. Is there some way this clear, succinct list could get into the
>> hardened documentation?
>>
>> 2. At this point, the 'clearest' way to build a hardened box from scratch
>> seems to go a few steps into the Gentoo handbook, then migrate using the
>> steps above. Not ideal, but until the documentation can be refined, how
>> about either putting these steps into the handbook, or alternatively a
>> reference *in the handbook* to wherever you find a home for these steps
>> (e.g. QandA).
> 
> I built a hardened box last week by grabbing a hardened autobuild, then
> following the regular handbook for my arch. Above steps are only needed
> when you start from a regular stage, or when you are converting a
> regular install.
> 
> Usage of autobuilds is missing in the handbook now, but iirc there are
> some open bugs on getting this changed.
> 
> --
> Regards,
> 	Tom

That's correct, these are instructions for switching from vanilla or if
you want to *very* safely recompile everything making sure you get
hardened.  It is the most conservative path but also very time consuming.

If you're starting from scratch, just grab the latest stage3 *hardened*
tarball, start building your system from there and save yourself the
time.  You will gain nothing but recompiling the tool chain and
system/world.

-- 
Anthony G. Basile, Ph.D.
Gentoo Linux Developer [Hardened]
E-Mail    : blueness@gentoo.org
GnuPG FP  : 8040 5A4D 8709 21B1 1A88  33CE 979C AF40 D045 5535
GnuPG ID  : D0455535



      parent reply	other threads:[~2011-06-30  2:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-15 10:55 [gentoo-hardened] Tips for upgrading to the current stable gentoo hardened? Kārlis Repsons
2011-06-15 11:35 ` Jean-François Maeyhieux
2011-06-28 21:42   ` [gentoo-hardened] " 7v5w7go9ub0o
2011-06-28 22:20     ` 7v5w7go9ub0o
2011-06-29  8:45       ` Kārlis Repsons
2011-06-20 14:20 ` [gentoo-hardened] " Ed W
2011-06-29  8:39   ` Kārlis Repsons
2011-06-29 11:19     ` Anthony G. Basile
2011-06-29 14:47       ` [gentoo-hardened] " 7v5w7go9ub0o
2011-06-29 21:39         ` Tom Hendrikx
2011-06-29 23:44           ` 7v5w7go9ub0o
2011-06-30  1:21           ` Anthony G. Basile [this message]

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=4E0BCF93.9090001@gentoo.org \
    --to=blueness@gentoo.org \
    --cc=gentoo-hardened@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