3 ms·
The highest priority IMHO is security. Given how a targeted email can reach someone wherever they are (and spam can conceal mass exploits), frequent security u
by neilv 4y ago
The highest priority IMHO is security.
Given how a targeted email can reach someone wherever they are (and spam can conceal mass exploits), frequent security updates are the wrong mindset.
The mindset of one necessary security update should be, OMG, we messed up badly, we need to fix and mitigate, and immediately figure out how never to need another security update, ever again.
Web browsers, OTOH, are hopeless for security right now, due to monstrously big-moat standards. But email MUAs (with addressbook, calendar, and maybe chat) are a much-much simpler problem, also high-value, and maybe the place to set a good example.
If someone objects "but we will always have constant stream of security vulns, because we need these 1,000 libraries, many of which are hopeless"... maybe that's not true. Implementing email is conceptually very easy, and you don't need all that much more than conceptual to get all the benefit that users actually want from email.
(Even incoming HTML multipart content-types, which are often a nightmare of BS generated by some MS program, can be transformed to a vastly simpler and cleaned-up form, enabling a very simple and secure rendering/editing engine, with zero baggage from hopeless browser engines.)
- cookiengineer 4y agoI wish we would have more intelligent email clients, that can be as "dumb" as remembering the email addresses and geolocation routes from their senders. It literally could be a simple ASN lookup, and you would prevent 99% of targeted phishing emails. Nobody in the world uses some random domain.trade to send emails as company.com ffs. Microsoft is kind of not giving a damn about security and I dont understand why they do not invest in Outlook security that much. To me this is straight up offensive how they behave. How can it be that a VBA exploit from 2003 can still compromise an updated system in 2023?
- gnabgib 4y ago> Nobody in the world uses some random domain.trade to send emails as company.com ffs. Lots of emails come via mail delivery services.. random domains (sendgrid, amazonses, mailchimp) Many phishing attempts can be defeated by SPF[0] (the servers that are allowed to send email for this domain), DKIM[1] (proof that it was sent from a domain, and not tampered with), and DMARC[2] (what to do if the email fails SPF/DKIM). Many virus scanners, spam filters pay attention to these, but your mail service can filter mail by it too. The other piece is seeing `FROM` (just a mail header, spammers will set this to what they're pretending to be) vs `Reply-To` (if you reply this is the address the message will be sent to, for spam this is often unrelated to the content eg random1222@example.com) vs `Return-Path` (who sent the email). This is sort of like the `raw domain` vs `internationalized domain` (allowing UTF8 similar characters to spoof a domain) vs `hiding the URL` problem in the browser. [0]: https://en.wikipedia.org/wiki/Sender_Policy_Framework https://en.wikipedia.org/wiki/Sender_Policy_Framework [1]: https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail [2]: https://en.wikipedia.org/wiki/DMARC https://en.wikipedia.org/wiki/DMARC