Issues
- 1
X25519 might not be FIPS compliant for use in key exchange
#1992 opened by RobMor - 0
Dependency Dashboard
#1990 opened by forking-renovate - 7
Poll-based encrypt/decrypt/sign API support in asynchronous and synchronous call
#1976 opened by taikulawo - 9
Suggest registering for OpenSSF Best Practices badge
#1901 opened by mspi21 - 0
Server-side Encrypted Client Hello (ECH) support
#1980 opened by cpu - 33
Rustls w/ aws-lc-rs on Windows requires NASM
#1913 opened by Diggsey - 6
Compile error when target is watchos
#1926 opened by sax - 2
`UnknownIssuer` with self-signed certificate
#1969 opened by dvorakchen - 8
- 1
build failure due to aws-lc-sys v0.16.0
#1967 opened by so-schen - 2
- 0
Clean up crate feature naming
#1961 opened by ctz - 2
UnbufferedConnectionState
#1957 opened by pascaldekloe - 3
How I use CryptoProvider::install_default() ?
#1938 opened by incker - 2
Build rustls v0.23.5 with musl
#1947 opened by incker - 21
Making impl ClientHelloPayload public ?
#1915 opened by dawid-nowak - 4
Expose ability to customize ClientHello message
#1932 opened by hellais - 19
- 5
Add RustCrypto cryptographic backend
#1945 opened by wiktor-k - 4
Error: badRecordMac
#1836 opened by peyman1992 - 6
Verify that SigningKey matches public key within certificate
#1918 opened by lvkv - 3
Illegal instruction on arm-a72
#1939 opened by Arne91 - 6
- 2
GHSA-6g7w-8wpp-frhj and CVE-2024-32650 don't make it clear that async rustls servers aren't susceptible
#1909 opened by sunshowers - 3
Question. Does rustls have something to hide cert (as it is sensitive data ) in binary and memory
#1917 opened by incker - 2
Pass ClientHello by reference to ResolvesServerCert
#1908 opened by blind-oracle - 2
Side-Channel Attack Mitigations in Rustls
#1898 opened by pavanmikkilineni - 4
unbuffered: After `Closed` no `WriteTraffic` state arrives
#1895 opened by uazu - 3
- 1
Incompatible License
#1893 opened by jjnicola - 7
- 6
Io(Custom { kind: InvalidData, error: AlertReceived(HandshakeFailure) })
#1887 opened by gcp-development - 9
- 2
- 6
- 4
US Export control information
#1864 opened by zaddok - 2
- 7
- 4
No common ciphersuit when FFDHE and ECDHE ciphersuites are available on server and client using TLS 1.2
#1860 opened by Taowyoo - 4
expose more information in ClientHello
#1857 opened by GlenDC - 7
- 1
optimize receiving data with TLS 1.2 and aes-128-gcm
#1828 opened by bdaehlie - 6
Cipher suites configured through WebPkiServerVerifier::builder_with_provider is not working. Client hello contains more cipher suites then it configured.
#1851 opened by pranaw215 - 1
Consider a process default server certificate verifier
#1821 opened by djc - 0
Connection::dangerous_extract_secrets returns ConnectionTrafficSecrets::Aes128Gcm even when AES-256-GCM is negotiated
#1833 opened by Arnavion - 2
0.23 docs build is broken
#1826 opened by howardjohn - 1
optimize server-side full handshakes for TLS 1.2 and 1.3
#1830 opened by bdaehlie - 0
optimize receiving data with TLS 1.3 and aes-256-gcm
#1829 opened by bdaehlie - 5
ClientConnection.peer_certificates() to return Some() regardless of CertificateError::UnknownIssuer
#1819 opened by nworbnhoj - 0
Profile-Guided Optimization (PGO) benchmark results
#1823 opened by zamazan4ik