File: semodule_package.8

package info (click to toggle)
policycoreutils 1.32-3
  • links: PTS
  • area: main
  • in suites: etch, etch-m68k
  • size: 2,804 kB
  • ctags: 717
  • sloc: ansic: 5,211; python: 2,505; makefile: 443; sh: 438; perl: 120
file content (52 lines) | stat: -rw-r--r-- 1,633 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
.TH SEMODULE_PACKAGE "8" "Nov 2005" "Security Enhanced Linux" NSA
.SH NAME 
semodule_package \- Create a SELinux policy module package.

.SH SYNOPSIS
.B semodule_package -o <output file> -m <module> [-f <file contexts>]
.br
.SH DESCRIPTION
.PP
semodule_package is the tool used to create a SELinux policy module
package from a binary policy module and optionally other data such as file
contexts.  semodule_package packages binary policy modules created by 
checkmodule.  The policy package created by semodule_package can then
be installed via semodule. 

.SH EXAMPLE
.nf
# Build a policy package for a base module.
$ semodule_package -o base.pp -m base.mod -f file_contexts
# Build a policy package for a httpd module.
$ semodule_package -o httpd.pp -m httpd.mod -f httpd.fc
# Build a policy package for local TE rules and no file contexts.
$ semodule_package -o local.pp -m local.mod 
.fi

.SH "OPTIONS"
.TP
.B \-o \-\-outfile <output file> 
Policy module package file generated by this tool.
.TP
.B  \-s \-\-seuser <seuser file>
seuser file to be included in the package.
.TP
.B  \-u \-\-user_extra <user extra file>
user_extra file to be included in the package.
.TP
.B  \-m \-\-module <Module file>
Policy module file to be included in the package.
.TP
.B  \-f \-\-fc	<File context file>
File contexts file for the module (optional).
.TP
.B  \-n \-\-nc <netfilter context file>
netfilter context file to be included in the package.

.SH SEE ALSO
.B checkmodule(8), semodule(8)
(8),
.SH AUTHORS
.nf
This manual page was written by Dan Walsh <dwalsh@redhat.com>.
The program was written by Karl MacMillan <kmacmillan@tresys.com>