swift 13/08/03 15:03:03 Modified: hb-install-stage.xml Log: Fix bug #470750 - Add instructions for gpg verification of stage digest, thanks to Roman Zilka
Revision Changes Path 1.133 xml/htdocs/doc/en/handbook/hb-install-stage.xml file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-stage.xml?rev=1.133&view=markup plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-stage.xml?rev=1.133&content-type=text/plain diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-stage.xml?r1=1.132&r2=1.133 Index: hb-install-stage.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-stage.xml,v retrieving revision 1.132 retrieving revision 1.133 diff -u -r1.132 -r1.133 --- hb-install-stage.xml 2 Jan 2013 19:06:51 -0000 1.132 +++ hb-install-stage.xml 3 Aug 2013 15:03:03 -0000 1.133 @@ -4,7 +4,7 @@ <!-- The content of this document is licensed under the CC-BY-SA license --> <!-- See http://creativecommons.org/licenses/by-sa/2.5 --> -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-stage.xml,v 1.132 2013/01/02 19:06:51 swift Exp $ --> +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-stage.xml,v 1.133 2013/08/03 15:03:03 swift Exp $ --> <sections> @@ -13,8 +13,8 @@ describe how you extract the stage3 archive and configure Portage. </abstract> -<version>18</version> -<date>2012-12-09</date> +<version>19</version> +<date>2013-08-03</date> <section> <title>Installing a Stage Tarball</title> @@ -152,10 +152,20 @@ <p> Then compare the output of these commands with the value registered in the -.DIGESTS files that can be found on the mirrors as well. The values need to +<path>.DIGESTS(.asc)</path> files that can be found on the mirrors as well. The values need to match, otherwise the downloaded file might be corrupt (or the digests file is). </p> +<p> +Just like with the ISO file, you can also verify the cryptographic signature of +the <path>.DIGESTS.asc</path> file using <c>gpg</c> to make sure the checksums +have not been tampered with: +</p> + +<pre caption="Validating the checksums using gpg"> +# <i>gpg --verify <keyval id="stage3" />.DIGESTS.asc</i> +</pre> + </body> </subsection> <subsection>
