QUOTE (Jack VII @ Apr 5 2014, 09:23 AM)

I believe the Spoof Command has to come from the owner. I'm not sure if a Host can be considered an owner. I'd say no as it seems just a bit too powerful.
QUOTE (Xystophoroi @ Apr 5 2014, 10:37 AM)

In a corp site, who is the owner of a security camera? Or a maglock or computer archive? If a Corp. Security guard has a gun but the gun is owned by their Corp and not them I need to get a Mark on...Ares Macrotech if I want to Spoof Command the gun? 'Cos that sounds like it will end badly. Spiders may not be on every site but Ares Macrotech almost certainly has a Spider checking their 'owner' id...thingy.
For a Host system, and probably for a corporate facility's gear not on a host too, the Spider is considered the owner of the devices.
Page 360 "Since spiders are considered the owners or administrators of a system, they can command any of the devices in that system without having to gain any marks, since they already have the owner mark for all devices. "
That means if you want to spoof commands to a device inside a host, you need to have a mark on the Spider, not the host.
QUOTE (Xystophoroi @ Apr 5 2014, 10:37 AM)

Can you tell who the owner of a device is?
Maybe. Ownership counts as having 4 marks on a device, so if you use matrix perception to look at a device icon, you can examine it's marks. Marks do not carry an ownership "name" but it's possible to ID marks to a persona you are familiar with.
Page 220: "Seeing a mark does not automatically tell you who put it there, though. Usually, you can only recognize a mark if you have already seen the persona responsible for the mark, or if you’re familiar with his or her marking style."
QUOTE (Xystophoroi @ Apr 5 2014, 02:53 PM)

Crack File is an Attack action so simply attempting it immediately alerts the target (and thus owner) that they've been attacked. Simply trying to open a locked file alerts the system that there's a Hacker about actively attacking it so I don't see that as a useful option until the closing stages of a run when you're already preparing to leave.
Trying to open a file doesn't alert anyone. Succeeding alerts them. Attack actions that
fail bounce off the firewall and raise no alerts (although they do increase OS and they can damage the persona that attempted the attack as it rebounds back onto them.)
Success at cracking a file's protection alerts the file's
owner, which is not necessarily the Spider, and isn't directly the host. Hosts aren't personas and can't own anything.
Most files a shadowrunner would be sent to steal aren't owned by the Spider. A research data file would be owned by the researcher, for example. You could crack the protection on such a file inside the Host, and for the Spider to know the researcher would have to notice (hopefully he's asleep) and then they would have to contact the spider.
It's still a mess. Cracking protection should really be a Sleaze/Attack option, and the complete lack of a legal way to remove protection is a prime example of the poorly executed matrix rules.
In theory, protecting a file is somewhat like encryption combined with DRM. No one can do anything with the file, owner included, until the protection is removed, which is again silly when you note the lack of instructions for removing protection legally. I personally consider it to be a password situation, just like setting a databomb. If you feed the protection the correct password the encryption is removed and you edit and work with the file normally, depending on marks/ownership as usual.
QUOTE
As an aside. There's this whole bit on ownership needing to be changed with extended hardware tests while it instead looks like a use of the Format Device action would make the stolen goods impossible to trace anyway, thus removing the risk of sending a warning about you failing to switch it over. Stealing stuff is much easier than it was made out in the ownership section...
A formatted device can not connect to the matrix and does not gain any wireless bonuses. This doesn't change ownership, because ownership is partially on the grids, not just the device. Page 236: "Ownership, at least in the Matrix, is something that is registered with both the device (or other icons) and the grids, so it’s a bit more involved than just putting a “Property of [blank]” sticker on it." Formatting just keeps the device off the matrix, which you can just as easily do by shutting it's wireless off manually if you have physically stollen the thing. The fact that a Hardware check is needed to alter ownership illegally implies that you're doing something akin to removing/replacing the ID chips in the device so that it's no longer matches the ownership listings out on the grid.
Of course if the object also have a few tags on/in it, you'll need to disable or destroy those too... or jam them with noise until you can deal with them.