> At that time, its researchers have modified Chromium to make use of Capsicum and compared how much effort was required to make use of each sandboxing mechanis

> At that time, its researchers have modified Chromium to make use of Capsicum and compared how much effort was required to make use of each sandboxing mechanism within Chromium. [..] If you’re only going to study one sandboxing mechanism in your life, it should be Capsicum. To this date, I have yet to see a better sandboxing mechanism than Capsicum. In the years since it was added, there's a reason you can count on two hands the number of programs using it in FreeBSD. Even less using it effectively, with refactoring, and not just calling cap_enter(). Capsicum Chrome has never been committed to the official FreeBSD ports tree, it was an academic research project from 17 years ago. https://github.com/rwatson/chromium-capsicum https://github.com/rwatson/chromium-capsicum https://www.freshports.org/www/chromium/ https://www.freshports.org/www/chromium/ https://cgit.freebsd.org/ports/log/www/chromium/Makefile?qt=grep&q=capsicum https://cgit.freebsd.org/ports/log/www/chromium/Makefile?qt=... No browsers on FreeBSD today use Capsicum. Compare that instead to OpenBSD, where the Chromium port has used pledge(2) since January 2016, and unveil(2) since 2018. Enabled by default. The Mozilla Firefox ports also use both pledge and unveil since 2018-2019, and this work has even been accepted upstream. https://marc.info/?l=openbsd-ports-cvs&m=145211683609002&w=2 https://marc.info/?l=openbsd-ports-cvs&m=145211683609002&w=2 https://github.com/openbsd/ports/blob/master/www/chromium/patches/patch-sandbox_policy_openbsd_sandbox_openbsd_cc https://github.com/openbsd/ports/blob/master/www/chromium/pa... https://github.com/openbsd/ports/tree/master/www/chromium/files https://github.com/openbsd/ports/tree/master/www/chromium/fi...