3 ms·
The link provided in the article to HTTPLeaks required some sort of login for me. Here is the direct link: * https://github.com/cure53/HTTPLeaks https://github
by upofadown 6y ago
The link provided in the article to HTTPLeaks required some sort of login for me. Here is the direct link:
* https://github.com/cure53/HTTPLeaks https://github.com/cure53/HTTPLeaks
There are a lot of ways HTML can leak information. HTTPLeaks is an attempt to create a test for all such leaks. Unfortunately, people keep inventing new ways for HTML interpretation to leak data. The article describes a particularly clever approach accidentally implemented by Apple.
- bawolff 6y agoI don't know what people expect - don't run code you don't trust. There is also lots of ways for python to leak data if you execute a malicious python script.
- schmidp 6y agoIt's not about running code, it's about opening a TXT file with the operating system default handler for TXT files. So you what you are saying is basically 'do not open any files or websites you don't trust' - which is usually not what people expect as that would basically mean 'don't use your computer'
- bawolff 6y agoMore specificly im saying, the web is designed around making network requests. If your threat model is not to make network requests, you shouldn't try and sanitize html vis blacklists because you'll be in for a bad tine (responding to the grandparent's list of html leaks not the article. I agree that its unreasonable that the txt file does anything. The mistake is in the apple devs trying to sanitize html which is doomed to failure)