authorized_keys2 is used to do atomic updates to authorized_keys, so it might appear and disappear
Best regards, Sytse Sijbrandij CEO GitLab B.V. On Wed, Sep 24, 2014 at 10:57 PM, Jesse Adelman <je...@hello.com> wrote: > Hey, thanks for the response! The odd thing is that, at least via the > shell, the file indeed exists, contains the keys as automatically generated > by Gitlab, and permissions are apparently correct. Note that the error is > "Permission denined", while a later error on a file that doesn't exist in > the same directory (authorized_keys2), gets a "No such file" error. > > Very odd. > > Jesse > > On Wed, Sep 24, 2014 at 12:46 AM, Sytse Sijbrandij <sy...@gitlab.com> > wrote: > >> Hi Jesse, >> >> It is strange that the authorized_keys file seems to be missing: >> Sep 23 23:18:42 gitlab-sauu sshd[18956]: debug1: Could not open >> authorized keys '/var/opt/gitlab/.ssh/authorized_keys': Permission denied >> >> Have you run gitlab-ctl reconfigure? >> >> >> Best regards, >> Sytse Sijbrandij >> CEO GitLab B.V. >> >> On Wed, Sep 24, 2014 at 1:27 AM, <je...@hello.com> wrote: >> >>> Howdy. I've recently installed the GitLab VM on Google Cloud Compute >>> cloud, and I'm having some teething pain as a new user. I've checked the >>> permissions on the git user home directory, and it looks correct, but I get >>> this result in the sshd logs on the gitlab host: >>> >>> Sep 23 23:18:42 gitlab-sauu sshd[18957]: debug1: kex: client->server >>> aes128-ctr hmac-md5 none >>> Sep 23 23:18:42 gitlab-sauu sshd[18957]: debug1: kex: server->client >>> aes128-ctr hmac-md5 none >>> Sep 23 23:18:42 gitlab-sauu sshd[18957]: debug1: >>> SSH2_MSG_KEX_DH_GEX_REQUEST received >>> Sep 23 23:18:42 gitlab-sauu sshd[18957]: debug1: >>> SSH2_MSG_KEX_DH_GEX_GROUP sent >>> Sep 23 23:18:42 gitlab-sauu sshd[18957]: debug1: expecting >>> SSH2_MSG_KEX_DH_GEX_INIT >>> Sep 23 23:18:42 gitlab-sauu sshd[18957]: debug1: >>> SSH2_MSG_KEX_DH_GEX_REPLY sent >>> Sep 23 23:18:42 gitlab-sauu sshd[18957]: debug1: SSH2_MSG_NEWKEYS sent >>> Sep 23 23:18:42 gitlab-sauu sshd[18957]: debug1: expecting >>> SSH2_MSG_NEWKEYS >>> Sep 23 23:18:42 gitlab-sauu sshd[18957]: debug1: SSH2_MSG_NEWKEYS >>> received >>> Sep 23 23:18:42 gitlab-sauu sshd[18957]: debug1: KEX done >>> Sep 23 23:18:42 gitlab-sauu sshd[18957]: debug1: userauth-request for >>> user git service ssh-connection method none >>> Sep 23 23:18:42 gitlab-sauu sshd[18957]: debug1: attempt 0 failures 0 >>> Sep 23 23:18:42 gitlab-sauu sshd[18956]: reverse mapping checking >>> getaddrinfo for 70.80.208.web-pass.com [208.80.70.74] failed - >>> POSSIBLE BREAK-IN ATTEMPT! >>> Sep 23 23:18:42 gitlab-sauu sshd[18956]: debug1: PAM: initializing for >>> "git" >>> Sep 23 23:18:42 gitlab-sauu sshd[18956]: debug1: PAM: setting PAM_RHOST >>> to "IP A" >>> Sep 23 23:18:42 gitlab-sauu sshd[18956]: debug1: PAM: setting PAM_TTY to >>> "ssh" >>> Sep 23 23:18:42 gitlab-sauu sshd[18957]: debug1: userauth-request for >>> user git service ssh-connection method publickey >>> Sep 23 23:18:42 gitlab-sauu sshd[18957]: debug1: attempt 1 failures 0 >>> Sep 23 23:18:42 gitlab-sauu sshd[18957]: debug1: test whether >>> pkalg/pkblob are acceptable >>> Sep 23 23:18:42 gitlab-sauu sshd[18956]: debug1: temporarily_use_uid: >>> 507/507 (e=0/0) >>> Sep 23 23:18:42 gitlab-sauu sshd[18956]: debug1: trying public key file >>> /var/opt/gitlab/.ssh/authorized_keys >>> Sep 23 23:18:42 gitlab-sauu sshd[18956]: debug1: Could not open >>> authorized keys '/var/opt/gitlab/.ssh/authorized_keys': Permission denied >>> Sep 23 23:18:42 gitlab-sauu sshd[18956]: debug1: restore_uid: 0/0 >>> Sep 23 23:18:42 gitlab-sauu sshd[18956]: debug1: temporarily_use_uid: >>> 507/507 (e=0/0) >>> Sep 23 23:18:42 gitlab-sauu sshd[18956]: debug1: trying public key file >>> /var/opt/gitlab/.ssh/authorized_keys2 >>> Sep 23 23:18:42 gitlab-sauu sshd[18956]: debug1: Could not open >>> authorized keys '/var/opt/gitlab/.ssh/authorized_keys2': No such file or >>> directory >>> Sep 23 23:18:42 gitlab-sauu sshd[18956]: debug1: restore_uid: 0/0 >>> Sep 23 23:18:42 gitlab-sauu sshd[18956]: Failed publickey for git from >>> [IP A} port 33269 ssh2 >>> Sep 23 23:18:42 gitlab-sauu sshd[18957]: Connection closed by [IP A] >>> Sep 23 23:18:42 gitlab-sauu sshd[18957]: debug1: do_cleanup >>> Sep 23 23:18:42 gitlab-sauu sshd[18956]: debug1: do_cleanup >>> Sep 23 23:18:42 gitlab-sauu sshd[18956]: debug1: PAM: cleanup >>> >>> Any clues? Also, we are using our GAD accounts to try HTTP, and that >>> also seems to not work from the git shell command. Are there pointers >>> somewhere for us to use to ensure smooth operation with GAD accounts? >>> >>> Thanks! >>> >>> Jesse Adelman >>> hello.com >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "GitLab" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to gitlabhq+unsubscr...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/gitlabhq/c3f70e6c-3f12-4efb-9922-1dab718f6ec2%40googlegroups.com >>> <https://groups.google.com/d/msgid/gitlabhq/c3f70e6c-3f12-4efb-9922-1dab718f6ec2%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "GitLab" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/gitlabhq/4oRe7qziHYc/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> gitlabhq+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/gitlabhq/CAJTzhG9pHmc5W2vqqVZ42VeFvgmu7hnubZACFL2o9OkDY-H7GA%40mail.gmail.com >> <https://groups.google.com/d/msgid/gitlabhq/CAJTzhG9pHmc5W2vqqVZ42VeFvgmu7hnubZACFL2o9OkDY-H7GA%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Productivity and Systems Engineer > Hello.com > > -- > You received this message because you are subscribed to the Google Groups > "GitLab" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to gitlabhq+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/gitlabhq/CALOVXq4YgLYc5e0_1twv3T5fq-uqyyTNU7V%2BZ%2Bh0MdCUk%2Bv%2BbA%40mail.gmail.com > <https://groups.google.com/d/msgid/gitlabhq/CALOVXq4YgLYc5e0_1twv3T5fq-uqyyTNU7V%2BZ%2Bh0MdCUk%2Bv%2BbA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "GitLab" group. To unsubscribe from this group and stop receiving emails from it, send an email to gitlabhq+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/CAJTzhG8yGMzHT7%3DCcf1wkKCNFpdTbRUtZ06kxQY83mFOebcphA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
