From: Martin Galvan <martin.galvan@tallertechnologies.com>
To: overseers@sourceware.org
Subject: SSH Public Key
Date: Wed, 27 May 2015 12:48:00 -0000 [thread overview]
Message-ID: <CAOKbPbZkDFS+A=dYLyAgohTbCJm5fAZEZjx1+cfBGwvVOZZLFg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 506 bytes --]
Hi there! Yesterday I got accepted as a Write-after-approval
maintainer for gdb. However, when testing my SSH access I always get a
Permission denied (publickey) error.
Is there a way to fix this? replacekey won't work. Just in case I'm
attaching a public key I just generated.
Thanks a lot, and sorry to bother!
--
Martin Galvan
Software Engineer
Taller Technologies Argentina
San Lorenzo 47, 3rd Floor, Office 5
Córdoba, Argentina
Phone: 54 351 4217888 / +54 351 4218211
[-- Attachment #2: id_rsa.pub --]
[-- Type: application/vnd.ms-publisher, Size: 409 bytes --]
next reply other threads:[~2015-05-27 12:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 12:48 Martin Galvan [this message]
2015-05-27 16:35 ` Christopher Faylor
2015-05-27 17:15 ` Martin Galvan
2015-05-28 0:52 ` Ian Lance Taylor
2015-05-28 13:52 ` Martin Galvan
2015-05-29 0:56 ` Ian Lance Taylor
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='CAOKbPbZkDFS+A=dYLyAgohTbCJm5fAZEZjx1+cfBGwvVOZZLFg@mail.gmail.com' \
--to=martin.galvan@tallertechnologies.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).