H
Ham Pastrami
Guest
I have read some articles about Windows NT/2K C2-compliance. The part that
interests me is object reuse protection. Supposedly this means that disk
space is initialized to 0 when it is allocated. However, I don't see this
happening on my 2K system, not as far as I can tell. Wouldn't zeroing (for
say, hundreds of megabytes) imply a long write to disk everytime a new file
was created?
I initially thought that C2 compliance could be achieved through
configuration, but did not ship that way out of the box. Some of the
articles state that the evaluation applies to off-the-shelf products, which
is ambiguous as to whether that means default configuration or simply a lack
of third party software.
The articles also tend to talk only about NT/2K and not XP or Vista. Why is
that?
interests me is object reuse protection. Supposedly this means that disk
space is initialized to 0 when it is allocated. However, I don't see this
happening on my 2K system, not as far as I can tell. Wouldn't zeroing (for
say, hundreds of megabytes) imply a long write to disk everytime a new file
was created?
I initially thought that C2 compliance could be achieved through
configuration, but did not ship that way out of the box. Some of the
articles state that the evaluation applies to off-the-shelf products, which
is ambiguous as to whether that means default configuration or simply a lack
of third party software.
The articles also tend to talk only about NT/2K and not XP or Vista. Why is
that?