Skip to main content

Hear No Evil, See No Evil: A Case Study

  • Chapter
Decompiling Android
  • 1654 Accesses

Abstract

You’re now almost at the end of your journey. By now you should have a sound understanding of the overall principles of how to decompile and how to make some attempts at protecting your code. Having said that, I’ve found from working with clients and colleagues that even if you understand what decompilation and obfuscation really mean, it doesn’t help you figure out what practical measures you can take to protect your code. A little knowledge can often create more questions than answers.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 44.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 59.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

Authors

Rights and permissions

Reprints and permissions

Copyright information

© 2012 Godfrey Nolan

About this chapter

Cite this chapter

Nolan, G. (2012). Hear No Evil, See No Evil: A Case Study. In: Decompiling Android. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4302-4249-9_7

Download citation

Publish with us

Policies and ethics