CLOVRDP / BLOG

Use SSH Keys from a Windows RDP Without Exposing Your Private Key

By Jack S4 min read
Cybersecurity-themed photograph illustrating protected remote access

A Windows RDP can act as an SSH client for servers you are authorized to administer. The key security decisions are where the private key is stored, which server account receives the public key, and how you verify the server before connecting. A working login is not enough if the key has been copied into an unsafe location.

This guide concerns outbound SSH from the Windows desktop to an approved server. It does not require enabling an SSH server on the RDP machine or opening another inbound port. Keep that distinction clear when reading installation instructions that cover both client and server roles.

Know which key answers which question

ItemPurposeHandling rule
Your private keyUsed by your SSH client to authenticateKeep it private, access-controlled, and protected by an appropriate passphrase
Your public keyInstalled for the approved account on the destinationShare through the server owner’s authorized process
The server’s host-key fingerprintHelps you verify which server you reachedCompare it with a trusted independent reference

Microsoft’s OpenSSH key-management guide explains the public/private pair, supported key-generation tools, and the importance of protecting the private key. A filename ending in .pub normally identifies the public half generated by OpenSSH. Verify the filename before copying anything into a support ticket or server-management panel.

Prepare a dedicated key for the approved purpose

Confirm that the approved OpenSSH client is installed by checking ssh -V in PowerShell. If it is unavailable, use your organization’s supported installation process. Do not download an executable from an unfamiliar mirror or install the server component merely to obtain a client.

Use a clearly named key for the project or administrative role rather than sharing one unrestricted key across unrelated customers. Ensure your own .ssh directory exists and inspect it for existing files. For a server that supports Ed25519, an example is ssh-keygen -t ed25519 -f "$env:USERPROFILE\.ssh\project-admin". Choose a unique filename and stop rather than overwriting an existing key. Use a strong passphrase at the prompt.

The example is a starting point, not an instruction to replace a key type required by an organization’s policy. Keep the private file out of ordinary synchronized folders, shared desktops, email attachments, and project repositories. Restrict local access and remember that a remote desktop with other authorized administrators is not a private hardware security device.

Install only the public key for the intended server account

Send the public key to the server owner through the approved channel, identifying the account and purpose. Ask for the minimum access required for the work. A public key installed for one account does not automatically authorize access to every server or justify an unrestricted administrator login.

Keep a record of the key’s owner, public fingerprint, approved servers, creation date, and review or retirement date. Do not record the private key or passphrase in that inventory. The server administrator should apply the destination operating system’s supported permissions and key-installation procedure; Windows and Linux server arrangements need not be identical.

Verify server identity before the first connection

Obtain the expected host-key fingerprint from an independent trusted source, such as the provider’s authenticated console or the server administrator. Compare the complete fingerprint presented by the SSH client. A familiar hostname is not a substitute for checking an unexpected host key.

The WinSCP host-key verification guide explains why this check matters and how to obtain a trusted reference. Although the interface differs between WinSCP and the OpenSSH command line, the identity question is the same. Do not disable host-key checking or automatically accept a changed key to make a warning disappear.

Test access without making production changes

Connect with the approved account, destination, and key file. In PowerShell, a template is ssh -i "$env:USERPROFILE\.ssh\project-admin" approved-user@approved-host. Replace both placeholders with the authorized values and use the assigned port when it differs from the default. Enter the passphrase only at the trusted client’s prompt.

Confirm the server identity and account with a harmless inspection, then exit. Do not use a configuration change as the first connectivity test. If authentication fails, give the administrator the public-key fingerprint, account, time, and redacted error. Never send the private file as evidence.

Plan revocation before the desktop changes hands

Document how the server owner will remove the public key when the project ends, the user leaves, or the RDP is replaced. Removing a private file from one desktop does not revoke copies that may exist elsewhere. Have the destination owner remove obsolete authorization and verify that the retired key no longer works through an approved test.

Use the recovery-planning guide to decide how approved credentials are recovered without dumping secrets into a general archive. For ClovRDP client-side access issues, contact support with redacted diagnostics. The destination server owner remains the authority for granting and revoking SSH access.

Featured photograph: FlyD on Unsplash. Technical references reviewed on 17 October 2026.

A little more information

Visit Contact