Path: csiph.com!goblin2!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail
From: Lars Schneider <larsxschneider@gmail.com>
Newsgroups: gnu.bash.bug
Subject: exec/read -s bug?
Date: Sun, 19 Aug 2018 18:33:49 +0200
Lines: 43
Approved: bug-bash@gnu.org
Message-ID: <mailman.5295.1534699754.1292.bug-bash@gnu.org>
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
Precedence: list
Xref: csiph.com gnu.bash.bug:14508

Hi,

consider this script:

	#!/bin/bash
	[ "`whoami`" =3D "root" ] || {
	  exec sudo -u root "$0" "$@"
	}
	read -s -p "enter stuff: " stuff

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.

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.

I also installed BASH 4.4.18 from source and I can replicate the issue.

Can you replicate the issue?=20
Is this a known issue?
Do you consider it a bug?=20
How would you investigate that further?=20
Do you see a workaround for the problem?

I briefly looked into the `builtins/exec.def` and `builtins/read.def` =
code
and my impression is that `exec` might mess with the `ttsave/ttyrestore`=20=

stack.

Thanks,
Lars


PS: Before I reached out on the bug bash mailing list I asked for help =
here:
=
https://unix.stackexchange.com/questions/463253/why-would-read-s-behaves-d=
ifferently-than-read-if-killed-with-ctrl-c =
<https://unix.stackexchange.com/questions/463253/why-would-read-s-behaves-=
differently-than-read-if-killed-with-ctrl-c>=