"the responsible persons" ... hmmm. Who would that be?
The programmer who implemented the code? Do you think they thunk these tricks up? They was just following orders.
The manager of the programming team, who set these tricks as things that needed to be implemented? Again, just following orders.
The "Cxx" Title people who directed that there be "some protection" in some way that got implemented as what we see? Did they specify these measures? Did they say "it should break if serviced by a competitor?" Unlikely. Thye wouldn't know how to be that specific, probably.
Some middle manager, maybe a committee meeting, sketched out a "DRM" scheme with the specifics? What do you imagine that meeting looked like? "We've got a directive to secure the systems from outside tampering, what does that mean in terms of how the machine behaves?" Or does that bring us back down to the engineers again?
... the responsible part here isn't a person, its the company as a whole. Just as it took the collective efforts of everyone to make the train, it took their collective efforts to make it wrong.
Corporate Death Penalty; perhaps. make it plain that we will no longer tolerate sill shenanigans like this.
> "the responsible persons" ... hmmm. Who would that be?
But that is the thing. We do not know who is responsible without an investigation.
We don't need to guess. The local responsible agency should get a warrant and take a copy of their code repo and their internal comms. And then they need to spend the time (call in experts if needed) to figure out what happened and who was involved.
If it is normal code development you can find all the paperwork which documents the change. If they tried to disguise it, (which they might have, or might not) then that is some maffioso stuff and you take the tools police use to break up organised crime groups. You take a low level person who you can incriminate and you flip them. You show them that you have enough to send them to a prison for years and offer them the opportunity to cooperate.
The programmer who implemented the code? Do you think they thunk these tricks up? They was just following orders.
The manager of the programming team, who set these tricks as things that needed to be implemented? Again, just following orders.
The "Cxx" Title people who directed that there be "some protection" in some way that got implemented as what we see? Did they specify these measures? Did they say "it should break if serviced by a competitor?" Unlikely. Thye wouldn't know how to be that specific, probably.
Some middle manager, maybe a committee meeting, sketched out a "DRM" scheme with the specifics? What do you imagine that meeting looked like? "We've got a directive to secure the systems from outside tampering, what does that mean in terms of how the machine behaves?" Or does that bring us back down to the engineers again?
... the responsible part here isn't a person, its the company as a whole. Just as it took the collective efforts of everyone to make the train, it took their collective efforts to make it wrong.
Corporate Death Penalty; perhaps. make it plain that we will no longer tolerate sill shenanigans like this.