On 10 ene, 18:38, Diego Algorta <[email protected]> wrote:
> On 9 ene, 22:21, Diego Algorta <[email protected]> wrote:
>
>
>
> > Johan Sørensen escribió:
>
> > > On Fri, Jan 9, 2009 at 11:42 PM, Diego Algorta <[email protected]> wrote:
> > >> This must be such an stupid issue...
>
> > >> I have experience setting up gitorious on a private server (did it a
> > >> couple of months ago)... but now I'm trying to use the public
> > >> gitorious.org and I'm unable to use my personal push URL.
>
> > >> I created my fork from akitaonrails-gitorious on
> > >>http://gitorious.org/projects/gitorious/repos/oboxodo-gitorious
>
> > >> I uploaded my public key correctly.
>
> > >> But when I try to clone or push using
> > >> [email protected]:gitorious/oboxodo-gitorious.git I get a prompt
> > >> asking me the password for "[email protected]'s password".
>
> > >> Any clue about this?
>
> > > Getting the pam login prompt means it didn't accept your public key
> > > for some reason. Was it marked as "ready" in the ui (it's created in
> > > the system async)? is it the public key for the machine from which
> > > you're pushing?
>
> > Yes to all.
> > Still not working.
>
> Trying to debug this. The public key I added to my gitorious account
> is in file /home/diego/.ssh/id_dsa.pub in my notebook. Here you have
> the output of a verbose attempt to authenticate to [email protected]
> via ssh. Obviously this is not the git command I need to execute, but
> still valid for debugging authentication (interesting bits are at the
> end):
>
> di...@ponja:~$ ssh -vvv [email protected]
...
> debug1: Authentications that can continue: publickey,password
> debug3: start over, passed a different list publickey,password
> debug3: preferred gssapi-keyex,gssapi-with-
> mic,gssapi,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/diego/.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/diego/.ssh/identity
> debug3: no such identity: /home/diego/.ssh/identity
> debug1: Trying private key: /home/diego/.ssh/id_dsa
> debug3: no such identity: /home/diego/.ssh/id_dsa
> debug2: we did not send a packet, disable method
> debug3: authmethod_lookup password
> debug3: remaining preferred: ,password
> debug3: authmethod_is_enabled password
> debug1: Next authentication method: password
> [email protected]'s password:
>
> Hope this can help you help me. :)
Well... Bjrn Lindeijer suggested on #gitorious at irc that maybe my
rsa key I've been using is being rejected by gitorious' server
suspecting it has been "affected by the weak key bug fixed in Debian a
while ago". So I created a new key pair, added it to gitorious via the
web interface, waited for it to be ready and... it works!
Too bad now I had to stop using my old key in other servers which were
still accepting it. :( I already updated them for my new key.
Diego
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Gitorious" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/gitorious?hl=en
-~----------~----~----~----~------~----~------~--~---
