arno/privatebin
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Fix step number

rugk 2017-05-24 11:05:02 +02:00
parent bfdfeefb7f
commit 7b14a3e297
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
FAQ.md

@ -120,9 +120,9 @@ Here is the workflow you should use for verifying commits or tags:
Primary key fingerprint: ABA9 B8F6 F448 B07F D7EA 4A1A 05D4 0A63 6AFA B34D
````
If you get a message that the signature is untrusted you may have skipped step 2. Now you should check the fingerprint shown in the output. If no one is shown you have to check the key with `gpg --list-public-keys --fingerprint` as mentioned above.
If you get a message that the signature is untrusted you may have skipped step 3. Now you should check the fingerprint shown in the output. If no one is shown you have to check the key with `gpg --list-public-keys --fingerprint` as mentioned above.
4. For subsequent updates it is enough to just run `git pull --verify-signatures`. It will check the signatures automatically and will notify you if a commit is not signed by a trusted PGP key.
Note that if you skipped step 2 the imported key is not trusted and the command may fail too. In this case you can just do a usual `git pull` and then use the steps explained above to verify the signature.
Note that if you skipped step 3 the imported key is not trusted and the command may fail too. In this case you can just do a usual `git pull` and then use the steps explained above to verify the signature.
**Note:** The GitHub wiki is currently not signed by anyone.