changes

paper.tex

@@ -191,7 +191,7 @@ \section{Protection}
 According to a paper by Hovav Shacham et al. ASLR is a good protection against ROP in 64 bit binaries assuming no side channel leakage since 40 bit are available for randomizations of the libraries and code locations, however, 32 Bit binaries only use 16 Bit for randomization. Because of that they were able to perform a buffer overflow attack like ret2libc on an Apache server with an average of 216 seconds.~\cite{aslr}
 
 \section{Conclusion}
-As it has been demonstrated Return Oriented Programming is a powerful exploitation technique which should be taken seriously. As we were able to see the only way to make a binary relatively safe is to compile it as 64 Bit with stack canaries, bounds checking and ASLR enabled, though even then side channel attacks, bugs and bruteforcing based on a poor entropy pool may make an attack possible. Replacing or patching vulnerable devices is very important and more research on this topic paired with direct action in systems design may be necessary to keep up with black-hats.
+As it has been demonstrated Return Oriented Programming is a powerful exploitation technique which should be taken seriously. From the research surrounding the attacking technique and protection mechanisms the only way to make the binary relatively safe is to compile it as 64 Bit executable with stack canaries, bounds checking and ASLR enabled, though even then side channel attacks, bugs and bruteforcing based on a poor entropy pool may make an attack possible. Replacing or patching vulnerable devices is very important and more research on this topic paired with direct action in systems design may be necessary to keep up with black-hats.
 %%%% 8. BILBIOGRAPHY %%%%
 \bibliographystyle{alpha}
 \bibliography{refs}