Reverse Engineering v/s Secure Coding.

1
Reverse Engineering v/s Secure Coding.
2
What is Secure Coding?

• Is Secure Coding simply avoiding certain already
  discovered vulnerable functions?
• What about Tons of Commercial applications that
  are released everyday?
• Software Crackers (Reverse Engineers) causing
  Millions of Dollars of loss Globally due to
  Software Piracy.
• Are you Programmers taking your Job seriously?

3
Cryptography?...Hmm

• Cryptography in Application Registration routines
  dont make sense.
• Cryptographic Algorithm adds to the applications
  size is Processor intense.
• Cryptographic Algorithm in Registration routines
  can be either completely ripped off or totally
  bypassed and they pose no challenge to a Cracker.

4
Packers Protectors?

• What are Packers?
• What are Protectors?
• Packers make Sense but Protectors dont !
• Packers very easy to defeat.
• Protectors who cares to defeat ?
• Virtual Machines?.... Not again!

5
.Net Java Not Cool?

• Decompilation not Disassembling.
• .Net is Ms take on Java.
• .class files .net executables rely heavily on
  Runtime Environment Components.
• Damn easy to break code and Damn tough to prevent
  us from Tampering with your App.

6
Mobile Devices. Yeah!

• Sony Ericssons .Sest Feature talked about for
  the first time ever!
• J2me applications built for Mobile Devices
  should be Freewares.
• J2me Trojans can be very easy to code.
• Dont even want to talk about Sony Ericsson
  Siemens Phone Modding.

7
Can I Tackle R.E ?

• Technically Speaking? No you Cant!
• Logically ? Bore us to Death!
• How?
• a Use spaghetti Code.
• b Jump all over the Place.
• c Learn Polymorphism.
• d Learn to use your Imagination as a tool.
• e Think like a Reverse Engineer!

8
Thinking Before Writing, saves the time spent in
Editing. Pirated.Thank You.

• Atul Alex Cherian,
• www.OrchidSeven.com.
• Ph9860056788.
• Atul.alex_at_orchidseven.com