From: "Frank Ch. Eigler" <fche@elastic.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: overseers@sourceware.org
Subject: Re: Git over SSH access problem
Date: Thu, 18 Jul 2019 13:05:00 -0000 [thread overview]
Message-ID: <20190718130531.GH3519528@elastic.org> (raw)
In-Reply-To: <837e8fy1rj.fsf@gnu.org>
Hi -
> Today I cannot access the sourceware Git repository for Binutils and
> GDB: Git says it cannot use my private SSH key. I have been using
> this key to access sourceware.org repositories for ages, last time
> this May.
# ssh-key-doctor eliz
[...]
FILENAME /home/eliz/.ssh/authorized_keys
FILEDATE 2005-12-08
RASH restricted shell, see https://www.sourceware.org/sourceware/accountinfo.html
RSA1 1024: already unsupported ssh1 key
You have no strong keys. If you still need access to sourceware/gcc,
consider generating new key-pair with % ssh-keygen -t rsa -b 4096
and if necessary, sending the .pub part to <overseers@sourceware.org>.
I'm surprised if it has worked for you so recently. Please generate
a new keypair as per the above instructions.
- FChE
next prev parent reply other threads:[~2019-07-18 13:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 12:18 Eli Zaretskii
2019-07-18 13:05 ` Frank Ch. Eigler [this message]
2019-07-18 14:08 ` Eli Zaretskii
2019-07-18 14:26 ` Frank Ch. Eigler
2019-07-18 14:40 ` Eli Zaretskii
2019-07-18 14:43 ` Frank Ch. Eigler
2019-07-18 14:46 ` Eli Zaretskii
2019-07-18 14:53 ` Frank Ch. Eigler
2019-07-18 14:57 ` Eli Zaretskii
2019-07-19 14:23 ` Martin Sebor
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=20190718130531.GH3519528@elastic.org \
--to=fche@elastic.org \
--cc=eliz@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).