Re:The modern HTTPS world has no place for old web servers
by fwip on Wednesday May 13, 2020 @12:39PM
(#23168714)
Until somebody finds a vulnerability in your JSON parser or other layers of your stack. :)
[ Parent
| on HN ]
Re:The modern HTTPS world has no place for old web servers
by sudosysgen on Wednesday May 13, 2020 @01:13PM
(#23169143)
There are inherent, unfixable vulnerabilities to a weather app, such as divulging location information and possibly travel patterns.
Re:The modern HTTPS world has no place for old web servers
by maxwellg on Wednesday May 13, 2020 @01:43PM
(#23169473)
If you request weather info for a large range of locations at once - the k-Anonymity that HAVE I BEEN PWNED uses - you could prevent this at the cost of increasing response size dramatically
https://www.troyhunt.com/ive-just-launched-pwned-passwords-v...
Re:The modern HTTPS world has no place for old web servers
by saagarjha on Wednesday May 13, 2020 @02:57PM
(#23170381)
I don't think that would help much. If my phone tries to get weather data for the prefix "66" and then "a9" and later "8d" and you correlate the cities together, you can be pretty sure I was driving around the Bay Area if the first list contains "Cupertino", the second "San Jose", and the third "Palo Alto".
Re:The modern HTTPS world has no place for old web servers
by maxwellg on Wednesday May 13, 2020 @06:41PM
(#23172682)
I was thinking less around prefix matching and more around requesting enough data to where an observer couldn't tell what I was really interested in. If I requested 100 distinct locations in every state - 5000 total - you would know I was interested in the United States, but you would have a hard time determining where specifically.