Thanks Bubonic for the feedback. Will do a full test shortly and fix this if needs be, but I see the commands match previous instructions found elsewhere.
Actually I left them in there for those that want to use Debian stable (jessie or stretch) versions of TorBirdy, since those steps are still needed.
Other than the snapshot for cadamail instead of VFEmail and minor changes to the text in that section, I think we should also have a section somewhere on how to email someone who hasn’t uploaded their public key to a key server, but announces their email address and PGP public key block on their website (you see this from time to time).
You know, annoying shit like this below, which assumes people know what to do with it - a very big assumption:
-----BEGIN PGP PUBLIC KEY BLOCK-----
mQINBFUq2IoBEADmtlJ+yoHlq+tVxS34HzuGqGrGDCspDNZq8B5he25FR+3qxVANHAfb201odraTcbqW+K5WqtJJXKkZSdRbtn8ENpQp8SPnR+WamT/V1WTxJPLuEqb9uFOjHZvKEmWRlMomTcWBKlEPxaIZX9ykNNJNSJF0U4BorJSXRy0TmjQ6ST5o2LVMTVH8pRoC4LrON19tEv+bquRDmHuUAgIzeyv0tMRBZ6e4l1epWDC+6NJkG6elgzIFqx3pg33wNIQJaCnju7MwWDKfYA86UjEMeGOJBpIkAuPCqauDYLtvliJE4PLQ0wHtv1cyeWoJFCJiPV1OzAx8JHsFLP4subgOaNCSug5VCoOI62kJHMqRR0QNH4l06XTcKVUStw+LSEzuXhK+nXYm5KBA+WiR3IGzKM32JeElyhI7kHwFAcVXe4ELZbZFXqGoC1RMz3Tj9vK0bfGgiK5t5ku4cSH+hafRHYX+M4jfWOB8W807AqEhMUGMZkm1LEHmd1xRGpqJejeXJlimAhcDmPu4DJV5TMGWdSrfW7opKzCxKlEX5GWfE54R0RkgBUQZ5IiGe+lZk88XkSBTnToWo8SQRSm0vBCpYKPc0Z49EeUKWs26vhKlnocHGVPr7xr2lae6elnlmyGJBRDUhQTil4ckuJ0O8wRknJwbWPld2y6aRqISYSwARAQABtCdCb2IgQ3JvbXdlbGwgPGJvYi5jcm9td2VsbEBjb21jYXN0Lm5ldD6JAjgEEwECACIFAlUq2IoCGwMGCwkIBwMCBhUIAgkKCwQWAgMBAh4BAheAAAoJEINEbupB4akpBtUQAMYFiSUKaxYq0ggqVTZ2f+3PqFlF9nM8RFQRmtgcW89xS5EV0tFklu4U6N+o6Zhq+6DVXXRucI5J5bgTbwct4fEIKLFlFBejmc9d5CZYoekKknxxHl2+raS0mjF+JQaMEsRsB4CDueB2nFgWB6dskggDddCkzAMGzeycXfqYdzTBYFdqXAfzg3BiAnWIfemIkmWM4Lxr8ov14Ej5rTlIjOIcTldBZyv+OP+vMMAJnmJW4PaLY0+KHVT8uKanP7fLvDhxnorCspUXeIrr8sbJp8jFnwvS64XQYuz2LR0CoB0WjzJiJs+QifmWavDQ4FNQu97gVOTpFes1OM7qd0Ja24DLEIcGr+3h3ruBLZoyEANDQg5jK6gffeWRXkxNi2cU4WfUArs86QyjDwSoe2UTnmW+y6ilHbEasj0TZ3KN26DlpYkcTzmQe46oznpnoMZbkdqCI55tZCdHpGqiSmMx5PqjR9AIKM6T0gxlCvGajMthfbsbdOwDYo3OJ8YWQFGhuzs6b8I91QTrbInVZocIaiLGhdofCDygaSQks3UpoMJJLuiMy127GbKTwdeIEBYn0idLog5FMPxpxZel51Bbi3a3p3YE7J5Zw5pKPHCo167VlzygUpg1d5mcWq7ExwPwORloEm+Oj7uV30AXT5O1f2chUnvQqGxQkVvOMd7f0hFnSRgplh3xRHhboGuJwSlcJiAvLfTLLKXyKWsOsLiydUcJrCjo7bOMP18Yn8omJNemqjnvC5AI9zZ6j2S8uxyL1+0AMVUU6vNqIIc+EXu8xDEM1tGZIh63FikZoeWBp4HBkMQB4zaU79gTdLeTueuVILxHhpV6ObajsFkR83VlUYwxU+fSYFgqhXP=Tzwq
-----END PGP PUBLIC KEY BLOCK-----
I assume the correct method is (never tried it):
1. Cut and paste entire HTML PGP public key block from the browser into a file, including line of text at top and bottom.
2. Save as a plain text file e.g. “newkey.txt”
3. On the command line, run:
gpg --import newkey.txt
4. If successful, user should get a message like the following:
gpg: key F78FFE84: public key imported
gpg: Total number processed: 1
gpg: imported: 1
5. User can then check the newly imported key is listed on the keyring:
gpg --list-keys