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

Bug#221531: marked as done (ssh: uses high priority debconf warning)

Your message dated Wed, 22 May 2013 11:04:13 +0000
with message-id <E1Uf6q5-000451-CS@franck.debian.org>
and subject line Bug#221531: fixed in openssh 1:6.2p2-2
has caused the Debian Bug report #221531,
regarding ssh: uses high priority debconf warning
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
221531: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=221531
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: ssh
Version: 1:3.6.1p2-9
Severity: important

ssh uses a high priority debconf warning to talk about PrivSep instead
of using NEWS.Debian.

Debconf warnings (notes) should not be used for these types of issues.

-- System Information:
Debian Release: testing/unstable
Architecture: powerpc
Kernel: Linux virgo 2.4.22-powerpc #1 Sat Sep 27 04:08:08 CEST 2003 ppc
Locale: LANG=C, LC_CTYPE=C

Versions of packages ssh depends on:
ii  adduser                     3.51         Add and remove users and groups
ii  debconf                     1.3.20       Debian configuration management sy
ii  libc6                       2.3.2.ds1-10 GNU C Library: Shared libraries an
ii  libpam-modules              0.76-14      Pluggable Authentication Modules f
ii  libpam0g                    0.76-14      Pluggable Authentication Modules l
ii  libssl0.9.7                 0.9.7c-5     SSL shared libraries
ii  libwrap0                    7.6-ipv6.1-3 Wietse Venema's TCP wrappers libra
ii  zlib1g                      1:1.1.4-16   compression library - runtime

-- debconf information:
* ssh/privsep_tell: 
  ssh/insecure_rshd: 
  ssh/privsep_ask: true
  ssh/user_environment_tell: 
  ssh/ssh2_keys_merged: 
* ssh/forward_warning: 
  ssh/insecure_telnetd: 
  ssh/new_config: true
* ssh/use_old_init_script: true
  ssh/protocol2_only: true
  ssh/encrypted_host_key_but_no_keygen: 
  ssh/run_sshd: true
  ssh/SUID_client: true

--- End Message ---
--- Begin Message --- 
Source: openssh
Source-Version: 1:6.2p2-2

