invitation to discussion: code and protocol obfuscation techniques

"Gyll ." <isiisorisiaint@gmail.com>
Thu, 1 Aug 2013 14:49:02 +0300

          From comp.compilers

Related articles
invitation to discussion: code and protocol obfuscation techniques isiisorisiaint@gmail.com (Gyll .) (2013-08-01)
RE: invitation to discussion: code and protocol obfuscation techniques costello@mitre.org (Costello, Roger L.) (2013-08-03)
Re: invitation to discussion: code and protocol obfuscation techniques gah@ugcs.caltech.edu (glen herrmannsfeldt) (2013-08-04)
Re: invitation to discussion: code and protocol obfuscation techniques isiisorisiaint@gmail.com (Gyll .) (2013-08-05)
Re: invitation to discussion: code and protocol obfuscation techniques isiisorisiaint@gmail.com (Gyll .) (2013-08-05)
Re: invitation to discussion: code and protocol obfuscation techniques gah@ugcs.caltech.edu (glen herrmannsfeldt) (2013-08-06)
Re: invitation to discussion: code and protocol obfuscation techniques isiisorisiaint@gmail.com (2013-08-08)
[3 later articles]
| List of all articles for this month |

From: "Gyll ." <isiisorisiaint@gmail.com>
Newsgroups: comp.compilers
Date: Thu, 1 Aug 2013 14:49:02 +0300
Organization: Compilers Central
Keywords: code, question
Posted-Date: 03 Aug 2013 16:46:51 EDT

I'd like to get some info on the subject of code obfuscation,
particularly source code-level obfuscation methods that will not get
rendered [totally] useless by code optimizers, program flow graph
extractors, and other program analysis tools.


More specifically, i need to build an obfuscator source code
preprocessor for a P2P client such that the obfuscator automatically
introduces additional protocol states to the base protocol in the
client code (a "protocol state" is state in the client algorithm state
machine where a [set of] messages are exchanged between two P2P
clients). The obfuscator-introduced protocol validation messages
should be as well obfuscated as possible, in order to make it
difficult for an attacker which has the original source code of the
client to determine which new protocol states have been introduced
(and where inside the code) by the obfuscator.


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.