[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#56299: marked as done (ssh2 to co-operate with ssh-nonfree)



Your message dated Sun, 29 Dec 2002 11:55:34 +0100
with message-id <E18Sb6U-0003lu-00@kalypso>
and subject line Your ssh2 bug
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 25 Jan 2000 01:53:38 +0000
Received: (qmail 14499 invoked from network); 25 Jan 2000 01:53:36 -0000
Received: from dynax.anu.edu.au (mail@150.203.126.171)
  by master.debian.org with SMTP; 25 Jan 2000 01:53:36 -0000
Received: from chanop by dynax.anu.edu.au with local (Exim 3.12 #1 (Debian))
	id 12CvAf-0003id-00
	for <submit@bugs.debian.org>; Tue, 25 Jan 2000 12:53:29 +1100
Date: Tue, 25 Jan 2000 12:53:29 +1100
From: Chanop Silpa-Anan <chanop@syseng.anu.edu.au>
To: submit@bugs.debian.org
Subject: ssh2 to co-operate with ssh-nonfree
Message-ID: <20000125125329.A14253@dynax.anu.edu.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Mutt/1.0i
Organization: Linux
X-URL: http://kenji.anu.edu.au/~chanop/
X-OS: Linux 2.2.14 i686  12:43pm  up 2 days, 16:48,  4 users,  load average: 0.16, 0.04, 0.01
Sender: Chanop Silpa-Anan <chanop@dynax.anu.edu.au>

Package: ssh2
Version: 2.0.13-4
Severity: important

I use both ssh2 andd ssh-nonfree on several machines. I change sshd2_config so
that it run on regular ssh port 22 and disable sshd from starting.

When I use ssh to machine running ssd2. I'll not be able to get into machine
unless I symlink /etc/ssh -> ssh-nonfree. This happen since we have both
and ssh-nonfree in the distributions.

IMO, ssh2 should stay on port 22 since it could spawn ssh1 when ssh1 client
try to connect if ssh1 is installed, so ssh2 post install script should do this  
or ask to do this.

I'm using Debian potato, kernel 2.2.14, libc6 2.1.2-11
ssh-nonfree version: 1.2.27-4




-- 
,-----------------------------------------------------------------------------.
| Chanop Silpa-Anan                       <chanop@faceng.anu.edu.au>          |
| Australian National University                                              |
| got sparetime ?                                                             |
| http://kenji.anu.edu.au/                                                    |
|           Debian GNU/Linux           ICQ uin 11366301                       |
`-----------------------------------------------------------------------------'
---------------------------------------
Received: (at 56299-done) by bugs.debian.org; 29 Dec 2002 10:55:36 +0000
>From bas@caradhras.net Sun Dec 29 04:55:36 2002
Return-path: <bas@caradhras.net>
Received: from smtpzilla2.xs4all.nl [194.109.127.138] 
	by master.debian.org with esmtp (Exim 3.12 1 (Debian))
	id 18Sb6V-0002M8-00; Sun, 29 Dec 2002 04:55:35 -0600
Received: from kalypso (ramstraat29.xs4all.nl [80.126.10.231])
	by smtpzilla2.xs4all.nl (8.12.0/8.12.0) with ESMTP id gBTAtYZR082330
	for <56299-done@bugs.debian.org>; Sun, 29 Dec 2002 11:55:34 +0100 (CET)
Received: from bas by kalypso with local (Exim 3.36 #1 (Debian))
	id 18Sb6U-0003lu-00
	for <56299-done@bugs.debian.org>; Sun, 29 Dec 2002 11:55:34 +0100
From: Bas Zoetekouw <bas@debian.org>
To: 56299-done@bugs.debian.org
Subject: Your ssh2 bug
Message-Id: <E18Sb6U-0003lu-00@kalypso>
Sender: Bas Zoetekouw <bas@caradhras.net>
Date: Sun, 29 Dec 2002 11:55:34 +0100
Delivered-To: 56299-done@bugs.debian.org
X-Spam-Status: No, hits=-0.7 required=5.0
	tests=SPAM_PHRASE_02_03
	version=2.41
X-Spam-Level: 

Hi!

Ssh2 was removed from the Debian archive this morning.  It's
replacement, openssh (ssh package), does not seem to be affected
by this bug; therefore, I'm closing it.

Kind regards,
Bas Zoetekouw.



Reply to: