Package: dash Version: 0.5.12-12 Severity: normal A command started from an interactive shell may set the terminal to raw mode for its own use. It usually resets it to cooked mode before terminating, but one should not rely on that because the process may crash or be killed.
All shells seem to (re)set the terminal to cooked mode to handle that... except dash! Example: execute sh -c 'echo $$; stty raw; sleep 30; stty -raw' from various shells, and kill sh (the output pid). Only with dash, the terminal remains in raw mode. -- System Information: Debian Release: forky/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.7.12-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages dash depends on: ii debianutils 5.24 ii libc6 2.43-7 dash recommends no packages. dash suggests no packages. -- debconf information: dash/ineffectivediversion: -- Vincent Lefèvre <[email protected]> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / Pascaline project (LIP, ENS-Lyon)