We believe that the bug you reported is fixed in the latest version of
openssh, which is due to be installed in the Debian FTP archive.

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 221531@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Colin Watson <cjwatson@debian.org> (supplier of updated openssh 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 ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Wed, 22 May 2013 09:07:42 +0100
Source: openssh
Binary: openssh-client openssh-server ssh ssh-krb5 ssh-askpass-gnome openssh-client-udeb openssh-server-udeb
Architecture: source i386 all
Version: 1:6.2p2-2
Distribution: unstable
Urgency: low
Maintainer: Debian OpenSSH Maintainers <debian-ssh@lists.debian.org>
Changed-By: Colin Watson <cjwatson@debian.org>
Description: 
 openssh-client - secure shell (SSH) client, for secure access to remote machines
 openssh-client-udeb - secure shell client for the Debian installer (udeb)
 openssh-server - secure shell (SSH) server, for secure access from remote machines
 openssh-server-udeb - secure shell server for the Debian installer (udeb)
 ssh        - secure shell client and server (metapackage)
 ssh-askpass-gnome - interactive X program to prompt users for a passphrase for ssh-ad
 ssh-krb5   - secure shell client and server (transitional package)
Closes: 214182 221531 677440 679458
Changes: 
 openssh (1:6.2p2-2) unstable; urgency=low
 .
   * Change start condition of Upstart job to be just the standard "runlevel
     [2345]", rather than "filesystem or runlevel [2345]"; the latter makes
     it unreasonably difficult to ensure that urandom starts before ssh, and
     is not really necessary since one of static-network-up and failsafe-boot
     is guaranteed to happen and will trigger entry to the default runlevel,
     and we don't care about ssh starting before the network (LP: #1098299).
   * Drop conffile handling for direct upgrades from pre-split ssh package;
     this was originally added in 1:4.3p2-7 / 1:4.3p2-8, and contained a
     truly ghastly hack around a misbehaviour in sarge's dpkg.  Since this is
     now four Debian releases ago, we can afford to drop this and simplify
     the packaging.
   * Remove ssh/use_old_init_script, which was a workaround for a very old
     bug in /etc/init.d/ssh.  If anyone has ignored this for >10 years then
     they aren't going to be convinced now (closes: #214182).
   * Remove support for upgrading directly from ssh-nonfree.
   * Remove lots of maintainer script support for direct upgrades from
     pre-etch (three releases before current stable).
   * Add #DEBHELPER# tokens to openssh-client.postinst and
     openssh-server.postinst.
   * Replace old manual conffile handling code with dpkg-maintscript-helper,
     via dh_installdeb.
   * Switch to new unified layout for Upstart jobs as documented in
     https://wiki.ubuntu.com/UpstartCompatibleInitScripts: the init script
     checks for a running Upstart, and we now let dh_installinit handle most
     of the heavy lifting in maintainer scripts.  Ubuntu users should be
     essentially unaffected except that sshd may no longer start
     automatically in chroots if the running Upstart predates 0.9.0; but the
     main goal is simply not to break when openssh-server is installed in a
     chroot.
   * Remove the check for vulnerable host keys; this was first added five
     years ago, and everyone should have upgraded through a version that
     applied these checks by now.  The ssh-vulnkey tool and the blacklisting
     support in sshd are still here, at least for the moment.
   * This removes the last of our uses of debconf (closes: #221531).
   * Use the pam_loginuid session module (thanks, Laurent Bigonville; closes:
     #677440, LP: #1067779).
   * Bracket our session stack with calls to pam_selinux close/open (thanks,
     Laurent Bigonville; closes: #679458).
   * Fix dh_builddeb invocation so that we really use xz compression for
     binary packages, as intended since 1:6.1p1-2.
Checksums-Sha1: 
 7c5a0438d4e1be946eb46307b6bf792c79f9c1dd 2571 openssh_6.2p2-2.dsc
 fec44d5254698fe2a1c34e1999b6f57b1feac001 169657 openssh_6.2p2-2.debian.tar.gz
 362e699296b4d050b3e2f02a317d29e8ee7c6a27 590244 openssh-client_6.2p2-2_i386.deb
 a3aef3510121e6f723e3c9797aaa7ea2c4358aac 260856 openssh-server_6.2p2-2_i386.deb
 a2f2b57564fdcfd982a9c16b012ddf55e4efc77e 1058 ssh_6.2p2-2_all.deb
 cf3ce89a04078609e0105a5e959688df37dcc33c 103058 ssh-krb5_6.2p2-2_all.deb
 9fe77d7b39e2efd36cad91039f71104305c515ac 110836 ssh-askpass-gnome_6.2p2-2_i386.deb
 bbd05e119ac0e343cb3c9b7e3c2e1812de5c01e7 183406 openssh-client-udeb_6.2p2-2_i386.udeb
 f5e9ba5521c2a8120869a21e8659d38cce65bd06 208380 openssh-server-udeb_6.2p2-2_i386.udeb
Checksums-Sha256: 
 253daefabf95e551a205838b90eccf385f644bc7a8758acbc91bd910485e3353 2571 openssh_6.2p2-2.dsc
 2906d93ab29357391e26c197cf3d3d234b601c198c8971219de1c15e168e89e1 169657 openssh_6.2p2-2.debian.tar.gz
 a16cff3959a4e0214dd0bfeb39d253372029bb9009f1d467f3a56a22b2781847 590244 openssh-client_6.2p2-2_i386.deb
 5fec4924ef505c92a1feb4600e1864cb661e063de9b88cf2bfd77988aae28d32 260856 openssh-server_6.2p2-2_i386.deb
 29a9d405cd9105f8fb37ca59f81bd520b7b9916e055e29566f7cdd95e744dc7f 1058 ssh_6.2p2-2_all.deb
 5813efcf86cb57b1df1251dcc55d5414c0fd0abae006419bb600557aaafbf899 103058 ssh-krb5_6.2p2-2_all.deb
 05249f022978d30c3443e85399efa49246854b32ea2e551f75a59d821c206ea2 110836 ssh-askpass-gnome_6.2p2-2_i386.deb
 08d4a6ee01c8b4b2a10426b1007cb4b7a324d6a9f9828a49a28663ac3843abe6 183406 openssh-client-udeb_6.2p2-2_i386.udeb
 68f6656ff1af721a7b590bf662018606f23d8f62e751412a9f8a374c19cc7735 208380 openssh-server-udeb_6.2p2-2_i386.udeb
Files: 
 80045b65df897c3504ab6866b17b49d8 2571 net standard openssh_6.2p2-2.dsc
 03caf980980633ac5a1cd9186e36be34 169657 net standard openssh_6.2p2-2.debian.tar.gz
 b3ace7d35794415e0d724d79423ba4fe 590244 net standard openssh-client_6.2p2-2_i386.deb
 951b3db4f5e657f938ed6bd080bcf605 260856 net optional openssh-server_6.2p2-2_i386.deb
 56a6d19338411c6302c3476465629912 1058 net extra ssh_6.2p2-2_all.deb
 722619c08ec7bb1a3ece3e5a36a22986 103058 oldlibs extra ssh-krb5_6.2p2-2_all.deb
 5c82ce70d64e312cb5cff4fd56044df6 110836 gnome optional ssh-askpass-gnome_6.2p2-2_i386.deb
 64cfcb59e1d7767d900ed8066d64331a 183406 debian-installer optional openssh-client-udeb_6.2p2-2_i386.udeb
 9814b4807bd05ccdbf52958616bcda8a 208380 debian-installer optional openssh-server-udeb_6.2p2-2_i386.udeb
Package-Type: udeb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Colin Watson <cjwatson@debian.org> -- Debian developer

iQIVAwUBUZyh0Dk1h9l9hlALAQhcvQ//ZsHdtmPBIPoZZv+wsBz4ETnQUMGkeNGa
paQ5/KFPZhtyzxkCIoXZdXM9dzcXSg11Jtb6QjMlsxOv0DINQjAnAYeM+wcvubEi
+ecaYGnbhpzxl9fX5eOF8PUXkWgCaVIXBtpKSDen0nRYsT1VwKDeeFg5e2EdA434
HzvQgSC2+oIdc5fEUNSf+mLUO+hCmrVniZIp5DfQ7o6TOJ/WWWimXeVSKQwd+V5x
yLrFrC8b8fcjXSCBsA9RLDxUhJQLU5Gp1/xhS//scadpAGFNKOQp6R39kMJUa4Kj
cu4dKKsuHTjkXXZv/kPZmGgHpxOzaTVUG9tfdzMd1Emj3SDOzwC00RfposAF5m9V
Z8TM9iSKoRX5hJZFmM7pxobnzjJuAubG1MiXjrZu2r6IsaLvABoQ8g2TOtDmZSMw
d6rETccHsuzNDcF3p2Lw370WVffhtKP7kmbWG2Shor2mndSnK0nwTQXQsL/aRg1W
q6GTA2IeQrcODAu6JjG3NhN0c6LZZgx+P2gnaSrLWlkg/N4D+LtWHGojqlvNwVwk
1CCF8CDI8XQltymOzjmKBCZr4CFrFYi1twbg4qSlo1kfBYdCBVT2WAG5MbF3NX16
WDqg9nUNYnPZdvZ8giRxGmoTCuhI93Cyw5tVuwB9pMahsnRKWmkTSJWoh/vkBLyF
Fe05OLnMs8I=
=cRF9
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: