this post was submitted on 18 Jun 2024
104 points (96.4% liked)
Cybersecurity
5763 readers
230 users here now
c/cybersecurity is a community centered on the cybersecurity and information security profession. You can come here to discuss news, post something interesting, or just chat with others.
THE RULES
Instance Rules
- Be respectful. Everyone should feel welcome here.
- No bigotry - including racism, sexism, ableism, homophobia, transphobia, or xenophobia.
- No Ads / Spamming.
- No pornography.
Community Rules
- Idk, keep it semi-professional?
- Nothing illegal. We're all ethical here.
- Rules will be added/redefined as necessary.
If you ask someone to hack your "friends" socials you're just going to get banned so don't do that.
Learn about hacking
Other security-related communities [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected]
Notable mention to [email protected]
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
My initial question was did this "researcher" just discover SMTP Open Relay? Cause if so I can do the exact same thing by configuring my SMTP server to open relay then using telnet to connect to it and issue the SMTP commands directly and it will send the email as though sent from whatever email address I want. This has been a known issue with SMTP for decades at this point and can't be reliably resolved with SMTP, but since the whole world uses it for email, its probably not going away any time soon. However to mitigate it as much as possible is what DMARC DNS entries are supposed to help with, by providing assurance that the email was sent by an SMTP server allowed to send email on behalf of the domain.
I used to send people emails from themselves to demonstrate why they can't trust the "from" address when they get an e-mail.
+DKIM and SPF as long as we're naming email authentication methods.
yup, those too.