From: owner-cypherpunks@toad.com
To: N/A
Message Hash: 915bb99fed376c0a6809c24cf8bc1a11703a56605313f0beb367b6083e5ce50f
Message ID: <QQahxy16435.199603210241@relay3.UU.NET>
Reply To: N/A
UTC Datetime: 1996-03-21 10:17:36 UTC
Raw Date: Thu, 21 Mar 1996 18:17:36 +0800
From: owner-cypherpunks@toad.com
Date: Thu, 21 Mar 1996 18:17:36 +0800
Subject: No Subject
Message-ID: <QQahxy16435.199603210241@relay3.UU.NET>
MIME-Version: 1.0
Content-Type: text/plain
I have been working for some time on a project that involves doing
proactive file authorization/authentication under Windows NT. In the
process, I've been working on an extension to the Kernel layer of the
operating system because we need to be able to catch read/writes to
the disk. (All perfectly legal according to the DDK, just
ot documented worth a damn.) All of this is designed to work
directly with the functionality given to us by the NT-Security layer.
Basically, I'm now questioning the C2 rating of Windows NT. The
entire security layer is modular to the Kernel. As a modular
driver, it can be removed, rewritten, and replaced.
So, what makes it secure? What gives it the C2 Rating? How would
one go about getting a C2 rating?
Brad
Return to March 1996
Return to “owner-cypherpunks@toad.com”
1996-03-21 (Thu, 21 Mar 1996 18:17:36 +0800) - No Subject - owner-cypherpunks@toad.com