WIP: first attempt at instructions #52
Conversation
| ## After the event | ||
|
|
||
| You should now have a table with a set of validated fingerprints and ids. You | ||
| can use this to now sign any of those identities that you have personally |
There was a problem hiding this comment.
Maybe highlight the words "personally validated"
| can use this to now sign any of those identities that you have personally | ||
| validated. | ||
|
|
||
| This guide is written assuming you have `gpg2` installed as `gpg` if any of |
There was a problem hiding this comment.
These instructions work on which platform?
There was a problem hiding this comment.
any with a terminal, a sh like shell (bash/zsh/PowerShell ish), and gpg 2+ installed,
There was a problem hiding this comment.
I think you should explicitly say what ios/android/windows should use
|
|
||
| I've includes a file in this repository `./keys.asc` that contains a dump of | ||
| every key that was submitted to this repository over the course of PyCon UK. | ||
| Do not sign every one of these keys: some of them you may have validated, some |
There was a problem hiding this comment.
embolden Do not sign every one of these keys
|
|
||
| For example: | ||
|
|
||
| * if you have marked a fingerprint as not `fp verified` do not sign. |
There was a problem hiding this comment.
if you have NOT marked a fingerprint as fp verified DO NOT SIGN
There was a problem hiding this comment.
Currently you have these a little out of order from unknown -> full verification. I feel that having them in order of trustiness might be more intuitive. Alternatively, maybe a diagram would be more helpful?
|
|
||
| Or search for your own key on a keyserver, you will be able to see the | ||
| signatures you have made and those that others have made in an ever expanding | ||
| web of trust! |
There was a problem hiding this comment.
Maybe we should add a feedback address like: "What would you like to have next year" or something like that?
Note, CLI only till I get my hands on a Mac OS