writes: While this is really a case of bad password management rather than hacking, I'm still disturbed that this remote disable/honking system is in existence. What's next? Disco Lights or doors that won't lock in houses when people are behind on mortgages? Apparently, he was really good with computers.Link to Original Source
writes: I've been given the task of designing the architecture and common tools for our new 3-tier .net environment with oracle. Some of our users are in the UK, which means we need to support globalized dates. I've argued that globalization is a job for the presentation tier, and that everything below that should use the provided date data types. I'm getting a lot of resistance from the other developers however. They're claiming that the best way is to store the dates in the database in yyyyMMdd format in varchar fields, or at least convert them all to that before returning from the stored procedures. This is obviously a bad idea. But I've argued this 100 ways and they refuse to "get it". Can anyone suggest a source I can point them at to educate them on proper system design?