Showing posts with tag: #pgp


OCTADE

In response to this post

Off the top of my head I can think of one alternative if metadata confidentiality or anonymity matter:

Bitmessage: https://github.com/Bitmessage/PyBitmessage

Bitmessage hides non-content metadata and uses a flood mixnet to unlink sender and receiver from eavesdropper view.

There is no alternative for email. Email clients support PGP and that's it. PGP does guarantee authenticity of a message due to digital signatures. PGP does not hide metadata about sender and receiver.

If you want truly confidential communication you have to set up a private pipeline. If you are using a public paid or free email service, you have zero confidentiality. Even if your message is encrypted, the email operators know who you are talking to.



Tags: #pgp #email #encryption #privacy

Mentions: @phlogiston@mastodon.nz


Likes: 0

Replies: 0

Boosts: 0

Guy

I was wondering ... as encryption via PGP/GnuPG is not suitable for true and ongoing end-to-end confidentiality. But what about authenticity of mails? I dislike S/MIME for its corporate nature, and via PGP/MIME is well enough supported by many (free) mail clients.

What's the or community's view on PGP for signing emails? Or what would a suitable alternative be? I haven't come across any, though.

1/2


Off the top of my head I can think of one alternative if metadata confidentiality or anonymity matter:

Bitmessage: https://github.com/Bitmessage/PyBitmessage

Bitmessage hides non-content metadata and uses a flood mixnet to unlink sender and receiver from eavesdropper view.

There is no alternative for email. Email clients support PGP and that's it. PGP does guarantee authenticity of a message due to digital signatures. PGP does not hide metadata about sender and receiver.

If you want truly confidential communication you have to set up a private pipeline. If you are using a public paid or free email service, you have zero confidentiality. Even if your message is encrypted, the email operators know who you are talking to.


by OCTADE ;

S/MIME has two problems: it’s harder to get a free certificate (Let’s Encrypt for S/MIME could really help here) and, AFAIK, it still technically is not using modern cryptographic cipher suites (e.g. no AEAD).

It would be cool to know these problems are being resolved.

FWIW in my experience S/MIME is also quite well supported in e-mail clients. Additionally due to centralized CA nature there are no questions whether the certificate is good or not.

by Wiktor Kwapisiewicz ;

Tags: #email #pgp #cryptography #security


Likes: 0

Replies: 2

Boosts: 0

Calisti πŸ³οΈβ€πŸŒˆπŸ¦‡

In response to this post

Pretty great for remote-specific πŸ” GPG commit signing configuration, too!


Tags: #git #gpg #pgp


Likes: 0

Replies: 0

Boosts: 0