Closed
Bug 1309029
Opened 9 years ago
Closed 9 years ago
Problems with using hg account
Categories
(Infrastructure & Operations :: MOC: Service Requests, task)
Infrastructure & Operations
MOC: Service Requests
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mcsmurf, Assigned: vinh)
Details
I wanted to use my hg/Mercurial account again after a while, but it no longer seems to be working. My LDAP account id is mcsmurf@mcsmurf.de. Can you please check if there's anything wrong with it (disabled?) or what could cause this problem?
What I tried so far: Generated a new SSH private/public key and uploaded it to login.mozilla.com about one day ago (did not change anything).
My .ssh config looks like this:
----
Host hg.mozilla.org
User mcsmurf@mcsmurf.de
----
Error message:
$ hg push
pushing to ssh://hg.mozilla.org/SeaMonkey/seamonkey-project-org/
remote: Permission denied (publickey).
abort: no suitable response from remote hg!
Also tried another repository (comm-central), same problem.
SSH log:
$ ssh -v mcsmurf@mcsmurf.de@hg.mozilla.org
OpenSSH_5.4p1, OpenSSL 1.0.0 29 Mar 2010
debug1: Reading configuration data /c/Users/Frank/.ssh/config
debug1: Applying options for hg.mozilla.org
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to hg.mozilla.org [63.245.215.102] port 22.
debug1: Connection established.
debug1: identity file /c/Users/Frank/.ssh/id_rsa type 1
debug1: identity file /c/Users/Frank/.ssh/id_rsa-cert type -1
debug1: identity file /c/Users/Frank/.ssh/id_dsa type 2
debug1: identity file /c/Users/Frank/.ssh/id_dsa-cert type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_6.6.1
debug1: match: OpenSSH_6.6.1 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.4
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes256-ctr hmac-ripemd160 none
debug1: kex: client->server aes256-ctr hmac-ripemd160 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<4096<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 'hg.mozilla.org' is known and matches the RSA host key.
debug1: Found key in /c/Users/Frank/.ssh/known_hosts:5
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
debug1: Next authentication method: publickey
debug1: Offering public key: /c/Users/Frank/.ssh/id_rsa
debug1: Authentications that can continue: publickey
debug1: Offering public key: /c/Users/Frank/.ssh/id_dsa
debug1: Authentications that can continue: publickey
debug1: No more authentication methods to try.
Permission denied (publickey).
Updated•9 years ago
|
Assignee: nobody → vhua
Status: NEW → ASSIGNED
Comment 1•9 years ago
|
||
Do you still have the private key for 'New SSH key' on login.mozilla.com? If so, can you try using that one? I'm seeing access attempts for your newest key ('new SSH key 2') and an old DSA key, and I'm wondering if there's a bug in the lookup script. It returns both RSA keys, and your LDAP attribs look correct, so if you have that key I'd like to see if that works.
If you don't, I would suggest removing it from login.mozilla.com entirely.
| Reporter | ||
Comment 2•9 years ago
|
||
Things seem to work again :) so, basically this was a user error. I guess the SSH key I originally uploaded never worked (that's my only explanation). In my attempts I did yesterday the problem was I copied the SSH key including the line breaks (via clipboard from vim in console), which was wrong and did not work. When I removed the line breaks, things started to work again.
Sorry for the inconvenience, bug can be closed.
Updated•9 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•