yum-software-management rpm-info.xml,1.4,1.5
by fedora-docs-commits@redhat.com
Author: elliss
Update of /cvs/docs/yum-software-management
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv22636
Modified Files:
rpm-info.xml
Log Message:
- Removed "Maintaining Yum" section, and migrated content to other sections.
- Minor polishing.
Index: rpm-info.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/rpm-info.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- rpm-info.xml 19 Mar 2006 21:39:02 -0000 1.4
+++ rpm-info.xml 24 Mar 2006 20:37:13 -0000 1.5
@@ -28,10 +28,15 @@
</translation>
</titles>
<changelog order="newest-first">
+ <revision date="2006-03-24" number="1.3" role="doc">
+ <author worker="StuartEllis"/>
+<!--PLEASE SET "lang" ATTRIBUTE IN DETAILS WHERE NEEDED-->
+ <details>Minor restructuring of sections.</details>
+ </revision>
<revision date="2006-03-19" number="1.2" role="doc">
<author worker="StuartEllis"/>
<!--PLEASE SET "lang" ATTRIBUTE IN DETAILS WHERE NEEDED-->
- <details>Added sections on caching and plugins.</details>
+ <details lang="en_US">Added sections on caching and plugins.</details>
</revision>
<revision date="2006-03-13" number="1.1" role="doc">
<author worker="StuartEllis"/>
18 years, 1 month
selinux-faq/en_US doc-entities.xml,1.1,1.2
by fedora-docs-commits@redhat.com
Author: kwade
Update of /cvs/docs/selinux-faq/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv20209/en_US
Modified Files:
doc-entities.xml
Log Message:
Updating revision info for publishing.
Index: doc-entities.xml
===================================================================
RCS file: /cvs/docs/selinux-faq/en_US/doc-entities.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- doc-entities.xml 16 Mar 2006 19:43:06 -0000 1.1
+++ doc-entities.xml 24 Mar 2006 19:22:24 -0000 1.2
@@ -20,7 +20,7 @@
</entity>
<entity name="DOCDATE">
<comment>Last revision date, format YYYY-MM-DD</comment>
- <text>2006-02-10</text>
+ <text>2006-03-24</text>
</entity>
<entity name="DOCID">
<comment>Same for every document</comment>
18 years, 1 month
selinux-faq rpm-info.xml,1.6,1.7
by fedora-docs-commits@redhat.com
Author: kwade
Update of /cvs/docs/selinux-faq
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv20209
Modified Files:
rpm-info.xml
Log Message:
Updating revision info for publishing.
Index: rpm-info.xml
===================================================================
RCS file: /cvs/docs/selinux-faq/rpm-info.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- rpm-info.xml 22 Mar 2006 03:04:45 -0000 1.6
+++ rpm-info.xml 24 Mar 2006 19:22:18 -0000 1.7
@@ -38,6 +38,11 @@
</translation>
</titles>
<changelog order="newest-first">
+ <revision date="2006-03-21" number="1.5.4" role="doc">
+ <author worker="ChadSellers"/>
+ <details lang="en_US">Updated log file location for FC5 release, added
+ targeted domains FAQ</details>
+ </revision>
<revision date="2006-03-21" number="1.5.3" role="doc">
<author worker="ChadSellers"/>
<details lang="en_US">Numerous content updates for FC5 release</details>
18 years, 1 month
selinux-faq/en_US selinux-faq.xml,1.2,1.3
by fedora-docs-commits@redhat.com
Author: csellers
Update of /cvs/docs/selinux-faq/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv15666
Modified Files:
selinux-faq.xml
Log Message:
updated log file location for FC5 release, added targeted domains FAQ
Index: selinux-faq.xml
===================================================================
RCS file: /cvs/docs/selinux-faq/en_US/selinux-faq.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- selinux-faq.xml 22 Mar 2006 03:04:53 -0000 1.2
+++ selinux-faq.xml 24 Mar 2006 17:56:33 -0000 1.3
@@ -333,55 +333,103 @@
</para>
</answer>
</qandaentry>
-<!-- Need to update this for FC5
<qandaentry>
<question>
<para>
- What daemons are protected by the targeted policy?
+ What programs are protected by the targeted policy?
</para>
</question>
<answer>
<para>
- Currently, the list of daemons is:
+ Currently, the list of programs is approximately:
</para>
- <itemizedlist>
- <listitem>
- <para><command>dhcpd</command></para>
- </listitem>
- <listitem>
- <para><command>httpd</command>
- (<filename>apache.te</filename>)</para>
- </listitem>
- <listitem>
- <para><command>named</command></para>
- </listitem>
- <listitem>
- <para><command>nscd</command></para>
- </listitem>
- <listitem>
- <para><command>ntpd</command></para>
- </listitem>
- <listitem>
- <para><command>portmap</command></para>
- </listitem>
- <listitem>
- <para><command>snmpd</command></para>
- </listitem>
- <listitem>
- <para><command>squid</command></para>
- </listitem>
- <listitem>
- <para><command>syslogd</command></para>
- </listitem>
- </itemizedlist>
<para>
- The policy files for these daemons are found in
- <filename>/etc/selinux/targeted/src/policy/domains/program</filename>.
- In the future, more daemons will be added to the targeted policy
- protection.
- </para>
+ <filename>accton</filename>,
+ <filename>amanda</filename>,
+ <filename>httpd</filename> (apache),
+ <filename>arpwatch</filename>,
+ <filename>pam</filename>,
+ <filename>automount</filename>,
+ <filename>avahi</filename>,
+ <filename>named</filename>,
+ <filename>bluez</filename>,
+ <filename>lilo</filename>,
+ <filename>grub</filename>,
+ <filename>canna</filename>,
+ <filename>comsat</filename>,
+ <filename>cpucontrol</filename>,
+ <filename>cpuspeed</filename>,
+ <filename>cups</filename>,
+ <filename>cvs</filename>,
+ <filename>cyrus</filename>,
+ <filename>dbskkd</filename>,
+ <filename>dbus</filename>,
+ <filename>dhcpd</filename>,
+ <filename>dictd</filename>,
+ <filename>dmidecode</filename>,
+ <filename>dovecot</filename>,
+ <filename>fetchmail</filename>,
+ <filename>fingerd</filename>,
+ <filename>ftpd</filename> (vsftpd, proftpd, and muddleftpd),
+ <filename>gpm</filename>,
+ <filename>hald</filename>,
+ <filename>hotplug</filename>,
+ <filename>howl</filename>,
+ <filename>innd</filename>,
+ <filename>kerberos</filename>,
+ <filename>ktalkd</filename>,
+ <filename>openldap</filename>,
+ <filename>auditd</filename>,
+ <filename>syslog</filename>,
+ <filename>logwatch</filename>,
+ <filename>lpd</filename>,
+ <filename>lvm</filename>,
+ <filename>mailman</filename>,
+ <filename>module-init-tools</filename>,
+ <filename>mount</filename>,
+ <filename>mysql</filename>,
+ <filename>NetworkManager</filename>,
+ <filename>NIS</filename>,
+ <filename>nscd</filename>,
+ <filename>ntp</filename>,
+ <filename>pegasus</filename>,
+ <filename>portmap</filename>,
+ <filename>postfix</filename>,
+ <filename>postgresql</filename>,
+ <filename>pppd</filename>,
+ <filename>pptp</filename>,
+ <filename>privoxy</filename>,
+ <filename>procmail</filename>,
+ <filename>radiusd</filename>,
+ <filename>radvd</filename>,
+ <filename>rlogin</filename>,
+ <filename>nfs</filename>,
+ <filename>rsync</filename>,
+ <filename>samba</filename>,
+ <filename>saslauthd</filename>,
+ <filename>snmpd</filename>,
+ <filename>spamd</filename>,
+ <filename>squid</filename>,
+ <filename>stunnel</filename>,
+ <filename>dhcpc</filename>,
+ <filename>ifconfig</filename>,
+ <filename>sysstat</filename>,
+ <filename>tcp wrappers</filename>,
+ <filename>telnetd</filename>,
+ <filename>tftpd</filename>,
+ <filename>updfstab</filename>,
+ <filename>user management</filename> (passwd, useradd, etc.),
+ <filename>crack</filename>,
+ <filename>uucpd</filename>,
+ <filename>vpnc</filename>,
+ <filename>webalizer</filename>,
+ <filename>xend</filename>,
+ <filename>xfs</filename>,
+ <filename>zebra</filename>
+ </para>
</answer>
</qandaentry>
+<!--
<qandaentry>
<question>
<para>
@@ -1099,7 +1147,7 @@
additional customizations.
</para>
<screen>
-<computeroutput>audit2allow -M local -l -i /var/log/audit/audit.log
+<computeroutput>audit2allow -M local -l -i /var/log/messages
Generating type enforcment file: local.te
Compiling policy
checkmodule -M -m -o local.mod local.te
@@ -1113,6 +1161,10 @@
semodule -i local.pp</computeroutput>
</screen>
<para>
+ Note that the above assumes you are not using the audit daemon.
+ If you were using the audit daemon, then you should use
+ <filename>/var/log/audit/audit.log</filename> instead of
+ <filename>/var/log/messages</filename> as your log file.
This will generate a <filename>local.te</filename> file, that
looks something like the following:
</para>
@@ -1475,7 +1527,9 @@
<para>
I get a specific permission denial only when &SEL; is in enforcing
mode, but I don't see any audit messages in
- <filename>/var/log/audit/audit.log</filename>. How can I identify the
+ <filename>/var/log/messages</filename> (or
+ <filename>/var/log/audit/audit.log</filename> if using the audit
+ daemon). How can I identify the
cause of these silent denials?
</para>
</question>
@@ -2243,6 +2297,27 @@
</itemizedlist>
</answer>
</qandaentry>
+ <qandaentry>
+ <question>
+ <para>
+ Where are &SEL; AVC messages (denial logs, etc.) stored?
+ </para>
+ </question>
+ <answer>
+ <para>
+ In &FC; 2 and 3, SELinux AVC messages could be found in
+ <filename>/var/log/messages</filename>.
+ In &FC; 4, the audit daemon was added, and these messages
+ moved to
+ <filename>/var/log/audit/audit.log</filename>.
+ In &FC; 5, the audit daemon is not installed by default, and
+ consequently these messages can be found in
+ <filename>/var/log/messages</filename> unless you choose to
+ install the audit daemon, in which case AVC messages will be in
+ <filename>/var/log/audit/audit.log</filename>.
+ </para>
+ </answer>
+ </qandaentry>
</qandadiv>
<qandadiv id="faq-div-deploying-selinux">
<title>Deploying &SEL;</title>
18 years, 1 month
selinux-faq/en_US selinux-faq.xml,1.1,1.2
by fedora-docs-commits@redhat.com
Author: csellers
Update of /cvs/docs/selinux-faq/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv25627/en_US
Modified Files:
selinux-faq.xml
Log Message:
Numerous updates for FC5 release
Index: selinux-faq.xml
===================================================================
RCS file: /cvs/docs/selinux-faq/en_US/selinux-faq.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- selinux-faq.xml 16 Mar 2006 19:43:06 -0000 1.1
+++ selinux-faq.xml 22 Mar 2006 03:04:53 -0000 1.2
@@ -243,20 +243,16 @@
<listitem>
<para>
This package is common to all types of policy and contains
- config files/man pages.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><filename>selinux-policy-devel-<replaceable><version></replaceable>.noarch.rpm</filename></term>
- <listitem>
- <para>
- This is the development environment. This replaces the
- -sources package from the past. This package contains the
- interface files used in reference policy along with a
- Makefile and a small tool used to generate a policy template
- file. The interface files reside in
- /usr/share/selinux/refpolicy/headers directory.
+ config files/man pages. This includes the interface files
+ for the development environment. This replaces the -sources
+ package from the past. This package contains the interface
+ files used in Reference Policy along with a Makefile and a
+ small tool called <command>policygentool</command> used to
+ generate a policy template file. The interface files reside
+ in <filename>/usr/share/selinux/devel/headers</filename>
+ directory. If you want to see all of the policy files used
+ to build the Reference Policy you need to install the
+ src.rpm.
</para>
</listitem>
</varlistentry>
@@ -266,13 +262,20 @@
<term><filename>selinux-policy-mls-<replaceable><version></replaceable>.noarch.rpm</filename></term>
<listitem>
<para>
- Binary policy files are in /etc/selinux/policyname. The
- policy for the types and domains is configured separately
- from security context for the subjects and objects.
+ Binary policy files are in
+ <filename>/etc/selinux/<replaceable>policyname</replaceable>/</filename>.
+ The policy for the types and domains is configured
+ separately from security context for the subjects and
+ objects.
</para>
</listitem>
</varlistentry>
</variablelist>
+ <para>
+ More information on the different policies available in SELinux
+ can be found at
+ <ulink url="http://fedoraproject.org/wiki/SELinux/Policies"/>.
+ </para>
</answer>
</qandaentry>
<qandaentry id="qa-whatis-targeted-policy" xreflabel="What is the
@@ -323,11 +326,15 @@
each of the specific daemons, refer to <xref
linkend="qa-using-s-c-securitylevel"/>.
</para>
+ <para>
+ More information on the different policies available in SELinux
+ can be found at
+ <ulink url="http://fedoraproject.org/wiki/SELinux/Policies"/>.
+ </para>
</answer>
</qandaentry>
+<!-- Need to update this for FC5
<qandaentry>
-<!-- https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133403 thanks to -->
-<!-- dwalsh for supplying the source FAQs -->
<question>
<para>
What daemons are protected by the targeted policy?
@@ -398,6 +405,7 @@
</para>
</answer>
</qandaentry>
+-->
<qandaentry>
<question>
<para>
@@ -417,6 +425,11 @@
For example, <command>system-config-securitylevel</command> builds
a relabel into the startup scripts.
</para>
+ <para>
+ More information on the different policies available in SELinux
+ can be found at
+ <ulink url="http://fedoraproject.org/wiki/SELinux/Policies"/>.
+ </para>
</answer>
</qandaentry>
<qandaentry>
@@ -435,6 +448,11 @@
This policy is geared toward this sort of environment, and is
probably not useful to you unless you fall into this category.
</para>
+ <para>
+ More information on the different policies available in SELinux
+ can be found at
+ <ulink url="http://fedoraproject.org/wiki/SELinux/Policies"/>.
+ </para>
</answer>
</qandaentry>
<qandaentry id="faq-entry-whatis-refpolicy" xreflabel="Reference Policy">
@@ -446,14 +464,24 @@
<answer>
<para>
The <firstterm>Reference Policy</firstterm>
- is a new project designed to rewrite the entire SELinux policy in a
- way that is easier to use and understand. To do this, it uses
- the concepts of modularity, abstraction, and well-defined interfaces.
+ is a new project maintained by Tresys Technology
+ (<ulink url="http://www.tresys.com/"/>) designed to rewrite
+ the entire SELinux policy in a way that is easier to use and
+ understand. To do this, it uses the concepts of modularity,
+ abstraction, and well-defined interfaces.
Refer to <ulink
url="http://serefpolicy.sourceforge.net/"/>
for more information on the Reference Policy.
</para>
<para>
+ Note that Reference Policy is not a new type of policy, like
+ targeted or strict. Rather, it is a new base that policies can be
+ built from. Targeted, strict, and mls policies can all be built
+ from Reference Policy. In fact, one of the design goals of Reference
+ Policy is to have a single unified source tree for the different
+ policy variants.
+ </para>
+ <para>
Fedora policies at version 1.x are based on the traditional example
policy. Version 2.x policies (as used in &FC; &LOCALVER;) are based
on the Reference Policy.
@@ -517,6 +545,71 @@
</para>
</answer>
</qandaentry>
+ <qandaentry id="faq-entry-whatare-policy-modules" xreflabel="Policy Modules">
+ <question>
+ <para>
+ What are policy modules?
+ </para>
+ </question>
+ <answer>
+ <para>
+ Prior to &FC; 5, SELinux policies were monolithic, meaning that
+ they were compiled into a single policy binary. To make changes
+ or additions to that policy, an administrator had to change out
+ the entire policy. With &FC; 5, the policy is now modular. This
+ means that third party developers can ship policy modules with
+ their applications, and then they can be added to the policy
+ without having to switch out the entire policy in much the
+ same way that kernel modules can add funcationality to the kernel
+ without having to reboot the entire system.
+ </para>
+ <para>
+ This actually works by separating out compile and link steps
+ in the policy build procedure. Policy modules are compiled from
+ source, and linked when installed into the module store (see
+ <xref linkend="faq-entry-whatis-managed-policy"/>). This linked
+ policy is then loaded into the kernel for enforcement.
+ </para>
+ <para>
+ The primary command for dealing with modules is
+ <command>semodule</command>, which will let you perform basic
+ functions such as installing, upgrading, or removing modules.
+ Modules are usually stored as policy package file (.pp
+ extension) in
+ <filename>/usr/share/selinux/<replaceable>policyname</replaceable>/</filename>.
+ There you should at least
+ find the base.pp, which is the base module.
+ </para>
+ </answer>
+ </qandaentry>
+ <qandaentry id="faq-entry-whatis-managed-policy" xreflabel="Managed Policy">
+ <question>
+ <para>
+ What is managed policy?
+ </para>
+ </question>
+ <answer>
+ <para>
+ Prior to &FC; 5, SELinux policies were handled as user-editable
+ config files in etc. Unfortunately, this made it difficult to
+ address many of the usability issues arising with SELinux. So, a
+ new libraray, <filename>libsemanage</filename>, was added to
+ provide userspace tools an interface to making policy management
+ easier. All policy management should use this library to access
+ the policy store. The policy store holds all the policy
+ information, and is found at
+ <filename>/etc/selinux/<replaceable>policyname</replaceable>/</filename>.
+ </para>
+ <para>
+ You should never have to edit the store directly. Instead, you
+ should use tools that link against libsemanage. One example tool
+ is <command>semanage</command>, which is a command line tool for
+ managing much of the policy such as SELinux user mappings,
+ SELinux port mappings, and file contexts entries. Other graphical
+ tools are currently being developed as well.
+ </para>
+ </answer>
+ </qandaentry>
</qandadiv>
<qandadiv id="faq-div-controlling-selinux">
<title>Controlling &SEL;</title>
@@ -882,14 +975,13 @@
</para>
<note>
<title><computeroutput>sysadm_r</computeroutput> Role
- Required</title>
+ Required for strict policy</title>
<para>
You must issue the <command>setenforce</command> command with
- the <computeroutput>sysadm_r</computeroutput> role. Use the
+ the <computeroutput>sysadm_r</computeroutput> role if you are
+ using strict policy. If you are using the standard targeted
+ policy, then this is not necessary. Use the
<command>newrole</command> command to assume this role.
- Alternately, if you switch to root using <command>su
- -</command>, you assume the
- <computeroutput>sysadm_r</computeroutput> role automatically.
</para>
</note>
</answer>
@@ -943,6 +1035,160 @@
</para>
</answer>
</qandaentry>
+ <qandaentry>
+ <question>
+ <para>
+ How do I write policy to allow a domain to use pam_unix.so?
+ </para>
+ </question>
+ <answer>
+ <para>
+ Very few domains in the SELinux world are allowed to read the
+ <filename>/etc/shadow</filename> file. There are constraint rules
+ that prevent policy writers from writing code like
+ </para>
+<screen>
+<command>allow mydomain_t shadow_t:file read;</command>
+</screen>
+ <para>
+ In RHEL4 you can setup your domain to use the
+ <command>unix_chkpwd</command> command. The easiest way is to use
+ the <command>unix_chkpwd</command> attribute. So if you were
+ writing policy for an ftpd daemon you would write something like
+ </para>
+<screen>
+<command>daemon_domain(vsftpd, `auth_chkpwd')</command>
+</screen>
+ <para>
+ This would create a context where
+ vsftpd_t -> chkpwd_exec_t -> system_chkpwd_t which can read
+ <filename>/etc/shadow</filename>, while vsftpd_t is not able to
+ read it.
+ </para>
+ <para>
+ In &FC; &LOCALVER;/RHEL5, add the rule
+ </para>
+<screen>
+<command>auth_domtrans_chk_passwd(vsftpd_t)</command>
+</screen>
+ </answer>
+ </qandaentry>
+ <qandaentry>
+ <question>
+ <para>
+ In the past I have written local.te file in policy sources for my
+ own local customization to policy, how do I do this with
+ Reference Policy?
+ </para>
+ </question>
+ <answer>
+ <para>
+ If you have specific AVC messages you can use
+ <command>audit2allow</command> to
+ generate a Type Enforcement file that is ready to load as a policy
+ module.
+ </para>
+<screen>
+<command>audit2allow -M local < /tmp/avcs</command>
+</screen>
+ <para>
+ This will create a <filename>local.pp</filename> which you can
+ then load into the kernel using
+ <command>semodule -i local.pp</command>.
+ You can also edit the <filename>local.te</filename> to make
+ additional customizations.
+ </para>
+<screen>
+<computeroutput>audit2allow -M local -l -i /var/log/audit/audit.log
+Generating type enforcment file: local.te
+Compiling policy
+checkmodule -M -m -o local.mod local.te
+semodule_package -o local.pp -m local.mod
+
+******************** IMPORTANT ***********************
+
+In order to load this newly created policy package into the kernel,
+you are required to execute
+
+semodule -i local.pp</computeroutput>
+</screen>
+ <para>
+ This will generate a <filename>local.te</filename> file, that
+ looks something like the following:
+ </para>
+<screen>
+<computeroutput>module local 1.0;
+
+require {
+ class file { append execute execute_no_trans getattr ioctl read write };
+ type httpd_t;
+ type httpd_w3c_script_exec_t;
+ };
+
+
+allow httpd_t httpd_w3c_script_exec_t:file { execute execute_no_trans getattr ioctl read };</computeroutput>
+</screen>
+ <para>
+ You can hand edit this file and then recompile and reload it
+ using
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <command>checkmodule</command> to compile the te file
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <command>semodule_package</command> to create a policy package
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <command>semodule</command> to add it to the current machines running policy
+ </para>
+ </listitem>
+ </itemizedlist>
+ <note>
+ <title>Important</title>
+ <para>
+ In order to load this newly created policy package into the
+ kernel, you are required to execute
+ <command>semodule -i local.pp</command>
+ </para>
+ </note>
+ </answer>
+ </qandaentry>
+ <qandaentry>
+ <question>
+ <para>
+ I created a new Policy Package where do I put it to make sure that
+ it gets loaded into the kernel?
+ </para>
+ </question>
+ <answer>
+ <para>
+ All you need to do execute the
+ <command>semodule -i myapp.pp</command>
+ command. This modifies the policy that is stored on the machine.
+ Everytime for now on your policy module will get loaded with the
+ rest of the policy. You can even remove the pp file from the
+ system.
+ </para>
+ <para>
+ <command>semodule -l</command> will list the currently loaded
+ modules.
+ </para>
+<screen>
+<computeroutput>#semodule -i
+myapp 1.2.1</computeroutput>
+</screen>
+ <para>
+ If you later would like to remove the policy package, you can
+ execute <command>semodule -r myapp</command>.
+ </para>
+ </answer>
+ </qandaentry>
</qandadiv>
<qandadiv id="faq-div-resolving-problems">
<title>Resolving Problems</title>
@@ -1186,7 +1432,7 @@
<para>
If you wanted to not audit <command>dmesg</command>, for example,
you would put this in your
- <filename>/etc/selinux/targeted/src/policy/dmesg.te</filename>
+ <filename>dmesg.te</filename>
file:
</para>
<screen>
@@ -1224,8 +1470,6 @@
</para>
</answer>
</qandaentry>
- <!-- Need to modify this to work with new policy sources, or find
- a better method than modifying all source
<qandaentry>
<question>
<para>
@@ -1248,9 +1492,7 @@
auditing of all <computeroutput>dontaudit</computeroutput> rules:
</para>
<screen>
-<command>cd /etc/selinux/targeted/src/policy
-make enableaudit
-make load</command>
+<command>semodule -b /usr/share/selinux/targeted/enableaudit.pp</command>
</screen>
<caution>
<title>Enabled <computeroutput>dontaudit</computeroutput> output
@@ -1270,14 +1512,12 @@
</para>
</caution>
<para>
- To re-enable <computeroutput>dontaudit</computeroutput> rules, do
- the following:
+ Once you have found your problem you can reset to the default
+ mode by executin
</para>
<screen>
-<command>cd /etc/selinux/targeted/src/policy
-make clean
-make load</command>
-</screen> -->
+<command>semodule -b /usr/share/selinux/targeted/base.pp</command>
+</screen>
<!-- commented out just in case it needs to be rewritten and included:
<para>
Another reason for getting silent denials is on an
@@ -1301,10 +1541,9 @@
been fixed):
audit(1083674459.837:0): security_compute_sid: invalid context root:sysadm_r:system_chkpwd_t for scontext=root:sysadm_r:newrole_t tcontext=system_u:object_r:chkpwd_exec_t tclass=process
-
+-->
</answer>
</qandaentry>
--->
<qandaentry>
<question>
<para>
@@ -1559,11 +1798,10 @@
which shows examples of policy.
</para>
<para>
- If you want to write a new policy domain, you should install the
- <filename>selinux-policy-devel</filename> package. This will place
- reference policy interface files into the
- <filename>/usr/share/selinux/refpolicy</filename> directory.
- There are also tools available to help you generate new policy.
+ If you want to create a new policy domain, you can look at the
+ interface files in the
+ <filename>/usr/share/selinux/devel</filename> sub-directories.
+ There is also a tool there to help you get started.
The following procedure is an example:
</para>
<procedure>
@@ -1580,7 +1818,8 @@
<command>policygentool <replaceable>mydaemon /usr/sbin/mydaemon</replaceable></command>
</screen>
<para>
- This command creates three files:
+ It will prompt you for a few common domain characteristics,
+ and will create three files:
<filename>mydaemon.te</filename>,
<filename>mydaemon.fc</filename> and
<filename>mydaemon.if</filename>.
@@ -1590,8 +1829,9 @@
<para>
After you generate the policy files, use the supplied
Makefile,
- <filename>/usr/share/selinux/refpolicy/Makefile</filename>, to
- build a policy package:
+ <filename>/usr/share/selinux/devel/Makefile</filename>, to
+ build a policy package
+ (<filename>mydaemon.pp</filename>):
</para>
<screen>
<command>make -f /usr/share/selinux/refpolicy/Makefile</command>
@@ -1615,7 +1855,7 @@
mode and then use the init script to start your daemon:
</para>
<screen>
-<command>setenforce 1</command> <!-- is this right? -->
+<command>setenforce 0</command>
<command>service <replaceable>mydaemon</replaceable> restart</command>
</screen>
</step>
@@ -1623,12 +1863,14 @@
<para>
Now you can collect avc messages. You can use
<command>audit2allow</command> to translate the avc messages to
- allow rules and begin updating you
+ allow rules and begin updating your
<filename>mydaemon.te</filename> file. You should search for
interface macros in the
- <filename>/etc/selinux/refpolicy/include</filename> directory and
+ <filename>/usr/share/selinux/devel/include</filename> directory and
use these instead of using the allow rules directly, whenever
- possible. If you want more examples of polcy, you could always
+ possible. <command>audit2allow -R</command> will attempt to find
+ interfaces that match the allow rule.
+ If you want more examples of polcy, you could always
install the selinux-policy src rpm, which contains all of the
policy te files for the reference policy.
</para>
@@ -1729,6 +1971,278 @@
</para>
</answer>
</qandaentry>
+ <qandaentry>
+ <question>
+ <para>
+ I have a process running as
+ <computeroutput>unconfined_t</computeroutput>, and &SEL; is
+ still preventing my application from running.
+ </para>
+ </question>
+ <answer>
+ <para>
+ We have begun to confine the
+ <computeroutput>unconfined_t</computeroutput> domain somewhat.
+ SELinux restricts certain memory protection operation. Following
+ is a list of those denials, as well as possible reasons and
+ solutions for those denials.
+ For more information on these restrictions, see <ulink
+ url="http://people.redhat.com/drepper/selinux-mem.html"/>.
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term><computeroutput>execmod</computeroutput></term>
+ <listitem>
+ <para>
+ This is usually based on a library label. You can change
+ the context on the library with the
+ <command>chcon -t testrel_shlib_t
+ <replaceable>LIBRARY</replaceable></command>. Now your
+ application can run. Please report this as a bugzilla.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><computeroutput>execstack</computeroutput></term>
+ <listitem>
+ <para>
+ Attempt to <command>execstack -c
+ <replaceable>LIBRARY</replaceable></command>. Now try your
+ application again. If the application now works, the
+ library was mistakenly marked as requiring
+ <computeroutput>execstack</computeroutput>. Please report
+ this as a bugzilla.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><computeroutput>execmem, execheap</computeroutput></term>
+ <listitem>
+ <para>
+ A boolean for each one of these memory check errors have been
+ provided. So if you need to run an application requiring
+ either of these permissions, you can set the boolean
+ allow_exec* to fix the problem. For instance if you try to run
+ an application and you get an AVC message containing an
+ <computeroutput>execstack</computeroutput> failure. You can
+ set the boolean with
+ </para>
+<screen>
+<command>setsebool -P allow_execstack=1</command>
+</screen>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </answer>
+ </qandaentry>
+ <qandaentry>
+ <question>
+ <para>
+ What do these rpm errors mean?
+ </para>
+ </question>
+ <answer>
+<screen>
+<computeroutput>genhomedircon: Warning! No support yet for expanding ROLE macros in the /etc/selinux/mls/contexts/files/homedir_template file when using libsemanage.
+genhomedircon: You must manually update file_contexts.homedirs for any non-user_r users (including root).</computeroutput>
+</screen>
+ <para>
+ Some of the interfaces are not complete yet for selinux. Most
+ users should not care about this warning. It will only affect you
+ if you are running the policy package that is reporting the
+ problem and have non standard SELinux role/user combinations.
+ IE You are using some custom policy.
+ </para>
+<screen>
+<computeroutput>restorecon reset /etc/modprobe.conf context system_u:object_r:etc_runtime_t->system_u:object_r:modules_conf_t
+restorecon reset /etc/cups/ppd/homehp.ppd context user_u:object_r:cupsd_etc_t->system_u:object_r:cupsd_rw_etc_t</computeroutput>
+</screen>
+ <para>
+ During the update process, the selinux package runs restorecon on
+ the difference between the previously install policy file_context
+ and the newly install policy context. This maintains the correct
+ file context on disk.
+ </para>
+<screen>
+<computeroutput>libsepol.sepol_genbools_array: boolean hidd_disable_trans no longer in policy</computeroutput>
+</screen>
+ <para>
+ This indicates that the updated policy has removed the boolean
+ from policy.
+ </para>
+ </answer>
+ </qandaentry>
+ <qandaentry>
+ <question>
+ <para>
+ I want to run a daemon on a non standard port but &SEL; will not
+ allow me. How do get this to work?
+ </para>
+ </question>
+ <answer>
+ <para>
+ You can use the <command>semanage</command> command to define
+ additional ports. So say you want httpd to be able to listen on
+ port 8082. You could enter the command.
+ </para>
+<screen>
+<command>semanage port -a -p tcp -t http_port_t 8082</command>
+</screen>
+ </answer>
+ </qandaentry>
+ <qandaentry>
+ <question>
+ <para>
+ How do I add additional translations to my MCS/MLS system?
+ </para>
+ </question>
+ <answer>
+ <para>
+ Translations are handled through libsemanage. Use
+ <command>semanage translation -l</command> to list all current
+ translations.
+ </para>
+<screen>
+<computeroutput># semanage translation -l
+Level Translation
+
+s0
+s0-s0:c0.c255 SystemLow-SystemHigh
+s0:c0.c255 SystemHigh</computeroutput>
+</screen>
+ <para>
+ Now pick an unused category. Say you wanted to add
+ Payroll as a translation, and s0:c6 is unused.
+ </para>
+<screen>
+<computeroutput># semanage translation -a -T Payroll s0:c6
+# semanage translation -l
+Level Translation
+
+s0
+s0-s0:c0.c255 SystemLow-SystemHigh
+s0:c0.c255 SystemHigh
+s0:c6 Payroll</computeroutput>
+</screen>
+ </answer>
+ </qandaentry>
+ <qandaentry>
+ <question>
+ <para>
+ I have setup my MCS/MLS translations, now I want to designate
+ which users can read a given category?
+ </para>
+ </question>
+ <answer>
+ <para>
+ You can modify the range of categories a user can login with
+ by using <command>semanage</command>, as seen in this example.
+ </para>
+<screen>
+<computeroutput># semanage login -a -r s0-Payroll csellers
+# semanage login -l
+
+Login Name SELinux User MLS/MCS Range
+
+__default__ user_u s0
+csellers user_u s0-Payroll
+root root SystemLow-SystemHigh</computeroutput>
+</screen>
+ <para>
+ In the above example, the user csellers was given access to the
+ <computeroutput>Payroll</computeroutput> category with the first
+ command, as indicated in the listing output from the second
+ command.
+ </para>
+ </answer>
+ </qandaentry>
+ <qandaentry>
+ <question>
+ <para>
+ I am writing an php script that needs to create temporary files in
+ <filename>/tmp</filename> and then execute them, SELinux policy is
+ preventing this. What should I do?
+ </para>
+ </question>
+ <answer>
+ <para>
+ You should avoid having system applications writing to the
+ <filename>/tmp</filename> directory, since users tend to use the
+ <filename>/tmp</filename> directory also. It would be better to
+ create a directory elsewhere which could be owned by the apache
+ process and allow your script to write to it. You should label the
+ directory <computeroutput>httpd_sys_script_rw_t</computeroutput>.
+ </para>
+ </answer>
+ </qandaentry>
+ <qandaentry>
+ <question>
+ <para>
+ I am setting up swapping to a file, but I am seeing AVC messages
+ in my log files?
+ </para>
+ </question>
+ <answer>
+ <para>
+ You need to identify the swapfile to SELinux by setting its file
+ context to <computeroutput>swapfile_t</computeroutput>.
+ </para>
+<screen>
+<command>chcon -t swapfile_t <replaceable>SWAPFILE</replaceable></command>
+</screen>
+ </answer>
+ </qandaentry>
+ <qandaentry>
+ <question>
+ <para>
+ Please explain the
+ <computeroutput>relabelto</computeroutput>/<computeroutput>relabelfrom</computeroutput>
+ permissions?
+ </para>
+ </question>
+ <answer>
+ <para>
+ For files, <computeroutput>relabelfrom</computeroutput> means "Can
+ domain D relabel a file from (i.e. currently in) type T1?" and
+ <computeroutput>relabelto</computeroutput> means "Can domain D
+ relabel a file to type T2?", so both checks are applied upon a
+ file relabeling, where T1 is the original type of the type and T2
+ is the new type specified by the program.
+ </para>
+ <para>
+ Useful documents to look at:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Object class and permission summary by Tresys <ulink
+ url="http://tresys.com/selinux/obj_perms_help.shtml"/>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Implementing SELinux as an LSM technical report (describes
+ permission checks on a per-hook basis) <ulink
+ url="http://www.nsa.gov/selinux/papers/module-abs.cfm"/>.
+ This is also available in the selinux-doc package
+ (and more up-to-date there).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Integrating Flexible Support for Security Policies into the
+ Linux Operating System - technical report (describes original
+ design and implementation, including summary tables of
+ classes, permissions, and what permission checks are applied
+ to what system calls. It is not entirely up-to-date with
+ current implementation, but a good resource nonetheless).
+ <ulink
+ url="http://www.nsa.gov/selinux/papers/slinux-abs.cfm"/>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </answer>
+ </qandaentry>
</qandadiv>
<qandadiv id="faq-div-deploying-selinux">
<title>Deploying &SEL;</title>
@@ -1835,15 +2349,23 @@
work under &SEL;.
</para>
<para>
+ Note that with the addition of <xref
+ linkend="faq-entry-whatare-policy-modules"/>, it is now possible
+ for third-party developers to include policy modules with their
+ application. If you are a third-party developer or a
+ package-maintainer, please consider including a policy module
+ in your package. This will allow you to secure the behavior
+ of your application with the power of &SEL; for any user
+ insalling your package.
+ </para>
+ <para>
One important value that &FC; testers and users bring to the
community is extensive testing of third-party applications. With
that in mind, please bring your experiences to the appropriate
- mailing list, such as the fedora-selinux.list, for discussion. For
+ mailing list, such as the fedora-selinux list, for discussion. For
more information about that list, refer to <ulink
url="http://www.redhat.com/mailman/listinfo/fedora-selinux-list/"/>.
</para>
- <!-- Add policy modules section -->
- <!-- Add managed policy section -->
</answer>
</qandaentry>
</qandadiv>
18 years, 1 month
selinux-faq rpm-info.xml,1.5,1.6
by fedora-docs-commits@redhat.com
Author: csellers
Update of /cvs/docs/selinux-faq
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv25627
Modified Files:
rpm-info.xml
Log Message:
Numerous updates for FC5 release
Index: rpm-info.xml
===================================================================
RCS file: /cvs/docs/selinux-faq/rpm-info.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- rpm-info.xml 17 Mar 2006 02:44:05 -0000 1.5
+++ rpm-info.xml 22 Mar 2006 03:04:45 -0000 1.6
@@ -38,6 +38,10 @@
</translation>
</titles>
<changelog order="newest-first">
+ <revision date="2006-03-21" number="1.5.3" role="doc">
+ <author worker="ChadSellers"/>
+ <details lang="en_US">Numerous content updates for FC5 release</details>
+ </revision>
<revision date="2006-02-10" number="1.5.2" role="doc">
<author worker="PaulWFrields"/>
<details lang="en_US">Make admonition more easily maintainable</details>
18 years, 1 month
release-notes rpm-info.xml,1.9,1.10
by fedora-docs-commits@redhat.com
Author: kwade
Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv7548
Modified Files:
rpm-info.xml
Log Message:
Last copyright correction.
Index: rpm-info.xml
===================================================================
RCS file: /cvs/docs/release-notes/rpm-info.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- rpm-info.xml 1 Mar 2006 00:48:46 -0000 1.9
+++ rpm-info.xml 21 Mar 2006 07:04:40 -0000 1.10
@@ -18,7 +18,7 @@
</license>
<copyright>
<year>2006</year>
- <holder>Fedora Foundation and others</holder>
+ <holder>Red Hat, Inc. and others</holder>
</copyright>
<titles>
<translation lang="en">
18 years, 1 month
docs-common/common legalnotice-content-en_US.xml, 1.1, 1.2 legalnotice-content-en.xml, 1.13, 1.14 legalnotice-content-it.xml, 1.4, 1.5 legalnotice-content-p1-en_US.xml, 1.1, 1.2 legalnotice-content-p1-en.xml, 1.4, 1.5 legalnotice-content-p1-it.xml, 1.1, 1.2 legalnotice-content-p3-en_US.xml, 1.1, 1.2 legalnotice-content-p3-en.xml, 1.2, 1.3 legalnotice-content-p3-it.xml, 1.1, 1.2
by fedora-docs-commits@redhat.com
Author: kwade
Update of /cvs/docs/docs-common/common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv4857
Modified Files:
legalnotice-content-en_US.xml legalnotice-content-en.xml
legalnotice-content-it.xml legalnotice-content-p1-en_US.xml
legalnotice-content-p1-en.xml legalnotice-content-p1-it.xml
legalnotice-content-p3-en_US.xml legalnotice-content-p3-en.xml
legalnotice-content-p3-it.xml
Log Message:
Sorry, I perpetrated this mistake that carried on through translation; 'and others' covers every individual contributor, aiui.
Index: legalnotice-content-en_US.xml
===================================================================
RCS file: /cvs/docs/docs-common/common/legalnotice-content-en_US.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- legalnotice-content-en_US.xml 2 Mar 2006 23:06:38 -0000 1.1
+++ legalnotice-content-en_US.xml 21 Mar 2006 06:03:43 -0000 1.2
@@ -13,7 +13,7 @@
<title>Legal Notice</title> -->
<para>
- Copyright (c) 2006 by Fedora Foundation and others. This material may be
+ Copyright (c) 2006 by Red Hat, Inc. and others. This material may be
distributed only subject to the terms and conditions set forth in the Open
Publication License, v1.0, available at <ulink
url="http://www.opencontent.org/openpub/"/>.
@@ -40,7 +40,7 @@
<para>
FEDORA, FEDORA PROJECT, and the Fedora Logo are trademarks of Red Hat, Inc.,
are registered or pending registration in the U.S. and other countries, and
- are used here under license to the Fedora Foundation.
+ are used here under license to the Fedora Project.
</para>
<para>
Index: legalnotice-content-en.xml
===================================================================
RCS file: /cvs/docs/docs-common/common/legalnotice-content-en.xml,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- legalnotice-content-en.xml 28 Feb 2006 23:18:42 -0000 1.13
+++ legalnotice-content-en.xml 21 Mar 2006 06:03:43 -0000 1.14
@@ -13,7 +13,7 @@
<title>Legal Notice</title> -->
<para>
- Copyright (c) 2006 by Fedora Foundation and others. This material may be
+ Copyright (c) 2006 by Red Hat, Inc. and others. This material may be
distributed only subject to the terms and conditions set forth in the Open
Publication License, v1.0, available at <ulink
url="http://www.opencontent.org/openpub/"/>.
@@ -40,7 +40,7 @@
<para>
FEDORA, FEDORA PROJECT, and the Fedora Logo are trademarks of Red Hat, Inc.,
are registered or pending registration in the U.S. and other countries, and
- are used here under license to the Fedora Foundation.
+ are used here under license to the Fedora Project.
</para>
<para>
Index: legalnotice-content-it.xml
===================================================================
RCS file: /cvs/docs/docs-common/common/legalnotice-content-it.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- legalnotice-content-it.xml 1 Mar 2006 13:47:35 -0000 1.4
+++ legalnotice-content-it.xml 21 Mar 2006 06:03:43 -0000 1.5
@@ -13,7 +13,7 @@
<title>Legal Notice</title> -->
<para>
- Copyright (c) 2006 by Fedora Foundation ed altri. Questo materiale potrebbe essere
+ Copyright (c) 2006 by Red Hat, Inc. ed altri. Questo materiale potrebbe essere
distribuito solo soggetto ai termini e condizioni precedentemente fissati nella Open
Publication License, v1.0, disponibile su <ulink
url="http://www.opencontent.org/openpub/"/>.
@@ -40,7 +40,7 @@
<para>
FEDORA, FEDORA PROJECT, ed il Fedora Logo sono marchi di Red Hat, Inc.,
sono registrati o in attesa di registrazione negli U.S. ed in altri paesi, e
- sono usati qui sotto licenza della Fedora Foundation.
+ sono usati qui sotto licenza della Fedora Project.
</para>
<para>
Index: legalnotice-content-p1-en_US.xml
===================================================================
RCS file: /cvs/docs/docs-common/common/legalnotice-content-p1-en_US.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- legalnotice-content-p1-en_US.xml 2 Mar 2006 23:06:38 -0000 1.1
+++ legalnotice-content-p1-en_US.xml 21 Mar 2006 06:03:43 -0000 1.2
@@ -9,7 +9,7 @@
]>
<para>
- Copyright (c) 2006 by Fedora Foundation and others. This material may be
+ Copyright (c) 2006 by Red Hat, Inc. and others. This material may be
distributed only subject to the terms and conditions set forth in the Open
Publication License, v1.0, available at <ulink
url="http://www.opencontent.org/openpub/"/>.
Index: legalnotice-content-p1-en.xml
===================================================================
RCS file: /cvs/docs/docs-common/common/legalnotice-content-p1-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- legalnotice-content-p1-en.xml 28 Feb 2006 18:07:11 -0000 1.4
+++ legalnotice-content-p1-en.xml 21 Mar 2006 06:03:43 -0000 1.5
@@ -9,7 +9,7 @@
]>
<para>
- Copyright (c) 2006 by Fedora Foundation and others. This material may be
+ Copyright (c) 2006 by Red Hat, Inc. and others. This material may be
distributed only subject to the terms and conditions set forth in the Open
Publication License, v1.0, available at <ulink
url="http://www.opencontent.org/openpub/"/>.
Index: legalnotice-content-p1-it.xml
===================================================================
RCS file: /cvs/docs/docs-common/common/legalnotice-content-p1-it.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- legalnotice-content-p1-it.xml 4 Mar 2006 10:30:04 -0000 1.1
+++ legalnotice-content-p1-it.xml 21 Mar 2006 06:03:43 -0000 1.2
@@ -9,7 +9,7 @@
]>
<para>
- Copyright (c) 2006 da Fedora Foundation ed altri. Questo materiale pu�� essere
+ Copyright (c) 2006 da Red Hat, Inc. ed altri. Questo materiale pu�� essere
distribuito solo soggetto ai termini e condizioni fissati nella Open
Publication License, v1.0, disponibile su <ulink
url="http://www.opencontent.org/openpub/"/>.
Index: legalnotice-content-p3-en_US.xml
===================================================================
RCS file: /cvs/docs/docs-common/common/legalnotice-content-p3-en_US.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- legalnotice-content-p3-en_US.xml 2 Mar 2006 23:06:38 -0000 1.1
+++ legalnotice-content-p3-en_US.xml 21 Mar 2006 06:03:43 -0000 1.2
@@ -11,5 +11,5 @@
<para>
FEDORA, FEDORA PROJECT, and the Fedora Logo are trademarks of Red Hat, Inc.,
are registered or pending registration in the U.S. and other countries, and
- are used here under license to the Fedora Foundation.
+ are used here under license to the Fedora Project.
</para>
Index: legalnotice-content-p3-en.xml
===================================================================
RCS file: /cvs/docs/docs-common/common/legalnotice-content-p3-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- legalnotice-content-p3-en.xml 20 Feb 2006 21:13:23 -0000 1.2
+++ legalnotice-content-p3-en.xml 21 Mar 2006 06:03:43 -0000 1.3
@@ -11,5 +11,5 @@
<para>
FEDORA, FEDORA PROJECT, and the Fedora Logo are trademarks of Red Hat, Inc.,
are registered or pending registration in the U.S. and other countries, and
- are used here under license to the Fedora Foundation.
+ are used here under license to the Fedora Project.
</para>
Index: legalnotice-content-p3-it.xml
===================================================================
RCS file: /cvs/docs/docs-common/common/legalnotice-content-p3-it.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- legalnotice-content-p3-it.xml 4 Mar 2006 10:30:04 -0000 1.1
+++ legalnotice-content-p3-it.xml 21 Mar 2006 06:03:43 -0000 1.2
@@ -11,5 +11,5 @@
<para>
FEDORA, FEDORA PROJECT, ed il Fedora Logo sono marchi di Red Hat, Inc.,
sono registrati od in attesa di registrazione negli U.S. ed in altri paesi, e
- sono usati qui sotto licenza alla Fedora Foundation.
+ sono usati qui sotto licenza alla Fedora Project.
</para>
18 years, 1 month
install-guide/en_US entities.xml,1.1,1.2
by fedora-docs-commits@redhat.com
Author: pfrields
Update of /cvs/docs/install-guide/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv28198
Modified Files:
entities.xml
Log Message:
Fix locale in local entities
Index: entities.xml
===================================================================
RCS file: /cvs/docs/install-guide/en_US/entities.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- entities.xml 17 Mar 2006 19:40:20 -0000 1.1
+++ entities.xml 20 Mar 2006 13:34:10 -0000 1.2
@@ -10,7 +10,7 @@
</entity>
<entity name="DOCLANG">
<comment>Document language</comment>
- <text>en</text>
+ <text>en_US</text>
</entity>
<entity name="DOCVERSION">
<comment>Document version</comment>
18 years, 1 month
yum-software-management/en_US yum-software-management.xml,1.3,1.4
by fedora-docs-commits@redhat.com
Author: elliss
Update of /cvs/docs/yum-software-management/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv24103/en_US
Modified Files:
yum-software-management.xml
Log Message:
- Fix typo.
Index: yum-software-management.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/en_US/yum-software-management.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- yum-software-management.xml 19 Mar 2006 21:39:08 -0000 1.3
+++ yum-software-management.xml 19 Mar 2006 22:01:30 -0000 1.4
@@ -1508,8 +1508,8 @@
<tip>
<title>Plugin File Extension</title>
<para>
- The names of <command>yum</command> plugin files end with
- <filename>.py</filename>, the standard file extension for
+ The names of <command>yum</command> plugins end with
+ <filename>.py</filename>, the standard extension for
Python files.
</para>
</tip>
@@ -1538,7 +1538,7 @@
<filename>exampleplugin.py</filename>, enter the command:
</para>
<screen>
-<userinput>su -c 'cp example-lugin.py /usr/lib/yum-plugins/'</userinput>
+<userinput>su -c 'cp exampleplugin.py /usr/lib/yum-plugins/'</userinput>
</screen>
<para>
Enter the password for the
18 years, 1 month