Path: csiph.com!xmission!news.snarked.org!news.linkpendium.com!news.linkpendium.com!panix!usenet.stanford.edu!not-for-mail
From: Lars Schneider <larsxschneider@gmail.com>
Newsgroups: gnu.bash.bug
Subject: Re: exec/read -s bug?
Date: Sun, 19 Aug 2018 20:45:36 +0200
Lines: 46
Approved: bug-bash@gnu.org
Message-ID: <mailman.5297.1534704344.1292.bug-bash@gnu.org>
References: <70D019FA-3393-404C-B689-20E499BC66B9@gmail.com>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
To: bug-bash@gnu.org
Envelope-to: bug-bash@gnu.org
In-Reply-To: <70D019FA-3393-404C-B689-20E499BC66B9@gmail.com>
Precedence: list
Xref: csiph.com gnu.bash.bug:14509


> On Aug 19, 2018, at 6:33 PM, Lars Schneider <larsxschneider@gmail.com> =
wrote:
>=20
> Hi,
>=20
> consider this script:
>=20
> 	#!/bin/bash
> 	[ "`whoami`" =3D "root" ] || {
> 	  exec sudo -u root "$0" "$@"
> 	}
> 	read -s -p "enter stuff: " stuff
>=20
> If I run the script as normal user (not root!) and I abort the "read =
-s -p"
> call with "ctrl-c", then my shell is still in silent mode.
>=20
> I can consitently replicate that behavior on Ubuntu 14.04.5 LTS =
(Trusty)=20
> and BASH 4.3.11(1)-release (x86_64-pc-linux-gnu) as well as BASH =
4.3.30.
>=20
> I also installed BASH 4.4.18 from source and I can replicate the =
issue.

I did a mistake: The problem _was_ fixed with BASH 4.4.18.
Further testing revealed that it is fixed with 4.4. too but not in =
Bash-4.3 patch 46.

I think the following item in the release notes corresponds to the =
problem:

 oo. Fixed a bug that caused bash to not clean up readline's state, =
including
     the terminal settings, if it received a fatal signal while in a =
readline()
     call (including `read -e' and `read -s').

Does anyone see a workaround to set the readline state properly
for older BASH versions?

Thanks,
Lars