[Bug 297426] linuxulator: linprocfs /proc/self/exe host path breaks execve under Linux ABI
| Newsgroups | gmane.os.freebsd.bugs |
|---|---|
| Message-ID | <[email protected]/bugzilla/> |
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=297426 --- Comment #21 from Devin Teske <[email protected]> --- (In reply to Dan Kotowski from comment #20) procfs is insecure, it's why we have procstat. We should be endeavoring to not require procfs (/proc) mounted, but more importantly, if Linux programs were expected to require procfs, then linux_enable=YES in rc.conf (and subsequently service linux start) should be mounting it, but it does not. So far, everyone that has said (in so many words) "works for me" and "cannot replicate" have had procfs mounted. It's so much more than just "deprecated feature" it's a UX issue. Like I did not spend 3 days trying to figure out why linux-brave would not launch on 16.0-CURRENT with linux_enable=YES only to find that mounting /proc solves the issue (not before devolving into potentially patching namei in the VFS layer to address the issue of compat lookups by Linux programs outside the emul path). We should be working toward a future where linuxulator is highly polished and doesn't require insecure procfs. Yes, procfs is not just an obsolete element, it was done-away-with because of security. I'm fine keeping linprocfs for Linux binaries and linux_enable=YES absolutely brings in linprocfs to satisfy the requirements of Linux binaries. However, it should not require a crutch of procfs to satisfy any Linux program looking at /proc/self/exe in linprocfs. -- You are receiving this mail because: You are the assignee for the bug.