872334 - Commit access for hg.ecmascript.org for Bill Sahlas

Status: RESOLVED FIXED

(mozilla.org Graveyard :: Server Operations, task)

Description

[Dave Herman [:dherman]]

Attachment: Bill Sahlas's public key

+++ This bug was initially created as a clone of Bug #862585 +++

+++ This bug was initially created as a clone of Bug #701067 +++

+++ This bug was initially created as a clone of Bug #627884 +++

Bill Sahlas <[e-mail]> needs commit access to hg.ecmascript.org/tests/test262. Note that Bill does *not* need to sign a committer's agreement (see bug 604656). I have attached Bill's public key.

Thanks,
Dave

Comment 1

[Dave Herman [:dherman]]

(another "clone bug" mistake)

Comment 2

[Shyam Mani [:fox2mike]]

Done. +ldap + scm_ecmascript.

Comment 3

[Bill Sahlas]

Attachment: new pub key

the public key I gave you, as it turns out, is corrupt (I'm missing the private key on my local) .  Please replace my public key with this new attachment.

Comment 4

[Peter Radcliffe [:pir]]

Key replaced with new public key. Give it a short while for the new key to be pushed out.

Comment 5

[Bill Sahlas]

Hey,

I'm failing to get access. 

I've got my ssh config/env setup correctly - here's my settings for hg.ecmascript.org

~/.ssh/config

Host hg.ecmascript.org
    HostName hg.ecmascript.org
    User [e-mail]
    IdentityFile ~/.ssh/bsahlas2_rsa


Here's a trace from an attempt at a connection using -v

ecma (master) > ssh -v hg.ecmascript.org
OpenSSH_5.6p1, OpenSSL 0.9.8r 8 Feb 2011
debug1: Reading configuration data /Users/bsahlas/.ssh/config
debug1: Applying options for hg.ecmascript.org
debug1: Reading configuration data /etc/ssh_config
debug1: Applying options for *
debug1: Connecting to hg.ecmascript.org [63.245.215.26] port 22.
debug1: Connection established.
debug1: identity file /Users/bsahlas/.ssh/bsahlas2_rsa type 1
debug1: identity file /Users/bsahlas/.ssh/bsahlas2_rsa-cert type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.4
debug1: match: OpenSSH_5.4 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.6
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-md5 none
debug1: kex: client->server aes128-ctr 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
The authenticity of host 'hg.ecmascript.org (63.245.215.26)' can't be established.
RSA key fingerprint is fa:e8:5a:cc:de:02:e0:c7:6e:ff:14:92:90:b9:12:be.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'hg.ecmascript.org,63.245.215.26' (RSA) to the list of known hosts.
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by server
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 RSA public key: /Users/bsahlas/.ssh/id_rsa
debug1: Authentications that can continue: publickey
debug1: Offering RSA public key: /Users/bsahlas/.ssh/bsahlas2_rsa
debug1: Server accepts key: pkalg ssh-rsa blen 279
debug1: PEM_read_PrivateKey failed
debug1: read PEM private key done: type <unknown>
debug1: PEM_read_PrivateKey failed
debug1: read PEM private key done: type <unknown>
debug1: No more authentication methods to try.
Permission denied (publickey).
ecma (master) >

Comment 6

[Bill Sahlas]

Attachment: another newly generated key using ssh-keygen -t rsa -C "[e-mail]"

Comment 7

[Bill Sahlas]

Comment on attachment 751673 [details]
another newly generated key using ssh-keygen -t rsa -C "[e-mail]"

If it helps to have another public key.

Comment 8

[Shyam Mani [:fox2mike]]

Bill,

I added this new key, give it a spin later. I'm fox2mike on irc.mozilla.org (#it) and I can look at the logs when you give it a shot.

Right now I see :

hgssh1 sshd[3829]: Failed publickey for [e-mail]

Comment 9

[Peter Radcliffe [:pir]]

debug1: Server accepts key: pkalg ssh-rsa blen 279
debug1: PEM_read_PrivateKey failed
debug1: read PEM private key done: type <unknown>
debug1: PEM_read_PrivateKey failed
debug1: read PEM private key done: type <unknown>
debug1: No more authentication methods to try.

That looks like it can't open the private half of the key. Are they passphrase protected (as they should be) and your ssh-agent isn't working properly, maybe?

Comment 10

[Bill Sahlas]

I'm good now, thanks guys

Authenticated to hg.ecmascript.org ([63.245.215.26]:22).