This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
trix_traps [2022/01/04 10:51] – jack | trix_traps [2024/03/20 18:24] (current) – Crosslinking as suggested in Discord. bloodninja | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | This will be a dump of various bits and pieces of undocumented | + | This will be a dump of various bits and pieces of miscellaneous |
- | 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 | + | Alternative representation and additional information |
- | 2. Analyze host is not the only analyze action | + | 1. Canonically |
- | 3. Some Colus notes. | + | 2. 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. | + | |
- | analyze access | + | |
- | -> There is nothing out of the ordinary about that subsystem. | + | |
- | # Well, now what? (This is what usually keeps people from logon. | + | |
- | analyze blah | + | |
- | -> Analyze what? (That doesn' | + | |
- | 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. | + | |
- | Colus — 07/ | + | |
- | So, the room is not the SAN, the exit is. An access-encrypted room should prevent movement out, not movement in. If encrypted SANs (Matrix exits) are a goal, then matrix exits should be ' | + | |
- | Colus: | + | So, the room is not the SAN, the exit is. An access-encrypted |
- | Related to that, 'you fail to X' messages when trying to do things involving encrypted subsystems are unhelpful. | + | |
- | Since it' | + | |
- | This came about when Khai was trying to decipher the one place in the game where a remote host (that has host encryption baked into the host) requires you to decrypt it remotely. | + | |
- | Colus — 07/ | + | |
- | Specifically, | + | |
- | It is a featureless cyberdeck. | + | |
- | Custom Components: | + | |
- | FUPS Port 2 Type: Ports (FUPS) | + | |
- | FUPS Port 1 Type: Ports (FUPS) | + | |
- | (The 2nd port has two closed color codes, notice the 8-char difference.) | + | |
- | Colus — 07/ | + | |
- | Yes, speaking to that: In SR3 base you technically aren't able to analyze a host to see if it's decrypted before entering it, and theoretically nothing prevents you from entering it. Once you're in, if the access subsystem is encrypted, you can't do any kind of logon operation until the encrypting IC is removed. | + | |
- | Colus — 07/ | + | |
- | (MM 98, talking about Encrypt Access actions) | + | |
- | The opposite of Decrypt Access, this operation allows the user to encrypt a system’s access nodes. If successful, the Access subsystem will be encrypted and no one will be able to log on without first succeeding in a Decrypt Access operation. | + | |
- | + | ||
- | That implies encrypting access within a node prevents logons from outside. | + | |
- | + | ||
- | Colus idea: I just noticed (and didn't think about it until now!) that some IC in the game are Scramble IC. Canonically, | + |