From: Sterling Augustine <saugustine@google.com>
To: overseers@sourceware.org, saugustine@google.com
Subject: Re: Updating my ssh keys
Date: Fri, 29 Jul 2011 11:44:00 -0000 [thread overview]
Message-ID: <CAEG7qUykxCi+XhnVNJgBv9xS2NWSwfkmsFRqEHnddVjNhZAj7Q@mail.gmail.com> (raw)
In-Reply-To: <m3sjpqpfzd.fsf@pepe.airs.com>
[-- Attachment #1: Type: text/plain, Size: 712 bytes --]
Here it is. Thanks.
Sterling
On Thu, Jul 28, 2011 at 8:44 AM, Ian Lance Taylor <ian@airs.com> wrote:
> Sterling Augustine <saugustine@google.com> writes:
>
>> Sterling Augustine here. I have an account at sourcware.org (I believe
>> under sterling, but to be completely honest, I don't remember.) I'm
>> listed as the Xtensa Maintainer for both GCC and binutils. I was also
>> recently granted write-after-approval for GDB.
>>
>> However, after a recent job switch from Tensilica to Google, I no
>> longer have the ssh keys I used to access that account. (and therefore
>> can't update them to any newly generated ones.) What is the best way
>> to get this resolved?
>
> Send a new SSH public key.
>
> Ian
>
[-- Attachment #2: id_rsa.pub --]
[-- Type: application/octet-stream, Size: 421 bytes --]
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCvuI+Iv1elY7QCjBIgfIPjP8wIfmF7FFze6/tvUUP94snBZh4WP6IYL7MqOHG1fRlfqhW45mGypSDEUREZBdib/3LjcjYfWnED9KkzwoblZx4SZkmj73oa5dr3WAmu4X8kcNwZFGq6aZi51Bur+EW6lpERpzYMri30VyPMaG2QZmFecfPzrOE+mwdoCnLqu43I3DM4Y1vg0SKbtIiCGD+r2c3F0en8EHtWTaeyCz8bR04rQm7Dnc7DonMXDmU51clI+ibMGuk9izW4UKnq5xzr4WcLqU/G4Nf2xmFMRpL3Zv841dIerju5k8uyj3/2fWwxVh4UohRoKevxqDkfANF5 saugustine@sterling.mtv.corp.google.com
next prev parent reply other threads:[~2011-07-29 11:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 18:46 Sterling Augustine
2011-07-28 15:44 ` Ian Lance Taylor
2011-07-29 11:44 ` Sterling Augustine [this message]
2011-07-29 13:39 ` Ian Lance Taylor
2011-07-29 13:40 ` 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=CAEG7qUykxCi+XhnVNJgBv9xS2NWSwfkmsFRqEHnddVjNhZAj7Q@mail.gmail.com \
--to=saugustine@google.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).