Package: mksh
Version: 46-2
Severity: normal
Logging with a shell set to mksh in /etc/passwd leads to weird behaviour:
hitting ^C kills the shell, and the session. This happens when logging on
the console, within an xterm, or remotely via ssh.
Workaround: running:
exec mksh
as the first command then leads to ^C behaving normally for the remaining
of the session.
This bug is deemed rather important because unepected killing of the shell
process can have adverse consequences, especially when running commands as root.
Note that this weird ^C behaviour does not affect children of mksh: running
"bc" as the first command and then hitting ^C leads to "bc" properly displaying:
(interrupt) use quit to exit.
But then hitting ^D to exit "bc" and ^C again kills the shell!
^C is properly configured to send "intr", as verified via "stty -a".
-- System Information:
Debian Release: 7.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR, LC_CTYPE=fr_FR (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Versions of packages mksh depends on:
ii libc6 2.17-7
ii libgcc1 1:4.7.2-5
mksh recommends no packages.
Versions of packages mksh suggests:
pn ed <none>
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
