Linked by Thom Holwerda on Sat 28th Jan 2006 17:34 UTC
Windows Customers and partners who've been holding their breath waiting for Beta 2 of Windows Vista before getting serious about testing Microsoft's next-generation operating system can exhale. There will be no single, catch-all Beta 2 of Vista, according to Jim Allchin, co-president of Microsoft's Platform Products & Services Division. Instead, Microsoft is planning to rely increasingly on CTP builds to get its feedback from Windows testers. Elsehwere, Allchin said you should buy Vista for its security enhancements.
Thread beginning with comment 90493
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: security?
by PlatformAgnostic on Sat 28th Jan 2006 22:39 UTC in reply to "RE[3]: security?"
Member since:

No OS does this because it's really stupid. Word and many other programs (almost anything that's big) uses many files at a time, including multiple files linked to the doc you're working on, undo records, settings files, etc. They create a number of files too. A program is always associated with the user who runs it. If I can do something through the shell, the program can do the same thing through the OS APIs. The alternative would either perform terribly or be impossibly onerous for app programmers so they'd just find ways to punch holes through this system and directly read/write other files (like the programs that require running as Admin just because they're not coded to deal with limited rights).

Reply Parent Score: 1

RE[5]: security?
by bytecoder on Sat 28th Jan 2006 22:55 in reply to "RE[4]: security?"
bytecoder Member since:

Did you not read what I said? Said office app would be able to modify the files it's working with, obviously, and the other example files you listed fall under "application files."

Reply Parent Score: 1

RE[6]: security?
by PlatformAgnostic on Sun 29th Jan 2006 06:28 in reply to "RE[5]: security?"
PlatformAgnostic Member since:

How does the OS decide what files Word can work with and what files it can't work with? How can we really decide which executable images are even part of one application or two totally separate entities. What about apps that work together on files?

The only way this is possible is if the security privileges are associated with the executable that is running rather than the user who launched that executable. This model doesn't really make sense to me. It would also totally break backwards compatibility and might make the system inflexible.

Reply Parent Score: 1