Finally, Debian has ditched OpenPGP for repository signing in favor of Ed25519 with SHA512. This is a step ahead for privacy and security. You can see the article here.
As @anon123@lemmy.ml pointed out, the following issues about PGP are not specifically related to Debian article I linked.
- No authenticated encryption.
- Receiving a signed message means nothing about who sent it to you
- Usability issues with GnuPG
- Discoverability of public keys issue.
- Bad integration with emails.
- No forward secrecy.
There’s usuful documentation about it:
In my understanding E2EE is a protocol.
E2EE seems like a too generic term to be a protocol. Things like UUCP, NNTP, SMTP,IMAP4 are protocols for which RFCs exist. https://tools.ietf.org/rfc/index
Hi, E2EE it’s quite common described as protocol, even on wikipedia or here, for example. However, I understand your point. Thank you for the useful link. :)
Sorry here, but any source you provides shows E2EE as part of the name not as a name itself for the protocol.
To be exact, the first tells Signal protocol all the time or “how Signal provides E2EE” stating that E2EE is an abstract concept and not an encryption protocol.
I think this is a similar misread in a bigger situation that the people believing that LZMA (even when described by people or in the description of the name) is an algorithm, when it is a method (protocol but other kind).
It is a bigger situation because of the reasons why is being misread.
In this last source, shows the same “an E2EE Scheme of Line”. Again, E2EE as a abstract concept in a super-entity, not an encryption protocol.
Edited: maybe the issue is what you understand as protocol.
Protocol here is not the raw abstract concept, in every case the word is being specific toward the specification of an encryption scheme.
I attach a Wikipedia article that is a good basis for it https://en.m.wikipedia.org/wiki/Cryptographic_protocol
Hi, Thank you for helping me to understand. I surely look at the article you linked. :)
WTF