Compiletime string literal obfuscation, random numbers and wide strings
crates.io/crates/obfstrPosted Mar 20, 2019, 2:57 PM UTC
Posted Mar 20, 2019, 2:57 PM UTC
You need a wide_null version that puts the 0 on the end.
I figured you'd just "\0" at the end. I find it a cleaner, simpler API. It could probably use a comment in the doc string.
This avoids hard questions like, does .len() include the null terminator or not. Here the answer is clear: it does not.
That's bad for ergonomics, but it's your lib.
Hmm. Interesting thing to have, but probably increasingly niche, given that the APIs presented seem pretty antithetical to reproducible builds and the push for those is on the rise.
Yes this isn't really meant for use in libraries of reputable nature.
I made it specifically to target a hostile environment of game hacking, where string constants are being targetted by anti-cheats as a way of identifying suspicious modules.
Specifically the purpose of the obfuscation is to defeat automated mechanisms to detect the presence of suspicious strings.
Disclaimer: I wrote the linked crate.
I recently started exploring procedural macros, so much potential to explore!