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