10-14-2020, 02:14 PM
Web of Trust, Part 1: Concept
<div style="margin: 5px 5% 10px 5%;"><img src="https://www.sickgaming.net/blog/wp-content/uploads/2020/10/web-of-trust-part-1-concept.png" width="512" height="512" title="" alt="" /></div><div><p>Every day we rely on technologies who nobody can fully understand. Since well before the industrial revolution, complex and challenging tasks required an approach that broke out the different parts into smaller scale tasks. Each resulting in specialized knowledge used in some parts of our lives, leaving other parts to trust in skills that others had learned. This shared knowledge approach also applies to software. Even the most avid readers of this magazine, will likely not compile and validate every piece of code they run. This is simply because the world of computers is itself also too big for one person to grasp. </p>
<p> <span id="more-31899"></span> </p>
<p>Still, even though it is nearly impossible to understand everything that happens within your PC when you are using it, that does not leave you blind and unprotected. <abbr title="Free/Libre and Open Source Software, umbrella term to describe software that is both free as in speech, and open source">FLOSS</abbr> software shares trust, giving protection to all users, even if individual users can’t grasp all parts in the system. This multi-part article will discuss how this ‘Web of Trust’ works and how you can get involved.</p>
<p>But first we’ll have to take a step back and discuss the basic concepts, before we can delve into the details and the web. Also, a note before we start, security is not just about viruses and malware. Security also includes your privacy, your economic stability and your technological independence.</p>
<h2>One-Way System</h2>
<p>By their design, computers can only work and function in the most rudimentary ways of logic: <em>True</em> or <em>false</em>. <em>And</em> or <em>Or. </em>This (boolean logic) is not readily accessible to humans, therefore we must do something special. We write applications in a code that we can (reasonably) comprehend (human readable). Once completed, we turn this human readable code into a code that the computer can comprehend (machine code).</p>
<p>The step of conversion is called compilation and/or building, and it’s a one-way process. Compiled code (machine code) is not really understandable by humans, and it takes special tools to study in detail. You can understand small chunks, but on the whole, an entire application becomes a black box. </p>
<p>This subtle difference shifts power. Power, in this case being the influence of one person over another person. The person who has written the human-readable version of the application and then releases it as compiled code to use by others, knows all about what the code does, while the end user knows a very limited scope. When using (software) in compiled form, it is impossible to know for certain what an application is intended to do, unless the original human readable code can be viewed. </p>
<h2><strong>The Nature of Power</strong></h2>
<p>Spearheaded by Richard Stallman, this shift of power became a point of concern. This discussion started in the 1980s, for this was the time that computers left the world of academia and research, and entered the world of commerce and consumers. Suddenly, that power became a source of control and exploitation.</p>
<p>One way to combat this imbalance of power, was with the concept of FLOSS software. FLOSS Software is built on <a rel="noreferrer noopener" href="https://fsfe.org/freesoftware/freesoftware.en.html" target="_blank">4-Freedoms</a>, which gives you a wide array of other ‘affiliated’ rights and guarantees. In essence, FLOSS software uses copyright-licensing as a form of moral contract, that forces software developers not to leverage the one-way power against their users. The principle way of doing this, is with the the GNU General Public Licenses, which Richard Stallman created and has since been promoting.</p>
<p>One of those guarantees, is that you can see the code that should be running on your device. When you get a device using FLOSS software, then the manufacturer should provide you the code that the device is using, as well as all instructions that you need to compile that code yourself. Then you can replace the code on the device with the version you can compile yourself. Even better, if you compare the version you have with the version on the device, you can see if the device manufacturer tried to cheat you or other customers.</p>
<p>This is where the web of Trust comes back into the picture. The Web of Trust implies that even if the vast majority of people can’t validate the workings of a device, that others can do so on their behalf. Journalists, security analysts and hobbyists, can do the work that others might be unable to do. And if they find something, they have the power to share their findings.</p>
<h2>Security by B<strong>lind </strong><strong>T</strong><strong>rust</strong></h2>
<p>This is of course, if the application and all components underneath it, are FLOSS. Proprietary software, or even software which is merely Open Source, has compiled versions that nobody can recreate and validate. Thus, you can never truly know if that software is secure. It might have a backdoor, it might sell your personal data, or it might be pushing a closed ecosystem to create a <abbr title="A vendor-lock makes a customer dependent on a vendor for products and services, unable to use another vendor without substantial switching costs.">vendor-lock</abbr>. With closed-source software, your security is as good as the company making the software is trustworthy.</p>
<p>For companies and developers, this actually creates another snare. While you might still care about your users and their security, you’re a liability:<mark class="annotation-text annotation-text-yoast" id="annotation-text-1239a1be-7f69-4b74-87fd-fcbdfdd79b6d"></mark> If a criminal can get to your official builds or supply-chain, then there is no way for anybody to discover that afterwards. An increasing number of attacks do not target users directly, but instead try to get in, by exploiting the trust the companies/developers have carefully grown.</p>
<p>You should also not underestimate pressure from outside: Governments can ask you to ignore a vulnerability, or they might even demand cooperation. Investment firms or shareholders, may also insist that you create a vendor-lock for future use. The blind trust that you demand of your users, can be used against you.</p>
<h2>Security by a Web of Trust</h2>
<p>If you are a user, FLOSS software is good because others can warn you when they find suspicious elements. You can use any FLOSS device with minimal economic risk, and there are many FLOSS developers who care for your privacy. Even if the details are beyond you, there are rules in place to facilitate trust.</p>
<p>If you are a tinkerer, FLOSS is good because with a little extra work, you can check the promises of others. You can warn people when something goes wrong, and you can validate the warnings of others. You’re also able to check individual parts in a larger picture. The libraries used by FLOSS applications, are also open for review: It’s “Trust all the way down”.</p>
<p>For companies and developers, FLOSS is also a great reassurance that your trust can’t be easily subverted. If malicious actors wish to attack your users, then any irregularity can quickly be spotted. Last but not least, since you also stand to defend your customers economic well-being and privacy, you can use that as an important selling point to customers who care about their own security.</p>
<h2>Fedora’s case</h2>
<p>Fedora embraces the concept of FLOSS and it stands strong to defend it. There are comprehensive <a href="https://fedoraproject.org/wiki/Licensing:Main?rd=Licensing" target="_blank" rel="noreferrer noopener">legal guidelines</a>, and Fedora’s principles are directly referencing the 4-Freedoms: <a href="https://docs.fedoraproject.org/en-US/project/" target="_blank" rel="noreferrer noopener">Freedom, Friends, Features, and First</a></p>
<div class="wp-block-image">
<figure class="aligncenter size-large is-resized"><img loading="lazy" src="https://www.sickgaming.net/blog/wp-content/uploads/2020/10/web-of-trust-part-1-concept.png" alt="Fedora's Foundation logo, with Freedom highlighted. Illustrative." class="wp-image-31951" width="217" height="217" /></figure>
</div>
<p>To this end, entire systems have been set up to facilitate this kind of security. Fedora works completely in the open, and any user can check the official servers. <a href="https://koji.fedoraproject.org/koji/index" target="_blank" rel="noreferrer noopener">Koji</a> is the name of the Fedora Buildsystem, and you can see every application and it’s build logs there. For added security, there is also <a href="https://bodhi.fedoraproject.org/" target="_blank" rel="noreferrer noopener">Bohdi</a>, which orchestrates the deployment of an application. Multiple people must approve it, before the application can become available.</p>
<p>This creates the Web of Trust on which you can rely. Every package in the repository goes through the same process, and at every point somebody can intervene. There are also escalation systems in place to report issues, so that issues can quickly be tackled when they occur. Individual contributors also know that they can be reviewed at every time, which itself is already enough of a precaution to dissuade mischievous thoughts.</p>
<p>You don’t have to trust Fedora (implicitly), you can get something better; trust in users like you. </p>
</div>
https://www.sickgaming.net/blog/2020/10/...1-concept/
<div style="margin: 5px 5% 10px 5%;"><img src="https://www.sickgaming.net/blog/wp-content/uploads/2020/10/web-of-trust-part-1-concept.png" width="512" height="512" title="" alt="" /></div><div><p>Every day we rely on technologies who nobody can fully understand. Since well before the industrial revolution, complex and challenging tasks required an approach that broke out the different parts into smaller scale tasks. Each resulting in specialized knowledge used in some parts of our lives, leaving other parts to trust in skills that others had learned. This shared knowledge approach also applies to software. Even the most avid readers of this magazine, will likely not compile and validate every piece of code they run. This is simply because the world of computers is itself also too big for one person to grasp. </p>
<p> <span id="more-31899"></span> </p>
<p>Still, even though it is nearly impossible to understand everything that happens within your PC when you are using it, that does not leave you blind and unprotected. <abbr title="Free/Libre and Open Source Software, umbrella term to describe software that is both free as in speech, and open source">FLOSS</abbr> software shares trust, giving protection to all users, even if individual users can’t grasp all parts in the system. This multi-part article will discuss how this ‘Web of Trust’ works and how you can get involved.</p>
<p>But first we’ll have to take a step back and discuss the basic concepts, before we can delve into the details and the web. Also, a note before we start, security is not just about viruses and malware. Security also includes your privacy, your economic stability and your technological independence.</p>
<h2>One-Way System</h2>
<p>By their design, computers can only work and function in the most rudimentary ways of logic: <em>True</em> or <em>false</em>. <em>And</em> or <em>Or. </em>This (boolean logic) is not readily accessible to humans, therefore we must do something special. We write applications in a code that we can (reasonably) comprehend (human readable). Once completed, we turn this human readable code into a code that the computer can comprehend (machine code).</p>
<p>The step of conversion is called compilation and/or building, and it’s a one-way process. Compiled code (machine code) is not really understandable by humans, and it takes special tools to study in detail. You can understand small chunks, but on the whole, an entire application becomes a black box. </p>
<p>This subtle difference shifts power. Power, in this case being the influence of one person over another person. The person who has written the human-readable version of the application and then releases it as compiled code to use by others, knows all about what the code does, while the end user knows a very limited scope. When using (software) in compiled form, it is impossible to know for certain what an application is intended to do, unless the original human readable code can be viewed. </p>
<h2><strong>The Nature of Power</strong></h2>
<p>Spearheaded by Richard Stallman, this shift of power became a point of concern. This discussion started in the 1980s, for this was the time that computers left the world of academia and research, and entered the world of commerce and consumers. Suddenly, that power became a source of control and exploitation.</p>
<p>One way to combat this imbalance of power, was with the concept of FLOSS software. FLOSS Software is built on <a rel="noreferrer noopener" href="https://fsfe.org/freesoftware/freesoftware.en.html" target="_blank">4-Freedoms</a>, which gives you a wide array of other ‘affiliated’ rights and guarantees. In essence, FLOSS software uses copyright-licensing as a form of moral contract, that forces software developers not to leverage the one-way power against their users. The principle way of doing this, is with the the GNU General Public Licenses, which Richard Stallman created and has since been promoting.</p>
<p>One of those guarantees, is that you can see the code that should be running on your device. When you get a device using FLOSS software, then the manufacturer should provide you the code that the device is using, as well as all instructions that you need to compile that code yourself. Then you can replace the code on the device with the version you can compile yourself. Even better, if you compare the version you have with the version on the device, you can see if the device manufacturer tried to cheat you or other customers.</p>
<p>This is where the web of Trust comes back into the picture. The Web of Trust implies that even if the vast majority of people can’t validate the workings of a device, that others can do so on their behalf. Journalists, security analysts and hobbyists, can do the work that others might be unable to do. And if they find something, they have the power to share their findings.</p>
<h2>Security by B<strong>lind </strong><strong>T</strong><strong>rust</strong></h2>
<p>This is of course, if the application and all components underneath it, are FLOSS. Proprietary software, or even software which is merely Open Source, has compiled versions that nobody can recreate and validate. Thus, you can never truly know if that software is secure. It might have a backdoor, it might sell your personal data, or it might be pushing a closed ecosystem to create a <abbr title="A vendor-lock makes a customer dependent on a vendor for products and services, unable to use another vendor without substantial switching costs.">vendor-lock</abbr>. With closed-source software, your security is as good as the company making the software is trustworthy.</p>
<p>For companies and developers, this actually creates another snare. While you might still care about your users and their security, you’re a liability:<mark class="annotation-text annotation-text-yoast" id="annotation-text-1239a1be-7f69-4b74-87fd-fcbdfdd79b6d"></mark> If a criminal can get to your official builds or supply-chain, then there is no way for anybody to discover that afterwards. An increasing number of attacks do not target users directly, but instead try to get in, by exploiting the trust the companies/developers have carefully grown.</p>
<p>You should also not underestimate pressure from outside: Governments can ask you to ignore a vulnerability, or they might even demand cooperation. Investment firms or shareholders, may also insist that you create a vendor-lock for future use. The blind trust that you demand of your users, can be used against you.</p>
<h2>Security by a Web of Trust</h2>
<p>If you are a user, FLOSS software is good because others can warn you when they find suspicious elements. You can use any FLOSS device with minimal economic risk, and there are many FLOSS developers who care for your privacy. Even if the details are beyond you, there are rules in place to facilitate trust.</p>
<p>If you are a tinkerer, FLOSS is good because with a little extra work, you can check the promises of others. You can warn people when something goes wrong, and you can validate the warnings of others. You’re also able to check individual parts in a larger picture. The libraries used by FLOSS applications, are also open for review: It’s “Trust all the way down”.</p>
<p>For companies and developers, FLOSS is also a great reassurance that your trust can’t be easily subverted. If malicious actors wish to attack your users, then any irregularity can quickly be spotted. Last but not least, since you also stand to defend your customers economic well-being and privacy, you can use that as an important selling point to customers who care about their own security.</p>
<h2>Fedora’s case</h2>
<p>Fedora embraces the concept of FLOSS and it stands strong to defend it. There are comprehensive <a href="https://fedoraproject.org/wiki/Licensing:Main?rd=Licensing" target="_blank" rel="noreferrer noopener">legal guidelines</a>, and Fedora’s principles are directly referencing the 4-Freedoms: <a href="https://docs.fedoraproject.org/en-US/project/" target="_blank" rel="noreferrer noopener">Freedom, Friends, Features, and First</a></p>
<div class="wp-block-image">
<figure class="aligncenter size-large is-resized"><img loading="lazy" src="https://www.sickgaming.net/blog/wp-content/uploads/2020/10/web-of-trust-part-1-concept.png" alt="Fedora's Foundation logo, with Freedom highlighted. Illustrative." class="wp-image-31951" width="217" height="217" /></figure>
</div>
<p>To this end, entire systems have been set up to facilitate this kind of security. Fedora works completely in the open, and any user can check the official servers. <a href="https://koji.fedoraproject.org/koji/index" target="_blank" rel="noreferrer noopener">Koji</a> is the name of the Fedora Buildsystem, and you can see every application and it’s build logs there. For added security, there is also <a href="https://bodhi.fedoraproject.org/" target="_blank" rel="noreferrer noopener">Bohdi</a>, which orchestrates the deployment of an application. Multiple people must approve it, before the application can become available.</p>
<p>This creates the Web of Trust on which you can rely. Every package in the repository goes through the same process, and at every point somebody can intervene. There are also escalation systems in place to report issues, so that issues can quickly be tackled when they occur. Individual contributors also know that they can be reviewed at every time, which itself is already enough of a precaution to dissuade mischievous thoughts.</p>
<p>You don’t have to trust Fedora (implicitly), you can get something better; trust in users like you. </p>
</div>
https://www.sickgaming.net/blog/2020/10/...1-concept/