Reverse Engineering - School of Computer Science - University …逆向工程-计算机科学学院….pptVIP

下载本文档

2
0
约2.41千字
约 12页
2018-04-17 发布于江西
举报
版权申诉

Reverse Engineering - School of Computer Science - University …逆向工程-计算机科学学院….ppt

1、本文档共12页，可阅读全部内容。
2、原创力文档（book118）网站文档一经付费（服务费），不意味着购买了该文档的版权，仅供个人/单位学习、研究之用，不得用于商业用途，未经授权，严禁复制、发行、汇编、翻译或者网络传播等，侵权必究。
3、本站所有内容均由合作方或网友上传，本站不对文档的完整性、权威性及其观点立场正确性做任何保证或承诺！文档内容仅供研究参考，付费前请自行鉴别。如您付费，意味着您自己接受本站规则且自行承担风险，本站不退款、不进行额外附加服务；查看《如何避免下载的几个坑》。如果您已付费下载过本站文档，您可以点击这里二次下载。
4、如文档侵犯商业秘密、侵犯著作权、侵犯人身权等，请点击“版权申诉”（推荐），也可以打举报电话：400-050-0827(电话支持时间：9:00-18:30)。
5、该文档为VIP文档，如果想要下载，成为VIP会员后，下载免费。
6、成为VIP后，下载本文档将扣除1次下载权益。下载后，不支持退款、换文档。如有疑问请联系我们。
7、成为VIP后，您将拥有八大权益，权益包括：VIP文档下载权益、阅读免打扰、文档格式转换、高级专利检索、专属身份标志、高级客服、多端互通、版权登记。
8、VIP文档为合作方或网友上传，每下载1次，网站将根据用户上传文档的质量评分、类型等，对文档贡献者给予高额补贴、流量扶持。如果你也想贡献VIP文档。上传文档

Reverse Engineering - School of Computer Science - University …逆向工程-计算机科学学院….ppt

Reverse Engineering Ian Kayne RCE Reverse (Code) Engineering – “reversing” What is it? Why is it done? Malware research defence System interoperability requirements Review and audit of software/security system Why is it useful to security specialists? “Learn the principles” RCE Required knowledge/skills (x86) Platform knowledge – stack, registers etc “Some” assembly language C/C++ as many other languages as possible Operating system mechanisms win32api Toolset (debugger, disasm, hex editor…) Mindset (patterns, logic) RCE Imagine a strong protection mechanism RCE Reversing demonstration RCE After the demonstration, recap: Analysed executable Set breakpoints on likely API calls Traced up the call stack Analysed the code Found the good boy/bad boy “switch” Patched the jump “live” to test Converted RVA to file offset, patched file 1 byte patch Protection Imagine a strong protection mechanism again License key system CRC Anti-debugging techniques Encryption Protection Encryption for protection Data must be decrypted before use Code must be decrypted before execution UPX (packer), Armadillo, Themida… Can be made very hard, but not impossible Remember the jump loop – EB FE Generics – break one, break all Homebrew is risky – “learn the principles” Protection Some obfuscation techniques: Encode obvious “beacon” strings Avoid win32api/library functions: bpx MessageboxA Use alternative functions/mechanisms E.g.: SetWindowPos instead of ShowWindow Roll your own api/GUI functions Can’t break on GetWindowText if you don’t use it! Hide code within the executable Self modifying code, PE sections etc Protection Some anti-debugger techniques Deliberate exceptions (code in SEH) Self-debugging (can’t “stack” debuggers) Timers and counters Alter DR0 – DR7 hardware debug registers IsDebuggerPresent() Check for/attack known debugger processes, windows, services, drivers… (Starforce) /infocus/1893 RCE Why are these low-level technical techniques important? “Learn the principles” Your