3 ms·
Problem is you've already received the rogue html before accessing the secure webpage. It's a shame email signing and encryption never took off.
by dm319 9y ago
Problem is you've already received the rogue html before accessing the secure webpage. It's a shame email signing and encryption never took off.
- alkonaut 9y agoThe solution assumed mail clients would be adapted to enforce this. So if you send me a forged email claiming to be from hsbc, the mail client would allow showing html content only from a https connection to somewhere on hsbc. Kind of like the same-origin policy but where the origin is the domain the email claims it came from.