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
snifd/srv.c, the listener for connections from the server processes on the end IoT devices,
relays the TLS traffic for the matched socket without any modifications, including the client TLS hello with a plaintext SNI record.
However, the server process on the end IoT device generally doesn't need a legible SNI.
Would like to explore the possibility of hiding or disguising the SNI hostname in snifd/cln.c connection
without breaking the end-to-end TLS stream.
The text was updated successfully, but these errors were encountered:
snifd/srv.c, the listener for connections from the server processes on the end IoT devices,
relays the TLS traffic for the matched socket without any modifications, including the client TLS hello with a plaintext SNI record.
However, the server process on the end IoT device generally doesn't need a legible SNI.
Would like to explore the possibility of hiding or disguising the SNI hostname in snifd/cln.c connection
without breaking the end-to-end TLS stream.
The text was updated successfully, but these errors were encountered: