zlacker

[parent] [thread] 7 comments
1. matheu+(OP)[view] [source] 2020-11-29 02:02:53
> I don't understand the disable JS movement

Javascript is a privacy and security nightmare. It's almost equivalent to downloading and silently executing untrusted code on your machine. I say "almost" because Javascript code is virtualized and sandboxed. Though I have no doubt people have already discovered vulnerabilities that enable code to break out of the sandbox.

replies(2): >>jolux+E >>kordle+75
2. jolux+E[view] [source] 2020-11-29 02:11:18
>>matheu+(OP)
The cost-benefit analysis of JavaScript usage comes down on the side of enabling it for most people, because of how much of the web is completely broken without it. Sandbox escapes are rare but extremely valuable, and they absolutely exist: https://www.computerworld.com/article/3186686/google-patches...
3. kordle+75[view] [source] 2020-11-29 03:15:39
>>matheu+(OP)
> Javascript is a privacy and security nightmare.

AFAIK, JavaScript the language has neither privacy nor security issues of "nightmare" level.

> It's almost equivalent to downloading and silently executing untrusted code on your machine.

No it's not. The code is run in a VM, which is run in a browser. So, the code is limited in doing things to the browser, which itself is limited in what it can do to your computer (files and whatnot). So it's not at all like running untrusted code "on your machine".

> I say "almost" because Javascript code is virtualized and sandboxed.

It's virtualized (in the browser) such that all the code will run almost the same on different browsers and chipsets. Again, the browser code is what keeps the computer safe from any code it runs, including CSS code or other VMs it may use, like Java or Flash. Also the OS keeps the computer safe from the browser (or at least it should).

So, no it's not JavaScript that is the boogeyman here.

replies(1): >>jachee+F5
◧◩
4. jachee+F5[view] [source] [discussion] 2020-11-29 03:24:14
>>kordle+75
My understanding is that JavaScript is the primary mechanism used in browser fingerprinting and cross-site user tracking/"analytics". Isn't that a rather large privacy and (personal, if not specifically "cyber") security risk?
replies(2): >>1vuio0+Od >>XCSme+WI1
◧◩◪
5. 1vuio0+Od[view] [source] [discussion] 2020-11-29 05:48:19
>>jachee+F5
Yes.

The "security features" of popular browsers will never protect the user from the tentacles of internet advertising. Companies/organizations that author popular web browsers generally rely on the success of internet advertising in order to continue as going concerns; as such, they are obviously not focused on internet advertising, and collection of user data, as a "security threat".

◧◩◪
6. XCSme+WI1[view] [source] [discussion] 2020-11-29 23:11:15
>>jachee+F5
Actually, the main and most used mechanism of cross-site user tracking and "fingerprinting" are cookies, which do not require any JS to work.
replies(1): >>jachee+o45
◧◩◪◨
7. jachee+o45[view] [source] [discussion] 2020-12-01 03:06:33
>>XCSme+WI1
How does cross-site user tracking do its thing?
replies(1): >>XCSme+Dz5
◧◩◪◨⬒
8. XCSme+Dz5[view] [source] [discussion] 2020-12-01 09:31:04
>>jachee+o45
Set a cookie using HTTP headers.

Use a tracking pixel (eg. image) to make further requests and cookie will be included in the request.

[go to top]