9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Adrian Tritschler <ajft@ajft.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Plan 9 hg with private repositories
Date: Thu, 13 Aug 2009 20:11:41 +1000	[thread overview]
Message-ID: <166806220908130311i40d8404bk1ba70222a53e5731@mail.gmail.com> (raw)
In-Reply-To: <4ecada1e0908130213u4ba7b10p1a2d85d803294e25@mail.gmail.com>

2009/8/13 Bela Valek <bvalek2@gmail.com>:
>>
>> Presumably this is because ssh is sshv1
>> but bitbucket requires sshv2.
>>
>> Russ
>>
>
> Correct me if I am wrong, but an sshv2 server is also providing sshv1
> too. Maybe when the Plan 9 ssh client is facing sshv2, instead of
> shutting down with an error, it should try sshv1, or wait until its
> offered, i am unsure about the mechanism here. Just an idea, I am
> really not an expert here.

OpenSSH can support v1 and v2, whether it is configured to is a local option.

man sshd_config

  :
 Protocol
             Specifies the protocol versions sshd(8) supports.  The
possible values are ‘1’ and ‘2’.   Multiple versions must be
             comma-separated.  The default is “2,1”.  Note that the
order of the protocol list does not indicate preference,
             because the client selects among multiple protocol
versions offered by the server.  Specifying “2,1” is identical
             to “1,2”.

  :

The /etc/ssh/sshd_config supplied by default with many (most?) linux
distributions seems to be configured to only allow v2.  If you're the
administrator or on good terms with the admin. you may be able to
reconfigure your SSH to allow v1 connections, otherwise get to work on
the p9 ssh v2 port.

> Greetings: Béla

-- 
Adrian



  parent reply	other threads:[~2009-08-13 10:11 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-11 16:37 John Floren
2009-08-11 17:52 ` Russ Cox
2009-08-11 18:03   ` John Floren
2009-08-11 18:21   ` Jeff Sickel
2009-08-11 21:13     ` John Floren
2009-08-13  9:13   ` Bela Valek
2009-08-13  9:47     ` Ethan Grammatikidis
2009-08-13 14:53       ` David Leimbach
2009-08-13 15:13         ` Devon H. O'Dell
2009-08-13 15:31           ` Russ Cox
2009-08-13 17:45           ` Daniel Lyons
2009-08-13 18:00             ` erik quanstrom
2009-08-13 10:11     ` Adrian Tritschler [this message]
2009-08-15 12:38       ` Steve Simon
2009-08-11 18:19 ` John Floren
2010-05-21  5:08 ` ron minnich
2010-05-21  5:15   ` erik quanstrom
2010-05-21  6:10   ` Federico G. Benavento
2010-05-21 14:31     ` ron minnich
2010-05-21 12:33   ` John Floren

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=166806220908130311i40d8404bk1ba70222a53e5731@mail.gmail.com \
    --to=ajft@ajft.org \
    --cc=9fans@9fans.net \
    /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 NNTP newsgroup(s).