• Save
Reverse Engineering v/s Secure Coding
Upcoming SlideShare
Loading in...5
×
 

Reverse Engineering v/s Secure Coding

on

  • 2,577 views

 

Statistics

Views

Total Views
2,577
Views on SlideShare
2,567
Embed Views
10

Actions

Likes
1
Downloads
0
Comments
0

2 Embeds 10

http://www.secguru.com 7
http://www.slideshare.net 3

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Reverse Engineering v/s Secure Coding Reverse Engineering v/s Secure Coding Presentation Transcript

  • Reverse Engineering v/s Secure Coding.
  • 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?
  • Cryptography?...Hmm…
    • Cryptography in Application Registration routines don’t 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.
    View slide
  • Packers & Protectors?
    • What are Packers?
    • What are Protectors?
    • Packers make Sense but Protectors don’t !
    • Packers == very easy to defeat.
    • Protectors == who cares to defeat ?
    • Virtual Machines?.... Not again!
    View slide
  • .Net & Java == Not Cool?
    • Decompilation & not Disassembling.
    • .Net is M$’s 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.
  • Mobile Devices…. Yeah!
    • Sony Ericsson’s “.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.
    • Don’t even want to talk about Sony Ericsson & Siemens’ “Phone Modding”.
  • Can I Tackle R.E ?
    • Technically Speaking? No you Can’t!
    • 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!
  • “ Thinking Before Writing, saves the time spent in Editing.” –Pirated. Thank You.
    • Atul Alex Cherian,
    • www.OrchidSeven.com .
    • Ph:9860056788.
    • [email_address]