Your message dated Sun, 15 Aug 2021 23:50:32 +0000
with message-id <[email protected]>
and subject line Bug#991960: fixed in putty 0.76-1
has caused the Debian Bug report #991960,
regarding /usr/bin/psusan: psusan example ends up with . on PATH due to #991959
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 [email protected]
immediately.)


-- 
991960: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991960
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: putty-tools
Version: 0.75-3
Severity: normal
File: /usr/bin/psusan

psusan(1) suggests this:

       And the setup script uml-psusan.sh might look like this:

       #!/bin/bash
       # Set up vital pseudo-filesystems
       mount -t proc none /proc
       mount -t devpts none /dev/pts
       # Redirect I/O to the serial port, but stderr to the console
       exec 0<>/dev/ttyS0 1>&0 2>/dev/console
       # Set the serial port into raw mode, to run a binary protocol
       stty raw -echo
       # Choose what shell you want to run inside psusan
       export SHELL=/bin/bash
       # And now run psusan over the serial port
       exec /home/simon/src/putty/misc/psusan

This sets SHELL.  It does not set PATH.  Due to #991959, the PATH
ends up set to
  /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
ie with cwd at the end.  This is quite undesirable.

I think it would be best to change the example to explicitly set PATH
to avoid this bug.  CCing upstream since even when bash is fixed in
Debian sid, the upstream manpage probably wants to have this
workaround indefinitely.

(I am using psusan from a .deb I built myself from the sid sources, so
the version number in this bug report ought really to refer to
src:putty but that seems more confusing than helpful.)

Thanks,
Ian.

-- System Information:
Debian Release: 10.10
  APT prefers stable-debug
  APT policy: (500, 'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 5.6.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages putty-tools depends on:
ii  libc6  2.28-10

putty-tools recommends no packages.

Versions of packages putty-tools suggests:
ii  putty-doc  0.75-3

-- no debconf information

--- End Message ---
--- Begin Message ---
Source: putty
Source-Version: 0.76-1
Done: Colin Watson <[email protected]>

We believe that the bug you reported is fixed in the latest version of
putty, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Colin Watson <[email protected]> (supplier of updated putty 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: SHA512

Format: 1.8
Date: Mon, 16 Aug 2021 00:29:11 +0100
Source: putty
Architecture: source
Version: 0.76-1
Distribution: unstable
Urgency: medium
Maintainer: Colin Watson <[email protected]>
Changed-By: Colin Watson <[email protected]>
Closes: 991960
Changes:
 putty (0.76-1) unstable; urgency=medium
 .
   * New upstream release.
   * Cherry-pick from upstream:
     - psusan manpage: add a PATH to the UML example (closes: #991960).
     - Bug workaround to delay sending our SSH greeting (see #991958).
Checksums-Sha1:
 ca92eab0b6c3c990d7882f705e5ec13474fa85f8 2422 putty_0.76-1.dsc
 de09f50aee330eb05ad0cb81b970d0cc8e5c9b25 2735687 putty_0.76.orig.tar.gz
 78ea6fd5bfd21663b4f7385ae1c501d403816785 659 putty_0.76.orig.tar.gz.asc
 a40cc807318bffc0bc2c82bd6fe2479999948d78 20704 putty_0.76-1.debian.tar.xz
Checksums-Sha256:
 a8147bf896238ba60f37ea9607f17b3950e94e3ee146a28f37f6c0cd25fdb350 2422 
putty_0.76-1.dsc
 547cd97a8daa87ef71037fab0773bceb54a8abccb2f825a49ef8eba5e045713f 2735687 
putty_0.76.orig.tar.gz
 54ac199bce49bbce7101442fa90731a98f6508cce7d473e409535d4cb2d86698 659 
putty_0.76.orig.tar.gz.asc
 dfb9aa8ffd4809ca0f6f019eaf9e5373525a26906fd1ae93d9527ec625533cf8 20704 
putty_0.76-1.debian.tar.xz
Files:
 b63e7d55217d595241d70323e58a4ebe 2422 net optional putty_0.76-1.dsc
 9d22f8c56c1eaa1c0af3098438f25908 2735687 net optional putty_0.76.orig.tar.gz
 28a0bf89835f5272897b0b3c4c6cb559 659 net optional putty_0.76.orig.tar.gz.asc
 305fc7282a5b74820330bb21f488be02 20704 net optional putty_0.76-1.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEErApP8SYRtvzPAcEROTWH2X2GUAsFAmEZo+EACgkQOTWH2X2G
UAv+NA//apCpVJWU/peOFzF0IK2NjCAobFW+6/nCt4mA2V1pG1J0ztdJJ0ImLfIC
RNHotG5ZpUw/jf3rehKpMdrpZYwG5JAROwmjZ2qIsCy8mZ4bGDH91V6ql8ej88Hm
1bJY9IwbsSL/UypFzSx2MpR5SwArDyDAy/msR1Foyn4IFNFDKUoR1SMUCiEDMsY1
/zYCMinQxQpjs4Iy7I4fS1I+5niOMgsFjI/98xuR3UrU4K40iSwB91G0Onqopq0G
RqnmWufAB7A5mHLblTTAyhsF5PXthEQyIMWUAFSdcwn8BceAZg3KQioBOrXuazbS
BhTqkBYHd4mh+BdF041RpSVqi34zusN9wzgRPUuG5CLG/6VeY0uzT/blSQSxvzDa
TuxHmaJpX+xXnKv4Wwl4zvvJUWyL12WOb7EqVESvSbgsvXcvRwEGRzWC3kzvWob+
riyMBdrhSKtNkmXTjiyqk6RkTGxLQmYSZrpHZn885reBEb/4XCWrOE7x1MIoDH1/
gbUhP7uLJUTchoJqiOuA1hQpLhEJTU+vdnjiN1s/JBhTIXR9XQI3/yn7yMDbTQI4
bgpGC0Cu4ksuPWsUO20irx8TB0vWb5nYhwMftbZ7yjQEg8XKlR0siov9tM9AogGq
J+acHL4xo8OB3twHMjDBjfk75mtdy2l8IhGN8wN3csMlD01INlA=
=3hxu
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to