[OE-core] pseudo: host user contamination
Seebs
seebs at seebs.net
Fri Mar 23 16:28:20 UTC 2018
On Fri, 23 Mar 2018 17:10:35 +0100
Enrico Scholz <enrico.scholz at sigma-chemnitz.de> wrote:
> I think, 'mv' is the culprit. It calls 'renameat2()' directly over
> 'syscall()':
>
> | $ ltrace mv foo bar
> | ...
> | syscall(316, 0xffffff9c, 0x7fff1564a341,
> 0xffffff9c) = 0
>
>
> Perhaps, 'pseudo' does not catch this?
Yeah.
And so far as I know, it's not actually *possible* to in the general
case. I really don't think it's safe to try to catch syscall().
I was afraid someone would do this. (It also breaks most Go programs,
for similar reasons; no libc calls.)
I have no idea why they're doing that; it seems distinctly unsafe.
-s
More information about the Openembedded-core
mailing list