056efe85d6
Hi, in https://github.com/TresysTechnology/refpolicy/pull/1 db_exception and db_datatype were added to reference policy. This small patch extends ability of label_db backend to work with these objects. Regards.
219 lines
8.2 KiB
Groff
219 lines
8.2 KiB
Groff
.\" Hey Emacs! This file is -*- nroff -*- source.
|
|
.\"
|
|
.\" Author: KaiGai Kohei <kaigai@ak.jp.nec.com> 2009
|
|
.TH "selabel_db" "5" "01 DEC 2011" "Security Enhanced Linux" "SELinux API documentation"
|
|
.SH "NAME"
|
|
selabel_db \- userspace SELinux labeling interface and configuration file format for the RDBMS objects context backend
|
|
.
|
|
.SH "SYNOPSIS"
|
|
.B #include <selinux/label.h>
|
|
.sp
|
|
.BI "int selabel_lookup(struct selabel_handle *" hnd ,
|
|
.in +\w'int selabel_lookup('u
|
|
.BI "char **" context ,
|
|
.br
|
|
.BI "const char *" object_name ", int " object_type ");"
|
|
.in
|
|
.sp
|
|
.BI "int selabel_lookup_raw(struct selabel_handle *" hnd ,
|
|
.in +\w'int selabel_lookup('u
|
|
.BI "char **" context ,
|
|
.br
|
|
.BI "const char *" object_name ", int " object_type ");"
|
|
.
|
|
.SH "DESCRIPTION"
|
|
The DB contexts backend maps from a pair of object name and class into security contexts. It is used to find the appropriate context for database objects when relabeling a certain database. The returned \fIcontext\fR must be freed using \fBfreecon\fR(3).
|
|
.br
|
|
\fBselabel_lookup\fR(3) describes the function with its return and error codes.
|
|
.sp
|
|
The \fIobject_name\fR should be a fully qualified name using the hierarchy of database objects. For example, the \fBpg_class\fR table in the \fBpostgres\fR database and \fBpg_catalog\fR schema should be qualified as:
|
|
.RS
|
|
.B Bpostgres.pg_catalog.pg_class
|
|
.RE
|
|
.sp
|
|
The \fBNOTES\fR section has further information on database support for namespace hierarchies.
|
|
.sp
|
|
The \fIobject_type\fR argument should be set to one of the following values:
|
|
.RS
|
|
.TP
|
|
.B SELABEL_DB_DATABASE
|
|
The
|
|
.I object_name
|
|
argument specifies the name of a database itself, such as "postgres".
|
|
.TP
|
|
.B SELABEL_DB_SCHEMA
|
|
The
|
|
.I object_name
|
|
argument specifies the name of a schema object, such as "postgres.public".
|
|
.TP
|
|
.B SELABEL_DB_TABLE
|
|
The
|
|
.I object_name
|
|
argument specifies the name of a table object, such as "postgres.public.my_table"
|
|
.TP
|
|
.B SELABEL_DB_COLUMN
|
|
The
|
|
.I object_name
|
|
argument specifies the name of a column object, such as "postgres.public.my_table.user_id"
|
|
.TP
|
|
.B SELABEL_DB_TUPLE
|
|
The
|
|
.I object_name
|
|
argument specifies the name of a table object which contains the tuples to be relabeled, such as "postgresql.public.my_table". Note that we have no way to identify individual tuple objects, except for WHERE clause on DML statements, because it has no name.
|
|
.TP
|
|
.B SELABEL_DB_PROCEDURE
|
|
The
|
|
.I object_name
|
|
argument specifies the name of a procedure object, such as "postgres.public.my_func". Note that we don't support lookup of individual security contexts for procedures which have the same name but different arguments.
|
|
.TP
|
|
.B SELABEL_DB_SEQUENCE
|
|
The
|
|
.I object_name
|
|
argument specifies the name of a sequence object, such as "postgres.public.my_seq".
|
|
.TP
|
|
.B SELABEL_DB_BLOB
|
|
The
|
|
.I object_name
|
|
argument specifies the name of a large object, such as "postgres.16308".
|
|
Note that a large object does not have a name, so it is identified by its identifier value.
|
|
.TP
|
|
.B SELABEL_DB_VIEW
|
|
The
|
|
.I object_name
|
|
argument specifies the name of a view object, such as "postgres.public.my_view".
|
|
.TP
|
|
.B SELABEL_DB_LANGUAGE
|
|
The
|
|
.I object_name
|
|
argument specifies the name of a language object, such as "postgres.public.tcl".
|
|
.TP
|
|
.B SELABEL_DB_EXCEPTION
|
|
The
|
|
.I object_name
|
|
argument specifies the name of a exception object.
|
|
.TP
|
|
.B SELABEL_DB_DATATYPE
|
|
The
|
|
.I object_name
|
|
argument specifies the name of a type or domain object, such as postgres.public.my_type.
|
|
.RE
|
|
.sp
|
|
Any messages generated by \fBselabel_lookup\fR(3) are sent to \fIstderr\fR
|
|
by default, although this can be changed by \fBselinux_set_callback\fR(3).
|
|
.sp
|
|
.BR selabel_lookup_raw (3)
|
|
behaves identically to \fBselabel_lookup\fR(3) but does not perform context
|
|
translation.
|
|
.sp
|
|
The \fBFILES\fR section details the configuration files used to determine the database object context.
|
|
.
|
|
.SH "OPTIONS"
|
|
In addition to the global options described in \fBselabel_open\fR(3), this backend recognizes the following options:
|
|
.RS
|
|
.TP
|
|
.B SELABEL_OPT_PATH
|
|
A non-null value for this option specifies a path to a file that will be opened in lieu of the standard DB contexts file.
|
|
It tries to open the specfile designed for SE-PostgreSQL as default, so if another RDBMS uses this interface, it needs to give an explicit specfile designed for that RDBMS (see the \fBFILES\fR section for details).
|
|
.RE
|
|
.
|
|
.SH "FILES"
|
|
The database context file used to retrieve a context depends on the \fBSELABEL_OPT_PATH\fR parameter passed to \fBselabel_open\fR(3). If \fINULL\fR, then the \fBSELABEL_OPT_PATH\fR value will default to the active policy database contexts location (as returned by \fBselinux_sepgsql_context_path\fR(3)), otherwise the actual \fBSELABEL_OPT_PATH\fR value specified is used (this option must be used to support databases other than SE-PostgreSQL).
|
|
.sp
|
|
The default database object contexts file is:
|
|
.RS
|
|
.I /etc/selinux/{SELINUXTYPE}/contexts/sepgsql_context
|
|
.RE
|
|
.sp
|
|
Where \fI{SELINUXTYPE}\fR is the entry from the selinux configuration file \fIconfig\fR (see \fBselinux_config\fR(5)).
|
|
.sp
|
|
The entries within the database contexts file are shown in the \fBObject Name String Values\fR and \fBFILE FORMAT\fR sections.
|
|
.
|
|
.SH "Object Name String Values"
|
|
The string name assigned to each \fIobject_type\fR argument that can be present in the database contexts file are:
|
|
.TS
|
|
center, allbox, tab(@);
|
|
lI lB
|
|
lB l .
|
|
object_type@Text Name
|
|
SELABEL_DB_DATABASE@db_database
|
|
SELABEL_DB_SCHEMA@db_schema
|
|
SELABEL_DB_VIEW@db_view
|
|
SELABEL_DB_LANGUAGE@db_language
|
|
SELABEL_DB_TABLE@db_table
|
|
SELABEL_DB_COLUMN@db_column
|
|
SELABEL_DB_TUPLE@db_tuple
|
|
SELABEL_DB_PROCEDURE@db_procedure
|
|
SELABEL_DB_SEQUENCE@db_sequence
|
|
SELABEL_DB_BLOB@db_blob
|
|
SELABEL_DB_EXCEPTION@db_exception
|
|
SELABEL_DB_DATATYPE@db_datatype
|
|
.TE
|
|
.
|
|
.SH "FILE FORMAT"
|
|
Each line within the database contexts file is as follows:
|
|
.RS
|
|
.I object_type object_name context
|
|
.RE
|
|
.sp
|
|
Where:
|
|
.RS
|
|
.I object_type
|
|
.RS
|
|
This is the string representation of the object type shown in the \fBObject Name String Values\fR section.
|
|
.RE
|
|
.I object_name
|
|
.RS
|
|
The key used to obtain the context based on the \fIobject_type\fR.
|
|
.sp
|
|
The entry can contain '*' for wildcard matching or '?' for substitution.
|
|
.sp
|
|
Note that if the '*' is used, then be aware that the order of entries in the file is important. The '*' on its own is used to ensure a default fallback context is assigned and should be the last entry in the \fIobject_type\fR block.
|
|
.RE
|
|
.I context
|
|
.RS
|
|
The security context that will be applied to the object.
|
|
.RE
|
|
.RE
|
|
.sp
|
|
The following example is for SE-PostgreSQL:
|
|
.sp
|
|
# ./contexts/sepgsql_contexts file
|
|
.br
|
|
# object_type object_name context
|
|
.br
|
|
db_database my_database system_u:object_r:sepgsql_db_t:s0
|
|
.br
|
|
db_database * system_u:object_r:sepgsql_db_t:s0
|
|
.br
|
|
db_schema *.* system_u:object_r:sepgsql_schema_t:s0
|
|
.br
|
|
db_tuple row_low system_u:object_r:sepgsql_table_t:s0
|
|
.br
|
|
db_tuple row_high system_u:object_r:sepgsql_table_t:s0:c1023
|
|
.br
|
|
db_tuple *.*.* system_u:object_r:sepgsql_table_t:s0
|
|
.
|
|
.SH "NOTES"
|
|
.IP "1." 4
|
|
A suitable database contexts file needs to be written for the target RDBMS and the \fBSELABEL_OPT_PATH\fR option must be used in \fBselabel_open\fR(3) to load it.
|
|
.IP "2." 4
|
|
The hierarchy of the namespace for database objects depends on the RDBMS, however the \fIselabel*\fR interfaces do not have any specific support for a namespace hierarchy.
|
|
.sp
|
|
SE-PostgreSQL has a namespace hierarchy where a database is the top level object with the schema being the next level. Under the schema object there can be other types of objects such as tables and procedures. This hierarchy is supported as follows:
|
|
.RS
|
|
.RS
|
|
.sp
|
|
If a security context is required for "my_table" table in the "public"
|
|
schema within the "postgres" database, then the \fBselabel_lookup\fR(3)
|
|
parameters for \fIobject_type\fR would be \fBSELABEL_DB_TABLE\fR and the
|
|
\fIobject_name\fR would be "postgres.public.my_table", the security
|
|
context (if available), would be returned in \fIcontext\fR.
|
|
.RE
|
|
.RE
|
|
.IP "3." 4
|
|
If contexts are to be validated, then the global option \fBSELABEL_OPT_VALIDATE\fR must be set before calling \fBselabel_open\fR(3). If this is not set, then it is possible for an invalid context to be returned.
|
|
.
|
|
.SH "SEE ALSO"
|
|
.ad l
|
|
.nh
|
|
.BR selinux "(8), " selabel_open "(3), " selabel_lookup "(3), " selabel_stats "(3), " selabel_close "(3), " selinux_set_callback "(3), " selinux_sepgsql_context_path "(3), " freecon "(3), " selinux_config "(5) "
|