[GH-ISSUE #1935] 不支持私钥??导入报Unsupported key format #1161

Open
opened 2026-02-27 00:02:27 +03:00 by kerem · 9 comments
Owner

Originally created by @coLATin on GitHub (Nov 29, 2020).
Original GitHub issue: https://github.com/electerm/electerm/issues/1935

Electerm version:v1.9.31

Operating system(linux, macos, or windows7/8/10?):

MacOS:Bigsur

Expected Behavior

不支持私钥??

Can you reproduce the same behavior in other terminal:

Current Behavior

Possible Solution

Steps to Reproduce

Context (Environment)

Detailed Description

导入私钥后,无法连接,提示: Cannot parse privateKey: Unsupported key format
可是在Termius下就是这样配的呀...

Suggestions?

Originally created by @coLATin on GitHub (Nov 29, 2020). Original GitHub issue: https://github.com/electerm/electerm/issues/1935 <!--- Provide some basic info --> ## Electerm version:v1.9.31 ## Operating system(linux, macos, or windows7/8/10?): MacOS:Bigsur ## Expected Behavior <!--- Tell me what should happen --> 不支持私钥?? ## Can you reproduce the same behavior in other terminal: <!--- If same bahavior happens in other terminal, maybe it is supposed to be like this or not a problem of terminal app --> ## Current Behavior <!--- Tell me what happens instead of the expected behavior --> ## Possible Solution <!--- Not obligatory, but suggest a fix/reason for the bug, --> ## Steps to Reproduce <!--- Provide a link to a live example, or an unambiguous set of steps to --> <!--- reproduce this bug. Include code to reproduce, if relevant --> ## Context (Environment) <!--- How has this issue affected you? What are you trying to accomplish? --> <!--- Providing context helps us come up with a solution that is most useful in the real world --> ## Detailed Description <!--- Provide a detailed description of the change or addition you are proposing --> 导入私钥后,无法连接,提示: Cannot parse privateKey: Unsupported key format 可是在Termius下就是这样配的呀... ## Suggestions? <!--- Not a bug report, just some thoughts or suggestions? It is totally OK and welcome too -->
Author
Owner

@zxdong262 commented on GitHub (Nov 30, 2020):

什么格式的呢?可以贴一下吗(注意脱敏)

<!-- gh-comment-id:735501454 --> @zxdong262 commented on GitHub (Nov 30, 2020): 什么格式的呢?可以贴一下吗(注意脱敏)
Author
Owner

@coLATin commented on GitHub (Nov 30, 2020):

您好,格式如下:
-----BEGIN PRIVATE KEY-----
XXXXXXXXXXXXXXXXXXXXXXXXXXXX
-----END PRIVATE KEY-----

<!-- gh-comment-id:735559811 --> @coLATin commented on GitHub (Nov 30, 2020): 您好,格式如下: -----BEGIN PRIVATE KEY----- XXXXXXXXXXXXXXXXXXXXXXXXXXXX -----END PRIVATE KEY-----
Author
Owner

@zxdong262 commented on GitHub (Nov 30, 2020):

@coLATin 请问创建的命令是什么

<!-- gh-comment-id:735622750 --> @zxdong262 commented on GitHub (Nov 30, 2020): @coLATin 请问创建的命令是什么
Author
Owner

@coLATin commented on GitHub (Nov 30, 2020):

ssh-keygen -t rsa -C "myemail@xxx.com"
另外貌似没支持公钥?总之一样的配法,Termius就可以ssh挂上去的,奇怪...

<!-- gh-comment-id:735677142 --> @coLATin commented on GitHub (Nov 30, 2020): ssh-keygen -t rsa -C "myemail@xxx.com" 另外貌似没支持公钥?总之一样的配法,Termius就可以ssh挂上去的,奇怪...
Author
Owner

@zxdong262 commented on GitHub (Dec 1, 2020):

@coLATin 我试验我这里是可以的,我也想不出会有什么问题。

<!-- gh-comment-id:736128437 --> @zxdong262 commented on GitHub (Dec 1, 2020): @coLATin 我试验我这里是可以的,我也想不出会有什么问题。
Author
Owner

@rossbu commented on GitHub (Jan 1, 2022):

这个问题轻松可以复现, 开一台ec2 machine and download private key xxx.pem file such as ec2-user on linux , 2. 简单的用cyber duck or termius 连接主机ec2 by the private key file xxx.pem. 没问题。 3. 同样的方式用electerm fails. 总结,注意其他然间都是最后一节指定文件就好。这里private key在界面上显示的私有钥匙的内容。转码可能会有问题,读取字符集也有可能出问题

<!-- gh-comment-id:1003470860 --> @rossbu commented on GitHub (Jan 1, 2022): 这个问题轻松可以复现, 开一台ec2 machine and download private key xxx.pem file such as ec2-user on linux , 2. 简单的用cyber duck or termius 连接主机ec2 by the private key file xxx.pem. 没问题。 3. 同样的方式用electerm fails. 总结,注意其他然间都是最后一节指定文件就好。这里private key在界面上显示的私有钥匙的内容。转码可能会有问题,读取字符集也有可能出问题
Author
Owner

@kkk935208447 commented on GitHub (Mar 13, 2024):

您好,格式如下: -----BEGIN PRIVATE KEY----- XXXXXXXXXXXXXXXXXXXXXXXXXXXX -----END PRIVATE KEY-----

谢谢老哥,解决了

<!-- gh-comment-id:1994225803 --> @kkk935208447 commented on GitHub (Mar 13, 2024): > 您好,格式如下: -----BEGIN PRIVATE KEY----- XXXXXXXXXXXXXXXXXXXXXXXXXXXX -----END PRIVATE KEY----- 谢谢老哥,解决了
Author
Owner

@zxdong262 commented on GitHub (Mar 14, 2024):

您好,格式如下: -----BEGIN PRIVATE KEY----- XXXXXXXXXXXXXXXXXXXXXXXXXXXX -----END PRIVATE KEY-----

谢谢老哥,解决了

请问是最新版可以了吗?

<!-- gh-comment-id:1996601370 --> @zxdong262 commented on GitHub (Mar 14, 2024): > > 您好,格式如下: -----BEGIN PRIVATE KEY----- XXXXXXXXXXXXXXXXXXXXXXXXXXXX -----END PRIVATE KEY----- > > 谢谢老哥,解决了 请问是最新版可以了吗?
Author
Owner

@kkk935208447 commented on GitHub (Mar 14, 2024):

可以的,-----BEGIN PRIVATE KEY----- -----END PRIVATE KEY-----
也要复制,选择字符串的那个选项,选择文件electerm似乎识别不出隐藏文件

ZHAO Xudong @.***> 於 2024年3月14日 週四 下午2:16寫道:

您好,格式如下: -----BEGIN PRIVATE KEY----- XXXXXXXXXXXXXXXXXXXXXXXXXXXX -----END
PRIVATE KEY-----

谢谢老哥,解决了

请问是最新版可以了吗?


Reply to this email directly, view it on GitHub
https://github.com/electerm/electerm/issues/1935#issuecomment-1996601370,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALSTK2UC3NZUPR427VH7B7TYYE6CPAVCNFSM4UGXIT42U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOJZGY3DAMJTG4YA
.
You are receiving this because you commented.Message ID:
@.***>

<!-- gh-comment-id:1997231760 --> @kkk935208447 commented on GitHub (Mar 14, 2024): 可以的,-----BEGIN PRIVATE KEY----- -----END PRIVATE KEY----- 也要复制,选择字符串的那个选项,选择文件electerm似乎识别不出隐藏文件 ZHAO Xudong ***@***.***> 於 2024年3月14日 週四 下午2:16寫道: > 您好,格式如下: -----BEGIN PRIVATE KEY----- XXXXXXXXXXXXXXXXXXXXXXXXXXXX -----END > PRIVATE KEY----- > > 谢谢老哥,解决了 > > 请问是最新版可以了吗? > > — > Reply to this email directly, view it on GitHub > <https://github.com/electerm/electerm/issues/1935#issuecomment-1996601370>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ALSTK2UC3NZUPR427VH7B7TYYE6CPAVCNFSM4UGXIT42U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOJZGY3DAMJTG4YA> > . > You are receiving this because you commented.Message ID: > ***@***.***> >
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/electerm#1161
No description provided.