summaryrefslogtreecommitdiff
path: root/man/man8/monkeysphere-server.8
blob: 8e7278bd4273cefa51757f874e148d2b8547cd56 (plain)
  1. .TH MONKEYSPHERE-SERVER "8" "June 2008" "monkeysphere" "User Commands"
  2. .SH NAME
  3. monkeysphere-server \- Monkeysphere server admin user interface
  4. .SH SYNOPSIS
  5. .B monkeysphere-server \fIsubcommand\fP [\fIargs\fP]
  6. .SH DESCRIPTION
  7. \fBMonkeysphere\fP is a framework to leverage the OpenPGP web of trust
  8. for OpenSSH authentication. OpenPGP keys are tracked via GnuPG, and
  9. added to the authorized_keys and known_hosts files used by OpenSSH for
  10. connection authentication.
  11. \fBmonkeysphere-server\fP is the Monkeysphere server admin utility.
  12. .SH SUBCOMMANDS
  13. \fBmonkeysphere-server\fP takes various subcommands:
  14. .TP
  15. .B update-users [ACCOUNT]...
  16. Rebuild the monkeysphere-controlled authorized_keys files. For each
  17. specified account, the user ID's listed in the account's
  18. authorized_user_ids file are processed. For each user ID, gpg will be
  19. queried for keys associated with that user ID, optionally querying a
  20. keyserver. If an acceptable key is found (see KEY ACCEPTABILITY in
  21. monkeysphere(5)), the key is added to the account's
  22. monkeysphere-controlled authorized_keys file. If the
  23. RAW_AUTHORIZED_KEYS variable is set, then a separate authorized_keys
  24. file (usually ~USER/.ssh/authorized_keys) is appended to the
  25. monkeysphere-controlled authorized_keys file. If no accounts are
  26. specified, then all accounts on the system are processed. `u' may be
  27. used in place of `update-users'.
  28. .TP
  29. .B gen-key [HOSTNAME]
  30. Generate a OpenPGP key pair for the host. If HOSTNAME is not
  31. specified, then the system fully-qualified domain name will be user.
  32. An alternate key bit length can be specified with the `-l' or
  33. `--length' option (default 2048). An expiration length can be
  34. specified with the `-e' or `--expire' option (prompt otherwise). A
  35. key revoker fingerprint can be specified with the `-r' or `--revoker'
  36. option. `g' may be used in place of `gen-key'.
  37. .TP
  38. .B add-hostname HOSTNAME
  39. Add a hostname user ID to the server host key. `n+' may be used in
  40. place of `add-hostname'.
  41. .TP
  42. .B revoke-hostname HOSTNAME
  43. Revoke a hostname user ID from the server host key. `n-' may be used
  44. in place of `revoke-hostname'.
  45. .TP
  46. .B show-key
  47. Output gpg information about host's OpenPGP key. `s' may be used in
  48. place of `show-key'.
  49. .TP
  50. .B fingerprint
  51. Output just the fingerprint for the host's OpenPGP key. `f' may be
  52. used in place of `fingerprint'.
  53. .TP
  54. .B publish-key
  55. Publish the host's OpenPGP key to the keyserver. `p' may be used in
  56. place of `publish-key'.
  57. .TP
  58. .B diagnostics
  59. Review the state of the server with respect to the MonkeySphere in
  60. general and report on suggested changes. Among other checks, this
  61. includes making sure there is a valid host key, that the key is
  62. published, that the sshd configuration points to the right place, and
  63. that there are at least some valid identity certifiers. `d' may be
  64. used in place of `diagnostics'.
  65. .TP
  66. .B add-identity-certifier KEYID
  67. Instruct system to trust user identity certifications made by KEYID.
  68. Using the `-n' or `--domain' option allows you to indicate that you
  69. only trust the given KEYID to make identifications within a specific
  70. domain (e.g. "trust KEYID to certify user identities within the
  71. @example.org domain"). A certifier trust level can be specified with
  72. the `-t' or `--trust' option (possible values are `marginal' and
  73. `full' (default is `full')). A certifier trust depth can be specified
  74. with the `-d' or `--depth' option (default is 1). `c+' may be used in
  75. place of `add-identity-certifier'.
  76. .TP
  77. .B remove-identity-certifier KEYID
  78. Instruct system to ignore user identity certifications made by KEYID.
  79. `c-' may be used in place of `remove-identity-certifier'.
  80. .TP
  81. .B list-identity-certifiers
  82. List key IDs trusted by the system to certify user identities. `c'
  83. may be used in place of `list-identity-certifiers'.
  84. .TP
  85. .B gpg-authentication-cmd
  86. Execute a gpg command on the gnupg-authentication keyring as the
  87. monkeysphere user. This takes a single command (multiple gpg
  88. arguments need to be quoted). Use this command with caution, as
  89. modifying the gnupg-authentication keyring can affect ssh user
  90. authentication.
  91. .TP
  92. .B help
  93. Output a brief usage summary. `h' or `?' may be used in place of
  94. `help'.
  95. .SH SETUP
  96. In order to start using the monkeysphere, you must first generate an
  97. OpenPGP key for the server and convert that key to an ssh key that can
  98. be used by ssh for host authentication. This can be done with the
  99. \fBgen-key\fP subcommand:
  100. $ monkeysphere-server gen-key
  101. To enable host verification via the monkeysphere, you must then
  102. publish the host's key to the Web of Trust using the \fBpublish-key\fP
  103. command to push the key to a keyserver. You must also modify the
  104. sshd_config on the server to tell sshd where the new server host key
  105. is located:
  106. HostKey /var/lib/monkeysphere/ssh_host_rsa_key
  107. In order for users logging into the system to be able to verify the
  108. host via the monkeysphere, at least one person (e.g. a server admin)
  109. will need to sign the host's key. This is done using standard key
  110. signing techniquies, usually by pulling the key from the keyserver,
  111. signing the key, and re-publishing the signature. Once that is done,
  112. users logging into the host will be able to certify the host's key via
  113. the signature of the host admin.
  114. If the server will also handle user authentication through
  115. monkeysphere-generated authorized_keys files, the server must be told
  116. which keys will act as user certifiers. This is done with the
  117. \fBadd-certifier\fP command:
  118. $ monkeysphere-server add-certifier KEYID
  119. where KEYID is the key ID of the server admin, or whoever's signature
  120. will be certifying users to the system. Certifiers can be removed
  121. with the \fBremove-certifier\fP command, and listed with the
  122. \fBlist-certifiers\fP command.
  123. Remote user's will then be granted access to a local user account
  124. based on the appropriately signed and valid keys associated with user
  125. IDs listed in the authorized_user_ids file of the local user. By
  126. default, the authorized_user_ids file for local users is found in
  127. ~/.config/monkeysphere/authorized_user_ids. This can be changed in
  128. the monkeysphere-server.conf file.
  129. The \fBupdate-users\fP command can then be used to generate
  130. authorized_keys file for local users based on the authorized user IDs
  131. listed in the various local user's authorized_user_ids file:
  132. $ monkeysphere-server update-users USER
  133. Not specifying a specific user will cause all users on the system to
  134. updated. sshd can then use these monkeysphere generated
  135. authorized_keys files to grant access to user accounts for remote
  136. users. You must also tell sshd to look at the monkeysphere-generated
  137. authorized_keys file for user authentication by setting the following
  138. in the sshd_config:
  139. AuthorizedKeysFile /var/lib/monkeysphere/authorized_keys/%u
  140. It is recommended to add "monkeysphere-server update-users" to a
  141. system crontab, so that user keys are kept up-to-date, and key
  142. revocations and expirations can be processed in a timely manor.
  143. .SH ENVIRONMENT
  144. The following environment variables will override those specified in
  145. the monkeysphere-server.conf configuration file (defaults in
  146. parentheses):
  147. .TP
  148. MONKEYSPHERE_KEYSERVER
  149. OpenPGP keyserver to use (subkeys.pgp.net).
  150. .TP
  151. MONKEYSPHERE_AUTHORIZED_USER_IDS
  152. Path to user authorized_user_ids file
  153. (%h/.config/monkeysphere/authorized_user_ids).
  154. .TP
  155. MONKEYSPHERE_RAW_AUTHORIZED_KEYS
  156. Path to user-controlled authorized_keys file. `-' means not to add
  157. user-controlled file (%h/.ssh/authorized_keys).
  158. .TP
  159. MONKEYSPHERE_MONKEYSPHERE_USER
  160. User to control authentication keychain (monkeysphere).
  161. .SH FILES
  162. .TP
  163. /etc/monkeysphere/monkeysphere-server.conf
  164. System monkeysphere-server config file.
  165. .TP
  166. /etc/monkeysphere/monkeysphere.conf
  167. System-wide monkeysphere config file.
  168. .TP
  169. /var/lib/monkeysphere/authorized_keys/USER
  170. Monkeysphere-generated user authorized_keys files.
  171. .TP
  172. /var/lib/monkeysphere/ssh_host_rsa_key
  173. Copy of the host's private key in ssh format, suitable for use by
  174. sshd.
  175. .TP
  176. /var/lib/monkeysphere/gnupg-host
  177. Monkeysphere host GNUPG home directory.
  178. .TP
  179. /var/lib/monkeysphere/gnupg-authentication
  180. Monkeysphere authentication GNUPG home directory.
  181. .SH AUTHOR
  182. Written by Jameson Rollins <jrollins@fifthhorseman.net>, Daniel Kahn
  183. Gillmor <dkg@fifthhorseman.net>
  184. .SH SEE ALSO
  185. .BR monkeysphere (1),
  186. .BR monkeysphere (5),
  187. .BR gpg (1),
  188. .BR ssh (1)