|
List Info
Thread: Help on new helix community account
|
|
| Help on new helix community account |

|
2006-09-19 05:38:33 |
hi, all
I am a new comer in the helix community. I created a new
account
yesterday and am trying to check out ribosome from
cvs.helixcommunity.org following the instructions at
https://common.helixcommunity.org/2004/devdocs/quickst
art. However I got
the following message when I tried to run $ssh -v
irenehuang cvs.helixcommunity.org (where irenehuang is my
account in
helixcommunity.org, and I set the password to be empty when
using
$ssh-keygen -t dsa -f $HOME/.ssh/helixid_dsa to generate the
public
key )
===============================================
Sun_SSH_1.1, SSH protocols 1.5/2.0, OpenSSL 0x0090801f
debug1: Reading configuration data
/export/home/real/.ssh/config
debug1: Applying options for cvs.helixcommunity.org
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Rhosts Authentication disabled, originating port
will not be
trusted.
debug1: ssh_connect: needpriv 0
debug1: Executing proxy command:
exec /usr/lib/ssh/ssh-socks5-proxy-connect
cvs.helixcommunity.org 22
debug1: identity file /export/home/real/.ssh/helixid_dsa
type 2
debug1: Remote protocol version 1.99, remote software
version
OpenSSH_3.9p1
debug1: match: OpenSSH_3.9p1 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-Sun_SSH_1.1
debug1: Failed to acquire GSS-API credentials for any
mechanisms (No
credentials were supplied, or the credentials were
unavailable or
inaccessible
Unknown code 0
)
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: Peer sent proposed langtags, ctos:
debug1: Peer sent proposed langtags, stoc:
debug1: We proposed langtags, ctos: i-default
debug1: We proposed langtags, stoc: i-default
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: dh_gen_key: priv key bits set: 133/256
debug1: bits set: 988/2048
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host 'cvs.helixcommunity.org' is known and matches
the RSA host
key.
debug1: Found key in /export/home/real/.ssh/known_hosts:1
debug1: bits set: 1019/2048
debug1: ssh_rsa_verify: signature correct
debug1: newkeys: mode 1
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: newkeys: mode 0
debug1: SSH2_MSG_NEWKEYS received
debug1: done: ssh_kex2.
debug1: send SSH2_MSG_SERVICE_REQUEST
debug1: got SSH2_MSG_SERVICE_ACCEPT
debug1: Authentications that can continue:
publickey,gssapi-with-mic,password
debug1: Next authentication method: gssapi-with-mic
debug1: Failed to acquire GSS-API credentials for any
mechanisms (No
credentials were supplied, or the credentials were
unavailable or
inaccessible
Unknown code 0
)
debug1: Next authentication method: publickey
debug1: Trying public key:
/export/home/real/.ssh/helixid_dsa
debug1: Authentications that can continue:
publickey,gssapi-with-mic,password
debug1: Next authentication method: password
irenehuang cvs.helixcommunity.org's password:
debug1: Authentications that can continue:
publickey,gssapi-with-mic,password
Permission denied, please try again.
irenehuang cvs.helixcommunity.org's password:
===============================================
No matter how I tried with my account password, the server
refuses to
let me check out ribosome.
Can anyone help me with this?
Thanks in advance.
--Irene
_______________________________________________
Player-dev mailing list
Player-dev helixcommunity.org
http://lists.helixcommunity.org/mailman/listinfo/play
er-dev
|
|
| Help on new helix community account |

