From: Casey Schaufler <casey@schaufler-ca.com>
To: "Dr. Greg" <greg@enjellic.com>, Paul Moore <paul@paul-moore.com>
Cc: linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, jmorris@namei.org,
Casey Schaufler <casey@schaufler-ca.com>
Subject: Re: [PATCH v4 2/14] Add TSEM specific documentation.
Date: Tue, 25 Feb 2025 07:48:31 -0800 [thread overview]
Message-ID: <2b09859e-e16b-4b58-987c-356d3fffa4fe@schaufler-ca.com> (raw)
In-Reply-To: <20250225120114.GA13368@wind.enjellic.com>
On 2/25/2025 4:01 AM, Dr. Greg wrote:
> On Tue, Jan 28, 2025 at 05:23:52PM -0500, Paul Moore wrote:
>
> For the record, further documentation of our replies to TSEM technical
> issues.
>
> ...
>
> Further, TSEM is formulated on the premise that software teams,
> as a by product of CI/CD automation and testing, can develop precise
> descriptions of the security behavior of their workloads.
I've said it before, and I'll say it again. This premise is hopelessly
naive. If it was workable you'd be able to use SELinux and audit2allow
to create perfect security, and it would have been done 15 years ago.
The whole idea that you can glean what a software system is *supposed*
to do from what it *does* flies completely in the face of basic security
principles.
next prev parent reply other threads:[~2025-02-25 15:58 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-26 10:37 [PATCH v4 00/14] Implement Trusted Security Event Modeling Greg Wettstein
2024-08-26 10:37 ` [PATCH v4 01/14] Update MAINTAINERS file Greg Wettstein
2024-08-26 10:37 ` [PATCH v4 02/14] Add TSEM specific documentation Greg Wettstein
2025-01-14 1:29 ` [PATCH v4 2/14] " Paul Moore
2025-01-17 4:47 ` Dr. Greg
2025-01-17 18:10 ` Casey Schaufler
2025-01-18 19:03 ` Dr. Greg
2025-01-21 18:09 ` Casey Schaufler
2025-01-26 18:40 ` Dr. Greg
2025-01-28 22:23 ` Paul Moore
2025-01-31 17:11 ` Dr. Greg
2025-02-25 12:01 ` Dr. Greg
2025-02-25 15:48 ` Casey Schaufler [this message]
2025-02-27 12:12 ` Dr. Greg
2025-02-27 16:47 ` Casey Schaufler
2025-03-03 10:14 ` Dr. Greg
2025-03-03 16:23 ` Casey Schaufler
2025-02-05 12:00 ` Dr. Greg
2025-02-05 19:58 ` Casey Schaufler
2025-02-06 12:45 ` Dr. Greg
2025-02-06 15:48 ` Paul Moore
2025-02-07 10:20 ` Dr. Greg
2025-02-07 17:42 ` Casey Schaufler
2025-02-08 0:29 ` Paul Moore
2025-02-17 12:53 ` Dr. Greg
2025-02-17 23:09 ` Paul Moore
2024-08-26 10:37 ` [PATCH v4 03/14] TSEM global declarations Greg Wettstein
2024-08-26 10:37 ` [PATCH v4 04/14] Add primary TSEM implementation file Greg Wettstein
2024-08-26 15:53 ` Casey Schaufler
2024-08-27 10:52 ` Dr. Greg
2024-08-27 17:51 ` Casey Schaufler
2024-08-26 10:37 ` [PATCH v4 05/14] Add root domain trust implementation Greg Wettstein
2024-08-26 10:37 ` [PATCH v4 06/14] Implement TSEM control plane Greg Wettstein
2024-08-26 10:37 ` [PATCH v4 07/14] Add namespace implementation Greg Wettstein
2024-08-26 10:37 ` [PATCH v4 08/14] Add security event description export facility Greg Wettstein
2024-08-26 10:37 ` [PATCH v4 09/14] Add event processing implementation Greg Wettstein
2024-08-26 10:37 ` [PATCH v4 10/14] Implement security event mapping Greg Wettstein
2024-08-26 10:37 ` [PATCH v4 11/14] Implement the internal Trusted Modeling Agent Greg Wettstein
2024-08-26 10:37 ` [PATCH v4 12/14] Implement configuration and methods for default model Greg Wettstein
2024-08-26 10:37 ` [PATCH v4 13/14] Implement infrastructure for loadable security models Greg Wettstein
2024-08-26 10:37 ` [PATCH v4 14/14] Activate the configuration and build of the TSEM LSM Greg Wettstein
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=2b09859e-e16b-4b58-987c-356d3fffa4fe@schaufler-ca.com \
--to=casey@schaufler-ca.com \
--cc=greg@enjellic.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.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