arduino/esp8266
1
0
Fork 0
mirror of https://github.com/esp8266/Arduino.git synced 2025-06-04 18:03:20 +03:00
Code

Update RFC 5246 URL (#8564)

Browse Source 
The old link to RFC 5246 has been moved to https://tools.ietf.org/search/rfc5246
This commit is contained in:
Chris Kitras 2022-05-12 15:03:32 -06:00 committed by GitHub
parent d1d4212e8b
commit 2de142b8db
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/esp8266wifi/bearssl-client-secure-class.rst
View File

@ -48,7 +48,7 @@ As a rule, either keep your objects global, use `new` to create them, or ensure
TLS and HTTPS Basics
~~~~~~~~~~~~~~~~~~~~
The following discussion is only intended to give a rough idea of TLS/HTTPS(which is just HTTP over a TLS connection) and the components an application needs to manage to make a TLS connection. For more detailed information, please check the relevant `RFC 5246 <https://www.ietf.org/rfc/rfc5246>`__ and others.
The following discussion is only intended to give a rough idea of TLS/HTTPS(which is just HTTP over a TLS connection) and the components an application needs to manage to make a TLS connection. For more detailed information, please check the relevant `RFC 5246 <https://tools.ietf.org/search/rfc5246>`__ and others.
TLS can be broken into two stages: verifying the identities of server (and potentially client), and then encrypting blocks of data bidirectionally. Verifying the identity of the other partner is handled via keys encoded in X509 certificates, optionally signed by a series of other entities.