From: "Moore, Catherine" <Catherine_Moore@mentor.com>
To: "overseers@gcc.gnu.org" <overseers@gcc.gnu.org>
Subject: ssh keys
Date: Thu, 13 Oct 2016 22:42:00 -0000 [thread overview]
Message-ID: <6afada6c44614247ae75cbf9fcd90faa@SVR-ORW-MBX-04.mgc.mentorg.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2603 bytes --]
It looks like I can no longer checkout out repositories with write access.
I'm attaching my two public key files (rsa/dsa). Would you please update them?
Hopefully that will fix the problem, but if not, I'm going to need some help figuring out what's wrong.
Thanks,
Catherine
SVN_SSH="ssh -v" svn co svn+ssh://clm@gcc.gnu.org/svn/gcc/trunk gcc
OpenSSH_6.6.1, OpenSSL 1.0.1f 6 Jan 2014
debug1: Reading configuration data /home/cmoore/.ssh/config
debug1: /home/cmoore/.ssh/config line 4: Applying options for gcc.gnu.org
debug1: /home/cmoore/.ssh/config line 31: Applying options for *
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Control socket "/tmp/ssh_clm@gcc.gnu.org:22" does not exist
debug1: Connecting to gcc.gnu.org [209.132.180.131] port 22.
debug1: Connection established.
debug1: identity file /home/cmoore/.ssh/internal_dsa type 2
debug1: identity file /home/cmoore/.ssh/internal_dsa-cert type -1
debug1: identity file /home/cmoore/.ssh/internal_rsa type 1
debug1: identity file /home/cmoore/.ssh/internal_rsa-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.7
debug1: Remote protocol version 1.99, remote software version OpenSSH_5.3
debug1: match: OpenSSH_5.3 pat OpenSSH_5* compat 0x0c000000
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: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<3072<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: Server host key: RSA 1d:1e:46:7f:4d:73:8d:10:20:c3:4c:5a:34:14:44:23
debug1: Host 'gcc.gnu.org' is known and matches the RSA host key.
debug1: Found key in /home/cmoore/.ssh/known_hosts:2
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
debug1: Next authentication method: publickey
debug1: Offering DSA public key: /home/cmoore/.ssh/internal_dsa
debug1: Authentications that can continue: publickey
debug1: Offering RSA public key: /home/cmoore/.ssh/internal_rsa
debug1: Authentications that can continue: publickey
debug1: No more authentication methods to try.
Permission denied (publickey).
[-- Attachment #2: internal_dsa.pub --]
[-- Type: application/x-mspublisher, Size: 1524 bytes --]
[-- Attachment #3: internal_rsa.pub --]
[-- Type: application/x-mspublisher, Size: 405 bytes --]
next reply other threads:[~2016-10-13 22:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 22:42 Moore, Catherine [this message]
2016-10-14 1:04 ` Frank Ch. Eigler
2016-10-14 14:24 ` Moore, Catherine
-- strict thread matches above, loose matches on Subject: below --
2021-10-11 1:46 Eric Gallager
2021-10-11 11:48 ` Mark Wielaard
2021-10-11 19:38 ` Eric Gallager
2021-10-11 19:59 ` Mark Wielaard
2006-02-15 4:21 bud davis
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=6afada6c44614247ae75cbf9fcd90faa@SVR-ORW-MBX-04.mgc.mentorg.com \
--to=catherine_moore@mentor.com \
--cc=overseers@gcc.gnu.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).