Re: Security Question. - FEXED, the Security NG helped.

Tech-Archive recommends: Speed Up your PC by fixing your registry




"Wiley Coyote - N2K" <mits_mvp@xxxxxxxx> wrote in message
news:u$4SG2VxGHA.2432@xxxxxxxxxxxxxxxxxxxxxxx
I have set NTFS perms on the Root of my system volume to EVERYONE: Deny
Write. Yet, I can still create folders and files! I've been an SE for a
longggg time and never saw this before.

This acount that I am using is NOT a member of any supernumery group,
just a plain jane user account. I logged in with admin rights to check the
NTFS perms and all seems to be OK as follows:

System: CHANGE (not FC),
Everyone Read & Exec, List, Read ((Deny Write),
C.O. : nada,
Administrators: Change,
Users: Read & Exec, List, Read (Deny Write)

One of the reasons for this level of security is to prevent certain web
sites from dropping VB apps in the root and other silly things.

Anyway, just curious.

If anyone know what is happending that would be good.

Thanks.



.



Relevant Pages

  • Re: Query that involves publci role
    ... dump the result of exec sp_helprotect null,'public' into a tmp table ... create 'deny' statements based on what is granted to public by querying ... > Id like to know all the permissions granted to the public role for all ...
    (microsoft.public.sqlserver.security)
  • Security Question.
    ... I have set NTFS perms on the Root of my system volume to EVERYONE: Deny ... Everyone Read & Exec, List, Read, ...
    (microsoft.public.windowsxp.general)