Your message dated Sun, 29 Dec 2002 11:55:38 +0100
with message-id <[EMAIL PROTECTED]>
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; 1 Mar 2000 09:49:44 +0000
Received: (qmail 22111 invoked from network); 1 Mar 2000 09:49:44 -0000
Received: from minnie.eecs.umich.edu (141.213.4.33)
by master.debian.org with SMTP; 1 Mar 2000 09:49:44 -0000
Received: (from [EMAIL PROTECTED])
by minnie.eecs.umich.edu (8.9.3/8.9.3/Debian 8.9.3-6) id EAA03478;
Wed, 1 Mar 2000 04:49:33 -0500
Date: Wed, 1 Mar 2000 04:49:33 -0500
Message-Id: <[EMAIL PROTECTED]>
From: Steve Hsieh <[EMAIL PROTECTED]>
Subject: ssh2: Should be easy to share ssh-nonfree and ssh2 on the same port
To: [EMAIL PROTECTED]
X-Mailer: bug 3.2.10
Package: ssh2
Version: 2.0.13-5
Severity: wishlist
Hi Ed/ssh2 developer,
According to README.Debian, it says that "trying to divert ssh1's daemon and
handle all error conditions proved too difficult... If you want this
situation to improve, please patch ssh1 and make it easier to replace...etc"
It would seem, however, that the only thing that needs to be done is
not start ssh-nonfree on startup. That being the case, it should be
easy to have both ssh1 and ssh2 share the same port.
The only steps that are required for ssh2 to do this properly is
1. In the postinst, stop ssh-nonfree if it is running, and then
do a diversion of /etc/init.d/ssh-nonfree:
dpkg-divert --package ssh2 --add --rename --divert
/etc/init.d/ssh-nonfree.ssh-nonfree /etc/init.d/ssh-nonfree
In postrm, do the reverse in case user removes ssh2 but keeps ssh1...
2. ssh2 must provide a dummy /etc/init.d/ssh-nonfree that just does an exit 0
and a comment that the original file has been diverted
3. (obvious) ssh2 must be configured to call ssh1 on backup. Add the two
additional lines in /etc/ssh2/sshd2_config (and change the port back to 22):
Ssh1Compatibility yes
Sshd1Path "/usr/sbin/sshd1"
.
That should be all that's required. This setup works for me and no changes
need to be done to ssh...
If it's the case that Debian Policy forbids packages from diverting other
package's /etc/init.d/ files, then all we need to do is get the ssh-nonfree
maintainer to add one line to their init.d file:
test -x /usr/sbin/sshd2 && exit 0
or something similar
Assuming that sshd2 is setup to call ssh1 in compatibility mode, then again
everything should work.
How about it? I'd like to see this worked out before potato is released as
it would seem to be a minor issue, and I'm sure a lot of users would appreciate
having both on the same port. If i'm naive and there's some reason why
what I wrote above can't be done, then forgive me and tell me why...
Steve
-- System Information
Debian Release: 2.2
Kernel Version: Linux minnie.eecs.umich.edu 2.2.14 #1 SMP Fri Jan 21 23:36:42
EST 2000 i686 unknown
Versions of the packages ssh2 depends on:
ii libc6 2.1.3-5 GNU C Library: Shared libraries and Timezone
ii libncurses4 4.2-8 Shared libraries for terminal handling
ii xlib6g 3.3.6-3 shared libraries required by X clients
ii zlib1g 1.1.3-5 compression library - runtime
^^^ (Provides virtual package libz1)
--- Begin /etc/ssh2/ssh2_config (modified conffile)
*:
Port 22
Ciphers AnyStdCipher
IdentityFile identification
AuthorizationFile authorization
RandomSeedFile random_seed
VerboseMode no
#PasswordPrompt "[EMAIL PROTECTED]'s password: "
PasswordPrompt "%U's password: "
#LocalForward "110:pop3.ssh.fi:110"
#RemoteForward "3000:foobar:22"
Ssh1Compatibility yes
Ssh1Path "/usr/bin/ssh1"
Ssh1AgentCompatibility none
#Ssh1AgentCompatibility traditional
#Ssh1AgentCompatibility ssh2
#SshSignerPath ssh-signer2
NoDelay no
KeepAlive yes
#
--- End /etc/ssh2/ssh2_config
---------------------------------------
Received: (at 59336-done) by bugs.debian.org; 29 Dec 2002 10:55:39 +0000
>From [EMAIL PROTECTED] Sun Dec 29 04:55:39 2002
Return-path: <[EMAIL PROTECTED]>
Received: from smtpzilla2.xs4all.nl [194.109.127.138]
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 18Sb6Z-0002Mp-00; Sun, 29 Dec 2002 04:55:39 -0600
Received: from kalypso (ramstraat29.xs4all.nl [80.126.10.231])
by smtpzilla2.xs4all.nl (8.12.0/8.12.0) with ESMTP id gBTAtcZR082345
for <[EMAIL PROTECTED]>; Sun, 29 Dec 2002 11:55:38 +0100 (CET)
Received: from bas by kalypso with local (Exim 3.36 #1 (Debian))
id 18Sb6Y-0003m9-00
for <[EMAIL PROTECTED]>; Sun, 29 Dec 2002 11:55:38 +0100
From: Bas Zoetekouw <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Your ssh2 bug
Message-Id: <[EMAIL PROTECTED]>
Sender: Bas Zoetekouw <[EMAIL PROTECTED]>
Date: Sun, 29 Dec 2002 11:55:38 +0100
Delivered-To: [EMAIL PROTECTED]
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.
