[gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en/handbook: hb-working-features.xml

["Sven Vermeulen (swift)" <swift@gentoo.org>]

swift       11/10/27 18:33:42

  Modified:             hb-working-features.xml
  Log:
  As per Jan ("jkt") feedback, ensure that directory is 0700 and mention key fingerprint (currently valid, but might change in november as the key expires then)

Revision  Changes    Path
1.39                 xml/htdocs/doc/en/handbook/hb-working-features.xml

file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-working-features.xml?rev=1.39&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-working-features.xml?rev=1.39&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-working-features.xml?r1=1.38&r2=1.39

Index: hb-working-features.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-features.xml,v
retrieving revision 1.38
retrieving revision 1.39
diff -u -r1.38 -r1.39
--- hb-working-features.xml	26 Oct 2011 19:46:19 -0000	1.38
+++ hb-working-features.xml	27 Oct 2011 18:33:42 -0000	1.39
@@ -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-working-features.xml,v 1.38 2011/10/26 19:46:19 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-features.xml,v 1.39 2011/10/27 18:33:42 swift Exp $ -->
 
 <sections>
 
@@ -13,8 +13,8 @@
 ccache and more.
 </abstract>
 
-<version>2</version>
-<date>2011-10-26</date>
+<version>3</version>
+<date>2011-10-27</date>
 
 <section>
 <title>Portage Features</title>
@@ -345,11 +345,14 @@
 To configure Portage, first create a truststore in which you download and accept
 the keys of the Gentoo Infrastructure responsible for signing the Portage tree
 snapshots. Of course, if you want to, you can validate this GPG key as per the
-<uri link="/doc/en/gnupg-user.xml#doc_chap2_sect4">proper guidelines</uri>.
+<uri link="/doc/en/gnupg-user.xml#doc_chap2_sect4">proper guidelines</uri>
+(like checking the key fingerprint <c>AE54 54F9 67B5 6AB0 9AE1 6064 0838
+C26E 239C 75C4</c>).
 </p>
 
 <pre caption="Creating a truststore for Portage">
 # <i>mkdir -p /etc/portage/gpg</i>
+# <i>chmod 0700 /etc/portage/gpg</i>
 # <i>gpg --homedir /etc/portage/gpg --keyserver subkeys.pgp.net --recv-keys 0x239C75C4</i>
 # <i>gpg --homedir /etc/portage/gpg --edit-key 0x239C75C4 trust</i>
 </pre>