Add a comment about a GPG warning being expected

This commit is contained in:
moneromooo-monero 2017-09-18 11:39:27 +01:00
parent abcf8c85b2
commit da2e7d937f
No known key found for this signature in database
GPG key ID: 686F07454D6CEFC3
2 changed files with 26 additions and 13 deletions

View file

@ -10905,6 +10905,19 @@ that file was properly signed by an attacker instead of moneromooo. Beware that
place any email address in a new GPG key, so the right email being shown is no guarantee.
</p>
<p>
NOTE: you will probably also see a warning like this:
</p>
<code>
gpg: WARNING: This key is not certified with a trusted signature!
</code>
<p>
That is expected, as you only told GPG to import the signature in the steps above, but not
to trust it. Look for tutorials on GPG if you want to do this, but it is not necessary here.
</p>
<p>
If you want to verify an old version of the file, you will have to retrieve the matching
signature file from git.