From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] firejail: new package
Date: Tue, 7 Mar 2017 21:50:32 +0100 [thread overview]
Message-ID: <20170307215032.64ed76d6@free-electrons.com> (raw)
In-Reply-To: <1477502552-4236-1-git-send-email-cdf123@cdf123.net>
Hello,
On Wed, 26 Oct 2016 12:22:32 -0500, Chris Frederick wrote:
> Firejail Security Sandbox
> https://firejail.wordpress.com/
>
> Lightweight application sandboxing system using seccomp and kernel
> namespaces.
>
> Signed-off-by: Chris Frederick <cdf123@cdf123.net>
> ---
> DEVELOPERS | 3 +++
> package/Config.in | 1 +
> package/firejail/Config.in | 17 +++++++++++++++++
> package/firejail/firejail.hash | 2 ++
> package/firejail/firejail.mk | 27 +++++++++++++++++++++++++++
> 5 files changed, 50 insertions(+)
> create mode 100644 package/firejail/Config.in
> create mode 100644 package/firejail/firejail.hash
> create mode 100644 package/firejail/firejail.mk
Thanks, I've applied to the master branch, with the following changes:
[Thomas:
- Fix DEVELOPERS entry: use <> around the e-mail address instead of ()
- firejail builds fine with musl, so only exclude uclibc, which fails
to build with EM_ARM undeclared
- Update to upstream version 0.9.44.8.
- Remove FIREJAIL_MAKE_OPTS, as suggested by Romain Naour.
- Pass --enable-busybox-workaround only if Busybox is enabled, as
suggested by Romain Naour.]
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-03-07 20:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 17:22 [Buildroot] [PATCH 1/1] firejail: new package Chris Frederick
2017-01-28 14:35 ` Romain Naour
2017-03-07 20:50 ` Thomas Petazzoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-10-20 17:54 Chris Frederick
2016-10-24 21:40 ` Thomas Petazzoni
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=20170307215032.64ed76d6@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.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