From: Ian Lance Taylor <ian@airs.com>
To: Toon Moene <toon@moene.org>
Cc: Joseph Myers <joseph@codesourcery.com>, overseers@gcc.gnu.org
Subject: Re: New ssh key after upgrading Debian Testing last Monday :-(
Date: Sun, 27 Dec 2015 13:44:00 -0000 [thread overview]
Message-ID: <m337urlgni.fsf@pepe.airs.com> (raw)
In-Reply-To: <567C1919.2090708@moene.org> (Toon Moene's message of "Thu, 24 Dec 2015 17:11:05 +0100")
Toon Moene <toon@moene.org> writes:
> On 12/24/2015 04:55 PM, Ian Lance Taylor wrote:
>
>> Toon Moene <toon@moene.org> writes:
>
>>> On 12/24/2015 01:08 PM, Joseph Myers wrote:
>
>>>> Ed25519 public keys are only 32 bytes. See <http://ed25519.cr.yp.to/>. I
>>>> don't know whether sourceware has a recent enough OpenSSH version to
>>>> support Ed25519, however.
>>>
>>> I was surprised at the shortness of the key, too. However, it works
>>> between my laptop and my PC (both upgraded to Debian Testing as-of
>>> 20151221) *and* my workstation at work (which is Fedora 21) and my PC.
>>>
>>> So if it doesn't work with gcc.gnu.org, perhaps *that* system is too old :-)
>>
>> Ah, OK, sorry. Well, I installed it. See if it works.
>
> Read access works, write access gets me the following error message:
>
> toon@moene:~/compilers$ svn co svn+ssh://toon@gcc.gnu.org/svn/gcc/trunk
> svn: E170013: Unable to connect to a repository at URL
> svn+ssh://toon@gcc.gnu.org/svn/gcc/trunk'
> svn: E210002: To better debug SSH connection problems, remove the -q
> option from 'ssh' in the [tunnels] section of your Subversion
> configuration file.
> svn: E210002: Network connection closed unexpectedly
What do you see from
ssh -v -v -v toon@gcc.gnu.org alive
?
Ian
prev parent reply other threads:[~2015-12-24 20:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-24 13:07 Toon Moene
2015-12-24 15:55 ` Ian Lance Taylor
2015-12-24 16:11 ` Joseph Myers
2015-12-24 20:45 ` Toon Moene
2015-12-27 8:54 ` Ian Lance Taylor
2015-12-27 11:37 ` Toon Moene
2015-12-27 13:44 ` 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=m337urlgni.fsf@pepe.airs.com \
--to=ian@airs.com \
--cc=joseph@codesourcery.com \
--cc=overseers@gcc.gnu.org \
--cc=toon@moene.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).