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.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:2005-07-06
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.
MS actually already does this with Code Access Security. Code is allowed or denied certain privileges not only based on the user token under which it runs, but also based on attributes about the code like where it came from, the functionality it incorporates, and what the developer has specifically allowed or restricted. More limited features for code trust are also available for unmanaged applications.
Member since:2005-11-27
How does the OS decide what files Word can work with and what files it can't work with?
The "OS" doesn't. If you completely move file opening into the file manager, as it should be, the file manager knows exactly which files the word processor can modify.
How can we really decide which executable images are even part of one application or two totally separate entities.
I'm not sure what this has to do with anything. If you mean calling one app from another, permissions (obviously) carry over.
What about apps that work together on files?
Still not sure what you mean.
Member since:
2006-01-02
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.