Advertising
- Anonymous
- Monday, May 7th, 2012 at 3:22:51am MDT
- milez@xcat:~$ ssh -v git.ezscratch.com info
- OpenSSH_5.8p1 Debian-7ubuntu1, OpenSSL 1.0.0e 6 Sep 2011
- debug1: Reading configuration data /home/milez/.ssh/config
- debug1: Applying options for git.ezscratch.com
- debug1: Reading configuration data /etc/ssh/ssh_config
- debug1: Applying options for *
- debug1: Connecting to git.ezscratch.com [176.9.136.50] port 22667.
- debug1: Connection established.
- debug1: identity file /home/milez/.ssh/id_rsa-gitolite type 1
- debug1: Checking blacklist file /usr/share/ssh/blacklist.RSA-2048
- debug1: Checking blacklist file /etc/ssh/blacklist.RSA-2048
- debug1: identity file /home/milez/.ssh/id_rsa-gitolite-cert type -1
- debug1: Remote protocol version 2.0, remote software version OpenSSH_5.8p1 Debian-7ubuntu1
- debug1: match: OpenSSH_5.8p1 Debian-7ubuntu1 pat OpenSSH*
- debug1: Enabling compatibility mode for protocol 2.0
- debug1: Local version string SSH-2.0-OpenSSH_5.8p1 Debian-7ubuntu1
- 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: sending SSH2_MSG_KEX_ECDH_INIT
- debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
- debug1: Server host key: RSA 1b:2c:c2:2d:91:43:03:36:de:44:cd:65:5c:47:ad:ef
- debug1: Host '[git.ezscratch.com]:22667' is known and matches the RSA host key.
- debug1: Found key in /home/milez/.ssh/known_hosts:16
- 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,password
- debug1: Next authentication method: publickey
- debug1: Offering RSA public key: /home/milez/.ssh/id_rsa-gitolite
- debug1: Authentications that can continue: publickey,password
- debug1: Offering RSA public key: git@Ubuntu-1110-oneiric-64-minimal
- debug1: Authentications that can continue: publickey,password
- debug1: Offering RSA public key: milez@awesome
- debug1: Server accepts key: pkalg ssh-rsa blen 279
- debug1: Authentication succeeded (publickey).
- Authenticated to git.ezscratch.com ([176.9.136.50]:22667).
- debug1: channel 0: new [client-session]
- debug1: Requesting no-more-sessions@openssh.com
- debug1: Entering interactive session.
- debug1: Remote: Forced command.
- debug1: Remote: Port forwarding disabled.
- debug1: Remote: X11 forwarding disabled.
- debug1: Remote: Agent forwarding disabled.
- debug1: Remote: Pty allocation disabled.
- debug1: Remote: Forced command.
- debug1: Remote: Port forwarding disabled.
- debug1: Remote: X11 forwarding disabled.
- debug1: Remote: Agent forwarding disabled.
- debug1: Remote: Pty allocation disabled.
- debug1: Sending environment.
- debug1: Sending env LANG = en_US.UTF-8
- debug1: Sending command: info
- hello milez, this is gitolite v2.3-32-ga8a3792 running on git 1.7.5.4
- the gitolite config gives you the following access:
- R W AffSystem
- R W CodeIgniter
- R W EZScratch
- R W EasyPeasyScratchMe
- R W FBScratch
- R W GameServer
- R W LotteryServer
- R W NoodlesFramework
- R W ScratchAPI
- R W ScratchCardClients
- R W gitolite-admin
- debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
- debug1: client_input_channel_req: channel 0 rtype eow@openssh.com reply 0
- debug1: channel 0: free: client-session, nchannels 1
- Transferred: sent 3240, received 3208 bytes, in 0.4 seconds
- Bytes per second: sent 8522.4, received 8438.2
- debug1: Exit status 0
advertising
Update the Post
Either update this post and resubmit it with changes, or make a new post.
You may also comment on this post.
Please note that information posted here will expire by default in one month. If you do not want it to expire, please set the expiry time above. If it is set to expire, web search engines will not be allowed to index it prior to it expiring. Items that are not marked to expire will be indexable by search engines. Be careful with your passwords. All illegal activities will be reported and any information will be handed over to the authorities, so be good.
