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

more indentation fixes

Browse Source
This commit is contained in:
Daniel Micay 2021-12-11 16:13:50 -05:00
parent fdab1720e7
commit 7ee2e4def4
1 changed files with 38 additions and 37 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

75
static/index.html
View File

@ -76,50 +76,51 @@
<h2 class="start"><a href="#about">About</a></h2> <h2 class="start"><a href="#about">About</a></h2>
<p>GrapheneOS is a privacy and security focused mobile OS with Android app <p>GrapheneOS is a privacy and security focused mobile OS with Android app
compatibility developed as a non-profit <a href="/source">open source</a> project. compatibility developed as a non-profit <a href="/source">open source</a>
It's focused on the research and development of privacy and security technology project. It's focused on the research and development of privacy and security
including substantial improvements to sandboxing, exploit mitigations and the technology including substantial improvements to sandboxing, exploit
permission model.</p> mitigations and the permission model.</p>
<p>GrapheneOS improves the privacy and security of the OS from the bottom up. It <p>GrapheneOS improves the privacy and security of the OS from the bottom up.
deploys technologies to mitigate whole classes of vulnerabilities and make exploiting It deploys technologies to mitigate whole classes of vulnerabilities and make
the most common sources of vulnerabilities substantially more difficult. It improves exploiting the most common sources of vulnerabilities substantially more
the security of both the OS and the apps running on it. The app sandbox and other difficult. It improves the security of both the OS and the apps running on it.
security boundaries are fortified. GrapheneOS tries to avoid impacting the user The app sandbox and other security boundaries are fortified. GrapheneOS tries
experience with the privacy and security features. Ideally, the features can be to avoid impacting the user experience with the privacy and security features.
designed so that they're always enabled with no impact on the user experience and no Ideally, the features can be designed so that they're always enabled with no
additional complexity like configuration options. It's not always feasible, and impact on the user experience and no additional complexity like configuration
GrapheneOS does add various toggles for features like the Network permission, Sensors options. It's not always feasible, and GrapheneOS does add various toggles for
permission, restrictions when the device is locked (USB peripherals, camera, quick features like the Network permission, Sensors permission, restrictions when
tiles), etc. along with more complex user-facing privacy and security features with the device is locked (USB peripherals, camera, quick tiles), etc. along with
their own UX.</p> more complex user-facing privacy and security features with their own UX.</p>
<p>The <a href="/features">features page</a> provides an overview of the substantial <p>The <a href="/features">features page</a> provides an overview of the
privacy and security improvements added by GrapheneOS to the Android Open Source substantial privacy and security improvements added by GrapheneOS to the
Project.</p> Android Open Source Project.</p>
<p>Official releases are available on the <a href="/releases">releases page</a> and <p>Official releases are available on the <a href="/releases">releases
installation instructions are on the <a href="/install/">install page</a>.</p> page</a> and installation instructions are on the <a href="/install/">install
page</a>.</p>
<p>GrapheneOS also develops various apps and services with a focus on privacy and <p>GrapheneOS also develops various apps and services with a focus on privacy
security. Vanadium is a hardened variant of the Chromium browser and WebView and security. Vanadium is a hardened variant of the Chromium browser and
specifically built for GrapheneOS. GrapheneOS also includes our minimal WebView specifically built for GrapheneOS. GrapheneOS also includes our
security-focused PDF Viewer, our hardware-based Auditor app / attestation service minimal security-focused PDF Viewer, our hardware-based Auditor app /
providing local and remote verification of devices, and the externally developed attestation service providing local and remote verification of devices, and
Seedvault encrypted backup which was initially developed for inclusion in the externally developed Seedvault encrypted backup which was initially
GrapheneOS.</p> developed for inclusion in GrapheneOS.</p>
</section> </section>
<section id="never-google-services"> <section id="never-google-services">
<h2><a href="#never-google-services">No Google apps or services</a></h2> <h2><a href="#never-google-services">No Google apps or services</a></h2>
<p>GrapheneOS will never include either Google Play services or another <p>GrapheneOS will never include either Google Play services or another
implementation of Google services like microG. It's possible to install Play implementation of Google services like microG. It's possible to install Play
services as a set of fully sandboxed apps without special privileges via our services as a set of fully sandboxed apps without special privileges via our
<a href="/usage#sandboxed-play-services">sandboxed Play services compatibility <a href="/usage#sandboxed-play-services">sandboxed Play services compatibility
layer</a>. See <a href="/faq#google-services">the FAQ section</a> for more details layer</a>. See <a href="/faq#google-services">the FAQ section</a> for more
on our plans for filling in the gaps from not shipping Play services and Google details on our plans for filling in the gaps from not shipping Play services
apps.</p> and Google apps.</p>
</section> </section>
<section id="history"> <section id="history">
@ -133,9 +134,9 @@
<section id="upstream"> <section id="upstream">
<h2><a href="#upstream">Upstream contributions</a></h2> <h2><a href="#upstream">Upstream contributions</a></h2>
<p>See <a href="/faq#upstream">the FAQ section on our upstream work</a> improving <p>See <a href="/faq#upstream">the FAQ section on our upstream work</a>
privacy and security for billions of users by getting a subset of our changes into improving privacy and security for billions of users by getting a subset of
core infrastructure projects.</p> our changes into core infrastructure projects.</p>
</section> </section>
<section id="roadmap"> <section id="roadmap">