From: "Frank Ch. Eigler" <fche@redhat.com>
To: William Cohen <wcohen@redhat.com>
Cc: overseers@sourceware.org
Subject: Re: new id_dsa.pub
Date: Mon, 02 May 2005 20:16:00 -0000 [thread overview]
Message-ID: <20050502201635.GE15292@redhat.com> (raw)
In-Reply-To: <42768594.9060507@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 590 bytes --]
Hi -
> I had to generate a new id_dsa to be able to get access to the
> cvs.fedora.redhat.com (id didn't work with the older format version).
Your ssh client or agent can juggle multiple keypairs. There is no
need to update all your login destinations/servers for each new key
you happen to create, as long as you don't erase previous ones.
> Would it be possible to install the attached id_dsa.pub, so
> sources.redhat.com also works?
Done, though since your sourceware account has full shell access, you
could've added it to your own authorized_keys file.
- FChE
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-05-02 20:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-02 19:55 William Cohen
2005-05-02 20:16 ` Frank Ch. Eigler [this message]
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=20050502201635.GE15292@redhat.com \
--to=fche@redhat.com \
--cc=overseers@sourceware.org \
--cc=wcohen@redhat.com \
/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).