From: Tim Guirgies <lt.infiltrator@gmail.com>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: gitosis asking for password
Date: Wed, 1 Jun 2011 12:23:16 +1000 [thread overview]
Message-ID: <20110601022313.GA3025@Imperial-SD-Longsword> (raw)
In-Reply-To: <vpqy61mrha6.fsf@bauges.imag.fr>
[-- Attachment #1: Type: text/plain, Size: 2227 bytes --]
On Tue, May 31, 2011 at 06:01:05PM +0200, Matthieu Moy wrote:
> Gitosis is no longer maintained. You should probably be trying gitolite
> instead.
Ah; well, I guess now's as good a time as any to migrate to gitolite
then. I set up gitosis a few years ago and it hadn't been giving me any
problems.
> If it asks for password, then it's probably a plain SSH problem. Try
> reproducing it with e.g.
...
> ssh -vvv gitosis@overlord.imperial.fleet
I did this just to see, and this is quite interesting:
debug3: Not a RSA1 key file /home/tim/.ssh/id_rsa.
debug2: key_type_from_name: unknown key type '-----BEGIN'
debug3: key_read: missing keytype
debug2: key_type_from_name: unknown key type 'Proc-Type:'
debug3: key_read: missing keytype
debug2: key_type_from_name: unknown key type 'DEK-Info:'
debug3: key_read: missing keytype
debug3: key_read: missing whitespace (x~20)
debug2: key_type_from_name: unknown key type '-----END'
debug3: key_read: missing keytype
debug1: identity file /home/tim/.ssh/id_rsa type 1
...
debug2: key: /home/tim/.ssh/id_rsa (0x7f7c8f0f7020)
debug2: key: /home/tim/.ssh/id_dsa ((nil))
debug1: Authentications that can continue: publickey,password
debug3: start over, passed a different list publickey,password
debug3: preferred
gssapi-keyex,gssapi-with-mic,publickey,keyboard-interactive,password
debug3: authmethod_lookup publickey
debug3: remaining preferred: keyboard-interactive,password
debug3: authmethod_is_enabled publickey
debug1: Next authentication method: publickey
debug1: Offering public key: /home/tim/.ssh/id_rsa
debug3: send_pubkey_test
debug2: we sent a publickey packet, wait for reply
debug1: Authentications that can continue: publickey,password
debug1: Trying private key: /home/tim/.ssh/id_dsa
debug3: no such identity: /home/tim/.ssh/id_dsa
debug2: we did not send a packet, disable method
...
That is very odd, as I didn't change anything after ssh-keygen and
gitosis-init. I suppose it's irrelevant anyway, as I'll be switching to
gitolite.
Thanks for the advice, and sorry about the noise.
Tim
--
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-06-01 2:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 15:49 gitosis asking for password Tim Guirgies
2011-05-31 16:01 ` Matthieu Moy
2011-06-01 2:23 ` Tim Guirgies [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-05-31 15:42 Tim Guirgies
2011-06-01 18:24 ` Drew Northup
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110601022313.GA3025@Imperial-SD-Longsword \
--to=lt.infiltrator@gmail.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).