[grumble]

Except that spoof only works if you have a valid ID to work from, if there's no way to analyze something to get a valid ID then basically it's a closed system. And closed systems are bad from a gameplay standpoint.

I imagine that a character can get an id from a data trail in a pinch or from a previously hacked account/node?

but it may take too long to travel that route. Assuming its the right ID that is 

[grumble]

id like to add intercepted traffic for a possible id source too.

[UmaroVI]

Also, only slaves, peripherals, and things with Pilot are spoof able anyways. "Allow haxxor y/n" options are not a good thing.

[lurkeroutthere]

Yep pretty much.

[Dog Boy]

Except that spoof only works if you have a valid ID to work from, if there's no way to analyze something to get a valid ID then basically it's a closed system. And closed systems are bad from a gameplay standpoint.

Well, I agree. Just a debate about RAW, or at least consequences of various interpretations.

However, thinking about it, this is the way to make it completely abusable:

It's been established that banning an access ID from a system is insufficient in and of itself to remove the user's _current_ subscription from the system. You have to terminate connection, or do some admin-y stuff to remove them from the subscription list.

So, consider the following scenario:

(i) Take over a node
(ii) Disarm or disable any offensive IC
(iii) Terminate connection of any spiders
(iv) Apply policy of "_no_ access IDs allowed to connect to node"
(v) Remain on node like a hacker pimp.

At this point, if it were the case that Hacking on the Fly could not circumvent the access ID ban, then you would have an unhackable node, which is definitely not something we ever want.

[lurkeroutthere]

Yes, that's kind of our point. If it could be done it would be done all the time.

[Dog Boy]

Also, only slaves, peripherals, and things with Pilot are spoof able anyways. "Allow haxxor y/n" options are not a good thing.

[See post: I agree, abusable scenarios are not a good idea]

It is worth pointing out that what I was proposing was not a 'spoof of the node', but rather spoofing your access ID at the source. I was referring to the fact that you can alter your access ID (Hacking + Software (2) temp, Hardware + Logic (2) [permanent, or free for technomancers). This would allow you to circumvent an admin command of 'ban all access IDs except that of my own' when logging into the node.

This does bring up a question:

Can an access ID be logged into a node twice? It seems not, given that agents (at least) have this restriction (pg 110, UW).

[grumble]

If you spoof your ID before sending it to a node, and im assuming that its not an ID listed on the defending node......

but i dont think that's what your trying to do.
or...

Changing (spoofing) the access Admin account's access ID to a slaved node. would have no  positive effect since;

either your already a trusted subscriber to the slave node as you already hacked the node your on.
or the spider's ID is still the only legit ID after issuing the command.

[Katrex]

well no access ids alowed to connect... well what would the point in the node be then. I mean you might as well turn off wireless (unhackable). I dont see the problem. But you could still find an exploit that convinced it not that you conected to the node but had always been there. Thats the point of exploits, its and unforseen counter. So even to No access ids can connect there will still be exploits. But even if it was unhackable dont see the problem.