[cfe-dev] aCob : Clang based code obfuscator for C

[Mohamed Yousef]

i would like to add that in this package the focus is more on binary
obfuscation rather than source-only obfuscation
i.e. if you ship some software that contains some algorithm that you want to
hide from a reverse-engineer
the basic idea is to make it hard to analyze the code and reconstruct the
algorithm even if it passes through a compiler and regardless of
optimizations it may apply

On 21 November 2010 02:18, Francois Pichet <pichet2000 at gmail.com> wrote:

> On Sat, Nov 20, 2010 at 7:00 PM, OvermindDL1 <overminddl1 at gmail.com>
> wrote:
> > 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.
>
> Gimpel software ships FlexeLint for C/C++ as obfuscated code so you
> can recompile it on your host without (easily) reverse engineer it.
>
> Sometimes shipping a library is not practical if your customers are
> using all kind of weird platforms, ABIs and compilers. That's why
> almost all C++ libs ship with the source.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20101121/443ffbcd/attachment.html>