summaryrefslogtreecommitdiff
path: root/man/man1/monkeysphere.1
blob: 07cd3ea80e82d385093c8338e880a449ef69178a (plain)
  1. .TH MONKEYSPHERE "1" "June 2008" "monkeysphere 0.1" "User Commands"
  2. .SH NAME
  3. monkeysphere \- MonkeySphere client user interface
  4. .SH SYNOPSIS
  5. .B monkeysphere \fIsubcommand\fP [\fIargs\fP]
  6. .SH DESCRIPTION
  7. \fBMonkeySphere\fP is a framework to leverage the OpenPGP Web of Trust
  8. for ssh authentication. OpenPGP keys are tracked via GnuPG, and added
  9. to the authorized_keys and known_hosts files used by ssh for
  10. connection authentication.
  11. \fBmonkeysphere\fP is the MonkeySphere client utility.
  12. .SH SUBCOMMANDS
  13. \fBmonkeysphere\fP takes various subcommands:
  14. .TP
  15. .B update-known_hosts [HOST]...
  16. Update the known_hosts file. For each specified host, gpg will be
  17. queried for a key associated with the host URI (see HOST
  18. IDENTIFICATION in monkeysphere(5)), optionally querying a keyserver.
  19. If an acceptable key is found for the host (see KEY ACCEPTABILITY in
  20. monkeysphere(5)), the key is added to the user's known_hosts file. If
  21. a key is found but is unacceptable for the host, any matching keys are
  22. removed from the user's known_hosts file. If no gpg key is found for
  23. the host, nothing is done. If no hosts are specified, all hosts
  24. listed in the known_hosts file will be processed. This subcommand
  25. will exit with a status of 0 if at least one acceptable key was found
  26. for a specified host, 1 if no matching keys were found at all, and 2
  27. if matching keys were found but none were acceptable. `k' may be used
  28. in place of `update-known_hosts'.
  29. .TP
  30. .B update-authorized_keys
  31. Update the monkeysphere authorized_keys file. For each user ID in the
  32. user's authorized_user_ids file, gpg will be queried for keys
  33. associated with that user ID, optionally querying a keyserver. If an
  34. acceptable key is found (see KEY ACCEPTABILITY in monkeysphere(5)),
  35. the key is add to the user's authorized_keys file. If a key is found
  36. but is unacceptable for the user ID, any matching keys are removed
  37. from the user's authorized_keys file. If no gpg key is found for the
  38. user ID, nothing is done. This subcommand will exit with a status of
  39. 0 if at least one acceptable key was found for a user ID, 1 if no
  40. matching keys wer found at all, and 2 if matching keys were found but
  41. none were acceptable. `a' may be used in place of
  42. `update-authorized_keys'.
  43. .TP
  44. .B gen-subkey KEYID
  45. Generate an authentication subkey. For the primary key with the
  46. specified key ID, generate a subkey with "authentication" capability
  47. that can be used for monkeysphere transactions. `g' may be used in
  48. place of `gen-subkey'.
  49. .TP
  50. .B help
  51. Output a brief usage summary. `h' or `?' may be used in place of
  52. `help'.
  53. .SH FILES
  54. .TP
  55. ~/.config/monkeysphere/monkeysphere.conf
  56. User monkeysphere config file.
  57. .TP
  58. /etc/monkeysphere/monkeysphere.conf
  59. System-wide monkeysphere config file.
  60. .TP
  61. ~/.config/monkeysphere/authorized_user_ids
  62. OpenPGP user IDs associated with keys that will be checked for
  63. addition to the authorized_keys file.
  64. .SH AUTHOR
  65. Written by Jameson Rollins <jrollins@fifthhorseman.net>, Daniel
  66. Kahn Gillmor <dkg@fifthhorseman.net>
  67. .SH SEE ALSO
  68. .BR monkeysphere-ssh-proxycommand (1),
  69. .BR monkeysphere-server (8),
  70. .BR monkeysphere (5),
  71. .BR ssh (1),
  72. .BR gpg (1)