use bare absolute paths for internal links
This commit is contained in:
parent
8e71d59492
commit
6a1b3041ef
@ -355,7 +355,7 @@
|
||||
<h3><a href="#updates-sideloading">Sideloading</a></h3>
|
||||
|
||||
<p>Updates can be downloaded via
|
||||
<a href="https://grapheneos.org/releases">the releases page</a> and installed via recovery
|
||||
<a href="/releases">the releases page</a> and installed via recovery
|
||||
with adb sideloading. The zip files are signed and verified by recovery, just as they
|
||||
are by the update client within the OS. This includes providing downgrade protection,
|
||||
which prevents attempting to downgrade the version. If recovery didn't enforce these
|
||||
@ -1022,11 +1022,11 @@
|
||||
enforce using Google certified operating systems. However, app developers can use
|
||||
it directly and permit other properly signed operating systems upholding the
|
||||
security model. GrapheneOS has a
|
||||
<a href="https://grapheneos.org/articles/attestation-compatibility-guide">
|
||||
detailed guide</a> for app developers on how to support GrapheneOS with the
|
||||
hardware attestation API. Direct use of the hardware attestation API provides much
|
||||
higher assurance than using SafetyNet so these apps have nothing to lose by using a
|
||||
more meaningful API and supporting a more secure OS.</p>
|
||||
<a href="/articles/attestation-compatibility-guide">detailed guide</a> for app
|
||||
developers on how to support GrapheneOS with the hardware attestation API. Direct
|
||||
use of the hardware attestation API provides much higher assurance than using
|
||||
SafetyNet so these apps have nothing to lose by using a more meaningful API and
|
||||
supporting a more secure OS.</p>
|
||||
</section>
|
||||
|
||||
<section id="app-link-verification">
|
||||
|
Loading…
x
Reference in New Issue
Block a user