postgres.git / summary / log / commit / refs

commit    2696434b7f6b38799e338ac66962ee75f97d3eba
Author:   Michael Paquier <michael@paquier.xyz>
Date:     Fri Jan 10 00:37:21 2020 +0000
First released in: 13.0, 9.4.26, 9.5.21, 9.6.17, 10.12, 11.7, 12.2

    doc: Fix naming of SELinux
    
    Reported-by: Tham Nguyen
    Discussion: https://postgr.es/m/157851402876.29175.12977878383183540468@wrigleys.postgresql.org
    Backpatch-through: 9.4


 doc/src/sgml/ref/security_label.sgml   |  2 +-
 src/test/modules/dummy_seclabel/README | 18 ++++++++----------
 2 files changed, 9 insertions(+), 11 deletions(-)

diff --git a/doc/src/sgml/ref/security_label.sgml b/doc/src/sgml/ref/security_label.sgml
index e9cfdec9f94..e9688cce214 100644
--- a/doc/src/sgml/ref/security_label.sgml
+++ b/doc/src/sgml/ref/security_label.sgml
@@ -80,7 +80,7 @@ SECURITY LABEL [ FOR <replaceable class="parameter">provider</replaceable> ] ON
    label provider must interpret security labels; it merely provides a
    mechanism for storing them.  In practice, this facility is intended to allow
    integration with label-based mandatory access control (MAC) systems such as
-   <productname>SE-Linux</productname>.  Such systems make all access control decisions
+   <productname>SELinux</productname>.  Such systems make all access control decisions
    based on object labels, rather than traditional discretionary access control
    (DAC) concepts such as users and groups.
   </para>
diff --git a/src/test/modules/dummy_seclabel/README b/src/test/modules/dummy_seclabel/README
index 75320aaeaca..a3fcbd75994 100644
--- a/src/test/modules/dummy_seclabel/README
+++ b/src/test/modules/dummy_seclabel/README
@@ -1,19 +1,17 @@
-The dummy_seclabel module exists only to support regression
-testing of the SECURITY LABEL statement.  It is not intended
-to be used in production.
+The dummy_seclabel module exists only to support regression testing of
+the SECURITY LABEL statement.  It is not intended to be used in production.
 
 Rationale
 =========
 
-The SECURITY LABEL statement allows the user to assign security
-labels to database objects; however, security labels can only be assigned
-when specifically allowed by a loadable module, so this module is provided
-to allow proper regression testing.
+The SECURITY LABEL statement allows the user to assign security labels to
+database objects; however, security labels can only be assigned when
+specifically allowed by a loadable module, so this module is provided to
+allow proper regression testing.
 
 Security label providers intended to be used in production will typically be
-dependent on a platform-specific feature such as
-SE-Linux.  This module is platform-independent,
-and therefore better-suited to regression testing.
+dependent on a platform-specific feature such as SELinux.  This module is
+platform-independent, and therefore better-suited to regression testing.
 
 Usage
 =====


[parent: 676c9156bbc8]