updatekey doesn't work?

updatekey doesn't work?

[Randolph Chung]

tausq@riot:~$ ssh  sourceware.org updatekey < hia.pub
error  unrecognized request `ssh-dss 
AAAAB3NzaC1kc3MAAACBAPpkGNu6EOb+OrdyDiLe9GSPifbJEHhJxMVD5ovBO4U3MOhraWfMSeJ0LAJo9qfNHRpEj9J3Rk1KPx+Mz9USJEbODU8dQKU7Gj232QFBlsntM6aUY7Ts+VZP+vLASVeu6U72xWtZtytrrv2UY3QDu6pAbKi5jhFscLzmGUOB4JcVAAAAFQC4kgzvesDqlogpUfPtBGbix2GPqwAAAIBseQo+og/MNdNvYtsl0TLVaAjejgYg0JvVe2FKnPInCo2Z6VzH8KERGFY59q02CoJ5bG+4BSyZEYw0YZrn6zbvkPru213Oa3416Ybpsk/JF/y87HhpmrjMYZvk05G8DQy5XuUlKAM2S5DXcH1H2dO8RCFW0BDrQvUJKpnSs2a+fgAAAIEA7kHOWf+bViT7m9l4R2LKguVdpsWqaBPFRCCQDW/inzs9wiQJXahaVHUBWwBExSS+HxFb/K9e3udbuYCm9dFKWIzgRAw7y+znKI/qI0VuKzv7YKa2GxrkmBOujPRvOETGPzX3P94j12SJ4glFk7tpqy5qSp1yi/fQeHVC+AfimgU= 
tausq@hiauly3.hia.nrc.ca'

is that the right procedure to use to add a key to my authorized_keys file?

randolph

Re: updatekey doesn't work?

[Christopher Faylor]

On Sat, Nov 19, 2005 at 03:16:44PM +0800, Randolph Chung wrote:
>tausq@riot:~$ ssh  sourceware.org updatekey < hia.pub
>error  unrecognized request `ssh-dss 
>AAAAB3NzaC1kc3MAAACBAPpkGNu6EOb+OrdyDiLe9GSPifbJEHhJxMVD5ovBO4U3MOhraWfMSeJ0LAJo9qfNHRpEj9J3Rk1KPx+Mz9USJEbODU8dQKU7Gj232QFBlsntM6aUY7Ts+VZP+vLASVeu6U72xWtZtytrrv2UY3QDu6pAbKi5jhFscLzmGUOB4JcVAAAAFQC4kgzvesDqlogpUfPtBGbix2GPqwAAAIBseQo+og/MNdNvYtsl0TLVaAjejgYg0JvVe2FKnPInCo2Z6VzH8KERGFY59q02CoJ5bG+4BSyZEYw0YZrn6zbvkPru213Oa3416Ybpsk/JF/y87HhpmrjMYZvk05G8DQy5XuUlKAM2S5DXcH1H2dO8RCFW0BDrQvUJKpnSs2a+fgAAAIEA7kHOWf+bViT7m9l4R2LKguVdpsWqaBPFRCCQDW/inzs9wiQJXahaVHUBWwBExSS+HxFb/K9e3udbuYCm9dFKWIzgRAw7y+znKI/qI0VuKzv7YKa2GxrkmBOujPRvOETGPzX3P94j12SJ4glFk7tpqy5qSp1yi/fQeHVC+AfimgU= 
>tausq@hiauly3.hia.nrc.ca'
>
>is that the right procedure to use to add a key to my authorized_keys file?

For gcc people, yes.  People in the gcc group were transitioned to use
a system which understands "updatekey".  You are a member of the gdb group
and, since gdb still uses cvs, there was no reason to switch you.

I've modified your account so that you can use updatekey now, however.

cgf

Re: updatekey doesn't work?

[Christopher Faylor]

[please use the overseers mailing list for sourceware requests]
On Sat, Dec 03, 2005 at 02:45:18PM +0800, Randolph Chung wrote:
>Christopher Faylor wrote:
>>On Sat, Nov 19, 2005 at 03:16:44PM +0800, Randolph Chung wrote:
>>>is that the right procedure to use to add a key to my authorized_keys 
>>>file?
>>
>>
>>For gcc people, yes.  People in the gcc group were transitioned to use
>>a system which understands "updatekey".  You are a member of the gdb group
>>and, since gdb still uses cvs, there was no reason to switch you.
>>
>>I've modified your account so that you can use updatekey now, however.
>
>i finally had a chance to try this, and it still doens't work, 
>unfortunately.

Try it again.

cgf

Re: updatekey doesn't work?

[Randolph Chung]

Christopher Faylor wrote:
> [please use the overseers mailing list for sourceware requests]
> On Sat, Dec 03, 2005 at 02:45:18PM +0800, Randolph Chung wrote:
> 
>>Christopher Faylor wrote:
>>
>>>On Sat, Nov 19, 2005 at 03:16:44PM +0800, Randolph Chung wrote:
>>>
>>>>is that the right procedure to use to add a key to my authorized_keys 
>>>>file?
>>>
>>>
>>>For gcc people, yes.  People in the gcc group were transitioned to use
>>>a system which understands "updatekey".  You are a member of the gdb group
>>>and, since gdb still uses cvs, there was no reason to switch you.
>>>
>>>I've modified your account so that you can use updatekey now, however.
>>
>>i finally had a chance to try this, and it still doens't work, 
>>unfortunately.
> 
> 
> Try it again.

Sorry, still doesn't work.

