[11/22] subjects: Convert to markdown

Message ID	20200909133039.44498-12-richard_c_haines@btinternet.com (mailing list archive)
State	Accepted
Headers	show Return-Path: <SRS0=Milt=CT=vger.kernel.org=selinux-owner@kernel.org> From: Richard Haines <richard_c_haines@btinternet.com> To: paul@paul-moore.com, selinux@vger.kernel.org Cc: Richard Haines <richard_c_haines@btinternet.com> Subject: [PATCH 11/22] subjects: Convert to markdown Date: Wed, 9 Sep 2020 14:30:28 +0100 Message-Id: <20200909133039.44498-12-richard_c_haines@btinternet.com> In-Reply-To: <20200909133039.44498-1-richard_c_haines@btinternet.com> References: <20200909133039.44498-1-richard_c_haines@btinternet.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: selinux-owner@vger.kernel.org Precedence: bulk
Series	SELinux Notebook: Convert batch 3 to markdown/tidy up \| expand [00/22] SELinux Notebook: Convert batch 3 to markdown/tidy up [01/22] kernel_policy_language: Tidy up formatting [02/22] mls_statements: Convert to markdown [03/22] object_classes_permissions: : Tidy up formatting [04/22] policy_config_files: Tidy up formatting [05/22] policy_validation_example: Tidy up formatting [06/22] postgresql: Tidy up formatting [07/22] security_context: Convert to markdown [08/22] selinux_cmds: Convert to markdown [09/22] selinux_overview: Convert to markdown [10/22] sid_statement: Convert to markdown [11/22] subjects: Convert to markdown [12/22] toc: Tidy up formatting [13/22] type_enforcement: Convert to markdown [14/22] type_statements: Add toc, tidy up formatting [15/22] types_of_policy: Convert to markdown [16/22] user_statements:: Tidy up formatting [17/22] users: Tidy up formatting [18/22] userspace_libraries: Tidy up formatting, add toc [19/22] vm_support: Tidy up formatting [20/22] x_windows: Tidy up formatting [21/22] xen_statements: Tidy up formatting [22/22] xperm_rules: Tidy up formatting

Message ID

20200909133039.44498-12-richard_c_haines@btinternet.com (mailing list archive)

State

Accepted

Headers

From: Richard Haines <richard_c_haines@btinternet.com>
To: paul@paul-moore.com, selinux@vger.kernel.org
Cc: Richard Haines <richard_c_haines@btinternet.com>
Subject: [PATCH 11/22] subjects: Convert to markdown
Date: Wed,  9 Sep 2020 14:30:28 +0100
Message-Id: <20200909133039.44498-12-richard_c_haines@btinternet.com>
In-Reply-To: <20200909133039.44498-1-richard_c_haines@btinternet.com>
References: <20200909133039.44498-1-richard_c_haines@btinternet.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Sender: selinux-owner@vger.kernel.org
Precedence: bulk

Series

SELinux Notebook: Convert batch 3 to markdown/tidy up | expand

Commit Message

Richard Haines Sept. 9, 2020, 1:30 p.m. UTC

Signed-off-by: Richard Haines <richard_c_haines@btinternet.com>
---
 src/subjects.md | 21 +++++++++------------
 1 file changed, 9 insertions(+), 12 deletions(-)

diff --git a/src/subjects.md b/src/subjects.md
index 4f677cb..bc7a89a 100644
--- a/src/subjects.md
+++ b/src/subjects.md
@@ -9,13 +9,13 @@  Within SELinux a subject is an active process and has a
 it, however a process can also be referred to as an object depending on the
 context in which it is being taken, for example:
 
-1.  A running process (i.e. an active entity) is a subject because it
-    causes information to flow among objects or can change the system
-    state.
-2.  The process can also be referred to as an object because each
-    process has an associated object class<a href="#fns1" class="footnote-ref" id="fnsub1"><strong><sup>1</sup></strong></a>
-    called '**process**'. This process 'object', defines what permissions the
-    policy is allowed to grant or deny on the active process.
+1. A running process (i.e. an active entity) is a subject because it
+   causes information to flow among objects or can change the system
+   state.
+2. The process can also be referred to as an object because each
+   process has an associated object class[^fn_sub_1]
+   called ***process***. This process 'object', defines what permissions the
+   policy is allowed to grant or deny on the active process.
 
 An example is given of the above scenarios in the
 [**Allowing a Process Access to Resources**](objects.md#allowing-a-process-access-to-resources)
@@ -37,11 +37,8 @@  under *semanage_t*).
 
 **Untrusted** - Everything else.
 
-<section class="footnotes">
-<ol>
-<li id="fns1"><p>The object class and its associated permissions are explained in the <strong><a href="object_classes_permissions.md#process-object-class"> Appendix A - Object Classes and Permissions - Process Object Class</a></strong> section.<a href="#fnsub1" class="footnote-back">↩</a></p></li>
-</ol>
-</section>
+[^fn_sub_1]: The object class and its associated permissions are explained in
+[**Appendix A - Object Classes and Permissions - Process Object Class**](object_classes_permissions.md#process-object-class)
 
 <!-- %CUTHERE% -->

[11/22] subjects: Convert to markdown

Commit Message

Patch