Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"/sys/kernel/security/chromiumos/inode_security_policies/allow_fifo" is now read-only #5056

Closed
powerCord154 opened this issue Mar 9, 2024 · 4 comments

Comments

@powerCord154
Copy link

powerCord154 commented Mar 9, 2024

Please paste the output of the following command here: sudo edit-chroot -all

cant

Please describe your issue:

/usr/local/bin/mount-chroot: 362: cannot create /sys/kernel/security/chromiumos/inode_security_policies/allow_fifo: Read-only file system occurs after today's dev channel update (124.0.6340.0).
It's /sys/kernel/security/ that's been made read-only

If known, describe the steps to reproduce the issue:

run crouton

@powerCord154
Copy link
Author

powerCord154 commented Mar 9, 2024

actually, I just found a fix:
sudo mount -o remount,rw /sys/kernel/security/

@dnschneid if this could be incorporated in the crouton enter-chroot script, that would help

@nethershaw
Copy link

"Maintenance mode" is code for "abandoned to a community that can't keep up with all the things Google does to make everyone else's lives harder, because asking someone to step up and wrangle the million forks was beyond us."

dnschneid added a commit that referenced this issue May 9, 2024
@dnschneid
Copy link
Owner

Actually, thanks for bumping this, since I somehow missed it in my inbox.

Give BRANCH=rwsec a try; I can't test it right now. It's based on the silence branch since I assume you need that.

@Mar-Kali
Copy link

Many thanks to powerCord154,
In a VT (Virtual Terminal) I did the command:
$ sudo mount -o remount, rw /sys/kernel/security
and after I was again able to do a "sudo enter-chroot".
;-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants