mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-08-22 15:33:23 +02:00
doc: Fix naming of SELinux
Reported-by: Tham Nguyen Discussion: https://postgr.es/m/157851402876.29175.12977878383183540468@wrigleys.postgresql.org Backpatch-through: 9.4
This commit is contained in:
parent
676c9156bb
commit
2696434b7f
@ -80,7 +80,7 @@ SECURITY LABEL [ FOR <replaceable class="parameter">provider</replaceable> ] ON
|
|||||||
label provider must interpret security labels; it merely provides a
|
label provider must interpret security labels; it merely provides a
|
||||||
mechanism for storing them. In practice, this facility is intended to allow
|
mechanism for storing them. In practice, this facility is intended to allow
|
||||||
integration with label-based mandatory access control (MAC) systems such as
|
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
|
based on object labels, rather than traditional discretionary access control
|
||||||
(DAC) concepts such as users and groups.
|
(DAC) concepts such as users and groups.
|
||||||
</para>
|
</para>
|
||||||
|
@ -1,19 +1,17 @@
|
|||||||
The dummy_seclabel module exists only to support regression
|
The dummy_seclabel module exists only to support regression testing of
|
||||||
testing of the SECURITY LABEL statement. It is not intended
|
the SECURITY LABEL statement. It is not intended to be used in production.
|
||||||
to be used in production.
|
|
||||||
|
|
||||||
Rationale
|
Rationale
|
||||||
=========
|
=========
|
||||||
|
|
||||||
The SECURITY LABEL statement allows the user to assign security
|
The SECURITY LABEL statement allows the user to assign security labels to
|
||||||
labels to database objects; however, security labels can only be assigned
|
database objects; however, security labels can only be assigned when
|
||||||
when specifically allowed by a loadable module, so this module is provided
|
specifically allowed by a loadable module, so this module is provided to
|
||||||
to allow proper regression testing.
|
allow proper regression testing.
|
||||||
|
|
||||||
Security label providers intended to be used in production will typically be
|
Security label providers intended to be used in production will typically be
|
||||||
dependent on a platform-specific feature such as
|
dependent on a platform-specific feature such as SELinux. This module is
|
||||||
SE-Linux. This module is platform-independent,
|
platform-independent, and therefore better-suited to regression testing.
|
||||||
and therefore better-suited to regression testing.
|
|
||||||
|
|
||||||
Usage
|
Usage
|
||||||
=====
|
=====
|
||||||
|
Loading…
Reference in New Issue
Block a user