From: Greg Wettstein <greg@enjellic.com>
To: linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: jmorris@namei.org
Subject: [PATCH v4 12/14] Implement configuration and methods for default model.
Date: Mon, 26 Aug 2024 05:37:26 -0500 [thread overview]
Message-ID: <20240826103728.3378-13-greg@enjellic.com> (raw)
In-Reply-To: <20240826103728.3378-1-greg@enjellic.com>
The implementation of a TSEM model consists of three separate
components:
- bypasses array
- event initialization method
- event coefficient mapping method.
Boolean true values in the bypasses array is used to indicate
that the event should be completely bypassed.
The event initialization initializes the event description
structure using the characteristics of the event.
The event coefficient mapping method is responsible for
generating the security event coefficient from the event
description structure.
The model0.c file provides the model components for the default
deterministic model implemented by the kernel.
---
security/tsem/model0.c | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
create mode 100644 security/tsem/model0.c
diff --git a/security/tsem/model0.c b/security/tsem/model0.c
new file mode 100644
index 000000000000..347ed8584842
--- /dev/null
+++ b/security/tsem/model0.c
@@ -0,0 +1,21 @@
+// SPDX-License-Identifier: GPL-2.0-only
+
+/*
+ * Copyright (C) 2024 Enjellic Systems Development, LLC
+ * Author: Dr. Greg Wettstein <greg@enjellic.com>
+ *
+ * This file contains methods and definitions for the 'model0'
+ * security model implementation. This is the default model that
+ * TSEM implements.
+ */
+
+#include "tsem.h"
+
+static bool event_bypasses[TSEM_EVENT_CNT];
+
+const struct tsem_context_ops tsem_model0_ops = {
+ .name = "model0",
+ .bypasses = event_bypasses,
+ .init = tsem_event_generate,
+ .map = tsem_map_event
+};
--
2.39.1
next prev parent reply other threads:[~2024-08-26 10:49 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
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 ` Greg Wettstein [this message]
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=20240826103728.3378-13-greg@enjellic.com \
--to=greg@enjellic.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
/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