home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!spool.mu.edu!umn.edu!lynx!unmvax!bbx!tantalum!edsr!tad!trs
- From: trs@tad.eds.com (Tim Steward)
- Newsgroups: comp.os.ms-windows.programmer.win32
- Subject: NTFS Security - Beware
- Message-ID: <1992Dec29.190314.2825@tad.eds.com>
- Date: 29 Dec 92 19:03:14 GMT
- Distribution: usa
- Organization: EDS Technology Architecture, Dallas
- Lines: 24
-
- I am using the October pre-release of NT. As an experiment, I built an
- NTFS partition to explore the security features. As initialized, the
- ACL on all of the NT files reads Everyone (All)(All) OWNER CREATOR (None)(All)
- giving any user full access to the system critical files.
-
- It seemed to me that this was pretty insecure, so I decided to modify it.
- At first, I simply changed the Everyone entry to Read Only. When I logged off
- and back on again, bad things seemed to happen. I tried to go to the
- Permissions... window, but got an error dialog saying "Server not available".
- I poked around some and tried to resolve the issue, but I was locked out of the
- apps in the Administrative Tools group. I tried to reboot and found that there
- was a 0x00... bug report. NT wouldn't come up. I had to use OS/2 fdisk to
- trash the partition in order to recover so that I could reinstall NT (Ouch).
-
- Being a glutten for punishment, I tried two more installs. The first time I
- changed Everyone to (Read)(Read) and OWNER CREATOR to (Full)(Full). Same result.
- The second time I made the same changes and then added Administrators (Full)(Full).
- This worked and I can use NTFS without problems.
-
- NOTES: I was logged on as the default Administrator account, which is a
- member of the Administrators group. The OWNER CREATER of all files was
- listed as Administrators (I assume the group). When I changed permissions,
- I cascaded the changes to the entire drive. The NT system directory was
- on the NTFS drive.
-