> More than a bit critical, but a good read all the same. Found on HN.
Although I largely share in the criticisms, I think the author made a
couple of serious mistakes.
First, RFC4880bis06 (the latest version) does a pretty good job of
bringing the crypto angle to a more modern level. There's
More than a bit critical, but a good read all the same. Found on HN.
https://latacora.micro.blog/2019/07/16/the-pgp-problem.html
HN comment thread here: https://news.ycombinator.com/item?id=20455780
-Ryan McGinnis
https://bigstormpicture.com
PGP: 5C73 8727 EE58 786A 777C 4F1D B5AA 3FA3 486E
On 16/07/2019 08:23, Wolfgang Traylor wrote:
> Try the gpg-wks-client command. It should try to automatically strip the user
> IDs. Werner Koch explained that in an old post:
> https://lists.gnupg.org/pipermail/gnupg-users/2019-February/061610.html
>
> Since my primary secret key is offline and
Thanks everybody.
> > Is there documentation somewhere how to produce the keys for both these
> > user IDs with GnuPG? (I don’t think the Python generate scripts do this
>
> I don't known about Python scripts. Kmail, GpgOL, and Enigmail do the
> publishing for you. You can also do it
On 16.07.2019 12:16, Werner Koch via Gnupg-users wrote:
So if I have two email addresses/user IDs m...@my.org and m...@my.org
associated with the same key, I cannot just export the key and publish
it, right? I have to somehow publish two different ‘stripped’ public
Sight. GnuPG handles this
On Mon, 15 Jul 2019 18:03, gnupg-users@gnupg.org said:
> So if I have two email addresses/user IDs m...@my.org and m...@my.org
> associated with the same key, I cannot just export the key and publish
> it, right? I have to somehow publish two different ‘stripped’ public
Sight. GnuPG handles
