[prev in list] [next in list] [prev in thread] [next in thread]
List: busybox
Subject: Re: NOEXEC environment bug
From: Denys Vlasenko <vda.linux () googlemail ! com>
Date: 2017-11-03 13:18:18
Message-ID: CAK1hOcMzic8MqTGWHrU97jAHHVgFj4NsA1F-iM3RhHj3s6r8tw () mail ! gmail ! com
[Download RAW message or body]
On Wed, Nov 1, 2017 at 8:50 PM, Ron Yorston <rmy@pobox.com> wrote:
> There's a related problem when SH_STANDALONE and SH_NOFORK are enabled:
> changed shell variables aren't visible to NOFORK applets. For example,
>
> $ ./busybox sh
> $ mkdir ~/mybin
> $ cp busybox ~/mybin/thing
> $ export PATH=~/mybin:$PATH
> $ which thing
> $
>
> If SH_NOFORK is disabled (or 'which' is not NOFORK):
>
> $ ./busybox sh
> $ export PATH=~/mybin:$PATH
> $ which thing
> /home/rmy/mybin/thing
> $
>
> Lots more applets have been made NOFORK recently, though at a quick
> glance I suspect most of them don't access environment variables.
> Obviously 'which' does. And 'printenv'.
Indeed, it's a bug. Fixed in git, thanks!
_______________________________________________
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic