gpt4 book ai didi

git - Smartgit 始终保持 pop 登录表单

转载 作者:太空狗 更新时间:2023-10-29 14:47:30 25 4
gpt4 key购买 nike

Smartgit 一直 pop 登录表单!

我已经在我的服务器上部署了 git。严格按照 git 设置的说明进行操作。

然后我用puttygen生成开放的SSH私钥,填写密码,把代码放在“public key...authorized_keys file:”框中到 Notepad++ 。

之后,我复制了 key 并将其放入 authorized_keys 文件“git/.ssh/authorized_keys”,并删除了其中的所有结束符。

然后我通过“ssh://git@mygitserver:myport/myproject.git”克隆存储库,指向打开之前生成的SSH私钥,填写密码并登录。

我已经搜索了很多并尝试将所有者更改为 git 用户、更改权限、编辑 key 文件,但仍然无望。

Smartgit 始终保持 pop 登录表单。我该如何解决?

我无法使用 SmartGit 或命令行连接到存储库。这是我的日志内容:`

19143347 (2013-09-07 13:24:00,907) [QThreadPoolThread-2 (smartgit.aES)] WARN  smartgit.ssh.client.ui  - could not authenticate, trying again
java.io.IOException: Publickey authentication failed.
at com.trilead.ssh2.auth.AuthenticationManager.authenticatePublicKey(AuthenticationManager.java:314)
at com.trilead.ssh2.Connection.authenticateWithPublicKey(Connection.java:466)
at com.trilead.ssh2.Connection.authenticateWithPublicKey(Connection.java:519)
at com.syntevo.dvcs.transport.ssh.f.a(SourceFile:39)
at com.syntevo.dvcs.transport.ssh.m.a(SourceFile:150)
at com.syntevo.dvcs.transport.ssh.h.a(SourceFile:141)
at smartgit.aES.a(SourceFile:61)
at smartgit.UL.run(SourceFile:24)
at smartgit.UQ.run(SourceFile:65)
Caused by: java.io.IOException: Sorry, this connection is closed.
at com.trilead.ssh2.transport.TransportManager.sendMessage(TransportManager.java:647)
at com.trilead.ssh2.auth.AuthenticationManager.authenticatePublicKey(AuthenticationManager.java:282)
... 8 more
Caused by: java.io.IOException: Cannot read full block, EOF reached.
at com.trilead.ssh2.crypto.cipher.CipherInputStream.getBlock(CipherInputStream.java:81)
at com.trilead.ssh2.crypto.cipher.CipherInputStream.read(CipherInputStream.java:108)
at com.trilead.ssh2.transport.TransportConnection.receiveMessage(TransportConnection.java:232)
at com.trilead.ssh2.transport.TransportManager.receiveLoop(TransportManager.java:681)
at com.trilead.ssh2.transport.TransportManager$1.run(TransportManager.java:480)
at java.lang.Thread.run(Unknown Source)
19144230 (2013-09-07 13:24:01,790) [QThreadPoolThread-2 (smartgit.aES)] WARN smartgit.ssh.client.ui - could not authenticate, trying again
java.io.IOException: pubkey authentication failed
at com.syntevo.dvcs.transport.ssh.f.a(SourceFile:40)
at com.syntevo.dvcs.transport.ssh.m.a(SourceFile:150)
at com.syntevo.dvcs.transport.ssh.h.a(SourceFile:141)
at smartgit.aES.a(SourceFile:61)
at smartgit.UL.run(SourceFile:24)
at smartgit.UQ.run(SourceFile:65)
19144231 (2013-09-07 13:24:01,791) [Thread-163] ERROR smartgit.ssh.trilead - com.trilead.ssh2.transport.TransportManager: Receive thread: error in receiveLoop: socket closed
19144841 (2013-09-07 13:24:02,401) [main] INFO q.dialog - Showing dialog 75 (@1E95534) '@1D8EDCE - SSH Authentication' (owner: @520C83)
19144859 (2013-09-07 13:24:02,419) [main] INFO q.swt.shellActivation - shell deactivated Shell {Clone}@520C83
19144860 (2013-09-07 13:24:02,420) [main] INFO q.swt.shellActivation - shell activated Shell {SSH Authentication}@1E95534
19144860 (2013-09-07 13:24:02,420) [main] INFO q.swt.shellActivation - Activation change from Shell {Clone}@520C83 to Shell {SSH Authentication}@1E95534
19146675 (2013-09-07 13:24:04,235) [main] INFO q.swt.shellActivation - shell deactivated Shell {SSH Authentication}@1E95534
19146677 (2013-09-07 13:24:04,237) [main] INFO q.swt.shellActivation - Activation change from Shell {SSH Authentication}@1E95534 to null
19264293 (2013-09-07 13:26:01,853) [Thread-165] ERROR smartgit.ssh.trilead - com.trilead.ssh2.transport.TransportManager: Receive thread: error in receiveLoop: Cannot read full block, EOF reached.
23254777 (2013-09-07 14:32:32,337) [main] INFO q.swt.shellActivation - shell activated Shell {SSH Authentication}@1E95534
23254777 (2013-09-07 14:32:32,337) [main] INFO q.swt.shellActivation - Activation change from null to Shell {SSH Authentication}@1E95534
23257318 (2013-09-07 14:32:34,878) [main] INFO q.swt.shellActivation - shell deactivated Shell {SSH Authentication}@1E95534
23257320 (2013-09-07 14:32:34,880) [main] INFO q.swt.shellActivation - Activation change from Shell {SSH Authentication}@1E95534 to null
23325752 (2013-09-07 14:33:43,312) [main] INFO q.swt.shellActivation - shell activated Shell {SSH Authentication}@1E95534
23325752 (2013-09-07 14:33:43,312) [main] INFO q.swt.shellActivation - Activation change from null to Shell {SSH Authentication}@1E95534
23326238 (2013-09-07 14:33:43,798) [main] INFO q.swt.shellActivation - shell deactivated Shell {SSH Authentication}@1E95534
23326239 (2013-09-07 14:33:43,799) [main] INFO q.swt.shellActivation - Activation change from Shell {SSH Authentication}@1E95534 to null

`

最佳答案

  • SmartGit 只能处理 OpenSSH 类型的 key
  • Puttygen 生成 Putty 类型的 key

必须转换(使用 Puttygen)之前创建的 Putty 的 *.ppk

PuTTY-User-Key-File-2: ssh-rsa
...

到OpenSSH的私钥文件

-----BEGIN RSA PRIVATE KEY-----
...
-----END RSA PRIVATE KEY-----

并仅与 Smart* line 一起使用 OpenSSH 版本的 key

关于git - Smartgit 始终保持 pop 登录表单,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/18670201/

25 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com