more information
This commit is contained in:
parent
3f04dffc16
commit
af9cf17da7
@ -48,7 +48,12 @@
|
||||
app compatibility. It's focused on the research and development of privacy and
|
||||
security technology including substantial improvements to sandboxing, exploit
|
||||
mitigations and the permission model. GrapheneOS also develops various apps and
|
||||
services with a focus on privacy and security.</p>
|
||||
services with a focus on privacy and security. Vanadium is a hardened variant of the
|
||||
Chromium browser and WebView specifically built for GrapheneOS. We also have a minimal
|
||||
security-focused PDF Viewer, our hardware-based Auditor app / attestation service
|
||||
providing local and remote verification of devices and the externally developed
|
||||
Seedvault encrypted backup which was initially developed for inclusion in GrapheneOS
|
||||
is integrated.</p>
|
||||
|
||||
<p>GrapheneOS is a collaborative open source project, not a company. It's used and
|
||||
supported by a variety of companies and other organizations. It won't be closely tied
|
||||
@ -115,6 +120,23 @@
|
||||
href="https://attestation.app/tutorial">tutorial</a>. These also support other
|
||||
operating systems.</p>
|
||||
|
||||
<h2 id="never-google-services">
|
||||
<a href="#never-google-services">No Google apps or services</a>
|
||||
</h2>
|
||||
|
||||
<p>GrapheneOS will never include either Google Play Services or another implementation
|
||||
of Google services like microG. Those are not part of the Android Open Source Project
|
||||
and are not required for baseline Android compatibility. Apps designed to run on
|
||||
Android rather than only Android with bundled Google apps and services already work on
|
||||
GrapheneOS, so a huge number of both open and closed source apps are already available
|
||||
for it. Open APIs not tied to Google will continue to be implemented using open source
|
||||
providers like the Seedvault backup app. Text-to-speech, voice-to-text, non-GPS-based
|
||||
location services, geocoding, accessibility services, etc. are examples of other open
|
||||
Android APIs where we need to develop/bundle an implementation based on existing open
|
||||
source projects. Compatibility with apps depending on Google APIs / services will be
|
||||
improved by implementing them in a way that pretends Google has stopped existing and
|
||||
the servers are unavailable.</p>
|
||||
|
||||
<h2 id="history">
|
||||
<a href="#history">History</a>
|
||||
</h2>
|
||||
@ -190,6 +212,7 @@
|
||||
<h2 id="roadmap">
|
||||
<a href="#roadmap">Roadmap</a>
|
||||
</h2>
|
||||
|
||||
<p>Details on the roadmap of the project will be posted on the site in the near
|
||||
future.</p>
|
||||
<p>To get an idea of the near term roadmap, check out the
|
||||
@ -219,9 +242,11 @@
|
||||
<p>Hardware and firmware security are core parts of the project, but it's currently
|
||||
limited to research and submitting suggestions and bug reports upstream. In the long
|
||||
term, the project will need to move into the hardware space.</p>
|
||||
|
||||
<h2 id="device-support">
|
||||
<a href="/faq#device-support">Device support</a>
|
||||
</h2>
|
||||
|
||||
<p>See <a href="/faq#device-support">the FAQ section on device support</a>.</p>
|
||||
</div>
|
||||
<footer>
|
||||
|
Loading…
x
Reference in New Issue
Block a user