summaryrefslogtreecommitdiff
path: root/man/man8/monkeysphere-authentication.8
blob: 38df65dbf396d659dfe6efe23ebaad303aba9241 (plain)
  1. .TH MONKEYSPHERE-SERVER "8" "June 2008" "monkeysphere" "User Commands"
  2. .SH NAME
  3. monkeysphere-authentication \- Monkeysphere authentication admin tool.
  4. .SH SYNOPSIS
  5. .B monkeysphere-authentication \fIsubcommand\fP [\fIargs\fP]
  6. .br
  7. .B monkeysphere-authentication expert \fIexpert-subcommand\fP [\fIargs\fP]
  8. .SH DESCRIPTION
  9. \fBMonkeysphere\fP is a framework to leverage the OpenPGP web of trust for
  10. OpenSSH authentication. OpenPGP keys are tracked via GnuPG, and added to the
  11. authorized_keys and known_hosts files used by OpenSSH for connection
  12. authentication.
  13. \fBmonkeysphere-authentication\fP is a Monkeysphere server admin utility.
  14. .SH SUBCOMMANDS
  15. \fBmonkeysphere-authentication\fP takes various subcommands:
  16. .TP
  17. .B update-users [ACCOUNT]...
  18. Rebuild the monkeysphere-controlled authorized_keys files. For each
  19. specified account, the user ID's listed in the account's
  20. authorized_user_ids file are processed. For each user ID, gpg will be
  21. queried for keys associated with that user ID, optionally querying a
  22. keyserver. If an acceptable key is found (see KEY ACCEPTABILITY in
  23. monkeysphere(7)), the key is added to the account's
  24. monkeysphere-controlled authorized_keys file. If the
  25. RAW_AUTHORIZED_KEYS variable is set, then a separate authorized_keys
  26. file (usually ~USER/.ssh/authorized_keys) is appended to the
  27. monkeysphere-controlled authorized_keys file. If no accounts are
  28. specified, then all accounts on the system are processed. `u' may be
  29. used in place of `update-users'.
  30. .TP
  31. .B add-id-certifier KEYID
  32. Instruct system to trust user identity certifications made by KEYID.
  33. Using the `-n' or `--domain' option allows you to indicate that you
  34. only trust the given KEYID to make identifications within a specific
  35. domain (e.g. "trust KEYID to certify user identities within the
  36. @example.org domain"). A certifier trust level can be specified with
  37. the `-t' or `--trust' option (possible values are `marginal' and
  38. `full' (default is `full')). A certifier trust depth can be specified
  39. with the `-d' or `--depth' option (default is 1). `c+' may be used in
  40. place of `add-id-certifier'.
  41. .TP
  42. .B remove-id-certifier KEYID
  43. Instruct system to ignore user identity certifications made by KEYID.
  44. `c-' may be used in place of `remove-id-certifier'.
  45. .TP
  46. .B list-id-certifiers
  47. List key IDs trusted by the system to certify user identities. `c'
  48. may be used in place of `list-id-certifiers'.
  49. .TP
  50. .B help
  51. Output a brief usage summary. `h' or `?' may be used in place of
  52. `help'.
  53. .TP
  54. .B version
  55. show version number
  56. Other commands:
  57. .TP
  58. .B setup
  59. Setup the server for Monkeysphere user authentication. This command
  60. is idempotent and run automatically by the other commands, and should
  61. therefore not usually need to be run manually. `s' may be used in
  62. place of `setup'.
  63. .TP
  64. .B diagnostics
  65. Review the state of the server with respect to authentication. `d'
  66. may be used in place of `diagnostics'.
  67. .TP
  68. .B gpg-cmd
  69. Execute a gpg command, as the monkeysphere user, on the monkeysphere
  70. authentication "sphere" keyring. This takes a single argument
  71. (multiple gpg arguments need to be quoted). Use this command with
  72. caution, as modifying the authentication sphere keyring can affect ssh
  73. user authentication.
  74. .SH SETUP USER AUTHENTICATION
  75. If the server will handle user authentication through
  76. monkeysphere-generated authorized_keys files, the server must be told
  77. which keys will act as identity certifiers. This is done with the
  78. \fBadd-id-certifier\fP command:
  79. $ monkeysphere-authentication add-id-certifier KEYID
  80. where KEYID is the key ID of the server admin, or whoever's
  81. certifications should be acceptable to the system for the purposes of
  82. authenticating remote users. You can run this command multiple times
  83. to indicate that multiple certifiers are trusted. You may also
  84. specify a filename instead of a key ID, as long as the file contains a
  85. single OpenPGP public key. Certifiers can be removed with the
  86. \fBremove-id-certifier\fP command, and listed with the
  87. \fBlist-id-certifiers\fP command.
  88. Remote users will then be granted access to a local account based on
  89. the appropriately-signed and valid keys associated with user IDs
  90. listed in that account's authorized_user_ids file. By default, the
  91. authorized_user_ids file for an account is
  92. ~/.monkeysphere/authorized_user_ids. This can be changed in the
  93. monkeysphere-authentication.conf file.
  94. The \fBupdate-users\fP command can then be used to generate
  95. authorized_keys file for local accounts based on the authorized user
  96. IDs listed in the account's authorized_user_ids file:
  97. $ monkeysphere-authentication update-users USER
  98. Not specifying USER will cause all accounts on the system to updated.
  99. sshd can then use these monkeysphere generated authorized_keys files
  100. to grant access to user accounts for remote users. You must also tell
  101. sshd to look at the monkeysphere-generated authorized_keys file for
  102. user authentication by setting the following in the sshd_config:
  103. AuthorizedKeysFile /var/lib/monkeysphere/authentication/authorized_keys/%u
  104. It is recommended to add "monkeysphere-authentication update-users" to a
  105. system crontab, so that user keys are kept up-to-date, and key
  106. revocations and expirations can be processed in a timely manner.
  107. .SH ENVIRONMENT
  108. The following environment variables will override those specified in
  109. the config file (defaults in parentheses):
  110. .TP
  111. MONKEYSPHERE_MONKEYSPHERE_USER
  112. User to control authentication keychain. (monkeysphere)
  113. .TP
  114. MONKEYSPHERE_LOG_LEVEL
  115. Set the log level. Can be SILENT, ERROR, INFO, VERBOSE, DEBUG, in
  116. increasing order of verbosity. (INFO)
  117. .TP
  118. MONKEYSPHERE_KEYSERVER
  119. OpenPGP keyserver to use. (pool.sks-keyservers.net)
  120. .TP
  121. MONKEYSPHERE_AUTHORIZED_USER_IDS
  122. Path to user's authorized_user_ids file. %h gets replaced with the
  123. user's homedir, %u with the username.
  124. (%h/.monkeysphere/authorized_user_ids)
  125. .TP
  126. MONKEYSPHERE_RAW_AUTHORIZED_KEYS
  127. Path to regular ssh-style authorized_keys file to append to
  128. monkeysphere-generated authorized_keys. `none' means not to add any
  129. raw authorized_keys file. %h gets replaced with the user's homedir,
  130. %u with the username. (%h/.ssh/authorized_keys)
  131. .TP
  132. MONKEYSPHERE_PROMPT
  133. If set to `false', never prompt the user for confirmation. (true)
  134. .SH FILES
  135. .TP
  136. /etc/monkeysphere/monkeysphere-authentication.conf
  137. System monkeysphere-authentication config file.
  138. .TP
  139. /var/lib/monkeysphere/authorized_keys/USER
  140. Monkeysphere-generated user authorized_keys files.
  141. .SH AUTHOR
  142. Written by:
  143. Jameson Rollins <jrollins@fifthhorseman.net>,
  144. Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
  145. Matthew Goins <mjgoins@openflows.com>
  146. .SH SEE ALSO
  147. .BR monkeysphere (1),
  148. .BR monkeysphere-host (8),
  149. .BR monkeysphere (7),
  150. .BR gpg (1),
  151. .BR ssh (1)