Reverse Engineering b10g | REM

hi

Cracking code - Introduction

from this link:
http://www.atrevido.net/blog/PermaLink.aspx?guid=73204548-5970-46db-b7cf-76cd4c22c3b9

To defend, you must have some idea of what you’re defending, and who and what you’re defending against, specifically, which attacks.  Failure do understand and know these things means that your defense will most likely not be effective, and could in fact decrease your security.  Here’s an example:

Near where I live, thieves were stealing cars that people parked in the street.  The neighbourhood committee decided that they’d stop this.  The solution they implemented was to put gates at all entrances and exits of their area, and have guards that only allow cars with a particular sticker get through.  This makes people FEEL more secure.  However, for the cost (guardhouses and gates construction, guard salaries), it’s not as effective as it could be.  A thief can still walk in just as easily (gates only block roads), and when driving a stolen car out, the guards will see the car and sticker, recognize it, and let them leave.  If they had thought about how thieves operated, then they would have realised this and done something more effective, perhaps hiring the same number of guards, but setting them on a patrol, instead of just sitting at their posts.  With unlimited resources, they could do both things, and give each member a special remote key-code to unlock the gate when they are driving.  However, the tradeoff in cost and convenience is too high for them.

This is how security is, in the physical and electronic worlds.  We have many possibilities, each with their tradeoffs.  Deciding which measures to implement requires us to understand how our opponent is going to operate, as well as the details of how exactly our defenses work.

In this series, I’m going to show you how to crack simple code.  I’m going to make a series of samples to try this out on (to avoid DMCA problems with real code), so as to get a feel of what crackers do to code.  It is not going to be in-depth or show how to become a master cracker.  Just enough so that we could attack a simple Windows/.NET program’s licensing key system, which is a common theme in software protection.

Continue to Part 1, where we’ll crack some simple code…

Cracking code - Part 1
http://www.atrevido.net/blog/PermaLink.aspx?guid=ec99e239-8917-48e3-bd4f-af866b730150
Cracking code - Part 2: Other simple attacks
http://www.atrevido.net/blog/PermaLink.aspx?guid=f2b7825e-1a8b-4beb-adf0-215011fd89e0
Cracking code 3: Cracking an obfuscated .NET assembly
http://www.atrevido.net/blog/PermaLink.aspx?guid=8315fa01-0286-47ce-a20b-fcc15eb297c3
Cracking Code 4: Replacing a strong name
http://www.atrevido.net/blog/PermaLink.aspx?guid=f772c18a-f389-4c28-bd6a-a30f4ccc84f5
Cracking code 5.1: Increasing your configuration
http://www.atrevido.net/blog/PermaLink.aspx?guid=92b5d25e-e53a-459c-b2c1-77aa26544880

WinHex Virus?
From time to time there appear proof-of-concept viruses for various platforms and applications that have their own scripting language interpreters. Almost a year ago a proof-of-concept virus for IDA (Interactive Disassembler Pro) appeared. IDA is our primary tool for reverse-engineering malware. No one in the industry was infected. As far as we know.

A few days ago someone sent us a new proof-of-concept virus. This time it was for WinHex, the powerful computer forensics, data recovery, and IT security tool. The virus prepends itself to all available .WHS (WinHex script) files. The infected WinHex scripts stop working and the only thing that they can do at that point is to spread the virus further. We named the virus “Vred.A”. Here’s a short description for the virus…

The developer of WinHex has been notified of the case.

Name :  Virus:WH/Vred.A
Type: Virus
Category: Malware

Summary 
Vred.A is a proof-of-concept virus for WinHex.

WinHex is a powerful computer forensics, data recovery, and IT security tool.
 Back to the Top

Detailed Description 
Vred.A is a proof-of-concept virus that is written in script language, that is used by the powerful computer forensics, data recovery, and IT security tool called WinHex.

Here’s a screenshot of the WinHex utility:

The virus contains less than 20 commands that allows it to look for all available .WHS (WinHex script) files and to prepend itself to them. As a result all infected scripts stop working until the virus’ code is removed from them.

It should be noted that WinHex shows a warning before running any script, so the virus can not replicate without user’s interaction:

hi

in this paper he tries to create a classification which will help when identifying them once theyhave
appeared and  establish the base for future papers about building secure system from a software
engineering point of view

link:

hi

This flash movie covers how to manual unpack and Auto-IAT fix UPX and Aspack packed binaries. It might be useful for people who are new to malware analysis and don’t have a clue how to unpack and repair a binary. The introduced technique works for many other easy executable packers like FSG too. For best view use a resolution of 1024×768 or higher and select fullscreen (F11) in your browser

link:

hi

today i want to give u the best collection

this is the Code Breakers Collection:)

links:

http://rapidshare.com/files/37261731/CodeBreakersCollection.tgz