You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Update README.md
Fix a phrasing error and adding a link to the ChromeBrew project.
* Add Crouton URL
Add URL for Crouton:
https://github.com/dnschneid/crouton
* Remove bad / in URL
Remove a bad slash (/) in an added URL
Copy file name to clipboardExpand all lines: README.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,20 +1,20 @@
1
1
# crew-sudo
2
-
Make `sudo` "works" on ChromeOS `crosh` shell (ChromeOS v117+) by redirecting sudo calls to VT-2 shell
2
+
Make `sudo` "works" on ChromeOS `crosh` shell (ChromeOS v117+) by redirecting sudo calls to VT-2 shell.
3
3
4
4
## Background
5
5
On ChromeOS v117, all Chrome-related processes (e.g. the ChromeOS UI) is executed with the `NO_NEW_PRIVS` bit, which means:
6
6
-`suid/sgid`-bit is blocked, and thus no more `sudo`
7
7
- This flag will be inherited by its subprocess (including `crosh`) and cannot be unset
8
8
9
-
That benefits security. However, it is bad for Crouton/Chromebrew users.
9
+
That benefits security. However, it is bad for [Crouton](https://github.com/dnschneid/crouton)/[Chromebrew](https://github.com/chromebrew/chromebrew) users.
10
10
11
11
The official workaround for this is using the VT-2 shell (aka `frecon`) [^1], but `frecon` just sucks:
12
12
- No clipboard support
13
13
- No Caps Lock support
14
14
- No HiDPI support
15
15
- Poor compatibility with TUI programs
16
16
17
-
So does there a way to call `sudo` in `crosh` but run it in VT-2? That's what this project does :)
17
+
So is there a way to call `sudo` in `crosh` but run it in VT-2? That's what this project does :)
18
18
19
19
[^1]: `sudo` works in VT-2 because the VT-2 process is independent of the browser process and executed without the `NO_NEW_PRIVS` bit
0 commit comments