Shadowrun

Catalyst Game Labs => Errata => Topic started by: Sentinemodo on <01-03-12/0426:48>

Title: response vs system rules (SR4A rules, Unwired examples)
Post by: Sentinemodo on <01-03-12/0426:48>
in SR4A
Quote
System
System measures the power of the device’s operating system (OS)
software. This includes its stability, multitasking properties, ability to
control hardware, resources, and the general quality of its code. If the
System software ever crashes, the entire device crashes. System limits
the rating of programs running on the device, and sets the limit on most
devices for the number of programs that can be run without a Response
drop. The System program is limited by the base Response rating of the
device it is on: if the base Response rating of the device is lower than the
System rating, then the System rating is set to equal the Response rating.
System also sets the size of the Matrix Condition Monitor of persona
programs running on the device (Cybercombat, p. 236).

Then in the example of peripherals and nodes in Unwired, pg. 204

Quote
Sample peripheral nodes
DeviceResponseSignalSystemFirewall
AR Glove2211
Credstick2266
Fridge1321
RFID tag1111
Security Camera2324
Smartgun2134

Examples of Standard nodes
NodeResponseSignalSystemFirewall
Standard Home Telecom3333
Premium Telecom4344
Business/Retail Terminal3344
Public Terminal2122
Civic/MSP Wireless Access Point3635
I've marked the examples conflicting the rules from the core. I don't care about the fridge, but credstick limited to system 2 and consequently to firewall 2 is a problem.
The simplest solution would be to increase the response and system to the required firewall, but I think that the problem is actually response limiting system rule, which should be removed.

The secondary problem with this example is the low rating of credstick. I've seen technomancers out-of-chargen TMs who could crack through firewall 6 easily, especially that credstick isn't going to have IC and security spiders inside.
Title: Re: response vs system rules (SR4A rules, Unwired examples)
Post by: Sentinemodo on <01-03-12/0509:32>
For the sake of completeness, I've seen the explanation of peripherals on Response vs System rating (pg. 48 Unwired).
it does not explain the errors in standard nodes examples
it is a workaround at best (linear system, single persona etc.) and it remove the +6 treshold for getting them cracked. which increase voulnerability of credsticks even more.
Title: Re: response vs system rules (SR4A rules, Unwired examples)
Post by: FastJack on <01-03-12/0756:27>
Firewall is hardware, so it is not limited by Response or System ratings. In the case of the Credstick, this means that it would operate at a Response 2, a modified System rating of 2 and a Firewall of 6.
Title: Re: response vs system rules (SR4A rules, Unwired examples)
Post by: Sentinemodo on <01-03-12/0806:52>
Quote
Firewall
Firewall is the device’s built-in security software. It protects against
unauthorized access and fends off hostile access attempts and exploits.
A firewall will, for instance, instantly block access to multiple icons
using the same access ID. Firewall is also used to defend against Matrix
attacks in cybercombat (p. 236).
While I understand the existence of security hardware, they are limited to crypto-processors (which access memory in strongly random method, and are protected against physical scan revealing the content of the registers). The actual firewall is a software package operating on given hardware.

Also, firewall is listen under matrix programs and programs rating are limited by system.
Title: Re: response vs system rules (SR4A rules, Unwired examples)
Post by: FastJack on <01-03-12/0825:41>
Quote from: Sentinemodo on <01-03-12/0806:52>
Quote
Firewall
Firewall is the device’s built-in security software. It protects against
unauthorized access and fends off hostile access attempts and exploits.
A firewall will, for instance, instantly block access to multiple icons
using the same access ID. Firewall is also used to defend against Matrix
attacks in cybercombat (p. 236).
While I understand the existence of security hardware, they are limited to crypto-processors (which access memory in strongly random method, and are protected against physical scan revealing the content of the registers). The actual firewall is a software package operating on given hardware.

Also, firewall is listen under matrix programs and programs rating are limited by system.
My bad, I'm always getting the Firewall mixed up. It is software.
Title: Re: response vs system rules (SR4A rules, Unwired examples)
Post by: Carmody on <01-04-12/0718:19>
I have always considered that firewall, while being software is a matrix attribute and that therefore the program < system rule does not apply to it.
Title: Re: response vs system rules (SR4A rules, Unwired examples)
Post by: Mirikon on <01-04-12/0723:49>
Quote from: Carmody on <01-04-12/0718:19>
I have always considered that firewall, while being software is a matrix attribute and that therefore the program < system rule does not apply to it.
I'd agree with this point of view.
Title: Re: response vs system rules (SR4A rules, Unwired examples)
Post by: Netzgeist on <01-04-12/0735:37>
Quote from: Mirikon on <01-04-12/0723:49>
Quote from: Carmody on <01-04-12/0718:19>
I have always considered that firewall, while being software is a matrix attribute and that therefore the program < system rule does not apply to it.
I'd agree with this point of view.

That's what the FAQ say, it's sad that SR4A does not expand on the matter.
Title: Re: response vs system rules (SR4A rules, Unwired examples)
Post by: Sentinemodo on <01-04-12/1028:00>
Quote
Matrix Attributes
Devices have Matrix attributes: Firewall, Response, Signal, and System.
Two of the Matrix attributes are based on the hardware in the device,
and the other two are software running on that hardware

Both are listed in matrix program tables costs (namely rtg*200 nuyen up to 3 and rtg*500 nuyen up to 6 for Firewall).

Note, that none of the core rulebook operating systems or any of the examples there have violate the rule of Firewall <= System <= Response.

While researching the subject however, I found out that in unwired matrix nodes (commlinks, nexi) are consistently using cases of Firewall > System > Response. Examples are security consultant template, examples of matrix nodes, examples of prepackaged nexi. If this is the intended way (probably intended by Unwired author, but not by SR4A author) the errata should be made into SR4A clearly stating that Firewall are not programs (though they are software) and peripherals are not nodes (in sense their system can be greater then response).