roots/wiki
1
0
Fork 0
mirror of https://github.com/PhyllomeOS/wiki.git synced 2024-12-22 05:35:22 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: update phyllomeos/comparaison

Browse Source
This commit is contained in:
lukas 2022-01-07 11:13:33 +00:00
parent f06a19c1cf
commit e08ad9252c
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
phyllomeos/comparaison.md
View File

@ -2,7 +2,7 @@
title: Comparaison
description:
published: true
date: 2022-01-07T10:56:47.689Z
date: 2022-01-07T11:13:31.045Z
tags:
editor: markdown
dateCreated: 2022-01-07T10:39:15.878Z
@ -42,6 +42,8 @@ This table is not meant to be clear-cut, or definitive.
[^3]: Take for instance the boot process, or before an operating system effectively takes control over the hardware. Major operating systems editors that are working directly with OEM integrators have a distinct advantage over editors that aren't: these major editors have almost unlimited resources, sometimes almost perfect control over hardware, and can therefore tame the underlying hardware, effectively controlling, measuring and attesting the entire boot process. To implement a user-backed root of trust on a particular hardware platform, one would need to take several extra measures, relying on something like [Heads](https://github.com/osresearch/heads) which, among other things, involves physically flashing a more open firmware to a motherboard, a complicated process. Fortunately, some hardware integrators like [Purism](https://puri.sm/) or [System76](https://system76.com/) are backing security measures straight into hardware platforms, while at the same time respecting user freedom.
> **Still undecided?** You can give Phyllome OS a try, as a live system booting off from a USB thumb drive, without impacting the existing operating system on your machine.
---
*[Go back one level](/phyllomeos/)*