As yet, it has not proved possible to recover the NTLM keys in order to decrypt the CredSSP encrypted PDUs.

The FreeRDP project provides a number of capture files, associated private keys and a detailed analysis of the protocol exchanges on their wiki. The CredSSP documentation states that SPNEGO is used to select between NTLM and Kerberos - but the RDP captures seen to date carry NTLM without any SPNEGO. This is always run under a SSL encrypted session. RDP can also use the Credential Security Support Provider ( CredSSP) protocol to provide authentication information. In order to dissect Enhanced RDP Security SSL, you should configure the SSL dissector with the following: ,3389,tpkt, There is no handling of virtual channel PDUs (beyond the security header) at the moment. If Standard RDP Security is being negotiated, all the PDUs after the SecurityExchangePDU will be encrypted. WiresharkĪ basic RDP dissector exists that can decode most of the PDUs that are exchanged during the connection sequence. The encapsulated RDP will never negotiate any Standard RDP Security, so all of these SSL protected PDUS should be able to be dissected (subject to be able to do applicable decompression).Įxample capture files are detailed below. The SSL dissector may be used to handle the SSL and then hand off the encapsulated data to the RDP dissector. SSL: SSL may be used with Enhanced RDP security, and is used on the same port as standard RDP. TPKT runs atop TCP when used to transport RDP, the well known TCP port is 3389, rather than the normal TPKT port 102. TPKT: Typically, RDP uses TPKT as its transport protocol. See Wikipedia entry Protocol dependencies RDP is a proprietary protocol developed by Microsoft for their Terminal Server services.

Wireshark tls decrypt protocol