(crossposted at Shadowrun4 forum)
I'm requesting a rules check as it looks to me as though there's a defense against (some) spoofing.
Put a databomb on the access port.
As I read the rules, to issue a command (with the access ID) the node must be accessed.
Now I'd not put this on devices that have a wide range of interaction. Putting them on the slaved drones and other devices, however, looks to me like a nice way to cover the only weakness of slaved devices -- their vulnerability to spoof attacks.
However, I'm still learning and could be wrong, so I'm asking for a doublecheck. Thanks.
Full Version: Data Bombs and Spoof
MM, i dont think so, since the DB only goes off if someone is unauthorized, if they spoof and succeed they're authorized, however,i would say if they spoof and fail, then it could go boom
No, you set a different passcode for the data bomb.
and
On the other hand I maybe found the answer, in the middle of those two quotes.
The question is whether spoofing is logging on for that single command. Just as with hacking on the fly and probing it has to deal with a firewall check. Unlike either, a failure means no alert as the command is considered 'just a bad packet' and discarded.
I know that as GM I'll have to make up my own mind, but I'm looking for some clarity for basis. at this point probably not, but the possibility...
QUOTE
When you [set a data bomb], you must
choose the rating for the data bomb (up to the rating of the Data
Bomb program), whether or not it will delete the file or crash the
node to which it is attached when activated as a secondary effect, and
the passcode required to deactivate it.
choose the rating for the data bomb (up to the rating of the Data
Bomb program), whether or not it will delete the file or crash the
node to which it is attached when activated as a secondary effect, and
the passcode required to deactivate it.
and
QUOTE
If the passcode is used, the data bomb does not activate
and remains attached to the file or node.
and remains attached to the file or node.
On the other hand I maybe found the answer, in the middle of those two quotes.
QUOTE
The way a data bomb triggers depends on whether it is attached
to a file or a node: it activates when a file is accessed, or when an icon
logs onto a node, respectively, without using the data bomb’s passcode.
to a file or a node: it activates when a file is accessed, or when an icon
logs onto a node, respectively, without using the data bomb’s passcode.
The question is whether spoofing is logging on for that single command. Just as with hacking on the fly and probing it has to deal with a firewall check. Unlike either, a failure means no alert as the command is considered 'just a bad packet' and discarded.
I know that as GM I'll have to make up my own mind, but I'm looking for some clarity for basis. at this point probably not, but the possibility...
I'd say no, it's doesn't count as a login - after all, you're not hacking the node's login mechanism, and while spoofing a slaved device you can't as a result login to the node it's slaved to. But ymmv.
Databombs only affect you if your logging in, if your spoofing your not logging in. By design slaving is vulnerable to spoofing there should not be a 100% foolproof unhackable system anyway.
Lurker, this wouldn't make it unhackable.
It would just make it a bit more difficult/risky to spoof. (grin)
It would just make it a bit more difficult/risky to spoof. (grin)
Spoofing is not logging in. It's touchless. Even if the data bomb could go off, there's literally nothing there for it to hit.
hurray for right answer, wrong reason 
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.