summaryrefslogtreecommitdiff
path: root/man/man1/monkeysphere.1
blob: eb085bf6ae617da055f99de9b4272774ee166a1c (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 \fIcommand\fP [\fIargs\fP]
  6. .SH DESCRIPTION
  7. \fBMonkeySphere\fP is a system to leverage the OpenPGP Web of Trust
  8. for ssh authentication. OpenPGP keys are tracked via GnuPG, and added
  9. to the ssh authorized_keys and known_hosts files to be used for
  10. authentication of ssh connections.
  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 URIs),
  18. querying a keyserver if specified. If a key is found, it will be
  19. converted to an ssh key, and any matching ssh keys will be removed
  20. from the user's known_hosts file. If the found key is acceptable (see
  21. KEY ACCEPTABILITY), then the key will be updated and re-added to the
  22. known_hosts file. If no gpg key is found for the host, then nothing
  23. is done. If no hosts are specified, all hosts listed in the
  24. known_hosts file will be processed. `k' may be used in place of
  25. `update-known_hosts'.
  26. .TP
  27. .B update-authorized_keys
  28. Update the monkeysphere authorized_keys file. For each user ID in the
  29. user's authorized_user_ids file, gpg will be queried for keys
  30. associated with that user ID, querying a keyserver if specified. If a
  31. key is found, it will be converted to an ssh key, and any matching ssh
  32. keys will be removed from the user's authorized_keys file. If the
  33. found key is acceptable (see KEY ACCEPTABILITY), then the key will be
  34. updated and re-added to the authorized_keys file. If no gpg key is
  35. found for the user ID, then nothing is done. `a' may be used in place
  36. of `update-authorized_keys'.
  37. .TP
  38. .B gen-subkey KEYID
  39. Generate an `a` capable subkey. For the primary key with the
  40. specified key ID, generate a subkey with "authentication" capability
  41. that can be used for MonkeySphere transactions. `g' may be used in
  42. place of `gen-subkey'.
  43. .TP
  44. .B help
  45. Output a brief usage summary. `h' or `?' may be used in place of
  46. `help'.
  47. .SH HOST URIs
  48. Host OpenPGP keys have associated user IDs that use the ssh URI
  49. specification for the host, ie. "ssh://host.full.domain[:port]".
  50. .SH KEY ACCEPTABILITY
  51. GPG keys are considered acceptable if the following criteria are met:
  52. .TP
  53. .B capability
  54. The key must have the "authentication" ("a") usage flag set.
  55. .TP
  56. .B validity
  57. The key must be "fully" valid (ie. signed by a trusted certifier), and
  58. must not be expired or revoked.
  59. .SH FILES
  60. .TP
  61. ~/.config/monkeysphere/monkeysphere.conf
  62. User monkeysphere config file.
  63. .TP
  64. /etc/monkeysphere/monkeysphere.conf
  65. System-wide monkeysphere config file.
  66. .TP
  67. ~/.config/monkeysphere/authorized_user_ids
  68. OpenPGP user IDs associated with keys that will be checked for
  69. addition to the authorized_keys file.
  70. .SH AUTHOR
  71. Written by Jameson Rollins <jrollins@fifthhorseman.net>
  72. .SH SEE ALSO
  73. .BR monkeysphere-ssh-proxycommand (1),
  74. .BR monkeysphere-server (8),
  75. .BR ssh (1),
  76. .BR gpg (1)