[gentoo-commits] gentoo commit in xml/htdocs/proj/en/hardened: pax-migrate-xattr.xml

[Anthony G. Basile (blueness)]

blueness    13/07/28 01:20:47

  Modified:             pax-migrate-xattr.xml
  Log:
  Update pax migration guide, bug #478400

Revision  Changes    Path
1.3                  xml/htdocs/proj/en/hardened/pax-migrate-xattr.xml

file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/hardened/pax-migrate-xattr.xml?rev=1.3&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/hardened/pax-migrate-xattr.xml?rev=1.3&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/hardened/pax-migrate-xattr.xml?r1=1.2&r2=1.3

Index: pax-migrate-xattr.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/hardened/pax-migrate-xattr.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- pax-migrate-xattr.xml	14 Jan 2013 12:20:38 -0000	1.2
+++ pax-migrate-xattr.xml	28 Jul 2013 01:20:47 -0000	1.3
@@ -1,5 +1,5 @@
 <?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/hardened/pax-migrate-xattr.xml,v 1.2 2013/01/14 12:20:38 blueness Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/hardened/pax-migrate-xattr.xml,v 1.3 2013/07/28 01:20:47 blueness Exp $ -->
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 
 <guide lang="en">
@@ -117,17 +117,7 @@
   <dd><b>a.</b> make sure you set USE=xattr in your global USE flags, and</dd>
   <dd><b>b.</b> emerge >=sys-apps/elfix-0.8.1 without disabling either ptpax or xtpax USE flags.</dd>
 
-  <dt><b>2. Portage preliminaries:</b></dt>
-  <dd>The current in tree pax-utils.eclass is not XATTR_PAX aware, and so we need to
-  use the pax-utils.eclass from the
-  <uri link='http://git.overlays.gentoo.org/gitweb/?p=proj/hardened-dev.git;a=summary'>
-  hardened-development overlay</uri>.  Add the overlay using layman and make sure you
-  set up your repos.conf file so that it overrides the tree eclass (man portage for more
-  details on how to setup repos.conf).  This step will be removed once we update the eclass
-  in tree (<uri link='https://bugs.gentoo.org/show_bug.cgi?id=431092'>bug #431092</uri>).
-  </dd>
-
-  <dt><b>3. Kernel preliminaries:</b></dt>
+  <dt><b>2. Kernel preliminaries:</b></dt>
   <dd>As you do the migration, you must make sure your filesystem can accomodate extended
   attributes, including tmpfs!  If your kernel hasn't been already so configured, do so
   now and reboot into it.  Choosing PAX_XATTR_PAX_FLAGS under the PaX kernel menu
@@ -136,7 +126,7 @@
   PT_PAX will be respected until you create XATTR_PAX fields on the target binaries.
   We'll tolerate this as a transition, but we recommend using only XATTR_PAX afterward.</dd>
 
-  <dt><b>4. Migrate the flags:</b></dt>
+  <dt><b>3. Migrate the flags:</b></dt>
   <dd>The elfix package comes with migrate-pax.  Running it with the -m flag will
   copy the PT_PAX flags to XATTR_PAX for every ELF object that portage knows about,
   <b>except</b> for those object which have the <b>default</b> flags.  Since a kernel
@@ -145,13 +135,13 @@
   desired.  Running <c>migrate-pax -m</c> is very safe and you can easily undo it by
   running <c>migrate-pax -d</c>.</dd>
 
-  <dt><b>5. Boot into an XATTR_PAX only kernel:</b></dt>
+  <dt><b>4. Boot into an XATTR_PAX only kernel:</b></dt>
   <dd>You can now boot into a pure XATTR_PAX kernel.  Make sure PT_PAX is off.  Even
   though the flags should be the same in both fields, or XATTR_PAX absent in the case
   of default flags, we will be on the side of caution and keep control over the effective
   flags by using only XATTR_PAX.</dd>
 
-  <dt><b>6. Profit!</b></dt>
+  <dt><b>5. Profit!</b></dt>
   <dd>If you really want to make sure it worked, the elfix package comes with some test
   suites.  These are tricky to use correctly because if you have the wrong combination
   of PT_PAX versus XATTR_PAX userland/kernel configurations, you'll get a lot of false