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

explain why it can make sense to skip signify

Browse Source
This commit is contained in:
Daniel Micay 2020-04-28 10:18:29 -04:00
parent 29bf5d4817
commit b61aa33dcc
1 changed files with 11 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
static/install.html
View File

@ -147,15 +147,20 @@ Installed as /home/username/downloads/platform-tools/fastboot</pre>
<a href="#obtaining-signify">Obtaining signify</a> <a href="#obtaining-signify">Obtaining signify</a>
</h3> </h3>
<p>To verify the download of the OS beyond the security offered by HTTPS, you need the <p>To verify the download of the OS beyond the security offered by HTTPS, you can use
signify tool. If you don't have a way to obtain signify from a trusted package the signify tool. If you do not have a way to obtain signify from a package repository
repository, such as on Windows, skip the additional verification. This is an important you're already trusting, it does not make sense to use it. GrapheneOS releases are
step, but it only makes sense if you can chain trust from your existing OS hosted on our servers and we do not have third party mirrors. A compromised signify
install.</p> would be able to compromise your OS and the GrapheneOS download due to the lack of an
application security model on traditional operating systems. It would be worse than
not trying to verify the signatures. It's far less likely that our servers would be
compromised than someone's GitHub account or GitHub itself. You're already trusting
these installation instructions from our site, which is hosted on the same static web
server infrastructure as the releases.</p>
<p>On many distributions, signify is available via a <code>signify</code> package in <p>On many distributions, signify is available via a <code>signify</code> package in
the official repositories. On Debian-based distributions like Ubuntu, the package and the official repositories. On Debian-based distributions like Ubuntu, the package and
command name were renamed to <code>signify-openbsd</code>. Following Debian tradition, command were renamed to <code>signify-openbsd</code>. Following Debian tradition,
the <code>signify</code> package and command are an <a the <code>signify</code> package and command are an <a
href="http://signify.sourceforge.net/">unmaintained mail-related tool for generating href="http://signify.sourceforge.net/">unmaintained mail-related tool for generating
mail signatures (not cryptographic signatures) with the final 3 releases from mail signatures (not cryptographic signatures) with the final 3 releases from