security/hakurei.app
security/hakurei.app
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 4 Wiki Activity

expand dynamic code loading blocking documentation

Browse Source
This commit is contained in:
Daniel Micay 2024-12-20 15:29:02 -05:00
parent f082e6f1c6
commit 5bccb7d322
1 changed files with 22 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

29
static/features.html
View File

@ -407,13 +407,28 @@
only JIT compilation in the base OS is the V8 JavaScript JIT which is only JIT compilation in the base OS is the V8 JavaScript JIT which is
disabled by default for the Vanadium browser with per-site exception disabled by default for the Vanadium browser with per-site exception
support.</li> support.</li>
<li>Prevention of dynamic native code execution via either memory or <li>Dynamic code loading for both native code or Java/Kotlin classes is
storage for the base OS including nearly all the base OS apps. For the blocked for nearly the entire base OS to prevent base OS processes. This
OS itself, only the processes involved in the OS package management works alongside verified boot to prevent base OS processes from running
system can write data to storage that can be executed and only the attacker controlled native code or Java/Kotlin code. The only exceptions
media DRM sandbox can do in-memory dynamic native code execution. The from the policy for the base OS are in-memory code loading for the media
Vanadium browser and WebView are excluded in order to support the JS DRM sandbox and the Vanadium JIT compiler being permitted. Vanadium has
JIT compiler.</li> JIT compilation disabled by default for every site and for apps using
the WebView with the exception of our PDF Viewer app. Vanadium disables
the JIT compiler by default with a per-site and per-app toggle for it
and per-process enforcement of blocking dynamic code loading implemented
with seccomp-bpf based on the per-site/per-app JIT compiler toggle.</li>
<li>Dynamic code loading for both native code or Java/Kotlin classes can
be disabled for user installed apps via 3 exploit protection toggles:
Dynamic code loading from memory, Dynamic code loading from storage and
WebView JIT. This can also be used to opt-out of the WebView JIT for our
PDF Viewer and dynamic code loading from memory for the Vanadium browser
to disable support for the per-site opt-in to JIT compilation. In order
to make the dynamic code loading toggles more usable, we show a user
facing notification when an app has dynamic code loading from memory or
storage blocked, including a file path being shown when it's blocked
from storage. This allows users to disable it for all their apps and
then enable them for the ones requiring it.</li>
<li>Filesystem access hardening</li> <li>Filesystem access hardening</li>
</ul> </ul>
</section> </section>