How can we use badly written code
-
We've all been there. Look at some code written by someone else and start thinking what is this guy doing? Long runs of code with no comments, code that is sometimes in procedures but also repeated outside procedures. On the plus side, wouldn't this be an ideal candidate for code obfuscation or security? You can't even understand it with the source code with comments: how about without source code or comments? If the obfuscator, also followed the same disorganized behaviour of a bad programmer, reverse engineering would be really difficult. I wonder if any obfuscation companies ask people to send in samples of bad code. The problem with security is that it is written by "good" programmers - it all lives in one routine which is called from everywhere. Clobber that routine and you've cracked the security. It would be better if the routine was inlined. Also it should not always follow the same sequence, which is what a bad programmer would typically do. CUP
-
We've all been there. Look at some code written by someone else and start thinking what is this guy doing? Long runs of code with no comments, code that is sometimes in procedures but also repeated outside procedures. On the plus side, wouldn't this be an ideal candidate for code obfuscation or security? You can't even understand it with the source code with comments: how about without source code or comments? If the obfuscator, also followed the same disorganized behaviour of a bad programmer, reverse engineering would be really difficult. I wonder if any obfuscation companies ask people to send in samples of bad code. The problem with security is that it is written by "good" programmers - it all lives in one routine which is called from everywhere. Clobber that routine and you've cracked the security. It would be better if the routine was inlined. Also it should not always follow the same sequence, which is what a bad programmer would typically do. CUP
-
We've all been there. Look at some code written by someone else and start thinking what is this guy doing? Long runs of code with no comments, code that is sometimes in procedures but also repeated outside procedures. On the plus side, wouldn't this be an ideal candidate for code obfuscation or security? You can't even understand it with the source code with comments: how about without source code or comments? If the obfuscator, also followed the same disorganized behaviour of a bad programmer, reverse engineering would be really difficult. I wonder if any obfuscation companies ask people to send in samples of bad code. The problem with security is that it is written by "good" programmers - it all lives in one routine which is called from everywhere. Clobber that routine and you've cracked the security. It would be better if the routine was inlined. Also it should not always follow the same sequence, which is what a bad programmer would typically do. CUP
The other use for badly written code is to include it in your project, unobfuscated, and in debug mode so it includes the source. If you can get it in VB6 or earlier that's even better. Compiler warnings (or even errors if you could manage it) are good. You don't have to call it, or use it in any way. But if you can hide a few side effects in there that you do use as a "security feature" that'd work as well. But when hackers spot it, it'll discourage them more than obfuscation ever would! :laugh:
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
-
We've all been there. Look at some code written by someone else and start thinking what is this guy doing? Long runs of code with no comments, code that is sometimes in procedures but also repeated outside procedures. On the plus side, wouldn't this be an ideal candidate for code obfuscation or security? You can't even understand it with the source code with comments: how about without source code or comments? If the obfuscator, also followed the same disorganized behaviour of a bad programmer, reverse engineering would be really difficult. I wonder if any obfuscation companies ask people to send in samples of bad code. The problem with security is that it is written by "good" programmers - it all lives in one routine which is called from everywhere. Clobber that routine and you've cracked the security. It would be better if the routine was inlined. Also it should not always follow the same sequence, which is what a bad programmer would typically do. CUP
How can we use badly written code
Vogon poetry.
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X If you think 'goto' is evil, try writing an Assembly program without JMP. -- TNCaver "When you have eliminated the JavaScript, whatever remains must be an empty page." -- Mike Hankey
-
The other use for badly written code is to include it in your project, unobfuscated, and in debug mode so it includes the source. If you can get it in VB6 or earlier that's even better. Compiler warnings (or even errors if you could manage it) are good. You don't have to call it, or use it in any way. But if you can hide a few side effects in there that you do use as a "security feature" that'd work as well. But when hackers spot it, it'll discourage them more than obfuscation ever would! :laugh:
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
Dammit, Stop talking about Windows 8. :laugh:
