Hello!
I would appreciate if bash could optionally
(some option – on by default when histexpand is set)
store the command line *before* history expansion
additionally to expanded line.
Regards,
Hans
On 12/10/15, Hans Ginzel wrote:
> Hello!
>
> I would appreciate if bash could optionally
> (some option – on by default when histexpand is set)
> store the command line *before* history expansion
> additionally to expanded line.
>
> Regards,
> Hans
>
Just curious, why?
---
xoxo iza
Hello,
This is a suggestion for a bash security hardening patch which
prevents xtrace from being initialized to the SHELLOPTS environment
variable when a new shell starts.
xtrace can be used to exploit bogus system()/popen() calls on setuid
binaries via a specially crafted PS4 environment
On 12/10/15 11:04 AM, Hans Ginzel wrote:
> Hello!
>
> I would appreciate if bash could optionally
> (some option – on by default when histexpand is set)
> store the command line *before* history expansion
> additionally to expanded line.
Store it where? In this history list? Why?
--
``The ly
2015-12-10 20:16:49 +0100, up201407...@alunos.dcc.fc.up.pt:
> Hello,
>
> This is a suggestion for a bash security hardening patch which
> prevents xtrace from being initialized to the SHELLOPTS environment
> variable when a new shell starts.
>
> xtrace can be used to exploit bogus system()/popen(
On 12/9/15 8:11 PM, Mingye Wang (Arthur2e5) wrote:
> Bash Version: 4.3
> Patch Level: 42
>
> Description:
> `alias' does not `--'-ize alias items with a name starting with a `-'
> when it is invoked to print aliases in the reusable form. This causes
> `invalid option' errors when trying to reuse
