Add risk flag about suspicious ESNI usage
In a Client Hello, the presence of both SNI and ESNI may obfuscate the real domain of an HTTPS connection, fooling DPI engines and firewalls, similarly to Domain Fronting. Such technique is reported in a presentation at DEF CON 28: "Domain Fronting is Dead, Long Live Domain Fronting: Using TLS 1.3 to evade censors, bypass network defenses, and blend in with the noise" Full credit for the idea must go the original author At the moment, the only way to get the pdf presention and related video is via https://forum.defcon.org/node/234492 Hopefully a direct link (and an example pcap) will be available soon
This commit is contained in:
+2
-1
@@ -312,6 +312,7 @@ typedef enum {
|
||||
NDPI_SSH_OBSOLETE_CLIENT_VERSION_OR_CIPHER,
|
||||
NDPI_SSH_OBSOLETE_SERVER_VERSION_OR_CIPHER,
|
||||
NDPI_SMB_INSECURE_VERSION,
|
||||
NDPI_TLS_SUSPICIOUS_ESNI_USAGE,
|
||||
/* Leave this as last member */
|
||||
NDPI_MAX_RISK
|
||||
} ndpi_risk_enum;
|
||||
@@ -1446,4 +1447,4 @@ class NDPI():
|
||||
def ndpi_exit_detection_module(self):
|
||||
""" Exit function for nDPI module """
|
||||
self._ndpi.ndpi_exit_detection_module(self._mod)
|
||||
self._ffi.dlclose(self._ndpi)
|
||||
self._ffi.dlclose(self._ndpi)
|
||||
|
||||
Reference in New Issue
Block a user