News for hackers. Stuff that matters.
Re:Own-Mailbox, the first 100% confidential mailbox by r1ch on Monday June 29, 2015 @11:10AM (#9798541)
Compromising a page doesn't necessarily have to alter existing content. It would be easy to add a "Download Preview Build" link pointing to a trojan, add links to a fake kickstarter, etc.
Re:Own-Mailbox, the first 100% confidential mailbox by giancarlostoro on Monday June 29, 2015 @11:17AM (#9798584)
That sounds like altering existing content by adding new content btw.
Re:Own-Mailbox, the first 100% confidential mailbox by nitrogen on Monday June 29, 2015 @11:35AM (#9798721)
Yes, a MITM can do that.
Re:Own-Mailbox, the first 100% confidential mailbox by jessaustin on Monday June 29, 2015 @12:38PM (#9799168)
And could still do the exact same thing if they had TLS: get the page, add crap, and serve the result (albeit without TLS).
Re:Own-Mailbox, the first 100% confidential mailbox by 3pt14159 on Monday June 29, 2015 @01:23PM (#9799473)
You know, I've never really realized that before. It's actually a pretty huge security hole for average users, no? There should be a way to explicitly forbid non-encrypted connections on a DNS level.
Re:Own-Mailbox, the first 100% confidential mailbox by lfowles on Monday June 29, 2015 @02:00PM (#9799748)
That's roughly the purpose of HSTS, but you need to have visited the site at least once first (or in the case of popular sites, HSTS status of a site is shipped with the browser.)
Re:Own-Mailbox, the first 100% confidential mailbox by schoen on Monday June 29, 2015 @07:18PM (#9801817)
People who are encountering this for the first time might want to look at

http://www.thoughtcrime.org/software/sslstrip/

for some of the motivation!

Re:Own-Mailbox, the first 100% confidential mailbox by vacri on Monday June 29, 2015 @11:02PM (#9802656)
A technical user could reasonably be expected to look for https before downloading 'preview build' or something equally payload-ey.

Then sigh and download PuTTY anyway...