News for hackers. Stuff that matters.
Re:Timeline of the xz open source attack by davedx on Tuesday April 02, 2024 @12:28PM (#39907634)
Nonsensical argument. JavaScript and TypeScript projects are developed with patches of the original source not some compressed artefact. Take your trolling elsewhere
Re:Timeline of the xz open source attack by Dalewyn on Tuesday April 02, 2024 @01:15PM (#39908266)
The vast majority of JavaShit executed by the end user in their user agent are "compressed artefacts" that cannot be read by human eyes in any practical way. Likewise most HTML and CSS which are also obfuscated to impracticality.

This is coincidentally drawing a parallel with the xz attack: The source code and the distributed tarballs (the "compressed artefacts") are different.

Re:Timeline of the xz open source attack by mardifoufs on Tuesday April 02, 2024 @05:40PM (#39911158)
Javascript is almost always executed in sandboxed, unprivileged environments. The issue here is that this type of obfuscation is easy to add in core os libraries. The JavaScript ecosystem, for all the hate that it gets, makes it super easy to sandbox any running code.

It doesn't matter if it's minified or obfuscated because you basically have to run unknown, untrusted code everywhere while browsing the web with JavaScript turned on. So the ecosystem and tooling is extremely resilient to most forms of malicious attacks no matter how minified or obfuscated the js you're running is. The complete opposite is true for bash and shell scripting in general