You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expected behavior
It should connect to the server.
Client (please complete the following information):
OS: macOS sonoma 14.4.1 (23E224)
Client: Citadel
Version of Citadel, if applicable: 0.7.2
Server (please complete the following information):
OS: Ubuntu 22.04
Server: OpenSSH_8.9p1 Ubuntu-3ubuntu0.1, OpenSSL 3.0.2 15 Mar 2022
Version of Citadel, if applicable: none
Additional context
Using the same key from the command line with "ssh -i key root@server" works.
The key starts with "-----BEGIN RSA PRIVATE KEY-----" and ends with "-----END RSA PRIVATE KEY-----"
Not sure if related (feel free to delete this part if not): on another server I get a Citadel.SSHClientError.allAuthenticationOptionsFailed error.
That key uses "-----BEGIN OPENSSH PRIVATE KEY-----" and "-----END OPENSSH PRIVATE KEY-----" as bondaries. It was generated on macOs 14.4.1 with this comand: "ssh-keygen -t rsa -b 4096". When connecting from the command line it works.
The text was updated successfully, but these errors were encountered:
Thanks for the reply. So Citadel doesn't support PEM files?
PEM files are quite common with vps providers. AWS for example: When creating a new vps/instance, they generate keys in PEM or PPK format, using either the RSA or ED25519 algorithms which the user then downloads and uses for their purposes.
Is there any plan to support PEM keys?
For context, I'm evaluating Citadel for an app I'm working on that allows users to connect through ssh to their servers and run commands there. They would provide either a password or a key file (that can be a PEM key pair, a locally generated rsa file, etc.).
Describe the bug
Trying to connect to a server using a RSA private key throws a invalidOpenSSHBoundary error without any other details.
Reproducer Sample
Expected behavior
It should connect to the server.
Client (please complete the following information):
Server (please complete the following information):
Additional context
Using the same key from the command line with "ssh -i key root@server" works.
The key starts with "-----BEGIN RSA PRIVATE KEY-----" and ends with "-----END RSA PRIVATE KEY-----"
Not sure if related (feel free to delete this part if not): on another server I get a Citadel.SSHClientError.allAuthenticationOptionsFailed error.
That key uses "-----BEGIN OPENSSH PRIVATE KEY-----" and "-----END OPENSSH PRIVATE KEY-----" as bondaries. It was generated on macOs 14.4.1 with this comand: "ssh-keygen -t rsa -b 4096". When connecting from the command line it works.
The text was updated successfully, but these errors were encountered: