Live data from Hacker News

PGP Is Dead? (2018)

wired.co.uk

51–53 of 53 posts

Re: PGP Is Dead? (2018)

#51
Funny. I was incidentally reading Snowden leaks recently, published by a German media. As is known, NSA put PGP in the category “catastrophic,” often responding to requests with “no decrypt available,”

But, interestingly, it said members of intelligence agency themselves are using PGP to secure their communication!

Anyways, this is not PGP vs non-PGP debate. Rather, whether you manage your key or let a company manage the key for you. At that point, it doesn’t matter much if you use OpenSSL, PGP, etc to encrypt your data.

And PGP offers a secure and convenient way to encrypt your information on your computer from command line.

Re: PGP Is Dead? (2018)

#52
post #42
post #12

"Let's ditch open protocol X that has worked well for decades, in favour or closed protocol Y. Because of some transient issue with open protocol X, it's now time for open protocol X to die" Heard that before? It's as if if your doctor told you it's now time for you to die because you caught a cold.

Isn't the Signal Protocol an open protocol? https://signal.org/docs/ and https://en.wikipedia.org/wiki/Signal_Protocol#Implementation...

The platform (smartphone) is a proprietary, insecure black box. Lately, vendors are brining client side scanning to phones too.

With PGP, you can take your message anywhere, to any OS, client software and with any encryption key and algorithm you like, to encrypt it.

Re: PGP Is Dead? (2018)

#53
post #37

Earlier quoted context omitted.

> keys.openpgp.org? Half-dead (HKPS access not working, it seems only web is working) etc Can you be more specific? HKPS looks fine from here, and we've had no downtimes on our monitoring.

[zxspectrum@zxspectrum ~]$ gpg --refresh-keys gpg: refreshing 204 keys from hkps://keys.openpgp.org gpg: keyserver refresh failed: No keyserver available

This is likely an issue with GnuPG, respectively its dirmngr component. This can typically be fixed via `killall dirmngr`. See also https://dev.gnupg.org/T4513

For a simple check, those two commands perform exactly the same http request: > curl https://keys.openpgp.org/pks/lookup?op=get&options=mr&search... > gpg --keyserver hkps://keys.openpgp.org --recv-keys F357AA1A5B1FA42CFD9FE52A9FF2194CC09A61E8

Post reply on HN