| 1 |
robbat2 07/12/24 09:21:44 |
| 2 |
|
| 3 |
Modified: cvs-sshkeys.xml |
| 4 |
Log: |
| 5 |
Update the old SSH key doc for LDAP. |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.4 xml/htdocs/proj/en/infrastructure/cvs-sshkeys.xml |
| 9 |
|
| 10 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/infrastructure/cvs-sshkeys.xml?rev=1.4&view=markup |
| 11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/infrastructure/cvs-sshkeys.xml?rev=1.4&content-type=text/plain |
| 12 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/infrastructure/cvs-sshkeys.xml?r1=1.3&r2=1.4 |
| 13 |
|
| 14 |
Index: cvs-sshkeys.xml |
| 15 |
=================================================================== |
| 16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/infrastructure/cvs-sshkeys.xml,v |
| 17 |
retrieving revision 1.3 |
| 18 |
retrieving revision 1.4 |
| 19 |
diff -p -w -b -B -u -u -r1.3 -r1.4 |
| 20 |
--- cvs-sshkeys.xml 5 Jul 2007 03:49:56 -0000 1.3 |
| 21 |
+++ cvs-sshkeys.xml 24 Dec 2007 09:21:44 -0000 1.4 |
| 22 |
@@ -8,12 +8,15 @@ |
| 23 |
<author title="Author"> |
| 24 |
<mail link="swift@g.o">Sven Vermeulen</mail> |
| 25 |
</author> |
| 26 |
+<author title="Author"> |
| 27 |
+ <mail link="robbat2@g.o">Robin H. Johnson</mail> |
| 28 |
+</author> |
| 29 |
<abstract> |
| 30 |
This mini-guide explains on how to create and use ssh-keys, especially |
| 31 |
for use on cvs.gentoo.org. |
| 32 |
</abstract> |
| 33 |
-<version>1.0</version> |
| 34 |
-<date>3rd of July, 2003</date> |
| 35 |
+<version>1.1</version> |
| 36 |
+<date>2007/12/24</date> |
| 37 |
|
| 38 |
<chapter> |
| 39 |
<title>SSH keys</title> |
| 40 |
@@ -83,6 +86,26 @@ $ <i>cat ~/.ssh/id_dsa.pub >> ~/.ssh/aut |
| 41 |
</body> |
| 42 |
</section> |
| 43 |
<section> |
| 44 |
+<title>Installing your public key on a machine using LDAP authentication for SSH</title> |
| 45 |
+<body> |
| 46 |
+<p> |
| 47 |
+For most of the Gentoo infrastructure, we use LDAP to distribute user |
| 48 |
+information including SSH public keys. On these machines, |
| 49 |
+<path>~/.ssh/authorized_keys</path> should generally not contain your key. |
| 50 |
+</p> |
| 51 |
+<p> |
| 52 |
+Instead, you should place your public key into LDAP, using |
| 53 |
+<path>perl_ldap</path>, or <path>ldapmodify</path> directly. |
| 54 |
+The Infrastructure <uri link="/proj/en/infrastructure/ldap.xml">LDAP |
| 55 |
+guide</uri> describes this in more detail. |
| 56 |
+</p> |
| 57 |
+<pre caption = "Adding the SSH key with perl_ldap on dev.gentoo.org"> |
| 58 |
+$ <i>perl_ldap -b user -C sshPublicKey "$(cat ~/.ssh/id_dsa.pub)" <username></i> |
| 59 |
+</pre> |
| 60 |
+<warn>Each <path>sshPublicKey</path> attribute must contain exactly one public key. If you have multiple public keys, you must have multiple attributes!</warn> |
| 61 |
+</body> |
| 62 |
+</section> |
| 63 |
+<section> |
| 64 |
<title>Using keychain</title> |
| 65 |
<body> |
| 66 |
<p> |
| 67 |
@@ -90,7 +113,7 @@ Every time you want to log on to a remot |
| 68 |
authentification, you will be asked to enter your passphrase. As much as |
| 69 |
everybody likes typing, too much is sometimes too much. Luckily, |
| 70 |
there is <c>keychain</c> to the rescue. There is an document on this |
| 71 |
-one <uri link="http://www.gentoo.org/proj/en/keychain.xml">here</uri>, |
| 72 |
+one <uri link="/proj/en/keychain.xml">here</uri>, |
| 73 |
but I'll give you a quick introduction. |
| 74 |
</p> |
| 75 |
<p> |
| 76 |
|
| 77 |
|
| 78 |
|
| 79 |
-- |
| 80 |
gentoo-commits@g.o mailing list |
Archives