tokio-postgres-rustls

What's Changed

• fix: correctly parse x509 certificates for channel binding by @conradludgate in #32
• chore: remove unsafe code by @conradludgate in #33
• fix: defer TLS hostname validation by @jbg in #39
• fix: avoid Ed25519 channel binding digest by @jbg in #40
• Bump Rust edition to 2024 by @jbg in #41
• feat: add rustls feature selection by @jbg in #42
• test: add postgres rustls integration suite by @jbg in #43
• chore: bump version to 0.14.0 by @jbg in #44

New Contributors

• @conradludgate made their first contribution in #32

Full Changelog: v0.13.0...v0.14.0

• Minimize API
• Add documentation
• Eliminate allocations
• Migrate from x509-certificate to x509-cert to avoid policy problems with x509-certificate's MPL license in some organizations

Thanks to @aumetra for the above improvements!

• Update rustls to 0.23 (thanks @aumetra!)

• Update x509-certificate to 0.23 to avoid pulling in multiple versions of ring. Thanks @serprex

• Fixed the SCRAM channel binding check to use the correct digest based on the server certificate (thanks @JamesGuthrie)
• Updated rustls to 0.22 (thanks @ol-teuto)
• Updated ring to 0.17 (thanks @fnichol)

• Updated rustls to 0.20 (thanks @UjOwtuc!)

Deferred failure in make_tls_connect (e.g. due to an invalid/missing hostname) until establishing the TLS connection is actually attempted. This is consistent with the behaviour of other tokio-postgres TLS integrations, and allows using SslMode::Disable to e.g. connect to a UNIX socket whilst still having tokio-postgres-rustls as the chosen TLS library for tokio-postgres.

• Updated to tokio 0.3, rustls 0.19, tokio-postgres 0.6, tokio-rustls 0.21.