Commit graph

8 commits

Author SHA1 Message Date
Jan Rüth
271acbb315 Bump boring to v5, align FIPS to SP 800-52r2, clean up features
- Bump boring/boring-sys from v4 to v5 (zero API breaks)
- Merge fips/fips-only into a single fips feature that both enables
  FIPS-validated BoringSSL and restricts algorithms to SP 800-52r2
- Tighten FIPS KX groups to P-256 and P-384 only (aligned with
  boring's fips202205 compliance policy)
- Remove ECDSA_P521_SHA512 from FIPS signature verification set
- Simplify fips feature to forward boring/fips only (drop redundant
  boring-sys/fips)
- Add fips-precompiled as deprecated alias matching boring's naming
- Change default features to empty (TLS 1.2 now requires explicit
  tls12 feature opt-in)
- Gate TLS 1.2 code paths properly so the crate compiles and passes
  tests with default (TLS 1.3 only) features
- Update README to reflect current state: boring v5, feature docs,
  FIPS mode documentation, workspace structure
2026-04-10 12:38:26 +02:00
Jan Rüth
b24ac52817 Implement QUIC traits (untested) 2023-11-30 00:29:31 +01:00
Jan Rüth
5ead01a5c7 Update to rustls = 0.22.0-alpha.5 2023-11-26 22:19:48 +01:00
Jan Rüth
7d7b1b3f99 RSA tests and fix chacha20 in tls 1.2 2023-11-26 22:19:48 +01:00
Jan Rüth
624eda8168 Fix TLS 1.2 crypto and add end-to-end tests 2023-11-26 19:49:01 +01:00
Jan Rüth
d38412a3bd Use boringssl prf for tls1.2 2023-11-25 15:26:58 +01:00
Jan Rüth
319029f2d4 Fix AES256 using wrong hash
Add TLS 1.2
Move aead crypter to boring-additions crate
2023-11-20 20:36:55 +01:00
Jan Rüth
5c45b9426b Initial dump for a boring-rustls-provider
This is just a dump of me figuring out how to interface with boring and rustls.
It works to establish a connection and exchange data but I haven't written real tests yet, nor did I cleanup the code or made the effort to make it look nice.
There is probably some code in here that should rather live in the `boring` crate.
2023-11-19 17:49:03 +01:00