Last Modified: Nov 22, 2021
See more info
Known Affected Versions:
13.1.0, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 13.1.1, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 13.1.3, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 13.1.4, 188.8.131.52, 14.0.0, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 14.0.1, 188.8.131.52
Opened: Mar 07, 2017
Microsoft Remote Desktop (MS RDP) may not work through native Application Tunnels on MacOS and Linux if there are no credentials specified prior to establishing the connection.
MS RDP connection through Application Tunnels doesn't work.
* Native applications tunnels are configured to use for MS RDP tunneling (MacOS and Linux). * Certificate of MS RDP backend is not always trusted by the keychain. * There are no credentials specified before establishing connection in remote desktop entry.
Use one of the following workarounds: A. Specify credentials in the remote desktop entry. B. Mark the certificate of the remote backend as "always trust". C. Create a /etc/hosts entry alias for the required backend to point to localhost. Use this alias to access the remote backend to SSL layer accessible do not complain about certificate