Re: Expanding on KB 244600?

"Will" <westes-usc@xxxxxxxxxxxxxx> wrote in message
news:%2364m4zjvGHA.560@xxxxxxxxxxxxxxxxxxxxxxx
"Joe Richards [MVP]" <humorexpress@xxxxxxxxxxx> wrote in message
news:O5fSLqhvGHA.1808@xxxxxxxxxxxxxxxxxxxxxxx
That general type of documentation, what and where MSFT apps use
something is generally unavailable. Personally I believe it is because
no one really knows and it isn't all documented. I have asked for this
on multiple occasions and always get the cold shoulder. Even for things
as recent as Active Directory attributes, etc.

Unfortunately, as I start to better understand the system, I get exactly
the
same feeling. It really looks like they had large numbers of different
players all integrating together in rather random ways, and "security" was
simply something that got in their way, and the permissions they chose are
utterly random DACLs on folders and files that were the minimum needed to
get each team's code to run.

The infrastructure of DACL and SACL itself seems extremely well done, so
how
frustrating it is that Microsoft's infrastructure teams produced a
wonderful
security layer at the bottom, and there was apparently no coherent
application of that infrastructure on the higher levels of the OS. And
the only guidance if a customer sees that and wants to (partially) fix it
is
to say that if you change default permissions in system32 Microsoft won't
support it.


It should not be considered as a feeling that you have Will. It is a view
of the history from its artifacts. The Cutler group was a new hire team
that worked to design/build NT (NT = new technology). Meanwhile
MS has existing workforce still churning out Windows (on DOS) and
apps for it. For the first few released builds of NT, Windows 3.11 was
still the mainstream, still living in a world with only limited concept of
networking. Around NT 3.5 use began in measurable amounts and
teams shifted focus, to Windows 95 etc, with the apps portable onto
NT, and with MS not quite yet having discovered the internet revolution.
What you see is from the history of use, by MS, and now still by some
of MS and by a fair part of third parties. Leading by example.


.

Relevant Pages

  • Re: XP BS
    ... So you bought a computer in the year 2003 with Windows '98 installed on it? ... Yes - the last two install from the web - but they are safe. ... Unwanted history of every website you visit? ... In Internet Explorer, on the Tools menu, click Internet Options. ...
    (microsoft.public.windowsxp.basics)
  • Re: Address bar will not save history
    ... Fixing History in Internet Explorer ... It could be that the History folder has become damaged or corrupted, ... See: How To Delete the Internet Explorer Temporary Internet Files: ... History folder in Windows 9x,2K, XP. ...
    (microsoft.public.windows.inetexplorer.ie6.browser)
  • Quick review of MS AntiSpywear reputed functionality
    ... Judging by the help from specific Microsoft private newsgroups ... ... And it searches for the bad guys in the Windows registry ... ... It will save the scan history if you enable that option ... ... Internet Explorer Explorer Bars, Internet Explorer Extensions, ... ...
    (alt.computer.security)
  • Quick review of MS AntiSpywear reputed functionality
    ... Judging by the help from specific Microsoft private newsgroups ... ... And it searches for the bad guys in the Windows registry ... ... It will save the scan history if you enable that option ... ... Internet Explorer Explorer Bars, Internet Explorer Extensions, ... ...
    (microsoft.public.security)
  • Quick review of MS AntiSpywear reputed functionality
    ... Judging by the help from specific Microsoft private newsgroups ... ... And it searches for the bad guys in the Windows registry ... ... It will save the scan history if you enable that option ... ... Internet Explorer Explorer Bars, Internet Explorer Extensions, ... ...
    (microsoft.public.security.virus)