summaryrefslogtreecommitdiff
path: root/man/man8/monkeysphere-host.8
blob: 7909b62789472d4b3d0f9416527a8349844d8153 (plain)
  1. .TH MONKEYSPHERE-SERVER "8" "June 2008" "monkeysphere" "User Commands"
  2. .SH NAME
  3. monkeysphere-host \- Monkeysphere host admin tool.
  4. .SH SYNOPSIS
  5. .B monkeysphere-host \fIsubcommand\fP [\fIargs\fP]
  6. .br
  7. .B monkeysphere-host expert \fIexpert-subcommand\fP [\fIargs\fP]
  8. .SH DESCRIPTION
  9. \fBMonkeysphere\fP is a framework to leverage the OpenPGP web of trust
  10. for OpenSSH authentication. OpenPGP keys are tracked via GnuPG, and
  11. added to the authorized_keys and known_hosts files used by OpenSSH for
  12. connection authentication.
  13. \fBmonkeysphere-host\fP is a Monkeysphere server admin utility.
  14. .SH SUBCOMMANDS
  15. \fBmonkeysphere-host\fP takes various subcommands:
  16. .TP
  17. .B import-key FILE NAME[:PORT]
  18. Import a pem-encoded ssh secret host key from file FILE. If FILE
  19. is '-', then the key will be imported from stdin. NAME[:PORT] is used
  20. to specify the fully-qualified hostname (and port) used in the user ID
  21. of the new OpenPGP key. If PORT is not specified, the no port is
  22. added to the user ID, which means port 22 is assumed. `i' may be used
  23. in place of `import-key'.
  24. .TP
  25. .B show-key
  26. Output information about host's OpenPGP and SSH keys. `s' may be used
  27. in place of `show-key'.
  28. .TP
  29. .B extend-key [EXPIRE]
  30. Extend the validity of the OpenPGP key for the host until EXPIRE from
  31. the present. If EXPIRE is not specified, then the user will be
  32. prompted for the extension term. Expiration is specified as with
  33. GnuPG:
  34. .nf
  35. 0 = key does not expire
  36. <n> = key expires in n days
  37. <n>w = key expires in n weeks
  38. <n>m = key expires in n months
  39. <n>y = key expires in n years
  40. .fi
  41. `e' may be used in place of `extend-key'.
  42. .TP
  43. .B add-hostname HOSTNAME
  44. Add a hostname user ID to the server host key. `n+' may be used in
  45. place of `add-hostname'.
  46. .TP
  47. .B revoke-hostname HOSTNAME
  48. Revoke a hostname user ID from the server host key. `n-' may be used
  49. in place of `revoke-hostname'.
  50. .TP
  51. .B add-revoker KEYID|FILE
  52. Add a revoker to the host's OpenPGP key. The key ID will be loaded
  53. from the keyserver. A file may be loaded instead of pulling the key
  54. from the keyserver by specifying the path to the file as the argument,
  55. or by specifying `-` to load from stdin. `r+' may be be used in place
  56. of `add-revoker'.
  57. .TP
  58. .B revoke-key
  59. Generate (with the option to publish) a revocation certificate for the
  60. host's OpenPGP key. If such a certificate is published, your host key
  61. will be permanently revoked. This subcommand will ask you a series of
  62. questions, and then generate a key revocation certificate, sending it
  63. to stdout. If you explicitly tell it to publish the revocation
  64. certificate immediately, it will send it to the public keyservers.
  65. USE WITH CAUTION!
  66. .TP
  67. .B publish-key
  68. Publish the host's OpenPGP key to the keyserver. `p' may be used in
  69. place of `publish-key'.
  70. .TP
  71. .B help
  72. Output a brief usage summary. `h' or `?' may be used in place of
  73. `help'.
  74. .TP
  75. .B version
  76. show version number
  77. Other commands:
  78. .TP
  79. .B diagnostics
  80. Review the state of the monkeysphere server host key and report on
  81. suggested changes. Among other checks, this includes making sure
  82. there is a valid host key, that the key is published, that the sshd
  83. configuration points to the right place, etc. `d' may be used in
  84. place of `diagnostics'.
  85. .SH SETUP HOST AUTHENTICATION
  86. To enable host verification via the monkeysphere, the host's key must
  87. be published to the Web of Trust. This is not done by default. To
  88. publish the host key to the keyservers, run the following command:
  89. $ monkeysphere-host publish-key
  90. In order for users logging into the system to be able to identify the
  91. host via the monkeysphere, at least one person (e.g. a server admin)
  92. will need to sign the host's key. This is done using standard OpenPGP
  93. keysigning techniques, usually: pull the key from the keyserver,
  94. verify and sign the key, and then re-publish the signature. Once an
  95. admin's signature is published, users logging into the host can use it
  96. to validate the host's key.
  97. .SH ENVIRONMENT
  98. The following environment variables will override those specified in
  99. the config file (defaults in parentheses):
  100. .TP
  101. MONKEYSPHERE_LOG_LEVEL
  102. Set the log level (INFO). Can be SILENT, ERROR, INFO, VERBOSE, DEBUG, in
  103. increasing order of verbosity.
  104. .TP
  105. MONKEYSPHERE_KEYSERVER
  106. OpenPGP keyserver to use (pool.sks-keyservers.net).
  107. .TP
  108. MONKEYSPHERE_PROMPT
  109. If set to `false', never prompt the user for confirmation. (true)
  110. .SH FILES
  111. .TP
  112. /etc/monkeysphere/monkeysphere-host.conf
  113. System monkeysphere-host config file.
  114. .TP
  115. /var/lib/monkeysphere/host/ssh_host_rsa_key
  116. Copy of the host's private key in ssh format, suitable for use by
  117. sshd.
  118. .SH AUTHOR
  119. Written by:
  120. Jameson Rollins <jrollins@fifthhorseman.net>,
  121. Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
  122. Matthew Goins <mjgoins@openflows.com>
  123. .SH SEE ALSO
  124. .BR monkeysphere (1),
  125. .BR monkeysphere-authentication (8),
  126. .BR monkeysphere (7),
  127. .BR gpg (1),
  128. .BR ssh (1)