[cfe-dev] aCob : Clang based code obfuscator for C
OvermindDL1
overminddl1 at gmail.com
Sat Nov 20 16:00:21 PST 2010
On Wed, Nov 3, 2010 at 11:26 AM, Mohamed Yousef <harrrrpo at gmail.com> wrote:
> any thoughts ?
>
> On 30 October 2010 00:08, Mohamed Yousef <harrrrpo at gmail.com> wrote:
>>
>> Hello,
>>
>> aCob - Another C Obfuscator, is an obfuscator for C code based on clang,
>> currently it only supports control flow flattening of input code. based on
>> modified algorithm of one suggested here :
>> http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.128.6241&rep=rep1&type=pdf
>> it's based on Clang
>>
>> aCob is hosted here : https://sourceforge.net/projects/acob/files/
>> the link gives :
>> 1) acob source code
>> 2) windows binaries
>> 3) sample inputs and outputs , discussion of used algorithm
>>
>> known problems:
>> 1) it outputs code using prettyprinter (till now, i faced no problems with
>> my samples. but many people in list say it's problematic)
>> 2) due to the way it uses prettyprint (statement by statement), it will
>> give output that gives compilation errors, for certain ways of declaring
>> structs/enums in C
>>
>> hope to hear suggestions / comments from you
>>
>> Thanks,
>>
>> Mohamed Yousef
Well since no one else replied, and I think it is due to this question
I am about to ask, why would you want to obfuscate C code? It is hard
enough to read as it is, want to make it more readable, not less
readable, so what is the purpose? And do not give me a reason about
needing to make code harder to read, just distribute a library then,
not code, or change your license.
More information about the cfe-dev
mailing list