不要在GitLab中使用SSH [英] Don't work ssh in GitLab

查看:1344
本文介绍了不要在GitLab中使用SSH的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

在我的一个PC命令ssh -T git@github.lcl.loc中工作并输出Welcome to GitLab, Anonymous!.

In my one PC command ssh -T git@github.lcl.loc work and output Welcome to GitLab, Anonymous!.

但是在我的两个PC命令输出中

But in my two PC command output

$ ssh -vT git@github.lcl.loc
OpenSSH_4.6p1, OpenSSL 0.9.8e 23 Feb 2007
debug1: Connecting to github.lcl.loc [192.168.1.104] port 22.
debug1: Connection established.
debug1: identity file /c/Documents and Settings/n.nozdrin-plotnickij.LCL/.ssh/id
entity type -1
debug1: identity file /c/Documents and Settings/n.nozdrin-plotnickij.LCL/.ssh/id
_rsa type 1
debug1: identity file /c/Documents and Settings/n.nozdrin-plotnickij.LCL/.ssh/id
_dsa type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_6.0p1 Debia
n-4+deb7u2
debug1: match: OpenSSH_6.0p1 Debian-4+deb7u2 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_4.6
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-cbc hmac-md5 none
debug1: kex: client->server aes128-cbc hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host 'github.lcl.loc' is known and matches the RSA host key.
debug1: Found key in /c/Documents and Settings/n.nozdrin-plotnickij.LCL/.ssh/kno
wn_hosts:1
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,password
debug1: Next authentication method: publickey
debug1: Trying private key: /c/Documents and Settings/n.nozdrin-plotnickij.LCL/.
ssh/identity
debug1: Offering public key: /c/Documents and Settings/n.nozdrin-plotnickij.LCL/
.ssh/id_rsa
debug1: Authentications that can continue: publickey,password
debug1: Trying private key: /c/Documents and Settings/n.nozdrin-plotnickij.LCL/.
ssh/id_dsa
debug1: Next authentication method: password
git@github.lcl.loc's password:
debug1: Authentications that can continue: publickey,password
Permission denied, please try again.
git@github.lcl.loc's password:
debug1: Authentications that can continue: publickey,password
Permission denied, please try again.
git@github.lcl.loc's password:
debug1: Authentications that can continue: publickey,password
debug1: No more authentication methods to try.
Permission denied (publickey,password).

我生成新的RSA密钥.什么也没有变. 密钥是在没有密码的情况下创建的.

I generate new RSA key. Nothing has changed. Key was created without a password.

如果您从git用户输入密码,请以git用户身份访问控制台.

If you enter the password from the user git, get access to the console as user git.

GitLab v7.9.4 亚搏体育app Shell 2.6.2 在没有omnibus-gitlab的情况下安装...

GitLab v7.9.4 GitLab Shell 2.6.2 Install whithout omnibus-gitlab...

推荐答案

确定.当我发现该文件未添加密钥时,我删除了文件/var/opt/gitlab/.ssh/authorized_keys并加注了命令sudo gitlab-ctl reconfigure.

OK. When I noticed that file don't add keys, I delete file /var/opt/gitlab/.ssh/authorized_keys and stared command sudo gitlab-ctl reconfigure.

此文件创建.通过Web界面,我删除了所有密钥,然后再次添加它们.

This file create. Via web-interface I delete all keys, and add their again.

成功了!

这篇关于不要在GitLab中使用SSH的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