TERMINAL
REBELS
Play

TERMINAL REBELS / WIKI

Gaining server access

Access depends on your certification, running tools and the target's defenses. A tool sitting on disk does not help until it is running. Compare requirements before starting an attack, and leave enough resources for the work itself.

Pick an approach

  • Password attack: a Cracker works against the target's Hasher. A known valid password can instead be used at login.
  • FTP exploit: targets file-transfer access. FTP permission alone does not grant all server controls.
  • SSH exploit: targets access to software and logs. The target's Firewall matters for exploit attempts.

Run a port scan when your certification and tools allow it. The result helps you choose a reachable service. Scanning does not open that service for you, and a saved scan can become outdated. Some accesses also require the relevant tool to keep running.

A normal server crack may target a Hasher up to 2.0 versions above your running Cracker. Underpowered attempts take longer and are easier for active Sentinel to detect. A detected attack reveals its outgoing game IP in the target log. Bank and wallet cracking and exploits retain their own requirements.

While the attack runs

Keep the necessary connection and watch Task Manager. A protected target can delay progress through Lockdown or Sentinel. A control-node intrusion is an optional way to contest active defense; it does not replace the normal hack or grant root access by itself.

After connecting

Use only the operations your access permits. Uploading a virus and installing it are separate actions. Existing files, logged connections and readable documents may contain useful observations, but a successful login does not reveal every secret on the server.

Your own server remains part of the network while you attack. Review its running protection and logs. Removing a log on one machine does not erase traces from every other machine involved.