diff options
Diffstat (limited to 'man')
| -rw-r--r-- | man/man1/monkeysphere-ssh-proxycommand.1 | 8 | ||||
| -rw-r--r-- | man/man1/monkeysphere.1 | 2 | ||||
| -rw-r--r-- | man/man8/monkeysphere-server.8 | 6 |
3 files changed, 8 insertions, 8 deletions
diff --git a/man/man1/monkeysphere-ssh-proxycommand.1 b/man/man1/monkeysphere-ssh-proxycommand.1 index 0e6d18d..a31a9d1 100644 --- a/man/man1/monkeysphere-ssh-proxycommand.1 +++ b/man/man1/monkeysphere-ssh-proxycommand.1 @@ -19,7 +19,7 @@ or by adding the following line to your ~/.ssh/config script: .B ProxyCommand monkeysphere-ssh-proxycommand %h %p The script can easily be incorporated into other ProxyCommand scripts -by calling it with the "--no-connect" option, ie: +by calling it with the "--no-connect" option, i.e.: .B monkeysphere-ssh-proxycommand --no-connect "$HOST" "$PORT" @@ -34,10 +34,10 @@ either the user's keyring or in the known_hosts file, then the keyserver is queried for the host userID. If the host userID is found in the user's keyring, then the keyserver is not checked. This assumes that the keyring is kept up-to-date, in a cron job or the -like, so that revokations are properly handled. If the host userID is +like, so that revocations are properly handled. If the host userID is not found in the user's keyring, but the host is listed in the known_hosts file, then the keyserver is not checked. This last policy -might change in the future, possibly by adding a defered check, so +might change in the future, possibly by adding a deferred check, so that hosts that go from non-monkeysphere-enabled to monkeysphere-enabled will be properly checked. @@ -57,6 +57,6 @@ Written by Jameson Rollins <jrollins@fifthhorseman.net> .SH SEE ALSO -.BR monkeypshere (1), +.BR monkeysphere (1), .BR ssh (1), .BR gpg (1) diff --git a/man/man1/monkeysphere.1 b/man/man1/monkeysphere.1 index 05376d0..cd3f45e 100644 --- a/man/man1/monkeysphere.1 +++ b/man/man1/monkeysphere.1 @@ -46,7 +46,7 @@ but is unacceptable for the user ID, any matching keys are removed from the user's authorized_keys file. If no gpg key is found for the user ID, nothing is done. This subcommand will exit with a status of 0 if at least one acceptable key was found for a user ID, 1 if no -matching keys wer found at all, and 2 if matching keys were found but +matching keys were found at all, and 2 if matching keys were found but none were acceptable. `a' may be used in place of `update-authorized_keys'. .TP diff --git a/man/man8/monkeysphere-server.8 b/man/man8/monkeysphere-server.8 index 97b2f38..4ae2d29 100644 --- a/man/man8/monkeysphere-server.8 +++ b/man/man8/monkeysphere-server.8 @@ -97,7 +97,7 @@ to tell sshd where the new server host key is located: HostKey /var/lib/monkeysphere/ssh_host_rsa_key In order for users logging into the system to be able to verify the -host via the monkeysphere, at least one person (ie. a server admin) +host via the monkeysphere, at least one person (i.e. a server admin) will need to sign the host's key. This is done in the same way that key signing is usually done, by pulling the host's key from the keyserver, signing the key, and re-publishing the signature. Once @@ -139,7 +139,7 @@ AuthorizedKeysFile /var/lib/monkeysphere/authorized_keys/%u It is recommended to add "monkeysphere-server update-users" to a system crontab, so that user keys are kept up-to-date, and key -revokations and expirations can be processed in a timely manor. +revocations and expirations can be processed in a timely manor. .SH ENVIRONMENT @@ -159,7 +159,7 @@ Path to user-controlled authorized_keys file. `-' means not to add user-controlled file (%h/.ssh/authorized_keys). .TP MONKEYSPHERE_MONKEYSPHERE_USER -User to control authentication keychain (monkeypshere). +User to control authentication keychain (monkeysphere). .SH FILES |