4 ms·
I don't think that's helpful. Perhaps more along the lines of putting a flat redirect on port 80, with no content. (It sounds like this attack depends on a com
by sliverstorm 13y ago
I don't think that's helpful. Perhaps more along the lines of putting a flat redirect on port 80, with no content.
(It sounds like this attack depends on a complete version of the website being available over port 80)
- agwa 13y ago> (It sounds like this attack depends on a complete version of the website being available over port 80) No, it doesn't. An attacker can always connect to the website over HTTPS and proxy the content to the victim over port 80.
- sliverstorm 13y agoHmm, yes, of course you are correct. I'm not sure why I was thinking that wouldn't be a risk.