|
2006-09-25 21:09:53 |
At 10:38 PM 9/18/2006, Irene (Shi Ying) Huang wrote:
>hi, all
>
>I am a new comer in the helix community. I created a new
account
>yesterday and am trying to check out ribosome from
>cvs.helixcommunity.org following the instructions at
>https://common.helixcommunity.org/2004/devdocs/quickst
art. However I got
>the following message when I tried to run $ssh -v
>irenehuang cvs.helixcommunity.org (where irenehuang
is my account in
>helixcommunity.org, and I set the password to be empty
when using
>$ssh-keygen -t dsa -f $HOME/.ssh/helixid_dsa to generate
the public
>key )
Have you tried again after that? It is possible that the
first day or so
you would have more problems, but if you have followed the
instruction on
the quickstart page, you should be able to get over this
problem. If it
really appears to be a server issue, there are server admins
who can help you.
--
Daniel Yek
>===============================================
>Sun_SSH_1.1, SSH protocols 1.5/2.0, OpenSSL 0x0090801f
>debug1: Reading configuration data
/export/home/real/.ssh/config
>debug1: Applying options for cvs.helixcommunity.org
>debug1: Reading configuration data /etc/ssh/ssh_config
>debug1: Rhosts Authentication disabled, originating port
will not be
>trusted.
>debug1: ssh_connect: needpriv 0
>debug1: Executing proxy command:
>exec /usr/lib/ssh/ssh-socks5-proxy-connect
cvs.helixcommunity.org 22
>debug1: identity file /export/home/real/.ssh/helixid_dsa
type 2
>debug1: Remote protocol version 1.99, remote software
version
>OpenSSH_3.9p1
>debug1: match: OpenSSH_3.9p1 pat OpenSSH*
>debug1: Enabling compatibility mode for protocol 2.0
>debug1: Local version string SSH-2.0-Sun_SSH_1.1
>debug1: Failed to acquire GSS-API credentials for any
mechanisms (No
>credentials were supplied, or the credentials were
unavailable or
>inaccessible
>Unknown code 0
>)
>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: Peer sent proposed langtags, ctos:
>debug1: Peer sent proposed langtags, stoc:
>debug1: We proposed langtags, ctos: i-default
>debug1: We proposed langtags, stoc: i-default
>debug1: SSH2_MSG_KEX_DH_GEX_REQUEST sent
>debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
>debug1: dh_gen_key: priv key bits set: 133/256
>debug1: bits set: 988/2048
>debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
>debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
>debug1: Host 'cvs.helixcommunity.org' is known and
matches the RSA host
>key.
>debug1: Found key in
/export/home/real/.ssh/known_hosts:1
>debug1: bits set: 1019/2048
>debug1: ssh_rsa_verify: signature correct
>debug1: newkeys: mode 1
>debug1: SSH2_MSG_NEWKEYS sent
>debug1: expecting SSH2_MSG_NEWKEYS
>debug1: newkeys: mode 0
>debug1: SSH2_MSG_NEWKEYS received
>debug1: done: ssh_kex2.
>debug1: send SSH2_MSG_SERVICE_REQUEST
>debug1: got SSH2_MSG_SERVICE_ACCEPT
>debug1: Authentications that can continue:
>publickey,gssapi-with-mic,password
>debug1: Next authentication method: gssapi-with-mic
>debug1: Failed to acquire GSS-API credentials for any
mechanisms (No
>credentials were supplied, or the credentials were
unavailable or
>inaccessible
>Unknown code 0
>)
>debug1: Next authentication method: publickey
>debug1: Trying public key:
/export/home/real/.ssh/helixid_dsa
>debug1: Authentications that can continue:
>publickey,gssapi-with-mic,password
>debug1: Next authentication method: password
>irenehuang cvs.helixcommunity.org's password:
>debug1: Authentications that can continue:
>publickey,gssapi-with-mic,password
>Permission denied, please try again.
>irenehuang cvs.helixcommunity.org's password:
>===============================================
>
>No matter how I tried with my account password, the
server refuses to
>let me check out ribosome.
>
>Can anyone help me with this?
>
>Thanks in advance.
>
>--Irene
>
_______________________________________________
Player-dev mailing list
Player-dev helixcommunity.org
http://lists.helixcommunity.org/mailman/listinfo/play
er-dev
|
|
| Help on new helix community account |

|
2006-09-26 01:32:38 |
|
Hi Irene,
Things seem correct on your side. It is probably due to the fact that
we are having CVS system upgrade and your ssh public key is not updated
into file in time. We are trying our best to bring the CVS system back
to normal.
Thanks,
Kinson
Daniel Yek wrote:
mailone.real.com"
type="cite">At 10:38 PM 9/18/2006, Irene (Shi Ying) Huang wrote:
hi, all
I am a new comer in the helix community. I created a new account
yesterday and am trying to check out ribosome from
cvs.helixcommunity.org following the instructions at
https://common.helixcommunity.org/2004/devdocs/quickstart. However I
got
the following message when I tried to run $ssh -v
cvs.helixcommunity.org">irenehuang cvs.helixcommunity.org (where irenehuang is my account in
helixcommunity.org, and I set the password to be empty when using
$ssh-keygen -t dsa -f $HOME/.ssh/helixid_dsa to generate the public
key )
Have you tried again after that? It is possible that the first day or
so you would have more problems, but if you have followed the
instruction on the quickstart page, you should be able to get over this
problem. If it really appears to be a server issue, there are server
admins who can help you.
|
| Help on new helix community account |

