Re: feature request: allow shif [n] with n > $#

2019-04-11 Thread Chet Ramey
On 4/11/19 4:18 PM, Toralf Förster wrote: > Given: > > $> cat #!/bin/bash > # > > shift 3 > > echo ">>${@}<<" > EOF > > then a call with less than 3 parameter, eg. "./shift.sh 1 2" gives ">>1 2<<". > Whilst the man page does not deny this behaviour I do wonder if a feature > reque

Update link to bash-completion (debian)

2019-04-11 Thread Дилян Палаузов
Hello, as alioth.debian.or is down, replace at https://www.gnu.org/software/bash/manual/html_node/A-Programmable-Completion-Example.html the reference from http://bash-completion.alioth.debian.org/ to https://salsa.debian.org/debian/bash-completion . Regards Дилян

process substitution and wait()

2019-04-11 Thread Daniel Kahn Gillmor
Over in the "here strings and tmpfiles" thread, a distraction came up, which i'm splitting out into a separate thread. Please don't conflate the two, i'm just looking for further clarity about process substitutions and the wait builtin. dkg and chet wrote: https://bugs.debian.org/920455 >>>

[PATCH] Add -q (quiet) option to pushd/popd

2019-04-11 Thread Benjamin Barenblat
Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -g -O2 -Wno-parentheses -Wno-format-security uname output: Linux summerland 4.9.0-8-amd64 #1 SMP Debian 4.9.144-3.1 (2019-02-19) x86_64 GNU/Linux Machine Type: x86_64

feature request: allow shif [n] with n > $#

2019-04-11 Thread Toralf Förster
Given: $> cat >${@}<<" EOF then a call with less than 3 parameter, eg. "./shift.sh 1 2" gives ">>1 2<<". Whilst the man page does not deny this behaviour I do wonder if a feature request to get ">><<" instead is sufficient here? -- Toralf PGP C4EACDDE

Re: "here strings" and tmpfiles

2019-04-11 Thread Chet Ramey
On 4/11/19 3:15 AM, Robert Elz wrote: > (Substitute cat if you're that kind of weirdo!). We're really going to throw down right here? -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, UTech, CWRUc...@c

Re: "here strings" and tmpfiles

2019-04-11 Thread Chet Ramey
On 4/11/19 12:12 AM, Jason A. Donenfeld wrote: > I keep forgetting things. The other thing I wanted to bring up is that > I suspect bash's actual implementation of temporary files is > problematic and might have some of the classic /tmp and TOCTOU style > attacks. It's a peripheral issue, since t

Re: "here strings" and tmpfiles

2019-04-11 Thread Chet Ramey
On 4/11/19 12:02 AM, Jason A. Donenfeld wrote: > Hi Chet, Hi. > I hope that can shed light on the motivation a bit. Pass got hit by > this a bit ago: > https://git.zx2c4.com/password-store/commit/?id=367efa5846492e1b0898aad8a2c26ce94163ba24 I note that the pipe-for-small-enough-heredocs works fo

Re: "here strings" and tmpfiles

2019-04-11 Thread konsolebox
On Thu, Apr 11, 2019 at 5:31 AM konsolebox wrote: > > On Thu, Apr 11, 2019, 4:45 AM Chet Ramey wrote: >> >> On 4/10/19 4:33 PM, konsolebox wrote: >> > On Wed, Apr 10, 2019 at 11:15 PM Chet Ramey wrote: >> >> If we're going to go off into hypotheticals and speculation, it would be >> >> nice if m

Re: "here strings" and tmpfiles

2019-04-11 Thread Chet Ramey
On 4/10/19 7:18 PM, Daniel Kahn Gillmor wrote: > On Wed 2019-04-10 16:16:44 -0400, Chet Ramey wrote: >> Is it just that people have not realized all along that most shells, >> certainly all historical shells, that implement here documents use temp >> files to do it? It's really only the ash-based s

Re: "here strings" and tmpfiles

2019-04-11 Thread Daniel Kahn Gillmor
On Thu 2019-04-11 10:04:02 +0200, Andreas Schwab wrote: > On Apr 10 2019, Daniel Kahn Gillmor wrote: > >> data written to the local filesystem can be discovered by someone >> analyzing the disk controller data path, or by someone with access to >> the underlying storage medium. > > Do you have swa

Re: "here strings" and tmpfiles

2019-04-11 Thread konsolebox
On Thu, Apr 11, 2019, 10:42 PM Andreas Kusalananda Kähäri < andreas.kah...@abc.se> wrote: > On Thu, Apr 11, 2019 at 09:01:50PM +0800, konsolebox wrote: > > On Thu, Apr 11, 2019, 4:04 PM Andreas Schwab wrote: > > > > > On Apr 10 2019, Daniel Kahn Gillmor wrote: > > > > > > > data written to the l

Re: "here strings" and tmpfiles

2019-04-11 Thread Andreas Kusalananda Kähäri
On Thu, Apr 11, 2019 at 09:01:50PM +0800, konsolebox wrote: > On Thu, Apr 11, 2019, 4:04 PM Andreas Schwab wrote: > > > On Apr 10 2019, Daniel Kahn Gillmor wrote: > > > > > data written to the local filesystem can be discovered by someone > > > analyzing the disk controller data path, or by some

Re: "here strings" and tmpfiles

2019-04-11 Thread konsolebox
On Thu, Apr 11, 2019 at 9:06 PM Greg Wooledge wrote: > So... yes. Because everyone in 2019 has a laptop and therefore has swap > enabled because it's used for hibernation. Sure captain. It was a joke. -- konsolebox

Re: "here strings" and tmpfiles

2019-04-11 Thread Greg Wooledge
On Thu, Apr 11, 2019 at 09:01:50PM +0800, konsolebox wrote: > On Thu, Apr 11, 2019, 4:04 PM Andreas Schwab wrote: > > Do you have swap enabled? > > It's 2019. So... yes. Because everyone in 2019 has a laptop and therefore has swap enabled because it's used for hibernation. That was what you me

Re: "here strings" and tmpfiles

2019-04-11 Thread konsolebox
On Thu, Apr 11, 2019, 4:04 PM Andreas Schwab wrote: > On Apr 10 2019, Daniel Kahn Gillmor wrote: > > > data written to the local filesystem can be discovered by someone > > analyzing the disk controller data path, or by someone with access to > > the underlying storage medium. > > Do you have sw

Re: "here strings" and tmpfiles

2019-04-11 Thread Greg Wooledge
On Thu, Apr 11, 2019 at 06:02:41AM +0200, Jason A. Donenfeld wrote: > what about internally treating "x < x"? Are these somehow not quite equivalent because x is in a subshell > in one but not the other, or something like that? cmd <<< string opens a temporary file for writing, dumps the string

Re: "here strings" and tmpfiles

2019-04-11 Thread Andreas Schwab
On Apr 10 2019, Daniel Kahn Gillmor wrote: > data written to the local filesystem can be discovered by someone > analyzing the disk controller data path, or by someone with access to > the underlying storage medium. Do you have swap enabled? Andreas. -- Andreas Schwab, SUSE Labs, sch...@suse.

Re: "here strings" and tmpfiles

2019-04-11 Thread Robert Elz
Date:Thu, 11 Apr 2019 06:02:41 +0200 From:"Jason A. Donenfeld" Message-ID: | Now, it might be the case that bash really isn't the | right tool for that kind of thing, and I shouldn't use bash for tasks | with security requirements as such. But I sort of love