Attachment 120977 Details for Bug 163866 – tsshbatch.1.patch.txt

tsshbatch.1.patch.txt

tsshbatch.1.patch.txt (text/plain; charset=us-ascii), 2.07 KB, created by Jason Helfman on 2012-01-11 19:07:42 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Jason Helfman

Created: 2012-01-11 19:07:42 UTC

Size: 2.07 KB

patch

obsolete

>--- tsshbatch.1.orig	2012-01-11 10:51:22.000000000 -0800
>+++ tsshbatch.1	2012-01-11 10:54:10.000000000 -0800
>@@ -91,7 +91,7 @@
> 
>             This method is handy when there are standard "sets" of hosts on
>             which you regularly work. For instance, you may wish to keep a host
>-            file lis for each of your production hosts, each of your test
>+            file list for each of your production hosts, each of your test
>             hosts, each of your AIX hosts, and so on.
> 
>  2. Authentication Using Name And Password
>@@ -101,7 +101,7 @@
> 
>     tsshbatch.py linux-prod-hosts uptime
> 
>-    You will be promted for your username and password one time which tsshbatch
>+    You will be prompted for your username and password one time which tsshbatch
>     will then use to log into each of the machines named in linux-prod-hosts. (
>     Notice that his assumes your name and password are the same on each host!)
> 
>@@ -189,8 +189,8 @@
>     For most applications of tsshbatch, it is much simpler to use key-based
>     authentication. For this to work, you must first have pushed ssh keys to
>     all your hosts. You then instruct tsshbatch to use key-based authentication
>-    rather than name and password. Not only does this elimintate the need to
>-    constantly provide name and passowrd, it also eliminates passing a plain
>+    rather than name and password. Not only does this eliminate the need to
>+    constantly provide name and password, it also eliminates passing a plain
>     text password on the command line and is thus far more secure. This also
>     overcomes the problem of having different name/password credentials on
>     different hosts.
>@@ -205,7 +205,7 @@
> 
>     tsshbatch is smart enough to handle commands that begin with sudo. It knows
>     that such commands require a password even if you used key exchange to
>-    intially log in. That's because, once you are logged in - whether via name/
>+    initially log in. That's because, once you are logged in - whether via name/
>     password or via key exchange - sudo requires your password again to promote
>     your privileges.
>

Actions: View

Attachments on bug 163866: 120977 | 120978 | 120979