432705 - access to sandbox network for try server staging environment

Status: RESOLVED INVALID

(Infrastructure & Operations Graveyard :: Account Requests, task)

Description

[David Ascher (:davida)]

I'd like to take a whack at solving some of the tryserver limitations.  Bhearsum says the easiest way to test my changes is to do so on the build staging server setup.

Comment 1

[Aravind Gottipati [:aravind]]

You should be able to access stuff once you vpn in.  What other access are you looking for?

Comment 2

[David Ascher (:davida)]

I'm trying to ssh to the staging try master.  As per bhearsum's instructions:

(while VPN'ed to both MPT and MV)

sleet:releasenotes davida$ ssh mpt-vpn.mozilla.com ssh cltbld@sm-staging-try-master
Permission denied (publickey,gssapi-with-mic).

With verbose logging on:

sleet:releasenotes davida$ ssh -v mpt-vpn.mozilla.com ssh cltbld@sm-staging-try-master
OpenSSH_4.7p1, OpenSSL 0.9.7l 28 Sep 2006
debug1: Reading configuration data /Users/davida/.ssh/config
debug1: Reading configuration data /etc/ssh_config
debug1: Connecting to mpt-vpn.mozilla.com [63.245.208.142] port 22.
debug1: Connection established.
debug1: identity file /Users/davida/.ssh/identity type -1
debug1: identity file /Users/davida/.ssh/id_rsa type 1
debug1: identity file /Users/davida/.ssh/id_dsa type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_4.5
debug1: match: OpenSSH_4.5 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_4.7
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-cbc hmac-md5 none
debug1: kex: client->server aes128-cbc 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
debug1: Host 'mpt-vpn.mozilla.com' is known and matches the RSA host key.
debug1: Found key in /Users/davida/.ssh/known_hosts:10
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,gssapi-with-mic
debug1: Next authentication method: publickey
debug1: Trying private key: /Users/davida/.ssh/identity
debug1: Offering public key: /Users/davida/.ssh/id_rsa
debug1: Authentications that can continue: publickey,gssapi-with-mic
debug1: Trying private key: /Users/davida/.ssh/id_dsa
debug1: No more authentication methods to try.
Permission denied (publickey,gssapi-with-mic).
sleet:releasenotes davida$ 

Comment 3

[Aravind Gottipati [:aravind]]

looks like your ssh key forwarding may not be set correctly.

Also, from the debug log above, it looks like you are on a Mac, so I am not sure what you'd use on it.

In linux, you would just run an ssh agent on the local machine and forward your keys with ssh -A.

Comment 4

[David Ascher (:davida)]

I already had VPN'ed in, so the first ssh was failing.  The second ssh works fine, except that i don't have the password, but that's something bhearsum can help me out with I think.