5 ms·
I Reflectored Reflector once and I found that the source was obfuscated. I don't think that would be a trivial task.
by jeffesp 16y ago
I Reflectored Reflector once and I found that the source was obfuscated. I don't think that would be a trivial task.
- nlawalker 16y agoInterestingly, I'm pretty sure that the original wasn't obfuscated, and Red Gate obfuscated it after they received it from the original developer.
- timrobinson 16y agoReflector's always been obfuscated; Lutz Roeder had a paid-for version as well alongside the free one. (You don't think the first thing we tried with Reflector was to reflect Reflector? :) )
- thisisfmu 16y agoReflector was not always obfuscated. Old versions embedded an unobfuscated but weakly encrypted dll with the core program.
- MichaelGG 16y agoMost compiled code doesn't have debug info and internal symbols. Yet, changing something like an expiry date is often a trivial task. Obfuscation just means you'll actually have to poke around a bit instead of just searching for "isExpiryDateReached".
- innes 16y agoReflector was written by a smart guy. IIRC the obfuscation partly consists of assemblies stored as resources in the executable assembly, and loaded dynamically. But no doubt you're right - it could be disentangled. Better and more ethical to re-write.