Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 00b047f

Browse files
committed
doc: Fix naming of SELinux
Reported-by: Tham Nguyen Discussion: https://postgr.es/m/157851402876.29175.12977878383183540468@wrigleys.postgresql.org Backpatch-through: 9.4
1 parent 39a5f2a commit 00b047f

File tree

2 files changed

+9
-11
lines changed

2 files changed

+9
-11
lines changed

doc/src/sgml/ref/security_label.sgml

+1-1
Original file line numberDiff line numberDiff line change
@@ -80,7 +80,7 @@ SECURITY LABEL [ FOR <replaceable class="parameter">provider</replaceable> ] ON
8080
label provider must interpret security labels; it merely provides a
8181
mechanism for storing them. In practice, this facility is intended to allow
8282
integration with label-based mandatory access control (MAC) systems such as
83-
<productname>SE-Linux</productname>. Such systems make all access control decisions
83+
<productname>SELinux</productname>. Such systems make all access control decisions
8484
based on object labels, rather than traditional discretionary access control
8585
(DAC) concepts such as users and groups.
8686
</para>

src/test/modules/dummy_seclabel/README

+8-10
Original file line numberDiff line numberDiff line change
@@ -1,19 +1,17 @@
1-
The dummy_seclabel module exists only to support regression
2-
testing of the SECURITY LABEL statement. It is not intended
3-
to be used in production.
1+
The dummy_seclabel module exists only to support regression testing of
2+
the SECURITY LABEL statement. It is not intended to be used in production.
43

54
Rationale
65
=========
76

8-
The SECURITY LABEL statement allows the user to assign security
9-
labels to database objects; however, security labels can only be assigned
10-
when specifically allowed by a loadable module, so this module is provided
11-
to allow proper regression testing.
7+
The SECURITY LABEL statement allows the user to assign security labels to
8+
database objects; however, security labels can only be assigned when
9+
specifically allowed by a loadable module, so this module is provided to
10+
allow proper regression testing.
1211

1312
Security label providers intended to be used in production will typically be
14-
dependent on a platform-specific feature such as
15-
SE-Linux. This module is platform-independent,
16-
and therefore better-suited to regression testing.
13+
dependent on a platform-specific feature such as SELinux. This module is
14+
platform-independent, and therefore better-suited to regression testing.
1715

1816
Usage
1917
=====

0 commit comments

Comments
 (0)