Re:When did POP and IMAP become a “legacy protocol?”
by hsbauauvhabzb on Sunday September 25, 2022 @06:41PM
(#32977144)
Exactly what risk does it have being on a low profile blog?
[ Parent
| on HN ]
Re:When did POP and IMAP become a “legacy protocol?”
by cesarb on Sunday September 25, 2022 @07:54PM
(#32977746)
Will it always be a "low profile blog"? It just got on the front page of HN, which is not exactly "low profile".
As for what risk, two words: Great Cannon. For those who don't know, it's a well-known MITM attacker which injects JavaScript code on non-HTTPS pages, the injected JavaScript being used to do distributed denial of service attacks on other sites. Using HTTPS protects against these kinds of attacks.
Re:When did POP and IMAP become a “legacy protocol?”
by oddlama on Sunday September 25, 2022 @06:58PM
(#32977281)
I for example just wouldn't like anyone to be able to see what data I exchange with any server, be it small profile blog or a login page.
Re:When did POP and IMAP become a “legacy protocol?”
by BeefWellington on Sunday September 25, 2022 @08:11PM
(#32977865)
I for example just wouldn't like anyone to be able to see what data I exchange with any server, be it small profile blog or a login page.
Note: It's really, "see and modify undetected" what data you are exchanging with any server.
Re:When did POP and IMAP become a “legacy protocol?”
by handsclean on Sunday September 25, 2022 @07:05PM
(#32977330)
It results in your browsing history being tracked and sometimes sold by your access point and ISP at a page level instead of just domain level, results in injected ads and banners on some access points, results in injected trackers on Verizon, and more broadly it permits unknown third parties to alter the content of your website.
Re:When did POP and IMAP become a “legacy protocol?”
by mccorrinall on Sunday September 25, 2022 @07:53PM
(#32977734)
If someone wants to track you, they can just mark the frame. Marking packets isn’t anything new,