Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PFS and integrity-only ciphersuites #54

Merged
merged 2 commits into from
Sep 23, 2024
Merged

PFS and integrity-only ciphersuites #54

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3fbeb8f
PFS and integrity-only ciphersuites
thomas-fossati Sep 3, 2024
5c5735d
Update draft-ietf-uta-tls13-iot-profile.md
hannestschofenig Sep 23, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 9 additions & 3 deletions draft-ietf-uta-tls13-iot-profile.md
View file
Open in desktop
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.
RFC 8446 has removed Static RSA and Static 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.
Copy link
Collaborator

@hannestschofenig hannestschofenig Sep 3, 2024 •
edited by thomas-fossati
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
For a few, very specific Industrial IoT use cases {{?RFC9150}} defines two cipher suites that provide data authenticity, but not data confidentiality.
To address use cases from Industrial IoT, such as railway control and power system automation, {{?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
Loading