User Tools
This is an old revision of the document!
This will be a dump of various bits and pieces of undocumented decking knowledge.
1. Canonically the Matrix requires a subscription to use. Because you're a fly-by-night shadowrunner who refuses to pay the corps their nuyen, not that you have a SIN to pay with, *any* intrusion into the Matrix is considered a hostile one. This means as soon as you step foot into it the tally (alert) level begins to climb.
2. Analyze host is not the only analyze action you can perform. As it turns out there are subsystems and built-in IC to hosts. You have to analyze the sybsystems to get it. Analyze files analyzes the files subsystem, and analyze slave detects for slaved programs and hosts. Hosts can have their own File subsytems and Slave subsystems, which can not only protect and encrypt host data, but also dump you into different locations if triggered. Decrypt file(s?)/decrypt slave is how you untangle that mess. It also shows trapdoors this way and you can find them/take them manually, and there are possibly hidden nodes around that require this.
3. Exits themselves (SANs) can be encrypted and there are several bugs on how it is documented.
- locate host blah
- → Your search returns the address blah.
- logon blah
- → You fail to gain access to the host.
- # The target room has an AccessScramble value, which blocks remote login. But it could be the source room blocking, so…
- analyze access
- → There is nothing out of the ordinary about that subsystem.
- # Well, now what? (This is what usually keeps people from logon. But the source room has no encryption. So decker has bright idea:)
- analyze blah
- → Analyze what? (That doesn't work…)
- help decrypt
- → helpfile shows no ability to decrypt exits/SANS exists
- # But finally if you just do it anyway:
- decrypt blah
- → You successfully decrypt that SAN.
So, the room is not the SAN, the exit is. An access-encrypted room should prevent movement in.
