![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
A guide to disaster.
Dec. 1st, 2004 10:16 amThe register has a nice piece about the DWP problems. The good thing about it is that it does not claim the problem is windows XP or EDS, easy scapegoats, but the "owner" of the system itself. It is their responsibility to check the safety of the work done by their contractors and to at least learn from their mistakes.
Defense in the depth is the only real solution, but personally I am starting to doubt why we are giving these end users PC's to start off with. Would a "dumb" terminal not be easier to manage and to adapt to the programs they need to use? Why spend millions on locking down XP when you could "roll-out" cheap terminals that connect to beefy servers in less time? I think that part of the problem is that the manager deciding to do so do not want to be "restricted" to running on "just" terminals, and they want their laptop. That and the fact that most programmers have no clue about network programming at all :-(.
Defense in the depth is the only real solution, but personally I am starting to doubt why we are giving these end users PC's to start off with. Would a "dumb" terminal not be easier to manage and to adapt to the programs they need to use? Why spend millions on locking down XP when you could "roll-out" cheap terminals that connect to beefy servers in less time? I think that part of the problem is that the manager deciding to do so do not want to be "restricted" to running on "just" terminals, and they want their laptop. That and the fact that most programmers have no clue about network programming at all :-(.