|
2006-09-25 21:09:53 |
At 10:38 PM 9/18/2006, Irene (Shi Ying) Huang wrote:
>hi, all
>
>I am a new comer in the helix community. I created a new
account
>yesterday and am trying to check out ribosome from
>cvs.helixcommunity.org following the instructions at
>https://common.helixcommunity.org/2004/devdocs/quickst
art. However I got
>the following message when I tried to run $ssh -v
>irenehuang cvs.helixcommunity.org (where irenehuang
is my account in
>helixcommunity.org, and I set the password to be empty
when using
>$ssh-keygen -t dsa -f $HOME/.ssh/helixid_dsa to generate
the public
>key )
Have you tried again after that? It is possible that the
first day or so
you would have more problems, but if you have followed the
instruction on
the quickstart page, you should be able to get over this
problem. If it
really appears to be a server issue, there are server admins
who can help you.
--
Daniel Yek
>===============================================
>Sun_SSH_1.1, SSH protocols 1.5/2.0, OpenSSL 0x0090801f
>debug1: Reading configuration data
/export/home/real/.ssh/config
>debug1: Applying options for cvs.helixcommunity.org
>debug1: Reading configuration data /etc/ssh/ssh_config
>debug1: Rhosts Authentication disabled, originating port
will not be
>trusted.
>debug1: ssh_connect: needpriv 0
>debug1: Executing proxy command:
>exec /usr/lib/ssh/ssh-socks5-proxy-connect
cvs.helixcommunity.org 22
>debug1: identity file /export/home/real/.ssh/helixid_dsa
type 2
>debug1: Remote protocol version 1.99, remote software
version
>OpenSSH_3.9p1
>debug1: match: OpenSSH_3.9p1 pat OpenSSH*
>debug1: Enabling compatibility mode for protocol 2.0
>debug1: Local version string SSH-2.0-Sun_SSH_1.1
>debug1: Failed to acquire GSS-API credentials for any
mechanisms (No
>credentials were supplied, or the credentials were
unavailable or
>inaccessible
>Unknown code 0
>)
>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: Peer sent proposed langtags, ctos:
>debug1: Peer sent proposed langtags, stoc:
>debug1: We proposed langtags, ctos: i-default
>debug1: We proposed langtags, stoc: i-default
>debug1: SSH2_MSG_KEX_DH_GEX_REQUEST sent
>debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
>debug1: dh_gen_key: priv key bits set: 133/256
>debug1: bits set: 988/2048
>debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
>debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
>debug1: Host 'cvs.helixcommunity.org' is known and
matches the RSA host
>key.
>debug1: Found key in
/export/home/real/.ssh/known_hosts:1
>debug1: bits set: 1019/2048
>debug1: ssh_rsa_verify: signature correct
>debug1: newkeys: mode 1
>debug1: SSH2_MSG_NEWKEYS sent
>debug1: expecting SSH2_MSG_NEWKEYS
>debug1: newkeys: mode 0
>debug1: SSH2_MSG_NEWKEYS received
>debug1: done: ssh_kex2.
>debug1: send SSH2_MSG_SERVICE_REQUEST
>debug1: got SSH2_MSG_SERVICE_ACCEPT
>debug1: Authentications that can continue:
>publickey,gssapi-with-mic,password
>debug1: Next authentication method: gssapi-with-mic
>debug1: Failed to acquire GSS-API credentials for any
mechanisms (No
>credentials were supplied, or the credentials were
unavailable or
>inaccessible
>Unknown code 0
>)
>debug1: Next authentication method: publickey
>debug1: Trying public key:
/export/home/real/.ssh/helixid_dsa
>debug1: Authentications that can continue:
>publickey,gssapi-with-mic,password
>debug1: Next authentication method: password
>irenehuang cvs.helixcommunity.org's password:
>debug1: Authentications that can continue:
>publickey,gssapi-with-mic,password
>Permission denied, please try again.
>irenehuang cvs.helixcommunity.org's password:
>===============================================
>
>No matter how I tried with my account password, the
server refuses to
>let me check out ribosome.
>
>Can anyone help me with this?
>
>Thanks in advance.
>
>--Irene
>
_______________________________________________
Player-dev mailing list
Player-dev helixcommunity.org
http://lists.helixcommunity.org/mailman/listinfo/play
er-dev
|
|
| Help on new helix community account |

|
2006-09-26 01:32:38 |
|
Hi Irene,
Things seem correct on your side. It is probably due to the fact that
we are having CVS system upgrade and your ssh public key is not updated
into file in time. We are trying our best to bring the CVS system back
to normal.
Thanks,
Kinson
Daniel Yek wrote:
mailone.real.com"
type="cite">At 10:38 PM 9/18/2006, Irene (Shi Ying) Huang wrote:
hi, all
I am a new comer in the helix community. I created a new account
yesterday and am trying to check out ribosome from
cvs.helixcommunity.org following the instructions at
https://common.helixcommunity.org/2004/devdocs/quickstart. However I
got
the following message when I tried to run $ssh -v
cvs.helixcommunity.org">irenehuang cvs.helixcommunity.org (where irenehuang is my account in
helixcommunity.org, and I set the password to be empty when using
$ssh-keygen -t dsa -f $HOME/.ssh/helixid_dsa to generate the public
key )
Have you tried again after that? It is possible that the first day or
so you would have more problems, but if you have followed the
instruction on the quickstart page, you should be able to get over this
problem. If it really appears to be a server issue, there are server
admins who can help you.
|
[1-5]
|
|