by hazebooth on 12/23/22, 7:36 PM with 122 comments
by noduerme on 12/24/22, 11:39 AM
I spent a lot of time in the early 2000s coming up with nasty obfuscation techniques to protect certain IP that inherently needed to be run client-side in casino games. Up to and including inserting bytecode that was custom crafted to intentionally crash off-the-shelf decompilers that had to run the code to disassemble it (and forcing them to phone home in the process where possible!)
My view on obfuscation is that since it's never a valid security practice, it's only admissible for hiding machinery from the general public. For instance, if you have IP you want to protect from average script kiddies. Any serious IP can be replicated by someone with deep pockets anyway. Most other uses of code obfuscation are nefarious, and obfuscated code should always be assumed to be malicious until proven otherwise. I'm not a reputable large company, but no reputable large company should be going to these lengths to hide their process from the user, because doing so serves no valid security purpose.
by codedokode on 12/24/22, 8:42 AM
This shows how browser developers race to provide new features ignoring privacy impact.
I don't understand why features that allow fingerprinting (reading back canvas pixels or GPU buffers) are not hidden behind a permission.
by TobyTheDog123 on 12/24/22, 11:27 AM
by thih9 on 12/24/22, 9:52 AM
[1]: https://github.com/javascript-obfuscator/javascript-obfuscat...
[2]: https://github.com/javascript-obfuscator/javascript-obfuscat...
by derefr on 12/24/22, 5:21 PM
by antiviral on 12/24/22, 8:24 PM
It also shows how Tiktok may be in violation of several US/EU privacy laws. I really wonder now who this data is shared with. Perhaps someone should bring this article to the FTC’s attention for further review.
by KirillPanov on 12/24/22, 1:20 PM
> If that is something you are interested in, keep an eye out for the second part of this series :)
Your site is missing an RSS/Atom feed, so I can't do that. ::sad face::
by wiml on 12/24/22, 6:03 PM
by amelius on 12/24/22, 7:48 PM
by Aperocky on 12/24/22, 3:03 PM
by Alifatisk on 12/24/22, 4:49 PM
But that explains the obvious subdomain vm.tiktok.com
by born-jre on 12/24/22, 12:21 PM
by mhasbini on 12/24/22, 11:14 AM
by lazyeye on 12/24/22, 11:06 PM
by derefr on 12/24/22, 5:18 PM
by thecleaner on 12/24/22, 11:16 PM
by Exuma on 12/24/22, 3:17 PM
by apienx on 12/24/22, 11:19 AM
Those who care and have to use TikTok can probably add their own virtualization layer (and tolerate the hit in cost/performance).
by frozencell on 12/24/22, 9:04 AM
by draw_down on 12/24/22, 10:39 AM
Kind of. But it was possible at one point, maybe still is, to rebind `undefined` to some other value, causing trouble. `void` is an operator, a language keyword; it’s guaranteed to give you the true undefined value. (In other words, the value whose type is `undefined`.)
If you’re coding against an environment as adversarial as these people clearly believe they are, you’d go with `void` as well.
by Kukumber on 12/24/22, 1:55 PM
This decompiled object class also spy on the grid network, that's quite interesting and very clever
I never knew we could also lobby governments to push for some office and cloud software full of spyware, even France had to ban them! [1]
This TikTok app is very dangerous!
Of course /s