-
Notifications
You must be signed in to change notification settings - Fork 363
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.
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
[DTLS] Removing/Disabling renegotiation feature #604
Comments
Votes for remove. |
Votes for configure. |
Given that this is not doable in DTLS 1.3, I see no reason to keep it. |
@jimsch |
sbernard31
added a commit
that referenced
this issue
Apr 25, 2018
sbernard31
added a commit
that referenced
this issue
Apr 25, 2018
sbernard31
added a commit
that referenced
this issue
Apr 25, 2018
sbernard31
added a commit
that referenced
this issue
Apr 25, 2018
sbernard31
added a commit
that referenced
this issue
Apr 26, 2018
sbernard31
added a commit
that referenced
this issue
Apr 26, 2018
sbernard31
added a commit
that referenced
this issue
Apr 26, 2018
sbernard31
added a commit
that referenced
this issue
May 2, 2018
sbernard31
added a commit
that referenced
this issue
May 2, 2018
sbernard31
added a commit
that referenced
this issue
May 2, 2018
sbernard31
added a commit
that referenced
this issue
May 2, 2018
sbernard31
added a commit
that referenced
this issue
May 3, 2018
sbernard31
added a commit
that referenced
this issue
May 3, 2018
sbernard31
added a commit
that referenced
this issue
May 3, 2018
sbernard31
added a commit
that referenced
this issue
May 3, 2018
#618 is integrated in 2.0.x branch. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The "Transport Layer Security (TLS) / Datagram Transport Layer Security (DTLS) Profiles for the Internet of Things" (RFC 7925) advices to disable renegociation feature.
Do you agree to remove it (which will clean the code) ? or should we add a way to disable it ?
(Personnally, I'm not even sure if this feature really works, I never tested it)
The text was updated successfully, but these errors were encountered: