3 ms·

There's one way I know to stop that. Ipfs. Its immutable, for a given key. And its easy to see what an IPNS link points to. It may not be a way to verify, but

• dvdkhlng 9y ago
  The only real antidote against unauthorized access is using end-to-end encryption between email's sender and recipient(s), via PGP/GPG or S/MIME. Unfortunately this requires the sender's cooperation. As long as the sender does not cooperate, there will always be some leg of the communication path that is vulnerable.
  • crankylinuxuser 9y ago
    Indeed. But that problem has been to "Show clients how to install the relevant plugins, make their certs, and then appropriately use certs." That's been error-prone since the beginning with PGPMail and PGPphone. That's why this was switched to doing it in a webapp, to streamline the process and remove user error out of the equation. There's one problem, and that the owner of the script can change it to a bad one that does X. With an immutable data structure, like what IPFS uses, can provide that chain of custody with a script they make that simplifies PGP usage, while still maintaining "We didn't change anything" - and you can prove that.