Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: <Paul_Koning@Dell.com>
To: <pierre.muller@ics-cnrs.unistra.fr>
Cc: <gdb@sourceware.org>
Subject: Re: Question about SSH protocol for developper access
Date: Wed, 28 Oct 2015 15:35:00 -0000	[thread overview]
Message-ID: <3C2DAE58-8CAA-427E-9A21-76431A63D593@dell.com> (raw)
In-Reply-To: <001101d1116d$817b8b80$8472a280$@muller@ics-cnrs.unistra.fr>


> On Oct 28, 2015, at 6:43 AM, Pierre Muller <pierre.muller@ics-cnrs.unistra.fr> wrote:
> 
> 
>   I am not sure this is the correct mailing list for this question,
> but I was wondering if it would not be better to allow now also SSH version
> 2 keys
> for remote write access to Gnu repositories.
> 
>   The reason for me to ask is simply that protocol 1 is now disabled by
> default on Cygwin installation.
> This means that ssh-agent, which I normally use to avoid having to type my
> password
> each time I access git repository for instance, does not work for my
> SSH-version 1 key anymore.
> 
>   I suppose that this has to do with the fact that version 1 is less
> "secure" than version 2.
> what are the reasons why GNU still insists on only using version 1 keys?

I don't believe that it does.  I have an SSH 2 key registered with the GNU servers, not a V1 key.  Maybe all you need to do is submit your SSH V2 key.

A related question is whether the GNU servers should disable SSH V1 across the board.  It seems like a good idea to do so.

	paul


  reply	other threads:[~2015-10-28 15:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-28 10:43 Pierre Muller
2015-10-28 15:35 ` Paul_Koning [this message]
     [not found] <24370.3848952011$1446029041@news.gmane.org>
2015-10-28 10:54 ` Andreas Schwab
2015-10-28 11:39   ` Pierre Muller
2015-10-28 11:46     ` Andreas Schwab
2015-10-28 11:50     ` Andreas Schwab

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=3C2DAE58-8CAA-427E-9A21-76431A63D593@dell.com \
    --to=paul_koning@dell.com \
    --cc=gdb@sourceware.org \
    --cc=pierre.muller@ics-cnrs.unistra.fr \
    /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