From: Michael Paquier Date: Fri, 10 Jan 2020 00:37:44 +0000 (+0900) Subject: doc: Fix naming of SELinux X-Git-Tag: REL9_4_26~21 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=27676e22d330e6a6f30b1e1dd6ed6e3d3413f200;p=thirdparty%2Fpostgresql.git doc: Fix naming of SELinux Reported-by: Tham Nguyen Discussion: https://postgr.es/m/157851402876.29175.12977878383183540468@wrigleys.postgresql.org Backpatch-through: 9.4 --- diff --git a/doc/src/sgml/dummy-seclabel.sgml b/doc/src/sgml/dummy-seclabel.sgml index d064705f2ae..f735cb5315f 100644 --- a/doc/src/sgml/dummy-seclabel.sgml +++ b/doc/src/sgml/dummy-seclabel.sgml @@ -26,7 +26,7 @@ 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, + SELinux. This module is platform-independent, and therefore better-suited to regression testing. diff --git a/doc/src/sgml/ref/security_label.sgml b/doc/src/sgml/ref/security_label.sgml index 6e2bd25240b..e17bc8cd462 100644 --- a/doc/src/sgml/ref/security_label.sgml +++ b/doc/src/sgml/ref/security_label.sgml @@ -76,7 +76,7 @@ SECURITY LABEL [ FOR provider ] 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 - SE-Linux. Such systems make all access control decisions + SELinux. Such systems make all access control decisions based on object labels, rather than traditional discretionary access control (DAC) concepts such as users and groups.