summaryrefslogtreecommitdiff
path: root/man/man8/monkeysphere-authentication.8
blob: 68a7a1b60533fc9753ef9d119a5a5caa1319cc35 (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.(Users may use the
  16. abbreviated subcommand in parentheses):
  17. .TP
  18. .B update-users (u) [ACCOUNT]...
  19. Rebuild the monkeysphere-controlled authorized_keys files. For each specified
  20. account, the user ID's listed in the account's authorized_user_ids file are
  21. processed. For each user ID, gpg will be queried for keys associated with that
  22. user ID, optionally querying a keyserver. If an acceptable key is found (see
  23. KEY ACCEPTABILITY in monkeysphere(7)), the key is added to the account's
  24. monkeysphere-controlled authorized_keys file. If the RAW_AUTHORIZED_KEYS
  25. variable is set, then a separate authorized_keys file (usually
  26. ~USER/.ssh/authorized_keys) is appended to the monkeysphere-controlled
  27. authorized_keys file. If no accounts are specified, then all accounts on the
  28. system are processed. `u' may be used in place of `update-users'.
  29. \" XXX
  30. .TP
  31. .B add-id-certifier (c+) 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 (c-) 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 (c)
  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. .SH "EXPERT" SUBCOMMANDS
  57. Some commands are very unlikely to be needed by most administrators.
  58. These commands must follow the word `expert'.
  59. .TP
  60. .B diagnostics (d)
  61. Review the state of the server with respect to authentication.
  62. .TP
  63. .B gpg-cmd
  64. Execute a gpg command on the gnupg-authentication keyring as the
  65. monkeysphere user. This takes a single command (multiple gpg
  66. arguments need to be quoted). Use this command with caution, as
  67. modifying the gnupg-authentication keyring can affect ssh user
  68. authentication.
  69. .SH SETUP
  70. If the server will handle user authentication through
  71. monkeysphere-generated authorized_keys files, the server must be told
  72. which keys will act as identity certifiers. This is done with the
  73. \fBadd-id-certifier\fP command:
  74. $ monkeysphere-authentication add-id-certifier KEYID
  75. where KEYID is the key ID of the server admin, or whoever's
  76. certifications should be acceptable to the system for the purposes of
  77. authenticating remote users. You can run this command multiple times
  78. to indicate that multiple certifiers are trusted. You may also
  79. specify a filename instead of a key ID, as long as the file contains a
  80. single OpenPGP public key. Certifiers can be removed with the
  81. \fBremove-id-certifier\fP command, and listed with the
  82. \fBlist-id-certifiers\fP command.
  83. Remote users will then be granted access to a local account based on
  84. the appropriately-signed and valid keys associated with user IDs
  85. listed in that account's authorized_user_ids file. By default, the
  86. authorized_user_ids file for an account is
  87. ~/.monkeysphere/authorized_user_ids. This can be changed in the
  88. monkeysphere-authentication.conf file.
  89. The \fBupdate-users\fP command can then be used to generate
  90. authorized_keys file for local accounts based on the authorized user
  91. IDs listed in the account's authorized_user_ids file:
  92. $ monkeysphere-authentication update-users USER
  93. Not specifying USER will cause all accounts on the system to updated.
  94. sshd can then use these monkeysphere generated authorized_keys files
  95. to grant access to user accounts for remote users. You must also tell
  96. sshd to look at the monkeysphere-generated authorized_keys file for
  97. user authentication by setting the following in the sshd_config:
  98. AuthorizedKeysFile /var/lib/monkeysphere/authorized_keys/%u
  99. It is recommended to add "monkeysphere-authentication update-users" to a
  100. system crontab, so that user keys are kept up-to-date, and key
  101. revocations and expirations can be processed in a timely manner.
  102. .SH ENVIRONMENT
  103. The following environment variables will override those specified in
  104. (defaults in parentheses):
  105. .TP
  106. MONKEYSPHERE_MONKEYSPHERE_USER
  107. User to control authentication keychain (monkeysphere).
  108. .TP
  109. MONKEYSPHERE_LOG_LEVEL
  110. Set the log level (INFO). Can be SILENT, ERROR, INFO, VERBOSE, DEBUG, in
  111. increasing order of verbosity.
  112. .TP
  113. MONKEYSPHERE_KEYSERVER
  114. OpenPGP keyserver to use (subkeys.pgp.net).
  115. .TP
  116. MONKEYSPHERE_AUTHORIZED_USER_IDS
  117. Path to user authorized_user_ids file
  118. (%h/.monkeysphere/authorized_user_ids).
  119. .TP
  120. MONKEYSPHERE_RAW_AUTHORIZED_KEYS
  121. Path to user-controlled authorized_keys file. `-' means not to add
  122. user-controlled file (%h/.ssh/authorized_keys).
  123. .SH FILES
  124. .TP
  125. /etc/monkeysphere/monkeysphere-authentication.conf
  126. System monkeysphere-authentication config file.
  127. .TP
  128. /var/lib/monkeysphere/authentication/authorized_keys/USER
  129. Monkeysphere-generated user authorized_keys files.
  130. .SH AUTHOR
  131. Written by Jameson Rollins <jrollins@fifthhorseman.net>, Daniel Kahn
  132. Gillmor <dkg@fifthhorseman.net>
  133. .SH SEE ALSO
  134. .BR monkeysphere (1),
  135. .BR monkeysphere-host (8),
  136. .BR monkeysphere (7),
  137. .BR gpg (1),
  138. .BR ssh (1)