public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Seebs <seebs@seebs.net>, Andre McCurdy <armccurdy@gmail.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] pseudo: Force seccomp to return success when in fact doing nothing
Date: Sat, 04 Apr 2020 23:45:51 +0100	[thread overview]
Message-ID: <dd4a9f62d5ed17c83fec6cdc8edb3b46453ad646.camel@linuxfoundation.org> (raw)
In-Reply-To: <20200404171329.3398164c@seebsdell>

On Sat, 2020-04-04 at 17:13 -0500, Seebs wrote:
> On Sat, 4 Apr 2020 14:32:03 -0700
> "Andre McCurdy" <armccurdy@gmail.com> wrote:
> 
> > Also, since prctl() is Linux specific, it looks like this patch
> > will
> > make pseudo Linux specific. Is that OK? If so maybe worth making an
> > official statement that OE is only supported for Linux hosts?
> 
> We have existing hooks for making things like this be in a
> Linux-specific port directory. I don't think the Darwin port still
> works; people asked me about it a lot, so I made it work and never
> heard about it again. :)

Darwin disabled LD preloads as they were too much of a security risk,
thereby making pseudo 'problematic' on darwin as I understand it :(

At Peter mentions, we should really have prctl in the Linux specific
ports directory.

Cheers,

Richard


      reply	other threads:[~2020-04-04 22:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-03 21:59 [PATCH] pseudo: Force seccomp to return success when in fact doing nothing Richard Purdie
2020-04-03 22:34 ` [OE-core] " Khem Raj
2020-04-03 22:39 ` Andre McCurdy
2020-04-04 10:17   ` Richard Purdie
2020-04-04 21:32     ` Andre McCurdy
2020-04-04 22:13       ` Seebs
2020-04-04 22:45         ` Richard Purdie [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=dd4a9f62d5ed17c83fec6cdc8edb3b46453ad646.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=armccurdy@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=seebs@seebs.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox