public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@airs.com>
To: Mark Geisert <mark@maxrnd.com>
Cc: overseers@sourceware.org
Subject: Re: Request to update shell access key because I can't
Date: Tue, 17 Nov 2015 16:13:00 -0000	[thread overview]
Message-ID: <m31tbu2fyo.fsf@pepe.airs.com> (raw)
In-Reply-To: <Pine.BSF.4.63.1511092351510.53805@m0.truegem.net> (Mark Geisert's message of "Mon, 9 Nov 2015 23:52:47 -0800 (PST)")

Mark Geisert <mark@maxrnd.com> writes:

> 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,

I installed this new key.  Let us know if it doesn't work.

Ian

      reply	other threads:[~2015-11-13 13:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-10 16:47 Mark Geisert
2015-11-17 16:13 ` Ian Lance Taylor [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=m31tbu2fyo.fsf@pepe.airs.com \
    --to=ian@airs.com \
    --cc=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).