From: Paul Moore <paul@paul-moore.com>
To: Ted Toth <txtoth@gmail.com>
Cc: SELinux <selinux@vger.kernel.org>,
Stephen Smalley <sds@tycho.nsa.gov>,
James Morris <jmorris@namei.org>, Joe Nall <joe@nall.com>
Subject: Re: no SELinux common criteria?
Date: Mon, 19 Apr 2021 16:15:46 -0400 [thread overview]
Message-ID: <CAHC9VhRFeg2KLSy-2frtN=mBhR=5VBVUq1LXfAqjCL0VAvt=uA@mail.gmail.com> (raw)
In-Reply-To: <CAFPpqQF7L_ecFzBsfG5EydnaZ7_NQeT4Yxi+aY9Q1Xj-N_0c7g@mail.gmail.com>
On Mon, Apr 19, 2021 at 3:43 PM Ted Toth <txtoth@gmail.com> wrote:
>
> Having read:
> https://www.redhat.com/en/about/press-releases/red-hat-adds-common-criteria-certification-red-hat-enterprise-linux-8
> and seen no mention of SELinux I/we are wondering what others are thinking/doing about the lack of certification? Are we going to have to take this on ourselves and if so what would be a good starting point (LSPP)?
As a reminder, the SELinux developers list is an upstream list for the
discussion and development of SELinux; it is not a distro specific
list. While the general topic of security certifications such as
Common Criteria can be on-topic for this list, distro specific
security certifications are likely best discussed with the individual
distro/vendor.
Last I checked, a CC eval of a general purpose Linux distro was a
rather expensive undertaking, I doubt that any of the volunteer based,
non "enterprise" distros would be able to go through such a
certification without some form of sponsorship or corporate backing.
--
paul moore
www.paul-moore.com
next parent reply other threads:[~2021-04-19 20:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAFPpqQF7L_ecFzBsfG5EydnaZ7_NQeT4Yxi+aY9Q1Xj-N_0c7g@mail.gmail.com>
2021-04-19 20:15 ` Paul Moore [this message]
2021-04-19 20:25 ` no SELinux common criteria? Ted Toth
2021-04-19 20:05 Ted Toth
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='CAHC9VhRFeg2KLSy-2frtN=mBhR=5VBVUq1LXfAqjCL0VAvt=uA@mail.gmail.com' \
--to=paul@paul-moore.com \
--cc=jmorris@namei.org \
--cc=joe@nall.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@vger.kernel.org \
--cc=txtoth@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.