swift 06/03/11 16:44:44 Modified: shb-services.xml Log: Explain how to add a key to the authorized_keys file, noted by Nathan L. Adams
Revision Changes Path 1.3 xml/htdocs/doc/en/security/shb-services.xml file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/security/shb-services.xml?rev=1.3&content-type=text/x-cvsweb-markup&cvsroot=gentoo plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/security/shb-services.xml?rev=1.3&content-type=text/plain&cvsroot=gentoo diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/security/shb-services.xml.diff?r1=1.2&r2=1.3&cvsroot=gentoo Index: shb-services.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/security/shb-services.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- shb-services.xml 1 Jun 2005 17:42:46 -0000 1.2 +++ shb-services.xml 11 Mar 2006 16:44:44 -0000 1.3 @@ -1,5 +1,5 @@ <?xml version='1.0' encoding='UTF-8'?> -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/security/shb-services.xml,v 1.2 2005/06/01 17:42:46 neysx Exp $ --> +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/security/shb-services.xml,v 1.3 2006/03/11 16:44:44 swift Exp $ --> <!DOCTYPE sections SYSTEM "/dtd/book.dtd"> <!-- The content of this document is licensed under the CC-BY-SA license --> @@ -7,8 +7,8 @@ <sections> -<version>1.0</version> -<date>2005-05-31</date> +<version>1.1</version> +<date>2006-03-11</date> <section> <title>Apache</title> @@ -438,9 +438,16 @@ <path>id_dsa</path> is your private key and should be kept from other people than yourself. The other file <path>id_dsa.pub</path> is to be distributed to every server that you have access to. Add the key to the users home directory -in <path>~/.ssh/authorized_keys</path> and the user should be able to login. +in <path>~/.ssh/authorized_keys</path> and the user should be able to login: </p> +<pre caption="Adding the id_dsa.pub file to the authorized_keys file"> +$ <i>scp id_dsa.pub other-host:/var/tmp/currenthostname.pub</i> +$ <i>ssh other-host</i> +password: +$ <i>cat /var/tmp/currenthostname.pub >> ~/.ssh/authorized_keys</i> +</pre> + <p> Now your users should guard this private key well. Put it on a media that they always carry with them or keep it on their workstation (put this in the <uri -- [email protected] mailing list
