.. _compat: Compatibility ============= The following table lists the compatibility between `Responder `_ and `Dementor `_, which protocols are available and which are currently in development. The legend for each symbol is as follows: .. raw:: html .. raw:: html
Supported Protocols Responder (3.2.2.0) Dementor (1.0.0.dev19)
DHCP (use bettercap)
DNS (use bettercap)
NBTNS
NBTDS
LLMNR
MDNS
SSDP
SSRP
QUIC
SMB
SMB 1.0 SSP
SMB 1.0 Raw
SMB 2.002
SMB 2.1
SMB 2.???
SMB 3.0
SMB 3.0.2
SMB 3.1.1
NTLM
NetNTLMv1
NetNTLMv1-ESS
NetLMv2
NetNTLMv2
[1]
Kerberos KDC
rc4_hmac
aes256_cts_hmac_sha1_96
aes128_cts_hmac_sha1_96
FTP
SMTP
PLAIN
LOGIN
NTLM
SNMP
RDP (use pyrdp-mitm)
HTTP_PROXY (use mitmproxy)
HTTP
Basic
NTLM
Bearer
[1]
IMAP
PLAIN
LOGIN
NTLM
POP3
USER/PASS
PLAIN
LOGIN
NTLM
LDAP
MQTT
MSSQL
Cleartext
NTLM
[1]
MySQL
mysql_clear_password
NTLM
SPNEGO
WinRM
DCE/RPC
NTLM
DCOM (interface)
EPMv4 (interface)
X11
IPP
UPnP

SMB Features

Feature Responder (3.2.2.0) Dementor (1.0.0.dev19)
Tree Connect
Logoff
NT4 clear-text capture
Multi-credential loop
Configurable ErrorCode
Configurable ServerOS

[1]: Responder combines NetNTLMv1 and NetNTLMv1-ESS under a single "NTLMv1-SSP" label. This is not incorrect — hashcat -m 5500 handles both — but Dementor distinguishes them for more granular reporting. Applies to all NTLM-capable protocols (SMB, HTTP, MSSQL, LDAP, DCE/RPC).

NTLM Spcifics

Feature Responder (3.2.2.0) Dementor (1.0.0.dev19)
Dummy LM filtering
LM dedup filtering
Anonymous detection
Flag mirroring
NetNTLMv2 threshold (≥ 48 B)
AV_PAIRS correctness
Hash label accuracy
Configurable challenge
SPNEGO unwrapping
Non-NTLM mech redirect
ESS configurable
NetNTLMv2 configurable