aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2020-01-10 09:36:55 +0900
committerMichael Paquier <michael@paquier.xyz>2020-01-10 09:36:55 +0900
commit00b047fa67e9f4428a682bd90d5e6b08d2f8a87b (patch)
tree7ae8bc60946a2a407648bbc030ad2ef5ab2e2ae9
parent39a5f2a94f8a3bcfdb3da7391427a63f8f88b210 (diff)
downloadpostgresql-00b047fa67e9f4428a682bd90d5e6b08d2f8a87b.tar.gz
postgresql-00b047fa67e9f4428a682bd90d5e6b08d2f8a87b.zip
doc: Fix naming of SELinux
Reported-by: Tham Nguyen Discussion: https://postgr.es/m/157851402876.29175.12977878383183540468@wrigleys.postgresql.org Backpatch-through: 9.4
-rw-r--r--doc/src/sgml/ref/security_label.sgml2
-rw-r--r--src/test/modules/dummy_seclabel/README18
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
=====