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

add more header ids for usage in links

Browse Source
This commit is contained in:
Daniel Micay 2019-05-09 16:17:33 -04:00
parent d183c966c5
commit d95a7fe1d5
8 changed files with 25 additions and 25 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
static/build.html
View File

@ -33,7 +33,7 @@
</ul>
</nav>
<div id="content">
<h1>Build</h1>
<h1 id="build">Build</h1>
<h2 id="build-dependencies">
Build dependencies
<a href="#build-dependencies"></a>

6
static/contact.html
View File

@ -33,7 +33,7 @@
</ul>
</nav>
<div id="content">
<h1>Contact</h1>
<h1 id="contact">Contact</h1>
<p>You can contact <a href="mailto:contact@grapheneos.org">contact@grapheneos.org</a> for topics
related to GrapheneOS. The <a href="mailto:security@grapheneos.org">security@grapheneos.org</a>
address can be used for high priority security issues. The email address of
@ -43,12 +43,12 @@
which is used for official announcements. The account of the lead developer is
<a href="https://twitter.com/DanielMicay">@DanielMicay</a> and is primarily focused on
the privacy and security research/engineering work on GrapheneOS.</p>
<h2>Community</h2>
<h2 id="community">Community</h2>
<p>The main forum currently used to discuss the project is the official
<a href="https://reddit.com/r/GrapheneOS">/r/GrapheneOS subreddit</a> on Reddit.</p>
<p>The main IRC channel is #grapheneos on irc.freenode.net. The #grapheneos channel on
irc.oftc.net is an alternate channel acting as a backup for when freenode is down.</p>
<h2>Reporting issues</h2>
<h2 id="reporting-issues">Reporting issues</h2>
<ul>
<li><a href="https://github.com/GrapheneOS/os_issue_tracker/issues">OS issue tracker</a></li>
<li><a href="https://github.com/GrapheneOS/grapheneos.org/issues">grapheneos.org issue tracker</a></li>

6
static/donate.html
View File

@ -33,14 +33,14 @@
</ul>
</nav>
<div id="content">
<h1>Donate</h1>
<h2>Bitcoin</h2>
<h1 id="donate">Donate</h1>
<h2 id="bitcoin">Bitcoin</h2>
<p>You can send Bitcoin donations to the following address to support this project:</p>
<div id="bitcoin_address">
<img src="/bitcoin_address.png" alt="Bitcoin address QR code" width="160" height="160"/>
<p>3QpKs45BLXirWAgYtV1sTCbAkfUe7HByR5</p>
</div>
<h2>PayPal</h2>
<h2 id="paypal">PayPal</h2>
<p>PayPal donations can be sent to danielmicay@gmail.com. Please mention GrapheneOS in
the donation description to allow for proper record keeping, since PayPal
<a href="https://www.paypal.com/ms/smarthelp/article/can-i-have-multiple-paypal-accounts-faq762">

6
static/index.html
View File

@ -33,7 +33,7 @@
</ul>
</nav>
<div id="content">
<h1>GrapheneOS</h1>
<h1 id="grapheneos">GrapheneOS</h1>
<p>GrapheneOS is an open source privacy and security focused mobile OS with Android
app compatibility.</p>
<p>Official Releases are available on the <a href="/releases">releases page</a> and
@ -51,7 +51,7 @@
support for your own builds.</p>
<p>The sources are available via the
<a href="https://github.com/GrapheneOS/platform_manifest">manifest on GitHub</a>.</p>
<h2>Early stage of development</h2>
<h2 id="early-stage-of-development">Early stage of development</h2>
<p>GrapheneOS is a privacy / security research and engineering project that has been
under way for over 5 years. It recently became rebranded as GrapheneOS and is taking a
different direction based on obtaining funding for the research and development work
@ -67,7 +67,7 @@
applications. It will take more time to organize and deploy these resources in order
for the project to have a strong development team with proper infrastructure behind
it.</p>
<h2>Roadmap</h2>
<h2 id="roadmap">Roadmap</h2>
<p>Details on the roadmap of the project will be posted on the site in the near
future. In the long term, it aims to move beyond a hardened fork of the Android Open
Source Project. Achieving the goals requires moving away from relying the Linux kernel

18
static/install.html
View File

