2 ms·
Interesting tidbit about Chrome using POSIX_SPAWN_NP_CSM_ALL now. But I would point out that according to the open-source Chromium code base, these CPU security
by kccqzy 5y ago
Interesting tidbit about Chrome using POSIX_SPAWN_NP_CSM_ALL now. But I would point out that according to the open-source Chromium code base, these CPU security mitigation APIs offer process-wide protection rather than thread-based protection (commit message at https://source.chromium.org/chromium/chromium/src/+/46e23c8166086ef63e7d383149d4c91f30b7415e https://source.chromium.org/chromium/chromium/src/+/46e23c81... )
Some more digging shows that Chrome started using a weaker version of CSM, TCSM (thread CSM I assume) two years ago in NaCl: https://source.chromium.org/chromium/_/chromium/native_client/src/native_client.git/+/4744a43b6fc4aaa5230541efad113b3cd86ea0f8 https://source.chromium.org/chromium/_/chromium/native_clien...
Firefox of course uses TCSM too: https://hg.mozilla.org/mozilla-central/rev/cd1ccb74af7c https://hg.mozilla.org/mozilla-central/rev/cd1ccb74af7c And so does Safari: https://trac.webkit.org/changeset/244233/webkit https://trac.webkit.org/changeset/244233/webkit
I hope this at least somewhat assuages the fears of people who prefer Firefox or Safari over Chrome.