Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either [email protected] or [email protected].
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email [email protected]. For other questions check our partnered communities list, or use the search function.
6) No US Politics.
Please don't post about current US Politics. If you need to do this, try [email protected] or [email protected]
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
I've seen something about emails being signed and stuff like that. I guess I'm out of the loop. I had a coworker once PGP sign their emails and it would have a signature at the bottom that I (and probably everyone else) ignored.
Why couldn't email just be encrypted ala https? Make a TLS connection, send message, end, move on. Or really just make TLS connection, POST a message, move on.
I know it's more complicated than that but not by much really.. why haven't we just made a new secure standard based on https?
Your email likely is already delivered over a TLS or SMARTLS protected channel. That's not the (only) problem PGP addresses. PGP provides message authentication in addition to encryption.
To take your colleague as an example, his email was cryptographically signed by him. A function that requires his private key, and possibly a passphrase to unlock the key. The signature includes a hash of the message, and requires that private key to generate. On your end, your client hashes the message again and compares the signature. If it isn't identical, someone has tampered with the content. Presuming you met up ahead of time in person or through another trusted channel, and shared public keys, seeing the valid signature also gives you confidence that this email was actually written by the person you expect, and not anyone else with access to their device or account. (If the senders key is still safe anyway.)
It is. When you send an email a startls session is created between the servers as its a point to point protocol. That session is then used to send the message. You can downgrade to plain text which is where the problem lies.