Displaying 2 results from an estimated 2 matches for "quoted_fil".
Did you mean:
quoted_file
2023 Mar 22
1
[libnbd PATCH v4 0/2] lib/utils: introduce async-signal-safe execvpe()
...is anything other than "sh", then the busybox binary doesn't recognize itself as the shell!
The as-if rule might allow us to invoke something like execv(<shell
path>, {"sh", "-c", munge(file), argv[0], argv[1], ..., NULL}, where
munge(file) produces ". quoted_file" as a way to source the contents
of file in the current shell environment, without ';' or other
metacharacters in file causing us to go off the rail. But getting
munge(file) to work correctly without post-fork() malloc() is going to
be just as difficult (our _init function pre-fork w...
2023 Mar 22
3
[libnbd PATCH v4 0/2] lib/utils: introduce async-signal-safe execvpe()
On 3/21/23 18:28, Eric Blake wrote:
> it is indeed a bug in busybox now that POSIX is moving towards
> standardizing realpath, so I've filed it:
> https://bugs.busybox.net/show_bug.cgi?id=15466
I've found another busybox bug.
The "/bin/sh" utility is provided by busybox as well (via the usual symlinking).
Per POSIX, if
execvp(file, { argv[0], argv[1], ..., NULL })