You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The ability to have a TLS secured TCP connection (by self signed or even letsencrypt certificate, certificate source is currently irrelevant).
An extension to the protocol with its own extension ID that replies with a port number that accepts the TLS encrypted connection in the same way that the DHT port extension works.
This would allow the use of standard TLS encryption for the entire connection once established, and would initially encrypt the entire connection beyond the initial "no, go here instead".
The text was updated successfully, but these errors were encountered:
I would like to propose a BEP that introduces:
This would allow the use of standard TLS encryption for the entire connection once established, and would initially encrypt the entire connection beyond the initial "no, go here instead".
The text was updated successfully, but these errors were encountered: