Windows: ssh key format

Feature Requests Royal TS (for Windows)
1

Hi everyone,
when creating ssh keys via powershell it defaults to id_ed25519.
When trying to use these ssh keys in RoyalTS it tells me “Could not handle private key file: Invalid password or bad data”

When trying to embed my ssh file it defaults to a “pri” file which seems to be created by putty. Since I do not use putty - is there a way to use the id_ed25519 file?

2

Hi,

Thanks for reporting this. To help narrow down why Royal TS cannot load the key, could you provide:

  • Your Royal TS version and whether you’re using the PuTTY-based or Rebex-based terminal.
  • The exact command you used to generate the key, with any personal information removed.
  • Whether the key is protected by a passphrase and, if so, whether you entered that passphrase in Royal TS.
  • Whether the error occurs when embedding the key, connecting using it, or both.
  • Whether the same key works with Windows’ built-in ssh command.

Also, are you selecting id_ed25519 or id_ed25519.pub? Royal TS needs the private key—the file without .pub.

The .pri filter does not necessarily identify the key’s format. Please share only the first line of the file, such as -----BEGIN OPENSSH PRIVATE KEY-----, not the private key contents or passphrase.

Regards,
Stefan

3

Hi Stefan,
RoyalTS 7.4.50820 and Rebex terminal.

The ssh keys are generated via powershell ssh-keygen.
The error comes when trying to embed or linking the key in RoyalTS.
The keys do work with native ssh-commands inside powershell.

It is microsoft implementation of the openssh-project as far as I know. I do not use encrpytion on the keyfile.

I do use the id_ed25519 (without pub).
The file looks like this:

-----BEGIN OPENSSH PRIVATE KEY-----
here comes the key
-----END OPENSSH PRIVATE KEY-----
4

Hi,

Thanks for the details. An unencrypted Ed25519 key in OpenSSH format should be supported by the Rebex terminal, so this warrants further investigation.

Could you try these checks?

  1. Run ssh -V in PowerShell and share the version output.
  2. Check whether OpenSSH can read the exact private key selected in Royal TS:
    ssh-keygen -y -f "$env:USERPROFILE\.ssh\id_ed25519" > $null
    Adjust the path if necessary. Does this complete without an error or passphrase prompt?
  3. Generate a separate test key:
    ssh-keygen -t ed25519 -f "$env:TEMP\royalts-ed25519-test"
    Leave the passphrase empty when prompted. If that filename already exists, choose another name. Then try embedding this test key in Royal TS. There’s no need to install its public key on a server for this test.

Also, does the error appear immediately when selecting or embedding the file, or only when you connect afterward? Please share the full error details, including any stack trace available in the Royal TS log, with sensitive information removed.

These checks will help distinguish a problem specific to the existing key from a reproducible key-loading issue. Please don’t share your existing private key.

Regards,
Stefan

5

@stefan_koell

I owe you a coffee – my key file is indeed encrypted. I completely forgot about it, since PowerShell stores the decryption phrase somewhere and hasn’t asked for it again in the last two years.

Sorry for the inconvenience!

6

No worried! Glad you found the issue and all is working again.

cheers,
Stefan