Mirror
/
acmed
mirror of https://github.com/breard-r/acmed.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
105 Commits
12 Branches
27 Tags
2.2 MiB
Tree: cd5f8d9e0d
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'cd5f8d9e0d'
${ noResults }
acmed/man/en/tacd.8

83 lines
2.6 KiB
Raw Normal View History

Add man pages Documentation is a crucial point for every project, and the most effective and traditional way to document a program is to write man page. Here, the mdoc is used because it is simple. Because the documentation is quite different from the project itself, the man pages and others helpful files are distributed under a different license. For this usage, the GNU All-Permissive License is adequate. https://www.gnu.org/prep/maintain/html_node/License-Notices-for-Other-Files.html man 7 groff_mdoc
6 years ago
​
​
​
​
​
ACMEd 0.5.0
6 years ago
Add man pages Documentation is a crucial point for every project, and the most effective and traditional way to document a program is to write man page. Here, the mdoc is used because it is simple. Because the documentation is quite different from the project itself, the man pages and others helpful files are distributed under a different license. For this usage, the GNU All-Permissive License is adequate. https://www.gnu.org/prep/maintain/html_node/License-Notices-for-Other-Files.html man 7 groff_mdoc
6 years ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Allow tacd to listen on a unix socket
6 years ago
Add man pages Documentation is a crucial point for every project, and the most effective and traditional way to document a program is to write man page. Here, the mdoc is used because it is simple. Because the documentation is quite different from the project itself, the man pages and others helpful files are distributed under a different license. For this usage, the GNU All-Permissive License is adequate. https://www.gnu.org/prep/maintain/html_node/License-Notices-for-Other-Files.html man 7 groff_mdoc
6 years ago
Allow tacd to listen on a unix socket
6 years ago
Add man pages Documentation is a crucial point for every project, and the most effective and traditional way to document a program is to write man page. Here, the mdoc is used because it is simple. Because the documentation is quite different from the project itself, the man pages and others helpful files are distributed under a different license. For this usage, the GNU All-Permissive License is adequate. https://www.gnu.org/prep/maintain/html_node/License-Notices-for-Other-Files.html man 7 groff_mdoc
6 years ago
Allow tacd to listen on a unix socket
6 years ago
Add man pages Documentation is a crucial point for every project, and the most effective and traditional way to document a program is to write man page. Here, the mdoc is used because it is simple. Because the documentation is quite different from the project itself, the man pages and others helpful files are distributed under a different license. For this usage, the GNU All-Permissive License is adequate. https://www.gnu.org/prep/maintain/html_node/License-Notices-for-Other-Files.html man 7 groff_mdoc
6 years ago
Allow tacd to listen on a unix socket
6 years ago
Add man pages Documentation is a crucial point for every project, and the most effective and traditional way to document a program is to write man page. Here, the mdoc is used because it is simple. Because the documentation is quite different from the project itself, the man pages and others helpful files are distributed under a different license. For this usage, the GNU All-Permissive License is adequate. https://www.gnu.org/prep/maintain/html_node/License-Notices-for-Other-Files.html man 7 groff_mdoc
6 years ago
Allow tacd to listen on a unix socket
6 years ago
Add man pages Documentation is a crucial point for every project, and the most effective and traditional way to document a program is to write man page. Here, the mdoc is used because it is simple. Because the documentation is quite different from the project itself, the man pages and others helpful files are distributed under a different license. For this usage, the GNU All-Permissive License is adequate. https://www.gnu.org/prep/maintain/html_node/License-Notices-for-Other-Files.html man 7 groff_mdoc
6 years ago
Allow tacd to listen on a unix socket
6 years ago
​
​
Add man pages Documentation is a crucial point for every project, and the most effective and traditional way to document a program is to write man page. Here, the mdoc is used because it is simple. Because the documentation is quite different from the project itself, the man pages and others helpful files are distributed under a different license. For this usage, the GNU All-Permissive License is adequate. https://www.gnu.org/prep/maintain/html_node/License-Notices-for-Other-Files.html man 7 groff_mdoc
6 years ago
Allow tacd to listen on a unix socket
6 years ago
Add man pages Documentation is a crucial point for every project, and the most effective and traditional way to document a program is to write man page. Here, the mdoc is used because it is simple. Because the documentation is quite different from the project itself, the man pages and others helpful files are distributed under a different license. For this usage, the GNU All-Permissive License is adequate. https://www.gnu.org/prep/maintain/html_node/License-Notices-for-Other-Files.html man 7 groff_mdoc
6 years ago
Allow tacd to listen on a unix socket
6 years ago
Add man pages Documentation is a crucial point for every project, and the most effective and traditional way to document a program is to write man page. Here, the mdoc is used because it is simple. Because the documentation is quite different from the project itself, the man pages and others helpful files are distributed under a different license. For this usage, the GNU All-Permissive License is adequate. https://www.gnu.org/prep/maintain/html_node/License-Notices-for-Other-Files.html man 7 groff_mdoc
6 years ago
​
​
Allow tacd to listen on a unix socket
6 years ago
Add man pages Documentation is a crucial point for every project, and the most effective and traditional way to document a program is to write man page. Here, the mdoc is used because it is simple. Because the documentation is quite different from the project itself, the man pages and others helpful files are distributed under a different license. For this usage, the GNU All-Permissive License is adequate. https://www.gnu.org/prep/maintain/html_node/License-Notices-for-Other-Files.html man 7 groff_mdoc
6 years ago
Allow tacd to listen on a unix socket
6 years ago
Add man pages Documentation is a crucial point for every project, and the most effective and traditional way to document a program is to write man page. Here, the mdoc is used because it is simple. Because the documentation is quite different from the project itself, the man pages and others helpful files are distributed under a different license. For this usage, the GNU All-Permissive License is adequate. https://www.gnu.org/prep/maintain/html_node/License-Notices-for-Other-Files.html man 7 groff_mdoc
6 years ago
​
​
​
​
​
​
​
​
​
​
​
  1. .\" Copyright (c) 2019 Rodolphe Bréard <rodolphe@breard.tf>
  2. .\"
  3. .\" Copying and distribution of this file, with or without modification,
  4. .\" are permitted in any medium without royalty provided the copyright
  5. .\" notice and this notice are preserved. This file is offered as-is,
  6. .\" without any warranty.
  7. .Dd May 9, 2019
  8. .Dt TACD 8
  9. .Os
  10. .Sh NAME
  11. .Nm tacd
  12. .Nd TLS-ALPN Challenge Daemon
  13. .Sh SYNOPSIS
  14. .Nm
  15. .Op Fl e|--acme-ext Ar STRING
  16. .Op Fl -acme-ext-file Ar FILE
  17. .Op Fl d|--domain Ar STRING
  18. .Op Fl -domain-file Ar STRING
  19. .Op Fl f|--foregroung
  20. .Op Fl h|--help
  21. .Op Fl l|--listen Ar host:port
  22. .Op Fl -log-stderr
  23. .Op Fl -log-syslog
  24. .Op Fl -log-level Ar LEVEL
  25. .Op Fl -pid-file Ar FILE
  26. .Op Fl V|--version
  27. .Sh DESCRIPTION
  28. .Nm
  29. is a server that will listen to incoming Transport Layer Security
  30. .Pq TLS
  31. connections and, if the
  32. .Em acme-tls/1
  33. protocol has been declared during the Application-Layer Protocol Negotiation
  34. .Pq ALPN ,
  35. present a self-signed certificate in order to attempt to solve the TLS-ALPN-01 challenge. It then drops the connection.
  36. .Pp
  37. In order to generate the self-signed certificate, it is required to specify both the
  38. .Em domain name
  39. to validate and the
  40. .Em acmeIdentifier extension .
  41. If one of those values is not specified using the available options, it is read from the standard input. When reading from the standard input, a new line character is expected at the end. In the case both values needs to be read from the standard input, the
  42. .Em domain name
  43. is read first, then the
  44. .Em acmeIdentifier extension .
  45. .Pp
  46. The options are as follows:
  47. .Bl -tag
  48. .It Fl e, -acme-ext Ar STRING
  49. The acmeIdentifier extension to set in the self-signed certificate.
  50. .It Fl -acme-ext-file Ar FILE
  51. File from which is read the acmeIdentifier extension to set in the self-signed certificate.
  52. .It Fl d, -domain Ar STRING
  53. The domain that is being validated.
  54. .It Fl -domain-file Ar STRING
  55. File from which is read the domain that is being validated.
  56. .It Fl f, -foregroung
  57. Runs in the foregroung.
  58. .It Fl h, -help
  59. Prints help information.
  60. .It Fl i, -listen Ar host:port | unix:path
  61. Specifies the host and port combination or the unix socket to listen on.
  62. .It Fl -log-stderr
  63. Prints log messages to the standard error output.
  64. .It Fl -log-syslog
  65. Sends log messages via syslog.
  66. .It Fl -log-level Ar LEVEL
  67. Specify the log level. Possible values: error, warn, info, debug and trace.
  68. .It Fl -pid-file Ar FILE
  69. Specifies the location of the PID file.
  70. .It Fl V, -version
  71. Prints version information.
  72. .Sh SEE ALSO
  73. .Xr acmed.toml 5
  74. .Sh STANDARDS
  75. .Rs
  76. .%A R. Shoemaker
  77. .%D August 2018
  78. .%R draft-ietf-acme-tls-alpn-05
  79. .%T ACME TLS ALPN Challenge Extension
  80. .Re
  81. .Sh AUTHORS
  82. .An Rodolphe Bréard
  83. .Aq rodolphe@breard.tf