Re: 2003 Web Server Security flaw
From: Karl Levinson [x y] mvp (levinson_k_at_despammed.com)
Date: 12/29/03
- Next message: Karl Levinson [x y] mvp: "Re: 2003 Web Server Security flaw"
- Previous message: Hairy One Kenobi: "Re: Dhcp/dns"
- In reply to: Robert Moir: "Re: 2003 Web Server Security flaw"
- Next in thread: Karl Levinson [x y] mvp: "Re: 2003 Web Server Security flaw"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Mon, 29 Dec 2003 07:17:51 -0500
"Robert Moir" <bofh@mvps.org> wrote in message
news:OejKXaXzDHA.3520@tk2msftngp13.phx.gbl...
> You can also use them as a template for setting permissions to deny
> read/write to *everyone*, including admins, which would certainly
"cripple"
> them to all intents and purposes, so as it happens I believe I answered
your
> question anyway.
> Sure. Delete them from the system file protection cache folder as well -
> C:\WINDOWS\system32\dllcache is the default location for this and its a
> protected operating system folder as well so you'll want to enable viewing
> of these in explorer folder options.
Not sure how SFC / WFP works in Windows 2003, but my understanding is that
neither ACLs nor deleting files are very effective ways to protect files
against WFP in Windows 2000. Both methods break WFP and cause annoying
error messages. And AFAIK, neither method will prevent the files from
being replaced when a future security patch or service pack containing those
files is installed.
- Next message: Karl Levinson [x y] mvp: "Re: 2003 Web Server Security flaw"
- Previous message: Hairy One Kenobi: "Re: Dhcp/dns"
- In reply to: Robert Moir: "Re: 2003 Web Server Security flaw"
- Next in thread: Karl Levinson [x y] mvp: "Re: 2003 Web Server Security flaw"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|
