Re:Google Chrome impacted by new Magellan 2.0 vulnerabilities
by thoksink on Thursday December 26, 2019 @12:13PM
(#21885172)
It might be the time to use something else, with less privacy violation
[ Parent
| on HN ]
Re:Google Chrome impacted by new Magellan 2.0 vulnerabilities
by rasz on Saturday December 28, 2019 @08:14PM
(#21903133)
Its not even strictly privacy violation, but carelessness. Google would never enable something like this(raw calling someone elses unvalidated library) internally, yet its a wild west when it comes to browsers running on user computers. How did we get to the point where browser will happily leak available C drive free space with one stupid navigator.storage.estimate() call.