On 2008-05-07 18:39 +0200, Andrei Popescu wrote:
> On Wed, May 07, 2008 at 08:44:34PM +1200, Chris Bannister wrote:
>> Umm, well, if /bin/sh points to dash/ash and you write a script with
>> bashisms then you have to have #!/bin/bash as the interpreter line. The
>> reason there was talk about it,
On Wed, May 07, 2008 at 08:44:34PM +1200, Chris Bannister wrote:
> > some years ago I remember reading here that pointing /bin/sh to dash or
> > ash would break a lot of important scripts in Debian;
>
> Umm, well, if /bin/sh points to dash/ash and you write a script with
> bashisms then you have
On Tue, May 06, 2008 at 09:29:44PM -0300, Otavio Exel wrote:
> Hello List,
>
> I've been writing shell scripts to be run as root lately;
> I'm not aware of any security-risk involving bash but I'd much more
> rather run those scripts with ash or dash instead of bash;
Obviously ash or dash have to
On Tue, May 06, 2008 at 09:29:44PM -0300, Otavio Exel wrote:
> some years ago I remember reading here that pointing /bin/sh to dash or
> ash would break a lot of important scripts in Debian;
$ ls -la `which sh`
lrwxrwxrwx 1 root root 4 2008-05-07 09:20 /bin/sh -> dash
I had it like this for so
Otavio Exel wrote:
Hello List,
I've been writing shell scripts to be run as root lately;
I'm not aware of any security-risk involving bash but I'd much more
rather run those scripts with ash or dash instead of bash;
What sort of security risks do you have in mind other than human error?
Parti
Hello List,
I've been writing shell scripts to be run as root lately;
I'm not aware of any security-risk involving bash but I'd much more
rather run those scripts with ash or dash instead of bash;
some years ago I remember reading here that pointing /bin/sh to dash or
ash would break a lot of imp
6 matches
Mail list logo
