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

Updated FAQ (markdown)

rugk 2017-06-22 14:18:00 +02:00
parent 394bbe23a0
commit 7782e41df2
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
FAQ.md

@ -144,7 +144,7 @@ If you get a message that the signature is untrusted you may have skipped the pr
gpg: Good signature from "rugk git (software signing only) <rugk@posteo.de>" [<trust level here>]
Primary key fingerprint: ABA9 B8F6 F448 B07F D7EA 4A1A 05D4 0A63 6AFA B34D
````
* When using the git verification method, you can also easily verify the new changes, when updating PrivateBin through a `git push`. 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.
* When using the git verification method, you can also easily verify the new changes, when updating PrivateBin by "pulling" the new changes from this repo. 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 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.