Skip to content

Commit

Permalink
PFS and integrity-only ciphersuites
Browse files Browse the repository at this point in the history
Fix #43

Signed-off-by: Thomas Fossati <[email protected]>
  • Loading branch information
thomas-fossati committed Sep 3, 2024
1 parent d7e5ab7 commit 3fbeb8f
Showing 1 changed file with 9 additions and 3 deletions.
12 changes: 9 additions & 3 deletions draft-ietf-uta-tls13-iot-profile.md
Original file line number Diff line number Diff line change
Expand Up @@ -224,10 +224,16 @@ protocol. Additionally, the work on Compact TLS (cTLS) {{?I-D.ietf-tls-ctls}} ha
a step further by utilizing out-of-band knowledge between the communication parties to reduce
the amount of data to be transmitted at each individual handshake, among applying other techniques.

# Perfect Forward Secrecy
# Forward Secrecy

TLS 1.3 allows the use of PFS with all ciphersuites since the support for it is
negotiated independently.
RFC8446 has removed Static RSA and Diffie-Hellman cipher suites, therefore all public-key-based key exchange mechanisms available in TLS 1.3 provide forward secrecy.

Pre-shared keys (PSKs) can be used with (EC)DHE key exchange to provide forward secrecy or can be used alone, at the cost of losing forward secrecy for the application data.

# Authentication and Integrity-only Cipher Suites

For a few, very specific Industrial IoT use cases {{?RFC9150}} defines two cipher suites that provide data authenticity, but not data confidentiality.
Please review the security and privacy considerations about their use detailed in {{Section 9 of RFC9150}}.

# Keep-Alive

Expand Down

0 comments on commit 3fbeb8f

Please sign in to comment.