Codex cli - Revision history

Busk at 23:08, 7 May 2026

2026-05-07T23:08:50Z

Busk at 23:08, 7 May 2026

2026-05-07T23:08:05Z

Busk: Created page with "2. Trusted Binaries The risk is considered low because bubblewrap is a small, heavily audited, and "security-first" piece of software. Its entire purpose is to provide isolati..."

2026-05-07T23:07:48Z

Created page with "2. Trusted Binaries The risk is considered low because bubblewrap is a small, heavily audited, and "security-first" piece of software. Its entire purpose is to provide isolati..."

New page

2. Trusted Binaries
The risk is considered low because bubblewrap is a small, heavily audited, and "security-first" piece of software. Its entire purpose is to provide isolation. Most Linux security experts consider it safer to allow bwrap to function (so it can sandbox other dangerous code) than to leave it broken.

3. Targeted vs. Global
This is significantly safer than the alternative method of running sudo sysctl -w kernel.unprivileged_userns_clone=1.

The Global Method: Allows every program on your computer (including a malicious script or a compromised web browser) to create namespaces.

The AppArmor Method: Limits that power strictly to the bwrap utility.

Summary
This configuration is the "middle ground" of security. It restores functionality to your development tools while keeping the rest of the operating system locked down. The risk is that you are placing absolute trust in the integrity of the bwrap developers.

← Older revision		Revision as of 23:08, 7 May 2026
Line 40:		Line 40:

	This configuration is the "middle ground" of security. It restores functionality to your development tools while keeping the rest of the operating system locked down. The risk is that you are placing absolute trust in the integrity of the `bwrap` developers.		This configuration is the "middle ground" of security. It restores functionality to your development tools while keeping the rest of the operating system locked down. The risk is that you are placing absolute trust in the integrity of the `bwrap` developers.
		+
		+
		+	# More
		+
		+	This message appears because modern Linux distributions (especially Ubuntu 23.10+ and 24.04) have introduced security restrictions on unprivileged user namespaces, which `bubblewrap` (the engine behind Codex's sandbox) requires to function.
		+
		+	### Fix for Ubuntu 24.04+ (AppArmor)
		+
		+	Ubuntu now requires an AppArmor profile to allow unprivileged applications to create namespaces. You can create a profile specifically for `bubblewrap`:
		+
		+	```bash
		+	sudo nano /etc/apparmor.d/usr.bin.bwrap
		+
		+	```
		+
		+	Paste the following into the file:
		+
		+	```text
		+	abi <abi/4.0>,
		+	include <tunables/global>
		+
		+	/usr/bin/bwrap flags=(unconfined) {
		+	userns,
		+	include if exists <local/usr.bin.bwrap>
		+	}
		+
		+	```
		+
		+	Reload AppArmor:
		+
		+	```bash
		+	sudo systemctl reload apparmor
		+
		+	```
		+
		+	---
		+
		+	### Alternative: Enable via Kernel Parameter
		+
		+	If the AppArmor fix does not apply or you are on a different distribution (like Debian), you can enable unprivileged namespaces directly via `sysctl`.
		+
		+	Temporary (until reboot):
		+
		+	```bash
		+	sudo sysctl -w kernel.unprivileged_userns_clone=1
		+
		+	```
		+
		+	Permanent:
		+
		+	```bash
		+	echo "kernel.unprivileged_userns_clone=1" \| sudo tee /etc/sysctl.d/99-userns.conf
		+	sudo sysctl -p /etc/sysctl.d/99-userns.conf
		+
		+	```
		+
		+	Note: On some systems, you may also need to ensure `user.max_user_namespaces` is set to a high value:
		+
		+	```bash
		+	sudo sysctl -w user.max_user_namespaces=15000
		+
		+	```
		+
		+	---
		+
		+	### Verification
		+
		+	Once applied, you can verify that namespaces are working by running:
		+
		+	```bash
		+	unshare -U --map-root-user true && echo "Success"
		+
		+	```
		+
		+	If it prints "Success", Codex should now be able to initialize its sandbox without the warning.

@@ Line 1: / Line 1: @@
-. Trusted Binaries
+This AppArmor profile is a **targeted exception**. Instead of turning off security restrictions for the entire operating system, it grants a specific permission to only one program: `bubblewrap` (`bwrap`).
-. Targeted vs. Global
+### Breakdown of the Code
-The Global Method: Allows every program on your computer (including a malicious script or a compromised web browser) to create namespaces.
+* **`abi <abi/4.0>,`**: This tells AppArmor to use the feature set and syntax rules introduced in version 4.0.
-The AppArmor Method: Limits that power strictly to the bwrap utility.
+---
-Summary
+### What does it do?
 This configuration is the "middle ground" of security. It restores functionality to your development tools while keeping the rest of the operating system locked down. The risk is that you are placing absolute trust in the integrity of the bwrap developers.