Hi there, there are a few systems based on NT other based on Linux and other based on pure assembly and deticated H/W. You had an expirence with an NT based box that for some reason did not implement any security (even a basic one). This ofcource is not acceptable at all. So I disagree with anyone that says "you have to be locked in..." In my opinion it would be OK if you just notify the hotel about the issue so that they would take further actions (implement at least a basic security). As about passwords: ppl, everyone knows that an easy to remember pass is a company's or a product's name, so spare me. I know it is wrong but this kind of pass had been used for a quite long time. Not to mention that the techies that do the installations are not computer freaks (at least the ppl I know of;) so... They trying to make their life easyer (and hackers/crackers or just curious ppl happy:).
Yep, sometimes the security is a major aspect. But let's say that some organization has some custom S/W developped internally for some funcy job. Let's also assume that this is a service running under some "user impersonation" and MS desides to change the security behavior of Win2K server, in this case the organization may have to stop functioning until the IT dep rewrite the service (this is acceptable in case of non mission critical services), but let's say that this service is serving a SCADA system that is responcible for making sure that all the equipment is functioning properly and it fails. If some one got hurt by S/W failure that is due to incompatibility with the latest updates of O/S who is to blame?
Slashdot Mirror
Hi there, there are a few systems based on NT other based on Linux and other based on pure assembly and deticated H/W. ;) so... They trying to make their life easyer (and hackers/crackers or just curious ppl happy :).
You had an expirence with an NT based box that for some reason did not implement any security (even a basic one). This ofcource is not acceptable at all.
So I disagree with anyone that says "you have to be locked in..." In my opinion it would be OK if you just notify the hotel about the issue so that they would take further actions (implement at least a basic security).
As about passwords: ppl, everyone knows that an easy to remember pass is a company's or a product's name, so spare me. I know it is wrong but this kind of pass had been used for a quite long time. Not to mention that the techies that do the installations are not computer freaks (at least the ppl I know of
Cheers
Sakis
Yep, sometimes the security is a major aspect. But let's say that some organization has some custom S/W developped internally for some funcy job. Let's also assume that this is a service running under some "user impersonation" and MS desides to change the security behavior of Win2K server, in this case the organization may have to stop functioning until the IT dep rewrite the service (this is acceptable in case of non mission critical services), but let's say that this service is serving a SCADA system that is responcible for making sure that all the equipment is functioning properly and it fails. If some one got hurt by S/W failure that is due to incompatibility with the latest updates of O/S who is to blame?