Crates.io | tokio-postgres-generic-rustls |
lib.rs | tokio-postgres-generic-rustls |
version | 0.1.0 |
source | src |
created_at | 2024-05-04 03:09:07.694831 |
updated_at | 2024-05-04 03:09:07.694831 |
description | rustls-backed TLS for tokio-postgres without a required crypto backend |
homepage | |
repository | https://git.asonix.dog/asonix/tokio-postgres-generic-rustls |
max_upload_size | |
id | 1229366 |
size | 40,136 |
An impelementation of TLS based on rustls for tokio-postgres
This crate allows users to select a crypto backend, or bring their own, rather than relying on
primitives provided by ring
directly. This is done through the use of x509-cert for
certificate parsing rather than X509-certificate, while also adding an abstraction for
computing digests.
By default, tokio-postgres-generic-rustls does not provide a digest implementation, but one or more are provided behind crate features.
Feature | Impelementation |
---|---|
aws-lc-rs |
AwsLcRsDigest |
ring |
RingDigest |
rustcrypto |
RustcryptoDigest |
Using this crate is fairly straightforward. First, select your digest impelementation via crate features (or provide your own), then construct rustls connector for tokio-postgres with your rustls client configuration.
The following example demonstrates providing a custom digest backend.
use tokio_postgres_generic_rustls::{DigestImplementation, DigestAlgorithm, MakeRustlsConnect};
#[derive(Clone)]
struct DemoDigest;
impl DigestImplementation for DemoDigest {
fn digest(&self, algorithm: DigestAlgorithm, bytes: &[u8]) -> Vec<u8> {
todo!("digest it")
}
}
fn main() {
let cert_store = rustls::RootCertStore::empty();
let config = rustls::ClientConfig::builder()
.with_root_certificates(cert_store)
.with_no_client_auth();
let tls = MakeRustlsConnect::new(config, DemoDigest);
let connect_future = tokio_postgres::connect("postgres://username:password@localhost:5432/db", tls);
// connect_future.await;
}
This project is licensed under either of
at your option.