+If you are interested in working on refpolicy feel free to contact the developers at either selinux@tresys.com or on the SELinux mailing list. All public development related discussion happens on the SELinux mailing list. +
\ No newline at end of file diff --git a/www/html/getting-started.html b/www/html/getting-started.html index dd3e0146f..940aa5c29 100644 --- a/www/html/getting-started.html +++ b/www/html/getting-started.html @@ -11,7 +11,7 @@ Modules should be placed in refpolicy/policy/LAYER, where LAYER is the name of t-First, let's create myapp.te and add the following: +First create myapp.te and add the following:
# Private type declarations @@ -38,19 +38,20 @@ allow myapp_t myapp_log_t:file ra_file_perms; allow myapp_t myapp_tmp_t:file create_file_perms;
This allows myapp_t to write to it's private types, but it needs to be able to +create its temporary files in /tmp. This requires a call to the files module.
files_create_tmp_files(myapp_t,myapp_tmp_t,file)
This call to the files module allows myapp_t to create myapp_tmp_t files in the /tmp directory.
-First, let's create myapp.if and add the following: +The interface file creates the macros that other modules will use to gain access to my resources. This allows the module that created the type or attribute to define appropriate uses. Additionally, it provides a single point for documentation. Create myapp.if and add the following:
## <module name="myapp" layer="apps"> @@ -102,6 +103,7 @@ define(`myapp_read_log',` ## </module>
The first interface allows other domains to do a domain transition to myapp_t, by executing a program labeled myapp_exec_t.