rane 05/09/29 21:51:19
Modified: xml/htdocs/doc/en/articles openssh-key-management-p1.xml
openssh-key-management-p2.xml
openssh-key-management-p3.xml
Log:
just a few final touch ups
Revision Changes Path
1.2 +5 -5 xml/htdocs/doc/en/articles/openssh-key-management-p1.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/articles/openssh-key-management-p1.xml?rev=1.2&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/articles/openssh-key-management-p1.xml?rev=1.2&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/articles/openssh-key-management-p1.xml.diff?r1=1.1&r2=1.2&cvsroot=gentoo
Index: openssh-key-management-p1.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/articles/openssh-key-management-p1.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- openssh-key-management-p1.xml 29 Sep 2005 20:59:13 -0000 1.1
+++ openssh-key-management-p1.xml 29 Sep 2005 21:51:19 -0000 1.2
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/articles/openssh-key-management-p1.xml,v 1.1 2005/09/29 20:59:13 rane Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/articles/openssh-key-management-p1.xml,v 1.2 2005/09/29 21:51:19 rane Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
<guide link="/doc/en/articles/openssh-key-management-p1.xml">
@@ -266,7 +266,7 @@
</p>
<pre caption="Logging in with passphrase">
-# <i>ssh drobbins@remotebox</i>
+$ <i>ssh drobbins@remotebox</i>
Enter passphrase for key '/home/drobbins/.ssh/identity': <comment>(enter passphrase)</comment>
Last login: Thu Jun 28 20:28:47 2001 from localbox.gentoo.org
@@ -448,11 +448,11 @@
<ul>
<li>
- Read Daniel's other two articles in this series, "<uri
+ Read Daniel's other two articles in this series, <uri
link="/doc/en/articles/openssh-key-management-p2.xml">OpenSSH key
- management, Part 2</uri>" and "<uri
+ management, Part 2</uri> and <uri
link="/doc/en/articles/openssh-key-management-p3.xml">OpenSSH key
- management, Part 3</uri>".
+ management, Part 3</uri>
</li>
<li>
Be sure to visit the home of <uri
1.2 +2 -2 xml/htdocs/doc/en/articles/openssh-key-management-p2.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/articles/openssh-key-management-p2.xml?rev=1.2&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/articles/openssh-key-management-p2.xml?rev=1.2&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/articles/openssh-key-management-p2.xml.diff?r1=1.1&r2=1.2&cvsroot=gentoo
Index: openssh-key-management-p2.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/articles/openssh-key-management-p2.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- openssh-key-management-p2.xml 29 Sep 2005 20:59:13 -0000 1.1
+++ openssh-key-management-p2.xml 29 Sep 2005 21:51:19 -0000 1.2
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/articles/openssh-key-management-p2.xml,v 1.1 2005/09/29 20:59:13 rane Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/articles/openssh-key-management-p2.xml,v 1.2 2005/09/29 21:51:19 rane Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
<guide link="/doc/en/articles/openssh-key-management-p2.xml">
@@ -118,7 +118,7 @@
</p>
<pre caption="Loading private RSA key to ssh-agent's cache">
-# <i>ssh-add ~/.ssh/identity</i>
+$ <i>ssh-add ~/.ssh/identity</i>
Need passphrase for /home/drobbins/.ssh/identity
Enter passphrase for /home/drobbins/.ssh/identity
(enter passphrase)
1.2 +25 -23 xml/htdocs/doc/en/articles/openssh-key-management-p3.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/articles/openssh-key-management-p3.xml?rev=1.2&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/articles/openssh-key-management-p3.xml?rev=1.2&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/articles/openssh-key-management-p3.xml.diff?r1=1.1&r2=1.2&cvsroot=gentoo
Index: openssh-key-management-p3.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/articles/openssh-key-management-p3.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- openssh-key-management-p3.xml 29 Sep 2005 20:59:13 -0000 1.1
+++ openssh-key-management-p3.xml 29 Sep 2005 21:51:19 -0000 1.2
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/articles/openssh-key-management-p3.xml,v 1.1 2005/09/29 20:59:13 rane Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/articles/openssh-key-management-p3.xml,v 1.2 2005/09/29 21:51:19 rane Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
<guide link="/doc/en/articles/openssh-key-management-p3.xml">
@@ -498,21 +498,21 @@
does a "dry run" of ps uxw, throwing away any output. If the error code from
this command is zero, we know that ps uxw works and we set the psopts value
appropriately. However, if ps uxw returned a non-zero error code (indicating
-that we need to use BSD-style options), we do a dry-run of ps -u `whoami` -f,
-again throwing away all output. At this point, hopefully we've found either a
-BSD or System V variant of ps that we can use. If we haven't, we print out an
-error and exit. But it is very likely that one of the two ps commands worked,
-in which case we execute the final line in the above code snippet, our ps
-pipeline. By using the $psopts variable expansion immediately after ps, we're
-able to pass the correct options to the ps command.
+that we need to use BSD-style options), we do a dry-run of <c>ps -u `whoami`
+-f</c>, again throwing away all output. At this point, hopefully we've found
+either a BSD or System V variant of ps that we can use. If we haven't, we print
+out an error and exit. But it is very likely that one of the two ps commands
+worked, in which case we execute the final line in the above code snippet, our
+ps pipeline. By using the $psopts variable expansion immediately after ps,
+we're able to pass the correct options to the ps command.
</p>
<p>
The ps pipeline also contains a true grep gem, which was kindly sent to me by
-Hans Peter Verne. Notice that grep -v grep is no longer part of the pipeline;
-instead, it has been removed and grep "ssh-agent" has been changed to grep
-"[s]sh-agent". This single grep command ends up doing the same thing as grep
-ssh-agent | grep -v grep; can you figure out why?
+Hans Peter Verne. Notice that <c>grep -v grep</c> is no longer part of the
+pipeline; instead, it has been removed and <c>grep "ssh-agent"</c> has been
+changed to grep <c>"[s]sh-agent"</c>. This single grep command ends up doing
+the same thing as <c>grep ssh-agent | grep -v grep</c>; can you figure out why?
</p>
<pre caption="Neat grep trick">
@@ -520,14 +520,14 @@
</pre>
<p>
-Stumped? If you've decided that a grep "ssh-agent" and grep "[s]sh-agent"
-should match the exact same lines of text, you are correct. So why do they
-generate different results when the output of ps is piped to them? Here's how
-it works: when you use grep "[s]sh-agent", you change how the grep command
-appears in the ps process list. By doing so, you prevent grep from matching
-itself, since the [s]sh-agent string doesn't match the [s]sh-agent regular
-expression. Isn't that brilliant? If you still don't get it, play around with
-grep a bit more and you'll get it soon enough.
+Stumped? If you've decided that a <c>grep "ssh-agent"</c> and <c>grep
+"[s]sh-agent"</c> should match the exact same lines of text, you are correct.
+So why do they generate different results when the output of ps is piped to
+them? Here's how it works: when you use grep "[s]sh-agent", you change how the
+grep command appears in the ps process list. By doing so, you prevent grep from
+matching itself, since the [s]sh-agent string doesn't match the [s]sh-agent
+regular expression. Isn't that brilliant? If you still don't get it, play
+around with grep a bit more and you'll get it soon enough.
</p>
</body>
@@ -555,8 +555,10 @@
<ul>
<li>
Read Daniel's other two articles in this series, <uri
- link="/doc/en/articles/openssh-key-management-p1.xml">Part 1</uri> and
- "<uri link="/doc/en/articles/openssh-key-management-p2.xml">Part 2</uri>.
+ link="/doc/en/articles/openssh-key-management-p1.xml">OpenSSH key
+ management, Part 1</uri> and <uri
+ link="/doc/en/articles/openssh-key-management-p2.xml">OpenSSH key
+ management, Part 2</uri>
</li>
<li>
The most recent version of keychain is available on the <uri
@@ -570,7 +572,7 @@
</li>
<li>
<uri link="http://www.chiark.greenend.org.uk/~sgtatham/putty/">PuTTY</uri>
- is an excellent ssh client for Windows machines.
+ is an excellent ssh client for Windows machines
</li>
<li>
The book "SSH, The Secure Shell: The Definitive Guide" (O'Reilly &
--
gentoo-doc-cvs@g.o mailing list
|
