On.Security
Developing secure software is a challenge. Writing really secure software is a real challenge.
Here are the articles which touch different security aspects of software, from “what cipher suites are not to be used with TLS”, to certain more or less novel things under ‘Security Research’ subcategory
Bot Fighting 202. Time-Based Protection
January 23, 2018 by • “No Bugs” Bunny
Quote:
Whenever we detect that the time spent within a piece-of-non-blocking-code, is more than a few seconds – then, either the system is hopelessly swapping, or we're being debugged
Another Quote:
What if we send not just a challenge, but a “challenge which includes some piece of code to be executed on the Client-Side”?
Filed under: On.SecurityFraud PreventionBook: D&D of MOGs1st beta of Vol. VII-IX
Read moreBot Fighting 201. Part 4. Obfuscating Protocols. Versioning.
January 16, 2018 by • “No Bugs” Bunny
Quote:
we can handle several Client versions (each with its own obfuscation) with the very same Server.
Another Quote:
Then, if/when a zero-day bug is encountered in TLS – our obfuscation does provide additional protection even before the attacker can reach the code with that zero-day vulnerability
Filed under: On.SecurityFraud PreventionBook: D&D of MOGs1st beta of Vol. VII-IXResearch
Read moreBot Fighting 201, part 3. ithare::obf: An Open Source Data+Source Randomized Obfuscation Library
January 9, 2018 by • “No Bugs” Bunny
Quote:
This is all what the-best-available-decompiler was able to do with our obfuscated code
Another Quote:
Performance-wise, we can do A LOT of obfuscation per network tick
Filed under: On.SecurityFraud PreventionBook: D&D of MOGs1st beta of Vol. VII-IX
Read moreBot Fighting 201, Part 2: Obfuscating Literals
January 2, 2018 by • “No Bugs” Bunny
Quote:
However, we can (and SHOULD) do MUCH better than that
Another Quote:
With our approach, each and every obfuscation has to be hacked individually..
Filed under: On.SecurityFraud PreventionBook: D&D of MOGs1st beta of Vol. VII-IX
Read more



