From: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
To: "Frank Ch. Eigler" <fche@redhat.com>, overseers@sourceware.org
Subject: Re: [Fwd: Welcome to sourceware.org]
Date: Fri, 30 Mar 2007 14:36:00 -0000 [thread overview]
Message-ID: <460D2040.6000604@linux.vnet.ibm.com> (raw)
In-Reply-To: <20070330125225.GD26915@redhat.com>
> This ssh-rsa key is on file for your account. Please check that it is
> still correct.
>
> ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAIEAwJ4NdHSUP5ifyz0ZFZFbepw6bvY57AHJ9xwMKuzaGwWAHJD/JEm4vouykIt8hPPRIx3tN9gOtI30ps1dQLLKO8Iz71vHUY3xV3psIF6cVRgxsEB1Z/Khnuv5dnSAgOBWU5gKwqpEMN/adDQX4So8SevkssJwEA1xrM7eNZOfsKc= srikar@srikar.in.ibm.com
>
This doesn't seem to match my .ssh/id_rsa.pub
The key on my system seems to be this.
----------------------------------------------------------------------------------------------------------------------------
ssh-rsa
AAAAB3NzaC1yc2EAAAABIwAAAQEAq3adtVzcmEfP5BF51osIjzAZcOXKt0fmCbM0IT0wzjdTEsaJ7aK5YXRhpp7etavjd2ItrK4b9FCk+b067vwUGAt373OESwh6MxVsMUoWtYEtIFHt3rKToww2IC0aTeRUCKZqtQhSgQYNj3QlN8rFYrknMkEcPi+j5gk0o7C+Yi9S8ND7VMv4t453NGqlmQMixMGwYlO7gDwYIjOMrzFPHgdmJ88Cm6yA/+7Uk/b7wN5sZQMFjcaYUoYy3gerdf6BrZaDZPlcunSaFU9BOQ5nSWF6+0EiYcpvzTJLkXMjNMnVVwJgsV961Z3IHkh4VTqThNd2Yns1LWD1ZBFOlZU7nQ==
srikar@srikar.in.ibm.com
----------------------------------------------------------------------------------------------------------------------------
However I don't recall updating /reinstalling my system after requesting
for the sourceware.org id.
Not sure how my keys have changed.
I am extremely sorry for the same.
Can you please update the key as given in this mail.
Also is it possible to have a key each from two different machines using
the
"updatekey" command?
--
Thanks and Regards
Srikar
PS: I also tried 'ssh -v srikar@sourceware.org "echo $PATH"
'OpenSSH_3.9p1, OpenSSL 0.9.7a Feb 19 2003
and the output is as follows.
--------------------------------------------------------------------------------------------------
OpenSSH_3.9p1, OpenSSL 0.9.7a Feb 19 2003
debug1: Reading configuration data /home/srikar/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to sourceware.org [209.132.176.174] port 22.
debug1: Connection established.
debug1: identity file /home/srikar/.ssh/identity type -1
debug1: identity file /home/srikar/.ssh/id_rsa type 1
debug1: identity file /home/srikar/.ssh/id_dsa type -1
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-OpenSSH_3.9p1
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
Warning: Permanently added 'sourceware.org,209.132.176.174' (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: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,gssapi-with-mic
debug1: Next authentication method: gssapi-with-mic
debug1: Authentications that can continue: publickey,gssapi-with-mic
debug1: Authentications that can continue: publickey,gssapi-with-mic
debug1: Next authentication method: publickey
debug1: Trying private key: /home/srikar/.ssh/identity
debug1: Offering public key: /home/srikar/.ssh/id_rsa
debug1: Authentications that can continue: publickey,gssapi-with-mic
debug1: Trying private key: /home/srikar/.ssh/id_dsa
debug1: No more authentication methods to try.
Permission denied (publickey,gssapi-with-mic).
--------------------------------------------------------------------------------------------------------------------------------------------------------------
next prev parent reply other threads:[~2007-03-30 14:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-30 11:53 Srikar Dronamraju
2007-03-30 11:59 ` Christopher Faylor
2007-03-30 12:56 ` Frank Ch. Eigler
2007-03-30 14:36 ` Srikar Dronamraju [this message]
2007-04-04 12:00 ` Srikar Dronamraju
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=460D2040.6000604@linux.vnet.ibm.com \
--to=srikar@linux.vnet.ibm.com \
--cc=fche@redhat.com \
--cc=overseers@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).