#acme #rustls #tls

rustls-acme

TLS certificate management and serving using rustls

17 unstable releases (3 breaking)

new 0.4.0-beta2 Aug 6, 2022
0.3.0 Jun 17, 2022
0.3.0-beta.4 May 24, 2022
0.2.0 Oct 20, 2021
0.1.4 Mar 20, 2021

#284 in Cryptography

Download history 81/week @ 2022-04-22 134/week @ 2022-04-29 195/week @ 2022-05-06 346/week @ 2022-05-13 254/week @ 2022-05-20 210/week @ 2022-05-27 271/week @ 2022-06-03 97/week @ 2022-06-10 160/week @ 2022-06-17 107/week @ 2022-06-24 90/week @ 2022-07-01 90/week @ 2022-07-08 119/week @ 2022-07-15 140/week @ 2022-07-22 88/week @ 2022-07-29 242/week @ 2022-08-05

609 downloads per month
Used in 8 crates (3 directly)

Apache-2.0 OR MIT

63KB
1.5K SLoC

Documentation

TLS certificate management and serving using rustls

License

Licensed under either of

at your option.

Contribution

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.


lib.rs:

rustls-acme is an easy-to-use, async compatible ACME client library for rustls. The validation mechanism used is tls-alpn-01, which allows serving acme challenge responses and regular TLS traffic on the same port.

rustls-acme is designed to be runtime agnostic and as runtime independent as Rust allows at the moment. No persistent tasks are spawned under the hood and the certificate acquisition/renewal process is folded into the streams and futures being polled by the library user.

The goal is to provide a Let's Encrypt compatible TLS serving and certificate management using a simple and flexible stream based API.

To use rustls-acme add the following lines to your Cargo.toml:

[dependencies]
rustls-acme = "*"

High-level API

The high-level API consists of a single stream [Incoming] of incoming TLS connection. Polling the next future of the stream takes care of acquisition and renewal of certificates, as well as accepting TLS connections, which are handed over to the caller on success.

use futures::prelude::*;
use rustls_acme::{AcmeConfig, caches::DirCache};

#[smol_potat::main]
async fn main() {
    simple_logger::init_with_level(log::Level::Info).unwrap();

    let tcp_listener = smol::net::TcpListener::bind("[::]:443").await.unwrap();

    let mut tls_incoming = AcmeConfig::new(["example.com"])
        .contact_push("mailto:admin@example.com")
        .cache(DirCache::new("./rustls_acme_cache"))
        .incoming(tcp_listener.incoming());

    while let Some(tls) = tls_incoming.next().await {
        let mut tls = tls.unwrap();
        smol::spawn(async move {
            tls.write_all(HELLO).await.unwrap();
            tls.close().await.unwrap();
        }).detach();
    }
}

const HELLO: &'static [u8] = br#"HTTP/1.1 200 OK
Content-Length: 11
Content-Type: text/plain; charset=utf-8

Hello Tls!"#;

examples/high_level.rs implements a "Hello Tls!" server similar to the one above, which accepts domain, port and cache directory parameters.

Note that all examples use the let's encrypt staging directory by default. The production directory imposes strict rate limits, which are easily exhausted accidentally during testing and development. For testing with the staging directory you may open https://<your domain>:<port> in a browser that allows TLS connections to servers signed by an untrusted CA (in Firefox click "Advanced..." -> "Accept the Risk and Continue").

Low-level Rustls API

For users who may want to interact with [rustls] or [futures_rustls] directly, the library exposes the underlying certificate management [AcmeState] as well as a matching resolver [ResolvesServerCertAcme] which implements the [rustls::ResolvesServerCert] trait. See the server_low_level example on how to use the low-level API directly with [futures_rustls].

Account and certificate caching

A production server using the let's encrypt production directory must implement both account and certificate caching to avoid exhausting the let's encrypt API rate limits. A file based cache using a cache directory is provided by [caches::DirCache]. Caches backed by other persistence layers may be implemented using the [Cache] trait, or the underlying [CertCache], [AccountCache] traits (contributions welcome). [caches::CompositeCache] provides a wrapper to combine two implementors of [CertCache] and [AccountCache] into a single [Cache].

Note, that the error type parameters of the cache carries over to some other types in this crate via the [AcmeConfig] they are added to. If you want to avoid different specializations based on cache type use the [AcmeConfig::cache_with_boxed_err] method to construct the an [AcmeConfig] object.

The acme module

The underlying implementation of an async acme client may be useful to others and is exposed as a module. It is incomplete (contributions welcome) and not covered by any stability promises.

Special thanks

This crate was inspired by the autocert package for Go.

This crate builds on the excellent work of the authors of rustls, futures-rustls, and many others.

Thanks to Josh Triplett for contributions and feedback.

Dependencies

~20MB
~446K SLoC