On Tue, 2020-03-31 at 12:57 +0200, Jan Luebbe wrote: > Hi, > > On Mon, 2020-01-20 at 17:10 +0000, Ross Burton wrote: > > On 20/01/2020 15:45, Khem Raj wrote: > > > pseudo needs some love since it alters syscalls which go out of > > > bounds > > > what is allowed by libseccomp until then pin your file version to > > > 5.37 > > > in arch till a supported distro is affected by same problem. It > > > wont > > > be long better option is to fix pseudo > > > > That's not quite right. pseudo LD_PRELOADs itself into file, and > > makes > > syscalls which are not whitelisted in file's seccomp configuration. > > > > There's nothing pseudo can do to solve this. > > I stumbled across this thread when checking why libseccomp is not in > oe-core or meta-oe. It seems to me that pseudo could intercept the > seccomp(2) or libseccomps seccomp_* function calls and report them as > unsupported to simulate running on a kernel without seccomp support. > > What am I missing? :)
I don't think we'd thought of that, I like the idea in principle... Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#136879): https://lists.openembedded.org/g/openembedded-core/message/136879 Mute This Topic: https://lists.openembedded.org/mt/72386229/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
