Author Topic: reverse engieneering to ports  (Read 2090 times)

0 Members and 1 Guest are viewing this topic.

Offline gh0st

  • Sir
  • ***
  • Posts: 575
  • Cookies: 8
  • #DEDSec
    • View Profile
reverse engieneering to ports
« on: June 07, 2011, 04:15:56 am »
guys how do I make reverse engieneering to ports? using wireshark and then analyze the binary code with a tool made by me ?
« Last Edit: June 07, 2011, 07:34:28 am by gh0st »

Offline ande

  • Owner
  • Titan
  • *
  • Posts: 2664
  • Cookies: 256
    • View Profile
Re: reverse engieneering to ports
« Reply #1 on: June 07, 2011, 04:53:39 am »
You mean reversing a undocumented protocol(s)?
if($statement) { unless(!$statement) { // Very sure } }
https://evilzone.org/?hack=true

Offline gh0st

  • Sir
  • ***
  • Posts: 575
  • Cookies: 8
  • #DEDSec
    • View Profile
Re: reverse engieneering to ports
« Reply #2 on: June 07, 2011, 07:34:09 am »
hmm I meant fuzzing* I suppose
« Last Edit: June 07, 2011, 07:34:47 am by gh0st »

Offline ande

  • Owner
  • Titan
  • *
  • Posts: 2664
  • Cookies: 256
    • View Profile
Re: reverse engieneering to ports
« Reply #3 on: June 07, 2011, 04:11:46 pm »
hmm I meant fuzzing* I suppose

What are you trying to do? Find vulnerabilities in software using the net?
if($statement) { unless(!$statement) { // Very sure } }
https://evilzone.org/?hack=true

iMorg

  • Guest
Re: reverse engieneering to ports
« Reply #4 on: June 07, 2011, 05:16:25 pm »
Your question is unclear.

Do you mean reverse engineering software to see what port it is sending/receiving data through?

Offline ca0s

  • VIP
  • Sir
  • *
  • Posts: 432
  • Cookies: 53
    • View Profile
    • ka0labs #
Re: reverse engieneering to ports
« Reply #5 on: June 08, 2011, 02:12:24 pm »
I think what he means is to reverse a protocol used by an app running a service in a port. USe wireshark or any other sniffer and try to figure out how does it work, send data and try to guess how the app manages it...

xor

  • Guest
Re: reverse engieneering to ports
« Reply #6 on: June 09, 2011, 02:31:55 pm »
The way I have always reverse engineered an undocumented network protocol is to code a client and server at the same time.

Here's my process for example:

1. Run official client / server programs (if available, otherwise, just the client)
2. Note which ports they connect to / open to listen on
3. Write a quick program to listen on the server port.
4. Redirect the client to your server (lots of ways to do this, hosts file being one)
5. Run the client... see if it sends any data first. If it doesn't send data, the server probably initiates the hand shake. If it does send data, then ..
6. Start writing the client. If the client starts the initial hand shake, send the data to the server and see what you get back.
7. Add this response into your server and run the official client again.
8. Repeat the last few steps as necessary.

Once you start to grasp how the programs communicate with each other, you can start to understand how the actual communication works, then start writing a protocol spec.