Linked by Thom Holwerda on Sun 29th Jan 2006 20:12 UTC, submitted by mono
Windows "On Wednesday morning, I met with Microsoft co-president Jim Allchin, the man most directly responsible for Windows Vista and Longhorn Server, the company's upcoming client and server operating system releases. Allchin is a soft-spoken, intelligent man with decades of industry experience, the last 15 years of which were spent at Microsoft. I've run into Mr. Allchin at various events throughout the years, but the last time I sat down with him for a one-on-one meeting was in August 2001, when we discussed the then-upcoming release of Windows XP. With Windows Vista on track for a late 2006 release, Allchin hit the road to meet with members of the technical press."
Thread beginning with comment 90776
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Security ...
by -earthdog- on Mon 30th Jan 2006 06:08 UTC in reply to "Security ..."
Member since:

I agree with you on Vista, XP, and security issues. Proper prevention and a little common sense will take you a long way with Windows. I personally don't consider it a bad OS. XP does everything I need it to do and has always been very stable for me. Plus, I can always play the latest games, -yadda yadda- hardware -yadda yadda- all the other platitudes you hear in almost every thread.

All that said, I'm looking forward to Vista. Mostly. I still have a few political/social problems with what is going to be in it (DRM) and the fact that we can no longer buy a Microsoft OS outright. I don't even like to lease cars or apartments.

However, my biggest question to Microsoft will be if software that is installed on the machine (through user accounts, not the superuser) will be allowed to change system files. I'm not an OS expert, but it seems to me if Company A can come in and swap out a .dll at will, you're just whistling past the graveyard as far as stability and security goes.

Now, on XP, I've noticed user accounts have their *own* WindowsSystem file, though I've never seen any software I've installed make use of it. Could this be used to solve the .dll swap-out and security probs? Sort of like all the .directories in *nix /home accounts?

If I'm off base here, let me know.

Reply Parent Score: 1

RE[2]: Security ...
by biteydog on Mon 30th Jan 2006 10:55 in reply to "RE: Security ..."
biteydog Member since:

3rd-party software is surely one of the problems - it's too tempting for developers to open up the system as much as they can so that installation and use are as universal and simple as possible (even at the cost of security) because <easy> = <less calls to the support lines> = <lower overheads> = <more profit>.

Reply Parent Score: 1