AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
![]() ![]() Use regedit to add a new Binary Value called SSLCertificateSHA1Hash at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp. Add user ‘NETWORK SERVICE’ with Read permission only (not Full Control), then Apply.Right-click on this site certificate and right-click, choose All Tasks / Manage Private Keys… Expanding your Personal/Certificates you should now see 3 certificates, one of which is your site certificate (e.g.Locate the pfx file and import it, I suggest that for security reasons you don’t make it exportable.In the left-hand window right-click on Certificates (Local Computer)Personal, choose All Tasks/Import….File > Add Remove Snap-in > Certficates > Add > Computer Account > Local Computer > OK. ![]() pfx) file into Windows host machine’s personal certificates store: Openssl x509 -in /etc/ssl/certs/mysite.crt -noout -fingerprint View SHA1 fingerprint of the key (you will need this below): Move or copy this pfx file as required so that it is accessible by your Windows host machine. pfx extension) you can view SHA1 fingerprint using Linux or Cygwin thus (you will need it below): openssl pkcs12 -in mysite.pfx -nodes|openssl x509 -noout -fingerprintĪlternatively if you have the individual certificate files in your Linux server at /etc/ssl (/etc/ssl/certs/mysite.crt, /etc/ssl/mysite.ca-bundle and /etc/ssl/private/mysite.key) you can create pfx file and obtain SHA1 fingerprint thus:Ĭreate pfx file for your certificate, if you don’t already have one (here: mysite.pfx) – set a good password when requested: sudo openssl pkcs12 -export -out mysite.pfx -inkey /etc/ssl/private/mysite.pem -in /etc/ssl/certs/mysite.crt -certfile /etc/ssl/mysite.ca-bundle If you have this certificate in pkcs12 format file (e.g. ![]() You can set this host machine to use and present your (existing) externally-verified SSL certificate thus (instructions probably also work for Windows 8 & 8.1, may or may not work for Windows 7) (parts of this based on a Microsoft KB 2001849):įirst, you need to have a genuine verified ssl certificate, whether one you purchased or a free one from e.g. How do I get a Windows 10 Pro (or Windows 7 / 8 / 8.1 Pro) machine acting as server/host to present a proper SSL certificate for Remote Desktop verification? The check reports fatal errors on this internet-facing remote desktop port: 'SSL Self-Signed Certificate' and 'SSL Certificate with Wrong Hostname'. Our site fails PCI-DSS 3.1 compliance check (required because we use there a point-of-sale debit/credit card machine that connects via internet).We cannot be fully confident when connecting remotely we really are connecting to this machine and not some hijacked connection. ![]() It is well protected by complex password and limited number of permitted attempts and only TLS 1.1 or higher, but it doesn't present an externally-verified SSL certificate, only the self-generated self-signed one that Remote Desktop Services provides, and this gives us two problems: We have a Windows 10 Pro machine at our office which has an open port to the internet for incoming remote desktop connections (a ‘host’). ![]()
0 Comments
Read More
Leave a Reply. |