From: Mark Geisert <mark@maxrnd.com>
To: overseers@sourceware.org
Subject: Request to update shell access key because I can't
Date: Tue, 10 Nov 2015 16:47:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.63.1511092351510.53805@m0.truegem.net> (raw)
Hi folks,
I've been unable to use sourceware shell access with the key I provided on the
sourceware.org/cgi-bin/pdw/ps_form.cgi form. Any ssh connection attempt to
mgeisert@sourceware.org would ask me for passphrase, but that key didn't have a
passphrase. Just pressing enter at the passphrase prompt would result in
connection denied.
I've generated a new key with a passphrase but I'm unable to set it on
sourceware.org due to the catch-22 of original key not providing access.
The original access request was for write access to the cygwin-apps project,
and was approved by corinna-cygwin@cygwin.com. Below is an ssh-keygen display
of the new key I'd like to have installed.
I don't know if it matters, but I had requested "mark" for Preferred Login on
the original request but that had to be modified to "mgeisert" because of a
previously existing "mark" account.
Thanks very much,
Mark Geisert
ssh-keygen -e -f .ssh/id_dsa.pub
---- BEGIN SSH2 PUBLIC KEY ----
Comment: "1024-bit DSA, converted by Mark@zotac from OpenSSH"
AAAAB3NzaC1kc3MAAACBAPqsi50rpgqK96tXNgBYvenDeC/cd2uNOlWd6Lnir7UkrouasK
cvzTjmonCqcjdNNND8ckSWr0mx2Vr1tlLAFziqRQN6WPzOISBsqbazB8LQ1OMfzjN2QNQN
0I2cQyoxkQGaRJZwucxYHTIRHIK7Os6k9Klwxh76FGNBUtzqrhfPAAAAFQDoP+1qKyKwV9
YVvI/uh6cukNjipQAAAIBnxrnRAyqBaZ34nxTiX14ulsROj/NfVNh99qI3z/dyWwseCW5Q
9h9IY8NhrXf6NuDoIuJ0W1S9LLa8qT/vWuHTCfpBkWfN/YZXM7Rd5rYqQTR0lWVIj7JAc6
A2jQTvz4McuECEBEVKF1GvNRxw/Gopi1XUzo8eZ3oH/tpHeIoZyQAAAIEAl7kkPDTSvBnN
YrB7gPoS5GHwKGOUx2/6t9JTs7AKjU/BV7jFrCm98bXFahYNvWMmL5sVvkHizC9jLktwUz
A4kxNifJVIO1PunwzAontScYkZTjJe67NBwmoqGxNalI90U8vk7i0RwjB60a7HM87qBLAq
3xBRP1hhseI+hk+EDzM=
---- END SSH2 PUBLIC KEY ----
next reply other threads:[~2015-11-10 7:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 16:47 Mark Geisert [this message]
2015-11-17 16:13 ` 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=Pine.BSF.4.63.1511092351510.53805@m0.truegem.net \
--to=mark@maxrnd.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).