@ -33,8 +33,8 @@
</ul>
</nav>
<div id="content">
<h1>Install</h1>
<h2>Prerequisites</h2>
<h1 id="install">Install</h1>
<h2 id="prerequisites">Prerequisites</h2>
<p>You should have at least 2GB of free memory available.</p>
<p>You need the unlocked variant of one of the supported devices, not a locked carrier
specific variant.</p>
@ -50,20 +50,20 @@
do not have support for current devices. Very old versions of <code>fastboot</code>
from several years ago are still shipped by Linux distributions like Debian and lack
the compatibility detection of modern versions so they can soft brick devices.</p>
<h2>Enabling OEM unlocking</h2>
<h2 id="enabling-oem-unlocking">Enabling OEM unlocking</h2>
<p>OEM unlocking needs to be enabled from within the operating system.</p>
<p>Enable the developer settings menu by going to Settings ➔ System ➔ About phone and
pressing on the build number menu entry until developer mode is enabled.</p>
<p>Next, go to Settings ➔ System ➔ Advanced ➔ Developer settings and toggle on the
'Enable OEM unlocking' setting. This requires internet access on devices with Google
Play Services.</p>
<h2>Unlocking the bootloader</h2>
<h2 id="unlocking-the-bootloader">Unlocking the bootloader</h2>
<p>First, boot into the bootloader interface. You can do this by turning off the
device and then turning it on by holding both the Volume Down and Power buttons.</p>
<p>The bootloader now needs to be unlocked to allow flashing new images:</p>
<pre>fastboot flashing unlock</pre>
<p>The command needs to be confirmed on the device.</p>
<h2>Obtaining factory images</h2>
<h2 id="obtaining-factory-images">Obtaining factory images</h2>
<p>The initial install will be performed by flashing the factory images. This will
replace the existing OS installation and wipe all the existing data.</p>
<p>You can download the factory images from <a href="/releases">the releases page</a>.</p>
@ -71,7 +71,7 @@
<pre>gpg --recv-keys 65EEFE022108E2B708CBFCF7F9E712E59AF5F22A
gpg --verify blueline-factory-2019.04.01.19.zip.sig blueline-factory-2019.04.01.19.zip</pre>
<p>When this signing key is replaced, the new key will be signed with it.</p>
<h2>Flashing factory images</h2>
<h2 id="flashing-factory-images">Flashing factory images</h2>
<p>Next, extract the factory images and run the script to flash them. Note that the
<code>fastboot</code> command run by the flashing script requires a fair bit of free
space in a temporary directory, which defaults to <code>/tmp</code>:<p>
@ -86,7 +86,7 @@ TMPDIR="$PWD/tmp" ./flash-all.sh</pre>
new operating system.</p>
<p>You should now proceed to locking the bootloader before using the device as locking
wipes the data again.</p>
<h2>Locking the bootloader</h2>
<h2 id="locking-the-bootloader">Locking the bootloader</h2>
<p>Locking the bootloader is important as it enables full verified boot. It also
prevents using fastboot to flash, format or erase partitions. Verified boot will
detect modifications to any of the OS partitions (vbmeta, boot/dtbo, product, system,
@ -99,10 +99,10 @@ TMPDIR="$PWD/tmp" ./flash-all.sh</pre>
<p>The command needs to be confirmed on the device since it needs to perform a factory
reset.</p>
<p>Unlocking the bootloader again will perform a factory reset.</p>
<h2>Disabling OEM unlocking</h2>
<h2 id="disabling-oem-unlocking">Disabling OEM unlocking</h2>
<p>OEM unlocking can be disabled again in the developer settings menu within the
operating system after booting it up again.</p>
<h2>Replacing GrapheneOS with the stock OS</h2>
<h2 id="replacing-grapheneos-with-the-stock-os">Replacing GrapheneOS with the stock OS</h2>
<p>Installation of the stock OS via the stock factory images is the same process
described above. However, before locking, there's an additional step to fully revert
the device to a clean factory state on modern devices with Android Verified Boot 2.0

6
static/releases.html
View File

@ -33,7 +33,7 @@
</ul>
</nav>
<div id="content">
<h1>Releases</h1>
<h1 id="releases">Releases</h1>
<p>These releases are available as both tags in the source code repositories and
official builds.</p>
<p>The factory images are used for the initial installation and can be verified with
@ -62,7 +62,7 @@
<noscript><strong>JavaScript is required to fetch the current list of releases from
the update server.</strong></noscript>
<h2>Stable channel</h2>
<h2 id="stable-channel">Stable channel</h2>
<div id="crosshatch-stable">
<h3>Pixel 3 XL</h3>
@ -152,7 +152,7 @@
<a>OTA update url loading...</a>
</div>
<h2>Changelog</h2>
<h2 id="changelog">Changelog</h2>
<p>List of tagged releases. Snapshot releases without tags such as early releases of
the project and early device support releases are not listed.</p>

2
static/source.html
View File

@ -33,7 +33,7 @@
</ul>
</nav>
<div id="content">
<h1>Source</h1>
<h1 id="source">Source</h1>
<ul>
<li><a href="https://github.com/GrapheneOS/os_issue_tracker/issues">OS issue tracker</a></li>
<li><a href="https://github.com/GrapheneOS/grapheneos.org">Website repository and issue tracker</a></li>

4
static/usage.html
View File

@ -33,9 +33,9 @@
</ul>
</nav>
<div id="content">
<h1>Usage</h1>
<h1 id="usage">Usage</h1>
<p><strong>This page is currently a placeholder and will be filled with lots of content over time.</strong></p>
<h2>Auditor</h2>
<h2 id="auditor">Auditor</h2>
<p>See the <a href="https://attestation.app/tutorial">tutorial page on the site for the attestation sub-project</a>.</p>
</div>
<footer>