comStar Firewall alert - PhaseThrough

hacker’s handbook . . . . . . . . . . . . . . . . . . . . . . . . . .
104
a note on coMManding deviceS
There’s more than one way to rig a drone. The same is true
for other devices controlled through the Matrix. Here’s a quick
and handy reference guide.
issue remote commands
You may remotely command any device that you have subscribed
to your persona (p. 221, SR4) with a Simple Action (see Issuing
Commands, p. 221, SR4). You do not need to be in the same node as
the device, as long as it is subscribed and your command can reach
them. Multiple devices may be controlled as a single subscription,
but this means they all receive the same command. Nodes, devices,
agents, drones, sprites, etc. may all be commanded this way.
In this case, the commanded device acts on the orders independently
on its own action. Pilot + autosofts are used for any
relevant tests. If the orders are complex, the gamemaster can
roll Pilot + Response to see if the device comprehends them
(see p. 111). More complicated orders can be issued in the way of
scripts (see Agent Scripts, p. 105).
remote control
Rather than letting the device operate on its own, you may
access it directly via AR or VR, using the Command program (see
Controlling Devices, p. 220). You must either log in to the device
or subscribe it to your persona. The program provides you with
a virtual interface, allowing you to control the device like a video
game. Most devices have built-in Command programs, which
you can run if you lack your own.
A remote-controlled device acts on your Initiative. All tests
are made by you, using Command + an appropriate skill. For
example, to fire a gun emplacement, you would roll Command +
Automatics. To maneuver a rotordrone around a tree, you would
use Command + Pilot Aircraft +/– Handling.
Devices, agents, and drones may all be remote controlled
this way.
Jump in
Your final, and most direct, option is to “jump into” the device
with a Simple Action via full-immersion VR (see Jumping Into
Drones, p. 239, SR4). This is only possible with devices that have
rigger adaptation (p. 341, SR4), typically drones and vehicles. In
rare occasions, other devices will feature rigger adaptation.
Devices rigged this way act on the rigger’s Initiative, and
tests are made using the rigger’s skill + appropriate vehicle attribute
(see Common Rigger/Drone Tests, p. 105).
multiple levels of access, linked passcodes or nanotech passkeys, encryption,
data bombs set to activate during off-hours, and proactive
IC. If a hacker does manage to access a nanofax or nanoforge, they’re
limited to producing items that the nanomanufacturing device that
they have the correct feedstocks to produce, and has nanoschematics
for. Nanofaxes are further limited in that they can only create a specific
type of gear, such as personal microtronics or pistols. If a nanofax
or desktop nanoforge is compromised (an Active Alert) instead of
shutting down it will self-destruct. Stolen nanofaxes and desktop
nanoforges are typically ordered to self-destruct wirelessly, or do so
Unwired
automatically when they leave the range of the wifi
network of the building they are in.
Nanoschematics are kept in high-level security
nodes, and legitimate users download them by logging
onto the node with their passcodes and then
verify their log-on by sending a valid license number
that is hard-coded into the nanofax processor. The
nanoschematics are encrypted when downloaded
from the secure node. Provided the character has
access to a nanofax, finding the license number
requires a Hardware + Logic (4) Test. A nanofax
license number only works with the appropriate
matching account. Nanoschematics cost serious
nuyen, and few show up on peer-to-peer file sharing
networks (see Piracy, p. 94)
proxy Servers
A “proxy server” is a program routine that
acts as a go-between, transferring data from a user
(the “client”) to another user or node. The advantage
to proxies is that they act as an intermediary,
so the data seems to be coming from the proxy
rather than the client. Hackers and shadowrunners
find proxies very useful both as anonymous
remailers (obfuscating the original message
source) and to foil tracking attempts.
Almost any node can be configured to act as a
proxy server, though this typically requires admin
access and a Computer + Edit (10, 1 Initiative Pass)
Test to set-up (use Hacking in place of Computer
if you do not have admin privileges). Once set up,
messages that are sent from a client through the
proxy server node will seem to have originated
from the proxy node. In order to determine the
source of a message, a hacker would need to trace
the message back to the proxy server node and then
hack that node’s access log (or request it from the
admin/owner of the node, if they are cooperating).
Anonymizing proxy servers are often set to not
keep or to delete message transfer logs.
A hacker can also route his connection through
a proxy server as a means of hindering traces. This
increases the threshold by +4 for Tracking Tests
for each proxy server used. The drawback, however,
is that each proxy server reduces the hacker’s
Response by 1.
Spotting traces
It can be advantageous to know when someone is trying to
track your datatrail (see Track, p. 219, SR4), so that you can redirect
the trace or otherwise make haste. In order to spot a trace, you
must be in the same node that the track attempt is launched in (if
someone is attempting to track your datatrail from the access log
of a node you are no longer in, for example, you will not know).
Spotting the trace requires a simple Matrix Perception Test (1)
Test. However, if the tracker is trying to keep the trace discreet,
you must beat them in an Opposed Test pitting your Analyze +
Computer versus their Track + Stealth.
Simon Wentworth (order #1132857) 9