Simple ACME client
Go to file
dependabot[bot] e6b2ff7fec Update thiserror requirement from 1.0.30 to 2.0.3
Updates the requirements on [thiserror](https://github.com/dtolnay/thiserror) to permit the latest version.
- [Release notes](https://github.com/dtolnay/thiserror/releases)
- [Commits](https://github.com/dtolnay/thiserror/compare/1.0.30...2.0.3)

---
updated-dependencies:
- dependency-name: thiserror
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
2024-11-11 14:36:55 +01:00
.github Add FUNDING metadata 2024-10-10 07:30:01 +00:00
examples Upgrade example to rcgen 0.13 2024-07-26 12:17:31 +02:00
src Add public `fn Account::id` 2024-10-23 15:33:32 +00:00
.gitignore Add .gitignore 2022-05-12 21:47:01 +02:00
Cargo.toml Update thiserror requirement from 1.0.30 to 2.0.3 2024-11-11 14:36:55 +01:00
LICENSE Add Apache 2.0 license file 2022-05-12 21:47:01 +02:00
README.md Update links to repository after move 2024-08-20 18:17:00 +02:00
deny.toml Update to hyper dependency to version 1 (#50) 2024-06-27 13:04:02 +02:00

README.md

instant-acme: async, pure-Rust ACME client

Documentation Crates.io Build status License: Apache 2.0

instant-acme is an async, pure-Rust ACME (RFC 8555) client.

instant-acme is used in production at Instant Domain Search to help us provision TLS certificates within seconds for our customers. instant-acme relies on Tokio and rustls to implement the RFC 8555 specification.

Features

  • Store/recover your account credentials by serializing/deserializing
  • Fully async implementation with tracing support
  • Support for processing multiple orders concurrently
  • Support for external account binding
  • Support for certificate revocation
  • Uses hyper with rustls and Tokio for HTTP requests
  • Uses ring or aws-lc-rs for ECDSA signing
  • Minimum supported Rust version: 1.63

Cargo features

  • hyper-rustls (default): use a hyper client with rustls
  • ring (default): use the ring crate as the crypto backend
  • aws-lc-rs: use the aws-lc-rs crate as the crypto backend
  • fips: enable the aws-lc-rs crate's FIPS-compliant mode

If both ring and aws-lc-rs are enabled, which backend is used depends on the fips feature. If fips is enabled, aws-lc-rs is used; otherwise, ring is used.

Limitations

  • Only tested with DNS challenges against Let's Encrypt (staging and production) and ZeroSSL (production) so far
  • Only supports ECDSA keys for now

Getting started

See the examples directory for an example of how to use instant-acme.