I need to distribute signed RDP connection files to a mix of domain users and people outside our organization. I'm looking for a code-signing certificate that can sign .RDP files and support trusted timestamping, so the signature remains valid after the certificate expires. Several certificate providers haven't been clear about whether their certificates work with RDP files or which timestamping services they support. What certificate and signing process would you recommend?
1 Answer
It may also be worth considering whether the RDP file needs to be signed at all. In many environments, the stronger approach is to configure and trust the certificate on the RDP server. However, signing the distributed shortcut can still make sense when external users aren’t members of the domain and need a way to verify the connection settings or publisher.
That’s the main reason I’m looking at signing the files: some of the people connecting to our servers are outside the domain, so they won’t automatically receive the organization’s trust settings.