| F. Cohen, "Operating System Protection Through Program Evolution", Computers and Security 12(6), 1 Oct. 1993, pp. 565--584. |
....We decided to rename this term since dynamic obfuscation may sound like obfuscation that happens as the program runs (e.g. as in dynamic compilation ) which is not the case here. techniques used by polymorphic computer viruses, which use them to hide themselves from anti virus programs [28]. Although very difficult, deobfuscating polymorphic viruses is not impossible because viruses, being self reproductive (by definition) contain the obfuscating code. Thus, once one version has been cracked and disassembled, it is possible to reverse engineer this code and develop an antidote ....
....is an old technique that has been around since programmers first started to worry about protecting their intellectual property from reverse engineering by competitors. In 1992, Cohen studied the application of obfuscation towards protecting operating systems from attacks by hackers or viruses [28]. At around the same time, these same techniques were actually being used already by virus writers themselves in polymorphic or evolutionary computer viruses. More recently, obfuscation has gained a lot of interest with the advent of Java, whose bytecode binary executable format is very easy to ....
[Article contains additional citation context not shown here]
F.B. Cohen. Operating System Protection Through Program Evolution. 1992. URL: http://all.net/books/IP/evolve.html
....generally believed that complete protection of client code is an unattainable goal [7] recent results (by ourselves and others) have shown that some degree of protection can be achieved. Recently, software watermarking [22] 28] 35] 60] tamper proofing [5] 6] 38] 77] and obfuscation [20], 23] 24] 25] 38] 49] 65] 92] have emerged as feasible technical means for the intellectual property protection of software. Other promising techniques, such as traitor tracing [14] secret sharing [8] reference states [39] and secure evaluation [2] 77] are still in the hands of ....
....to a desired operation code and places the code jumped to appropriately so that the jump works and the proper return address is in the middle of the previously executed instruction. In this way, we reuse the last bytes of the jump location as operation codes on the next pass through the code [20]. Antidebugging. We may disable or confuse a debugger, for example, by writing code that actively uses all available Fig. 5. Strong opaque predicates based on the intractability of alias analysis. g(V) f(p,q) p q V 2p q 0 I True 1 I 0 True 2 A AND [A, B] 0 [ 2 3 03000 13123 20213 ....
[Article contains additional citation context not shown here]
F.B. Cohen, Operating System Protection through Program Evolution. http: / / all.net/books/IP / evolve.html, 1992.
....code. While it is generally believed that complete protection of client code is an unattainable goal [7] recent results (by ourselves and others) have shown that some degree of protection can be achieved. Recently, software watermarking [22,28,35,60] tamper proofing [5,6,38,77] and obfuscation [20,23 25,38,49,65, 92] have emerged as feasible technical means for the intellectual property protection of software. Other promising techniques, such as traitor tracing [14] secret sharing [8] reference states [39] and secure evaluation [2,77] are still in the hands of theorists. Obfuscation attempts to transform ....
....to a desired operation code, and place the code jumped to appropriately so that the jump works and the proper return address is in the middle of the previously executed instruction. In this way, we reuse the last bytes of the jump location as operation codes on the next pass through the code. [20]. Anti Debugging. We may disable or confuse a debugger, for example by writing code that actively uses all available interrupts (including the breakpoint interrupt) 84] If we know what debugger the reverseengineer is likely to be using, then our code may be able attack the debugger by writing ....
[Article contains additional citation context not shown here]
Frederick B. Cohen. Operating system protection through program evolution. http://all.net/ books/IP/evolve.html, 1992.
....While it is generally believed that complete protection of client code is an unattainable goal, recent results (by ourselves and others) have shown that some degree of protection can be achieved. Recently, software watermarking [12, 16, 21, 36] tamper proofing [4, 5, 23, 45] and obfuscation [10, 13 15] have emerged as alternatives to other forms of intellectual property protection of software. Obfuscation attempts to transform a program into an equivalent one that is harder to reverse engineer. Tamper proofing causes a program to malfunction when it detects that it has been modified. Software ....
Frederick B. Cohen. Operating system protection through program evolution. http:// all.net/books/IP/evolve.html, 1992.
No context found.
F. Cohen, "Operating System Protection Through Program Evolution", Computers and Security 12(6), 1 Oct. 1993, pp. 565--584.
No context found.
F. Cohen, Operating System Protection Through Program Evolution, Computers and Security 12(6), 1 Oct. 1993, pp. 565-584.
No context found.
F. Cohen, \Operating System Protection Through Program Evolution", Computers and Security vol.12 no.6, 1 Oct. 1993, pp. 565-584.
No context found.
F. Cohen, "Operating System Protection Through Program Evolution", Computers and Security 12(6), 1 Oct. 1993, pp. 565--584.
No context found.
F. Cohen, "Operating System Protection Through Program Evolution", Computers and Security 12(6), 1 Oct. 1993, pp. 565--584.
No context found.
F. Cohen, \Operating System Protection Through Program Evolution", Computers and Security 12(6), 1 Oct. 1993, pp. 565-584.
No context found.
F. Cohen, Operating System Protection Through Program Evolution, Computers and Security vol.12 no.6 (1 Oct. 1993), pp.565-584.
No context found.
F. Cohen, \Operating System Protection Through Program Evolution", Computers and Security 12(6), 1 Oct. 1993, pp. 565-584.
No context found.
F. Cohen, Operating System Protection Through Program Evolution, Computers and Security vol.12 no.6 (1 Oct. 1993), pp.565-584.
No context found.
F. B. Cohen. Operating system protection through program evolution. all.net/books/IP/evolve. html, 1992.
No context found.
Frederick B. Cohen. Operating system protection through program evolution. all.net/books/IP/ evolve.html, 1992.
No context found.
F. Cohen. Operating System Protection through Program Evolution. Computers and Security, 12(6):565--584, Oct. 1993.
No context found.
COHEN, F. Operating System Protection through Program Evolution. Computers and Security 12, 6 (Oct. 1993), 565--584.
No context found.
F. B. Cohen. Operating system protection through program evolution, 1992. http://all.net/books/IP/evolve.html.
No context found.
Frederick B. Cohen, Operating System Protection Through Program Evolution, 1992
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC