comments

kuangkaiyuan · Sep 27, 2016 · 23cf579 · 23cf579
1 parent f63fc29
commit 23cf579
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 4 deletions.
diff --git a/DCVP.tex b/DCVP.tex
@@ -223,8 +223,6 @@ \section{Introduction}
 
 \input{motivation}
 
-\FIXME{We need an overview section here to briefly describe each step of your approach.}
-
 \input{implementation}
 
 

diff --git a/implementation.tex b/implementation.tex
@@ -1,5 +1,7 @@
-\section{Implementation Details}\label{sec:overview}
-As we have described, the reuse of \textit{analysis knowledge} about the semantics of bytecode instructions can save an analyst much time and effort. Since the longer the software stay uncompromised, the more benefit the software authors will get, the naive idea to harden code virtualized obfuscation is to disable the \textit{analysis knowledge} and force analysts to analyze the obfuscated software programs from scratch. Our solution is randomizing the relationships between the bytecode instructions and their semantics for each obfuscation instance. In this section, we will present the details about our solution. For better understanding, we will start from the design of virtual IS and \texttt{handlers}.
+\section{Overview}\label{sec:overview}
+%As we have described, the reuse of \textit{analysis knowledge} about the semantics of bytecode instructions can save an analyst much time and effort. Since the longer the software stay uncompromised, the more benefit the software authors will get, the naive idea to harden code virtualized obfuscation is to disable the \textit{analysis knowledge} and force analysts to analyze the obfuscated software programs from scratch. Our solution is randomizing the relationships between the bytecode instructions and their semantics for each obfuscation instance. In this section, we will present the details about our solution. For better understanding, we will start from the design of virtual IS and \texttt{handlers}.
+
+\FIXME{This is not an overview. Please briefly describe your approach but not explainations of terminologies.}
 
 \paragraph{Virtual IS and Handlers}
 %\subsubsection{Virtual IS and Handlers}
Original file line number	Diff line number	Diff line change
Expand Up		@@ -223,8 +223,6 @@ \section{Introduction}

		\input{motivation}

		\FIXME{We need an overview section here to briefly describe each step of your approach.}

		\input{implementation}


Expand Down