4 ms·
The more this happens the more Chrome deciding to freeze the UA string forever makes sense.
by Spivak 4y ago
The more this happens the more Chrome deciding to freeze the UA string forever makes sense.
- LightHugger 4y agoIt's not a bad idea for security either, as a way to combat fingerprinting efforts.
- Nextgrid 4y agoWhich is also exactly why it ended up being reverted.
- PenguinCoder 4y agoUser agent strings aren't reliable for fingerprinting users or devices already. Shouldn't be using them as high fidelity IOCs. But yeah, some still do. Much better ways to fingerprint users or devices on HTTP/websites.
- deleted 4y ago[deleted]
- ape4 4y agoLooks like that's been replace by "Reduce User-Agent request header Reduce (formerly, "freeze") the amount of information available in the User-Agent request header. See https://www.chromium.org/updates/ua-reduction https://www.chromium.org/updates/ua-reduction for more info. – Mac, Windows, Linux, ChromeOS, Android, Fuchsia, Lacros #reduce-user-agent"
- chungy 4y agoWhat? Since when? I just checked with useragentstring.com and the UA reports the same version I'm actually using.
- Hamuko 4y agoI was under the impression that the User-Agent is kinda on its way out anyways.
- Dalewyn 4y agoPerhaps reflective of the times. A browser becomes less and less an agent of the user with each passing day.
- olliej 4y agoYeah, all browser developers have tried to essentially freeze the UA, if nothing else to stop keying site behaviour off random subsets of it. For example here is my UA: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/16.2 Safari/605.1.15 Which is all sorts of frozen (old os version, intel on an arm device, etc)