From: Sarmila Vasanthadevan <vsarmila@redhat.com>
To: linux-audit@redhat.com
Subject: RHEL and Object reuse requirements.
Date: Tue, 27 Feb 2007 09:56:39 +0530 [thread overview]
Message-ID: <45E3B2FF.7050303@redhat.com> (raw)
Hello,
From reading the Redhat Enterprise Linux security target for CAPP document I can see that the common criteria evaluation identified these
object reuse requirements (OR.1, OR.2, and OR.3) and that Redhat met these requirements. And these requirements were met in,
Section 6.2.5.1, which states that file system objects are created with no contents. The exceptions are listed right above that line.
Section 6.2.5.2 says that IPC objects are initialized with 0 at creation and do not change size.
Section 6.2.5.3 discusses about memory objects.
Can anybody help me out to identify where in the Linux source code these requirements are met.
Thanks,
--
Sarmila
reply other threads:[~2007-02-27 4:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45E3B2FF.7050303@redhat.com \
--to=vsarmila@redhat.com \
--cc=linux-audit@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox