It occurred to me that it might be good to set NO_NEW_PRIVS automatically when chroot is not invoked by root, rather than error out and make the user specify -n.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Feed Search
Yesterday
Yesterday
Mon, Mar 23
Mon, Mar 23
Sun, Mar 22
Sun, Mar 22
Wed, Mar 11
Wed, Mar 11
Tue, Mar 10
Tue, Mar 10
Sat, Mar 7
Sat, Mar 7
Thu, Mar 5
Thu, Mar 5
Wed, Mar 4
Wed, Mar 4
Feb 4 2026
Feb 4 2026
Feb 1 2026
Feb 1 2026
Jan 31 2026
Jan 31 2026
Jan 30 2026
Jan 30 2026
Jan 22 2026
Jan 22 2026
Jan 14 2026
Jan 14 2026
Jan 11 2026
Jan 11 2026
Dec 21 2025
Dec 21 2025
Dec 20 2025
Dec 20 2025
Dec 18 2025
Dec 18 2025
Dec 17 2025
Dec 17 2025
Dec 16 2025
Dec 16 2025
Dec 11 2025
Dec 11 2025
Dec 7 2025
Dec 7 2025
Nov 28 2025
Nov 28 2025
Nov 26 2025
Nov 26 2025
Nov 13 2025
Nov 13 2025
Oct 30 2025
Oct 30 2025
Oct 29 2025
Oct 29 2025
Oct 27 2025
Oct 27 2025
Oct 26 2025
Oct 26 2025
Oct 25 2025
Oct 25 2025
Oct 5 2025
Oct 5 2025
Oct 3 2025
Oct 3 2025
Oct 1 2025
Oct 1 2025
Sep 30 2025
Sep 30 2025
Sep 21 2025
Sep 21 2025
Sep 19 2025
Sep 19 2025
Sep 16 2025
Sep 16 2025
Sep 14 2025
Sep 14 2025
Sep 10 2025
Sep 10 2025
Sep 7 2025
Sep 7 2025
Sep 6 2025
Sep 6 2025
Sep 5 2025
Sep 5 2025
Aug 26 2025
Aug 26 2025
Aug 24 2025
Aug 24 2025
Aug 21 2025
Aug 21 2025
Aug 14 2025
Aug 14 2025
Aug 5 2025
Aug 5 2025
Aug 3 2025
Aug 3 2025
For chroot(8), it seems a little cryptic to only mention security.bsd.unprivileged_chroot in the -n flag section. Might I suggest adding a paragraph like the following up-top, before the options descriptions:
Jul 27 2025
Jul 27 2025
Jul 24 2025
Jul 24 2025
Jun 28 2025
Jun 28 2025
Jun 21 2025
Jun 21 2025
Jun 16 2025
Jun 16 2025
Jun 14 2025
Jun 14 2025
Jun 11 2025
Jun 11 2025
Jun 7 2025
Jun 7 2025
Jun 5 2025
Jun 5 2025
Jun 4 2025
Jun 4 2025
Jun 1 2025
Jun 1 2025
May 30 2025
May 30 2025
May 27 2025
May 27 2025
May 25 2025
May 25 2025
May 23 2025
May 23 2025
May 20 2025
May 20 2025