acmed

Commit Graph

Author	SHA1	Message	Date
Rodolphe Breard	ed9bd8aaf2	Fix a typo	5 years ago
Rodolphe Breard	f2e048c15c	Add a Makefile	5 years ago
Rodolphe Breard	e0d260ca8c	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	5 years ago
Rodolphe Breard	1c65795e2b	Add build instruction for Debian-based systems	5 years ago
Rodolphe Breard	ed547f6a46	Update the README	5 years ago
Rodolphe Breard	644484cb31	Change the hook and domains definitions The previous system was too limited when it comes to flexibility using hooks. This limitation came from the false idea that, for a given certificate, all challenges must be validated with the same method. In order to prove that false, domains in a certificate can now make use of any challenge type available. In order to be more flexible, hooks are now given a type and are defined in the same registry (instead of 6). Each one will be called when considered relevant based on its type.	5 years ago
Rodolphe Breard	2fc4eef60c	Add tacd, a daemon for the tls-alpn-01 challenge ACMEd should and will remain as simple as possible and let the user alone take care of the challenge validation. However, this philosophy does not forbid the project itself to distribute additional tools that are designed to improve the user experience. Because the TLS-ALPN ecosystem is currently very slim, adding tacd is really benefic to ACMEd.	5 years ago
Rodolphe Breard	79dd765c93	Update the README	5 years ago
Rodolphe Breard	0a7deb4cdc	Add tls-alpn-01 challenge support Although the standardization is still a draft, this challenge is already supported by Let's Encrypt. https://datatracker.ietf.org/doc/draft-ietf-acme-tls-alpn/	5 years ago
Rodolphe Breard	c5c9d17885	Update the README	5 years ago
Rodolphe Breard	2c7b716584	Retry request rejected with a recoverable error Some errors, like the badNonce one, are recoverable. Hence, the client is expected to retry. ACMEd will now re-send the associated request until it succeed or the max retries number is reached. Each retry is preceded by a small waiting time in order to let the server recover in case it was faulty.	5 years ago
Rodolphe Breard	9576a0b755	Update the rustc badge	5 years ago
Rodolphe Breard	11255d4275	Update the minimal rustc version	5 years ago
Rodolphe Breard	6258175c5e	Reduce the executable size In release mode, the executable size should be kept to the bare minimum in order to be used in environments with low storage and reduce the data consumption when pre-built packages are downloaded. Because performance is absolutely not needed, it allows to a quite aggressive compiling strategy (opt-level = 'z'). https://doc.rust-lang.org/cargo/reference/manifest.html#the-profile-sections Fixes #1	5 years ago
Rodolphe Breard	f4f339b8c2	Add hooks before and after a file is created or edited It is considered a good practice to archive old certificates and private keys instead of simply dropping them away. Because ACMEd should not impose a way of doing things to system administrators, hooks are the way to go.	6 years ago
Rodolphe Breard	3a9cbdd926	Fix some stuff in the readme	6 years ago
Rodolphe Breard	27aecdc2a4	Replace the space by %20	6 years ago
Rodolphe Breard	ece0f8dc42	Fix the readme	6 years ago
Rodolphe Breard	fd50694318	Add badges to the readme	6 years ago
Rodolphe Breard	ad5f418f85	Add question about the FOSS	6 years ago
Rodolphe Breard	6c48ef901e	Specify the OpenSSL dependency in the readme	6 years ago
Rodolphe Breard	39d73f1b10	Acknowledge the minimal required Rust version	6 years ago
Rodolphe Breard	a6c9a8bf9b	Switch from heading underline to ATX headings Both markdown and CommonMark support only 2 level of heading underline. A third level using the `~` character is only supported as an extension in some implementations. While GitHub and most software do not support it, it is a better choice to switch to ATX headings. https://daringfireball.net/projects/markdown/syntax https://spec.commonmark.org/	6 years ago
Rodolphe Breard	8d49775e56	Expand the readme	6 years ago
Rodolphe Breard	5753d768f7	Add a README.md file	6 years ago

25 Commits (a0e3c80e51804b8c4e190dc8481f98781e8f43f5)