Windows 10: RDP Self Signed Certificate 3389 Remote Desktop Protocol

Tenable Nessus Scans showing self signed cert used for RDP on port 3389.Done my due diligence - 1. Cert is located in certlm.msc > Remote Desktop2. You can create a custom template and generate a cert to be used for RDP and put in that folder3. Deleting the self signed - it just regenerates it when you reboot4. Found some reg hacks to tell windows to use the generated cert5. found some other permission hacks to stop self signed from being regeneratedthrough all that - some how RDP broke and I had to revert everything.In short - this is classified as a medium vulnerability and it would be ni

:)

 

Port forwarding Remote Desktop (RDP) and installing SSL Certificate?

So, I'm not using Remote Desktop Gateway. Just RDP on a standard Windows 11 system. And that certificate error always pops up warning me that the certificate is not trusted. It's just the default that the computer creates. I am wondering if its possible to use a certificate just for one computer using RDP

 

Using Remote Desktop Services with a self-signed SHA256 (SHA-2) certificate - help!

Hello,

I've searched the internet high and low to find the answer to this problem and have not come up with much.

I run a remote desktop protocol in order to access my PC remotely. The self-signed certificated which is auto-generated by Windows (in order to support the TLS encryption) is SHA1. I work in the security industry and I understand that SHA1 is phasing out.

What is the process to upgrade this auto-generated certificate so that it can use SHA256? The closest article I've been able to find is here,
but it discusses replacing the RDP certificate with a custom SHA1 cert: it says nothing about SHA2.

Does anybody know how to accomplish this?

Thanks

Bob

 

RDP port 3389 stopped listening.


RDP port 3389 just stopped listening after some of the updates, netstat -an command doesn't list it.
Remote Desktop Service is displayed as Running, but Event Viewer has following error:

Remote Desktop Service start failed. The relevant status code was 0x80070721.