Inferencium/website
1
0
Fork 0
Code Issues Activity

Fix code to conform to code style

Browse Source
This commit is contained in:
inference 2023-10-30 23:58:03 +00:00
parent b6a2c8b798
commit a13c639e3c
Signed by: inference
SSH Key Fingerprint: SHA256:FtEVfx1CmTKMy40VwZvF4k+3TC+QhCWy+EmPRg50Nnc
1 changed files with 151 additions and 132 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

283
blog/foss_is_working_against_itself.html
View File

@ -5,7 +5,7 @@
<!-- Copyright 2022 Jake Winters --> <!-- Copyright 2022 Jake Winters -->
<!-- SPDX-License-Identifier: BSD-3-Clause --> <!-- SPDX-License-Identifier: BSD-3-Clause -->
<!-- Version: 5.0.1-alpha.2 --> <!-- Version: 5.0.1-alpha.3 -->
<html> <html>
@ -29,145 +29,164 @@
<div><a href="../changelog.html">Changelog</a></div> <div><a href="../changelog.html">Changelog</a></div>
</div> </div>
<h1>Blog - #0</h1> <h1>Blog - #0</h1>
<section id="blog"> <h2>FOSS is Working Against Itself</h2>
<h2>FOSS is Working Against Itself</h2> <p class="update_date">Posted: 2022-01-27 (UTC+00:00)</p>
<p class="update_date">Posted: 2022-01-27 (UTC+00:00)</p> <p class="update_date">Updated: 2022-11-09 (UTC+00:00)</p>
<p class="update_date">Updated: 2022-11-09 (UTC+00:00)</p> <section id="toc">
<section id="toc"> <h2 id="toc"><a href="#toc">Table of Contents<a/></h2>
<h2 id="toc"><a href="#toc">Table of Contents<a/></h2> <ul>
<ul> <li><a href="#introduction">Introduction</a></li>
<li><a href="#introduction">Introduction</a></li> <li><a href="#examples">Examples</a></li>
<li><a href="#examples">Examples</a></li> <ul>
<ul> <li><a href="#examples-smartphones">Smartphones</a></li>
<li><a href="#examples-smartphones">Smartphones</a></li> </ul>
</ul> <li><a href="#solution">Solution</a></li>
<li><a href="#solution">Solution</a></li> <li><a href="#conclusion">Conclusion</a></li>
<li><a href="#conclusion">Conclusion</a></li> </ul>
</ul> </section>
</section> <section id="introduction">
<section id="introduction"> <h2 id=introduction"><a href="#introduction">Introduction</a></h2>
<h2 id=introduction"><a href="#introduction">Introduction</a></h2> <p>The world has become a dangerous, privacy invading, human rights stripping,
<p>The world has become a dangerous, privacy invading, human rights stripping, totalitarian place; totalitarian place; in order to combat this, people are joining a growing, and
in order to combat this, people are joining a growing, and dangerous, trend, which I will refer to dangerous, trend, which I will refer to in this post as the "Free and Open
in this post as the "Free and Open Source (FOSS) movement". With that stated, I will now debunk the Source (FOSS) movement". With that stated, I will now debunk the misinformation
misinformation being spread inside of this extremely flawed movement.</p> being spread inside of this extremely flawed movement.</p>
<p>The <p>The
<a href="https://en.wikipedia.org/wiki/Free_software">FOSS</a> <a href="https://en.wikipedia.org/wiki/Free_software">FOSS</a>
movement is an attempt to regain movement is an attempt to regain
<a href="https://en.wikipedia.org/wiki/Privacy">privacy</a> <a href="https://en.wikipedia.org/wiki/Privacy">privacy</a>
and and
<a href="https://en.wikipedia.org/wiki/Control_(psychology)">control</a> <a href="https://en.wikipedia.org/wiki/Control_(psychology)">control</a>
over our devices and data, but the entire concept of FOSS-only, at the current time, is over our devices and data, but the entire concept of FOSS-only, at the current
severely, and dangerously, flawed. What the FOSS community does not seem to understand is the fact time, is severely, and dangerously, flawed. What the FOSS community does not
that most FOSS software cares not about seem to understand is the fact that most FOSS software cares not about
<a href="https://en.wikipedia.org/wiki/Security">security</a>. <a href="https://en.wikipedia.org/wiki/Security">security</a>.
"Security"; keep that word in mind as you progress through this article. What is security? Security "Security"; keep that word in mind as you progress through this article. What is
is being safe and secure from adversaries and unwanted consequences; security protects our rights security? Security is being safe and secure from adversaries and unwanted
and allows us to protect ourselves. Without security, we have no protection, and without protection, consequences; security protects our rights and allows us to protect ourselves.
we have a lack of certainty of everything else, including privacy and control, which is what the Without security, we have no protection, and without protection, we have a lack
FOSS movement is seeking.</p> of certainty of everything else, including privacy and control, which is what
<p>FOSS projects rarely take security into account; they simply look at the surface level, rather the FOSS movement is seeking.</p>
than the actual <p>FOSS projects rarely take security into account; they simply look at the
<a href="https://en.wikipedia.org/wiki/Root_cause_analysis">root cause</a> surface level, rather than the actual
of the issues they are attempting to fight against. In this case, the focus is on <a href="https://en.wikipedia.org/wiki/Root_cause_analysis">root cause</a>
privacy and control. Without security mechanisms to protect the privacy features and the ability to of the issues they are attempting to fight against. In this case, the focus is
control your devices and data, it can be stripped away as if it never existed in the first place, on privacy and control. Without security mechanisms to protect the privacy
which, inevitably, leads us back to the beginning, and the cycle repeats. With this features and the ability to control your devices and data, it can be stripped
<a href="https://en.wikipedia.org/wiki/Ideology">ideology</a>, away as if it never existed in the first place, which, inevitably, leads us back
privacy and control will *never* be achieved. There is no foundation to build privacy to the beginning, and the cycle repeats. With this
or control upon. It is impossible to build a solid, freedom respecting platform on this model.</p> <a href="https://en.wikipedia.org/wiki/Ideology">ideology</a>,
</section> privacy and control will *never* be achieved. There is no foundation to build
<section id="examples"> privacy or control upon. It is impossible to build a solid, freedom respecting
<h2 id="examples"><a href="#examples">Examples</a></h2> platform on this model.</p>
<section id="examples-smartphones"> </section>
<h3 id="examples-smartphones"><a href="#examples-smartphones">Smartphones</a></h3> <section id="examples">
<p>A FOSS phone, especially so-called <h2 id="examples"><a href="#examples">Examples</a></h2>
<a href="https://en.wikipedia.org/wiki/Linux_for_mobile_devices#Smartphones">"Linux phones"</a> <section id="examples-smartphones">
are completely <h3 id="examples-smartphones"><a href="#examples-smartphones">Smartphones</a></h3>
detrimental to privacy and control, because they do not have the security necessary to enforce that <p>A FOSS phone, especially so-called
privacy. <a href="https://en.wikipedia.org/wiki/Linux_for_mobile_devices#Smartphones">"Linux phones"</a>
<a href="https://en.wikipedia.org/wiki/Bootloader_unlocking">Unlocked bootloaders</a> are completely detrimental to privacy and control, because they
prevent the device from do not have the security necessary to enforce that privacy.
<a href="https://source.android.com/docs/security/features/verifiedboot/">verifying the integrity of the boot chain</a>, <a href="https://en.wikipedia.org/wiki/Bootloader_unlocking">Unlocked bootloaders</a>
including the OS, meaning any adversary, whether a prevent the device from
stranger who happens to pick up the device, or a big tech or government entity, can simply inject <a href="https://source.android.com/docs/security/features/verifiedboot/">verifying the integrity of the boot chain</a>,
malicious code into your software and you wouldn't have any idea it was there. If that's not enough including the OS, meaning any adversary, whether a stranger who
of a backdoor for you to reconsider your position, how about the trivial happens to pick up the device, or a big tech or government
<a href="https://en.wikipedia.org/wiki/Evil_maid_attack">evil maid</a> entity, can simply inject malicious code into your software and
and data extraction attacks which could be executed on your device, without coercion? you wouldn't have any idea it was there. If that's not enough of
With Android phones, this is bad enough to completely break the privacy and control the FOSS a backdoor for you to reconsider your position, how about the
movement seeks, but "Linux phones" take it a step further by implementing barely any security, if trivial
any at all. <a href="https://en.wikipedia.org/wiki/Evil_maid_attack">evil maid</a>
<a href="https://en.wikipedia.org/wiki/Privilege_escalation">Privilege escalation</a> and data extraction attacks which could be executed on your
is trivial to achieve on any Linux system, which is the reason Linux device, without coercion? With Android phones, this is bad
<a href="https://en.wikipedia.org/wiki/Hardening_(computing)">hardening</a> enough to completely break the privacy and control the FOSS
strategies often include restricting access to the root account; if you movement seeks, but "Linux phones" take it a step further by
<a href="https://en.wikipedia.org/wiki/Rooting_(Android)">root your Android phone</a>, implementing barely any security, if any at all.
or use a "Linux phone", you've already destroyed the security model, <a href="https://en.wikipedia.org/wiki/Privilege_escalation">Privilege escalation</a>
and thus privacy and control model you were attempting to achieve. Not only are these side effects is trivial to achieve on any Linux system, which is the reason
of FOSS, so is the absolutely illogical restriction of not being able to, or making it unnecessarily Linux
difficult to, install and update critical components of the system, such as proprietary <a href="https://en.wikipedia.org/wiki/Hardening_(computing)">hardening</a>
<a href="https://en.wikipedia.org/wiki/Firmware">firmware</a>, strategies often include restricting access to the root account;
which just so happens to be almost all of them. "Linux phones" are not as free as if you
they proclaim to be.</p> <a href="https://en.wikipedia.org/wiki/Rooting_(Android)">root your Android phone</a>,
<p>You may ask "What's so bad about using or use a "Linux phone", you've already destroyed the security
<a href="https://lineageos.org/">LineageOS</a>?", model, and thus privacy and control model you were attempting to
to which I answer with "What's not bad about it?".</p> achieve. Not only are these side effects of FOSS, so is the
absolutely illogical restriction of not being able to, or making
it unnecessarily difficult to, install and update critical
components of the system, such as proprietary
<a href="https://en.wikipedia.org/wiki/Firmware">firmware</a>,
which just so happens to be almost all of them. "Linux phones"
are not as free as they proclaim to be.</p>
<p>You may ask "What's so bad about using
<a href="https://lineageos.org/">LineageOS</a>?",
to which I answer with "What's not bad about it?".
<ul> <ul>
<li>LineageOS uses <li>LineageOS uses
<a href="https://github.com/LineageOS/hudson/blob/master/lineage-build-targets">debug builds</a>, <a href="https://github.com/LineageOS/hudson/blob/master/lineage-build-targets">debug builds</a>,
not safe and secure release builds.</li> not safe and secure release builds.</li>
<li>LineageOS requires an unlocked bootloader. Even when installed on devices which support custom <li>LineageOS requires an unlocked bootloader.
Android Verified Boot (AVB) keys, the bootloader cannot be locked due to lack of the OS being Even when installed on devices which support
signed.</li> custom Android Verified Boot (AVB) keys, the
<li>LineageOS does not install critically important firmware without manual flashing, requiring users bootloader cannot be locked due to lack of the
to perform a second update to install this firmware; this likely causes users to ignore the OS being signed.</li>
notification or miss firmware updates.</li> <li>LineageOS does not install critically
important firmware without manual flashing,
requiring users to perform a second update to
install this firmware; this likely causes users
to ignore the notification or miss firmware
updates.</li>
<li>LineageOS does not implement <li>LineageOS does not implement
<a href="https://source.android.com/docs/security/features/verifiedboot/verified-boot#rollback-protection">rollback protection</a>, <a href="https://source.android.com/docs/security/features/verifiedboot/verified-boot#rollback-protection">rollback protection</a>,
meaning any adversary, from a stranger who physically picks up the device, meaning any adversary, from a stranger who
to a goverment entity remotely, can simply downgrade the OS to a previous version in order to physically picks up the device, to a goverment
exploit known entity remotely, can simply downgrade the OS to
a previous version in order to exploit known
<a href="https://en.wikipedia.org/wiki/Vulnerability_(computing)">security vulnerabilities</a>.</li> <a href="https://en.wikipedia.org/wiki/Vulnerability_(computing)">security vulnerabilities</a>.</li>
</ul> </ul>
<p>LineageOS is not the only Android OS (commonly, and incorrectly, referred to as a "ROM") with such </p>
issues, but it is one of the worst. The only things such insecure OSes can provide you are <p>LineageOS is not the only Android OS (commonly, and
customisation abilities, and a backdoor to your data. They are best suited as a development OS, not incorrectly, referred to as a "ROM") with such issues, but it is
a production OS.</p> one of the worst. The only things such insecure OSes can provide
</section> you are customisation abilities, and a backdoor to your data.
</section> They are best suited as a development OS, not a production
<section id="solution"> OS.</p>
<h2 id="solution"><a href="#solution">Solution</a></h2> </section>
<p>What can you do about this? The answer is simple; however, it does require you to use logic, </section>
fact, and evidence, not emotion, which is a difficult pill for most people to swallow. Use your <section id="solution">
adversaries' weapons against them. The only way to effectively combat the privacy invasion and lack <h2 id="solution"><a href="#solution">Solution</a></h2>
of control of our devices and data is to become a <p>What can you do about this? The answer is simple; however, it does require
<a href="https://en.wikipedia.org/wiki/Turncoat">renegade</a> you to use logic, fact, and evidence, not emotion, which is a difficult pill for
and not take sides. Yes, that means not taking sides with the closed source, most people to swallow. Use your adversaries' weapons against them. The only way
proprietary, big tech and government entities, but it also means not taking sides with any to effectively combat the privacy invasion and lack of control of our devices
FOSS entities. The only way to win this war is to take *whatever* hardware and software you can, and and data is to become a
use it tactically.</p> <a href="https://en.wikipedia.org/wiki/Turncoat">renegade</a>
<p>The only solution for phone security, privacy, and control, is to use a Google Pixel (currently, and not take sides. Yes, that means not taking sides with the closed source,
Pixel 4a-series or newer) running proprietary, big tech and government entities, but it also means not taking
<a href="https://grapheneos.org/">GrapheneOS</a>. sides with any FOSS entities. The only way to win this war is to take *whatever*
Google Pixel phones allow you complete bootloader freedom, including the hardware and software you can, and use it tactically.</p>
<a href="https://android.googlesource.com/platform/external/avb/+/master/README.md#pixel-2-and-later">ability to lock the bootloader after flashing a custom OS</a> <p>The only solution for phone security, privacy, and control, is to use a
(GrapheneOS includes a custom OS signing key to allow locking the bootloader and enabling verified Google Pixel (currently, Pixel 4a-series or newer) running
boot to prevent <a href="https://grapheneos.org/">GrapheneOS</a>.
<a href="https://en.wikipedia.org/wiki/Malware">malware</a> Google Pixel phones allow you complete bootloader freedom, including the
persistence, evil maid attacks, and boot chain <a href="https://android.googlesource.com/platform/external/avb/+/master/README.md#pixel-2-and-later">ability to lock the bootloader after flashing a custom OS</a>
<a href="https://en.wikipedia.org/wiki/Data_corruption">corruption</a>), (GrapheneOS includes a custom OS signing key to allow locking the bootloader and
<a href="https://support.google.com/nexus/answer/4457705">long device support lifecycles</a> enabling verified boot to prevent
(minimum 3 years for Pixel 4a-series to Pixel 5a, minimum 5 <a href="https://en.wikipedia.org/wiki/Malware">malware</a>
years for Pixel 6-series and newer), and persistence, evil maid attacks, and boot chain
<a href="https://source.android.com/docs/security/bulletin/pixel/">guaranteed monthly security updates</a> <a href="https://en.wikipedia.org/wiki/Data_corruption">corruption</a>),
for the entire support timeframe of the devices.</p> <a href="https://support.google.com/nexus/answer/4457705">long device support lifecycles</a>
</section> (minimum 3 years for Pixel 4a-series to Pixel 5a, minimum 5 years for Pixel
<section id="conclusion"> 6-series and newer), and
<h2 id="conclusion"><a href="#conclusion">Conclusion</a></h2> <a href="https://source.android.com/docs/security/bulletin/pixel/">guaranteed monthly security updates</a>
<p>Use what you can, and do what you can. By neglecting security, you are, even if unintentionally, for the entire support timeframe of the devices.</p>
neglecting exactly what you are trying to gain; privacy and control.</p> </section>
</section> <section id="conclusion">
<h2 id="conclusion"><a href="#conclusion">Conclusion</a></h2>
<p>Use what you can, and do what you can. By neglecting security, you are, even
if unintentionally, neglecting exactly what you are trying to gain; privacy and
control.</p>
</section> </section>
</body> </body>
</html> </html>