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

Bug#267941: marked as done (ssh: systematic restart of sshd at upgrade)



Your message dated Wed, 25 Aug 2004 12:46:06 +0100
with message-id <20040825114606.GA12292@riva.ucam.org>
and subject line Bug#267941: ssh: systematic restart of sshd at upgrade
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 Aug 2004 08:45:01 +0000
>From robind@esiee.fr Wed Aug 25 01:45:01 2004
Return-path: <robind@esiee.fr>
Received: from mail.esiee.fr [147.215.1.3] 
	by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1BztOv-00031u-00; Wed, 25 Aug 2004 01:45:01 -0700
Received: from localhost.esiee.fr (localhost.esiee.fr [127.0.0.1])
	by mail.esiee.fr (Postfix) with ESMTP id 15A9E3658C6
	for <submit@bugs.debian.org>; Wed, 25 Aug 2004 10:44:30 +0200 (CEST)
Received: from mail.esiee.fr (localhost.esiee.fr [127.0.0.1])
	by localhost.esiee.fr (VaMailArmor-2.0.1.16) id 16931-45E1E67B;
	Wed, 25 Aug 2004 10:44:30 +0200
Received: from esiee.fr (localhost.esiee.fr [127.0.0.1])
	by mail.esiee.fr (Postfix) with ESMTP id E4BC93658C2
	for <submit@bugs.debian.org>; Wed, 25 Aug 2004 10:44:29 +0200 (CEST)
X-Originating-IP: [82.230.88.157]
Date: Wed, 25 Aug 2004 10:44:29 +0300
User-Agent: IMHO/0.99 (Webmail for Roxen)
Subject: ssh: systematic restart of sshd at upgrade
MIME-Version: 1.0
To: submit@bugs.debian.org
From: David ROBIN <robind@esiee.fr>
Content-Type: text/plain; charset=iso-8859-1
Message-Id: <[🔎] 20040825084429.E4BC93658C2@mail.esiee.fr>
Content-Transfer-Encoding: quoted-printable
X-AntiVirus: checked by Vexira MailArmor (version: 2.0.1.16; VAE: 6.27.0.6; VDF: 6.27.0.29; host: mail.esiee.fr)
Delivered-To: submit@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
	autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 

Package: ssh =20
Version: 1:3.8.1p1-4 =20
Severity: minor =20
Tags: sarge =20
 =20
Dear Maintainers,=20
=20
When upgrading, .deb scripts do not check the current status of sshd :

sshd is systematicly restarted. After an version upgrade, sshd should=20
only be restarted if it was previously running !=20
The current behaviour is causing an important service to be opened=20
without my agreement.=20
=20
Thanks and Regards,=20
David.=20
=20
=20
apt log, with the unexpected last line being "restarting sshd" :=20
=20
debian: ~# apt-get install  ssh =20
Reading Package Lists... Done =20
Building Dependency Tree... Done =20
Suggested packages: =20
  ssh-askpass =20
The following packages will be upgraded: =20
  ssh =20
1 upgraded, 0 newly installed, 0 to remove and 493 not upgraded. =20
Need to get 684kB of archives. =20
After unpacking 24.6kB disk space will be freed. =20
Get:1 ftp://ftp.fr.debian.org testing/main ssh 1:3.8.1p1-4 [684kB] =20
Fetched 684kB in 6s (110kB/s) =20
Reading package fields... Done =20
Reading package status... Done =20
Retrieving bug reports... Done =20
Preconfiguring packages ... =20
(Reading database ... 87332 files and directories currently
installed.) =20
Preparing to replace ssh 1:3.8p1-3 (using .../ssh_1%=20
3a3.8.1p1-4_i386.deb) ... =20
Unpacking replacement ssh ... =20
Setting up ssh (3.8.1p1-4) ... =20
Restarting OpenBSD Secure Shell server: sshd. =20
=20

---------------------------------------
Received: (at 267941-done) by bugs.debian.org; 25 Aug 2004 11:46:13 +0000
>From cjwatson@flatline.org.uk Wed Aug 25 04:46:13 2004
Return-path: <cjwatson@flatline.org.uk>
Received: from chiark.greenend.org.uk [193.201.200.170] (mail)
	by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1BzwEH-0005ab-00; Wed, 25 Aug 2004 04:46:13 -0700
Received: from [192.168.124.112] (helo=riva.lab.dotat.at)
	by chiark.greenend.org.uk (Debian Exim 3.35 #1) with esmtp
	id 1BzwEF-0000g4-00; Wed, 25 Aug 2004 12:46:11 +0100
Received: from cjwatson by riva.lab.dotat.at with local (Exim 3.35 #1 (Debian))
	id 1BzwEA-0003R1-00; Wed, 25 Aug 2004 12:46:06 +0100
Date: Wed, 25 Aug 2004 12:46:06 +0100
From: Colin Watson <cjwatson@debian.org>
To: 267941-done@bugs.debian.org
Cc: control@bugs.debian.org
Subject: Re: Bug#267941: ssh: systematic restart of sshd at upgrade
Message-ID: <20040825114606.GA12292@riva.ucam.org>
References: <[🔎] 20040825084429.E4BC93658C2@mail.esiee.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[🔎] 20040825084429.E4BC93658C2@mail.esiee.fr>
User-Agent: Mutt/1.3.28i
Delivered-To: 267941-done@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER,
	VALID_BTS_CONTROL autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 
X-CrossAssassin-Score: 2

tags 267941 - sarge
thanks

On Wed, Aug 25, 2004 at 10:44:29AM +0300, David ROBIN wrote:
> Package: ssh  
> Version: 1:3.8.1p1-4  
> Severity: minor  
> Tags: sarge  
>   
> Dear Maintainers, 
>  
> When upgrading, .deb scripts do not check the current status of sshd :
> 
> sshd is systematicly restarted. After an version upgrade, sshd should 
> only be restarted if it was previously running ! 
> The current behaviour is causing an important service to be opened 
> without my agreement. 

For now, the correct way for you to configure your system this way is
'dpkg-reconfigure ssh', and answer no to the question about whether to
run sshd. This is fixed in the version of openssh in the experimental
distribution by allowing you to remove the server package altogether.

Cheers,

-- 
Colin Watson                                  [cjwatson@flatline.org.uk]



Reply to: