Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#36811 - [chromium] Enable sandboxed chromium by default
Attached to Project:
Arch Linux
Opened by Mark E. Lee (bluerider) - Friday, 06 September 2013, 15:39 GMT
Last edited by Evangelos Foutras (foutrelis) - Sunday, 08 September 2013, 09:32 GMT
Opened by Mark E. Lee (bluerider) - Friday, 06 September 2013, 15:39 GMT
Last edited by Evangelos Foutras (foutrelis) - Sunday, 08 September 2013, 09:32 GMT
|
DetailsDescription:
The current chromium.desktop file in /usr/share/applications is not called with sandboxing. For increased security, the .desktop file should probably be edited to include "--enable-seccomp-sandbox" in the exec line. |
This task depends upon
Closed by Evangelos Foutras (foutrelis)
Sunday, 08 September 2013, 09:32 GMT
Reason for closing: Not a bug
Sunday, 08 September 2013, 09:32 GMT
Reason for closing: Not a bug
"This has been replaced by the seccomp-bpf sandbox, already on by default. People who want what we now call "seccomp-legacy" can still use --enable-seccomp-sandbox."