Your message dated Sun, 16 Dec 2001 20:53:20 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#51993: fixed in ssh2 2.0.13-7
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; 6 Dec 1999 01:21:34 +0000
Received: (qmail 28307 invoked from network); 6 Dec 1999 01:21:33 -0000
Received: from rhme114.res.utk.edu (HELO rhme114) (128.169.156.214)
  by master.debian.org with SMTP; 6 Dec 1999 01:21:33 -0000
Received: from alphenglor by rhme114 with local (Exim 3.03 #1 (Debian))
        id 11umqK-0005hc-00; Sun, 05 Dec 1999 20:21:32 -0500
From: Rob Mahurin <[EMAIL PROTECTED]>
Subject: ssh2: fails to configure -- does not stop daemon before restarting
To: [EMAIL PROTECTED]
X-Mailer: bug 3.2.7
Message-Id: <[EMAIL PROTECTED]>
Date: Sun, 05 Dec 1999 20:21:32 -0500

Package: ssh2
Version: 2.0.13-4
Severity: normal

running apt-get upgrade included thisL

Starting Secure Shell server v2: FATAL: Creating listener failed: port 22
probably already in use!
dpkg: error processing ssh2 (--configure):
 subprocess post-installation script returned error exit status 255
Errors were encountered while processing:
 ssh2
E: Sub-process returned an error code (1)

fixed it like this:

peon:~# /etc/init.d/ssh2 stop
Stopping Secure Shell server v2: sshd2.
peon:~# fuser -k -n tcp 22
peon:~# dpkg --configure ssh2
Setting up ssh2 (2.0.13-4) ...
You already have a host key in /etc/ssh2/hostkey.

You should read the documentation and then configure /etc/ssh2/ssh2_config
and /etc/ssh2/sshd2_config to your sites needs and preferences.
Do you want to use the SSH 2 applications (say n to keep SSH 1 in use)?
[y/N]? y
Switching to the SSH 2 applications
Starting Secure Shell server v2: sshd2.

peon:~# 

Thanks.

Rob

-- System Information
Debian Release: potato
Kernel Version: Linux peon 2.2.13 #1 SMP Sat Nov 13 19:43:37 EST 1999 i586 
unknown

Versions of the packages ssh2 depends on:
ii  libc6           2.1.2-10       GNU C Library: Shared libraries and timezone
ii  libncurses4     4.2-3.4        Shared libraries for terminal handling
ii  zlib1g          1.1.3-5        compression library - runtime
        ^^^ (Provides virtual package libz1)

--- Begin /etc/ssh2/sshd2_config (modified conffile)
*:
        Port                            22
        ListenAddress                   0.0.0.0
        Ciphers                         AnyStd
        IdentityFile                    identification
        AuthorizationFile               authorization
        HostKeyFile                     hostkey
        PublicHostKeyFile               hostkey.pub
        RandomSeedFile                  random_seed
        ForwardAgent                    yes
        ForwardX11                      yes
        PasswordGuesses                 3
        MaxConnections                  0 
        PermitRootLogin                 yes
        AllowedAuthentications          publickey,password
        ForcePTTYAllocation             no
        VerboseMode                     no
        PrintMotd                       yes
        CheckMail                       yes
        UserConfigDirectory             "%D/.ssh2"
        SyslogFacility                  AUTH
        Ssh1Compatibility               no
        RequireReverseMapping           yes
        UserKnownHosts                  yes
        subsystem-sftp                  sftp-server

--- End /etc/ssh2/sshd2_config
---------------------------------------
Received: (at 51993-close) by bugs.debian.org; 16 Dec 2001 20:08:46 +0000
>From [EMAIL PROTECTED] Sun Dec 16 14:08:46 2001
Return-path: <[EMAIL PROTECTED]>
Received: from pandora.debian.org [132.229.137.249] (mail)
        by master.debian.org with esmtp (Exim 3.12 1 (Debian))
        id 16FhaY-0000II-00; Sun, 16 Dec 2001 14:08:46 -0600
Received: from troup by pandora.debian.org with local (Exim 3.12 1 (Debian))
        id 16FhLc-0001Gq-00; Sun, 16 Dec 2001 20:53:20 +0100
From: Colin Watson <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.67 $
Subject: Bug#51993: fixed in ssh2 2.0.13-7
Message-Id: <[EMAIL PROTECTED]>
Sender: James Troup <[EMAIL PROTECTED]>
Date: Sun, 16 Dec 2001 20:53:20 +0100
Delivered-To: [EMAIL PROTECTED]

We believe that the bug you reported is fixed in the latest version of
ssh2, which has been installed in the Debian FTP archive:

ssh2_2.0.13-7.diff.gz
  to pool/non-US/non-free/s/ssh2/ssh2_2.0.13-7.diff.gz
ssh2_2.0.13-7.dsc
  to pool/non-US/non-free/s/ssh2/ssh2_2.0.13-7.dsc
ssh2_2.0.13-7_i386.deb
  to pool/non-US/non-free/s/ssh2/ssh2_2.0.13-7_i386.deb
ssh2_2.0.13-7_sparc.deb
  to pool/non-US/non-free/s/ssh2/ssh2_2.0.13-7_sparc.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Colin Watson <[EMAIL PROTECTED]> (supplier of updated ssh2 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Sat, 15 Dec 2001 12:43:25 +0000
Source: ssh2
Binary: ssh2
Architecture: source i386 sparc
Version: 2.0.13-7
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group <[EMAIL PROTECTED]>
Changed-By: Colin Watson <[EMAIL PROTECTED]>
Description: 
 ssh2       - a secure replacement for rlogin, rsh, and rcp
Closes: 38895 38921 51993 58855 60912 75008
Changes: 
 ssh2 (2.0.13-7) unstable; urgency=low
 .
   * QA upload.
   * debian/rules: Configure Sshd1Path correctly (closes: #58855).
   * debian/init: Find port from /etc/ssh2/sshd2_config (closes: #60912).
   * apps/ssh/sshunixuserfiles.c: Treat absolute paths given to -i as
     absolute rather than relative to $HOME/.ssh2 (closes: #75008).
   * debian/postinst: Restart ssh2 rather than starting it, in case it was
     configured differently when the prerm tried to stop it (closes: #51993).
   * debian/postinst: Use alternatives in order to co-operate better with
     ssh-nonfree (closes: #38895, #38921).
Files: 
 891e722c754bd2c8542d26765c4eb383 650 non-US/non-free optional ssh2_2.0.13-7.dsc
 95579867c3a4f90d839ebd4f18ca2cee 50270 non-US/non-free optional 
ssh2_2.0.13-7.diff.gz
 b0f319fc1250a103bbc05164341dca59 983530 non-US/non-free optional 
ssh2_2.0.13-7_i386.deb
 a229de90c1a8c718bd516a70a5d8ca23 1072558 non-US/non-free optional 
ssh2_2.0.13-7_sparc.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8G05T9t0zAhD6TNERAiMZAJ4smMsgDGUVcUEn4SVsbJ7J7J9kgQCcDcaZ
xxhQBqQ5y/xnx5xwGe8nDpY=
=nQw/
-----END PGP SIGNATURE-----

Reply via email to