Security - XP & Longhorn | The Coffeehouse

Steve411

Shining Arcanine wrote:

Shining Arcanine wrote:

That is called slipstreaming. It can be done but isn't as easy as it could be. Maybe Microsoft could make it easier to create a slipstreamed disk, that would be easier than creating them itself and then handling the task of distribution.

I'v slipstreamed SP1 before, got to go through all of the 'create this directory create that directory begin from run, blah blah blah..
MS Should make some sort of software that does that all in one function..

eddwo
Wheres my head at?

I really want a slipstreamed install disc as well. With things like blaster and sasser out there it won't be safe to do a vanilla XP install and then go online to download the updates to SP2 level.
It'd be cool if you could take your retail copy of XP back to a store and they would replace it with an updated version. If you've got an official hologramed disc its pretty obvious that you've actually paid for it.

surferdude
surferdude

We've made the bet that making it hard for users to make themselves vulnerable to attack is the right thing to do...

Excellent. Wonderful. Thank you! Smart!!! 99.999999% of the users out there are far from power users for sure! This is your core market and the source of the problem!!!

- surferdude

jamie

none of you get the point...

yes - all idiots - run sp2

if your a developer - its a nightmare

yell at me all you want

Charles
Welcome Change

Back to the original question, what are we doing in terms of security for Longhorn.

Here's a quote from Jim Allchin. He runs the Windows division and is directly responsible for the success or failure of our operating systems. You better believe he is serious about security which means Windows will just get more and more secure with each iteration as well as more and more stable and reliable. To me, those three factors are among the most important aspects of any good operating system.

Security. Stability. Reliability.

"The one thing about Longhorn is that the quality is going to be there. Security is going to be addressed. We have done a very good job with Windows XP SP2, and we are redoubling, tripling, our efforts to ensure that the quality base is beyond anything we've ever done." -Jim Allchin

Charles

jonathanh
My mod color is red

jamie wrote:
none of you get the point...

yes - all idiots - run sp2

if your a developer - its a nightmare

yell at me all you want

As far as I can tell, we knew that the various security lockdowns in SP2 would cause pain to developers, and we've been pretty upfront about, releasing documents showing what the changes would be (the latest is a bunch of code and demos). But where security is concerned there's really no way to keep BOTH developers AND customers happy, and right now it's pretty clear that customers have to come 1^st.

jonathanh
My mod color is red

As a followup, we spent part of today tracking down why one of our demos had stopped working. Yup, it was caused by an SP2 security lockdown. So we do feel your pain.

But don't worry, it was easy to fix and the demo will be ready for a TechEd keynote Smiley

jamie

haha - cut to crowded conference hall ... and a box popping up every 5 minutes through the presentation "You need to reboot now!" cancel... 5 min later ... "You need to reboot now!" cancel ... 5 minutes later... you get the picture

jonathanh
My mod color is red

Oh great, now you're giving me nightmares!

Smiley

Charles
Welcome Change

Jamie is referring to the auto update reminder that aggressively reminds users to reboot a system that requires a reboot after installation of a patch or new feature via Windows Update (which is the service auto update uses too).

It would be great to never have to reboot again, but that's not gonna come for a while. We're working on it...

In SP2 Auto Update does a MUCH better job of figuring out if a reboot will be needed after update installation. Thing is, this is a really hard problem. See, when you are prompted to reboot it is generally due to some dll that needs to be upgraded being locked by another process ( or some exe that is running that needs to be upgraded(replaced) )when the installation of the patch is happening.

Sometimes people forget to reboot. This means their systems are not patched, for example.

We want to make it hard for you to do things that will make your system vulnerable to attack (like forgetting to reboot a machine that ran a reboot-required critical security update installation).

Thanks for the feedback.

Charles

sbc
GW R/Me

Perhaps dll's should work like they do in ASP.NET - when you update a file, it is replaces the already existing one in the cache when it has finished doing it's task.

Also what would be good is when a program wishes to load a dll that needs to be replaced, it instead uses the new version that is to replace it. That way, when programs have finished with the file it is replaced.

Security - XP &amp; Longhorn

Security - XP & Longhorn