<div><br></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Jan 20, 2020 at 9:10 AM Ross Burton <<a href="mailto:ross.burton@intel.com">ross.burton@intel.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 20/01/2020 15:45, Khem Raj wrote:<br>
> pseudo needs some love since it alters syscalls which go out of bounds<br>
> what is allowed by libseccomp until then pin your file version to 5.37<br>
> in arch till a supported distro is affected by same problem. It wont<br>
> be long better option is to fix pseudo<br>
<br>
That's not quite right. pseudo LD_PRELOADs itself into file, and makes <br>
syscalls which are not whitelisted in file's seccomp configuration.<br>
</blockquote><div dir="auto"><br></div><div dir="auto">It’s is not different than what I was saying how it inserts itself into process is a detail which is hidden from operating system </div><div dir="auto"><br></div><div dir="auto">However I think file is only one case when used along with libseccomp there could be more use cases if other host tools we use start using it</div><div dir="auto"><br></div><div dir="auto">So I wonder If we should start building own native versions of tools or make it part of build tools tarball </div><div dir="auto">Or perhaps just publish a self built container and not worry about what distros are doing underneath </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
There's nothing pseudo can do to solve this.<br>
<br>
Ross<br>
</blockquote></div></div>