Inferencium/website
1
0
Fork 0
Code Issues Activity

Properly indent Recommendations section.

Browse Source
This commit is contained in:
inference 2023-04-30 21:29:01 +01:00
parent ef04b6f8ac
commit a90a2d83f5
Signed by: inference
SSH Key Fingerprint: SHA256:9Pl0nZ2UJacgm+IeEtLSZ4FOESgP1eKCtRflfPfdX9M
1 changed files with 383 additions and 312 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

695
about.html
View File

@ -5,7 +5,7 @@
<!-- Copyright 2022 Jake Winters -->
<!-- SPDX-License-Identifier: BSD-3-Clause-Clear -->
<!-- Version: 4.3.0.83 -->
<!-- Version: 4.3.0.84 -->
<html>
@ -340,320 +340,391 @@
<br>
<br>
<h2 id="recommendations"><a href="#recommendations" class="h2"
>Recommendations</a></h2>
<br>
<!-- Hardware I recommend as production hardware. -->
<h3 id="hardware"><a href="#hardware" class="h3"
>Hardware</a></h3>
<br>
<h4 id="hdw-smartphone"><a href="#hdw-smartphone" class="h4"
>Smartphone</a></h4>
<div style="overflow-x:auto;">
<table>
<tr>
<td class="table-title">Type</td>
<td class="table-title">Hardware</td>
<td class="table-title">Description</td>
<td class="table-title">Source model<br>
<h2 id="recommendations"><a href="#recommendations" class="h2"
>Recommendations</a></h2>
<br>
<!-- Hardware I recommend as production hardware. -->
<h3 id="hardware"><a href="#hardware" class="h3"
>Hardware</a></h3>
<br>
<h4 id="hdw-smartphone"><a href="#hdw-smartphone" class="h4"
>Smartphone</a></h4>
<div style="overflow-x:auto;">
<table>
<tr>
<td class="table-title">Type</td>
<td class="table-title">Hardware</td>
<td class="table-title">Description</td>
<td class="table-title">Source model<br>
<br>
(License - SPDX)</td>
</tr>
<tr>
<td class="table-main">Smartphone</td>
<td class="table-main"><img src="asset/img/google-
pixel_6.png"
width="100px" height="100px"/><br>
<br>
Google Pixel</td>
<td>Google Pixel devices are the best Android devices
available on the market for
<a class="body-link" href="https://security.googleblog
.com/2021/10/pixel-6-setting-new-standard-for-mobile
.html"
>security and privacy</a>.<br>
<br>
They allow locking the bootloader with a
<a class="body-link" href="https://android.googlesource
.com/platform/external/avb/+/master/README.md#pixel-2-
and-later"
>custom Android Verified Boot (AVB) key</a> in order to
preserve security and privacy features when installing a
custom operating system, such as <a class="body-link"
href="https://source.android.com/docs/security/features/
verifiedboot/"
>verified boot</a> which verifies that the OS has not
been corrupted or tampered with, and
<a class="body-link" href="https://source.android.com/
docs/security/features/verifiedboot/verified-boot
#rollback-protection"
>rollback protection</a> which prevents an adversary
from rolling back the OS or firmware version to a
previous version with known security vulnerabilities.<br>
<br>
They also include a
<a class="body-link" href="https://developer.android
.com/training/articles/keystore#HardwareSecurityModule"
>hardware security module</a> (Titan M2, improving on
the previous generation <a class="body-link"
href="https://security.googleblog.com/2018/10/building-
titan-better-security-through.html"
>Titan M</a>) which is extremely resistant to both
remote and physical attacks due to being completely
isolated from the rest of the system, including the
operating system. Titan M2 ensures that the device
cannot be remotely compromised by requiring the side
buttons of the device to be physically pressed for some
sensitive operations. Titan M2 also takes the role of
<a class="body-link" href="https://source.android.com/
docs/security/best-practices/hardware#strongbox-
keymaster"
>Android StrongBox Keymaster</a>,
a <a class="body-link" href="https://source.android.com/
docs/security/features/keystore"
>hardware-backed Keystore</a> containing sensitive user
keys which are unavailable to the OS or apps running on
it without authorisation from Titan M2 itself.
<a class="body-link" href="https://android-developers
.googleblog.com/2018/05/insider-attack-resistance.html"
>Insider attack resistance</a> ensures that Titan M2
firmware can be flashed only if the user PIN/password is
already known, making it impossible to backdoor the
device without already knowing these secrets.<br>
<br>
Google Pixel device kernels are compiled with
<a class="body-link" href="https://android-developers
.googleblog.com/2018/10/control-flow-integrity-in-
android-kernel.html"
>forward-edge control-flow integrity</a> and
<a class="body-link" href="https://security.googleblog
.com/2019/10/protecting-against-code-reuse-in-linux_30
.html"
>backward-edge control-flow integrity</a> to prevent
code reuse attacks against the kernel. MAC address
randomisation is
<a class="body-link" href="https://android-developers
.googleblog.com/2017/04/changes-to-device-identifiers-in
.html"
>implemented well, along with minimal probe requests and
randomised initial sequence numbers</a>.<br>
<br>
Google releases
<a class="body-link" href="https://source.android.com/
docs/security/bulletin/pixel/"
>guaranteed monthly security updates</a>, ensuring
Google Pixel devices are up-to-date and quickly
protected against security vulnerabilities.<br>
<br>
Pixel 6-series and 7-series devices are a large
improvement over the already very secure and private
previous generation Pixel devices. They replace
ARM-based Titan M with RISC-V-based Titan M2, reducing
trust by removing ARM from the equation. Titan M2 is
more resiliant to attacks than Titan M, and is
<a class="body-link" href="https://www.tuv-nederland.nl/
assets/files/cerfiticaten/2022/09/nscib-cc-22-0228971-
cert-final.pdf"
>AVA_VAN.5 certified</a>, the highest level of
vulnerability assessment. Google's in-house Tensor SoC
includes Tensor Security Core, further improving device
security.<br>
<br>
Pixel 6-series and 7-series devices are supported for a
<a class="body-link" href="https://support.google.com/
nexus/answer/4457705#zippy=%2Cpixel-and-later"
>minimum of 5 years from launch</a>, an increase from
previous generations'
<a class="body-link" href="https://support.google.com/
nexus/answer/4457705#zippy=%2Cpixel-xl-a-a-g-and-a-g"
>support lifecycles of 3 years</a>.</td>
</tr>
</table>
</div>
<br>
<br>
<!-- Software I recommend as production software. -->
<h3 id="software"><a href="#software" class="h3"
>Software</a></h3>
<br>
<h4 id="sfw-desktop"><a href="#sfw-desktop" class="h4"
>Desktop</a></h4>
<div style="overflow-x:auto;">
<table>
<tr>
<td class="table-title">Type</td>
<td class="table-title">Software</td>
<td class="table-title">Description</td>
<td class="table-title">Source model<br>
<br>
(License - SPDX)</td>
</tr>
<tr>
<td class="table-main">Operating system</td>
<td class="table-main"><img src="asset/img/logo-
gentoo_linux.png" width="100px" height="100px"/><br>
<br>
Gentoo Linux</td>
<td><a class="body-link" href="https://www.gentoo.org/"
>Gentoo Linux</a> is a highly modular, source-based
Linux-based operating system which allows vast
customisation to tailor the operating system to suit
your specific needs. There are many advantages to such
an operating system, with the most notable being the
ability to optimise the software for security, privacy,
performance, or power usage; however, there are
effectively unlimited other use cases, or a combination
of multiple use cases.<br>
<br>
I have focused on security hardening and privacy
hardening, placing performance below those aspects,
although my system is still very performant. Some of the
hardening I apply includes
<a class="body-link" href="https://en.wikipedia.org/
wiki/Buffer_overflow_protection"
>stack protection</a>,
<a class="body-link" href="https://en.wikipedia.org/
wiki/Integer_overflow"
>signed integer overflow wrapping</a>, and GrapheneOS'
<a class="body-link" href="https://github.com/
GrapheneOS/hardened_malloc/"
>hardened_malloc</a> memory allocator.<br>
<br>
You can find my personal Gentoo Linux configurations in
my personal
<a class="body-link" href="https://git.inferencium.net/
inference/cfg/"
>configuration respository</a>.</td>
<td class="table-main">Open source<br>
<br>
(GPL-2.0-only)</td>
</tr>
<tr>
<td class="table-main">Web browser</td>
<td class="table-main"><img src="asset/img/logo-chromium
.png" width="100px" height="100px"/><br>
<br>
Chromium</td>
<td><a class="body-link" href="https://chromium.org/"
>Chromium</a> is a highly secure web browser which is
often ahead of other web browsers in security aspects.
It has a dedicated security team and a very impressive
<a class="body-link" href="https://www.chromium.org/
Home/chromium-security/brag-sheet/"
>security brag sheet</a>.
Chromium's security features include a strong
<a class="body-link" href="https://code.google.com/p/
chromium/wiki/LinuxSandboxing"
>multi-layer sandbox</a>,
strong <a class="body-link" href="https://www.chromium
.org/Home/chromium-security/site-isolation"
>site isolation</a>,
<a class="body-link" href="https://www.chromium.org/
Home/chromium-security/binding-integrity"
>Binding Integrity</a> memory hardening, and
<a class="body-link" href="https://www.chromium.org/
developers/testing/control-flow-integrity/"
>control-flow integrity (CFI)</a>.</td>
<td class="table-main">Open source<br>
<br>
(BSD-3-Clause)</td>
</tr>
</table>
</div>
<br>
(License - SPDX)</td>
</tr>
<tr>
<td class="table-main">Smartphone</td>
<td class="table-main"><img src="asset/img/google-pixel_6.png"
width="100px" height="100px"/><br>
<h4 id="sfw-smartphone"><a href="#sfw-smartphone" class="h4"
>Smartphone</a></h4>
<div style="overflow-x:auto;">
<table>
<tr>
<td class="table-title">Type</td>
<td class="table-title">Software</td>
<td class="table-title">Description</td>
<td class="table-title">Source model<br>
<br>
(License - SPDX)</td>
</tr>
<tr>
<td class="table-main">Operating system</td>
<td class="table-main"><img src="asset/img/logo-
grapheneos.png" width="100px" height="100px"/><br>
<br>
GrapheneOS</td>
<td><a class="body-link" href="https://grapheneos.org/"
>GrapheneOS</a> is a security-hardened,
privacy-hardened, secure-by-default Android-based
operating system which implements extensive, systemic
security and privacy hardening to the Android Open
Source Project used as its base codebase. Its hardening
includes closing gaps for apps to access sensitive
system information, a secure app spawning feature which
avoids sharing address space layout and other secrets
AOSP's default Zygote app spawning model would share,
<a class="body-link" href="https://github.com/
GrapheneOS/kernel_gs-gs101/"
>hardened kernel</a>, hardened memory allocator
(<a class="body-link" href="https://github.com/
GrapheneOS/hardened_malloc/"
>hardened_malloc</a>) to protect against common memory
corruption vulnerabilties,
<a class="body-link" href="https://github.com/
GrapheneOS/platform_bionic/"
>hardened Bionic standard C library</a>,
<a class="body-link" href="https://github.com/
GrapheneOS/platform_system_sepolicy/"
>stricter SELinux policies</a>, and local and remote
hardware-backed attestation
(<a class="body-link" href="https://attestation.app/
about/"
>Auditor</a>) to ensure the OS has not been corrupted or
tampered with.<br>
<br>
GrapheneOS only supports
<a class="body-link" href="https://grapheneos.org/faq
#device-support"
>high security and well-supported devices</a> which
receive full support from their manufacturers, including
firmware updates, long support lifecycles, secure
hardware, and overall high security practices.<br>
<br>
For an extensive list of features GrapheneOS provides,
visit its
<a class="body-link" href="https://grapheneos.org/
features/"
>official features list</a> which provides extensive
documentation.</td>
<td class="table-main">Open source<br>
<br>
(MIT)</td>
</tr>
<tr>
<td class="table-main">Web browser</td>
<td class="table-main"><img src="asset/img/logo-vanadium
.png" width="100px" height="100px"/><br>
<br>
Vanadium</td>
<td>Vanadium is a security-hardened, privacy-hardened
Chromium-based web browser which utilises GrapheneOS'
operating system hardening to implement stronger
defenses to the already very secure Chromium web
browser. Its hardening alongside Chromium's base
security features includes
<a class="body-link" href="https://github.com/
GrapheneOS/Vanadium/blob/13/patches/0081-Implement-UI-
for-JIT-site-settings.patch"
>disabling JavaScript just-in-time (JIT) compilation by
default</a>,
<a class="body-link" href="https://github.com/
GrapheneOS/Vanadium/blob/13/patches/0051-stub-out-the-
battery-status-API.patch"
>stubbing out the battery status API to prevent abuse of
it</a>, and
<a class="body-link" href="https://github.com/
GrapheneOS/Vanadium/blob/13/patches/0084-Toggle-for-
navigating-external-URL-in-incognito.patch"
>always-on Incognito mode as an option</a>.<br>
<br>
Vanadium's source code, including its Chromium patchset,
can be found in its
<a class="body-link" href="https://github.com/
GrapheneOS/Vanadium/"
>official repository</a>.</td>
<td class="table-main">Open source<br>
<br>
(GPL-2.0-only)</td>
</tr>
<tr>
<td class="table-main">Messenger</td>
<td class="table-main"><img src="asset/img/logo-molly
.png" width="100px" height="100px"><br>
<br>
Molly</td>
<td><a class="body-link" href="https://molly.im/"
>Molly</a> is a security-hardened, privacy-hardened
<a class="body-link" href="https://signal.org/"
>Signal</a> client which hardens Signal by using a
variety of
<a class="body-link" href="https://github.com/mollyim/
mollyim-android#features"
>unique features</a>, allowing
<a class="body-link" href="https://github.com/mollyim/
mollyim-android/wiki/Data-Encryption-At-Rest"
>locking the database when not in use</a>, and
<a class="body-link" href="https://github.com/mollyim/
mollyim-android/blob/
a81ff7d120adc9d427be17239107343146bad704/app/src/main/
java/org/thoughtcrime/securesms/crypto/MasterSecretUtil
.java#L91"
>utilising Android StrongBox</a> to protect user keys
using the device's hardware security module.<br>
<br>
Molly is available in
<a class="body-link" href="https://github.com/mollyim/
mollyim-android#free-and-open-source"
>2 flavours</a>:<br>
<ul>
<li>Molly, which includes the same
proprietary Google code as Signal to
support more features.</li>
<br>
<li>Molly-FOSS, which removes the
proprietary Google code to provide an
entirely open-source client.</li>
</ul>
</td>
<td class="table-main">Open source<br>
<br>
(GPL-3.0-only)</td>
</tr>
<tr>
<td class="table-main">Messenger</td>
<td class="table-main"><img src="asset/img/logo-
conversations.png" width="100px" height="100px"><br>
<br>
Conversations</td>
<td><a class="body-link" href="https://conversations
.im/"
>Conversations</a> is a well-designed Android
<a class="body-link" href="https://xmpp.org/"
>XMPP</a> client which serves as the de facto XMPP
reference client and has great usability.</td>
<td class="table-main">Open source<br>
<br>
(GPL-3.0-only)</td>
</tr>
</table>
</div>
<br>
Google Pixel</td>
<td>Google Pixel devices are the best Android devices available on the market for
<a class="body-link" href="https://security.googleblog.com/2021/10/
pixel-6-setting-new-standard-for-mobile.html"
>security and privacy</a>.<br>
<br>
They allow locking the bootloader with a
<a class="body-link" href="https://android.googlesource.com/platform/external/avb/+/
master/README.md#pixel-2-and-later"
>custom Android Verified Boot (AVB) key</a> in order to preserve security and privacy
features when installing a custom operating system, such as
<a class="body-link" href="https://source.android.com/docs/security/features/
verifiedboot/"
>verified boot</a> which verifies that the OS has not been corrupted or tampered with,
and
<a class="body-link" href="https://source.android.com/docs/security/features/
verifiedboot/verified-boot#rollback-protection"
>rollback protection</a> which prevents an adversary from rolling back the OS or
firmware version to a previous version with known security vulnerabilities.<br>
<br>
They also include a
<a class="body-link" href="https://developer.android.com/training/articles/
keystore#HardwareSecurityModule"
>hardware security module</a> (Titan M2, improving on the previous generation
<a class="body-link" href="https://security.googleblog.com/2018/10/
building-titan-better-security-through.html"
>Titan M</a>) which is extremely resistant to both remote and physical attacks due to
being completely isolated from the rest of the system, including the operating system.
Titan M2 ensures that the device cannot be remotely compromised by requiring the side
buttons of the device to be physically pressed for some sensitive operations. Titan M2
also takes the role of
<a class="body-link" href="https://source.android.com/docs/security/best-practices/
hardware#strongbox-keymaster"
>Android StrongBox Keymaster</a>,
a <a class="body-link" href="https://source.android.com/docs/security/features/keystore"
>hardware-backed Keystore</a> containing sensitive user keys which are unavailable to
the OS or apps running on it without authorisation from Titan M2 itself.
<a class="body-link" href="https://android-developers.googleblog.com/2018/05/
insider-attack-resistance.html"
>Insider attack resistance</a> ensures that Titan M2 firmware can be flashed only if the
user PIN/password is already known, making it impossible to backdoor the device without
already knowing these secrets.<br>
<br>
Google Pixel device kernels are compiled with
<a class="body-link" href="https://android-developers.googleblog.com/2018/10/
control-flow-integrity-in-android-kernel.html"
>forward-edge control-flow integrity</a> and
<a class="body-link" href="https://security.googleblog.com/2019/10/
protecting-against-code-reuse-in-linux_30.html"
>backward-edge control-flow integrity</a> to prevent code reuse attacks against the
kernel. MAC address randomisation is
<a class="body-link" href="https://android-developers.googleblog.com/2017/04/
changes-to-device-identifiers-in.html"
>implemented well, along with minimal probe requests and randomised initial sequence
numbers</a>.<br>
<br>
Google releases
<a class="body-link" href="https://source.android.com/docs/security/bulletin/pixel/"
>guaranteed monthly security updates</a>, ensuring Google Pixel devices are up-to-date
and quickly protected against security vulnerabilities.<br>
<br>
Pixel 6-series and 7-series devices are a large improvement over the already very
secure and private previous generation Pixel devices. They replace ARM-based Titan M
with RISC-V-based Titan M2, reducing trust by removing ARM from the equation. Titan M2
is more resiliant to attacks than Titan M, and is
<a class="body-link" href="https://www.tuv-nederland.nl/assets/files/cerfiticaten/2022/
09/nscib-cc-22-0228971-cert-final.pdf"
>AVA_VAN.5 certified</a>, the highest level of vulnerability assessment. Google's
in-house Tensor SoC includes Tensor Security Core, further improving device security.<br>
<br>
Pixel 6-series and 7-series devices are supported for a
<a class="body-link" href="https://support.google.com/nexus/answer/
4457705#zippy=%2Cpixel-and-later"
>minimum of 5 years from launch</a>, an increase from previous generations'
<a class="body-link" href="https://support.google.com/nexus/answer/
4457705#zippy=%2Cpixel-xl-a-a-g-and-a-g"
>support lifecycles of 3 years</a>.</td>
</tr>
</table>
</div>
<br>
<br>
<!-- Software I recommend as production software. -->
<h3 id="software"><a href="#software" class="h3"
>Software</a></h3>
<br>
<h4 id="sfw-desktop"><a href="#sfw-desktop" class="h4"
>Desktop</a></h4>
<div style="overflow-x:auto;">
<table>
<tr>
<td class="table-title">Type</td>
<td class="table-title">Software</td>
<td class="table-title">Description</td>
<td class="table-title">Source model<br>
<br>
(License - SPDX)</td>
</tr>
<tr>
<td class="table-main">Operating system</td>
<td class="table-main"><img src="asset/img/logo-gentoo_linux.png"
width="100px" height="100px"/><br>
<br>
Gentoo Linux</td>
<td><a class="body-link" href="https://www.gentoo.org/"
>Gentoo Linux</a> is a highly modular, source-based Linux-based operating system which
allows vast customisation to tailor the operating system to suit your specific needs.
There are many advantages to such an operating system, with the most notable being the
ability to optimise the software for security, privacy, performance, or power usage;
however, there are effectively unlimited other use cases, or a combination of multiple
use cases.<br>
<br>
I have focused on security hardening and privacy hardening, placing performance below
those aspects, although my system is still very performant. Some of the hardening I
apply includes
<a class="body-link" href="https://en.wikipedia.org/wiki/Buffer_overflow_protection"
>stack protection</a>,
<a class="body-link" href="https://en.wikipedia.org/wiki/Integer_overflow"
>signed integer overflow wrapping</a>, and GrapheneOS'
<a class="body-link" href="https://github.com/GrapheneOS/hardened_malloc/"
>hardened_malloc</a> memory allocator.<br>
<br>
You can find my personal Gentoo Linux configurations in my personal
<a class="body-link" href="https://git.inferencium.net/inference/cfg/"
>configuration respository</a>.</td>
<td class="table-main">Open source<br>
<br>
(GPL-2.0-only)</td>
</tr>
<tr>
<td class="table-main">Web browser</td>
<td class="table-main"><img src="asset/img/logo-chromium.png"
width="100px" height="100px"/><br>
<br>
Chromium</td>
<td><a class="body-link" href="https://chromium.org/"
>Chromium</a> is a highly secure web browser which is often ahead of other web browsers
in security aspects. It has a dedicated security team and a very impressive
<a class="body-link" href="https://www.chromium.org/Home/chromium-security/brag-sheet/"
>security brag sheet</a>.
Chromium's security features include a strong
<a class="body-link" href="https://code.google.com/p/chromium/wiki/LinuxSandboxing"
>multi-layer sandbox</a>,
strong <a class="body-link" href="https://www.chromium.org/Home/chromium-security/
site-isolation"
>site isolation</a>,
<a class="body-link" href="https://www.chromium.org/Home/chromium-security/
binding-integrity"
>Binding Integrity</a> memory hardening, and
<a class="body-link" href="https://www.chromium.org/developers/testing/
control-flow-integrity/"
>control-flow integrity (CFI)</a>.</td>
<td class="table-main">Open source<br>
<br>
(BSD-3-Clause)</td>
</tr>
</table>
</div>
<br>
<h4 id="sfw-smartphone"><a href="#sfw-smartphone" class="h4"
>Smartphone</a></h4>
<div style="overflow-x:auto;">
<table>
<tr>
<td class="table-title">Type</td>
<td class="table-title">Software</td>
<td class="table-title">Description</td>
<td class="table-title">Source model<br>
<br>
(License - SPDX)</td>
</tr>
<tr>
<td class="table-main">Operating system</td>
<td class="table-main"><img src="asset/img/logo-grapheneos.png"
width="100px" height="100px"/><br>
<br>
GrapheneOS</td>
<td><a class="body-link" href="https://grapheneos.org/"
>GrapheneOS</a> is a security-hardened, privacy-hardened, secure-by-default
Android-based operating system which implements extensive, systemic security and privacy
hardening to the Android Open Source Project used as its base codebase. Its hardening
includes closing gaps for apps to access sensitive system information, a secure app
spawning feature which avoids sharing address space layout and other secrets AOSP's
default Zygote app spawning model would share,
<a class="body-link" href="https://github.com/GrapheneOS/kernel_gs-gs101/"
>hardened kernel</a>, hardened memory allocator
(<a class="body-link" href="https://github.com/GrapheneOS/hardened_malloc/"
>hardened_malloc</a>) to protect against common memory corruption vulnerabilties,
<a class="body-link" href="https://github.com/GrapheneOS/platform_bionic/"
>hardened Bionic standard C library</a>,
<a class="body-link" href="https://github.com/GrapheneOS/platform_system_sepolicy/"
>stricter SELinux policies</a>, and local and remote hardware-backed attestation
(<a class="body-link" href="https://attestation.app/about/"
>Auditor</a>) to ensure the OS has not been corrupted or tampered with.<br>
<br>
GrapheneOS only supports
<a class="body-link" href="https://grapheneos.org/faq#device-support"
>high security and well-supported devices</a> which receive full support from their
manufacturers, including firmware updates, long support lifecycles, secure hardware, and
overall high security practices.<br>
<br>
For an extensive list of features GrapheneOS provides, visit its
<a class="body-link" href="https://grapheneos.org/features/"
>official features list</a> which provides extensive documentation.</td>
<td class="table-main">Open source<br>
<br>
(MIT)</td>
</tr>
<tr>
<td class="table-main">Web browser</td>
<td class="table-main"><img src="asset/img/logo-vanadium.png"
width="100px" height="100px"/><br>
<br>
Vanadium</td>
<td>Vanadium is a security-hardened, privacy-hardened Chromium-based web browser which
utilises GrapheneOS' operating system hardening to implement stronger defenses to the
already very secure Chromium web browser. Its hardening alongside Chromium's base
security features includes
<a class="body-link" href="https://github.com/GrapheneOS/Vanadium/blob/13/patches/
0081-Implement-UI-for-JIT-site-settings.patch"
>disabling JavaScript just-in-time (JIT) compilation by default</a>,
<a class="body-link" href="https://github.com/GrapheneOS/Vanadium/blob/13/patches/
0051-stub-out-the-battery-status-API.patch"
>stubbing out the battery status API to prevent abuse of it</a>, and
<a class="body-link" href="https://github.com/GrapheneOS/Vanadium/blob/13/patches/
0084-Toggle-for-navigating-external-URL-in-incognito.patch"
>always-on Incognito mode as an option</a>.<br>
<br>
Vanadium's source code, including its Chromium patchset, can be found in its
<a class="body-link" href="https://github.com/GrapheneOS/Vanadium/"
>official repository</a>.</td>
<td class="table-main">Open source<br>
<br>
(GPL-2.0-only)</td>
</tr>
<tr>
<td class="table-main">Messenger</td>
<td class="table-main"><img src="asset/img/logo-molly.png"
width="100px" height="100px"><br>
<br>
Molly</td>
<td><a class="body-link" href="https://molly.im/"
>Molly</a> is a security-hardened, privacy-hardened
<a class="body-link" href="https://signal.org/"
>Signal</a> client which hardens Signal by using a variety of
<a class="body-link" href="https://github.com/mollyim/mollyim-android#features"
>unique features</a>, allowing
<a class="body-link" href="https://github.com/mollyim/mollyim-android/wiki/
Data-Encryption-At-Rest"
>locking the database when not in use</a>, and
<a class="body-link" href="https://github.com/mollyim/mollyim-android/blob/
a81ff7d120adc9d427be17239107343146bad704/app/src/main/java/org/thoughtcrime/securesms/
crypto/MasterSecretUtil.java#L91"
>utilising Android StrongBox</a> to protect user keys using the device's hardware
security module.<br>
<br>
Molly is available in
<a class="body-link" href="https://github.com/mollyim/
mollyim-android#free-and-open-source"
>2 flavours</a>:<br>
<ul>
<li>Molly, which includes the same proprietary Google code as Signal to support
more features.</li>
<br>
<li>Molly-FOSS, which removes the proprietary Google code to provide an
entirely open-source client.</li>
</ul></td>
<td class="table-main">Open source<br>
<br>
(GPL-3.0-only)</td>
</tr>
<tr>
<td class="table-main">Messenger</td>
<td class="table-main"><img src="asset/img/logo-conversations.png"
width="100px" height="100px"><br>
<br>
Conversations</td>
<td><a class="body-link" href="https://conversations.im/"
>Conversations</a> is a well-designed Android
<a class="body-link" href="https://xmpp.org/"
>XMPP</a> client which serves as the de facto XMPP reference client and has great
usability.</td>
<td class="table-main">Open source<br>
<br>
(GPL-3.0-only)</td>
</tr>
</table>
</div>
<br>
<br>
<h3 id="music"><a href="#music" class="h3"
>Music</a></h3>