It is a good idea, that's why there are multiple mature solutions in the market, including free and open source solutions like the one I mentioned
HN user
enjoytheview
Opengrep, the OSS sucessor to semgrep. There is no sane reason in this world to use this slopfest instead of opengrep.
Answer starting with "You're absolutely right!" means instant ignore
A security project vibe coded by someone who admittedly does not have a security or even software engineering background, what could go wrong!
Here's a really good free one:
OpenSecurityTraining2 Architecture 1001: x86-64 Assembly
https://p.ost2.fyi/courses/course-v1:OpenSecurityTraining2+A...
They also have RISC-V and many other for debuggers and reverse engineering tools (ida/ghidra for example)
In my case, I had a lung issue and CT scans are more sensitive to air being where it shouldn't be. At least two of the 5 ct scans could probaly just have been x-rays tho.
So 0.1% extra lifetime risk for every CT scan, I guess I went from 40% lifetime risk to 40.5, I guess I'll keep not drinking, not smoking and not being obese to help with the statistics.
How do you even eat 3 kilograms of cheese in one day?
This guys youtube channel (low byte productions) is an absolute gem if you like low level stuff.
The answer is both. Devs will first try to fix it by correctly emulating the system behavior because like you said, that can also fix other games and because that is the right thing to do. There are occasions where doing that can result in a huge performance penalty or some other underised behavior so they just resort to hacks in the emulator or straight up patching the game.
The other comment on this thread mentions that it also does something else:
disables all the system calls not explicitly invoked by the program text of a static binary
This means that if the original library didn't have an execve call in it, you would'nt be able to use it even if with ROP. In short, this seems useful to block attackers from using syscalls that were not originally used by the program and nothing else. It can be useful.
I'm using an extension called "Bypass Paywalls Clean", haven't updated it in a very longe while and it still works, looks like the current versions is here: https://github.com/iamadamdev/bypass-paywalls-chrome
I wonder if that would be enough to precisely identify a single user between millions like regular fingerprinting can already do, but yeah it's still a big fingerprinting vector
Bezier curves are easily detected by machine learning models as non-human, that software wont work on akamai or any decent anti-bot
You don't need to precisely identify users across sessions without their consent to detect bots, advanced anti-bots make heavy use of biometrics to detect bots and don't rely too heavily on fingerprinting, mostly because they're easy to spoof in general, but generating human-like mouse data is a bigger challange.
This study is talking about testosterone changes in relation to number of days of ejaculation abstinence.
It says nothing about testosterone levels vs ejaculation frequency.
Yeah, pretty sure that loop is to modify the lookup table for strings in runtime so you can't just statically replace it in the code, it's not strong obfuscation but in a properly deobfuscated code that loop wouldn't exist