comStar Firewall alert - PhaseThrough

node attributes like a metaphor or special sculpting. Most of the
time a user with security access is able to create or delete standard
user accounts, edit other users’ data, initiate (and deactivate) an
active alert, and read the access log (see Access Log, p. 65). Security
privileges also grant the ability to control and command all the
agents or IC deployed by the node and run hacking programs.
admin access rights
The admin level is reserved for an owner or someone responsible
for an entire node. Admin access grants the right to
do everything the user wants to on a node. Admin privileges
empower individuals to reboot the node, alter the node’s sculpting,
create and delete any possible account, assign access levels to
accounts, and assign privileges to account levels. Furthermore,
admins can view and edit all the log files and statistics available
on the node, including the access log (see Access Log, p. 65). An
admin cannot, however, affect programs and files he does not
know about. He has to first defeat the Stealth program of an intruding
agent that is running on the node before he can unload
the unwelcome guest.
coMMcodeS
Matrix service providers (MSPs) issue commcodes (see
p. 214, SR4), which are not to be confused with access IDs.
Whereas your access ID is a sort of serial number that you use
for all of your interactions online, and which is recorded in access
logs (like an IP address in real life), your commcode is more akin
to a phone number or email address.
In principle it would suffice to call somebody by sending a
phone request to the access ID of his commlink. The commlink
would receive the request and the phone call could take place.
On occasion, however, people buy new commlinks, leave their
commlinks at home, in another room, or simply want to take
their phone call, or any other kind of interaction, elsewhere.
That is why people register their devices at a Matrix service
provider that issues commcodes. Matrix devices can be set to register
with the Matrix service provider as soon as they go online.
Every time somebody dials the commcode, the communication
request is automatically routed through the database of the
MSP that knows which devices are available to receive the call.
Modern commlinks, house telecoms, and cars offer additional
convenience by providing the MSP with the information on
whether the user related to the commcode is present or not, so
the incoming call can be relayed to the appropriate device.
data excHange
In every data exchange, access IDs are used to guide the data
from the sender to the receiver. The receiver then automatically
knows where to send the answer. Thus both nodes, the sender
and the receiver, have to be aware of the other’s access ID for a
successful data exchange. Every node in between tries to forward
the traffic a little further to the receiver. In the wired part of the
Matrix, the nodes performing these relay tasks are the routers of
the Matrix’s backbone.
The wireless part of the Matrix is a decentralized mesh
network. This means that every node will work as a router for
all the other nodes around it. If a node wants to go online, it
just connects to the next available node around it, which in
Unwired
BeHind tHe SceneS
So what happens when you get online? When
you jack into or otherwise connect to your commlink
(or any other device), what exactly happens under
the hood?
Before anything, you must log on to the device.
This presumes that you have an account on the device
and a passcode (p. 215, SR4) for accessing it. Some
devices may have a public interface, meaning anyone
that picks it up can use it. When you enter the passcode,
the Firewall authenticates you and the operating
system fires up a persona interface for you.
When you engage the persona, several things happen.
First, you are immediately assigned an access ID
(p. 216, SR4) which stays with you for the duration
of your session. This access ID may be spoofed (see
p. 224, SR4), but this must be done before you open
connections to other nodes; otherwise, the switch in
access ID will immediately sever all of your connections.
Second, you gain access to all of the privileges
your account offers (p. 216, SR4). Third, you gain access
to all of the programs and data stored in the device
that the account has access privileges too. You may
run these programs, loading them into active memory,
at which point they count against the node’s processor
limit (p. 48). Fourth, you are assigned an icon that
represents you in AR or VR interactions, which you
may modify as you see fit. Fifth, your persona informs
your Matrix Service Provider that you are online and
that your commcode should be routed towards that
particular node and access ID, so that you receive all
of your messages and calls.
Other users may use the same node as you, of
course, interfacing through their own, separate personas.
Programs that they run also count against
the node’s processor limit, of course, which is why
nexi are better equipped for multiple users than
standard nodes. (Note that even peripheral nodes
have persona interfaces, though these are obviously
more limited.) Other personas from the same node
will not have the same access ID as you, though all
such access IDs will leave a datatrail that leaves
back to the same node (and, in particular, a specific
account on that node).
From your persona interface, you may access
other nodes. If you are simply making a comcall or
data request, accessing a public site or profile, or
otherwise connecting to a public account, no subscription
or login is required—your access ID suffices.
If you are logging in to a user/security/admin account,
communicating with encryption, controlling
an agent/drone, or making some other bandwidthintensive
connection, a subscription is required, and
counts against your subscription limit (p. 51). Your
activity is logged, of course, creating a datatrail that
may be used to track you (p. 55).
Simon Wentworth (order #1132857) 9
53
Matrix topoloGy . . . . . . . . . . . . . . . . . . . . . . . . . . . . .