New versions of Akira and any other ransomware are constantly being developed. This code is specific to a certain version of the malware.
As noted in the article, it also requires:
1. An extremely capable sysadmin 2. A bunch of GPU capacity 3. That the timestamps be brute-forced separately
So it's not exactly a turn-key defeat of Akira.
It's hard to have more chips, for example. You run less experiments, you have less throughput in an already computationally tight environment.
Code is a good place for logic to live.
Compared to yaml, code is more testable, readable and expressible.
I should’ve restricted my original comment to the kind of situation in the article where different configs are created for various regions and test environments with optional values. Totally agree configs are useful for defining more static values.
Yes, logic should live in code, but very often that logic needs to behave differently depending on some piece of (inherently variable, not static) configuration.
Random examples (written from the perspective of personified code): - How many threads should I use? - On which port should I serve metrics? - Which retry strategy should I use?
does it really though? what part do they struggle with?
The incentive structure behind paying by the search has diminishing returns, as I see it. You need the results to be of a high enough quality to drive the user to want to run another search with you. Beyond that point, though, in the absence of a direct competitor, where is the incentive for you to continue improving search result quality? M