From Grey Hack Wiki
Jump to navigation Jump to search

Tracing is a dangerous thing to have happen to you when hacking. It has three causes, and one result: Game Over!


The primary cause of being caught is timing and not having AdminMonitor.exe running for a warning. When you are hacking an NPC Server, you have the chance of being caught due to an Admin being actively online to see your intrusion. When you hack into an NPC server, always run the ps command and look for the process: dsession, or something similar: this is the Admin! You need to clear the server log (See Below) and exit ASAP! Else, you are victim of an active trace.
The second cause of Tracing is a passive trace. A passive trace effectively runs when you leave a shell log entry (See Below) when you hack a system. The passive trace will run without you knowing (unless you have AdminMonitor.exe) and you will be caught.
The final cause of Tracing is being... framed! That is correct- you can be framed. When another hacker inputs YOUR IPs into a server with an Admin, the Admin will think YOU are the hacker, and passively trace you.


It is always a good mindset to startup AdminMonitor.exe when you startup the game. AdminMonitor.exe allows you to be actively notified of any form of tracing against you, and you can take preventative actions. The fastest way to ward off a trace is to switch WiFi networks. This works because your IP will be changed in adaptation to a new network router.


Proxies, used by [[Tool|Map.exe, are simply chains of SSH'ed computers that will make it longer for traces to get to the starting computer- you. Proxies can be created by buying NPC Servers from NPC Shops, and you can SSH into many of them- as many as needed!


To frame a user into getting traced & caught is simple- create log entries that trail back to the victim!

Importance of Logs

"It's log, it's log, it's better than bad, it good! (Blamo! - Ren & Stimpy - Cartoon Network's Adult Swim)"! That's right! Logs leave trails that Admin's can trace. To avoid this, simply go, on the victim's server, to /var/server.log, AND ALWAYS CHECK, TOO, IN /etc/! Open the file(s) and delete any related logs with your IP that contains any trace of opening the Shell.

Debug data: