From: Ed Smith-Rowland <3dw4rd@verizon.net>
To: overseers@gcc.gnu.org
Subject: Lost ssh key
Date: Wed, 22 Feb 2012 14:54:00 -0000 [thread overview]
Message-ID: <4F45016A.9050405@verizon.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 233 bytes --]
Greetings,
I have an account emsr@gcc.gnu.org. I have completely lost my ssh keys
so I can't get updatekey to work.
Could someone please set my key up? Here is a new public key attached.
Thank you very much,
Ed Smith-Rowland
[-- Attachment #2: id_dsa.pub --]
[-- Type: text/plain, Size: 602 bytes --]
ssh-dss AAAAB3NzaC1kc3MAAACBAMSD/znDAqHv1zkko9rKB6dRznGPf/mUk1PP5LkC1C+rPmCxbWGZM2S2lEesanGUTvitxNYL6GK/A5vhYCYtH4np92fUBnbJykHFxKM8k3zjVjDJbHsMWT07cDrUqkJaSAg24Ib6lkTUsA/x7DsD4Ee9mc6ckIudcjiG9MzHeavDAAAAFQCApIar+WwHl4EW3CgNtRtqqoUzOwAAAIA96RkSzA47lD3l+Vivlq+sCSinsTiYuoq5b4U6VWRvpgrGxtoAGIgiF0l9xBmbapND49BetxZ9rhq30B/iqp1oCGb1dU+Mf5mYEjrxWzKxHJBcTNmhkuwbHBSzOqbjZmTSj3YjuCiNQzhTW2wsbfFIJ5BogvSmV5mt0Y3hH7QlagAAAIAkKtjZfP/fInySTFOIaOzuDy94LtESwvGPTlgMlL7AeXzyc/uiUHjFgJtEME5UTq5fJ7Y4L2fqtb5nC3wNfkHo8mnAWOY8TOmS6jLlME69bwC6WIi47klAvmM4zSPDXDhjNE3M6nh/o4bT5ZFFgap6mfdEmuHzmv7WDb6jd8ecXg== ed@bad-horse
next reply other threads:[~2012-02-22 14:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 14:54 Ed Smith-Rowland [this message]
2012-02-22 16:10 ` Ian Lance Taylor
2016-02-25 19:52 Lost SSH key Martin Galvan
2016-02-26 0:36 ` Ian Lance Taylor
2016-03-01 18:15 ` Martin Galvan
2016-03-02 4:47 ` Ian Lance Taylor
2016-03-02 5:34 ` Hans-Peter Nilsson
2016-03-02 6:00 ` Ian Lance Taylor
2016-03-02 13:29 ` Martin Galvan
2016-03-02 13:51 ` Frank Ch. Eigler
2016-03-02 14:00 ` Martin Galvan
2016-03-02 14:37 ` Martin Galvan
2019-07-08 13:43 Andrew Sutton
2019-07-08 13:53 ` Carlos O'Donell
2021-03-11 8:59 Robin Dapp
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=4F45016A.9050405@verizon.net \
--to=3dw4rd@verizon.net \
--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).