Commit `be4078d25ff3af268a6ef7ab56c8121f9a8dfb36' introduced the following
issue:
| dualbus@system76-pc:~/src/gnu/bash$ ./configure --silent
|
| Beginning configuration for bash-5.0-maint for x86_64-pc-linux-gnu
|
| ./configure: line 9614: gl_PTHREAD_RWLOCK_RDLOCK_PREFER_WRITER: command not
fo
Date:Tue, 19 Feb 2019 10:41:41 -0500
From:Greg Wooledge
Message-ID: <20190219154141.di73jptd2ric6...@eeg.ccf.org>
| Looks like the best workaround (for bash/ksh) is to store the -d '' args
| in an array, and use something like:
|
| mapfile -t ${bNullDelimited+
Date:Sun, 17 Feb 2019 20:07:06 -0500
From:Chet Ramey
Message-ID: <71d1418e-54a1-ddd4-6467-cbc27122e...@case.edu>
| The idea behind the bash behavior is that a
| null string added to a non-empty word is simply discarded,
This is clearly not POSIX compliant behavio
On 2/19/19 7:31 PM, Grisha Levit wrote:
> -c "($BASH --norc -i -c 'set +m; exec /; set -m; \$(:)')"
Thanks, I was able to reproduce it with this.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRUc.
On Tue, Feb 19, 2019, 7:28 PM Chet Ramey wrote:
> I can't reproduce this on my Mac OS X box when I run the devel version
> as a login shell and ssh to localhost.
>
I was also able to get the same result with
$BASH -c "($BASH --norc -i -c 'set +m; exec /; set -m; \$(:)')"
>
On 2/18/19 12:55 PM, Grisha Levit wrote:
> On Sun, Feb 17, 2019 at 8:23 PM Chet Ramey wrote:
>> Thanks for the report. I'll fix it in the next devel branch push.
>
> One more corner case, only shows up when bash is started by `login`:
>
> $ set +m; exec /
> -bash: /: Is a directory
> -bash: exec
On 2019-02-19 10:41, Greg Wooledge wrote:
On Sun, Feb 17, 2019 at 08:07:06PM -0500, Chet Ramey wrote:
On 2/16/19 11:38 AM, sunnycemet...@gmail.com wrote:
There are mixed behaviors. The idea behind the bash behavior is that a
null string added to a non-empty word is simply discarded, and this hap
On Tue, Feb 19, 2019 at 09:24:38AM -0500, Chet Ramey wrote:
> On 2/19/19 3:24 AM, azad vishwakarma wrote:
> > hi there
> > while changing password with terminal/bash, it accepts tab and arrow keys
> > along with characters,symbols and spacebar. But when we try to login into
> > the system *"TAB and
On Sun, Feb 17, 2019 at 08:07:06PM -0500, Chet Ramey wrote:
> On 2/16/19 11:38 AM, sunnycemet...@gmail.com wrote:
> > I would like to include a null string as part of a parameter expansion word:
> >
> >> mapfile -t${bNullDelimited+d ''}
> >
> > When bNullDelimited is set, I expect this to expand
On 2/19/19 3:24 AM, azad vishwakarma wrote:
> hi there
> while changing password with terminal/bash, it accepts tab and arrow keys
> along with characters,symbols and spacebar. But when we try to login into
> the system *"TAB and ARROW key" *perform their own usual task. So we can't
> enter the pas
-- Forwarded message -
From: Kali Linux Bug Tracker
Date: Mon, Feb 18, 2019 at 7:11 PM
Subject: [Kali Linux 0005256]: validation problem in password
To:
The following issue has been CLOSED
==
https://bugs.kali.o
hi there
while changing password with terminal/bash, it accepts tab and arrow keys
along with characters,symbols and spacebar. But when we try to login into
the system *"TAB and ARROW key" *perform their own usual task. So we can't
enter the password and it tells that password is incorrect.i tried
12 matches
Mail list logo
