From: "H.J. Lu" <hjl.tools@gmail.com>
To: Tobias Burnus <burnus@net-b.de>
Cc: GCC Development <gcc@gcc.gnu.org>, overseers@sourceware.org
Subject: Re: How to update my SSH authorized_keys on gcc.gnu.org?
Date: Tue, 23 Feb 2010 17:29:00 -0000 [thread overview]
Message-ID: <6dc9ffc81002230929l6c61f804ife8deb09c4e0b7e0@mail.gmail.com> (raw)
In-Reply-To: <4B840FBF.7080706@net-b.de>
On Tue, Feb 23, 2010 at 9:26 AM, Tobias Burnus <burnus@net-b.de> wrote:
> Hi,
>
>> Is there a way to update my SSH authorized_keys on gcc.gnu.org? I
>> tried
>
> As written at http://sourceware.org/cgi-bin/pdw/ps_form.cgi
>
> ssh sourceware.org updatekey < ~/.ssh/id_dsa.pub
>
> should do the deed.
>
Does it work for anyone? I got
# ssh sourceware.org updatekey < ~/.ssh/id_dsa.pub
Permission denied (publickey,gssapi-with-mic).
--
H.J.
prev parent reply other threads:[~2010-02-23 17:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6dc9ffc81002230910s465d27b4pa3d4877b189a5326@mail.gmail.com>
[not found] ` <m3vddnyiit.fsf@hase.home>
2010-02-23 17:27 ` H.J. Lu
2010-02-23 17:35 ` Christopher Faylor
2010-02-23 17:51 ` H.J. Lu
[not found] ` <4B840FBF.7080706@net-b.de>
2010-02-23 17:29 ` H.J. Lu [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=6dc9ffc81002230929l6c61f804ife8deb09c4e0b7e0@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=burnus@net-b.de \
--cc=gcc@gcc.gnu.org \
--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).