This basically describes my experience with counter strike pre-1.6.... like 1.3 thru 1.5, circa 2002-2005. Lost thousands of hours of my youth negotiating knives-only rounds and doing stupid totem pole camping on de_dust while 1 guy on the other team tried to AWP everybody. Am I old?
GenitalHurricane
Say what you will about Hitler, but at least he killed Hitler.
This comment makes me sad because you are probably right. Mashinky it is!
Worth mentioning to anyone who is excited for a possible new version of this title but hates AAA ethics, OpenTTD is FOSS and pretty good.
Alternatively if you'd like a modern take on this, Mashinky is super good and was made by a 1-man studio. It's also beautiful. (And multiplayer!)
So nothing ... Ok
This loser works cashier at a gas station in a racist town until evidence is provided to counter my obvious facts
Ah yes, delete your original incorrect comment instead of continuing the discussion about how wrong and lazy it was to make, nice.
Libmanwe-lib.so is a library file in machine language (compiled). A Google search reveals that it is exclusively mentioned in the context of PDD software—all five search results refer to PDD’s apps. According to this discussion on GitHub, “the malicious code of PDD is protected by two sets of VMPs (manwe, nvwa)”. Libmanwe is the library to use manwe.
An anonymous user uploaded a decompiled version of libmanwe-lib to GitHub. It reads like it is a list of methods to encrypt, decrypt or shift integer signals, which fits the above description as a VMP for the sake of hiding a program’s purpose.
In plain words, TEMU’s app employed a PDD proprietary measure to hide malicious code in an opaque bubble within the application’s executables
- Dynamic compilation using runtime.exec(). A cryptically named function in the source code calls for “package compile”, using runtime.exec(). This means a new program is created by the app itself.—Compiling is the process of creating a computer executable from a human-readable code. The executable created by this function is not visible to security scans before or during installation of the app, or even with elaborate penetration testing. Therefore, TEMU’s app could have passed all the tests for approval into Google’s Play Store, despite having an open door built in for an unbounded use of exploitative methods. The local compilation even allows the software to make use of other data on the device that itself could have been created dynamically and with information from TEMU’s servers.
The study and evidence was already provided months ago
This was also linked in the article if you read it
he_glass