From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/portage:master commit in: cnf/
Date: Wed, 12 Dec 2018 18:41:49 +0000 (UTC) [thread overview]
Message-ID: <1544640085.55a9d4ccc5ac90b454638f9205f8a5d20ca8b47a.mgorny@gentoo> (raw)
commit: 55a9d4ccc5ac90b454638f9205f8a5d20ca8b47a
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Wed Dec 12 17:36:48 2018 +0000
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Wed Dec 12 18:41:25 2018 +0000
URL: https://gitweb.gentoo.org/proj/portage.git/commit/?id=55a9d4cc
Enable {ipc,network,pid}-sandbox by default
The sandboxes are stable enough to be enabled by default, and they all
prevent undesirable situations. Furthermore, they all gracefully handle
missing namespace support.
Reviewed-by: Zac Medico <zmedico <AT> gentoo.org>
Signed-off-by: Michał Górny <mgorny <AT> gentoo.org>
cnf/make.globals | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/cnf/make.globals b/cnf/make.globals
index d394a1890..1bcc7ce64 100644
--- a/cnf/make.globals
+++ b/cnf/make.globals
@@ -52,10 +52,11 @@ FETCHCOMMAND_SFTP="bash -c \"x=\\\${2#sftp://} ; host=\\\${x%%/*} ; port=\\\${ho
# Default user options
FEATURES="assume-digests binpkg-docompress binpkg-dostrip binpkg-logs
config-protect-if-modified distlocks ebuild-locks
- fixlafiles merge-sync multilib-strict news
- parallel-fetch preserve-libs protect-owned
- sandbox sfperms strict unknown-features-warn unmerge-logs
- unmerge-orphans userfetch userpriv usersandbox usersync"
+ fixlafiles ipc-sandbox merge-sync multilib-strict
+ network-sandbox news parallel-fetch pid-sandbox
+ preserve-libs protect-owned sandbox sfperms strict
+ unknown-features-warn unmerge-logs unmerge-orphans userfetch
+ userpriv usersandbox usersync"
# Ignore file collisions in /lib/modules since files inside this directory
# are never unmerged, and therefore collisions must be ignored in order for
next reply other threads:[~2018-12-12 18:41 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 18:41 Michał Górny [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-10 22:59 [gentoo-commits] proj/portage:master commit in: cnf/ Sam James
2023-10-13 10:19 Sam James
2023-08-03 21:15 Sam James
2023-08-03 21:15 Sam James
2022-04-11 20:17 Mike Gilbert
2022-02-06 19:19 Zac Medico
2021-11-16 21:17 Zac Medico
2020-05-03 20:32 Zac Medico
2019-10-21 18:07 Michał Górny
2019-09-26 0:03 Zac Medico
2019-07-05 5:39 Michał Górny
2019-04-19 5:16 Zac Medico
2018-08-12 10:05 Zac Medico
2018-07-11 18:01 Zac Medico
2018-05-11 7:48 Michał Górny
2017-12-11 2:27 Zac Medico
2017-08-02 8:06 Michał Górny
2017-01-06 22:13 Brian Dolbec
2017-01-06 18:00 Brian Dolbec
2017-01-06 18:00 Brian Dolbec
2015-12-15 8:40 Brian Dolbec
2015-03-10 17:53 Zac Medico
2014-11-02 3:02 Zac Medico
2013-07-25 22:00 Zac Medico
2013-05-10 4:09 Zac Medico
2013-01-21 16:52 Zac Medico
2013-01-21 16:48 Zac Medico
2012-11-05 8:52 Zac Medico
2012-09-06 20:06 Zac Medico
2012-08-17 21:36 Zac Medico
2012-08-05 8:13 Zac Medico
2012-07-23 17:45 Zac Medico
2012-07-09 21:03 Zac Medico
2012-07-06 6:43 Zac Medico
2012-05-05 16:41 Zac Medico
2011-12-22 4:30 Zac Medico
2011-12-22 4:22 Zac Medico
2011-12-21 21:45 Zac Medico
2011-11-11 21:23 Zac Medico
2011-08-26 3:52 Zac Medico
2011-06-03 5:24 Zac Medico
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=1544640085.55a9d4ccc5ac90b454638f9205f8a5d20ca8b47a.mgorny@gentoo \
--to=mgorny@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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