If your Windows client does not have group policy editor or above “Oracle Remediation” option (like Windows Home Edition), then you can temporarily uninstall the security update patch in May 2018, KB41037XX: Windows Home Edition client (without above option) Remember to revert the setting after you are done. Now your remote desktop should be able to connect. Just change it to “Enabled”, and set “Protection Level” as “Vulnerable”. Under Computer Configuration -> Administrative Templates -> System -> Credentials Delegation, there is a setting “Encryption Oracle Remediation”.
The workable solution I found is to edit client Windows’ local group policy (gpedit.msc): Windows Pro Edition (with group policy editor) However, if you do not have the permission to patch the remote Windows (In this case, I am connecting to a build VM provided by AppVeyor), then you have to compromise the client.
The solution is certainly patching the remote Windows. This could be due to CredSSP encryption oracle remediation.įor more information, see https:/go./fwlink/?linkid=866660 Windows clientįollowing the above link, and searching around, this seems caused by the client Windows is patched with a CredSSP (Credential Security Support Provider protocol) update for CVE-2018-0886, while the remote Windows is not. Recently, when connecting to another Windows machine with RD, I got the following RDP authentication error due to CredSSP encryption oracle remediation:
0 kommentar(er)