randolph

Re: updatekey doesn't work?

[Christopher Faylor]

On Sun, Dec 04, 2005 at 09:52:37AM +0800, Randolph Chung wrote:
>Christopher Faylor wrote:
>>[please use the overseers mailing list for sourceware requests]
>>On Sat, Dec 03, 2005 at 02:45:18PM +0800, Randolph Chung wrote:
>>
>>>Christopher Faylor wrote:
>>>
>>>>On Sat, Nov 19, 2005 at 03:16:44PM +0800, Randolph Chung wrote:
>>>>
>>>>>is that the right procedure to use to add a key to my authorized_keys 
>>>>>file?
>>>>
>>>>
>>>>For gcc people, yes.  People in the gcc group were transitioned to use
>>>>a system which understands "updatekey".  You are a member of the gdb 
>>>>group
>>>>and, since gdb still uses cvs, there was no reason to switch you.
>>>>
>>>>I've modified your account so that you can use updatekey now, however.
>>>
>>>i finally had a chance to try this, and it still doens't work, 
>>>unfortunately.
>>
>>
>>Try it again.
>
>Sorry, still doesn't work.

"doesn't work" == ?

It should at least be different.

cgf

Re: updatekey doesn't work?

[Randolph Chung]

>>>Try it again.
>>
>>Sorry, still doesn't work.
> 
> 
> "doesn't work" == ?
> 
> It should at least be different.

seems the same:

tausq@riot:~$ ssh -v  sources.redhat.com updatekey < hia.pub
OpenSSH_4.2p1 Debian-5, OpenSSL 0.9.8a 11 Oct 2005
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to sources.redhat.com [209.132.176.174] port 22.
debug1: Connection established.
debug1: identity file /home/tausq/.ssh/identity type -1
debug1: identity file /home/tausq/.ssh/id_rsa type -1
debug1: identity file /home/tausq/.ssh/id_dsa type 2
debug1: Remote protocol version 1.99, remote software version OpenSSH_3.9p1
debug1: match: OpenSSH_3.9p1 pat OpenSSH_3.*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_4.2p1 Debian-5
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 'sources.redhat.com' is known and matches the RSA host key.
debug1: Found key in /home/tausq/.ssh/known_hosts:8
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: /home/tausq/.ssh/identity
debug1: Trying private key: /home/tausq/.ssh/id_rsa
debug1: Offering public key: /home/tausq/.ssh/id_dsa
debug1: Remote: Port forwarding disabled.
debug1: Remote: X11 forwarding disabled.
debug1: Remote: Agent forwarding disabled.
debug1: Remote: Forced command: /usr/local/bin/cvs server
debug1: Server accepts key: pkalg ssh-dss blen 434
debug1: read PEM private key done: type DSA
debug1: Remote: Port forwarding disabled.
debug1: Remote: X11 forwarding disabled.
debug1: Remote: Agent forwarding disabled.
debug1: Remote: Forced command: /usr/local/bin/cvs server
debug1: Authentication succeeded (publickey).
debug1: channel 0: new [client-session]
debug1: Entering interactive session.
debug1: Sending environment.
debug1: Sending command: updatekey
error  unrecognized request `ssh-dss 
AAAAB3NzaC1kc3MAAACBAPpkGNu6EOb+OrdyDiLe9GSPifbJEHhJxMVD5ovBO4U3MOhraWfMSeJ0LAJo9qfNHRpEj9J3Rk1KPx+Mz9USJEbODU8dQKU7Gj232QFBlsntM6aUY7Ts+VZP+vLASVeu6U72xWtZtytrrv2UY3QDu6pAbKi5jhFscLzmGUOB4JcVAAAAFQC4kgzvesDqlogpUfPtBGbix2GPqwAAAIBseQo+og/MNdNvYtsl0TLVaAjejgYg0JvVe2FKnPInCo2Z6VzH8KERGFY59q02CoJ5bG+4BSyZEYw0YZrn6zbvkPru213Oa3416Ybpsk/JF/y87HhpmrjMYZvk05G8DQy5XuUlKAM2S5DXcH1H2dO8RCFW0BDrQvUJKpnSs2a+fgAAAIEA7kHOWf+bViT7m9l4R2LKguVdpsWqaBPFRCCQDW/inzs9wiQJXahaVHUBWwBExSS+HxFb/K9e3udbuYCm9dFKWIzgRAw7y+znKI/qI0VuKzv7YKa2GxrkmBOujPRvOETGPzX3P94j12SJ4glFk7tpqy5qSp1yi/fQeHVC+AfimgU= 
tausq@hiauly3.hia.nrc.ca'
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug1: channel 0: free: client-session, nchannels 1
debug1: fd 0 clearing O_NONBLOCK
debug1: Transferred: stdin 0, stdout 0, stderr 0 bytes in 0.3 seconds
debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 0.0
debug1: Exit status 0

Re: updatekey doesn't work?

[Christopher Faylor]

On Sun, Dec 04, 2005 at 11:15:55AM +0800, Randolph Chung wrote:
>>>>Try it again.
>>>
>>>Sorry, still doesn't work.
>>
>>
>>"doesn't work" == ?
>>
>>It should at least be different.
>
>seems the same:
>
>tausq@riot:~$ ssh -v  sources.redhat.com updatekey < hia.pub
>debug1: Remote: Forced command: /usr/local/bin/cvs server

Ah, I see.  I forgot to remove the cvs server restriction from
.ssh/authorized_keys.

It should work now.

cgf