From: "Dorit Naishlos" <DORIT@il.ibm.com>
To: overseers@gcc.gnu.org
Subject: Please replace the public SSH key for my account
Date: Thu, 02 Oct 2003 17:34:00 -0000 [thread overview]
Message-ID: <OFC3EABBE7.317D26BA-ONC2256DB3.005ED090-C2256DB3.00616180@telaviv.ibm.com> (raw)
I had lost the ssh keys that I used for setting up CVS write access for my
account (dorit@gcc.gnu.org). Please replace the public key with the
following new key:
ssh-rsa
AAAAB3NzaC1yc2EAAAABIwAAAIEAwSBUJUSDlDCxvwwjW+4VH82JLnlqEeY6oztaUwBqWpAw/5dczZovuKPL0IwcVrKp2Prjq41RTRs5sWq4SKN33rogFQoQk1EnruLQkH7v0PQwPLQk2hg5YHcC2ijs8N0XwHYPoGeGpbdCHVyKcrPfOVbXGJknJ3rdTC16t21Cpws
dorit@mac-dorit.haifa.ibm.com
thanks,
dorit
----- Forwarded by Dorit Naishlos/Haifa/IBM on 02/10/2003 20:15 -----
Dorit Naishlos
To: Gerald Pfeifer <gerald@pfeifer.com>
01/10/2003 14:41 cc: overseers@gcc.gnu.org
From: Dorit Naishlos/Haifa/IBM@IBMIL
Subject: Re: Welcome to gcc.gnu.org(Document link: Dorit Naishlos)
> why did you send the SSH key of a machine
> instead of using a _personal_ SSH key (which you can copy to arbitrarily
> many hosts)?
>
I did create a personal key, but unfortunately I don't have access to the
files that contain the private and public keys that I had generated
(they are in the corrupted disk from which I cannot recover data anymore).
So, I need to generate new keys, and the question is -
how do I send my new public key - do I need to fill up the same on-line
form? the form says:
"Note that if you already have an account on sources.redhat.com or
gcc.gnu.org for CVS write access, then do not use this form. Instead send
an email to the overseers mail account..."
thanks,
dorit
Gerald Pfeifer
<gerald@pfeifer.c To: Dorit Naishlos/Haifa/IBM@IBMIL
om> cc: overseers@gcc.gnu.org
Subject: Re: Welcome to gcc.gnu.org
01/10/2003 12:54
On Wed, 1 Oct 2003, Dorit Naishlos wrote:
> The machine from which I sent an SSH key for authentication had crashed;
I cannot answer this, but why did you send the SSH key of a machine
instead of using a _personal_ SSH key (which you can copy to arbitrarily
many hosts)?
Please refer to `man ssh-keygen` for details.
Gerald
--
Gerald Pfeifer (Jerry) gerald@pfeifer.com
http://www.pfeifer.com/gerald/
next reply other threads:[~2003-10-02 17:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-02 17:34 Dorit Naishlos [this message]
2003-10-02 17:42 ` Christopher Faylor
2003-10-02 18:10 ` Dorit Naishlos
2003-10-02 18:15 ` Christopher Faylor
2003-10-05 9:48 ` Dorit Naishlos
2003-10-05 16:58 ` Christopher Faylor
2003-10-06 21:53 ` Dorit Naishlos
2003-12-08 9:14 Dhananjay R. Deshpande
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=OFC3EABBE7.317D26BA-ONC2256DB3.005ED090-C2256DB3.00616180@telaviv.ibm.com \
--to=dorit@il.ibm.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).