[web] rebuild SELUG for es

Rüdiger Landmann rlandmann at fedoraproject.org
Sun Jun 13 22:20:49 UTC 2010


commit 92a612507eba60f0febda5f070b816ad5b5495f1
Author: Ruediger Landmann <r.landmann at redhat.com>
Date:   Mon Jun 14 08:18:22 2010 +1000

    rebuild SELUG for es

 fedoradocs.db                                      |  Bin 338944 -> 339968 bytes
 public_html/Sitemap                                |   16 +-
 .../Fedora-11-Security-Enhanced_Linux-es-ES.epub   |  Bin 331484 -> 339261 bytes
 .../Common_Content/css/common.css                  |   44 +-
 .../Common_Content/css/lang.css                    |    2 +
 .../html-single/Security-Enhanced_Linux/index.html | 1236 ++++++++++----------
 .../Common_Content/css/common.css                  |   44 +-
 .../Common_Content/css/lang.css                    |    2 +
 ...e-Security-Enhanced_Linux-Revision_History.html |    8 +-
 ...ap-Security-Enhanced_Linux-Confining_Users.html |   12 +-
 ...ecurity-Enhanced_Linux-Further_Information.html |    4 +-
 .../chap-Security-Enhanced_Linux-Introduction.html |   46 +-
 ...p-Security-Enhanced_Linux-SELinux_Contexts.html |   48 +-
 ...ap-Security-Enhanced_Linux-Targeted_Policy.html |   46 +-
 ...urity-Enhanced_Linux-Trademark_Information.html |   14 +-
 ...ap-Security-Enhanced_Linux-Troubleshooting.html |   12 +-
 ...curity-Enhanced_Linux-Working_with_SELinux.html |   38 +-
 .../11/html/Security-Enhanced_Linux/index.html     |    8 +-
 .../11/html/Security-Enhanced_Linux/pr01s02.html   |    4 +-
 .../pref-Security-Enhanced_Linux-Preface.html      |   22 +-
 ...d_Linux-Booleans-Booleans_for_NFS_and_CIFS.html |   34 +-
 ...hanced_Linux-Booleans-Configuring_Booleans.html |   20 +-
 ...-Booleans_for_Users_Executing_Applications.html |   24 +-
 ...nfining_Users-Changing_the_Default_Mapping.html |   14 +-
 ...fining_Existing_Linux_Users_semanage_login.html |   18 +-
 ...ng_Users-Confining_New_Linux_Users_useradd.html |   20 +-
 ...ed_Linux-Confining_Users-xguest_Kiosk_Mode.html |   16 +-
 ...ng_and_Disabling_SELinux-Disabling_SELinux.html |    8 +-
 ...ixing_Problems-Allowing_Access_audit2allow.html |   32 +-
 ...-Fixing_Problems-Manual_Pages_for_Services.html |   16 +-
 ...d_Linux-Fixing_Problems-Permissive_Domains.html |   30 +-
 ...Problems-Possible_Causes_of_Silent_Denials.html |   16 +-
 ...d_Linux-Fixing_Problems-Raw_Audit_Messages.html |   22 +-
 ...Problems-Searching_For_and_Viewing_Denials.html |   42 +-
 ...ced_Linux-Fixing_Problems-sealert_Messages.html |   28 +-
 ..._Linux-Further_Information-Other_Resources.html |   32 +-
 ...urity-Enhanced_Linux-Introduction-Examples.html |   30 +-
 ...ed_Linux-Introduction-SELinux_Architecture.html |    8 +-
 ...duction-SELinux_on_Other_Operating_Systems.html |    8 +-
 ..._SELinux_Labels_-Archiving_Files_with_star.html |   26 +-
 ...g_SELinux_Labels_-Archiving_Files_with_tar.html |   26 +-
 ...bels_-Checking_the_Default_SELinux_Context.html |   18 +-
 ...Linux_Labels_-Moving_Files_and_Directories.html |   18 +-
 ..._File_Systems-Changing_the_Default_Context.html |   18 +-
 ...e_Systems-Making_Context_Mounts_Persistent.html |    6 +-
 ...g_File_Systems-Mounting_an_NFS_File_System.html |   12 +-
 ...-Mounting_File_Systems-Multiple_NFS_Mounts.html |   14 +-
 ...ive_Domains-Denials_for_Permissive_Domains.html |   10 +-
 ...ux_Contexts-SELinux_Contexts_for_Processes.html |   20 +-
 ...ELinux_Contexts-SELinux_Contexts_for_Users.html |    8 +-
 ...Files-Persistent_Changes_semanage_fcontext.html |   78 +-
 ...geted_Policy-Confined_and_Unconfined_Users.html |   50 +-
 ...Linux-Targeted_Policy-Unconfined_Processes.html |   52 +-
 ...ems-Evolving_Rules_and_Broken_Applications.html |    8 +-
 ...Problems-How_are_Confined_Services_Running.html |   28 +-
 ...nced_Linux-Troubleshooting-Fixing_Problems.html |   16 +-
 ...oubleshooting-Top_Three_Causes_of_Problems.html |   30 +-
 ...hanced_Linux-Working_with_SELinux-Booleans.html |   20 +-
 ...ith_SELinux-Enabling_and_Disabling_SELinux.html |   44 +-
 ...rking_with_SELinux-Main_Configuration_File.html |   12 +-
 ...g_with_SELinux-Maintaining_SELinux_Labels_.html |   42 +-
 ...Working_with_SELinux-Mounting_File_Systems.html |   18 +-
 ...th_SELinux-SELinux_Contexts_Labeling_Files.html |   52 +-
 ...d_Linux-Working_with_SELinux-SELinux_Modes.html |   16 +-
 ...ith_SELinux-The_file_t_and_default_t_Types.html |   12 +-
 ...orking_with_SELinux-Which_Log_File_is_Used.html |   20 +-
 .../Fedora-11-Security-Enhanced_Linux-es-ES.pdf    |  Bin 582720 -> 594868 bytes
 .../Fedora-13-Security-Enhanced_Linux-es-ES.epub   |  Bin 339706 -> 340067 bytes
 .../Common_Content/css/common.css                  |   44 +-
 .../Common_Content/css/lang.css                    |    2 +
 .../html-single/Security-Enhanced_Linux/index.html |  434 ++++----
 .../Common_Content/css/common.css                  |   44 +-
 .../Common_Content/css/lang.css                    |    2 +
 ...e-Security-Enhanced_Linux-Revision_History.html |   15 +-
 ...ap-Security-Enhanced_Linux-Confining_Users.html |    6 +-
 ...ecurity-Enhanced_Linux-Further_Information.html |   10 +-
 .../chap-Security-Enhanced_Linux-Introduction.html |   34 +-
 ...p-Security-Enhanced_Linux-SELinux_Contexts.html |   28 +-
 ...ap-Security-Enhanced_Linux-Targeted_Policy.html |   53 +-
 ...urity-Enhanced_Linux-Trademark_Information.html |    8 +-
 ...ap-Security-Enhanced_Linux-Troubleshooting.html |    6 +-
 ...curity-Enhanced_Linux-Working_with_SELinux.html |   20 +-
 .../13/html/Security-Enhanced_Linux/index.html     |    8 +-
 .../13/html/Security-Enhanced_Linux/pr01s02.html   |    2 +-
 .../pref-Security-Enhanced_Linux-Preface.html      |   14 +-
 ...d_Linux-Booleans-Booleans_for_NFS_and_CIFS.html |   14 +-
 ...hanced_Linux-Booleans-Configuring_Booleans.html |    2 +-
 ...-Booleans_for_Users_Executing_Applications.html |   10 +-
 ...nfining_Users-Changing_the_Default_Mapping.html |    4 +-
 ...fining_Existing_Linux_Users_semanage_login.html |    6 +-
 ...ng_Users-Confining_New_Linux_Users_useradd.html |    2 +-
 ...ed_Linux-Confining_Users-xguest_Kiosk_Mode.html |    6 +-
 ...ng_and_Disabling_SELinux-Disabling_SELinux.html |    2 +-
 ...ixing_Problems-Allowing_Access_audit2allow.html |    6 +-
 ...-Fixing_Problems-Manual_Pages_for_Services.html |    2 +-
 ...d_Linux-Fixing_Problems-Permissive_Domains.html |    4 +-
 ...Problems-Possible_Causes_of_Silent_Denials.html |    4 +-
 ...d_Linux-Fixing_Problems-Raw_Audit_Messages.html |    2 +-
 ...Problems-Searching_For_and_Viewing_Denials.html |   24 +-
 ...ced_Linux-Fixing_Problems-sealert_Messages.html |   10 +-
 ..._Linux-Further_Information-Other_Resources.html |   40 +-
 ...urity-Enhanced_Linux-Introduction-Examples.html |   20 +-
 ...ed_Linux-Introduction-SELinux_Architecture.html |    4 +-
 ...duction-SELinux_on_Other_Operating_Systems.html |    6 +-
 ..._SELinux_Labels_-Archiving_Files_with_star.html |    2 +-
 ...g_SELinux_Labels_-Archiving_Files_with_tar.html |    2 +-
 ...bels_-Checking_the_Default_SELinux_Context.html |    6 +-
 ...Linux_Labels_-Moving_Files_and_Directories.html |    2 +-
 ..._File_Systems-Changing_the_Default_Context.html |    8 +-
 ...e_Systems-Making_Context_Mounts_Persistent.html |    2 +-
 ...g_File_Systems-Mounting_an_NFS_File_System.html |    4 +-
 ...-Mounting_File_Systems-Multiple_NFS_Mounts.html |    2 +-
 ...ive_Domains-Denials_for_Permissive_Domains.html |    2 +-
 ...ux_Contexts-SELinux_Contexts_for_Processes.html |    4 +-
 ...ELinux_Contexts-SELinux_Contexts_for_Users.html |    4 +-
 ...Files-Persistent_Changes_semanage_fcontext.html |   14 +-
 ...geted_Policy-Confined_and_Unconfined_Users.html |   14 +-
 ...Linux-Targeted_Policy-Unconfined_Processes.html |   16 +-
 ...ems-Evolving_Rules_and_Broken_Applications.html |    4 +-
 ...Problems-How_are_Confined_Services_Running.html |   10 +-
 ...nced_Linux-Troubleshooting-Fixing_Problems.html |    4 +-
 ...oubleshooting-Top_Three_Causes_of_Problems.html |   12 +-
 ...hanced_Linux-Working_with_SELinux-Booleans.html |    2 +-
 ...ith_SELinux-Enabling_and_Disabling_SELinux.html |    4 +-
 ...rking_with_SELinux-Main_Configuration_File.html |    6 +-
 ...g_with_SELinux-Maintaining_SELinux_Labels_.html |   10 +-
 ...Working_with_SELinux-Mounting_File_Systems.html |    2 +-
 ...th_SELinux-SELinux_Contexts_Labeling_Files.html |   14 +-
 ...d_Linux-Working_with_SELinux-SELinux_Modes.html |    4 +-
 ...ith_SELinux-The_file_t_and_default_t_Types.html |   10 +-
 ...orking_with_SELinux-Which_Log_File_is_Used.html |    8 +-
 .../Fedora-13-Security-Enhanced_Linux-es-ES.pdf    |  Bin 594963 -> 619066 bytes
 public_html/es-ES/toc.html                         |    4 +-
 public_html/toc.html                               |    4 +-
 134 files changed, 1864 insertions(+), 1912 deletions(-)
---
diff --git a/fedoradocs.db b/fedoradocs.db
index c922979..571376a 100644
Binary files a/fedoradocs.db and b/fedoradocs.db differ
diff --git a/public_html/Sitemap b/public_html/Sitemap
index 136bb52..27a60cb 100644
--- a/public_html/Sitemap
+++ b/public_html/Sitemap
@@ -3140,25 +3140,25 @@
 </url>
 <url>
 	<loc>http://docs.fedoraproject.org/es-ES/Fedora/13/epub/Security-Enhanced_Linux/Fedora-13-Security-Enhanced_Linux-es-ES.epub</loc>
-	<lastmod>2010-05-22</lastmod>
+	<lastmod>2010-06-13</lastmod>
 	<changefreq>monthly</changefreq>
 	<priority>0.8</priority>
 </url>
 <url>
 	<loc>http://docs.fedoraproject.org/es-ES/Fedora/13/html/Security-Enhanced_Linux/index.html</loc>
-	<lastmod>2010-05-22</lastmod>
+	<lastmod>2010-06-13</lastmod>
 	<changefreq>monthly</changefreq>
 	<priority>0.8</priority>
 </url>
 <url>
 	<loc>http://docs.fedoraproject.org/es-ES/Fedora/13/html-single/Security-Enhanced_Linux/index.html</loc>
-	<lastmod>2010-05-22</lastmod>
+	<lastmod>2010-06-13</lastmod>
 	<changefreq>monthly</changefreq>
 	<priority>0.8</priority>
 </url>
 <url>
 	<loc>http://docs.fedoraproject.org/es-ES/Fedora/13/pdf/Security-Enhanced_Linux/Fedora-13-Security-Enhanced_Linux-es-ES.pdf</loc>
-	<lastmod>2010-05-22</lastmod>
+	<lastmod>2010-06-13</lastmod>
 	<changefreq>monthly</changefreq>
 	<priority>0.8</priority>
 </url>
@@ -3548,25 +3548,25 @@
 </url>
 <url>
 	<loc>http://docs.fedoraproject.org/es-ES/Fedora/11/epub/Security-Enhanced_Linux/Fedora-11-Security-Enhanced_Linux-es-ES.epub</loc>
-	<lastmod>2009-11-17</lastmod>
+	<lastmod>2010-06-13</lastmod>
 	<changefreq>monthly</changefreq>
 	<priority>0.8</priority>
 </url>
 <url>
 	<loc>http://docs.fedoraproject.org/es-ES/Fedora/11/html/Security-Enhanced_Linux/index.html</loc>
-	<lastmod>2009-11-17</lastmod>
+	<lastmod>2010-06-13</lastmod>
 	<changefreq>monthly</changefreq>
 	<priority>0.8</priority>
 </url>
 <url>
 	<loc>http://docs.fedoraproject.org/es-ES/Fedora/11/html-single/Security-Enhanced_Linux/index.html</loc>
-	<lastmod>2009-11-17</lastmod>
+	<lastmod>2010-06-13</lastmod>
 	<changefreq>monthly</changefreq>
 	<priority>0.8</priority>
 </url>
 <url>
 	<loc>http://docs.fedoraproject.org/es-ES/Fedora/11/pdf/Security-Enhanced_Linux/Fedora-11-Security-Enhanced_Linux-es-ES.pdf</loc>
-	<lastmod>2009-11-17</lastmod>
+	<lastmod>2010-06-13</lastmod>
 	<changefreq>monthly</changefreq>
 	<priority>0.8</priority>
 </url>
diff --git a/public_html/es-ES/Fedora/11/epub/Security-Enhanced_Linux/Fedora-11-Security-Enhanced_Linux-es-ES.epub b/public_html/es-ES/Fedora/11/epub/Security-Enhanced_Linux/Fedora-11-Security-Enhanced_Linux-es-ES.epub
index b6ace08..fa94468 100644
Binary files a/public_html/es-ES/Fedora/11/epub/Security-Enhanced_Linux/Fedora-11-Security-Enhanced_Linux-es-ES.epub and b/public_html/es-ES/Fedora/11/epub/Security-Enhanced_Linux/Fedora-11-Security-Enhanced_Linux-es-ES.epub differ
diff --git a/public_html/es-ES/Fedora/11/html-single/Security-Enhanced_Linux/Common_Content/css/common.css b/public_html/es-ES/Fedora/11/html-single/Security-Enhanced_Linux/Common_Content/css/common.css
index e1f4d9f..d8a380f 100644
--- a/public_html/es-ES/Fedora/11/html-single/Security-Enhanced_Linux/Common_Content/css/common.css
+++ b/public_html/es-ES/Fedora/11/html-single/Security-Enhanced_Linux/Common_Content/css/common.css
@@ -50,7 +50,8 @@ body.desktop .book > .toc {
 	line-height:1.35em;
 }
 
-.toc .chapter, .toc .appendix, .toc .glossary {
+ .toc .glossary,
+.toc .chapter, .toc .appendix {
 	margin-top:1em;
 }
 
@@ -59,7 +60,8 @@ body.desktop .book > .toc {
 	display:block;
 }
 
-span.appendix, span.glossary {
+span.glossary,
+span.appendix {
 	display:block;
 	margin-top:0.5em;
 }
@@ -346,7 +348,6 @@ a.version:focus, a.version:hover {
 	clear:both;
 }
 
-
 /*revision history*/
 .revhistory {
 	display:block;
@@ -362,34 +363,24 @@ a.version:focus, a.version:hover {
 }
 
 .revhistory td {
-	text-align:right;
+	text-align :left;
 	padding:0em;
 	border: none;
 	border-top: 1px solid #fff;
+	font-weight: bold;
 }
 
-
-.revhistory tr td:first-child {
-	text-align:left;
+.revhistory .simplelist td {
+	font-weight: normal;
 }
 
-.revhistory tr td p, .revhistory tr td div.para {
-	text-align:left;
-	font-weight:bold;
-	display:block;
-	margin:0em;
-	padding:0em;
-	padding-bottom:0.7em;
-	border-bottom:1px solid #eee;
+.revhistory .simplelist {
+	margin-bottom: 1.5em;
+	margin-left: 1em;
 }
 
 .revhistory table th {
-	background-color:transparent;
-	color:#336699;
-	font-size:2em;
-	padding: 1em 0em;
-	border: none;
-	border-bottom:1px solid #eee;
+	display: none;
 }
 
 
@@ -901,6 +892,10 @@ th, td {
 	border: 1px solid #000;
 }
 
+.simplelist th, .simplelist td {
+	border: none;
+}
+
 table table td {
 	border-bottom:1px dotted #aaa;
 	background-color:white;
@@ -1007,7 +1002,8 @@ span.chapter {
 	margin-bottom:1em;
 }
 
-.glossary dt, .index dt {
+.glossary dt,
+.index dt {
 	color:#444;
 	padding-top:.5em;
 }
@@ -1375,10 +1371,6 @@ pre {
 	border-radius: 15px;
 }
 
-.term{
-	color:#336699;
-}
-
 .package, .citetitle {
 	font-style: italic;
 }
diff --git a/public_html/es-ES/Fedora/11/html-single/Security-Enhanced_Linux/Common_Content/css/lang.css b/public_html/es-ES/Fedora/11/html-single/Security-Enhanced_Linux/Common_Content/css/lang.css
index e69de29..81c3115 100644
--- a/public_html/es-ES/Fedora/11/html-single/Security-Enhanced_Linux/Common_Content/css/lang.css
+++ b/public_html/es-ES/Fedora/11/html-single/Security-Enhanced_Linux/Common_Content/css/lang.css
@@ -0,0 +1,2 @@
+/* place holder */
+
diff --git a/public_html/es-ES/Fedora/11/html-single/Security-Enhanced_Linux/index.html b/public_html/es-ES/Fedora/11/html-single/Security-Enhanced_Linux/index.html
index 5745a80..4102031 100644
--- a/public_html/es-ES/Fedora/11/html-single/Security-Enhanced_Linux/index.html
+++ b/public_html/es-ES/Fedora/11/html-single/Security-Enhanced_Linux/index.html
@@ -1,9 +1,9 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Security-Enhanced Linux</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><meta name="description" content="This book is about managing and using Security-Enhanced Linux." /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/im
 ages/image_right.png" alt="Documentation Site" /></a></p><div xml:lang="es-ES" class="book" title="Security-Enhanced Linux" lang="es-ES"><div class="titlepage"><div><div class="producttitle" font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><span class="productname">Fedora</span> <span class="productnumber">11</span></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h1 id="id2098166" class="title">Security-Enhanced Linux</h1></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h2 class="subtitle">User Guide</h2></div><p class="edition">Edición 1.3</p><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h3 class="corpauthor">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Linux con Seguridad Mejorada</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><meta name="description" content="Este libro es acerca de la administración y uso del Linux de Seguridad Mejorada." /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><im
 g src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><div xml:lang="es-ES" class="book" title="Linux con Seguridad Mejorada" lang="es-ES"><div class="titlepage"><div><div class="producttitle" font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><span class="productname">Fedora</span> <span class="productnumber">11</span></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h1 id="id678371" class="title">Linux con Seguridad Mejorada</h1></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h2 class="subtitle">Guía del Usuario</h2></div><p class="edition">Edición 1.3</p><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h3 class="corpauthor">
 		<span class="inlinemediaobject"><object data="Common_Content/images/title_logo.svg" type="image/svg+xml"> Fedora Documentation Project</object></span>
 
-	</h3></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div xml:lang="es-ES" class="authorgroup" lang="es-ES"><div class="author"><h3 class="author"><span class="firstname">Murray</span> <span class="surname">McAllister</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:mmcallis at redhat.com">mmcallis at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Daniel</span> <span class="surname">Walsh</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Security Engineering</span></div><code class="email"><a class="email" href="mailto:dwalsh at redhat.com">dwalsh at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Dominick</span> <span class="surname">Grift</span></h3><span class
 ="contrib">Technical editor for the Introduction, SELinux Contexts, Targeted Policy, Working with SELinux, Confining Users, and Troubleshooting chapters.</span> <div class="affiliation"><span class="orgname"></span> <span class="orgdiv"></span></div><code class="email"><a class="email" href="mailto:domg472 at gmail.com">domg472 at gmail.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Eric</span> <span class="surname">Paris</span></h3><span class="contrib">Technical editor for the Mounting File Systems and Raw Audit Messages sections.</span> <div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Security Engineering</span></div><code class="email"><a class="email" href="mailto:eparis at parisplace.org">eparis at parisplace.org</a></code></div><div class="author"><h3 class="author"><span class="firstname">James</span> <span class="surname">Morris</span></h3><span class="contrib">Technical editor for the Introduction and Targ
 eted Policy chapters.</span> <div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Security Engineering</span></div><code class="email"><a class="email" href="mailto:jmorris at redhat.com">jmorris at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Scott</span> <span class="surname">Radvan</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:sradvan at redhat.com">sradvan at redhat.com</a></code></div></div></div><hr /><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div id="id1823271" class="legalnotice"><h1 class="legalnotice">Aviso Legal</h1><div class="para">
+	</h3></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div xml:lang="es-ES" class="authorgroup" lang="es-ES"><div class="author"><h3 class="author"><span class="firstname">Murray</span> <span class="surname">McAllister</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:mmcallis at redhat.com">mmcallis at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Daniel</span> <span class="surname">Walsh</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Security Engineering</span></div><code class="email"><a class="email" href="mailto:dwalsh at redhat.com">dwalsh at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Dominick</span> <span class="surname">Grift</span></h3><span class
 ="contrib">Technical editor for the Introduction, SELinux Contexts, Targeted Policy, Working with SELinux, Confining Users, and Troubleshooting chapters.</span> <div class="affiliation"><span class="orgname"></span> <span class="orgdiv"></span></div><code class="email"><a class="email" href="mailto:domg472 at gmail.com">domg472 at gmail.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Eric</span> <span class="surname">Paris</span></h3><span class="contrib">Technical editor for the Mounting File Systems and Raw Audit Messages sections.</span> <div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Security Engineering</span></div><code class="email"><a class="email" href="mailto:eparis at parisplace.org">eparis at parisplace.org</a></code></div><div class="author"><h3 class="author"><span class="firstname">James</span> <span class="surname">Morris</span></h3><span class="contrib">Technical editor for the Introduction and Targ
 eted Policy chapters.</span> <div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Security Engineering</span></div><code class="email"><a class="email" href="mailto:jmorris at redhat.com">jmorris at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Scott</span> <span class="surname">Radvan</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:sradvan at redhat.com">sradvan at redhat.com</a></code></div></div></div><hr /><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div id="id762015" class="legalnotice"><h1 class="legalnotice">Aviso Legal</h1><div class="para">
 		Copyright <span class="trademark"></span>© 2009 Red Hat, Inc. and others.
 	</div><div class="para">
 		The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at <a href="http://creativecommons.org/licenses/by-sa/3.0/">http://creativecommons.org/licenses/by-sa/3.0/</a>. The original authors of this document, and Red Hat, designate the Fedora Project as the "Attribution Party" for purposes of CC-BY-SA. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
@@ -22,24 +22,24 @@
 	</div><div class="para">
 		All other trademarks are the property of their respective owners.
 	</div></div></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div class="abstract" title="Resumen"><h6>Resumen</h6><div class="para">
-			This book is about managing and using Security-Enhanced <span class="trademark">Linux</span>®.
-		</div></div></div></div><hr /></div><div class="toc"><dl><dt><span class="preface"><a href="#pref-Security-Enhanced_Linux-Preface">Preface</a></span></dt><dd><dl><dt><span class="section"><a href="#id453696">1. Convenciones del Documento</a></span></dt><dd><dl><dt><span class="section"><a href="#id1623466">1.1. Convenciones Tipográficas</a></span></dt><dt><span class="section"><a href="#id1650144">1.2. Convenciones del documento</a></span></dt><dt><span class="section"><a href="#id1640274">1.3. Notas y Advertencias</a></span></dt></dl></dd><dt><span class="section"><a href="#id472182">2. ¡Necesitamos sus comentarios!</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Security-Enhanced_Linux-Trademark_Information">1. Trademark Information</a></span></dt><dd><dl><dt><span class="section"><a href="#chap-Security-Enhanced_Linux-Trademark_Information-Source_Code">1.1. Source Code</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Security-Enhance
 d_Linux-Introduction">2. Introduction</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Introduction-Benefits_of_running_SELinux">2.1. Benefits of running SELinux</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Introduction-Examples">2.2. Examples</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture">2.3. SELinux Architecture</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Introduction-SELinux_on_Other_Operating_Systems">2.4. SELinux on Other Operating Systems</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Security-Enhanced_Linux-SELinux_Contexts">3. SELinux Contexts</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-SELinux_Contexts-Domain_Transitions">3.1. Domain Transitions</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-SELi
 nux_Contexts-SELinux_Contexts_for_Processes">3.2. SELinux Contexts for Processes</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Users">3.3. SELinux Contexts for Users</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Security-Enhanced_Linux-Targeted_Policy">4. Targeted Policy</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Targeted_Policy-Confined_Processes">4.1. Confined Processes</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Targeted_Policy-Unconfined_Processes">4.2. Unconfined Processes</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users">4.3. Confined and Unconfined Users</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Security-Enhanced_Linux-Working_with_SELinux">5. Working with SELinux</a></span></dt><dd><dl><dt><span cl
 ass="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Packages">5.1. SELinux Packages</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used">5.2. Which Log File is Used</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Main_Configuration_File">5.3. Main Configuration File</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux">5.4. Enabling and Disabling SELinux</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Enabling_SELinux">5.4.1. Enabling SELinux</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux">5.4.2. Disabling SELinux</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security-Enhance
 d_Linux-Working_with_SELinux-SELinux_Modes">5.5. SELinux Modes</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans">5.6. Booleans</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Booleans-Listing_Booleans">5.6.1. Listing Booleans</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Booleans-Configuring_Booleans">5.6.2. Configuring Booleans</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS">5.6.3. Booleans for NFS and CIFS</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files">5.7. SELinux Contexts - Labeling Files</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Temporary_Changes_chcon">5.7.1. Temporary Changes: chcon</a></span></dt
 ><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext">5.7.2. Persistent Changes: semanage fcontext</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types">5.8. The file_t and default_t Types</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems">5.9. Mounting File Systems</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Mounting_File_Systems-Context_Mounts">5.9.1. Context Mounts</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Mounting_File_Systems-Changing_the_Default_Context">5.9.2. Changing the Default Context</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Mounting_File_Systems-Mounting_an_NFS_File_System">5.9.3. Mounting an NFS File Sys
 tem</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Mounting_File_Systems-Multiple_NFS_Mounts">5.9.4. Multiple NFS Mounts</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Mounting_File_Systems-Making_Context_Mounts_Persistent">5.9.5. Making Context Mounts Persistent</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_">5.10. Maintaining SELinux Labels </a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Copying_Files_and_Directories">5.10.1. Copying Files and Directories</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Moving_Files_and_Directories">5.10.2. Moving Files and Directories</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Defa
 ult_SELinux_Context">5.10.3. Checking the Default SELinux Context</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_tar">5.10.4. Archiving Files with tar</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_star">5.10.5. Archiving Files with star</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#chap-Security-Enhanced_Linux-Confining_Users">6. Confining Users</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Confining_Users-Linux_and_SELinux_User_Mappings">6.1. Linux and SELinux User Mappings</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Confining_Users-Confining_New_Linux_Users_useradd">6.2. Confining New Linux Users: useradd</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Confining_Users-Confining_
 Existing_Linux_Users_semanage_login">6.3. Confining Existing Linux Users: semanage login</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Confining_Users-Changing_the_Default_Mapping">6.4. Changing the Default Mapping</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Confining_Users-xguest_Kiosk_Mode">6.5. xguest: Kiosk Mode</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications">6.6. Booleans for Users Executing Applications</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Security-Enhanced_Linux-Troubleshooting">7. Troubleshooting</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Troubleshooting-What_Happens_when_Access_is_Denied">7.1. What Happens when Access is Denied</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Cau
 ses_of_Problems">7.2. Top Three Causes of Problems</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Labeling_Problems">7.2.1. Labeling Problems</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running">7.2.2. How are Confined Services Running?</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Evolving_Rules_and_Broken_Applications">7.2.3. Evolving Rules and Broken Applications</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems">7.3. Fixing Problems</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Linux_Permissions">7.3.1. Linux Permissions</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Possible
 _Causes_of_Silent_Denials">7.3.2. Possible Causes of Silent Denials</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services">7.3.3. Manual Pages for Services</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains">7.3.4. Permissive Domains</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Searching_For_and_Viewing_Denials">7.3.5. Searching For and Viewing Denials</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages">7.3.6. Raw Audit Messages</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages">7.3.7. sealert Messages</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow">7.3.8. Allowing Access: audit2allow</a></span>
 </dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#chap-Security-Enhanced_Linux-Further_Information">8. Further Information</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Further_Information-Contributors">8.1. Contributors</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Further_Information-Other_Resources">8.2. Other Resources</a></span></dt></dl></dd><dt><span class="appendix"><a href="#appe-Security-Enhanced_Linux-Revision_History">A. Revision History</a></span></dt></dl></div><div xml:lang="es-ES" class="preface" title="Preface" id="pref-Security-Enhanced_Linux-Preface" lang="es-ES"><div class="titlepage"><div><div><h1 class="title">Preface</h1></div></div></div><div class="para">
-		The Fedora 11 SELinux User Guide is for people with minimal or no experience with SELinux. Although system administration experience is not necessary, content in this guide is written for system administration tasks. This guide provides an introduction to fundamental concepts and practical applications of SELinux. After reading this guide you should have an intermediate understanding of SELinux.
+			Este libro es acerca de la administración y uso del <span class="trademark">Linux</span>® de Seguridad Mejorada.
+		</div></div></div></div><hr /></div><div class="toc"><dl><dt><span class="preface"><a href="#pref-Security-Enhanced_Linux-Preface">Prefacio</a></span></dt><dd><dl><dt><span class="section"><a href="#id744180">1. Convenciones del Documento</a></span></dt><dd><dl><dt><span class="section"><a href="#id857155">1.1. Convenciones Tipográficas</a></span></dt><dt><span class="section"><a href="#id728246">1.2. Convenciones del documento</a></span></dt><dt><span class="section"><a href="#id728296">1.3. Notas y Advertencias</a></span></dt></dl></dd><dt><span class="section"><a href="#id883887">2. ¡Necesitamos sus comentarios!</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Security-Enhanced_Linux-Trademark_Information">1. Información de Marca Comercial</a></span></dt><dd><dl><dt><span class="section"><a href="#chap-Security-Enhanced_Linux-Trademark_Information-Source_Code">1.1. Source Code</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Security
 -Enhanced_Linux-Introduction">2. Introducción</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Introduction-Benefits_of_running_SELinux">2.1. Beneficios de usar SELinux</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Introduction-Examples">2.2. Ejemplos</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture">2.3. Arquitectura de SELinux</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Introduction-SELinux_on_Other_Operating_Systems">2.4. SELinux en otros Sistemas Operativos</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Security-Enhanced_Linux-SELinux_Contexts">3. Contextos de SELinux</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-SELinux_Contexts-Domain_Transitions">3.1. Transiciones de Dominios</a></span></dt><dt><span class="section"><a href="#sect-Secur
 ity-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Processes">3.2. Contextos de SELinux para los Procesos</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Users">3.3. Contextos de SELinux para los Usuarios</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Security-Enhanced_Linux-Targeted_Policy">4. Política Destinado</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Targeted_Policy-Confined_Processes">4.1. Procesos Confinados</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Targeted_Policy-Unconfined_Processes">4.2. Procesos no Confinados</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users">4.3. Usuarios Confinados y no Confinados</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Security-Enhanced_Linux-Working_with_SELinux">5. 
 Trabajando con SELinux</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Packages">5.1. Paquetes de SELinux</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used">5.2. Qué Archivo Log se usa</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Main_Configuration_File">5.3. Archivo de Configuración Principal</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux">5.4. Habilitando y Deshabilitando SELinux</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Enabling_SELinux">5.4.1. Habilitando SELinux</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux">5.4.2. Deshabilitando SE
 Linux</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes">5.5. Modos de SELinux</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans">5.6. Booleanos</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Booleans-Listing_Booleans">5.6.1. Listando los Booleanos</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Booleans-Configuring_Booleans">5.6.2. Configurando los Booleanos</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS">5.6.3. Booleanos para NFS y CIFS</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files">5.7. Contextos de SELinux - Etiquetado de Archivos</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-En
 hanced_Linux-SELinux_Contexts_Labeling_Files-Temporary_Changes_chcon">5.7.1. Cambios Temporales: chcon</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext">5.7.2. Cambios Persistentes: semanage fcontext</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types">5.8. Los tipos file_t y default_t</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems">5.9. Montaje de Sistemas de Archivos</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Mounting_File_Systems-Context_Mounts">5.9.1. Montajes de Contexto</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Mounting_File_Systems-Changing_the_Default_Context">5.9.2. Cambio del Contexto Predeterminado</a></span></dt><dt><spa
 n class="section"><a href="#sect-Security-Enhanced_Linux-Mounting_File_Systems-Mounting_an_NFS_File_System">5.9.3. Montando un Sistema de Archivos NFS</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Mounting_File_Systems-Multiple_NFS_Mounts">5.9.4. Montajes NFS Múltiples</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Mounting_File_Systems-Making_Context_Mounts_Persistent">5.9.5. Haciendo Persistente los Contextos de Montajes</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_">5.10. Mantención de las Etiquetas de SELinux</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Copying_Files_and_Directories">5.10.1. Copia de Directorios y Archivos</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Moving_Files_
 and_Directories">5.10.2. Movimiento de Archivos y Directorios</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context">5.10.3. Chequeando el Contexto SELinux Predeterminado</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_tar">5.10.4. Archivando archivos con tar</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_star">5.10.5. Archivando archivos con tar</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#chap-Security-Enhanced_Linux-Confining_Users">6. Confinando a los Usuarios</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Confining_Users-Linux_and_SELinux_User_Mappings">6.1. Linux y los Mapeos de Usuarios de SELinux</a></span></dt><dt><span class="section"><a href="#sect-
 Security-Enhanced_Linux-Confining_Users-Confining_New_Linux_Users_useradd">6.2. Confinando Usuarios Nuevos de Linux: useradd</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Confining_Users-Confining_Existing_Linux_Users_semanage_login">6.3. Confinando Usuarios Linux Existentes: semanage login</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Confining_Users-Changing_the_Default_Mapping">6.4. Cambiando el Mapeo Predeterminado</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Confining_Users-xguest_Kiosk_Mode">6.5. xguest: Modo Kiosk</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications">6.6. Booleanos para que los Usuarios Ejecuten Aplicaciones</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Security-Enhanced_Linux-Troubleshooting">7. Solución a Problemas</a></span></dt><dd><dl><dt><s
 pan class="section"><a href="#sect-Security-Enhanced_Linux-Troubleshooting-What_Happens_when_Access_is_Denied">7.1. Qué pasa cuando el Acceso es Denegado</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems">7.2. Tres Principales Causas de Problemas</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Labeling_Problems">7.2.1. Problemas de Etiquetados</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running">7.2.2. ¿Cómo se Ejecutan los Servicios Confinados?</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Evolving_Rules_and_Broken_Applications">7.2.3. Evolucionando las Reglas y las Aplicaciones Rotas</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Troub
 leshooting-Fixing_Problems">7.3. Corrección de Problemas</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Linux_Permissions">7.3.1. Permisos de Linux</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Possible_Causes_of_Silent_Denials">7.3.2. Posibles Causas de las Negaciones Silenciosas</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services">7.3.3. Páginas de Manual para Servicios</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains">7.3.4. Dominios Permisivos</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Searching_For_and_Viewing_Denials">7.3.5. Búsqueda y Revisión de Negaciones</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages">7.
 3.6. Raw Audit Messages</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages">7.3.7. Mensajes sealert</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow">7.3.8. Permitiendo el Acceso: audit2allow</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#chap-Security-Enhanced_Linux-Further_Information">8. Información Adicional</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Further_Information-Contributors">8.1. Contributors</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Further_Information-Other_Resources">8.2. Other Resources</a></span></dt></dl></dd><dt><span class="appendix"><a href="#appe-Security-Enhanced_Linux-Revision_History">A. Revision History</a></span></dt></dl></div><div xml:lang="es-ES" class="preface" title="Prefacio" id="pref-Security-Enhance
 d_Linux-Preface" lang="es-ES"><div class="titlepage"><div><div><h1 class="title">Prefacio</h1></div></div></div><div class="para">
+		La Guía del Usuario de SELinux de Fedora 11 es para gente sin o con mínima experiencia con SELinux. Aunque la experiencia de administración de sistema no es necesario, el contenido de esta guía se escribe para tareas de administración del sistema. Esta guía provee una introducción a los conceptos fundamentales y aplicaciones prácticas de SELinux. Después de leer esta guía debe tener un entendimiento intermedio de SELinux.
 	</div><div class="para">
-		Thank you to everyone who offered encouragement, help, and testing - it is most appreciated. Very special thanks to:
+		Gracias a todos los que nos alentaron, ofrecieron ayuda y lo probaron - la ayuda es muy apreciada. Agradecimientos muy especiales a:
 	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-				Dominick Grift, Stephen Smalley, and Russell Coker for their contributions, help, and patience.
+				Dominick Grift, Stephen Smalley y Russell Coker por sus contribuciones, ayuda y paciencia.
 			</div></li><li class="listitem"><div class="para">
 				Karsten Wade for his help, adding a component for this guide to <a href="https://bugzilla.redhat.com/"> Red Hat Bugzilla</a>, and sorting out web hosting on <a href="http://docs.fedoraproject.org/">http://docs.fedoraproject.org/</a>.
 			</div></li><li class="listitem"><div class="para">
-				The <a href="http://fedoraproject.org/wiki/Infrastructure">Fedora Infrastructure Team</a> for providing hosting.
+				Al <a href="http://fedoraproject.org/wiki/Infrastructure">Equipo de Infraestructura de Fedora</a> por proveer el alojamiento.
 			</div></li><li class="listitem"><div class="para">
-				Jens-Ulrik Petersen for making sure the Red Hat Brisbane office has up-to-date Fedora mirrors.
-			</div></li></ul></div><div xml:lang="es-ES" class="section" title="1. Convenciones del Documento" lang="es-ES"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id453696">1. Convenciones del Documento</h2></div></div></div><div class="para">
+				Jens-Ulrik Petersen por asegurar que la oficina de Brisbane de Red Hat tenga espejos de Fedora actualizados.
+			</div></li></ul></div><div xml:lang="es-ES" class="section" title="1. Convenciones del Documento" lang="es-ES"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id744180">1. Convenciones del Documento</h2></div></div></div><div class="para">
 		Este manual utiliza varias convenciones para resaltar algunas palabras y frases y llamar la atención sobre ciertas partes específicas de información.
 	</div><div class="para">
 		En ediciones PDF y de papel, este manual utiliza tipos de letra procedentes de <a href="https://fedorahosted.org/liberation-fonts/">Liberation Fonts</a>. Liberation Fonts también se utilizan en ediciones de HTML si están instalados en su sistema. Si no, se muestran tipografías alternativas pero equivalentes. Nota: Red Hat Enterprise Linux 5 y siguientes incluyen Liberation Fonts predeterminadas.
-	</div><div class="section" title="1.1. Convenciones Tipográficas"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id1623466">1.1. Convenciones Tipográficas</h3></div></div></div><div class="para">
+	</div><div class="section" title="1.1. Convenciones Tipográficas"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id857155">1.1. Convenciones Tipográficas</h3></div></div></div><div class="para">
 			Se utilizan cuatro convenciones tipográficas para llamar la atención sobre palabras o frases específicas. Dichas convenciones y las circunstancias en que se aplican son las siguientes:
 		</div><div class="para">
 			<code class="literal">Negrita monoespaciado</code>
@@ -87,7 +87,7 @@
 			Aparte del uso estándar para presentar el título de un trabajo, las itálicas denotan el primer uso de un término nuevo e importante. Por ejemplo:
 		</div><div class="blockquote"><blockquote class="blockquote"><div class="para">
 				Publican es un sistema de publicación de <em class="firstterm">DocBook</em>.
-			</div></blockquote></div></div><div class="section" title="1.2. Convenciones del documento"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id1650144">1.2. Convenciones del documento</h3></div></div></div><div class="para">
+			</div></blockquote></div></div><div class="section" title="1.2. Convenciones del documento"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id728246">1.2. Convenciones del documento</h3></div></div></div><div class="para">
 			Los mensajes de salida de la terminal o fragmentos de código fuente se distinguen visualmente del texto circundante.
 		</div><div class="para">
 			Los mensajes de salida enviados a una terminal se muestran en <code class="computeroutput">romano monoespaciado</code> y se presentan así:
@@ -116,7 +116,7 @@ books_tests  Desktop1  downloads      images  notes  scripts  svgs
    }
 }
 
-</pre></div><div class="section" title="1.3. Notas y Advertencias"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id1640274">1.3. Notas y Advertencias</h3></div></div></div><div class="para">
+</pre></div><div class="section" title="1.3. Notas y Advertencias"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id728296">1.3. Notas y Advertencias</h3></div></div></div><div class="para">
 			Finalmente, utilizamos tres estilos visuales para llamar la atención sobre la información que de otro modo se podría pasar por alto.
 		</div><div class="note"><h2>Nota</h2><div class="para">
 				Una nota es una sugerencia, atajo o enfoque alternativo para una tarea determinada. Ignorar una nota no debería tener consecuencias negativas, pero podría perderse de algunos trucos que pueden facilitarle las cosas.
@@ -124,90 +124,90 @@ books_tests  Desktop1  downloads      images  notes  scripts  svgs
 				Important boxes detail things that are easily missed: configuration changes that only apply to the current session, or services that need restarting before an update will apply. Ignoring a box labeled 'Important' won't cause data loss but may cause irritation and frustration.
 			</div></div><div class="warning"><h2>Advertencia</h2><div class="para">
 				Las advertencias no deben ignorarse. Ignorarlas muy probablemente ocasionará pérdida de datos.
-			</div></div></div></div><div xml:lang="es-ES" class="section" title="2. ¡Necesitamos sus comentarios!" lang="es-ES"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id472182">2. ¡Necesitamos sus comentarios!</h2></div></div></div><a id="id472426" class="indexterm"></a><div class="para">
+			</div></div></div></div><div xml:lang="es-ES" class="section" title="2. ¡Necesitamos sus comentarios!" lang="es-ES"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id883887">2. ¡Necesitamos sus comentarios!</h2></div></div></div><a id="id883896" class="indexterm"></a><div class="para">
 		Si encuentra un error tipográfico en este manual o si sabe de alguna manera de mejorarlo, nos gustaría escuchar sus sugerencias. Por favor complete un reporte en Bugzilla: <a href="http://bugzilla.redhat.com/bugzilla/">http://bugzilla.redhat.com/bugzilla/</a> usando el producto <span class="application"><strong>Fedora Documentation</strong></span>.
 	</div><div class="para">
 		Cuando envíe un reporte de error no olvide mencionar el identificador del manual: <em class="citetitle">selinux-user-guide</em>
 	</div><div class="para">
 		Si tiene una sugerencia para mejorar la documentación, intente ser tan específico como sea posible cuando describa su sugerencia. Si ha encontrado un error, por favor incluya el número de sección y parte del texto que rodea el error para que podamos encontrarlo más fácilmente.
-	</div></div></div><div xml:lang="es-ES" class="chapter" title="Capítulo 1. Trademark Information" id="chap-Security-Enhanced_Linux-Trademark_Information" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 1. Trademark Information</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#chap-Security-Enhanced_Linux-Trademark_Information-Source_Code">1.1. Source Code</a></span></dt></dl></div><div class="para">
-		<span class="trademark">Linux</span>® is the registered trademark of Linus Torvalds in the U.S. and other countries.
+	</div></div></div><div xml:lang="es-ES" class="chapter" title="Capítulo 1. Información de Marca Comercial" id="chap-Security-Enhanced_Linux-Trademark_Information" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 1. Información de Marca Comercial</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#chap-Security-Enhanced_Linux-Trademark_Information-Source_Code">1.1. Source Code</a></span></dt></dl></div><div class="para">
+		<span class="trademark">Linux</span>® es una marca comercial registrada de Linus Torvalds en los EEUU y en otros países.
 	</div><div class="para">
-		UNIX is a registered trademark of The Open Group.
+		UNIX es una marca comercial registrada de El Grupo Abierto.
 	</div><div class="para">
-		Type Enforcement is a trademark of Secure Computing, LLC, a wholly owned subsidiary of McAfee, Inc., registered in the U.S. and in other countries. Neither McAfee nor Secure Computing, LLC, has consented to the use or reference to this trademark by the author outside of this guide.
+		Type Enforcement (Obligación de Tipos) es una marca comercial de Secure Computing, LLC, una subsidiaria de McAfee, Inc., registrada en los EEUU y en otros países. Ni McAfee ni Secure Computing, LLC, ha consentido el uso o referencia de esta marca comercial para el autor fuera de esta guía.
 	</div><div class="para">
-		Apache is a trademark of The Apache Software Foundation.
+		Apache es una marca comercial de La Fundación de Software Apache.
 	</div><div class="para">
-		MySQL is a trademark or registered trademark of MySQL AB in the U.S. and other countries.
+		MySQL es una marca comercial o marca comercial registrada de MySQL AB en los EEUU y en otros países.
 	</div><div class="section" title="1.1. Source Code" id="chap-Security-Enhanced_Linux-Trademark_Information-Source_Code"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">1.1. Source Code</h2></div></div></div><div class="para">
 			The XML source for this guide is available at <a href="http://svn.fedorahosted.org/svn/selinuxguide/">http://svn.fedorahosted.org/svn/selinuxguide/</a>
-		</div></div></div><div xml:lang="es-ES" class="chapter" title="Capítulo 2. Introduction" id="chap-Security-Enhanced_Linux-Introduction" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 2. Introduction</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Introduction-Benefits_of_running_SELinux">2.1. Benefits of running SELinux</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Introduction-Examples">2.2. Examples</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture">2.3. SELinux Architecture</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Introduction-SELinux_on_Other_Operating_Systems">2.4. SELinux on Other Operating Systems</a></span></dt></dl></div><div class="para">
-		Files, such as directories and devices, are called objects. Processes, such as a user running a command or the <span class="trademark">Mozilla</span>®<span class="trademark"> Firefox</span>® application, are called subjects. Most operating systems use a Discretionary Access Control (DAC) system that controls how subjects interact with objects, and how subjects interact with each other. On operating systems using DAC, users control the permissions of files (objects) that they own. For example, on <span class="trademark">Linux</span>® operating systems, users can make their home directories world-readable, giving users and processes (subjects) access to potentially sensitive information.
+		</div></div></div><div xml:lang="es-ES" class="chapter" title="Capítulo 2. Introducción" id="chap-Security-Enhanced_Linux-Introduction" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 2. Introducción</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Introduction-Benefits_of_running_SELinux">2.1. Beneficios de usar SELinux</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Introduction-Examples">2.2. Ejemplos</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture">2.3. Arquitectura de SELinux</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Introduction-SELinux_on_Other_Operating_Systems">2.4. SELinux en otros Sistemas Operativos</a></span></dt></dl></div><div class="para">
+		Los Archivos, tales como directorios y dispositivos, se llaman objetos. Los procesos, tal como un comando que ejecuta el usuario o la aplicación <span class="trademark">Mozilla</span>®<span class="trademark"> Firefox</span>®, se llaman sujetos. La mayoría de los sistemas oeprativos usan un sistema de Control de Acceso Discrecional (DAC), que controla cómo interactuan los sujetos con los objetos, y cómo los sujetos interactuan entre sí. En sistemas operativos que usan DAC, los usuarios controlan los permisos de archivos (objetos) de los que son dueños. Por ejemplo, en sistemas operativos <span class="trademark">Linux</span>®, los usuarios pueden hacer sus directorios legibles para el resto del mundo, dando a los usuarios y procesos (sujetos) acceso a información potencialmente sensible.
 	</div><div class="para">
-		DAC mechanisms are fundamentally inadequate for strong system security. DAC access decisions are only based on user identity and ownership, ignoring other security-relevant information such as the role of the user, the function and trustworthiness of the program, and the sensitivity and integrity of the data. Each user has complete discretion over their files, making it impossible to enforce a system-wide security policy. Furthermore, every program run by a user inherits all of the permissions granted to the user and is free to change access to the user's files, so no protection is provided against malicious software. Many system services and privileged programs must run with coarse-grained privileges that far exceed their requirements, so that a flaw in any one of these programs can be exploited to obtain complete system access.<sup>[<a id="id1642551" href="#ftn.id1642551" class="footnote">1</a>]</sup>
+		DAC mechanisms are fundamentally inadequate for strong system security. DAC access decisions are only based on user identity and ownership, ignoring other security-relevant information such as the role of the user, the function and trustworthiness of the program, and the sensitivity and integrity of the data. Each user has complete discretion over their files, making it impossible to enforce a system-wide security policy. Furthermore, every program run by a user inherits all of the permissions granted to the user and is free to change access to the user's files, so no protection is provided against malicious software. Many system services and privileged programs must run with coarse-grained privileges that far exceed their requirements, so that a flaw in any one of these programs can be exploited to obtain complete system access.<sup>[<a id="id647740" href="#ftn.id647740" class="footnote">1</a>]</sup>
 	</div><div class="para">
-		The following is an example of permissions used on Linux operating systems that do not run Security-Enhanced Linux (SELinux). The permissions in these examples may differ from your system. Use the <code class="command">ls -l</code> command to view file permissions:
+		El siguiente es un ejemplo de permisos usados en sistemas operativos Linux que no corren el Linux de Seguridad Mejorada (SELinux). Los permisos en estos ejemplos pueden diferir de su sistema. Use el comando <code class="command">ls -l</code> para ver los permisos de archivos:
 	</div><pre class="screen">$ ls -l file1
 -rwxrw-r-- 1 user1 group1 0 2009-04-30 15:42 file1
 
 </pre><div class="para">
-		The first three permission bits, <code class="computeroutput">rwx</code>, control the access the Linux <code class="computeroutput">user1</code> user (in this case, the owner) has to <code class="filename">file1</code>. The next three permission bits, <code class="computeroutput">rw-</code>, control the access the Linux <code class="computeroutput">group1</code> group has to <code class="filename">file1</code>. The last three permission bits, <code class="computeroutput">r--</code>, control the access everyone else has to <code class="filename">file1</code>, which includes all users and processes.
+		Los primeros tres bits de permisos, <code class="computeroutput">rwx</code>, controlan el acceso que el usuario Linux <code class="computeroutput">usuario1</code> (en este caso, el dueño) tiene para el <code class="filename">archivo1</code>. Los siguientes tres bits de permisos, <code class="computeroutput">rw-</code>, controlan el acceso que el grupo Linux <code class="computeroutput">grupo1</code> tiene para el <code class="filename">archivo1</code>. Los últimos tres bits de permisos, <code class="computeroutput">r--</code>, controlan el acceso que todo el mundo tiene para el <code class="filename">archivo1</code>, que incluyen a todos los usuarios y procesos.
 	</div><div class="para">
-		Security-Enhanced Linux (SELinux) adds Mandatory Access Control (MAC) to the Linux kernel, and is enabled by default in Fedora. A general purpose MAC architecture needs the ability to enforce an administratively-set security policy over all processes and files in the system, basing decisions on labels containing a variety of security-relevant information. When properly implemented, it enables a system to adequately defend itself and offers critical support for application security by protecting against the tampering with, and bypassing of, secured applications. MAC provides strong separation of applications that permits the safe execution of untrustworthy applications. Its ability to limit the privileges associated with executing processes limits the scope of potential damage that can result from the exploitation of vulnerabilities in applications and system services. MAC enables information to be protected from legitimate users with limited authorization as well as from a
 uthorized users who have unwittingly executed malicious applications.<sup>[<a id="id673419" href="#ftn.id673419" class="footnote">2</a>]</sup>
+		Security-Enhanced Linux (SELinux) adds Mandatory Access Control (MAC) to the Linux kernel, and is enabled by default in Fedora. A general purpose MAC architecture needs the ability to enforce an administratively-set security policy over all processes and files in the system, basing decisions on labels containing a variety of security-relevant information. When properly implemented, it enables a system to adequately defend itself and offers critical support for application security by protecting against the tampering with, and bypassing of, secured applications. MAC provides strong separation of applications that permits the safe execution of untrustworthy applications. Its ability to limit the privileges associated with executing processes limits the scope of potential damage that can result from the exploitation of vulnerabilities in applications and system services. MAC enables information to be protected from legitimate users with limited authorization as well as from a
 uthorized users who have unwittingly executed malicious applications.<sup>[<a id="id726676" href="#ftn.id726676" class="footnote">2</a>]</sup>
 	</div><div class="para">
-		The following is an example of the labels containing security-relevant information that are used on processes, Linux users, and files, on Linux operating systems that run SELinux. This information is called the SELinux context, and is viewed using the <code class="command">ls -Z</code> command:
+		El siguiente es un ejemplo de las etiquetas que contienen información de seguridad relevante que se usa en los procesos, usuarios Linux y archivos, en sistemas operativos Linux que corren SELinux. Esta información se llama contexto de SELinux y se visualiza usando el comando <code class="command">ls -Z</code>:
 	</div><pre class="screen">$ ls -Z file1
 -rwxrw-r--  user1 group1 unconfined_u:object_r:user_home_t:s0      file1
 
 </pre><div class="para">
-		In this example, SELinux provides a user (<code class="computeroutput">unconfined_u</code>), a role (<code class="computeroutput">object_r</code>), a type (<code class="computeroutput">user_home_t</code>), and a level (<code class="computeroutput">s0</code>). This information is used to make access control decisions. With DAC, access is controlled based only on Linux user and group IDs. SELinux policy rules are checked after DAC rules. SELinux policy rules are not used if DAC rules deny access first.
-	</div><div class="formalpara"><h5 class="formalpara">Linux and SELinux Users</h5>
+		En este ejemplo, SELinux provee un usuario (<code class="computeroutput">unconfined_u</code>), un rol (<code class="computeroutput">object_r</code>), un tipo (<code class="computeroutput">user_home_t</code>), y un nivel (<code class="computeroutput">s0</code>). Esta información se usa para tomar decisiones sobre el control de acceso. Con DAC, el acceso se controla basado sólo en los IDs de usuarios y grupos de Linux. Las reglas de políticas de SELinux se chequean después de las reglas DAC. Las reglas de políticas de SELInux no se usan si las reglas DAC niegan el acceso al principio.
+	</div><div class="formalpara" id="form-Security-Enhanced_Linux-Introduction-Linux_and_SELinux_Users"><h5 class="formalpara">Linux y los Usuarios SELinux</h5>
 			On Linux operating systems that run SELinux, there are Linux users as well as SELinux users. SELinux users are part of SELinux policy. Linux users are mapped to SELinux users. To avoid confusion, this guide uses "Linux user" and "SELinux user" to differentiate between the two.
-		</div><div class="section" title="2.1. Benefits of running SELinux" id="sect-Security-Enhanced_Linux-Introduction-Benefits_of_running_SELinux"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.1. Benefits of running SELinux</h2></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-					All processes and files are labeled with a type. A type defines a domain for processes, and a type for files. Processes are separated from each other by running in their own domains, and SELinux policy rules define how processes interact with files, as well as how processes interact with each other. Access is only allowed if an SELinux policy rule exists that specifically allows it.
+		</div><div class="section" title="2.1. Beneficios de usar SELinux" id="sect-Security-Enhanced_Linux-Introduction-Benefits_of_running_SELinux"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.1. Beneficios de usar SELinux</h2></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+					Todos los procesos y archivos se etiquetan con un tipo. Un tipo define un dominio para los procesos y un tipo para los archivos. Los procesos se separan entre sí corriéndolos en sus propios dominios, y las reglas de políticas de SELinux define cómo interactúan los procesos con los archivos, así como la forma en que interactúan entre sí. El acceso sólo se permite si existe una regla de política de SELinux que específicamente lo permita.
 				</div></li><li class="listitem"><div class="para">
-					Fine-grained access control. Stepping beyond traditional <span class="trademark">UNIX</span>® permissions that are controlled at user discretion and based on Linux user and group IDs, SELinux access decisions are based on all available information, such as an SELinux user, role, type, and, optionally, a level.
+					Control de acceso más fino. Yendo un paso más alla de los permisos tradicionales de <span class="trademark">UNIX</span>® que se controlan a discreción del usuario y se basa en los IDs de usuario y de grupos de Linux, las decisiones de accesos de SELinux se basan en toda la información disponible, tales como un usuario SELinux, el rol, el tipo y, opcionalmente, un nivel.
 				</div></li><li class="listitem"><div class="para">
-					SELinux policy is administratively-defined, enforced system-wide, and is not set at user discretion.
+					La política de SELinux se define administrativamente, obligando a todo el sistema, y no se pone a discreción del usuario.
 				</div></li><li class="listitem"><div class="para">
-					Reduced vulnerability to privilege escalation attacks. One example: since processes run in domains, and are therefore separated from each other, and SELinux policy rules define how processes access files and other processes, if a process is compromised, the attacker only has access to the normal functions of that process, and to files the process has been configured to have access to. For example, if the Apache HTTP Server is compromised, an attacker can not use that process to read files in user home directories, unless a specific SELinux policy rule was added or configured to allow such access.
+					Vulnerabilidad reducida para ataques de escalamiento de privilegios. Un ejemplo: dado que los procesos corren en dominios, y son por lo tanto separados entresi, y las reglas de la política de SELinux definen cómo los procesos acceden a los archivos y a otros procesos, si un proceso queda comprometido, el atacante sólo tiene acceso a las funciones normales de ese proceso, y a archivos a los que el proceso tiene configurado que puede acceder. Por ejemplo, si el Servidor HTTP Apache es comprometido, un atacante no puede usar el proceso para leer archivos en los directorios home de los usuarios, a menos que una regla específica de la política de SELinux haya sido agregada o configurada para permitir tal acceso.
 				</div></li><li class="listitem"><div class="para">
-					SELinux can be used to enforce data confidentiality and integrity, as well as protecting processes from untrusted inputs.
+					Se linux se puede usar para asegurar la confidencialidad e integridad de los datos, así como proteger los procesos de entradas no confiables.
 				</div></li></ul></div><div class="para">
-			SELinux is not:
+			SELinux no es:
 		</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-					antivirus software.
+					software antivirus.
 				</div></li><li class="listitem"><div class="para">
-					a replacement for passwords, firewalls, or other security systems.
+					un reemplazo para las contraseñas, cortafuegos y otros sistemas de seguridad.
 				</div></li><li class="listitem"><div class="para">
-					an all-in-one security solution.
+					una solución todo en uno.
 				</div></li></ul></div><div class="para">
-			SELinux is designed to enhance existing security solutions, not replace them. Even when running SELinux, continue to follow good security practices, such as keeping software up-to-date, using hard-to-guess passwords, firewalls, and so on.
-		</div></div><div class="section" title="2.2. Examples" id="sect-Security-Enhanced_Linux-Introduction-Examples"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.2. Examples</h2></div></div></div><div class="para">
-			The following examples demonstrate how SELinux increases security:
+			SELinux está diseñado para mejorar las soluciones de seguridad existentes, no reemplazarlas. Aún cuando corra SELinux, siga las buenas prácticas de seguridad, tales como mantener el software actualizado, usar contraseñas difíciles de adivinar, cortafuegos y demás.
+		</div></div><div class="section" title="2.2. Ejemplos" id="sect-Security-Enhanced_Linux-Introduction-Examples"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.2. Ejemplos</h2></div></div></div><div class="para">
+			Los siguientes ejemplos demuestran cómo SELinux aumenta la seguridad:
 		</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-					the default action is deny. If an SELinux policy rule does not exist to allow access, such as for a process opening a file, access is denied.
+					la acción por defecto es denegar. Si una regla de la política de SELinux no existe para permitir el acceso, como para que un proceso pueda abrir un archivo, el acceso es denegado.
 				</div></li><li class="listitem"><div class="para">
-					SELinux can confine Linux users. A number of confined SELinux users exist. Linux users can be mapped to SELinux users to take advantage of confined SELinux users. For example, mapping a Linux user to the SELinux user_u user, results in a Linux user that is not able to run (unless configured otherwise) set user ID (setuid) applications, such as <code class="command">sudo</code> and <code class="command">su</code>, as well as preventing them from executing files and applications in their home directory- if configured, this prevents users from executing malicious files from their home directories.
+					SELinux puede confinar a usuarios Linux. Existe un número de usuarios SELinux confinados. Los usuarios Linux se pueden mapear a usuarios SELinux para sacar ventaja de los usuarios SELinux confinados. Por ejemplo, mapear un usario Linux al usuario SELinux user_u, resulta en un usuario Linux que no puede ejecutar (a menos que se configure de otra forma) aplicaciones con el ID del usuario (setuid), tales como <code class="command">sudo</code> y <code class="command">su</code>, así como previene la ejecución de archivos y aplicaciones en sus directorios de inicio (home)- si se configura, esto evita que los usuarios ejecuten archivos maliciosos desde sus directorios de inicio.
 				</div></li><li class="listitem"><div class="para">
-					process separation. Processes run in their own domains, preventing processes from accessing files used by other processes, as well as processes accessing other processes. For example, when running SELinux, unless otherwise configured, an attacker can not compromise a Samba server, and then use that Samba server to read and write to files used by other processes, such as databases used by <span class="trademark">MySQL</span>®.
+					separación de procesos. Los procesos que corren en sus propios dominios, previenen que estos accedan a archivos usados por otros procesos, así como el acceso a otros procesos. Por ejemplo, cuando se ejecuta SELinux, a menos que se configure de otra forma, un atacante no puede comprometer un servidor Samba, y luego usar ese servidor Samba para leer y escribir archivos usados por otros procesos, tales como las bases de datos usadas por <span class="trademark">MySQL</span>®.
 				</div></li><li class="listitem"><div class="para">
-					help limit the damage done by configuration mistakes. <a href="http://en.wikipedia.org/wiki/Domain_Name_System">Domain Name System (DNS)</a> servers can replicate information between each other. This is known as a zone transfer. Attackers can use zone transfers to update DNS servers with false information. When running the <a href="https://www.isc.org/software/bind">Berkeley Internet Name Domain (BIND)</a> DNS server in Fedora 11, even if an administrator forgets to limit which servers can perform a zone transfer, the default SELinux policy prevents zone files <sup>[<a id="id1616703" href="#ftn.id1616703" class="footnote">3</a>]</sup> from being updated by zone transfers, the BIND <code class="systemitem">named</code> daemon, and other processes.
+					ayuda a limitar los daños hechos por errores en la configuración. Los servidores <a href="http://en.wikipedia.org/wiki/Domain_Name_System">Sistema de Nombres de Dominio (DNS)</a> pueden replicar información entre si. Esto se conoce como transferencia de zona. Los atacantes pueden usar las transferencias de zonas para actualizar los servidores de DNS con información falsa. Cuando se ejecuta el servidor de DNS <a href="https://www.isc.org/software/bind">Berkeley Internet Name Domain (BIND)</a> en Fedora 11, aún si un administrador se olvida de limitar qué servidores pueden realizar las transferencias de zona, la política predeterminada de SELinux evita que los archivos de zonas <sup>[<a id="id707849" href="#ftn.id707849" class="footnote">3</a>]</sup> sean actualizados por transferencias, por el demonio BIND <code class="systemitem">named</code> y por otros procesos.
 				</div></li><li class="listitem"><div class="para">
-					refer to the <a href="http://www.redhatmagazine.com/"><span class="trademark">Red Hat</span>® Magazine</a> article, <a href="http://www.redhatmagazine.com/2008/02/26/risk-report-three-years-of-red-hat-enterprise-linux-4/">Risk report: Three years of Red Hat Enterprise Linux 4</a><sup>[<a id="id1616743" href="#ftn.id1616743" class="footnote">4</a>]</sup>, for exploits that were restricted due to the default SELinux targeted policy in <span class="trademark">Red Hat</span>® Enterprise <span class="trademark">Linux</span>® 4.
+					refer to the <a href="http://www.redhatmagazine.com/"><span class="trademark">Red Hat</span>® Magazine</a> article, <a href="http://www.redhatmagazine.com/2008/02/26/risk-report-three-years-of-red-hat-enterprise-linux-4/">Risk report: Three years of Red Hat Enterprise Linux 4</a><sup>[<a id="id707884" href="#ftn.id707884" class="footnote">4</a>]</sup>, for exploits that were restricted due to the default SELinux targeted policy in <span class="trademark">Red Hat</span>® Enterprise <span class="trademark">Linux</span>® 4.
 				</div></li><li class="listitem"><div class="para">
-					refer to the <a href="http://www.linuxworld.com">LinuxWorld.com</a> article, <a href="http://www.linuxworld.com/news/2008/022408-selinux.html?page=1">A seatbelt for server software: SELinux blocks real-world exploits</a><sup>[<a id="id1840556" href="#ftn.id1840556" class="footnote">5</a>]</sup>, for background information about SELinux, and information about various exploits that SELinux has prevented.
+					refer to the <a href="http://www.linuxworld.com">LinuxWorld.com</a> article, <a href="http://www.linuxworld.com/news/2008/022408-selinux.html?page=1">A seatbelt for server software: SELinux blocks real-world exploits</a><sup>[<a id="id707926" href="#ftn.id707926" class="footnote">5</a>]</sup>, for background information about SELinux, and information about various exploits that SELinux has prevented.
 				</div></li><li class="listitem"><div class="para">
-					refer to James Morris's <a href="http://james-morris.livejournal.com/25421.html">SELinux mitigates remote root vulnerability in OpenPegasus</a> blog post, for information about an exploit in <a href="http://www.openpegasus.org/">OpenPegasus</a> that was mitigated by SELinux as shipped with Red Hat Enterprise Linux 4 and 5.
+					vaya al blog de James Morris <a href="http://james-morris.livejournal.com/25421.html">SELinux mitiga la vulnerabilidad de root en OpenPegasus</a>, para información acerca de una brecha en <a href="http://www.openpegasus.org/">OpenPegasus</a> que fue mitigada por SELinux tal como fue distribuido con el Linux para Empresas de Red Hat 4 y 5.
 				</div></li></ul></div><div class="para">
-			The <a href="http://www.tresys.com/">Tresys Technology</a> website has an <a href="http://www.tresys.com/innovation.php">SELinux Mitigation News</a> section (on the right-hand side), that lists recent exploits that have been mitigated or prevented by SELinux.
-		</div></div><div class="section" title="2.3. SELinux Architecture" id="sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.3. SELinux Architecture</h2></div></div></div><div class="para">
-			SELinux is a Linux security module that is built into the Linux kernel. SELinux is driven by loadable policy rules. When security-relevant access is taking place, such as when a process attempts to open a file, the operation is intercepted in the kernel by SELinux. If an SELinux policy rule allows the operation, it continues, otherwise, the operation is blocked and the process receives an error.
+			El sitio web de <a href="http://www.tresys.com/">Tresys Technology</a> tiene una sección de <a href="http://www.tresys.com/innovation.php">Noticias de Migración a SELinux</a> (en la parte derecha), que lista los ataques recientes que fueron mitigados o prevenidos por SELinux.
+		</div></div><div class="section" title="2.3. Arquitectura de SELinux" id="sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.3. Arquitectura de SELinux</h2></div></div></div><div class="para">
+			SELinux es un módulo de seguridad de Linux que se construye dentro del kernel de Linux. SELinux se maneja por reglas de políticas cargables. Cuando un acceso de seguridad relevante se lleva a cabo, tal como un proceso que trata de abrir un archivo, la operación es interceptada por SELinux en el kernel. Si una regla de política de SELinux permite la operación, continúa, sino, la operación se bloquea y el proceso recibe un error.
 		</div><div class="para">
-			SELinux decisions, such as allowing or disallowing access, are cached. This cache is known as the Access Vector Cache (AVC). Caching decisions decreases how often SELinux policy rules need to be checked, which increases performance. SELinux policy rules have no effect if DAC rules deny access first.
-		</div></div><div class="section" title="2.4. SELinux on Other Operating Systems" id="sect-Security-Enhanced_Linux-Introduction-SELinux_on_Other_Operating_Systems"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.4. SELinux on Other Operating Systems</h2></div></div></div><div class="para">
-			Refer to the following for information about running SELinux on operating systems:
+			Las decisiones de SELinux, tales como permitir o negar accesos, son cacheadas. Este caché se conoce como Caché Vector de Acceso (AVC). Las decisiones de cacheado disminuye la necesidad de que las reglas de políticas de SELinux sean chequeadas muy a menudo, lo que mejora la performance. Las reglas de políticas de SELinux no tienen efecto si las reglas DAC niegan el acceso primero.
+		</div></div><div class="section" title="2.4. SELinux en otros Sistemas Operativos" id="sect-Security-Enhanced_Linux-Introduction-SELinux_on_Other_Operating_Systems"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.4. SELinux en otros Sistemas Operativos</h2></div></div></div><div class="para">
+			Vaya a la siguiente información sobre cómo correr SELinux en sistemas operativos:
 		</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
 					Hardened Gentoo: <a href="http://www.gentoo.org/proj/en/hardened/selinux/selinux-handbook.xml">http://www.gentoo.org/proj/en/hardened/selinux/selinux-handbook.xml</a>.
 				</div></li><li class="listitem"><div class="para">
@@ -215,30 +215,30 @@ books_tests  Desktop1  downloads      images  notes  scripts  svgs
 				</div></li><li class="listitem"><div class="para">
 					Ubuntu: <a href="https://wiki.ubuntu.com/SELinux">https://wiki.ubuntu.com/SELinux</a> and <a href="https://help.ubuntu.com/community/SELinux">https://help.ubuntu.com/community/SELinux</a>.
 				</div></li><li class="listitem"><div class="para">
-					Red Hat Enterprise Linux: <a href="http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.2/html/Deployment_Guide/selg-overview.html">Red Hat Enterprise Linux Deployment Guide</a> and <a href="http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/selinux-guide/">Red Hat Enterprise Linux 4 SELinux Guide</a>.
+					Linux para Empresas de Red Hat: <a href="http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.2/html/Deployment_Guide/selg-overview.html">Guía de Despliegue del Linux para Empresas de Red Hat</a> y la <a href="http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/selinux-guide/">Guía de SELinux para el Linux para Empresas de Red Hat</a>.
 				</div></li><li class="listitem"><div class="para">
 					Fedora: <a href="http://fedoraproject.org/wiki/SELinux">http://fedoraproject.org/wiki/SELinux</a> and the <a href="http://docs.fedoraproject.org/selinux-faq-fc5/">Fedora Core 5 SELinux FAQ</a>.
-				</div></li></ul></div></div><div class="footnotes"><br /><hr width="100" align="left" /><div class="footnote"><p><sup>[<a id="ftn.id1642551" href="#id1642551" class="para">1</a>] </sup>
+				</div></li></ul></div></div><div class="footnotes"><br /><hr width="100" align="left" /><div class="footnote"><p><sup>[<a id="ftn.id647740" href="#id647740" class="para">1</a>] </sup>
 			"Integrating Flexible Support for Security Policies into the Linux Operating System", by Peter Loscocco and Stephen Smalley. This paper was originally prepared for the National Security Agency and is, consequently, in the public domain. Refer to the <a href="http://www.nsa.gov/research/_files/selinux/papers/freenix01/index.shtml">original paper</a> for details and the document as it was first released. Any edits and changes were done by Murray McAllister.
-		</p></div><div class="footnote"><p><sup>[<a id="ftn.id673419" href="#id673419" class="para">2</a>] </sup>
+		</p></div><div class="footnote"><p><sup>[<a id="ftn.id726676" href="#id726676" class="para">2</a>] </sup>
 			"Meeting Critical Security Objectives with Security-Enhanced Linux", by Peter Loscocco and Stephen Smalley. This paper was originally prepared for the National Security Agency and is, consequently, in the public domain. Refer to the <a href="http://www.nsa.gov/research/_files/selinux/papers/ottawa01/index.shtml">original paper</a> for details and the document as it was first released. Any edits and changes were done by Murray McAllister.
-		</p></div><div class="footnote"><p><sup>[<a id="ftn.id1616703" href="#id1616703" class="para">3</a>] </sup>
-						Text files that include information, such as hostname to IP address mappings, that are used by DNS servers.
-					</p></div><div class="footnote"><p><sup>[<a id="ftn.id1616743" href="#id1616743" class="para">4</a>] </sup>
+		</p></div><div class="footnote"><p><sup>[<a id="ftn.id707849" href="#id707849" class="para">3</a>] </sup>
+						Archivos de texto que incluyen información, tal como el mapeo de nombre de equipo a dirección IP, que usan los servidores de DNS.
+					</p></div><div class="footnote"><p><sup>[<a id="ftn.id707884" href="#id707884" class="para">4</a>] </sup>
 						Cox, Mark. "Risk report: Three years of Red Hat Enterprise Linux 4". Published 26 February 2008. Accessed 28 August 2008: <a href="http://www.redhatmagazine.com/2008/02/26/risk-report-three-years-of-red-hat-enterprise-linux-4/">http://www.redhatmagazine.com/2008/02/26/risk-report-three-years-of-red-hat-enterprise-linux-4/</a>.
-					</p></div><div class="footnote"><p><sup>[<a id="ftn.id1840556" href="#id1840556" class="para">5</a>] </sup>
+					</p></div><div class="footnote"><p><sup>[<a id="ftn.id707926" href="#id707926" class="para">5</a>] </sup>
 						Marti, Don. "A seatbelt for server software: SELinux blocks real-world exploits". Published 24 February 2008. Accessed 28 August 2008: <a href="http://www.linuxworld.com/news/2008/022408-selinux.html?page=1">http://www.linuxworld.com/news/2008/022408-selinux.html?page=1</a>.
-					</p></div></div></div><div xml:lang="es-ES" class="chapter" title="Capítulo 3. SELinux Contexts" id="chap-Security-Enhanced_Linux-SELinux_Contexts" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 3. SELinux Contexts</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-SELinux_Contexts-Domain_Transitions">3.1. Domain Transitions</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Processes">3.2. SELinux Contexts for Processes</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Users">3.3. SELinux Contexts for Users</a></span></dt></dl></div><div class="para">
-		Processes and files are labeled with an SELinux context that contains additional information, such as an SELinux user, role, type, and, optionally, a level. When running SELinux, all of this information is used to make access control decisions. In Fedora 11, SELinux provides a combination of Role-Based Access Control (RBAC), <span class="trademark">Type Enforcement</span>® (TE), and, optionally, Multi-Level Security (MLS).
+					</p></div></div></div><div xml:lang="es-ES" class="chapter" title="Capítulo 3. Contextos de SELinux" id="chap-Security-Enhanced_Linux-SELinux_Contexts" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 3. Contextos de SELinux</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-SELinux_Contexts-Domain_Transitions">3.1. Transiciones de Dominios</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Processes">3.2. Contextos de SELinux para los Procesos</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Users">3.3. Contextos de SELinux para los Usuarios</a></span></dt></dl></div><div class="para">
+		Los procesos y archivos se etiquetan con un contexto SELinux que contiene información adicional, tal como un usuario SELinux, rol, tipo y, opcionalmente, un nivel. Cuando se ejecuta SELinux, toda esta información se usa para tomar decisiones de control de acceso. En Fedora 11, SELinux provee una combinación de Control de Acceso Basado en Roles (RBAC en inglés), <span class="trademark">Obligación de Tipos</span>® (TE en inglés), y, opcionalmente, Seguridad Multi-nivel (MLS en inglés).
 	</div><div class="para">
-		The following is an example SELinux context. SELinux contexts are used on processes, Linux users, and files, on Linux operating systems that run SELinux. Use the <code class="command">ls -Z</code> command to view the SELinux context of files and directories:
+		El siguiente es un ejemplo de contexto de SELinux. Los contextos de SELinux se usan en procesos, usuarios de Linux y archivos, en sistemas operativos Linux que corren SELinux. Use el comando <code class="command">ls -Z</code> para ver el contexto SELinux de archivos y directorios:
 	</div><pre class="screen">$ ls -Z file1
 -rwxrw-r--  user1 group1 unconfined_u:object_r:user_home_t:s0      file1
 
 </pre><div class="para">
-		SELinux contexts follow the <span class="emphasis"><em>SELinux user:role:type:level</em></span> syntax:
+		Los contextos de SELinux siguen la <span class="emphasis"><em>SELinux nombre-de-usuario:role:type:level</em></span> sintaxis:
 	</div><div class="variablelist"><dl><dt><span class="term"><span class="emphasis"><em>SELinux user</em></span></span></dt><dd><div class="para">
-					The SELinux user identity is an identity known to the policy that is authorized for a specific set of roles, and for a specific MLS range. Each Linux user is mapped to an SELinux user via SELinux policy. This allows Linux users to inherit the restrictions on SELinux users. The mapped SELinux user identity is used in the SELinux context for processes in that session, in order to bound what roles and levels they can enter. Run the <code class="command">semanage login -l</code> command as the Linux root user to view a list of mappings between SELinux and Linux user accounts:
+					La identidad de usuario SELinux es una identidad conocida para la política a la que se le autoriza un conjunto específico de roles, y un rango específico de MLS. Cada usuario Linux se mapea a un usuario SELinux vía la política de SELinux. Esto permite a los usuarios de LInux heredar las restricciones de los usuarios SELinux. La identidad del usuario SELinux mapeado se usa en el contexto de SELinux para procesos en esa sesión, para agrupar a qué roles y niveles pueden ingresar. Ejecute el comando <code class="command">semanage login -l</code> como usuario root de Linux para ver una lista de mapeos entre cuentas de usuarios Linux y SELinux:
 				</div><pre class="screen">
 # /usr/sbin/semanage login -l
 
@@ -249,61 +249,61 @@ root                      unconfined_u              s0-s0:c0.c1023
 system_u                  system_u                  s0-s0:c0.c1023
 
 </pre><div class="para">
-					Output may differ from system to system. The <code class="computeroutput">Login Name</code> column lists Linux users, and the the <code class="computeroutput">SELinux User</code> column lists which SELinux user is mapped to which Linux user. For processes, the SELinux user limits which roles and levels are accessible. The last column, <code class="computeroutput">MLS/MCS Range</code>, is the level used by Multi-Level Security (MLS) and Multi-Category Security (MCS). Levels are briefly discussed later.
+					La salida puede ser distinta de sistema a sistema. La columna <code class="computeroutput">Nombre de Ingreso</code> lista los usuarios Linux, y la columna <code class="computeroutput">Usuario SELinux</code> lista qué a usuario SELinux es mapeado un usuario Linux. Para procesos, el usuario SELinux limita qué roles y niveles son accesibles. La última columna, <code class="computeroutput">Rango MLS/MCS</code>, es el nivel usado por la Seguridad Multi Nivel (MLS) y por la Seguridad Multi Categoría (MCS). Los niveles se describen brevemente más adelante.
 				</div></dd><dt><span class="term"><span class="emphasis"><em>role</em></span></span></dt><dd><div class="para">
-					Part of SELinux is the Role-Based Access Control (RBAC) security model. The role is an attribute of RBAC. SELinux users are authorized for roles, and roles are authorized for domains. The role serves as an intermediary between domains and SELinux users. The roles that can be entered determine which domains can be entered - ultimately, this controls which object types can be accessed. This helps reduce vulnerability to privilege escalation attacks.
+					Parte de SELinux es el modelo de seguridad de Control de Acceso Basado en Roles (RBAC). El rol es un atributo de RBAC. Los usuarios de SELinux son autorizados para ciertos roles y los roles son autorizados para ciertos dominios. Los roles sirven como un intermediario entre dominios y usarios SELinux. Los roles en los que se puede ingresar determinan los dominios a los que se ingresan - al final, esto controla los tipos de objetos que se pueden acceder. Esto ayuda a reducir la vulnerabilidad de ataques de escalada de privilegios.
 				</div></dd><dt><span class="term"><span class="emphasis"><em>type</em></span></span></dt><dd><div class="para">
-					The type is an attribute of Type Enforcement. The type defines a domain for processes, and a type for files. SELinux policy rules define how types access each other, whether it be a domain accessing a type, or a domain accessing another domain. Access is only allowed if a specific SELinux policy rule exists that allows it.
+					El tipo es un atributo de la Obligación de Tipos. El tipo define un dominio para procesos y un tipo para los archivos. Las reglas de políticas de SELinux define cómo se acceden los tipos entre si, ya sea un dominio que accede a un tipo o un dominio que accede a otro dominio. Los acceso sólo se permiten si existe una regla de política de SELinux que lo permita.
 				</div></dd><dt><span class="term"><span class="emphasis"><em>level</em></span></span></dt><dd><div class="para">
-					The level is an attribute of MLS and Multi-Category Security (MCS). An MLS range is a pair of levels, written as <span class="emphasis"><em>lowlevel-highlevel</em></span> if the levels differ, or <span class="emphasis"><em>lowlevel</em></span> if the levels are identical (<code class="computeroutput">s0-s0</code> is the same as <code class="computeroutput">s0</code>). Each level is a sensitivity-category pair, with categories being optional. If there are categories, the level is written as <span class="emphasis"><em>sensitivity:category-set</em></span>. If there are no categories, it is written as <span class="emphasis"><em>sensitivity</em></span>.
+					El nivel es un atributo de MLS y la Seguridad Multi Categoría (MCS). Un rango MLS es un par de niveles, escrito como <span class="emphasis"><em>bajonivel-altonivel</em></span> si los niveles sin distintos, o <span class="emphasis"><em>bajonivel</em></span> si los niveles son idénticos (<code class="computeroutput">s0-s0</code> es lo mismo que <code class="computeroutput">s0</code>). Cada nivel es un par sensible a categorías, donde las categorías son opcionales. Si no hay categorías, el nivel se escribe como <span class="emphasis"><em>sensibilidad:conjunto-de-categoría</em></span>. Si no hay categorías, se escribe como <span class="emphasis"><em>sensibilidad</em></span>.
 				</div><div class="para">
-					If the category set is a contiguous series, it can be abbreviated. For example, <code class="computeroutput">c0.c3</code> is the same as <code class="computeroutput">c0,c1,c2,c3</code>. The <code class="filename">/etc/selinux/targeted/setrans.conf</code> file maps levels (<code class="computeroutput">s0:c0</code>) to human-readable form (<code class="computeroutput">CompanyConfidential</code>). Do not edit <code class="filename">setrans.conf</code> with a text editor: use <code class="command">semanage</code> to make changes. Refer to the <span class="citerefentry"><span class="refentrytitle">semanage</span>(8)</span> manual page for further information. In Fedora 11, targeted policy enforces MCS, and in MCS, there is one sensitivity, <code class="computeroutput">s0</code>. MCS in Fedora 11 supports 1024 different categories: <code class="computeroutput">c0</code> through to <code class="computeroutput">c1023</code>. <code class="computeroutput">s0-s0:c0.c1023</code> is
  sensitivity <code class="computeroutput">s0</code> and authorized for all categories.
+					Si el conjunto de categoría es una serie contigua, se puede abreviar. Por ejemplo, <code class="computeroutput">c0.c3</code> es lo mismo que <code class="computeroutput">c0,c1,c2,c3</code>. El archivo <code class="filename">/etc/selinux/targeted/setrans.conf</code> mapea los niveles (<code class="computeroutput">s0:c0</code>) a una forma legible al humano (<code class="computeroutput">CompanyConfidential</code>). No edite <code class="filename">setrans.conf</code> con un editor de texto: use <code class="command">semanage</code> para hacer cambios. Vaya a la página de manual de <span class="citerefentry"><span class="refentrytitle">semanage</span>(8)</span> para más información. En Fedora 11, la política destinada obglica MCS, y en MCS hay sólo una sensibilidad, la <code class="computeroutput">s0</code>. MCS en Fedora 11 soporta 1024 categorías distintas: <code class="computeroutput">c0</code> a <code class="computeroutput">c1023</code>. <code class="computeroutp
 ut">s0-s0:c0.c1023</code> es la sensibilidad <code class="computeroutput">s0</code> y autorizado para todas las categorías.
 				</div><div class="para">
-					MLS enforces the <a href="http://en.wikipedia.org/wiki/Bell-LaPadula_model">Bell-LaPadula Mandatory Access Model</a>, and is used in Labeled Security Protection Profile (LSPP) environments. To use MLS restrictions, install the <span class="package">selinux-policy-mls</span> package, and configure MLS to be the default SELinux policy. The MLS policy shipped with Fedora omits many program domains that were not part of the evaluated configuration, and therefore, MLS on a desktop workstation is unusable (no support for the X Window System); however, an MLS policy from the <a href="http://oss.tresys.com/projects/refpolicy">upstream SELinux Reference Policy</a> can be built that includes all program domains.
-				</div></dd></dl></div><div class="section" title="3.1. Domain Transitions" id="sect-Security-Enhanced_Linux-SELinux_Contexts-Domain_Transitions"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">3.1. Domain Transitions</h2></div></div></div><div class="para">
-			A process in one domain transitions to another domain by executing an application that has the <code class="computeroutput">entrypoint</code> type for the new domain. The <code class="computeroutput">entrypoint</code> permission is used in SELinux policy, and controls which applications can be used to enter a domain. The following example demonstrates a domain transition:
+					MLS aplica el <a href="http://en.wikipedia.org/wiki/Bell-LaPadula_model">Modelo de Acceso Obligatorio Bell-LaPadula</a>, y se usa en entornos de Perfil de Protección de Seguirdad Etiquetada (LSPP en inglés). Para usar las restricciones MLS, instale el paquete <span class="package">selinux-policy-mls</span>, y configure a MLS como la política de SELinux predeterminada. La política MLS puesta en Fedora mite muchos dominios de programa que no eran parte de la configuración evaluada, y por lo tanto, MLS es inútil en un escritorio (no hay soporte para el Sistema de Ventanas X); sin embargo, una política MLS se puede incluir desde los <a href="http://oss.tresys.com/projects/refpolicy">desarrolladores de la Política de Referencia de SELinux</a> que incluya todos los dominios de programa.
+				</div></dd></dl></div><div class="section" title="3.1. Transiciones de Dominios" id="sect-Security-Enhanced_Linux-SELinux_Contexts-Domain_Transitions"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">3.1. Transiciones de Dominios</h2></div></div></div><div class="para">
+			Un proceso transiciona de un dominio a otro ejecutando una aplicación que tiene el tipo <code class="computeroutput">entrypoint</code> en el nuevo dominio. Los permisos <code class="computeroutput">entrypoint</code> se usan en las políticas de SELinux, y controlan qué aplicaciones pueden usarse para ingresar a un dominio. El siguiente ejemplo muestra una transición de dominio.
 		</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
-					A users wants to change their password. To change their password, they run the <code class="command">passwd</code> application. The <code class="filename">/usr/bin/passwd</code> executable is labeled with the <code class="computeroutput">passwd_exec_t</code> type:
+					Un usuario desea cambiar su contraseña. Para cambiar sus contraseñas, corren la aplicación <code class="command">passwd</code>. El ejecutable <code class="filename">/usr/bin/passwd</code> está etiquetado con el tipo <code class="computeroutput">passwd_exec_t</code>:
 				</div><pre class="screen">$ ls -Z /usr/bin/passwd
 -rwsr-xr-x  root root system_u:object_r:passwd_exec_t:s0 /usr/bin/passwd
 
 </pre><div class="para">
-					The <span class="application"><strong>passwd</strong></span> application accesses <code class="filename">/etc/shadow</code>, which is labeled with the <code class="computeroutput">shadow_t</code> type:
+					La aplicación <span class="application"><strong>passwd</strong></span> accede <code class="filename">/etc/shadow</code>, que está etiquetado con el tipo <code class="computeroutput">shadow_t</code>:
 				</div><pre class="screen">$ ls -Z /etc/shadow
 -r--------  root root system_u:object_r:shadow_t:s0    /etc/shadow
 
 </pre></li><li class="listitem"><div class="para">
-					An SELinux policy rule states that processes running in the <code class="computeroutput">passwd_t</code> domain are allowed to read and write to files labeled with the <code class="computeroutput">shadow_t</code> type. The <code class="computeroutput">shadow_t</code> type is only applied to files that are required for a password change. This includes <code class="filename">/etc/gshadow</code>, <code class="filename">/etc/shadow</code>, and their backup files.
+					Una regla de política de SELinux dice que los procesos que se ejecutan en el dominio <code class="computeroutput">passwd_t</code> no pueden leer y escribir archivos etiquetados con el tipo <code class="computeroutput">shadow_t</code>. El tipo <code class="computeroutput">shadow_t</code> sólo se aplica a archivos que necesitan un cambio de contraseñas. Esto incluye a <code class="filename">/etc/gshadow</code>, <code class="filename">/etc/shadow</code>, y sus archivos de respaldo.
 				</div></li><li class="listitem"><div class="para">
-					An SELinux policy rule states that the <code class="computeroutput">passwd_t</code> domain has <code class="computeroutput">entrypoint</code> permission to the <code class="computeroutput">passwd_exec_t</code> type.
+					Una regla de política de SELinux fija que el dominio <code class="computeroutput">passwd_t</code> tiene permiso de <code class="computeroutput">entrypoint</code> al tipo <code class="computeroutput">passwd_exec_t</code>.
 				</div></li><li class="listitem"><div class="para">
-					When a user runs the <code class="command">/usr/bin/passwd</code> application, the user's shell process transitions to the <code class="computeroutput">passwd_t</code> domain. With SELinux, since the default action is to deny, and a rule exists that allows (among other things) applications running in the <code class="computeroutput">passwd_t</code> domain to access files labeled with the <code class="computeroutput">shadow_t</code> type, the <span class="application"><strong>passwd</strong></span> application is allowed to access <code class="filename">/etc/shadow</code>, and update the user's password.
+					Cuando un usuario ejecuta la aplicación <code class="command">/usr/bin/passwd</code>, el proceso shell del usuario transiciona al dominio <code class="computeroutput">passwd_t</code>. Con SELinux, dado que la acción por defecto es negar, y existe una regla que permite (entre otras cosas) a aplicaciones que corran en el dominio <code class="computeroutput">passwd_t</code> acceder a archivos etiquetados con el tipo <code class="computeroutput">shadow_t</code>, se le permite a <span class="application"><strong>passwd</strong></span> acceder a <code class="filename">/etc/shadow</code>, y actualizar la contraseña del usuario.
 				</div></li></ol></div><div class="para">
-			This example is not exhaustive, and is used as a basic example to explain domain transition. Although there is an actual rule that allows subjects running in the <code class="computeroutput">passwd_t</code> domain to access objects labeled with the <code class="computeroutput">shadow_t</code> file type, other SELinux policy rules must be met before the subject can transition to a new domain. In this example, Type Enforcement ensures:
+			Este ejemplo no es exhaustivo, y se usa como un ejemplo básico para explicar la transición de dominio. Aunque hay una regla actual que permite a sujetos corriendo en el dominio <code class="computeroutput">passwd_t</code> accedan objetos etiquetados con el tipo de archivo <code class="computeroutput">shadow_t</code>, otras reglas de política de SELinux se deben cumplir para que el sujeto pueda transicionar a un nuevo dominio. En este ejemplo, la Obligación de Tipo asegura:
 		</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-					the <code class="computeroutput">passwd_t</code> domain can only be entered by executing an application labeled with the <code class="computeroutput">passwd_exec_t</code> type; can only execute from authorized shared libraries, such as the <code class="computeroutput">lib_t</code> type; and can not execute any other applications.
+					el dominio <code class="computeroutput">passwd_t</code> sólo se puede ingresar ejecutando una aplicación con la etiqueta del tipo <code class="computeroutput">passwd_exec_t</code>; sólo pueden ejecutar desde bibliotecas compartidas autorizadas, tales como las del tipo <code class="computeroutput">lib_t</code>; y no pueden ejecutar ninguna otra aplicación.
 				</div></li><li class="listitem"><div class="para">
-					only authorized domains, such as <code class="computeroutput">passwd_t</code>, can write to files labeled with the <code class="computeroutput">shadow_t</code> type. Even if other processes are running with superuser privileges, those processes can not write to files labeled with the <code class="computeroutput">shadow_t</code> type, as they are not running in the <code class="computeroutput">passwd_t</code> domain.
+					sólo los dominios autorizados, tales como <code class="computeroutput">passwd_t</code>, pueden escribir en archivos con la etiqueta del tipo <code class="computeroutput">shadow_t</code>. Aún si otros procesos corren con privilegios de superusuario, esos procesos no podrán escribir archivos etiquetados con el tipo <code class="computeroutput">shadow_t</code>, porque no están corriendo en el dominio <code class="computeroutput">passwd_t</code>.
 				</div></li><li class="listitem"><div class="para">
-					only authorized domains can transition to the <code class="computeroutput">passwd_t</code> domain. For example, the <code class="systemitem">sendmail</code> process running in the <code class="computeroutput">sendmail_t</code> domain does not have a legitimate reason to execute <code class="command">passwd</code>; therefore, it can never transition to the <code class="computeroutput">passwd_t</code> domain.
+					sólo los dominios autorizados pueden transicionar al dominio <code class="computeroutput">passwd_t</code>. Por ejemplo, el proceso <code class="systemitem">sendmail</code> corriendo en el dominio <code class="computeroutput">sendmail_t</code> no tiene una razón legítima para ejecutar <code class="command">passwd</code>; por lo tanto, no puede transicionar nunca al dominio <code class="computeroutput">passwd_t</code>.
 				</div></li><li class="listitem"><div class="para">
-					processes running in the <code class="computeroutput">passwd_t</code> domain can only read and write to authorized types, such as files labeled with the <code class="computeroutput">etc_t</code> or <code class="computeroutput">shadow_t</code> types. This prevents the <span class="application"><strong>passwd</strong></span> application from being tricked into reading or writing arbitrary files.
-				</div></li></ul></div></div><div class="section" title="3.2. SELinux Contexts for Processes" id="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Processes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">3.2. SELinux Contexts for Processes</h2></div></div></div><div class="para">
-			Use the <code class="command">ps -eZ</code> command to view the SELinux context for processes. For example:
+					los procesos que se ejecutan en el dominio <code class="computeroutput">passwd_t</code> sólo pueden leer y escribir a tipos autorizados, tales como archivos etiquetados con los tipos <code class="computeroutput">etc_t</code> o <code class="computeroutput">shadow_t</code>. Esto impide a la aplicación <span class="application"><strong>passwd</strong></span> de ser modificada para leer o escribir en archivos arbitrarios.
+				</div></li></ul></div></div><div class="section" title="3.2. Contextos de SELinux para los Procesos" id="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Processes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">3.2. Contextos de SELinux para los Procesos</h2></div></div></div><div class="para">
+			Use el comando <code class="command">ps -eZ</code> para ver los contextos de SELinux para los procesos. Por ejemplo:
 		</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
-					Open a terminal, such as <span class="guimenu"><strong>Applications</strong></span> → <span class="guisubmenu"><strong>System Tools</strong></span> → <span class="guimenuitem"><strong>Terminal</strong></span>.
+					Abra una terminal, como la de <span class="guimenu"><strong>Aplicaciones</strong></span> → <span class="guisubmenu"><strong>Herramientas del Sistema</strong></span> → <span class="guimenuitem"><strong>Terminal</strong></span>.
 				</div></li><li class="listitem"><div class="para">
-					Run the <code class="command">/usr/bin/passwd</code> command. Do not enter a new password.
+					Ejecute el comando <code class="command">/usr/bin/passwd</code>. No ingrese una nueva contraseña.
 				</div></li><li class="listitem"><div class="para">
-					Open a new tab, or another terminal, and run the <code class="command">ps -eZ | grep passwd</code> command. The output is similar to the following:
+					Abra una nueva pestaña, u otra terminal, y ejecute el comando <code class="command">ps -eZ | grep passwd</code>. La salida es similar a la siguiente:
 				</div><pre class="screen">unconfined_u:unconfined_r:passwd_t:s0-s0:c0.c1023 13212 pts/1 00:00:00 passwd
 
 </pre></li><li class="listitem"><div class="para">
-					In the first tab, press <strong class="userinput"><code>Ctrl+C</code></strong> to cancel the <span class="application"><strong>passwd</strong></span> application.
+					En la primer pestaña, presione <strong class="userinput"><code>Ctrl+C</code></strong> para cancelar la aplicación <span class="application"><strong>passwd</strong></span>.
 				</div></li></ol></div><div class="para">
-			In this example, when the <code class="filename">/usr/bin/passwd</code> application (labeled with the <code class="computeroutput">passwd_exec_t</code> type) is executed, the user's shell process transitions to the <code class="computeroutput">passwd_t</code> domain. Remember: the type defines a domain for processes, and a type for files.
+			En este ejemplo, cuando la aplicación <code class="filename">/usr/bin/passwd</code> (etiquetada con el tipo <code class="computeroutput">passwd_exec_t</code>) se ejecuta, el proceso shell del usuario transiciona al dominio <code class="computeroutput">passwd_t</code>. Recuerde: el tipo define un dominio para procesos y un tipo para archivos.
 		</div><div class="para">
-			Use the <code class="command">ps -eZ</code> command to view the SELinux contexts for running processes. The following is a limited example of the output, and may differ on your system:
+			Use el comando <code class="command">ps -eZ</code> para ver los contextos SELinux de los procesos en ejecución. El siguiente es un ejemplo limitado de la salida, y puede cambiar en su sistema:
 		</div><pre class="screen">system_u:system_r:setroubleshootd_t:s0 1866 ?  00:00:08 setroubleshootd
 system_u:system_r:dhcpc_t:s0     1869 ?        00:00:00 dhclient
 system_u:system_r:sshd_t:s0-s0:c0.c1023 1882 ? 00:00:00 sshd
@@ -313,23 +313,23 @@ system_u:system_r:kerneloops_t:s0 1983 ?       00:00:05 kerneloops
 system_u:system_r:crond_t:s0-s0:c0.c1023 1991 ? 00:00:00 atd
 
 </pre><div class="para">
-			The <code class="computeroutput">system_r</code> role is used for system processes, such as daemons. Type Enforcement then separates each domain.
-		</div></div><div class="section" title="3.3. SELinux Contexts for Users" id="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Users"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">3.3. SELinux Contexts for Users</h2></div></div></div><div class="para">
-			Use the <code class="command">id -Z</code> command to view the SELinux context associated with your Linux user:
+			El rol <code class="computeroutput">system_r</code> se usa para procesos de sistema, como los demonios. El tipo obligatorio los separa luego en dominios.
+		</div></div><div class="section" title="3.3. Contextos de SELinux para los Usuarios" id="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Users"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">3.3. Contextos de SELinux para los Usuarios</h2></div></div></div><div class="para">
+			Use el comando <code class="command">id -Z</code> para ver el contexto SELinux asociado con su usuario Linux:
 		</div><pre class="screen">unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
 
 </pre><div class="para">
-			In Fedora 11, Linux users run unconfined by default. This SELinux context shows that the Linux user is mapped to the SELinux <code class="computeroutput">unconfined_u</code> user, running as the <code class="computeroutput">unconfined_r</code> role, and is running in the <code class="computeroutput">unconfined_t</code> domain. <code class="computeroutput">s0-s0</code> is an MLS range, which in this case, is the same as just <code class="computeroutput">s0</code>. The categories the user has access to is defined by <code class="computeroutput">c0.c1023</code>, which is all categories (<code class="computeroutput">c0</code> through to <code class="computeroutput">c1023</code>).
-		</div></div></div><div xml:lang="es-ES" class="chapter" title="Capítulo 4. Targeted Policy" id="chap-Security-Enhanced_Linux-Targeted_Policy" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 4. Targeted Policy</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Targeted_Policy-Confined_Processes">4.1. Confined Processes</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Targeted_Policy-Unconfined_Processes">4.2. Unconfined Processes</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users">4.3. Confined and Unconfined Users</a></span></dt></dl></div><div class="para">
-		Targeted policy is the default SELinux policy used in Fedora 11. When using targeted policy, processes that are targeted run in a confined domain, and processes that are not targeted run in an unconfined domain. For example, by default, logged in users run in the <code class="computeroutput">unconfined_t</code> domain, and system processes started by init run in the <code class="computeroutput">initrc_t</code> domain - both of these domains are unconfined.
+			En Fedora 11, los usuarios Linux corren no confinados por defecto. Este contexto de SELinux muestra que el usuario Linux se mapea al usuario SELinux <code class="computeroutput">unconfined_u</code>, corriendo con el rol <code class="computeroutput">unconfined_r</code> y en el dominio <code class="computeroutput">unconfined_t</code>. <code class="computeroutput">s0-s0</code> es un rango MLS, que en este caso, es el mismo que <code class="computeroutput">s0</code>. Las categorías a las que el usuario tiene acceso se definen por <code class="computeroutput">c0.c1023</code>, que son todas las categorías (<code class="computeroutput">c0</code> a <code class="computeroutput">c1023</code>).
+		</div></div></div><div xml:lang="es-ES" class="chapter" title="Capítulo 4. Política Destinado" id="chap-Security-Enhanced_Linux-Targeted_Policy" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 4. Política Destinado</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Targeted_Policy-Confined_Processes">4.1. Procesos Confinados</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Targeted_Policy-Unconfined_Processes">4.2. Procesos no Confinados</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users">4.3. Usuarios Confinados y no Confinados</a></span></dt></dl></div><div class="para">
+		La política destinada es la política predeterminada de SELinux usada en Fedora 11. Cuando la política destinada está en uso, los procesos son destinados a correr en dominios confinados, y los procesos que no son destinados a correr en un dominio corren en un dominio no confinado. Por ejemplo, por defecto, los usuarios que ingresaron corren en el dominio <code class="computeroutput">unconfined_t</code>, y los procesos del sistema iniciado por init corren en el dominio <code class="computeroutput">initrc_t</code> - ambos dominios están no confinados.
 	</div><div class="para">
 		Unconfined domains (as well as confined domains) are subject to executable and writeable memory checks. By default, subjects running in an unconfined domain can not allocate writeable memory and execute it. This reduces vulnerability to <a href="http://en.wikipedia.org/wiki/Buffer_overflow">buffer overflow attacks</a>. These memory checks are disabled by setting Booleans, which allow the SELinux policy to be modified at runtime. Boolean configuration is discussed later.
-	</div><div class="section" title="4.1. Confined Processes" id="sect-Security-Enhanced_Linux-Targeted_Policy-Confined_Processes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.1. Confined Processes</h2></div></div></div><div class="para">
-			Almost every service that listens on a network is confined in Fedora 11. Also, most processes that run as the Linux root user and perform tasks for users, such as the <span class="application"><strong>passwd</strong></span> application, are confined. When a process is confined, it runs in its own domain, such as the <code class="systemitem">httpd</code> process running in the <code class="computeroutput">httpd_t</code> domain. If a confined process is compromised by an attacker, depending on SELinux policy configuration, an attacker's access to resources and the possible damage they can do is limited.
+	</div><div class="section" title="4.1. Procesos Confinados" id="sect-Security-Enhanced_Linux-Targeted_Policy-Confined_Processes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.1. Procesos Confinados</h2></div></div></div><div class="para">
+			Casi todos los servicios que escuchan en la red se confinan en Fedora 11. También, la mayoría de los procesos que corren como usuario root de Linux y realizan tareas para los usuarios, tales como la aplicación <span class="application"><strong>passwd</strong></span>, están confinadas. Cuando un proceso se confina, corre en su propio dominio, tal como el proceso <code class="systemitem">httpd</code> ejecutándose en el domino <code class="computeroutput">httpd_t</code>. Si un proceso confinado es comprometido por un atacante, dependiendo de la configuración de política de SELinux, el acceso del atacante a recursos y el posible daño que puedan causar es limitado.
 		</div><div class="para">
-			The following example demonstrates how SELinux prevents the Apache HTTP Server (<code class="systemitem">httpd</code>) from reading files that are not correctly labeled, such as files intended for use by Samba. This is an example, and should not be used in production. It assumes that the <span class="package">httpd</span>, <span class="package">wget</span>, <span class="package">setroubleshoot-server</span>, and <span class="package">audit</span> packages are installed, that the SELinux targeted policy is used, and that SELinux is running in enforcing mode:
+			El siguiente ejemplo muestra cómo previene SELinux la lectura por parte del Servidor HTTP Apache (<code class="systemitem">httpd</code>) de archivos que no se etiquetaron correctamente, tales como archivos a usar con Samba. Este es un ejemplo, y no se debe usar en producción. Asume que los paquetes <span class="package">httpd</span>, <span class="package">wget</span>, <span class="package">setroubleshoot-server</span> y <span class="package">audit</span> están instalados, que se usa la política destinada de SELinux y que SELinux está corriendo en modo obligatorio:
 		</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
-					Run the <code class="command">sestatus</code> command to confirm that SELinux is enabled, is running in enforcing mode, and that targeted policy is being used:
+					Ejecute el comando <code class="command">sestatus</code> para confirmar que SELinux está activado, se ejecuta en modo obligatorio y que la política destinada se está usando:
 				</div><pre class="screen">
 $ /usr/sbin/sestatus
 SELinux status:                 enabled
@@ -342,20 +342,20 @@ Policy from config file:        targeted
 </pre><div class="para">
 					<code class="computeroutput">SELinux status: enabled</code> is returned when SELinux is enabled. <code class="computeroutput">Current mode: enforcing</code> is returned when SELinux is running in enforcing mode. <code class="computeroutput">Policy from config file: targeted</code> is returned when the SELinux targeted policy is used.
 				</div></li><li class="listitem"><div class="para">
-					As the Linux root user, run the <code class="command">touch /var/www/html/testfile</code> command to create a file.
+					Como usuario root de Linux, ejecute el comando <code class="command">touch /var/www/html/prueba</code> para crear un archivo.
 				</div></li><li class="listitem"><div class="para">
-					Run the <code class="command">ls -Z /var/www/html/testfile</code> command to view the SELinux context:
+					Ejecute el comando <code class="command">ls -Z /var/www/html/prueba</code> para ver el contexto SELinux:
 				</div><pre class="screen">-rw-r--r--  root root unconfined_u:object_r:httpd_sys_content_t:s0 /var/www/html/testfile
 
 </pre><div class="para">
-					By default, Linux users run unconfined in Fedora 11, which is why the <code class="filename">testfile</code> file is labeled with the SELinux <code class="computeroutput">unconfined_u</code> user. RBAC is used for processes, not files. Roles do not have a meaning for files - the <code class="computeroutput">object_r</code> role is a generic role used for files (on persistent storage and network file systems). Under the <code class="filename">/proc/</code> directory, files related to processes may use the <code class="computeroutput">system_r</code> role.<sup>[<a id="id535564" href="#ftn.id535564" class="footnote">6</a>]</sup> The <code class="computeroutput">httpd_sys_content_t</code> type allows the <code class="systemitem">httpd</code> process to access this file.
+					Por defecto, los usuarios Linux corren no confinados en Fedora 11, razón por la cual el archivo <code class="filename">prueba</code> se etiqueta con el usuario SELinux <code class="computeroutput">unconfined_u</code>. RBAC se usa para procesos, y no para archivos. Los roles no tienen significado para archivos - el rol <code class="computeroutput">object_r</code> es un rol genérico usado para archivos (en sistemas de archivos persistentes y de red). Bajo el directorio <code class="filename">/proc/</code>, los archivos relacionados con procesos pueden usar el rol <code class="computeroutput">system_r</code>.<sup>[<a id="id753277" href="#ftn.id753277" class="footnote">6</a>]</sup> El tipo <code class="computeroutput">httpd_sys_content_t</code> permite al proceso <code class="systemitem">httpd</code> acceder a este archivo.
 				</div></li><li class="listitem"><div class="para">
-					As the Linux root user, run the <code class="command">service httpd start</code> command to start the <code class="systemitem">httpd</code> process. The output is as follows if <code class="systemitem">httpd</code> starts successfully:
+					Como usuario root de Linux, ejecute el comando <code class="command">service httpd start</code> para iniciar el proceso <code class="systemitem">httpd</code>. La salida escomo sigue si <code class="systemitem">httpd</code> inicia con éxito:
 				</div><pre class="screen"># /sbin/service httpd start
 Starting httpd:                                            [  OK  ]
 
 </pre></li><li class="listitem"><div class="para">
-					Change into a directory where your Linux user has write access to, and run the <code class="command">wget http://localhost/testfile</code> command. Unless there are changes to the default configuration, this command succeeds:
+					Cambie al directorio donde su usuario Linux tenga acceso de escritura y ejecute el comando <code class="command">wget http://localhost/prueba</code>. A menos que hubieran cambios en la configuración predeterminada, este comando tiene éxito:
 				</div><pre class="screen">--2009-05-06 23:00:01--  http://localhost/testfile
 Resolving localhost... 127.0.0.1
 Connecting to localhost|127.0.0.1|:80... connected.
@@ -368,15 +368,15 @@ Saving to: `testfile'
 2009-05-06 23:00:01 (0.00 B/s) - `testfile' saved [0/0]
 
 </pre></li><li class="listitem"><div class="para">
-					The <code class="command">chcon</code> command relabels files; however, such label changes do not survive when the file system is relabeled. For permanent changes that survive a file system relabel, use the <code class="command">semanage</code> command, which is discussed later. As the Linux root user, run the following command to change the type to a type used by Samba:
+					El comando <code class="command">chcon</code> reetiqueta archivos; sin embargo, tales cambios de etiquetas no sobreviven cuando el sistema se reetiqueta. Para que los cambios sobrevivan un reetiquetado del sistema, use el comando <code class="command">semanage</code>, que se discute más adelante. Como usuario root de Linux, corra el siguiente comando para cambiar el tipo a un tipo usado por Samba:
 				</div><div class="para">
 					<code class="command">chcon -t samba_share_t /var/www/html/testfile</code>
 				</div><div class="para">
-					Run the <code class="command">ls -Z /var/www/html/testfile</code> command to view the changes:
+					Ejecute el comando <code class="command">ls -Z /var/www/html/prueba</code> para ver los cambios:
 				</div><pre class="screen">-rw-r--r--  root root unconfined_u:object_r:samba_share_t:s0 /var/www/html/testfile
 
 </pre></li><li class="listitem"><div class="para">
-					Note: the current DAC permissions allow the <code class="systemitem">httpd</code> process access to <code class="filename">testfile</code>. Change into a directory where your Linux user has write access to, and run the <code class="command">wget http://localhost/testfile</code> command. Unless there are changes to the default configuration, this command fails:
+					Nota: los permisos de DAC actuales permiten al proceso <code class="systemitem">httpd</code> acceder al <code class="filename">prueba</code>. Cambie al directorio donde el usuario Linux tenga permiso de escritura y ejecute el comando <code class="command">wget http://localhost/prueba</code>. A menos que hayan cambios en la configuración predeterminada, este comando fallará:
 				</div><pre class="screen">--2009-05-06 23:00:54--  http://localhost/testfile
 Resolving localhost... 127.0.0.1
 Connecting to localhost|127.0.0.1|:80... connected.
@@ -384,36 +384,36 @@ HTTP request sent, awaiting response... 403 Forbidden
 2009-05-06 23:00:54 ERROR 403: Forbidden.
 
 </pre></li><li class="listitem"><div class="para">
-					As the Linux root user, run the <code class="command">rm -i /var/www/html/testfile</code> command to remove <code class="filename">testfile</code>.
+					Como usuario root de Linux, corra el comando <code class="command">rm -i /var/www/html/prueba</code> para borrar <code class="filename">prueba</code>.
 				</div></li><li class="listitem"><div class="para">
-					If you do not require <code class="systemitem">httpd</code> to be running, as the Linux root user, run the <code class="command">service httpd stop</code> command to stop <code class="systemitem">httpd</code>:
+					Si no necesita que corra <code class="systemitem">httpd</code>, como usuario root de Linux corra el comando <code class="command">service httpd stop</code> para detener a <code class="systemitem">httpd</code>:
 				</div><pre class="screen"># /sbin/service httpd stop
 Stopping httpd:                                            [  OK  ]
 
 </pre></li></ol></div><div class="para">
-			This example demonstrates the additional security added by SELinux. Although DAC rules allowed the <code class="systemitem">httpd</code> process access to <code class="filename">testfile</code> in step 7, because the file was labeled with a type that the <code class="systemitem">httpd</code> process does not have access to, SELinux denied access. After step 7, an error similar to the following is logged to <code class="filename">/var/log/messages</code>:
+			Este ejemplo muestra la seguridad adicional agregada por SELinux. Aunque las reglas de DAC permitieron al proceso <code class="systemitem">httpd</code> acceder a <code class="filename">prueba</code> en el paso 7, dado que estaba etiquetado con un tipo al que el proceso <code class="systemitem">httpd</code> no tenía acceso, SELinux negó el acceso. Después del paso 7, un error similar al siguiente se guarda en <code class="filename">/var/log/messages</code>:
 		</div><pre class="screen">May 6 23:00:54 localhost setroubleshoot: SELinux is preventing httpd (httpd_t) "getattr"
 to /var/www/html/testfile (samba_share_t). For complete SELinux messages.
 run sealert -l c05911d3-e680-4e42-8e36-fe2ab9f8e654
 
 </pre><div class="para">
-			Previous log files may use a <code class="filename">/var/log/messages.<em class="replaceable"><code>YYYYMMDD</code></em></code> format. When running <span class="application"><strong>syslog-ng</strong></span>, previous log files may use a <code class="filename">/var/log/messages.<em class="replaceable"><code>X</code></em></code> format. If the <code class="systemitem">setroubleshootd</code> and <code class="systemitem">auditd</code> processes are running, errors similar to the following are logged to <code class="filename">/var/log/audit/audit.log</code>:
+			Archivos log previos pueden usar el formato <code class="filename">/var/log/messages.<em class="replaceable"><code>YYYYMMDD</code></em></code>. Cuando se ejecuta <span class="application"><strong>syslog-ng</strong></span>, los archivos log previos pueden usar el formato <code class="filename">/var/log/messages.<em class="replaceable"><code>X</code></em></code>. Si los procesos <code class="systemitem">setroubleshootd</code> y <code class="systemitem">auditd</code> están ejecutándose, errores similares a los siguientes se registran en <code class="filename">/var/log/audit/audit.log</code>:
 		</div><pre class="screen">type=AVC msg=audit(1220706212.937:70): avc:  denied  { getattr } for  pid=1904 comm="httpd" path="/var/www/html/testfile" dev=sda5 ino=247576 scontext=unconfined_u:system_r:httpd_t:s0 tcontext=unconfined_u:object_r:samba_share_t:s0  tclass=file
 
 type=SYSCALL msg=audit(1220706212.937:70): arch=40000003 syscall=196 success=no exit=-13 a0=b9e21da0 a1=bf9581dc a2=555ff4 a3=2008171 items=0 ppid=1902 pid=1904 auid=500 uid=48 gid=48 euid=48 suid=48 fsuid=48 egid=48 sgid=48 fsgid=48 tty=(none) ses=1 comm="httpd" exe="/usr/sbin/httpd" subj=unconfined_u:system_r:httpd_t:s0 key=(null)
 
 </pre><div class="para">
-			Also, an error similar to the following is logged to <code class="filename">/var/log/httpd/error_log</code>:
+			También, un error similar al siguiente se registra en <code class="filename">/var/log/httpd/error_log</code>:
 		</div><pre class="screen">[Wed May 06 23:00:54 2009] [error] [client <em class="replaceable"><code>127.0.0.1</code></em>] (13)Permission denied: access to /testfile denied
 
 </pre><div class="note"><h2>Nota</h2><div class="para">
-				In Fedora 11, the <span class="package">setroubleshoot-server</span> and <span class="package">audit</span> packages are installed by default. These packages include the <code class="systemitem">setroubleshootd</code> and <code class="systemitem">auditd</code> daemons respectively. These daemons run by default. Stopping either of these daemons changes where SELinux denials are written to. Refer to <a class="xref" href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used" title="5.2. Which Log File is Used">Sección 5.2, “Which Log File is Used”</a> for further information.
-			</div></div></div><div class="section" title="4.2. Unconfined Processes" id="sect-Security-Enhanced_Linux-Targeted_Policy-Unconfined_Processes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.2. Unconfined Processes</h2></div></div></div><div class="para">
-			Unconfined processes run in unconfined domains, for example, init programs run in the unconfined <code class="computeroutput">initrc_t</code> domain, unconfined kernel processes run in the <code class="computeroutput">kernel_t</code> domain, and unconfined Linux users run in the <code class="computeroutput">unconfined_t</code> domain. For unconfined processes, SELinux policy rules are applied, but policy rules exist that allow processes running in unconfined domains almost all access. Processes running in unconfined domains fall back to using DAC rules exclusively. If an unconfined process is compromised, SELinux does not prevent an attacker from gaining access to system resources and data, but of course, DAC rules are still used. SELinux is a security enhancement on top of DAC rules - it does not replace them.
+				In Fedora 11, the <span class="package">setroubleshoot-server</span> and <span class="package">audit</span> packages are installed by default. These packages include the <code class="systemitem">setroubleshootd</code> and <code class="systemitem">auditd</code> daemons respectively. These daemons run by default. Stopping either of these daemons changes where SELinux denials are written to. Refer to <a class="xref" href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used" title="5.2. Qué Archivo Log se usa">Sección 5.2, “Qué Archivo Log se usa”</a> for further information.
+			</div></div></div><div class="section" title="4.2. Procesos no Confinados" id="sect-Security-Enhanced_Linux-Targeted_Policy-Unconfined_Processes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.2. Procesos no Confinados</h2></div></div></div><div class="para">
+			Los procesos no confinados corren en dominios no confinados, por ejemplo, los programas init (del arranque) corren en el dominio no confinado <code class="computeroutput">initrc_t</code>, los procesos no confinados del kernel corren en el dominio <code class="computeroutput">kernel_t</code> y los usuarios no confinados deLInux corren en el dominio <code class="computeroutput">unconfined_t</code>. Para procesos no confinados, las reglas de la política de SELinux son aplicadas, pero hay reglas de la política que permiten que los procesos se ejecuten en dominios no confinados tengan casi todos los accesos. Los procesos que corren en dominios no confinados terminan usando exclusivamente las reglas DAC. Si un proceso no confinado es comprometido, SELinux no impide que un atacante gane acceso a los recursos del sistema y a los datos, pero, por supuesto, las reglas DAC todavía se usan. SELinux es una mejora de seguridad sobre las reglas DAC - no las reemplaza.
 		</div><div class="para">
-			The following example demonstrates how the Apache HTTP Server (<code class="systemitem">httpd</code>) can access data intended for use by Samba, when running unconfined. Note: in Fedora 11, the <code class="systemitem">httpd</code> process runs in the confined <code class="computeroutput">httpd_t</code> domain by default. This is an example, and should not be used in production. It assumes that the <span class="package">httpd</span>, <span class="package">wget</span>, <span class="package">setroubleshoot-server</span>, and <span class="package">audit</span> packages are installed, that the SELinux targeted policy is used, and that SELinux is running in enforcing mode:
+			El siguiente ejemplo muestra cómo el Servidor HTTP Apache (<code class="systemitem">httpd</code>) puede acceder datos que se suponen son para ser usados por Samba, cuando se corre no confinado. Nota: en Fedora 11, el proceso <code class="systemitem">httpd</code> corre en el dominio confinado <code class="computeroutput">httpd_t</code> por defecto. Este es un ejemplo, y no debe usarse en producción. Se asume que los paquetes <span class="package">httpd</span>, <span class="package">wget</span>, <span class="package">setroubleshoot-server</span>, y <span class="package">audit</span> están instalados, que se usa la política destinada de SELinux y que SELinux corre en modo obligatorio:
 		</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
-					Run the <code class="command">sestatus</code> command to confirm that SELinux is enabled, is running in enforcing mode, and that targeted policy is being used:
+					Ejecute el comando <code class="command">sestatus</code> para confirmar que SELinux está activado, se ejecuta en modo obligatorio y que la política destinada se está usando:
 				</div><pre class="screen">
 $ /usr/sbin/sestatus
 SELinux status:                 enabled
@@ -426,46 +426,46 @@ Policy from config file:        targeted
 </pre><div class="para">
 					<code class="computeroutput">SELinux status: enabled</code> is returned when SELinux is enabled. <code class="computeroutput">Current mode: enforcing</code> is returned when SELinux is running in enforcing mode. <code class="computeroutput">Policy from config file: targeted</code> is returned when the SELinux targeted policy is used.
 				</div></li><li class="listitem"><div class="para">
-					As the Linux root user, run the <code class="command">touch /var/www/html/test2file</code> command to create a file.
+					Como usuario root de Linux, corra el comando <code class="command">touch /var/www/html/prueba2</code> para crear un archivo.
 				</div></li><li class="listitem"><div class="para">
-					Run the <code class="command">ls -Z /var/www/html/test2file</code> command to view the SELinux context:
+					Ejecute el comando <code class="command">ls -Z /var/www/html/prueba2</code> para ver el contexto SELinux:
 				</div><pre class="screen">-rw-r--r--  root root unconfined_u:object_r:httpd_sys_content_t:s0 /var/www/html/test2file
 
 </pre><div class="para">
-					By default, Linux users run unconfined in Fedora 11, which is why the <code class="filename">test2file</code> file is labeled with the SELinux <code class="computeroutput">unconfined_u</code> user. RBAC is used for processes, not files. Roles do not have a meaning for files - the <code class="computeroutput">object_r</code> role is a generic role used for files (on persistent storage and network file systems). Under the <code class="filename">/proc/</code> directory, files related to processes may use the <code class="computeroutput">system_r</code> role.<sup>[<a id="id1840232" href="#ftn.id1840232" class="footnote">7</a>]</sup> The <code class="computeroutput">httpd_sys_content_t</code> type allows the <code class="systemitem">httpd</code> process to access this file.
+					Por defecto, los usuarios Linux corren no confinados en Fedora 11, razón por la cual el archivo <code class="filename">prueba2</code> está etiquetado con el usuario SELinux <code class="computeroutput">unconfined_u</code>. RBAC se usa para procesos, no para archivos. Los roles no tienen un significado para archivos - el rol <code class="computeroutput">object_r</code> es el rol genérico que se usa para archivos (en almacenamiento persistente y sistemas de archivos de red). Bajo el directorio <code class="filename">/proc/</code>, los archivos relacionados con procesos pueden usar el rol <code class="computeroutput">system_r</code>.<sup>[<a id="id765190" href="#ftn.id765190" class="footnote">7</a>]</sup> El tipo <code class="computeroutput">httpd_sys_content_t</code> permite al proceso <code class="systemitem">httpd</code> acceder a este archivo.
 				</div></li><li class="listitem"><div class="para">
-					The <code class="command">chcon</code> command relabels files; however, such label changes do not survive when the file system is relabeled. For permanent changes that survive a file system relabel, use the <code class="command">semanage</code> command, which is discussed later. As the Linux root user, run the following command to change the type to a type used by Samba:
+					El comando <code class="command">chcon</code> reetiqueta archivos; sin embargo, tales cambios de etiquetas no sobreviven cuando el sistema se reetiqueta. Para que los cambios sobrevivan un reetiquetado del sistema, use el comando <code class="command">semanage</code>, que se discute más adelante. Como usuario root de Linux, corra el siguiente comando para cambiar el tipo a un tipo usado por Samba:
 				</div><div class="para">
 					<code class="command">chcon -t samba_share_t /var/www/html/test2file</code>
 				</div><div class="para">
-					Run the <code class="command">ls -Z /var/www/html/test2file</code> command to view the changes:
+					Ejecute el comando <code class="command">ls -Z /var/www/html/prueba2</code> para ver los cambios:
 				</div><pre class="screen">-rw-r--r--  root root unconfined_u:object_r:samba_share_t:s0 /var/www/html/test2file
 
 </pre></li><li class="listitem"><div class="para">
-					Run the <code class="command">service httpd status</code> command to confirm that the <code class="systemitem">httpd</code> process is not running:
+					Corra el comando <code class="command">service httpd status</code> para confirmar que el proceso <code class="systemitem">httpd</code> no se está ejecutando:
 				</div><pre class="screen">$ /sbin/service httpd status
 httpd is stopped
 
 </pre><div class="para">
-					If the output differs, run the <code class="command">service httpd stop</code> command as the Linux root user to stop the <code class="systemitem">httpd</code> process:
+					Si la salida difiere, ejecute <code class="command">service httpd stop</code> como usuario root de Linux para detener el proceso <code class="systemitem">httpd</code>:
 				</div><pre class="screen"># /sbin/service httpd stop
 Stopping httpd:                                            [  OK  ]
 
 </pre></li><li class="listitem"><div class="para">
-					To make the <code class="systemitem">httpd</code> process run unconfined, run the following command as the Linux root user to change the type of <code class="filename">/usr/sbin/httpd</code>, to a type that does not transition to a confined domain:
+					Para hacer que el proceso <code class="systemitem">httpd</code> corra no confinado, ejecute el siguiente comando como usuario root de Linux para cambiar el tipo de <code class="filename">/usr/sbin/httpd</code>, a un tipo que no transicione a un dominio confinado:
 				</div><div class="para">
 					<code class="command">chcon -t unconfined_exec_t /usr/sbin/httpd</code>
 				</div></li><li class="listitem"><div class="para">
-					Run the <code class="command">ls -Z /usr/sbin/httpd</code> command to confirm that <code class="filename">/usr/sbin/httpd</code> is labeled with the <code class="computeroutput">unconfined_exec_t</code> type:
+					Ejecute el comando <code class="command">ls -Z /usr/sbin/httpd</code> para confirmar que <code class="filename">/usr/sbin/httpd</code> está etiquetado con el tipo <code class="computeroutput">unconfined_exec_t</code>:
 				</div><pre class="screen">-rwxr-xr-x  root root system_u:object_r:unconfined_exec_t /usr/sbin/httpd
 
 </pre></li><li class="listitem"><div class="para">
-					As the Linux root user, run the <code class="command">service httpd start</code> command to start the <code class="systemitem">httpd</code> process. The output is as follows if <code class="systemitem">httpd</code> starts successfully:
+					Como usuario root de Linux, ejecute el comando <code class="command">service httpd start</code> para iniciar el proceso <code class="systemitem">httpd</code>. La salida escomo sigue si <code class="systemitem">httpd</code> inicia con éxito:
 				</div><pre class="screen"># /sbin/service httpd start
 Starting httpd:                                            [  OK  ]
 
 </pre></li><li class="listitem"><div class="para">
-					Run the <code class="command">ps -eZ | grep httpd</code> command to view the <code class="systemitem">httpd</code> running in the <code class="computeroutput">unconfined_t</code> domain:
+					Ejecute el comando <code class="command">ps -eZ | grep httpd</code> para ver si <code class="systemitem">httpd</code> está corriendo en el dominio <code class="computeroutput">unconfined_t</code>:
 				</div><pre class="screen">$ ps -eZ | grep httpd
 unconfined_u:system_r:unconfined_t <em class="replaceable"><code>7721</code></em> ?      00:00:00 httpd
 unconfined_u:system_r:unconfined_t <em class="replaceable"><code>7723</code></em> ?      00:00:00 httpd
@@ -478,7 +478,7 @@ unconfined_u:system_r:unconfined_t <em class="replaceable"><code>7729</code></em
 unconfined_u:system_r:unconfined_t <em class="replaceable"><code>7730</code></em> ?      00:00:00 httpd
 
 </pre></li><li class="listitem"><div class="para">
-					Change into a directory where your Linux user has write access to, and run the <code class="command">wget http://localhost/test2file</code> command. Unless there are changes to the default configuration, this command succeeds:
+					Cambie al directorio donde su usuario Linux tenga permiso de escritura y ejecute el comando <code class="command">wget http://localhost/prueba2</code>. A menos que hayan cambios en la configuración predeterminada, este comando debería tener éxito:
 				</div><pre class="screen">--2009-05-07 01:41:10--  http://localhost/test2file
 Resolving localhost... 127.0.0.1
 Connecting to localhost|127.0.0.1|:80... connected.
@@ -491,19 +491,19 @@ Saving to: `test2file.1'
 2009-05-07 01:41:10 (0.00 B/s) - `test2file.1' saved [0/0]
 
 </pre><div class="para">
-					Although the <code class="systemitem">httpd</code> process does not have access to files labeled with the <code class="computeroutput">samba_share_t</code> type, <code class="systemitem">httpd</code> is running in the unconfined <code class="computeroutput">unconfined_t</code> domain, and falls back to using DAC rules, and as such, the <code class="command">wget</code> command succeeds. Had <code class="systemitem">httpd</code> been running in the confined <code class="computeroutput">httpd_t</code> domain, the <code class="command">wget</code> command would have failed.
+					Aunque el proceso <code class="systemitem">httpd</code> no tiene acceso a archivos etiquetados con el tipo <code class="computeroutput">samba_share_t</code>, <code class="systemitem">httpd</code> se ejecuta en el dominio <code class="computeroutput">unconfined_t</code>, y termina usando las reglas DAC, como tal, el comando <code class="command">wget</code> tiene éxito. Teniendo a <code class="systemitem">httpd</code> ejecutándose en el dominio <code class="computeroutput">httpd_t</code>, el comando <code class="command">wget</code> habría fallado.
 				</div></li><li class="listitem"><div class="para">
-					The <code class="command">restorecon</code> command restores the default SELinux context for files. As the Linux root user, run the <code class="command">restorecon -v /usr/sbin/httpd</code> command to restore the default SELinux context for <code class="filename">/usr/sbin/httpd</code>:
+					El comando <code class="command">restorecon</code> restaura el contexto SELinux predeterminado de los archivos. Como usuario root de Linux, ejecute el comando <code class="command">restorecon -v /usr/sbin/httpd</code> para restaurar el contexto SELinux de <code class="filename">/usr/sbin/httpd</code>:
 				</div><pre class="screen"># /sbin/restorecon -v /usr/sbin/httpd
 restorecon reset /usr/sbin/httpd context system_u:object_r:unconfined_notrans_exec_t:s0-&gt;system_u:object_r:httpd_exec_t:s0
 
 </pre><div class="para">
-					Run the <code class="command">ls -Z /usr/sbin/httpd</code> command to confirm that <code class="filename">/usr/sbin/httpd</code> is labeled with the <code class="computeroutput">httpd_exec_t</code> type:
+					Ejecute el comando <code class="command">ls -Z /usr/sbin/httpd</code> para confirmar que <code class="filename">/usr/sbin/httpd</code> está etiquetado con el tipo <code class="computeroutput">httpd_exec_t</code>:
 				</div><pre class="screen">$ ls -Z /usr/sbin/httpd
 -rwxr-xr-x  root root system_u:object_r:httpd_exec_t   /usr/sbin/httpd
 
 </pre></li><li class="listitem"><div class="para">
-					As the Linux root user, run the <code class="command">/sbin/service httpd restart</code> command to restart <code class="systemitem">httpd</code>. After restarting, run the <code class="command">ps -eZ | grep httpd</code> to confirm that <code class="systemitem">httpd</code> is running in the confined <code class="computeroutput">httpd_t</code> domain:
+					Como usuario root de Linux, corra el comando <code class="command">/sbin/service httpd restart</code> para reiniciar <code class="systemitem">httpd</code>. Después de reiniciar, ejecute <code class="command">ps -eZ | grep httpd</code> para confirmar que <code class="systemitem">httpd</code> se está ejecutando en el dominio confinado <code class="computeroutput">httpd_t</code>:
 				</div><pre class="screen"># /sbin/service httpd restart
 Stopping httpd:                                            [  OK  ]
 Starting httpd:                                            [  OK  ]
@@ -519,16 +519,16 @@ unconfined_u:system_r:httpd_t    8888 ?        00:00:00 httpd
 unconfined_u:system_r:httpd_t    8889 ?        00:00:00 httpd
 
 </pre></li><li class="listitem"><div class="para">
-					As the Linux root user, run the <code class="command">rm -i /var/www/html/test2file</code> command to remove <code class="filename">test2file</code>.
+					Como usuario root de Linux, corra el comando <code class="command">rm -i /var/www/html/prueba2</code> para eliminar <code class="filename">prueba2</code>.
 				</div></li><li class="listitem"><div class="para">
-					If you do not require <code class="systemitem">httpd</code> to be running, as the Linux root user, run the <code class="command">service httpd stop</code> command to stop <code class="systemitem">httpd</code>:
+					Si no necesita que corra <code class="systemitem">httpd</code>, como usuario root de Linux corra el comando <code class="command">service httpd stop</code> para detener a <code class="systemitem">httpd</code>:
 				</div><pre class="screen"># /sbin/service httpd stop
 Stopping httpd:                                            [  OK  ]
 
 </pre></li></ol></div><div class="para">
-			The examples in these sections demonstrate how data can be protected from a compromised confined-process (protected by SELinux), as well as how data is more accessible to an attacker from a compromised unconfined-process (not protected by SELinux).
-		</div></div><div class="section" title="4.3. Confined and Unconfined Users" id="sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.3. Confined and Unconfined Users</h2></div></div></div><div class="para">
-			Each Linux user is mapped to an SELinux user via SELinux policy. This allows Linux users to inherit the restrictions on SELinux users. This Linux user mapping is seen by running the <code class="command">semanage login -l</code> command as the Linux root user:
+			Los ejemplos en estas secciones muestran cómo proteger los datos desde un proceso confinado comprometido (protegido por SELinux), así como cuánto más accesible son los datos para un atacante si el proceso comprometido estaba no confinado (no protegido por SELinux).
+		</div></div><div class="section" title="4.3. Usuarios Confinados y no Confinados" id="sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.3. Usuarios Confinados y no Confinados</h2></div></div></div><div class="para">
+			Cada usuario Linux se mapea a un usuario SELinux vía la política de SELinux. Esto permite a los usuarios Linux heredar las restricciones sobre los usuarios SELinux. Este mapeo de usuarios Linux se ve ejecutando el comando <code class="command">semanage login -l</code> como usuario root de Linux:
 		</div><pre class="screen"># /usr/sbin/semanage login -l
 
 Login Name                SELinux User              MLS/MCS Range
@@ -538,13 +538,13 @@ root                      unconfined_u              s0-s0:c0.c1023
 system_u                  system_u                  s0-s0:c0.c1023
 
 </pre><div class="para">
-			In Fedora 11, Linux users are mapped to the SELinux <code class="computeroutput">__default__</code> login by default (which is mapped to the SELinux <code class="computeroutput">unconfined_u</code> user). The following defines the default-mapping:
+			En Fedora 11, los usuarios de Linux se mapean por defecto al ingreso <code class="computeroutput">__default__</code> de SELinux (el cual se mapea al usuario SELinux <code class="computeroutput">unconfined_u</code>). Lo siguiente define el mapeo por defecto:
 		</div><pre class="screen">__default__               unconfined_u              s0-s0:c0.c1023
 
 </pre><div class="para">
-			The following example demonstrates adding a new Linux user, and that Linux user being mapped to the SELinux <code class="computeroutput">unconfined_u</code> user. It assumes that the Linux root user is running unconfined, as it does by default in Fedora 11:
+			El siguiente ejemplo muestra el agregado de un usuario de Linux nuevo y el mapeo de ese usuario al usuario SELinux <code class="computeroutput">unconfined_u</code>. Asume que el usuario root corre no confinado, como es por defecto en Fedora 11:
 		</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
-					As the Linux root user, run the <code class="command">/usr/sbin/useradd newuser</code> command to create a new Linux user named newuser.
+					Como usuario root de Linux, ejecute el comando <code class="command">/usr/sbin/useradd usuarionuevo</code> para crear un nuevo usuario Linux con nombre usuarionuevo.
 				</div></li><li class="listitem"><div class="para">
 					As the Linux root user, run the <code class="command">passwd newuser</code> command to assign a password to the Linux newuser user:
 				</div><pre class="screen"># passwd newuser
@@ -554,28 +554,28 @@ Retype new UNIX password: <em class="replaceable"><code>Enter the same password
 passwd: all authentication tokens updated successfully.
 
 </pre></li><li class="listitem"><div class="para">
-					Log out of your current session, and log in as the Linux newuser user. When you log in, pam_selinux maps the Linux user to an SELinux user (in this case, unconfined_u), and sets up the resulting SELinux context. The Linux user's shell is then launched with this context. Run the <code class="command">id -Z</code> command to view the context of a Linux user:
+					Salga de su sesión actual e ingrese como el usuario Linux usuarionuevo. Cuando ingrese, pam_selinux mapea el usuario Linux a un usuario SELinux (en este caso, unconfined_u), y configura el contexto SELinux resultante. El shell del usuario Linux es entonces lanzado en este contexto. Corra el comando <code class="command">id -Z</code> para ver el contexto de un usuario Linux:
 				</div><pre class="screen">[newuser at localhost ~]$ id -Z
 unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
 
 </pre></li><li class="listitem"><div class="para">
-					Log out of the Linux newuser's session, and log in with your account. If you do not want the Linux newuser user, run the <code class="command">/usr/sbin/userdel -r newuser</code> command as the Linux root user to remove it, along with the Linux newuser's home directory.
+					Salga de la sesión del usuarionuevo de Linux e ingrese con su cuenta. Si no quiere el usuario usuarionuevo, ejecute el comando <code class="command">/usr/sbin/userdel -r usuarionuevo</code> como usuario root de Linux para eliminarlo, junto con su directorio de inicio.
 				</div></li></ol></div><div class="para">
-			Confined and unconfined Linux users are subject to executable and writeable memory checks, and are also restricted by MCS (and MLS, if the MLS policy is used). If unconfined Linux users execute an application that SELinux policy defines can transition from the <code class="computeroutput">unconfined_t</code> domain to its own confined domain, unconfined Linux users are still subject to the restrictions of that confined domain. The security benefit of this is that, even though a Linux user is running unconfined, the application remains confined, and therefore, the exploitation of a flaw in the application can be limited by policy. Note: this does not protect the system from the user. Instead, the user and the system are being protected from possible damage caused by a flaw in the application.
+			Los usuarios Linux confinados y no confinados son sujeto a chequeso de memoria escribible y ejecutable, y también son restringidos por MCS (y MLS, si la política MLS está siendo usada). Si los usuarios Linux no confinados ejecutan una aplicación que la política de SELinux define que puede transicionar del dominio <code class="computeroutput">unconfined_t</code> a su propio dominio confinado, los usuarios Linux no confinados están sujetos a restricciones de ese dominio confinado. El beneficio de seguridad de esto es que, aunque un usuario Linux corra no confinado, la aplicación permanece confinada, y por lo tanto, la explotación de una brecha en la aplicación está limitada por la política. Nota: esto no protege al sistema del usuario. En su defecto, el usuario y el sistema están siendo protegidos de posibles daños causados por una brecha en la aplicación.
 		</div><div class="para">
-			The following confined SELinux users are available in Fedora 11:
-		</div><div class="table"><div class="table-contents"><table summary="SELinux User Capabilities" border="1"><colgroup><col width="17%" /><col width="17%" /><col width="17%" /><col width="17%" /><col width="17%" /><col width="17%" /></colgroup><thead><tr><th>
-							User
+			Los siguientes usuarios SELinux confinados están disponibles en Fedora 11:
+		</div><div class="table" title="Tabla 4.1. Capacidades del Usuario SELinux" id="tabl-Security-Enhanced_Linux-Confined_and_Unconfined_Users-SELinux_User_Capabilities"><div class="table-contents"><table summary="Capacidades del Usuario SELinux" border="1"><colgroup><col width="17%" /><col width="17%" /><col width="17%" /><col width="17%" /><col width="17%" /><col width="17%" /></colgroup><thead><tr><th>
+							Usuario
 						</th><th>
-							Domain
+							Dominio
 						</th><th>
-							X Window System
+							Sistema de Ventanas X
 						</th><th>
-							su and sudo
+							su y sudo
 						</th><th>
-							Execute in home directory and /tmp/
+							Ejecute en el directorio de inicio y /tmp/
 						</th><th>
-							Networking
+							Red
 						</th></tr></thead><tbody><tr><td>
 							guest_u
 						</td><td>
@@ -624,64 +624,64 @@ unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
 							optional
 						</td><td align="center">
 							yes
-						</td></tr></tbody></table></div><h6>Tabla 4.1. SELinux User Capabilities</h6></div><br class="table-break" /><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-					Linux users in the <code class="computeroutput">guest_t</code>, <code class="computeroutput">xguest_t</code>, and <code class="computeroutput">user_t</code> domains can only run set user ID (setuid) applications if SELinux policy permits it (such as <code class="command">passwd</code>). They can not run the <code class="command">su</code> and <code class="command">/usr/bin/sudo</code> setuid applications, and therefore, can not use these applications to become the Linux root user.
+						</td></tr></tbody></table></div><h6>Tabla 4.1. Capacidades del Usuario SELinux</h6></div><br class="table-break" /><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+					Los usuarios Linux en los dominios <code class="computeroutput">guest_t</code>, <code class="computeroutput">xguest_t</code> y <code class="computeroutput">user_t</code> sólo pueden ejecutar aplicaciones con ID de usuario (setuid) si la política de SELinux lo permite (tal como <code class="command">passwd</code>). No podrán ejecutar <code class="command">su</code> y <code class="command">/usr/bin/sudo</code>
 				</div></li><li class="listitem"><div class="para">
-					Linux users in the <code class="computeroutput">guest_t</code> domain have no network access, and can only log in via a terminal (including <code class="systemitem">ssh</code>; they can log in via <code class="systemitem">ssh</code>, but can not use <code class="systemitem">ssh</code> to connect to another system).
+					Los usuarios Linux en el dominio <code class="computeroutput">guest_t</code> no tienen acceso a la red, y sólo pueden ingresar vía una terminal (incluyendo <code class="systemitem">ssh</code>; pueden ingresaro por <code class="systemitem">ssh</code>, pero no se pueden <code class="systemitem">ssh</code> conectar a otro sistema).
 				</div></li><li class="listitem"><div class="para">
-					The only network access Linux users in the <code class="computeroutput">xguest_t</code> domain have is <span class="application"><strong>Firefox</strong></span> connecting to web pages.
+					El único acceso de red que tienen los usuarios en el dominoi <code class="computeroutput">xguest_t</code> es con <span class="application"><strong>Firefox</strong></span> conectándose a páginas web.
 				</div></li><li class="listitem"><div class="para">
-					Linux users in the <code class="computeroutput">xguest_t</code>, <code class="computeroutput">user_t</code> and <code class="computeroutput">staff_t</code> domains can log in via the X Window System and a terminal.
+					Los usuarios Linux en los dominios <code class="computeroutput">xguest_t</code>, <code class="computeroutput">user_t</code> y <code class="computeroutput">staff_t</code> pueden ingresar vía el Sistema de Ventanas X o por una terminal.
 				</div></li><li class="listitem"><div class="para">
-					By default, Linux users in the <code class="computeroutput">staff_t</code> domain do not have permissions to execute applications with <code class="command">/usr/bin/sudo</code>. These permissions must be configured by an administrator.
+					Por defecto, los usuarios Linux en el dominio <code class="computeroutput">staff_t</code> no tienen permisos para ejecutar aplicaciones con <code class="command">/usr/bin/sudo</code>. Estos permisos deben ser configurados por un administrador.
 				</div></li></ul></div><div class="para">
-			By default, Linux users in the <code class="computeroutput">guest_t</code> and <code class="computeroutput">xguest_t</code> domains can not execute applications in their home directories or <code class="filename">/tmp/</code>, preventing them from executing applications (which inherit users' permissions) in directories they have write access to. This helps prevent flawed or malicious applications from modifying files users' own.
+			Por defecto, los usuarios de Linux en los dominios <code class="computeroutput">guest_t</code> y <code class="computeroutput">xguest_t</code> no pueden ejecutar aplicaciones en sus directorios de inicio o en <code class="filename">/tmp/</code>, previniéndolos de ejecutar aplicaciones (que hereden los permisos de los usuarios) en directorios a los que tienen acceso de escritura. Esto ayuda a prevenir que aplicaciones maliciosas modifiquen archivos de los usuarios.
 		</div><div class="para">
-			By default, Linux users in the <code class="computeroutput">user_t</code> and <code class="computeroutput">staff_t</code> domains can execute applications in their home directories and <code class="filename">/tmp/</code>. Refer to <a class="xref" href="#sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications" title="6.6. Booleans for Users Executing Applications">Sección 6.6, “Booleans for Users Executing Applications”</a> for information about allowing and preventing users from executing applications in their home directories and <code class="filename">/tmp/</code>.
-		</div></div><div class="footnotes"><br /><hr width="100" align="left" /><div class="footnote"><p><sup>[<a id="ftn.id535564" href="#id535564" class="para">6</a>] </sup>
-						When using other policies, such as MLS, other roles may be used, for example, <code class="computeroutput">secadm_r</code>.
-					</p></div><div class="footnote"><p><sup>[<a id="ftn.id1840232" href="#id1840232" class="para">7</a>] </sup>
-						When using other policies, such as MLS, other roles may also be used, for example, <code class="computeroutput">secadm_r</code>.
-					</p></div></div></div><div xml:lang="es-ES" class="chapter" title="Capítulo 5. Working with SELinux" id="chap-Security-Enhanced_Linux-Working_with_SELinux" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 5. Working with SELinux</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Packages">5.1. SELinux Packages</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used">5.2. Which Log File is Used</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Main_Configuration_File">5.3. Main Configuration File</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux">5.4. Enabling and Disabling SELinux</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_L
 inux-Enabling_and_Disabling_SELinux-Enabling_SELinux">5.4.1. Enabling SELinux</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux">5.4.2. Disabling SELinux</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes">5.5. SELinux Modes</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans">5.6. Booleans</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Booleans-Listing_Booleans">5.6.1. Listing Booleans</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Booleans-Configuring_Booleans">5.6.2. Configuring Booleans</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS">5.6.3. Booleans for NFS and CIFS</a></span></dt></dl></dd><dt><span class="section"><a href=
 "#sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files">5.7. SELinux Contexts - Labeling Files</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Temporary_Changes_chcon">5.7.1. Temporary Changes: chcon</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext">5.7.2. Persistent Changes: semanage fcontext</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types">5.8. The file_t and default_t Types</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems">5.9. Mounting File Systems</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Mounting_File_Systems-Context_Mounts">5.9.1. Context Mounts</a></span></dt>
 <dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Mounting_File_Systems-Changing_the_Default_Context">5.9.2. Changing the Default Context</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Mounting_File_Systems-Mounting_an_NFS_File_System">5.9.3. Mounting an NFS File System</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Mounting_File_Systems-Multiple_NFS_Mounts">5.9.4. Multiple NFS Mounts</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Mounting_File_Systems-Making_Context_Mounts_Persistent">5.9.5. Making Context Mounts Persistent</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_">5.10. Maintaining SELinux Labels </a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Copying_Files_and_Directories">5.10.1. Copying Files a
 nd Directories</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Moving_Files_and_Directories">5.10.2. Moving Files and Directories</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context">5.10.3. Checking the Default SELinux Context</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_tar">5.10.4. Archiving Files with tar</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_star">5.10.5. Archiving Files with star</a></span></dt></dl></dd></dl></div><div class="para">
-		The following sections give a brief overview of the main SELinux packages in Fedora 11; installing and updating packages; which log files are used; the main SELinux configuration file; enabling and disabling SELinux; SELinux modes; configuring Booleans; temporarily and persistently changing file and directory labels; overriding file system labels with the <code class="command">mount</code> command; mounting NFS file systems; and how to preserve SELinux contexts when copying and archiving files and directories.
-	</div><div class="section" title="5.1. SELinux Packages" id="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Packages"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.1. SELinux Packages</h2></div></div></div><div class="para">
-			In Fedora 11, the SELinux packages are installed by default, unless they are manually excluded during installation. By default, SELinux targeted policy is used, and SELinux runs in enforcing mode. The following is a brief description of the main SELinux packages:
+			By default, Linux users in the <code class="computeroutput">user_t</code> and <code class="computeroutput">staff_t</code> domains can execute applications in their home directories and <code class="filename">/tmp/</code>. Refer to <a class="xref" href="#sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications" title="6.6. Booleanos para que los Usuarios Ejecuten Aplicaciones">Sección 6.6, “Booleanos para que los Usuarios Ejecuten Aplicaciones”</a> for information about allowing and preventing users from executing applications in their home directories and <code class="filename">/tmp/</code>.
+		</div></div><div class="footnotes"><br /><hr width="100" align="left" /><div class="footnote"><p><sup>[<a id="ftn.id753277" href="#id753277" class="para">6</a>] </sup>
+						cuando se usan otras políticas, tal como MLS, se pueden usar otros roles, por ejemplo <code class="computeroutput">secadm_r</code>.
+					</p></div><div class="footnote"><p><sup>[<a id="ftn.id765190" href="#id765190" class="para">7</a>] </sup>
+						Cuando se usan otras políticas, tal como la MLS, se pueden usar también otros roles, por ejemplo el <code class="computeroutput">secadm_r</code>.
+					</p></div></div></div><div xml:lang="es-ES" class="chapter" title="Capítulo 5. Trabajando con SELinux" id="chap-Security-Enhanced_Linux-Working_with_SELinux" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 5. Trabajando con SELinux</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Packages">5.1. Paquetes de SELinux</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used">5.2. Qué Archivo Log se usa</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Main_Configuration_File">5.3. Archivo de Configuración Principal</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux">5.4. Habilitando y Deshabilitando SELinux</a></span></dt><dd><dl><dt><span class="section"><a href=
 "#sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Enabling_SELinux">5.4.1. Habilitando SELinux</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux">5.4.2. Deshabilitando SELinux</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes">5.5. Modos de SELinux</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans">5.6. Booleanos</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Booleans-Listing_Booleans">5.6.1. Listando los Booleanos</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Booleans-Configuring_Booleans">5.6.2. Configurando los Booleanos</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS">5.6.3. Booleanos para NFS y CIFS</a></span
 ></dt></dl></dd><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files">5.7. Contextos de SELinux - Etiquetado de Archivos</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Temporary_Changes_chcon">5.7.1. Cambios Temporales: chcon</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext">5.7.2. Cambios Persistentes: semanage fcontext</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types">5.8. Los tipos file_t y default_t</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems">5.9. Montaje de Sistemas de Archivos</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Mo
 unting_File_Systems-Context_Mounts">5.9.1. Montajes de Contexto</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Mounting_File_Systems-Changing_the_Default_Context">5.9.2. Cambio del Contexto Predeterminado</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Mounting_File_Systems-Mounting_an_NFS_File_System">5.9.3. Montando un Sistema de Archivos NFS</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Mounting_File_Systems-Multiple_NFS_Mounts">5.9.4. Montajes NFS Múltiples</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Mounting_File_Systems-Making_Context_Mounts_Persistent">5.9.5. Haciendo Persistente los Contextos de Montajes</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_">5.10. Mantención de las Etiquetas de SELinux</a></span></dt><dd><dl><dt><span class="section
 "><a href="#sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Copying_Files_and_Directories">5.10.1. Copia de Directorios y Archivos</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Moving_Files_and_Directories">5.10.2. Movimiento de Archivos y Directorios</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context">5.10.3. Chequeando el Contexto SELinux Predeterminado</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_tar">5.10.4. Archivando archivos con tar</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_star">5.10.5. Archivando archivos con tar</a></span></dt></dl></dd></dl></div><div class="para">
+		Las siguientes secciones dan un breve repaso de los paquetes de SELinux principales en Fedora 11; instalación y actualización de paquetes; qué archivos de registro se usan; el archivo de configuración principal de SELinux; habilitación y deshabilitación de SELinux; modos de SELinux; configuración de Booleanos; cambios temporales y permanentes de etiquetas de archivos y directorios; superposición de las etiquetas de sistemas de archivos con el comando <code class="command">mount</code>; montaje de sistemas de archivos NFS; y cómo preservar contextos de SELinux cuando se copia y compacta archivos y directorios.
+	</div><div class="section" title="5.1. Paquetes de SELinux" id="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Packages"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.1. Paquetes de SELinux</h2></div></div></div><div class="para">
+			En Fedora 11, los paquetes SELinux se instalan por defecto, a menos que hayan sido manualmente excluídos durante la instalación. Por defecto, la política destinada de SELinux se usa y SELinux corre en modo Obediente. La siguiente es una descripción breve de los paquetes SELinux principales:
 		</div><div class="para">
-			<span class="package">policycoreutils</span>: provides utilities, such as <code class="command">semanage</code>, <code class="command">restorecon</code>, <code class="command">audit2allow</code>, <code class="command">semodule</code>, <code class="command">load_policy</code>, and <code class="command">setsebool</code>, for operating and managing SELinux.
+			<span class="package">policycoreutils</span>: provee utilitarios, tales como <code class="command">semanage</code>, <code class="command">restorecon</code>, <code class="command">audit2allow</code>, <code class="command">semodule</code>, <code class="command">load_policy</code> y <code class="command">setsebool</code>, para la operación y administración de SELinux.
 		</div><div class="para">
-			<span class="package">policycoreutils-gui</span>: provides <code class="command">system-config-selinux</code>, a graphical tool for managing SELinux.
+			<span class="package">policycoreutils-gui</span>: provee <code class="command">system-config-selinux</code>, una herramienta gráfica para la administración de SELinux.
 		</div><div class="para">
-			<span class="package">selinux-policy</span>: provides the SELinux Reference Policy. The SELinux Reference Policy is a complete SELinux policy, and is used as a basis for other policies, such as the SELinux targeted policy. Refer to the Tresys Technology <a href="http://oss.tresys.com/projects/refpolicy">SELinux Reference Policy</a> page for further information. The <span class="package">selinux-policy-devel</span> package provides development tools, such as <code class="command">/usr/share/selinux/devel/policygentool</code> and <code class="command">/usr/share/selinux/devel/policyhelp</code>, as well as example policy files. This package was merged into the <span class="package">selinux-policy</span> package.
+			<span class="package">selinux-policy</span>: provee una Política de Referencia de SELinux. La Política de Referencia de SELinux en una política de SELinux completa, y se usa como base para otras políticas, tales como la política destinada de SELinux. Vaya a la página <a href="http://oss.tresys.com/projects/refpolicy">Política de Referencia de SELinux</a> de Tresys Technology para más información. El paquete <span class="package">selinux-policy-devel</span> provee herramientas de desarrollo, tales como<code class="command">/usr/share/selinux/devel/policygentool</code> y <code class="command">/usr/share/selinux/devel/policyhelp</code>, así como archivos de política ejemplos. Este paquete fue mezclado con el paquete <span class="package">selinux-policy</span>.
 		</div><div class="para">
-			<span class="package">selinux-policy-<em class="replaceable"><code>policy</code></em></span>: provides SELinux policies. For targeted policy, install <span class="package">selinux-policy-targeted</span>. For MLS, install <span class="package">selinux-policy-mls</span>. In Fedora 8, the strict policy was merged into targeted policy, allowing confined and unconfined users to co-exist on the same system.
+			<span class="package">selinux-policy-<em class="replaceable"><code>policy</code></em></span>: provee las políticas de SELinux. Para la política destinada, instale <span class="package">selinux-policy-targeted</span>. Para MLS, instale <span class="package">selinux-policy-mls</span>. En Fedora 8, la política estricta fue mezclada con la política destinada, permitiendo a los usuarios confinados y no confinados coexistir en el mismo sistema.
 		</div><div class="para">
-			<span class="package">setroubleshoot-server</span>: translates denial messages, produced when access is denied by SELinux, into detailed descriptions that are viewed with <code class="command">sealert</code> (which is provided by this package).
+			<span class="package">setroubleshoot-server</span>: traduce mensajes de negaciones, producidos cuando el acceso es denegado por SELinux, en descripciones detalladas que se ven con <code class="command">sealert</code> (que se provee en este paquete).
 		</div><div class="para">
-			<span class="package">setools</span>, <span class="package">setools-gui</span>, and <span class="package">setools-console</span>: these packages provide the <a href="http://oss.tresys.com/projects/setools">Tresys Technology SETools distribution</a>, a number of tools and libraries for analyzing and querying policy, audit log monitoring and reporting, and file context management<sup>[<a id="id1588199" href="#ftn.id1588199" class="footnote">8</a>]</sup>. The <span class="package">setools</span> package is a meta-package for SETools. The <span class="package">setools-gui</span> package provides the <code class="command">apol</code>, <code class="command">seaudit</code>, and <code class="command">sediffx</code> tools. The <span class="package">setools-console</span> package provides the <code class="command">seaudit-report</code>, <code class="command">sechecker</code>, <code class="command">sediff</code>, <code class="command">seinfo</code>, <code class="command">sesearch</c
 ode>, <code class="command">findcon</code>, <code class="command">replcon</code>, and <code class="command">indexcon</code> command line tools. Refer to the <a href="http://oss.tresys.com/projects/setools">Tresys Technology SETools</a> page for information about these tools.
+			<span class="package">setools</span>, <span class="package">setools-gui</span>, and <span class="package">setools-console</span>: these packages provide the <a href="http://oss.tresys.com/projects/setools">Tresys Technology SETools distribution</a>, a number of tools and libraries for analyzing and querying policy, audit log monitoring and reporting, and file context management<sup>[<a id="id820736" href="#ftn.id820736" class="footnote">8</a>]</sup>. The <span class="package">setools</span> package is a meta-package for SETools. The <span class="package">setools-gui</span> package provides the <code class="command">apol</code>, <code class="command">seaudit</code>, and <code class="command">sediffx</code> tools. The <span class="package">setools-console</span> package provides the <code class="command">seaudit-report</code>, <code class="command">sechecker</code>, <code class="command">sediff</code>, <code class="command">seinfo</code>, <code class="command">sesearch</cod
 e>, <code class="command">findcon</code>, <code class="command">replcon</code>, and <code class="command">indexcon</code> command line tools. Refer to the <a href="http://oss.tresys.com/projects/setools">Tresys Technology SETools</a> page for information about these tools.
 		</div><div class="para">
-			<span class="package">libselinux-utils</span>: provides the <code class="command">avcstat</code>, <code class="command">getenforce</code>, <code class="command">getsebool</code>, <code class="command">matchpathcon</code>, <code class="command">selinuxconlist</code>, <code class="command">selinuxdefcon</code>, <code class="command">selinuxenabled</code>, <code class="command">setenforce</code>, <code class="command">togglesebool</code> tools.
+			<span class="package">libselinux-utils</span>: provee las herramientas <code class="command">avcstat</code>, <code class="command">getenforce</code>, <code class="command">getsebool</code>, <code class="command">matchpathcon</code>, <code class="command">selinuxconlist</code>, <code class="command">selinuxdefcon</code>, <code class="command">selinuxenabled</code>, <code class="command">setenforce</code>, <code class="command">togglesebool</code>.
 		</div><div class="para">
-			<span class="package">mcstrans</span>: translates levels, such as <code class="computeroutput">s0-s0:c0.c1023</code>, to an easier to read form, such as <code class="computeroutput">SystemLow-SystemHigh</code>. This package is not installed by default.
+			<span class="package">mcstrans</span>: traduce niveles, tales como <code class="computeroutput">s0-s0:c0.c1023</code>, a una forma legible como <code class="computeroutput">SystemLow-SystemHigh</code>. Este paquete no se instala por defecto.
 		</div><div class="para">
-			To install packages in Fedora 11, as the Linux root user, run the <code class="command">yum install <em class="replaceable"><code>package-name</code></em></code> command. For example, to install the <span class="package">mcstrans</span> package, run the <code class="command">yum install mcstrans</code> command. To upgrade all installed packages in Fedora 11, run the <code class="command">yum update</code> command.
+			Para instalar paquetes en Fedora 11, como usuario root de Linux ejecute el comando <code class="command">yum install <em class="replaceable"><code>nombre-de-paquete</code></em></code>. Por ejemplo, para instalar el paquete <span class="package">mcstrans</span>, ejecute el comando <code class="command">yum install mcstrans</code>. Para actualizar todos los paquetes instalados en Fedora 11, ejecute el comando <code class="command">yum update</code>.
 		</div><div class="para">
-			Refer to <a href="http://docs.fedoraproject.org/yum/en/">Managing Software with yum</a><sup>[<a id="id708842" href="#ftn.id708842" class="footnote">9</a>]</sup> for further information about using <code class="command">yum</code> to manage packages.
+			Vaya a <a href="http://docs.fedoraproject.org/yum/en/">Administración de Software con yum</a><sup>[<a id="id778158" href="#ftn.id778158" class="footnote">9</a>]</sup> para más información sobre el uso de <code class="command">yum</code> para administrar paquetes.
 		</div><div class="note"><h2>Nota</h2><div class="para">
-				In previous versions of Fedora, the <span class="package">selinux-policy-devel</span> package is required when making a local policy module with <code class="command">audit2allow -M</code>.
-			</div></div></div><div class="section" title="5.2. Which Log File is Used" id="sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.2. Which Log File is Used</h2></div></div></div><div class="para">
-			In Fedora 11, the <span class="package">setroubleshoot-server</span> and <span class="package">audit</span> packages are installed if packages are not removed from the default package selection. These packages include the <code class="systemitem">setroubleshootd</code> and <code class="systemitem">auditd</code> daemons respectively. These daemons run by default.
+				En versiones anteriores de Fedora, el paquete <span class="package">selinux-policy-devel</span> es necesario cuando se crea un módulo de política local con <code class="command">audit2allow -M</code>.
+			</div></div></div><div class="section" title="5.2. Qué Archivo Log se usa" id="sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.2. Qué Archivo Log se usa</h2></div></div></div><div class="para">
+			En Fedora 11, los paquetes <span class="package">setroubleshoot-server</span> y <span class="package">audit</span> se instalan si los paquetes no se eliminan de la selección de paquetes predeterminada. Estos paquetes incluyen a los demonios <code class="systemitem">setroubleshootd</code> y <code class="systemitem">auditd</code> respectivamente. Estos demonios se ejecutan por defecto.
 		</div><div class="para">
-			SELinux denial messages, such as the following, are written to <code class="filename">/var/log/audit/audit.log</code> by default:
+			Los mensajes de negación de SELinux, tales como el siguiente, se escriben por defecto en <code class="filename">/var/log/audit/audit.log</code>:
 		</div><pre class="screen">type=AVC msg=audit(1223024155.684:49): avc:  denied  { getattr } for  pid=2000 comm="httpd" path="/var/www/html/file1" dev=dm-0 ino=399185 scontext=unconfined_u:system_r:httpd_t:s0 tcontext=system_u:object_r:samba_share_t:s0 tclass=file
 
 </pre><div class="para">
-			Also, if <code class="systemitem">setroubleshootd</code> is running, which it is by default, denial messages from <code class="filename">/var/log/audit/audit.log</code> are translated to an easier-to-read form and sent to <code class="filename">/var/log/messages</code>:
+			También, si <code class="systemitem">setroubleshootd</code> está ejecutándose, lo que es por defecto, los mensajes de negación desde <code class="filename">/var/log/audit/audit.log</code> se traducen a una forma más fácil de leer en <code class="filename">/var/log/messages</code>:
 		</div><pre class="screen">May  7 18:55:56 localhost setroubleshoot: SELinux is preventing httpd (httpd_t) "getattr" to /var/www/html/file1 (samba_share_t). For complete SELinux messages. run sealert -l de7e30d6-5488-466d-a606-92c9f40d316d
 
 </pre><div class="para">
-			Denial messages are sent to a different location, depending on which daemons are running:
-		</div><div class="segmentedlist"><table border="0"><thead><tr class="segtitle"><th>Daemon</th><th>Log Location</th></tr></thead><tbody><tr class="seglistitem"><td class="seg">auditd on</td><td class="seg"><code class="filename">/var/log/audit/audit.log</code></td></tr><tr class="seglistitem"><td class="seg">auditd off; rsyslogd on</td><td class="seg"><code class="filename">/var/log/messages</code></td></tr><tr class="seglistitem"><td class="seg">setroubleshootd, rsyslogd, and auditd on</td><td class="seg"><code class="filename">/var/log/audit/audit.log</code>. Easier-to-read denial messages also sent to <code class="filename">/var/log/messages</code></td></tr></tbody></table></div><div class="formalpara"><h5 class="formalpara">Starting Daemons Automatically</h5>
-				To configure the <code class="systemitem">auditd</code>, <code class="systemitem">rsyslogd</code>, and <code class="systemitem">setroubleshootd</code> daemons to automatically start at boot, run the following commands as the Linux root user:
+			Los mensajes de negación se envían a una ubicación distinta, dependiendo de cuáles demonios se están ejecutando:
+		</div><div class="segmentedlist"><table border="0"><thead><tr class="segtitle"><th>Daemon</th><th>Log Location</th></tr></thead><tbody><tr class="seglistitem"><td class="seg">auditd on</td><td class="seg"><code class="filename">/var/log/audit/audit.log</code></td></tr><tr class="seglistitem"><td class="seg">auditd off; rsyslogd on</td><td class="seg"><code class="filename">/var/log/messages</code></td></tr><tr class="seglistitem"><td class="seg">setroubleshootd, rsyslogd, and auditd on</td><td class="seg"><code class="filename">/var/log/audit/audit.log</code>. Easier-to-read denial messages also sent to <code class="filename">/var/log/messages</code></td></tr></tbody></table></div><div class="formalpara" id="form-Security-Enhanced_Linux-Which_Log_File_is_Used-Starting_Daemons_Automatically"><h5 class="formalpara">Iniciando Demonios Automáticamente</h5>
+				Para configurar los demonios <code class="systemitem">auditd</code>, <code class="systemitem">rsyslogd</code>, y <code class="systemitem">setroubleshootd</code> para que inicien automáticamente al arrancar, corra los siguientes comandos como usuario root de Linux:
 			</div><pre class="screen">/sbin/chkconfig --levels 2345 auditd on
 
 </pre><pre class="screen">/sbin/chkconfig --levels 2345 rsyslog on
@@ -689,19 +689,19 @@ unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
 </pre><pre class="screen">/sbin/chkconfig --levels 345 setroubleshoot on
 
 </pre><div class="para">
-			Use the <code class="command">service <em class="replaceable"><code>service-name</code></em> status</code> command to check if these services are running, for example:
+			Use el comando <code class="command">service <em class="replaceable"><code>nombre-de-servicio</code></em> status</code> para chequear si estos servicios se están ejecutando, por ejemplo:
 		</div><pre class="screen">
 $ /sbin/service auditd status
 auditd (pid  <em class="replaceable"><code>1318</code></em>) is running...
 
 </pre><div class="para">
-			If the above services are not running (<code class="computeroutput"><em class="replaceable"><code>service-name</code></em> is stopped</code>), use the <code class="command">service <em class="replaceable"><code>service-name</code></em> start</code> command as the Linux root user to start them. For example:
+			Si los servicos de arriba no se están ejecutando (<code class="computeroutput"><em class="replaceable"><code>nombre-de-servicio</code></em> está detenido</code>), use el comando <code class="command">service <em class="replaceable"><code>nombre-de-servicio</code></em> start</code> como usuario root de Linux para iniciarlos. Por ejemplo:
 		</div><pre class="screen">
 # /sbin/service setroubleshoot start
 Starting setroubleshootd:                                  [  OK  ]
 
-</pre></div><div class="section" title="5.3. Main Configuration File" id="sect-Security-Enhanced_Linux-Working_with_SELinux-Main_Configuration_File"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.3. Main Configuration File</h2></div></div></div><div class="para">
-			The <code class="filename">/etc/selinux/config</code> file is the main SELinux configuration file. It controls the SELinux mode and the SELinux policy to use:
+</pre></div><div class="section" title="5.3. Archivo de Configuración Principal" id="sect-Security-Enhanced_Linux-Working_with_SELinux-Main_Configuration_File"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.3. Archivo de Configuración Principal</h2></div></div></div><div class="para">
+			El archivo <code class="filename">/etc/selinux/config</code> es el archivo de configuración principal de SELinux. Controla el modo de SELinux y la política de SELinux a usar:
 		</div><pre class="screen"># This file controls the state of SELinux on the system.
 # SELINUX= can take one of these three values:
 #       enforcing - SELinux security policy is enforced.
@@ -714,20 +714,20 @@ SELINUX=enforcing
 SELINUXTYPE=targeted
 
 </pre><div class="variablelist"><dl><dt><span class="term"><code class="computeroutput">SELINUX=enforcing</code></span></dt><dd><div class="para">
-						The <code class="option">SELINUX</code> option sets the mode SELinux runs in. SELinux has three modes: enforcing, permissive, and disabled. When using enforcing mode, SELinux policy is enforced, and SELinux denies access based on SELinux policy rules. Denial messages are logged. When using permissive mode, SELinux policy is not enforced. SELinux does not deny access, but denials are logged for actions that would have been denied if running SELinux in enforcing mode. When using disabled mode, SELinux is disabled (the SELinux module is not registered with the Linux kernel), and only DAC rules are used.
+						La opción <code class="option">SELINUX</code> pone el modo en el que corre SELinux. SELinux tiene tres modos: obediente, permisivo y deshabilitado. Cuando se usa modo obediente, la política de SELinux es aplicada y SELinux niega el acceso basándose en las reglas de políticas de SELinux. Los mensajes de negación se guardan. Cuando se usa modo permisivo, la política de SELinux no es obediente. Los mensajes son guardados. SELinux no niega el acceso, pero se guardan las negaciones de acciones que hubieran sido negadas si SELinux estaba en modo obediente. Cuando se usa el modo deshabilitado, SELinux está deshabilitado (el módulo de SELinux no se registra con el kernel de Linux), y sólo se usan las reglas DAC.
 					</div></dd><dt><span class="term"><code class="computeroutput">SELINUXTYPE=targeted</code></span></dt><dd><div class="para">
-						The <code class="option">SELINUXTYPE</code> option sets the SELinux policy to use. Targeted policy is the default policy. Only change this option if you want to use the MLS policy. To use the MLS policy, install the <span class="package">selinux-policy-mls</span> package; configure <code class="option">SELINUXTYPE=mls</code> in <code class="filename">/etc/selinux/config</code>; and reboot your system.
+						La opción <code class="option">SELINUXTYPE</code> pone la política SELinux a usar. La política Destinada es la predeterminada. Sólo cambie esta opción si quiere usar la política MLS. Para usar la política MLS, instale el paquete <span class="package">selinux-policy-mls</span>; configure <code class="option">SELINUXTYPE=mls</code> en <code class="filename">/etc/selinux/config</code>; y reinicie su sistema.
 					</div></dd></dl></div><div class="important"><h2>Importante</h2><div class="para">
-				When systems run with SELinux in permissive or disabled mode, users have permission to label files incorrectly. Also, files created while SELinux is disabled are not labeled. This causes problems when changing to enforcing mode. To prevent incorrectly labeled and unlabeled files from causing problems, file systems are automatically relabeled when changing from disabled mode to permissive or enforcing mode.
-			</div></div></div><div class="section" title="5.4. Enabling and Disabling SELinux" id="sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.4. Enabling and Disabling SELinux</h2></div></div></div><div class="para">
-			Use the <code class="command">/usr/sbin/getenforce</code> or <code class="command">/usr/sbin/sestatus</code> commands to check the status of SELinux. The <code class="command">getenforce</code> command returns <code class="computeroutput">Enforcing</code>, <code class="computeroutput">Permissive</code>, or <code class="computeroutput">Disabled</code>. The <code class="command">getenforce</code> command returns <code class="computeroutput">Enforcing</code> when SELinux is enabled (SELinux policy rules are enforced):
+				Cuando los sistemas corren con SELinux en modo permisivo o deshabilitado, los usuarios tiene permiso para etiquetar los archivos incorrectamente. También, los archivos creados con SELinux deshabilitado no son etiquetados. Esto causa problemas cuando se cambia a modo obediente. Para prevenir el etiquetado incorrecto o la falta de etiquetado, los sistemas de archivos son automáticamente reetiquetados cuando se cambie desde el modo deshabilitado al modo permisivo u obediente.
+			</div></div></div><div class="section" title="5.4. Habilitando y Deshabilitando SELinux" id="sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.4. Habilitando y Deshabilitando SELinux</h2></div></div></div><div class="para">
+			Use los comandos <code class="command">/usr/sbin/getenforce</code> o <code class="command">/usr/sbin/sestatus</code> para chequear el estado de SELinux. El comando <code class="command">getenforce</code> devuelve <code class="computeroutput">Obediente</code>, <code class="computeroutput">Permisivo</code>, o <code class="computeroutput">Deshabilitado</code>. El comando <code class="command">getenforce</code> devuelve <code class="computeroutput">Obediente</code> cuando SELinux está habilitado (las reglas de la política de SELinux son aplicadas):
 		</div><pre class="screen">$ /usr/sbin/getenforce
 Enforcing
 
 </pre><div class="para">
-			The <code class="command">getenforce</code> command returns <code class="computeroutput">Permissive</code> when SELinux is enabled, but SELinux policy rules are not enforced, and only DAC rules are used. The <code class="command">getenforce</code> command returns <code class="computeroutput">Disabled</code> if SELinux is disabled.
+			El comando <code class="command">getenforce</code> devuelve <code class="computeroutput">Permissive</code> cuando SELinux está activado, pero las reglas de políticas de SELinux no están en obligatorio, y sólo se usan las reglas DAC. El comando <code class="command">getenforce</code> devuelve <code class="computeroutput">Disabled</code> si SELinux está deshabilitado.
 		</div><div class="para">
-			The <code class="command">sestatus</code> command returns the SELinux status and the SELinux policy being used:
+			El comando <code class="command">sestatus</code> devuelve el estado de SELinux y la política de SELinux que se está usando:
 		</div><pre class="screen">$ /usr/sbin/sestatus
 SELinux status:                 enabled
 SELinuxfs mount:                /selinux
@@ -738,8 +738,8 @@ Policy from config file:        targeted
 
 </pre><div class="para">
 			<code class="computeroutput">SELinux status: enabled</code> is returned when SELinux is enabled. <code class="computeroutput">Current mode: enforcing</code> is returned when SELinux is running in enforcing mode. <code class="computeroutput">Policy from config file: targeted</code> is returned when the SELinux targeted policy is used.
-		</div><div class="section" title="5.4.1. Enabling SELinux" id="sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Enabling_SELinux"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.4.1. Enabling SELinux</h3></div></div></div><div class="para">
-				On systems with SELinux disabled, the <code class="computeroutput">SELINUX=disabled</code> option is configured in <code class="filename">/etc/selinux/config</code>:
+		</div><div class="section" title="5.4.1. Habilitando SELinux" id="sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Enabling_SELinux"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.4.1. Habilitando SELinux</h3></div></div></div><div class="para">
+				En sistemas con SELinux deshabilitado, la opción <code class="computeroutput">SELINUX=disabled</code> se configura en <code class="filename">/etc/selinux/config</code>:
 			</div><pre class="screen"># This file controls the state of SELinux on the system.
 # SELINUX= can take one of these three values:
 #       enforcing - SELinux security policy is enforced.
@@ -752,23 +752,23 @@ SELINUX=disabled
 SELINUXTYPE=targeted
 
 </pre><div class="para">
-				Also, the <code class="command">getenforce</code> command returns <code class="computeroutput">Disabled</code>:
+				También, el comando <code class="command">getenforce</code> devuelve <code class="computeroutput">Disabled</code>:
 			</div><pre class="screen">$ /usr/sbin/getenforce
 Disabled
 
 </pre><div class="para">
-				To enable SELinux:
+				Para habilitar SELinux:
 			</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
-						Use the <code class="command">rpm -qa | grep selinux</code>, <code class="command">rpm -q policycoreutils</code>, and <code class="command">rpm -qa | grep setroubleshoot</code> commands to confirm that the SELinux packages are installed. This guide assumes the following packages are installed: <span class="package">selinux-policy-targeted</span>, <span class="package">selinux-policy</span>, <span class="package">libselinux</span>, <span class="package">libselinux-python</span>, <span class="package">libselinux-utils</span>, <span class="package">policycoreutils</span>, <span class="package">setroubleshoot</span>, <span class="package">setroubleshoot-server</span>, <span class="package">setroubleshoot-plugins</span>. If these packages are not installed, as the Linux root user, install them via the <code class="command">yum install <em class="replaceable"><code>package-name</code></em></code> command. The following packages are optional: <span class="package">policycoreu
 tils-gui</span>, <span class="package">setroubleshoot</span>, <span class="package">selinux-policy-devel</span>, and <span class="package">mcstrans</span>.
+						Use los comandos <code class="command">rpm -qa | grep selinux</code>, <code class="command">rpm -q policycoreutils</code> y <code class="command">rpm -qa | grep setroubleshoot</code> para confirmar que los paquetes de SELinux están instalados. esta guía asume que los siguientes paquetes están instalados: <span class="package">selinux-policy-targeted</span>, <span class="package">selinux-policy</span>, <span class="package">libselinux</span>, <span class="package">libselinux-python</span>, <span class="package">libselinux-utils</span>, <span class="package">policycoreutils</span>, <span class="package">setroubleshoot</span>, <span class="package">setroubleshoot-server</span>, <span class="package">setroubleshoot-plugins</span>. Si estos paquetes no están instalados, como usuario root de Linux, debe instalarlos con el comando <code class="command">yum install <em class="replaceable"><code>nombre-de-paquete</code></em></code>. Los siguientes paquetes son opcionales: <
 span class="package">policycoreutils-gui</span>, <span class="package">setroubleshoot</span>, <span class="package">selinux-policy-devel</span> y <span class="package">mcstrans</span>.
 					</div><div class="para">
-						After installing the <span class="package">setroubleshoot-server</span> package, use the <code class="command">/sbin/chkconfig --list setroubleshoot</code> command to confirm that <code class="systemitem">setroubleshootd</code> starts when the system is running in runlevel<sup>[<a id="id556305" href="#ftn.id556305" class="footnote">10</a>]</sup> 3, 4, and 5:
+						After installing the <span class="package">setroubleshoot-server</span> package, use the <code class="command">/sbin/chkconfig --list setroubleshoot</code> command to confirm that <code class="systemitem">setroubleshootd</code> starts when the system is running in runlevel<sup>[<a id="id852675" href="#ftn.id852675" class="footnote">10</a>]</sup> 3, 4, and 5:
 					</div><pre class="screen">$ /sbin/chkconfig --list setroubleshoot
 setroubleshoot  0:off   1:off   2:off   3:on    4:on    5:on    6:off
 
 </pre><div class="para">
-						If the output differs, as the Linux root user, run the <code class="command">/sbin/chkconfig --levels 345 setroubleshoot on</code> command. This makes <code class="systemitem">setroubleshootd</code> automatically start when the system is in runlevel 3, 4, and 5.
+						Si la salida difiere, como usuario root de Linux ejecute el comando <code class="command">/sbin/chkconfig --levels 345 setroubleshoot on</code>. Esto hace que <code class="systemitem">setroubleshootd</code> se inicie automáticamente cuando el sistema esté en los niveles de ejecución 3, 4 y 5.
 					</div></li><li class="listitem"><div class="para">
-						Before SELinux is enabled, each file on the file system must be labeled with an SELinux context. Before this happens, confined domains may be denied access, preventing your system from booting correctly. To prevent this, configure <code class="computeroutput">SELINUX=permissive</code> in <code class="filename">/etc/selinux/config</code>:
+						Antes de activar SELinux, cada archivo en el sistema de archivo debe ser etiquetado con un contexto de SELinux. Antes que esto ocurra, los dominios confinados pueden tener el acceso denegado, impidiendo de que su sistema se inicie correctamente. Para prevenir esto, configure <code class="computeroutput">SELINUX=permissive</code> en <code class="filename">/etc/selinux/config</code>:
 					</div><pre class="screen"># This file controls the state of SELinux on the system.
 # SELINUX= can take one of these three values:
 #       enforcing - SELinux security policy is enforced.
@@ -781,18 +781,18 @@ SELINUX=permissive
 SELINUXTYPE=targeted
 
 </pre></li><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">reboot</code> command to restart the system. During the next boot, file systems are labeled. The label process labels all files with an SELinux context:
+						Como usuario root de Linux, corra el comando <code class="command">reboot</code> para reiniciar el sistema. Durante el siguiente arranque, los sistemas de archivo son etiquetados. El proceso etiqueta todos los archivos con un contexto de SELinux:
 					</div><pre class="screen">*** Warning -- SELinux targeted policy relabel is required.
 *** Relabeling could take a very long time, depending on file
 *** system size and speed of hard drives.
 ****
 
 </pre><div class="para">
-						Each <code class="computeroutput">*</code> character on the bottom line represents 1000 files that have been labeled. In the above example, four <code class="computeroutput">*</code> characters represent 4000 files have been labeled. The time it takes to label all files depends upon the number of files on the system, and the speed of the hard disk drives. On modern systems, this process can take as little as 10 minutes.
+						Cada carácter <code class="computeroutput">*</code> en la línea de abajo representa 1000 archivos que han sido etiquetados. En el ejemplo de arriba, cuatro caracteres <code class="computeroutput">*</code> representan 4000 archivos etiquetados. El tiempo que toma reetiquetar todos los archivos depende del número de archivos del sistema, y la velocidad de los discos rígidos. En sistemas modernos, este proceso puede tomar 10 minutos.
 					</div></li><li class="listitem"><div class="para">
-						In permissive mode, SELinux policy is not enforced, but denials are still logged for actions that would have been denied if running in enforcing mode. Before changing to enforcing mode, as the Linux root user, run the <code class="command">grep "SELinux is preventing" /var/log/messages</code> command as the Linux root user to confirm that SELinux did not deny actions during the last boot. If SELinux did not deny actions during the last boot, this command does not return any output. Refer to <a class="xref" href="#chap-Security-Enhanced_Linux-Troubleshooting" title="Capítulo 7. Troubleshooting">Capítulo 7, <i>Troubleshooting</i></a> for troubleshooting information if SELinux denied access during boot.
+						In permissive mode, SELinux policy is not enforced, but denials are still logged for actions that would have been denied if running in enforcing mode. Before changing to enforcing mode, as the Linux root user, run the <code class="command">grep "SELinux is preventing" /var/log/messages</code> command as the Linux root user to confirm that SELinux did not deny actions during the last boot. If SELinux did not deny actions during the last boot, this command does not return any output. Refer to <a class="xref" href="#chap-Security-Enhanced_Linux-Troubleshooting" title="Capítulo 7. Solución a Problemas">Capítulo 7, <i>Solución a Problemas</i></a> for troubleshooting information if SELinux denied access during boot.
 					</div></li><li class="listitem"><div class="para">
-						If there were no denial messages in <code class="filename">/var/log/messages</code>, configure <code class="computeroutput">SELINUX=enforcing</code> in <code class="filename">/etc/selinux/config</code>:
+						Si no hay mensajes de negación en <code class="filename">/var/log/messages</code>, configure <code class="computeroutput">SELINUX=enforcing</code> en <code class="filename">/etc/selinux/config</code>:
 					</div><pre class="screen"># This file controls the state of SELinux on the system.
 # SELINUX= can take one of these three values:
 #       enforcing - SELinux security policy is enforced.
@@ -805,12 +805,12 @@ SELINUX=enforcing
 SELINUXTYPE=targeted
 
 </pre></li><li class="listitem"><div class="para">
-						Reboot your system. After reboot, confirm that the <code class="command">getenforce</code> command returns <code class="computeroutput">Enforcing</code>:
+						Reinicie su sistema. Después de reiniciar, confirme que <code class="command">getenforce</code> devuelve <code class="computeroutput">Enforcing</code>:
 					</div><pre class="screen">$ /usr/sbin/getenforce
 Enforcing
 
 </pre></li><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">/usr/sbin/semanage login -l</code> command to view the mapping between SELinux and Linux users. The output should be as follows:
+						Como usuario root de Linux, corra el comando <code class="command">/usr/sbin/semanage login -l</code> para ver el mapeo entre usuarios de SELinux y de Linux. La salida debe ser como la siguiente:
 					</div><pre class="screen">Login Name                SELinux User              MLS/MCS Range
 
 __default__               unconfined_u              s0-s0:c0.c1023
@@ -818,7 +818,7 @@ root                      unconfined_u              s0-s0:c0.c1023
 system_u                  system_u                  s0-s0:c0.c1023
 
 </pre></li></ol></div><div class="para">
-				If this is not the case, run the following commands as the Linux root user to fix the user mappings. It is safe to ignore the <code class="computeroutput">SELinux-user<em class="replaceable"><code> username</code></em> is already defined</code> warnings if they occur, where <em class="replaceable"><code>username</code></em> can be <code class="computeroutput">unconfined_u</code>, <code class="computeroutput">guest_u</code>, or <code class="computeroutput">xguest_u</code>:
+				Si éste no es el caso, ejecute los siguientes comandos como usuario root de Linux para corregir los mapeos de usuario. Es seguro ignorar los mensajes <code class="computeroutput">El usuario SELinux <em class="replaceable"><code>nombre-de-usuario</code></em> ya está definido</code> si es que aparecen, donde <em class="replaceable"><code>nombre-de-usuario</code></em> puede ser <code class="computeroutput">unconfined_u</code>, <code class="computeroutput">guest_u</code>, o <code class="computeroutput">xguest_u</code>:
 			</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
 						
 <pre class="screen">/usr/sbin/semanage user -a -S targeted -P user -R "unconfined_r system_r" -r s0-s0:c0.c1023 unconfined_u
@@ -850,9 +850,9 @@ system_u                  system_u                  s0-s0:c0.c1023
 </pre>
 
 					</div></li></ol></div><div class="important"><h2>Importante</h2><div class="para">
-					When systems run with SELinux in permissive or disabled mode, users have permission to label files incorrectly. Also, files created while SELinux is disabled are not labeled. This causes problems when changing to enforcing mode. To prevent incorrectly labeled and unlabeled files from causing problems, file systems are automatically relabeled when changing from disabled mode to permissive or enforcing mode.
-				</div></div></div><div class="section" title="5.4.2. Disabling SELinux" id="sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.4.2. Disabling SELinux</h3></div></div></div><div class="para">
-				To disable SELinux, configure <code class="option">SELINUX=disabled</code> in <code class="filename">/etc/selinux/config</code>:
+					Cuando los sistemas corren con SELinux en modo permisivo o deshabilitado, los usuarios tiene permiso para etiquetar los archivos incorrectamente. También, los archivos creados con SELinux deshabilitado no son etiquetados. Esto causa problemas cuando se cambia a modo obediente. Para prevenir el etiquetado incorrecto o la falta de etiquetado, los sistemas de archivos son automáticamente reetiquetados cuando se cambie desde el modo deshabilitado al modo permisivo u obediente.
+				</div></div></div><div class="section" title="5.4.2. Deshabilitando SELinux" id="sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.4.2. Deshabilitando SELinux</h3></div></div></div><div class="para">
+				Para deshabilitar SELinux, configure <code class="option">SELINUX=disabled</code> en <code class="filename">/etc/selinux/config</code>:
 			</div><pre class="screen"># This file controls the state of SELinux on the system.
 # SELINUX= can take one of these three values:
 #       enforcing - SELinux security policy is enforced.
@@ -865,26 +865,26 @@ SELINUX=disabled
 SELINUXTYPE=targeted
 
 </pre><div class="para">
-				Reboot your system. After reboot, confirm that the <code class="command">getenforce</code> command returns <code class="computeroutput">Disabled</code>:
+				Reinicie su sistema. Después de reiniciar, confirme que <code class="command">getenforce</code> devuelve <code class="computeroutput">Disabled</code>:
 			</div><pre class="screen">$ /usr/sbin/getenforce
 Disabled
 
-</pre></div></div><div class="section" title="5.5. SELinux Modes" id="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.5. SELinux Modes</h2></div></div></div><div class="para">
-			SELinux has three modes:
+</pre></div></div><div class="section" title="5.5. Modos de SELinux" id="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.5. Modos de SELinux</h2></div></div></div><div class="para">
+			SELinux tiene tres modos:
 		</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-					Enforcing: SELinux policy is enforced. SELinux denies access based on SELinux policy rules.
+					Obligatorio: la política de SELinux es obligatoria. SELinux niega el acceso basado en las reglas de políticas de SELinux.
 				</div></li><li class="listitem"><div class="para">
-					Permissive: SELinux policy is not enforced. SELinux does not deny access, but denials are logged for actions that would have been denied if running in enforcing mode.
+					Permisivo: la política de SELinux no es obligatoria. SELinux no niega el acceso, pero se guardan las negaciones para acciones que hubieran sido negadas si el modo obligatorio estaba activado.
 				</div></li><li class="listitem"><div class="para">
-					Disabled: SELinux is disabled. Only DAC rules are used.
+					Deshabilitado: SELinux está deshabilitado. Sólo se usan las reglas DAC.
 				</div></li></ul></div><div class="para">
-			Use the <code class="command">/usr/sbin/setenforce</code> command to change between enforcing and permissive mode. Changes made with <code class="command">/usr/sbin/setenforce</code> do not persist across reboots. To change to enforcing mode, as the Linux root user, run the <code class="command">/usr/sbin/setenforce 1</code> command. To change to permissive mode, run the <code class="command">/usr/sbin/setenforce 0</code> command. Use the <code class="command">/usr/sbin/getenforce</code> command to view the current SELinux mode.
+			Use el comando <code class="command">/usr/sbin/setenforce</code> para cambiar entre los modos obediente y permisivo. Los cambios hechos con <code class="command">/usr/sbin/setenforce</code> no sobreviven a una reiniciada. Para cambiar a modo obediente, como usuario root de Linux, ejecute el comando <code class="command">/usr/sbin/setenforce 1</code>. Para cambiar a modo permisivo, ejecute el comando <code class="command">/usr/sbin/setenforce 0</code>. Use el comando <code class="command">/usr/sbin/getenforce</code> para ver el modo de SELinux actual.
 		</div><div class="para">
-			Persistent mode changes are covered in <a class="xref" href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux" title="5.4. Enabling and Disabling SELinux">Sección 5.4, “Enabling and Disabling SELinux”</a>.
-		</div></div><div class="section" title="5.6. Booleans" id="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.6. Booleans</h2></div></div></div><div class="para">
-			Booleans allow parts of SELinux policy to be changed at runtime, without any knowledge of SELinux policy writing. This allows changes, such as allowing services access to NFS file systems, without reloading or recompiling SELinux policy.
-		</div><div class="section" title="5.6.1. Listing Booleans" id="sect-Security-Enhanced_Linux-Booleans-Listing_Booleans"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.6.1. Listing Booleans</h3></div></div></div><div class="para">
-				For a list of Booleans, an explanation of what each one is, and whether they are on or off, run the <code class="command">semanage boolean -l</code> command as the Linux root user. The following example does not list all Booleans:
+			Persistent mode changes are covered in <a class="xref" href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux" title="5.4. Habilitando y Deshabilitando SELinux">Sección 5.4, “Habilitando y Deshabilitando SELinux”</a>.
+		</div></div><div class="section" title="5.6. Booleanos" id="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.6. Booleanos</h2></div></div></div><div class="para">
+			Los booleanos permiten cambiar partes de la política de SELinux en tiempo de ejecución, sin ningún conocimiento sobre la escritura de políticas de SELinux. Esto permite cambios, como permitir el acceso de servicios a sistemas de archivo NFS, sin recargar o recompilar la política de SELinux.
+		</div><div class="section" title="5.6.1. Listando los Booleanos" id="sect-Security-Enhanced_Linux-Booleans-Listing_Booleans"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.6.1. Listando los Booleanos</h3></div></div></div><div class="para">
+				Para una lista de los Booleanos, una explicación de lo que son y de si están activos o inactivos, ejecute el comando <code class="command">semanage boolean -l</code> como usuario root de Linux. El siguiente ejemplo no lista todos los Booleanos:
 			</div><pre class="screen"># /usr/sbin/semanage boolean -l
 SELinux boolean                          Description
 
@@ -893,137 +893,137 @@ xen_use_nfs                    -&gt; off   Allow xen to manage nfs files
 xguest_connect_network         -&gt; on    Allow xguest to configure Network Manager
 
 </pre><div class="para">
-				The <code class="computeroutput">SELinux boolean</code> column lists Boolean names. The <code class="computeroutput">Description</code> column lists whether the Booleans are on or off, and what they do.
+				La columna <code class="computeroutput">SELinux boolean</code> lista los nombres de Booleanos. La columna <code class="computeroutput">Description</code> lista si el booleano está activo (on) o inactivo (off) y lo que hacen.
 			</div><div class="para">
-				In the following example, the <code class="computeroutput">ftp_home_dir</code> Boolean is off, preventing the FTP daemon (<code class="systemitem">vsftpd</code>) from reading and writing to files in user home directories:
+				En el siguiente ejemplo, el Booleano <code class="computeroutput">ftp_home_dir</code> está apagado, impidiendo al demonio FTP (<code class="systemitem">vsftpd</code>) la lectura y escritura de archivos en los directorios de inicio de los usuarios:
 			</div><pre class="screen">ftp_home_dir                   -&gt; off   Allow ftp to read and write files in the user home directories
 
 </pre><div class="para">
-				The <code class="command">getsebool -a</code> command lists Booleans, whether they are on or off, but does not give a description of each one. The following example does not list all Booleans:
+				El comando <code class="command">getsebool -a</code> lista los Booleanos, ya sea que estén activos o inactivos, pero no da una descripción de cada uno. El siguiente ejemplo no lista todos los booleanos:
 			</div><pre class="screen">$ /usr/sbin/getsebool -a
 allow_console_login --&gt; off
 allow_cvs_read_shadow --&gt; off
 allow_daemons_dump_core --&gt; on
 
 </pre><div class="para">
-				Run the <code class="command">getsebool <em class="replaceable"><code>boolean-name</code></em></code> command to only list the status of the <em class="replaceable"><code>boolean-name</code></em> Boolean:
+				Ejecute el comando <code class="command">getsebool <em class="replaceable"><code>nombre-de-booleano</code></em></code> para listar solamente el estado del booleano <em class="replaceable"><code>nombre-de-booleano</code></em>:
 			</div><pre class="screen">$ /usr/sbin/getsebool allow_console_login
 allow_console_login --&gt; off
 
 </pre><div class="para">
-				Use a space-separated list to list multiple Booleans:
+				Una lista separada por espacio para listar los Booleanos múltiples:
 			</div><pre class="screen">$ getsebool allow_console_login allow_cvs_read_shadow allow_daemons_dump_core
 allow_console_login --&gt; off
 allow_cvs_read_shadow --&gt; off
 allow_daemons_dump_core --&gt; on
 
-</pre></div><div class="section" title="5.6.2. Configuring Booleans" id="sect-Security-Enhanced_Linux-Booleans-Configuring_Booleans"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.6.2. Configuring Booleans</h3></div></div></div><div class="para">
-				The <code class="command">setsebool <em class="replaceable"><code>boolean-name</code></em> <em class="replaceable"><code>x</code></em></code> command turns Booleans on or off, where <em class="replaceable"><code>boolean-name</code></em> is a Boolean name, and <em class="replaceable"><code>x</code></em> is either <code class="option">on</code> to turn the Boolean on, or <code class="option">off</code> to turn it off.
+</pre></div><div class="section" title="5.6.2. Configurando los Booleanos" id="sect-Security-Enhanced_Linux-Booleans-Configuring_Booleans"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.6.2. Configurando los Booleanos</h3></div></div></div><div class="para">
+				El comando <code class="command">setsebool <em class="replaceable"><code>nombre-de-booleano</code></em> <em class="replaceable"><code>x</code></em></code> activa o desactiva Booleanos, donde <em class="replaceable"><code>nombre-de-booleano</code></em> es un nombre de Booleano, y <em class="replaceable"><code>x</code></em> es <code class="option">on</code> para activar, u <code class="option">off</code> para desactivar.
 			</div><div class="para">
-				The following example demonstrates configuring the <code class="computeroutput">httpd_can_network_connect_db</code> Boolean:
+				El siguiente ejemplo muestra la configuración de Booleano <code class="computeroutput">httpd_can_network_connect_db</code>:
 			</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
-						By default, the <code class="computeroutput">httpd_can_network_connect_db</code> Boolean is off, preventing Apache HTTP Server scripts and modules from connecting to database servers:
+						Por defecto, el booleano <code class="computeroutput">httpd_can_network_connect_db</code> está apagado, impidiendo a los scripts y módulos del Servidor HTTP Apache conectarse a servidores de bases de datos:
 					</div><pre class="screen">$ /usr/sbin/getsebool httpd_can_network_connect_db
 httpd_can_network_connect_db --&gt; off
 
 </pre></li><li class="listitem"><div class="para">
-						To temporarily enable Apache HTTP Server scripts and modules to connect to database servers, run the <code class="command">setsebool httpd_can_network_connect_db on</code> command as the Linux root user.
+						Para permitir temporalmente a los scripts y módulos del Servidor HTTP Apache conectarse a servidores de bases de datos, ejecute el comando <code class="command">setsebool httpd_can_network_connect_db on</code> como usuario root de Linux.
 					</div></li><li class="listitem"><div class="para">
-						Use the <code class="command">getsebool httpd_can_network_connect_db</code> command to verify the Boolean is turned on:
+						Use el comando <code class="command">getsebool httpd_can_network_connect_db</code> para verificar que el Booleano está activado:
 					</div><pre class="screen">$ /usr/sbin/getsebool httpd_can_network_connect_db
 httpd_can_network_connect_db --&gt; on
 
 </pre><div class="para">
-						This allows Apache HTTP Server scripts and modules to connect to database servers.
+						Esto permite a los scripts y módulos del Servidor HTTP Apache conectarse a servidores de bases de datos.
 					</div></li><li class="listitem"><div class="para">
-						This change is not persistent across reboots. To make changes persistent across reboots, run the <code class="command">setsebool -P <em class="replaceable"><code>boolean-name</code></em> on</code> command as the Linux root user:
+						Este cambio no es persistente entre reinicios. Para hacer los cambios persistentes, corra el comando <code class="command">setsebool -P <em class="replaceable"><code>boolean-name</code></em> on</code> como usuario root de Linux:
 					</div><pre class="screen"># /usr/sbin/setsebool -P httpd_can_network_connect_db on
 
 </pre></li><li class="listitem"><div class="para">
-						To temporarily revert to the default behavior, as the Linux root user, run the <code class="command">setsebool httpd_can_network_connect_db off</code> command. For changes that persist across reboots, run the <code class="command">setsebool -P httpd_can_network_connect_db off</code> command.
-					</div></li></ol></div></div><div class="section" title="5.6.3. Booleans for NFS and CIFS" id="sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.6.3. Booleans for NFS and CIFS</h3></div></div></div><div class="para">
-				By default, NFS mounts on the client side are labeled with a default context defined by policy for NFS file systems. In common policies, this default context uses the <code class="computeroutput">nfs_t</code> type. Also, by default, Samba shares mounted on the client side are labeled with a default context defined by policy. In common policies, this default context uses the <code class="computeroutput">cifs_t</code> type.
+						Para revertir temporalmente el comportamiento por defecto, como usuario root de Linux, corra el comando <code class="command">setsebool httpd_can_network_connect_db off</code>. Para que los cambios sean persistentes entre reiniciadas, ejecute el comando <code class="command">setsebool -P httpd_can_network_connect_db off</code>.
+					</div></li></ol></div></div><div class="section" title="5.6.3. Booleanos para NFS y CIFS" id="sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.6.3. Booleanos para NFS y CIFS</h3></div></div></div><div class="para">
+				Por defecto, los montajes NFS en el lado del cliente se etiquetan con el contexto predeterminado definido por la política para sistemas de archivos NFS. En políticas comúnes, este contexto predeterminado usa el tipo <code class="computeroutput">nfs_t</code>. También, por defecto, los compartidos de Samba en el lado del cliente se etiquetan con el contexto predeterminado definido por la política. En políticas comúnes, este contexto predeterminado usa el tipo <code class="computeroutput">cifs_t</code>.
 			</div><div class="para">
-				Depending on policy configuration, services may not be able to read files labeled with the <code class="computeroutput">nfs_t</code> or <code class="computeroutput">cifs_t</code> types. This may prevent file systems labeled with these types from being mounted and then read or exported by other services. Booleans can be turned on or off to control which services are allowed to access the <code class="computeroutput">nfs_t</code> and <code class="computeroutput">cifs_t</code> types.
+				Dependiendo en la configuración de la política, los servicios pueden tener bloqueado la lectura a archivos con la etiqueta de los tipos <code class="computeroutput">nfs_t</code> o <code class="computeroutput">cifs_t</code>. Esto puede prevenir que los sistemas de archivo etiquetados con estas etiquetas se monten y sean leídos o exportados por otros servicios. Hay Booleanos que se pueden poner en 1 o 0 para controlar qué servicios pueden acceder los tipos <code class="computeroutput">nfs_t</code> y <code class="computeroutput">cifs_t</code>.
 			</div><div class="para">
-				The <code class="command">setsebool</code> and <code class="command">semanage</code> commands must be run as the Linux root user. The <code class="command">setsebool -P</code> command makes persistent changes. Do not use the <code class="option">-P</code> option if you do not want changes to persist across reboots:
-			</div><div class="formalpara"><h5 class="formalpara">Apache HTTP Server</h5>
-					To allow access to NFS file systems (files labeled with the <code class="computeroutput">nfs_t</code> type):
+				Los comandos <code class="command">setsebool</code> y <code class="command">semanage</code> se deben ejecutar como usuario root de Linux. El comando <code class="command">setsebool -P</code> hace persistentes a los cambios. No use la opción <code class="option">-P</code> si no quiere que los cambios persistan entre reiniciadas:
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Booleans_for_NFS_and_CIFS-Apache_HTTP_Server"><h5 class="formalpara">Servidor HTTP Apache</h5>
+					Para permitir el acceso a sistemas de archivo NFS (archivos etiquetados con el tipo <code class="computeroutput">nfs_t</code>):
 				</div><div class="para">
 				<code class="command">/usr/sbin/setsebool -P httpd_use_nfs on</code>
 			</div><div class="para">
-				To allow access to Samba file systems (files labeled with the <code class="computeroutput">cifs_t</code> type):
+				Para permitir el acceso a sistemas de archivos SAMBA (archivos etiquetados con el tipo <code class="computeroutput">cifs_t</code>):
 			</div><div class="para">
 				<code class="command">/usr/sbin/setsebool -P httpd_use_cifs on</code>
-			</div><div class="formalpara"><h5 class="formalpara">Samba</h5>
-					To export NFS file systems:
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Booleans_for_NFS_and_CIFS-Samba"><h5 class="formalpara">Samba</h5>
+					Para exportar sistemas de archivo NFS:
 				</div><div class="para">
 				<code class="command">/usr/sbin/setsebool -P samba_share_nfs on</code>
-			</div><div class="formalpara"><h5 class="formalpara">FTP (<code class="systemitem">vsftpd</code>)</h5>
-					To allow access to NFS file systems:
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Booleans_for_NFS_and_CIFS-FTP_vsftpd"><h5 class="formalpara">FTP (<code class="systemitem">vsftpd</code>)</h5>
+					Para permitir el acceso a sistemas de archivo NFS:
 				</div><div class="para">
 				<code class="command">/usr/sbin/setsebool -P allow_ftpd_use_nfs on</code>
 			</div><div class="para">
-				To allow access to Samba file systems:
+				Para permitir el acceso a sistemas de archivo Samba:
 			</div><div class="para">
 				<code class="command">/usr/sbin/setsebool -P allow_ftpd_use_cifs on</code>
-			</div><div class="formalpara"><h5 class="formalpara">Other Services</h5>
-					For a list of NFS related Booleans for other services:
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Booleans_for_NFS_and_CIFS-Other_Services"><h5 class="formalpara">Otros Servicios</h5>
+					Para una lista de los Booleanos relacionados con NFS para otros servicios:
 				</div><div class="para">
 				<code class="command">/usr/sbin/semanage boolean -l | grep nfs</code>
 			</div><div class="para">
-				For a list of Samba related Booleans for other services:
+				Para una lista de los Booleanos relacionados con SAMBA para otros servicios:
 			</div><div class="para">
 				<code class="command">/usr/sbin/semanage boolean -l | grep cifs</code>
 			</div><div class="note"><h2>Nota</h2><div class="para">
-					These Booleans exist in SELinux policy as shipped with Fedora 11. They may not exist in policy shipped with other versions of Fedora or other operating systems.
-				</div></div></div></div><div class="section" title="5.7. SELinux Contexts - Labeling Files" id="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.7. SELinux Contexts - Labeling Files</h2></div></div></div><div class="para">
-			On systems running SELinux, all processes and files are labeled with a label that contains security-relevant information. This information is called the SELinux context. For files, this is viewed using the <code class="command">ls -Z</code> command:
+					Estos Booleanos existen en la política de SELinux tal cual fueron puestos en Fedora 11. No pu eden existir en la política puesta en otras versiones de Fedora o de otros sistemas operativos.
+				</div></div></div></div><div class="section" title="5.7. Contextos de SELinux - Etiquetado de Archivos" id="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.7. Contextos de SELinux - Etiquetado de Archivos</h2></div></div></div><div class="para">
+			En sistemas que corren SELinux, todos los procesos y archivos son etiquetados con una etiqueta que contiene información de seguridad relevante. Esta información se llama contexto de SELinux. Para archivos, esto se ve usando el comando <code class="command">ls -Z</code>:
 		</div><pre class="screen">$ ls -Z file1
 -rw-rw-r--  user1 group1 unconfined_u:object_r:user_home_t:s0 file1
 
 </pre><div class="para">
-			In this example, SELinux provides a user (<code class="computeroutput">unconfined_u</code>), a role (<code class="computeroutput">object_r</code>), a type (<code class="computeroutput">user_home_t</code>), and a level (<code class="computeroutput">s0</code>). This information is used to make access control decisions. On DAC systems, access is controlled based on Linux user and group IDs. SELinux policy rules are checked after DAC rules. SELinux policy rules are not used if DAC rules deny access first.
+			En este ejemplo, SELinux provee un usuario (<code class="computeroutput">unconfined_u</code>), un rol (<code class="computeroutput">object_r</code>), un tipo (<code class="computeroutput">user_home_t</code>) y un nivel (<code class="computeroutput">s0</code>). Esta información se usa para tomar decisiones sobre el control de acceso. En sistemas DAC, el control de acceso se basa en los IDs de usuario y grupo de Linux. Las reglas de la política de SELinux se chequean después de las reglas DAC. Las reglas de la política de SELinux no se usan si las reglas DAC niegan el acceso antes.
 		</div><div class="para">
-			There are multiple commands for managing the SELinux context for files, such as <code class="command">chcon</code>, <code class="command">semanage fcontext</code>, and <code class="command">restorecon</code>.
-		</div><div class="section" title="5.7.1. Temporary Changes: chcon" id="sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Temporary_Changes_chcon"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.7.1. Temporary Changes: chcon</h3></div></div></div><div class="para">
-				The <code class="command">chcon</code> command changes the SELinux context for files. These changes do not survive a file system relabel, or the <code class="command">/sbin/restorecon</code> command. SELinux policy controls whether users are able to modify the SELinux context for any given file. When using <code class="command">chcon</code>, users provide all or part of the SELinux context to change. An incorrect file type is a common cause of SELinux denying access.
-			</div><div class="formalpara"><h5 class="formalpara">Quick Reference</h5>
+			Hay muchos comandos para la administración del contexto de archivos de SELinux, como por ejemplo <code class="command">chcon</code>, <code class="command">semanage fcontext</code>, y <code class="command">restorecon</code>.
+		</div><div class="section" title="5.7.1. Cambios Temporales: chcon" id="sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Temporary_Changes_chcon"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.7.1. Cambios Temporales: chcon</h3></div></div></div><div class="para">
+				El comando <code class="command">chcon</code> cambia el contexto SELinux de los archivos. Estos cambios no sobreviven un reetiquetado del sistema de archivo, o el comando <code class="command">/sbin/restorecon</code>. La política de SELinux controla si los usuarios pueden modificar el contexto SELinux de algún archivo. Cuando se usa <code class="command">chcon</code>, los usuarios proveen toda o parte del contexto SELinux a cambiar. Un tipo de archivo incorrecto es una causa común de negación de acceso de SELinux.
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Temporary_Changes_chcon-Quick_Reference"><h5 class="formalpara">Referencia Rápida</h5>
 					<div class="itemizedlist"><ul><li class="listitem"><div class="para">
-								Run the <code class="command">chcon -t <em class="replaceable"><code>type</code></em> <em class="replaceable"><code>file-name</code></em></code> command to change the file type, where <em class="replaceable"><code>type</code></em> is a type, such as <code class="computeroutput">httpd_sys_content_t</code>, and <em class="replaceable"><code>file-name</code></em> is a file or directory name.
+								Ejecute el comando <code class="command">chcon -t <em class="replaceable"><code>tipo</code></em> <em class="replaceable"><code>nombre-de-archivo</code></em></code> para cambiar el tipo de archivo, donde <em class="replaceable"><code>tipo</code></em> es el tipo, por ejemplo <code class="computeroutput">httpd_sys_content_t</code>, y <em class="replaceable"><code>nombre-de-archivo</code></em> es un nombre de archivo o de directorio.
 							</div></li><li class="listitem"><div class="para">
-								Run the <code class="command">chcon -R -t <em class="replaceable"><code>type</code></em> <em class="replaceable"><code>directory-name</code></em></code> command to change the type of the directory and its contents, where <em class="replaceable"><code>type</code></em> is a type, such as <code class="computeroutput">httpd_sys_content_t</code>, and <em class="replaceable"><code>directory-name</code></em> is a directory name.
+								Ejecute el comando <code class="command">chcon -R -t <em class="replaceable"><code>tipo</code></em> <em class="replaceable"><code>nombre-de-directorio</code></em></code> para cambiar el tipo de un directorio y su contenido, donde <em class="replaceable"><code>tipo</code></em> es el tipo, por ejemplo <code class="computeroutput">httpd_sys_content_t</code>, y <em class="replaceable"><code>nombre-de-directorio</code></em> es un nombre de directorio.
 							</div></li></ul></div>
 
-				</div><div class="formalpara"><h5 class="formalpara">Changing a File's or Directory's Type</h5>
-					The following example demonstrates changing the type, and no other attributes of the SELinux context:
+				</div><div class="formalpara" id="form-Security-Enhanced_Linux-Temporary_Changes_chcon-Changing_a_Files_or_Directorys_Type"><h5 class="formalpara">Cambiando el Tipo de un Archivo o de un Directorio</h5>
+					El siguiente ejemplo muestra el cambio de tipo solamente en el contexto de SELinux:
 				</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
-						Run the <code class="command">cd</code> command without arguments to change into your home directory.
+						Ejecute el comando <code class="command">cd</code> sin argumentos para cambiar a su directorio de inicio.
 					</div></li><li class="listitem"><div class="para">
-						Run the <code class="command">touch file1</code> command to create a new file. Use the <code class="command">ls -Z file1</code> command to view the SELinux context for <code class="filename">file1</code>:
+						Ejecute el comando <code class="command">touch archivo1</code> para crear un archivo nuevo. Use el comando <code class="command">ls -Z archivo1</code> para ver el contexto de SELinux del <code class="filename">archivo1</code>:
 					</div><pre class="screen">$ ls -Z file1
 -rw-rw-r--  user1 group1 unconfined_u:object_r:user_home_t:s0 file1
 
 </pre><div class="para">
-						In this example, the SELinux context for <code class="filename">file1</code> includes the SELinux <code class="computeroutput">unconfined_u</code> user, <code class="computeroutput">object_r</code> role, <code class="computeroutput">user_home_t</code> type, and the <code class="computeroutput">s0</code> level. For a description of each part of the SELinux context, refer to <a class="xref" href="#chap-Security-Enhanced_Linux-SELinux_Contexts" title="Capítulo 3. SELinux Contexts">Capítulo 3, <i>SELinux Contexts</i></a>.
+						In this example, the SELinux context for <code class="filename">file1</code> includes the SELinux <code class="computeroutput">unconfined_u</code> user, <code class="computeroutput">object_r</code> role, <code class="computeroutput">user_home_t</code> type, and the <code class="computeroutput">s0</code> level. For a description of each part of the SELinux context, refer to <a class="xref" href="#chap-Security-Enhanced_Linux-SELinux_Contexts" title="Capítulo 3. Contextos de SELinux">Capítulo 3, <i>Contextos de SELinux</i></a>.
 					</div></li><li class="listitem"><div class="para">
-						Run the <code class="command">chcon -t samba_share_t file1</code> command to change the type to <code class="computeroutput">samba_share_t</code>. The <code class="option">-t</code> option only changes the type. View the change with <code class="command">ls -Z file1</code>:
+						EJecute el comando <code class="command">chcon -t samba_share_t archivo1</code> para cambiar el tipo a <code class="computeroutput">samba_share_t</code>. La opción <code class="option">-t</code> sólo cambia el tipo. Vea el cambio con <code class="command">ls -Z archivo1</code>:
 					</div><pre class="screen">$ ls -Z file1 
 -rw-rw-r--  user1 group1 unconfined_u:object_r:samba_share_t:s0 file1
 
 </pre></li><li class="listitem"><div class="para">
-						Use the <code class="command">/sbin/restorecon -v file1</code> command to restore the SELinux context for the <code class="filename">file1</code> file. Use the <code class="option">-v</code> option to view what changes:
+						Use el comando <code class="command">/sbin/restorecon -v archivo1</code> para restaurar el contexto de SELinux del <code class="filename">archivo1</code>. Use la opción <code class="option">-v</code> para ver qué cambia:
 					</div><pre class="screen">$ /sbin/restorecon -v file1
 restorecon reset file1 context unconfined_u:object_r:samba_share_t:s0-&gt;system_u:object_r:user_home_t:s0
 
 </pre><div class="para">
-						In this example, the previous type, <code class="computeroutput">samba_share_t</code>, is restored to the correct, <code class="computeroutput">user_home_t</code> type. When using targeted policy (the default SELinux policy in Fedora 11), the <code class="command">/sbin/restorecon</code> command reads the files in the <code class="filename">/etc/selinux/targeted/contexts/files/</code> directory, to see which SELinux context files should have.
+						En este ejemplo, el tipo previo <code class="computeroutput">samba_share_t</code>, se restaura al tipo correcto <code class="computeroutput">user_home_t</code>. Cuando se usa la política destinada (la política SELinux predeterminada en Fedora 11), el comando <code class="command">/sbin/restorecon</code> lee los archivos en el directorio <code class="filename">/etc/selinux/targeted/contexts/files/</code> para ver qué contexto de SELinux deben tener los archivos.
 					</div></li></ol></div><div class="para">
-				The example in this section works the same for directories, for example, if <code class="filename">file1</code> was a directory.
-			</div><div class="formalpara"><h5 class="formalpara">Changing a Directory and its Contents Types</h5>
-					The following example demonstrates creating a new directory, and changing the directory's file type (along with its contents) to a type used by the Apache HTTP Server. The configuration in this example is used if you want Apache HTTP Server to use a different document root (instead of <code class="filename">/var/www/html/</code>):
+				El ejemplo en esta sección funciona igual para directorios, por ejemplo, si <code class="filename">archivo1</code> fuera un directorio.
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Temporary_Changes_chcon-Changing_a_Directory_and_its_Contents_Types"><h5 class="formalpara">Cambio de un Directorio y sus Tipos de Contenidos</h5>
+					El siguiente ejemplo muestra la creación de un directorio nuevo y el cambio del tipo de archivo del mismo (junto con su contenido) a un tipo usado por el Servidor HTTP Apache. La configuración en este ejemplo se usa si quiere que el Servidor HTTP Apache use una raíz de documento distinta (en vez de <code class="filename">/var/www/html/</code>):
 				</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">mkdir /web</code> command to create a new directory, and then the <code class="command">touch /web/file{1,2,3}</code> command to create 3 empty files (<code class="filename">file1</code>, <code class="filename">file2</code>, and <code class="filename">file3</code>). The <code class="filename">/web/</code> directory and files in it are labeled with the <code class="computeroutput">default_t</code> type:
+						Como usuario root de Linux, ejecute el comando <code class="command">mkdir /web</code> para crear un directorio nuevo, y luego el comando <code class="command">touch /web/archivo{1,2,3}</code> para crear 3 archivos vacíos (<code class="filename">archivo1</code>, <code class="filename">archivo2</code> y <code class="filename">archivo3</code>). El directorio <code class="filename">/web/</code> y los archivos en él son etiquetados con el tipo <code class="computeroutput">default_t</code>:
 					</div><pre class="screen"># ls -dZ /web
 drwxr-xr-x  root root unconfined_u:object_r:default_t:s0 /web
 # ls -lZ /web
@@ -1032,7 +1032,7 @@ drwxr-xr-x  root root unconfined_u:object_r:default_t:s0 /web
 -rw-r--r--  root root unconfined_u:object_r:default_t:s0 file3
 
 </pre></li><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">chcon -R -t httpd_sys_content_t /web/</code> command to change the type of the <code class="filename">/web/</code> directory (and its contents) to <code class="computeroutput">httpd_sys_content_t</code>:
+						Como usuario root de Linux, corra el comando <code class="command">chcon -R -t httpd_sys_content_t /web/</code> para cambiar el tipo del directorio <code class="filename">/web/</code> (y su contenido) a <code class="computeroutput">httpd_sys_content_t</code>:
 					</div><pre class="screen"># chcon -R -t httpd_sys_content_t /web/
 # ls -dZ /web/
 drwxr-xr-x  root root unconfined_u:object_r:httpd_sys_content_t:s0 /web/
@@ -1042,7 +1042,7 @@ drwxr-xr-x  root root unconfined_u:object_r:httpd_sys_content_t:s0 /web/
 -rw-r--r--  root root unconfined_u:object_r:httpd_sys_content_t:s0 file3
 
 </pre></li><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">/sbin/restorecon -R -v /web/</code> command to restore the default SELinux contexts:
+						Como usuario root de Linux, corra el comando <code class="command">/sbin/restorecon -R -v /web/</code> para restaurar los contextos de SELinux predeterminados:
 					</div><pre class="screen"># /sbin/restorecon -R -v /web/
 restorecon reset /web context unconfined_u:object_r:httpd_sys_content_t:s0-&gt;system_u:object_r:default_t:s0
 restorecon reset /web/file2 context unconfined_u:object_r:httpd_sys_content_t:s0-&gt;system_u:object_r:default_t:s0
@@ -1050,77 +1050,77 @@ restorecon reset /web/file3 context unconfined_u:object_r:httpd_sys_content_t:s0
 restorecon reset /web/file1 context unconfined_u:object_r:httpd_sys_content_t:s0-&gt;system_u:object_r:default_t:s0
 
 </pre></li></ol></div><div class="para">
-				Refer to the <span class="citerefentry"><span class="refentrytitle">chcon</span>(1)</span> manual page for further information about <code class="command">chcon</code>.
+				Vaya a la página del manual de <span class="citerefentry"><span class="refentrytitle">chcon</span>(1)</span> para más información sobre <code class="command">chcon</code>.
 			</div><div class="note"><h2>Nota</h2><div class="para">
-					Type Enforcement is the main permission control used in SELinux targeted policy. For the most part, SELinux users and roles can be ignored.
-				</div></div></div><div class="section" title="5.7.2. Persistent Changes: semanage fcontext" id="sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.7.2. Persistent Changes: semanage fcontext</h3></div></div></div><div class="para">
-				The <code class="command">/usr/sbin/semanage fcontext</code> command changes the SELinux context for files. When using targeted policy, changes made with this command are added to the <code class="filename">/etc/selinux/targeted/contexts/files/file_contexts</code> file if the changes are to files that exists in <code class="filename">file_contexts</code>, or are added to <code class="filename">file_contexts.local</code> for new files and directories, such as creating a <code class="filename">/web/</code> directory. <code class="command">setfiles</code>, which is used when a file system is relabeled, and <code class="command">/sbin/restorecon</code>, which restores the default SELinux contexts, read these files. This means that changes made by <code class="command">/usr/sbin/semanage fcontext</code> are persistent, even if the file system is relabeled. SELinux policy controls whether users are able to modify the SELinux context for any given file.
-			</div><div class="formalpara"><h5 class="formalpara">Quick Reference</h5>
-					To make SELinux context changes that survive a file system relabel:
+					La Obligación de Tipo es el control de permisos principal usado en la política destinada de SELinux. Para la mayor parte, los usuarios y roles de SELinux se pueden ignorar.
+				</div></div></div><div class="section" title="5.7.2. Cambios Persistentes: semanage fcontext" id="sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.7.2. Cambios Persistentes: semanage fcontext</h3></div></div></div><div class="para">
+				El comando <code class="command">/usr/sbin/semanage fcontext</code> cambia el contexto SELinux de los archivos. Cuando se usa la política destinada, los cambios hechos con este comando se agregan al archivo <code class="filename">/etc/selinux/targeted/contexts/files/file_contexts</code> si los cambios so para archivos que están en <code class="filename">file_contexts</code>, se agregan a <code class="filename">file_contexts.local</code> para archivos nuevos y directorios, como sería al crear un directorio <code class="filename">/web/</code> nuevo. <code class="command">setfiles</code>, que se usa cuando el sistema de archivo es reetiquetado, y <code class="command">/sbin/restorecon</code>, que restaura los contextos de SELinux predeterminados, leen estos archivos, Lo que significa que los cambios hechos por <code class="command">/usr/sbin/semanage fcontext</code> son persistentes, aún si el sistema de archivo es reetiquetado. La política de SELinux controla si los u
 suarios pueden modificar el contexto de SELinux para cualquier archivo dado.
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Persistent_Changes_semanage_fcontext-Quick_Reference"><h5 class="formalpara">Referencia Rápida</h5>
+					Para hacer que los cambios de contexto de SELinux sobrevivan un reetiquetado del sistema de archivo:
 				</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
-						Run the <code class="command">/usr/sbin/semanage fcontext -a <em class="replaceable"><code>options</code></em> <em class="replaceable"><code>file-name</code></em>|<em class="replaceable"><code>directory-name</code></em></code> command, remembering to use the full path to the file or directory.
+						Ejecute el comando <code class="command">/usr/sbin/semanage fcontext -a <em class="replaceable"><code>opciones</code></em> <em class="replaceable"><code>nombre-de-archivo</code></em>|<em class="replaceable"><code>nombre-de-directorio</code></em></code>, recuerde usar la dirección completa del archivo o del directorio.
 					</div></li><li class="listitem"><div class="para">
-						Run the <code class="command">/sbin/restorecon -v <em class="replaceable"><code>file-name</code></em>|<em class="replaceable"><code>directory-name</code></em></code> command to apply the context changes.
-					</div></li></ol></div><div class="formalpara"><h5 class="formalpara">Changing a File's Type</h5>
-					The following example demonstrates changing a file's type, and no other attributes of the SELinux context:
+						Ejecute el comando <code class="command">/sbin/restorecon -v <em class="replaceable"><code>nombre-de-archivo</code></em>|<em class="replaceable"><code>nombre-de-directorio</code></em></code> para aplicar los cambios de contexto.
+					</div></li></ol></div><div class="formalpara" id="form-Security-Enhanced_Linux-Persistent_Changes_semanage_fcontext-Changing_a_Files_Type"><h5 class="formalpara">Cambiando un Tipo de archivo</h5>
+					El siguiente ejemplo muestra el cambio de tipo de un archivo, sin tocar otros atributos del contexto de SELinux:
 				</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">touch /etc/file1</code> command to create a new file. By default, newly-created files in the <code class="filename">/etc/</code> directory are labeled with the <code class="computeroutput">etc_t</code> type:
+						Como usuario root de Linux, ejecute el comando <code class="command">touch /etc/archivo1</code> para crear un archivo nuevo. Por defecto, los archivos recién creados en el directorio <code class="filename">/etc/</code> se etiquetan con el tipo <code class="computeroutput">etc_t</code>:
 					</div><pre class="screen"># ls -Z /etc/file1
 -rw-r--r--  root root unconfined_u:object_r:etc_t:s0       /etc/file1
 
 </pre></li><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">/usr/sbin/semanage fcontext -a -t samba_share_t /etc/file1</code> command to change the <code class="filename">file1</code> type to <code class="computeroutput">samba_share_t</code>. The <code class="option">-a</code> option adds a new record, and the <code class="option">-t</code> option defines a type (<code class="computeroutput">samba_share_t</code>). Note: running this command does not directly change the type - <code class="filename">file1</code> is still labeled with the <code class="computeroutput">etc_t</code> type:
+						Como usuario root de Linux, ejecute el comando <code class="command">/usr/sbin/semanage fcontext -a -t samba_share_t /etc/archivo1</code> para cambiar el tipo del <code class="filename">archivo1</code> a <code class="computeroutput">samba_share_t</code>. La opción <code class="option">-a</code> agrega un registro nuevo, y la opción <code class="option">-t</code> define un tipo (<code class="computeroutput">samba_share_t</code>). Nota: al ejecutar este comando no se cambia directamente el tipo - el <code class="filename">archivo1</code> todavía es del tipo <code class="computeroutput">etc_t</code>:
 					</div><pre class="screen"># /usr/sbin/semanage fcontext -a -t samba_share_t /etc/file1
 # ls -Z /etc/file1
 -rw-r--r--  root root unconfined_u:object_r:etc_t:s0       /etc/file1
 
 </pre><div class="para">
-						The <code class="command">/usr/sbin/semanage fcontext -a -t samba_share_t /etc/file1</code> command adds the following entry to <code class="filename">/etc/selinux/targeted/contexts/files/file_contexts.local</code>:
+						El comando <code class="command">/usr/sbin/semanage fcontext -a -t samba_share_t /etc/archivo1</code> agrega la siguiente entrada a <code class="filename">/etc/selinux/targeted/contexts/files/file_contexts.local</code>:
 					</div><pre class="screen">/etc/file1    unconfined_u:object_r:samba_share_t:s0
 
 </pre></li><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">/sbin/restorecon -v /etc/file1</code> command to change the type. Since the <code class="command">semanage</code> command added an entry to <code class="filename">file.contexts.local</code> for <code class="filename">/etc/file1</code>, the <code class="command">/sbin/restorecon</code> command changes the type to <code class="computeroutput">samba_share_t</code>:
+						Como usuario root de Linux, ejecute el comando <code class="command">/sbin/restorecon -v /etc/archivo1</code> para cambiar el tipo. Dado que el comando <code class="command">semanage</code> agregó una entrada a <code class="filename">file.contexts.local</code> para <code class="filename">/etc/archivo1</code>, el comando <code class="command">/sbin/restorecon</code> cambia el tipo a <code class="computeroutput">samba_share_t</code>:
 					</div><pre class="screen"># /sbin/restorecon -v /etc/file1
 restorecon reset /etc/file1 context unconfined_u:object_r:etc_t:s0-&gt;system_u:object_r:samba_share_t:s0
 
 </pre></li><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">rm -i /etc/file1</code> command to remove <code class="filename">file1</code>.
+						Como usuario root de Linux, ejecute el comando <code class="command">rm -i /etc/archivo1</code> para borrar el <code class="filename">archivo1</code>.
 					</div></li><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">/usr/sbin/semanage fcontext -d /etc/file1</code> command to remove the context added for <code class="filename">/etc/file1</code>. When the context is removed, running <code class="command">restorecon</code> changes the type to <code class="computeroutput">etc_t</code>, rather than <code class="computeroutput">samba_share_t</code>.
-					</div></li></ol></div><div class="formalpara"><h5 class="formalpara">Changing a Directory's Type</h5>
-					The following example demonstrates creating a new directory and changing that directory's file type, to a type used by Apache HTTP Server:
+						Como usuario root de Linux, ejecute el comando <code class="command">/usr/sbin/semanage fcontext -d /etc/archivo1</code> para eliminar el contexto agregado para <code class="filename">/etc/archivo1</code>. Cuando el contexto se elimina, ejecutando <code class="command">restorecon</code> cambia el tipo a <code class="computeroutput">etc_t</code>, en vez de <code class="computeroutput">samba_share_t</code>.
+					</div></li></ol></div><div class="formalpara" id="form-Security-Enhanced_Linux-Persistent_Changes_semanage_fcontext-Changing_a_Directorys_Type"><h5 class="formalpara">Cambiando un Tipo de Directorio</h5>
+					El siguiente ejemplo muestra la creación de un directorio nuevo y el cambio del tipo de archivo del directorio a un tipo usado por el Servidor HTTP Apache:
 				</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">mkdir /web</code> command to create a new directory. This directory is labeled with the <code class="computeroutput">default_t</code> type:
+						Como usuario root de LInux, ejecute el comando <code class="command">mkdir /web</code> para crear un directorio nuevo. Este directorio se etiqueta con el tipo <code class="computeroutput">default_t</code>:
 					</div><pre class="screen"># ls -dZ /web
 drwxr-xr-x  root root unconfined_u:object_r:default_t:s0 /web
 
 </pre><div class="para">
-						The <code class="command">ls</code> <code class="option">-d</code> option makes <code class="command">ls</code> list information about a directory, rather than its contents, and the <code class="option">-Z</code> option makes <code class="command">ls</code> display the SELinux context (in this example, <code class="computeroutput">unconfined_u:object_r:default_t:s0</code>).
+						La opción <code class="option">-d</code> de <code class="command">ls</code> hace que <code class="command">ls</code> liste la información de un directorio, en vez de su contenido, y la opción <code class="option">-Z</code> hace que <code class="command">ls</code> muestre el contexto de SELinux (en este ejemplo, <code class="computeroutput">unconfined_u:object_r:default_t:s0</code>).
 					</div></li><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">/usr/sbin/semanage fcontext -a -t httpd_sys_content_t /web</code> command to change the <code class="filename">/web/</code> type to <code class="computeroutput">httpd_sys_content_t</code>. The <code class="option">-a</code> option adds a new record, and the <code class="option">-t</code> option defines a type (<code class="computeroutput">httpd_sys_content_t</code>). Note: running this command does not directly change the type - <code class="filename">/web/</code> is still labeled with the <code class="computeroutput">default_t</code> type:
+						Como usuario root de Linux, ejecute el comando <code class="command">/usr/sbin/semanage fcontext -a -t httpd_sys_content_t /web</code> para cambiar el tipo de <code class="filename">/web/</code> a <code class="computeroutput">httpd_sys_content_t</code>. La opción <code class="option">-a</code> agrega un nuevo registro, y la opción <code class="option">-t</code> define un tipo (<code class="computeroutput">httpd_sys_content_t</code>). Nota: la ejecución de este comando no cambia el tipo directamente - <code class="filename">/web/</code> todavía tiene la etiqueta de tipo <code class="computeroutput">default_t</code>:
 					</div><pre class="screen"># /usr/sbin/semanage fcontext -a -t httpd_sys_content_t /web
 # ls -dZ /web
 drwxr-xr-x  root root unconfined_u:object_r:default_t:s0   /web
 
 </pre><div class="para">
-						The <code class="command">/usr/sbin/semanage fcontext -a -t httpd_sys_content_t /web</code> command adds the following entry to <code class="command">/etc/selinux/targeted/contexts/files/file_contexts.local</code>:
+						El comando <code class="command">/usr/sbin/semanage fcontext -a -t httpd_sys_content_t /web</code> agrega la siguiente entrada a <code class="command">/etc/selinux/targeted/contexts/files/file_contexts.local</code>:
 					</div><pre class="screen">/web    unconfined_u:object_r:httpd_sys_content_t:s0
 
 </pre></li><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">/sbin/restorecon -v /web</code> command to change the type. Since the <code class="command">semanage</code> command added an entry to <code class="filename">file.contexts.local</code> for <code class="filename">/web</code>, the <code class="command">/sbin/restorecon</code> command changes the type to <code class="computeroutput">httpd_sys_content_t</code>:
+						Como usuario root de Linux, ejecute el comando <code class="command">/sbin/restorecon -v /web</code> para cambiar el tipo. Como el comando <code class="command">semanage</code> agregó una entrada a <code class="filename">file.contexts.local</code> para <code class="filename">/web</code>, el comando <code class="command">/sbin/restorecon</code> cambia el tipo a <code class="computeroutput">httpd_sys_content_t</code>:
 					</div><pre class="screen"># /sbin/restorecon -v /web
 restorecon reset /web context unconfined_u:object_r:default_t:s0-&gt;system_u:object_r:httpd_sys_content_t:s0
 
 </pre><div class="para">
-						By default, newly-created files and directories inherit the SELinux type of their parent folders. When using this example, and before removing the SELinux context added for <code class="filename">/web/</code>, files and directories created in the <code class="filename">/web/</code> directory are labeled with the <code class="computeroutput">httpd_sys_content_t</code> type.
+						Por defecto, los archivos y directorios recién creados heredan el tipo SELinux de sus carpetas padres. Cuando se usó este ejemplo, y antes de eliminar el contexto SELinux agregado para <code class="filename">/web/</code>, los archivos y directorios creados en el directorio <code class="filename">/web/</code> fueron etiquetados con el tipo <code class="computeroutput">httpd_sys_content_t</code>.
 					</div></li><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">/usr/sbin/semanage fcontext -d /web</code> command to remove the context added for <code class="filename">/web/</code>.
+						Como usuario root de Linux, ejecute el comando <code class="command">/usr/sbin/semanage fcontext -d /web</code> para borrar el contexto agregado para <code class="filename">/web/</code>.
 					</div></li><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">/sbin/restorecon -v /web</code> command to restore the default SELinux context.
-					</div></li></ol></div><div class="formalpara"><h5 class="formalpara">Changing a Directory and its Contents Types</h5>
-					The following example demonstrates creating a new directory, and changing the directory's file type (along with its contents) to a type used by Apache HTTP Server. The configuration in this example is used if you want Apache HTTP Server to use a different document root (instead of <code class="filename">/var/www/html/</code>):
+						Como usuario root de Linux, ejecute el comando <code class="command">/sbin/restorecon -v /web</code> para restaurar el contexto predeterminado de SELinux.
+					</div></li></ol></div><div class="formalpara" id="form-Security-Enhanced_Linux-Persistent_Changes_semanage_fcontext-Changing_a_Directory_and_its_Contents_Types"><h5 class="formalpara">Cambio de un Directorio y sus Tipos de Contenidos</h5>
+					El siguiente ejemplo muestra la creación de un directorio nuevo y el cambio del tipo de archivo del mismo (junto con su contenido) a un tipo usado por el Servidor HTTP Apache. La configuración en este ejemplo se usa si quiere que el Servidor HTTP Apache use una raíz de documento distinta (en vez de <code class="filename">/var/www/html/</code>):
 				</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">mkdir /web</code> command to create a new directory, and then the <code class="command">touch /web/file{1,2,3}</code> command to create 3 empty files (<code class="filename">file1</code>, <code class="filename">file2</code>, and <code class="filename">file3</code>). The <code class="filename">/web/</code> directory and files in it are labeled with the <code class="computeroutput">default_t</code> type:
+						Como usuario root de Linux, ejecute el comando <code class="command">mkdir /web</code> para crear un directorio nuevo, y luego el comando <code class="command">touch /web/archivo{1,2,3}</code> para crear 3 archivos vacíos (<code class="filename">archivo1</code>, <code class="filename">archivo2</code> y <code class="filename">archivo3</code>). El directorio <code class="filename">/web/</code> y los archivos en él son etiquetados con el tipo <code class="computeroutput">default_t</code>:
 					</div><pre class="screen"># ls -dZ /web
 drwxr-xr-x  root root unconfined_u:object_r:default_t:s0 /web
 # ls -lZ /web
@@ -1142,7 +1142,7 @@ drwxr-xr-x  root root unconfined_u:object_r:default_t:s0 /web
 					</div><pre class="screen">/web(/.*)?    system_u:object_r:httpd_sys_content_t:s0
 
 </pre></li><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">/sbin/restorecon -R -v /web</code> command to change the type of the <code class="filename">/web/</code> directory, as well as all files in it. The <code class="option">-R</code> is for recursive, which means all files and directories under the <code class="filename">/web/</code> directory are labeled with the <code class="computeroutput">httpd_sys_content_t</code> type. Since the <code class="command">semanage</code> command added an entry to <code class="filename">file.contexts.local</code> for <code class="computeroutput">/web(/.*)?</code>, the <code class="command">/sbin/restorecon</code> command changes the types to <code class="computeroutput">httpd_sys_content_t</code>:
+						Como usuario root de LInux, ejecute el comando <code class="command">/sbin/restorecon -R -v /web</code> para cambiar elt ipo del directorio <code class="filename">/web/</code>, junto con los archivos dentro de él. La opción <code class="option">-R</code> significa recursivo, es decir, todos los archivos y directorios dentro del directorio <code class="filename">/web/</code> se etiquetarán con el tipo <code class="computeroutput">httpd_sys_content_t</code>. Dado que el comando <code class="command">semanage</code> agregó una entrada en <code class="filename">file.contexts.local</code> para <code class="computeroutput">/web(/.*)?</code>, el comando <code class="command">/sbin/restorecon</code> los tipos a <code class="computeroutput">httpd_sys_content_t</code>:
 					</div><pre class="screen"># /sbin/restorecon -R -v /web
 restorecon reset /web context unconfined_u:object_r:default_t:s0-&gt;system_u:object_r:httpd_sys_content_t:s0
 restorecon reset /web/file2 context unconfined_u:object_r:default_t:s0-&gt;system_u:object_r:httpd_sys_content_t:s0
@@ -1150,45 +1150,45 @@ restorecon reset /web/file3 context unconfined_u:object_r:default_t:s0-&gt;syste
 restorecon reset /web/file1 context unconfined_u:object_r:default_t:s0-&gt;system_u:object_r:httpd_sys_content_t:s0
 
 </pre><div class="para">
-						By default, newly-created files and directories inherit the SELinux type of their parents. In this example, files and directories created in the <code class="filename">/web/</code> directory will be labeled with the <code class="computeroutput">httpd_sys_content_t</code> type.
+						Por defecto, los archivos y directorios recién creados heredan el tipo SELinux de sus padres. En este ejemplo, los archivos y directorios creado en el directorio <code class="filename">/web/</code> se etiquetarán con el tipo <code class="computeroutput">httpd_sys_content_t</code>.
 					</div></li><li class="listitem"><div class="para">
 						As the Linux root user, run the <code class="command">/usr/sbin/semanage fcontext -d "/web(/.*)?"</code> command to remove the context added for <code class="computeroutput">"/web(/.*)?"</code>.
 					</div></li><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">/sbin/restorecon -R -v /web</code> command to restore the default SELinux contexts.
-					</div></li></ol></div><div class="formalpara"><h5 class="formalpara">Deleting an added Context</h5>
-					The following example demonstrates adding and removing an SELinux context:
+						Como usuario root de Linux, ejecute el comando <code class="command">/sbin/restorecon -R -v /web</code> para restaurar el contexto predeterminado de SELinux.
+					</div></li></ol></div><div class="formalpara" id="form-Security-Enhanced_Linux-Persistent_Changes_semanage_fcontext-Deleting_an_added_Context"><h5 class="formalpara">Borrado de un Contexto agregado</h5>
+					El siguiente ejemplo muestra el agregado y su eliminación del contexto de SELinux:
 				</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">/usr/sbin/semanage fcontext -a -t httpd_sys_content_t /test</code> command. The <code class="filename">/test/</code> directory does not have to exist. This command adds the following context to <code class="filename">/etc/selinux/targeted/contexts/files/file_contexts.local</code>:
+						Como usuario root de Linux, ejecute el comando <code class="command">/usr/sbin/semanage fcontext -a -t httpd_sys_content_t /prueba</code>. El directorio <code class="filename">/prueba/</code> no tiene que existir. Este comando agrega el siguiente contexto a <code class="filename">/etc/selinux/targeted/contexts/files/file_contexts.local</code>:
 					</div><pre class="screen">/test    system_u:object_r:httpd_sys_content_t:s0
 
 </pre></li><li class="listitem"><div class="para">
-						To remove the context, as the Linux root user, run the <code class="command">/usr/sbin/semanage fcontext -d <em class="replaceable"><code>file-name</code></em>|<em class="replaceable"><code>directory-name</code></em></code> command, where <em class="replaceable"><code>file-name</code></em>|<em class="replaceable"><code>directory-name</code></em> is the first part in <code class="filename">file_contexts.local</code>. The following is an example of a context in <code class="filename">file_contexts.local</code>:
+						Para eliminar el contexto, como usuario root de Linux, ejecute el comando <code class="command">/usr/sbin/semanage fcontext -d <em class="replaceable"><code>nombre-de-archivo</code></em>|<em class="replaceable"><code>nombre-de-directorio</code></em></code>, donde <em class="replaceable"><code>nombre-de-archivo</code></em>|<em class="replaceable"><code>nombre-de-directorio</code></em> es la primera parte en <code class="filename">file_contexts.local</code>. El siguiente es un ejemplo de un contexto en <code class="filename">file_contexts.local</code>:
 					</div><pre class="screen">/test    system_u:object_r:httpd_sys_content_t:s0
 
 </pre><div class="para">
-						With the first part being <code class="computeroutput">/test</code>. To prevent the <code class="filename">/test/</code> directory from being labeled with the <code class="computeroutput">httpd_sys_content_t</code> after running <code class="command">/sbin/restorecon</code>, or after a file system relabel, run the following command as the Linux root user to delete the context from <code class="filename">file_contexts.local</code>:
+						Siendo la primera parte <code class="computeroutput">/prueba</code>. Para evitar que el directorio <code class="filename">/prueba/</code> se etiquete con <code class="computeroutput">httpd_sys_content_t</code> después de ejecutar <code class="command">/sbin/restorecon</code>, o después de un reetiquetado del sistema, ejecute el siguiente comando como usuario root de Linux para eliminar el contexto de <code class="filename">file_contexts.local</code>:
 					</div><div class="para">
 						<code class="command">/usr/sbin/semanage fcontext -d /test</code>
 					</div></li></ol></div><div class="para">
-				If the context is part of a regular expression, for example, <code class="computeroutput">/web(/.*)?</code>, use quotation marks around the regular expression:
+				Si el contexto es parte de una expresión regular, por ejemplo <code class="computeroutput">/web(/.*)?</code>, use las comillas para encerrar la expresión regular:
 			</div><div class="para">
 				<code class="command">/usr/sbin/semanage fcontext -d "/web(/.*)?"</code>
 			</div><div class="para">
-				Refer to the <span class="citerefentry"><span class="refentrytitle">semanage</span>(8)</span> manual page for further information about <code class="command">/usr/sbin/semanage</code>.
+				Vaya a la página de manual de <span class="citerefentry"><span class="refentrytitle">semanage</span>(8)</span> para información adicional sobre <code class="command">/usr/sbin/semanage</code>.
 			</div><div class="important"><h2>Importante</h2><div class="para">
-					When changing the SELinux context with <code class="command">/usr/sbin/semanage fcontext -a</code>, use the full path to the file or directory to avoid files being mislabeled after a file system relabel, or after the <code class="command">/sbin/restorecon</code> command is run.
-				</div></div></div></div><div class="section" title="5.8. The file_t and default_t Types" id="sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.8. The file_t and default_t Types</h2></div></div></div><div class="para">
-			On file systems that support extended attributes, when a file that lacks an SELinux context on disk is accessed, it is treated as if it had a default context as defined by SELinux policy. In common policies, this default context uses the <code class="computeroutput">file_t</code> type. This should be the only use of this type, so that files without a context on disk can be distinguished in policy, and generally kept inaccessible to confined domains. The <code class="computeroutput">file_t</code> type should not exist on correctly-labeled file systems, because all files on a system running SELinux should have an SELinux context, and the <code class="computeroutput">file_t</code> type is never used in file-context configuration<sup>[<a id="id1847598" href="#ftn.id1847598" class="footnote">11</a>]</sup>.
+					Cuando se cambia el contexto de SELinux con <code class="command">/usr/sbin/semanage fcontext -a</code>, use la dirección completa del archivo o directorio para evitar etiquetar mal los archivos después de un reetiquetado del sistema de archivo, o después ejecutar el comando <code class="command">/sbin/restorecon</code>.
+				</div></div></div></div><div class="section" title="5.8. Los tipos file_t y default_t" id="sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.8. Los tipos file_t y default_t</h2></div></div></div><div class="para">
+			En sistemas de archivo que soportan atributos extendidos, cuando se accede a un archivo en disco al que le falta el contexto de SELinux, se trata como si tuviera un contexto predeterminado tal como fue definido en la política de SELinux. En políticas comunes, este conexto por defecto usa el tipo <code class="computeroutput">file_t</code>. Este debería ser el único uso de este tipo, por lo que los archivos sin un contexto en el disco se podrían distinguir en la política, y generalmente mantenerse inaccesibles a dominios confinados. El tipo <code class="computeroutput">file_t</code> no debería existir en sistemas de archivo correctamente etiquetados, porque todos los archivos dado que todos los archivos en un sistema corriendo SELinux deberían tener un contexto de SELinux, y el tipo <code class="computeroutput">file_t</code> no sebería usarse en la configuración de contexto de archivos <sup>[<a id="id890908" href="#ftn.id890908" class="footnote">11</a>]</sup>.
 		</div><div class="para">
-			The <code class="computeroutput">default_t</code> type is used on files that do not match any other pattern in file-context configuration, so that such files can be distinguished from files that do not have a context on disk, and generally kept inaccessible to confined domains. If you create a new top-level directory, such as <code class="filename">/mydirectory/</code>, this directory may be labeled with the <code class="computeroutput">default_t</code> type. If services need access to such a directory, update the file-contexts configuration for this location. Refer to <a class="xref" href="#sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext" title="5.7.2. Persistent Changes: semanage fcontext">Sección 5.7.2, “Persistent Changes: semanage fcontext”</a> for details on adding a context to the file-context configuration.
-		</div></div><div class="section" title="5.9. Mounting File Systems" id="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.9. Mounting File Systems</h2></div></div></div><div class="para">
-			By default, when a file system that supports extended attributes is mounted, the security context for each file is obtained from the <span class="emphasis"><em>security.selinux</em></span> extended attribute of the file. Files in file systems that do not support extended attributes are assigned a single, default security context from the policy configuration, based on file system type.
+			The <code class="computeroutput">default_t</code> type is used on files that do not match any other pattern in file-context configuration, so that such files can be distinguished from files that do not have a context on disk, and generally kept inaccessible to confined domains. If you create a new top-level directory, such as <code class="filename">/mydirectory/</code>, this directory may be labeled with the <code class="computeroutput">default_t</code> type. If services need access to such a directory, update the file-contexts configuration for this location. Refer to <a class="xref" href="#sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext" title="5.7.2. Cambios Persistentes: semanage fcontext">Sección 5.7.2, “Cambios Persistentes: semanage fcontext”</a> for details on adding a context to the file-context configuration.
+		</div></div><div class="section" title="5.9. Montaje de Sistemas de Archivos" id="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.9. Montaje de Sistemas de Archivos</h2></div></div></div><div class="para">
+			Por defecto, cuando un sistema de archivo que soporta atributos extendidos se monta, el contexto de seguridad para cada archivo se obtiene de atributo extendido <span class="emphasis"><em>security.selinux</em></span> del archivo. A los archivos en sistemas de archivo que no dan soporte a atributos extendidos se les asigna un único contexto de seguridad predeterminado desde la configuración de la política, basada en el tipo de sistema de archivo.
 		</div><div class="para">
-			Use the <code class="command">mount -o context</code> command to override existing extended attributes, or to specify a different, default context for file systems that do not support extended attributes. This is useful if you do not trust a file system to supply the correct attributes, for example, removable media used in multiple systems. The <code class="command">mount -o context</code> command can also be used to support labeling for file systems that do not support extended attributes, such as File Allocation Table (FAT) or NFS file systems. The context specified with the <code class="option">context</code> is not written to disk: the original contexts are preserved, and are seen when mounting without a <code class="option">context</code> option (if the file system had extended attributes in the first place).
+			Use el comando <code class="command">mount -o context</code> para superponer los atributos extendidos actuales, o para especificar uno distinto y por defecto para sistemas de archivo que no dan soporte a atributos extendidos. Esto es útil si no confía en que un sistema de archivo provea los atributos correctos, por ejemplo, medios removibles en sistemas múltiples. El comando <code class="command">mount -o context</code> también se puede ussar para dar soporte al etiquetado de sistemas de archivos que no soportan atributos extendidos, tales como la Tabla de Ubicación de Archivos (FAT) o los sistemas de archivo NFS. El contexto especificado con la opción <code class="option">context</code> no se escribe al disco: los contextos originales son preservados, y se ven cuando se lo monta sin la opción <code class="option">context</code> (si el sistema de archivo ya tenía sopoorte para atributos extendidos).
 		</div><div class="para">
 			For further information about file system labeling, refer to James Morris's "Filesystem Labeling in SELinux" article: <a href="http://www.linuxjournal.com/article/7426">http://www.linuxjournal.com/article/7426</a>.
-		</div><div class="section" title="5.9.1. Context Mounts" id="sect-Security-Enhanced_Linux-Mounting_File_Systems-Context_Mounts"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.9.1. Context Mounts</h3></div></div></div><div class="para">
-				To mount a file system with the specified context, overriding existing contexts if they exist, or to specify a different, default context for a file system that does not support extended attributes, as the Linux root user, use the <code class="command">mount -o context=<em class="replaceable"><code>SELinux_user:role:type:level</code></em></code> command when mounting the desired file system. Context changes are not written to disk. By default, NFS mounts on the client side are labeled with a default context defined by policy for NFS file systems. In common policies, this default context uses the <code class="computeroutput">nfs_t</code> type. Without additional mount options, this may prevent sharing NFS file systems via other services, such as the Apache HTTP Server. The following example mounts an NFS file system so that it can be shared via the Apache HTTP Server:
+		</div><div class="section" title="5.9.1. Montajes de Contexto" id="sect-Security-Enhanced_Linux-Mounting_File_Systems-Context_Mounts"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.9.1. Montajes de Contexto</h3></div></div></div><div class="para">
+				Para montar un sistema de archivo con el contexto especificado, superponiendo los contextos existentes si existieran, o para especificar uno predeterminado distinto para un sistema de archivo que no da soporte para atributos extendidos, como usuario root de Linux, use el comando <code class="command">mount -o context=<em class="replaceable"><code>SELinux_user:role:type:level</code></em></code> cuando monte el sistema de archivo deseado. Los cambios de contexto no se graban en el disco. Por defecto, los montajes NFS en el lado del cliente se etiquetan con un contexto distinto definido por una política para sistemas de archivo NFS. En políticas comunes, este contexto predeterminado usa el tipo <code class="computeroutput">nfs_t</code>. Sin las opciones de montaje adicionales, esto podría evitar el que sistemas de archivo NFS sean compartidos vía otros servicios, como el Servidor HTTP Apache. El siguiente ejemplo monta un sistema de archivo NFS para que se pueda acceder
  a través del Servidor HTTP Apache:
 			</div><div class="para">
 				
 <pre class="screen"># mount server:/export /local/mount/point -o\
@@ -1197,39 +1197,39 @@ context="system_u:object_r:httpd_sys_content_t:s0"
 </pre>
 
 			</div><div class="para">
-				Newly-created files and directories on this file system appear to have the SELinux context specified with <code class="option">-o context</code>; however, since context changes are not written to disk for these situations, the context specified with the <code class="option">context</code> option is only retained if the <code class="option">context</code> option is used on the next mount, and if the same context is specified.
+				Los archivos y directorios recién creados en este sistema de archivo parecen tener un contexto SELinux especificado con <code class="option">-o contexto</code>; sin embargo, dado que los cambios del contexto no se escriben en el disco en estas situaciones, el contexto especificado por la opción <code class="option">-o contexto</code> sólo se mantiene si se usa la misma opción en la siguiente montada, y si además se especifica el mismo contexto.
 			</div><div class="para">
-				Type Enforcement is the main permission control used in SELinux targeted policy. For the most part, SELinux users and roles can be ignored, so, when overriding the SELinux context with <code class="option">-o context</code>, use the SELinux <code class="computeroutput">system_u</code> user and <code class="computeroutput">object_r</code> role, and concentrate on the type. If you are not using the MLS policy or multi-category security, use the <code class="computeroutput">s0</code> level.
+				La Obligación de Tipo es el control de permiso principal en la política destinada de SELinux. Para la mayor parte, los usuarios y roles de SELinux se pueden ignorar, por lo que, cuando se superponga el contexto de SELinux con <code class="option">-o context</code>, use el usuario SELinux <code class="computeroutput">system_u</code> y el rol <code class="computeroutput">object_r</code>, y concéntrese en el tipo. Si no está usando la política MLS o seguridad multi-categoría, use el nivel <code class="computeroutput">s0</code>.
 			</div><div class="note"><h2>Nota</h2><div class="para">
-					When a file system is mounted with a <code class="option">context</code> option, context changes (by users and processes) are prohibited. For example, running <code class="command">chcon</code> on a file system mounted with a <code class="option">context</code> option results in a <code class="computeroutput">Operation not supported</code> error.
-				</div></div></div><div class="section" title="5.9.2. Changing the Default Context" id="sect-Security-Enhanced_Linux-Mounting_File_Systems-Changing_the_Default_Context"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.9.2. Changing the Default Context</h3></div></div></div><div class="para">
-				As mentioned in <a class="xref" href="#sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types" title="5.8. The file_t and default_t Types">Sección 5.8, “The file_t and default_t Types”</a>, on file systems that support extended attributes, when a file that lacks an SELinux context on disk is accessed, it is treated as if it had a default context as defined by SELinux policy. In common policies, this default context uses the <code class="computeroutput">file_t</code> type. If it is desirable to use a different default context, mount the file system with the <code class="option">defcontext</code> option.
+					Cuando se monta un sistema de archivo con la opción <code class="option">context</code>, los cambios de contexto (por usuarios y procesos) son prohibidos. Por ejemplo, ejecutando <code class="command">chcon</code> en un sistema de archivo montado con la opción <code class="option">context</code> resulta en un error de <code class="computeroutput">Operación no soportada</code>.
+				</div></div></div><div class="section" title="5.9.2. Cambio del Contexto Predeterminado" id="sect-Security-Enhanced_Linux-Mounting_File_Systems-Changing_the_Default_Context"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.9.2. Cambio del Contexto Predeterminado</h3></div></div></div><div class="para">
+				As mentioned in <a class="xref" href="#sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types" title="5.8. Los tipos file_t y default_t">Sección 5.8, “Los tipos file_t y default_t”</a>, on file systems that support extended attributes, when a file that lacks an SELinux context on disk is accessed, it is treated as if it had a default context as defined by SELinux policy. In common policies, this default context uses the <code class="computeroutput">file_t</code> type. If it is desirable to use a different default context, mount the file system with the <code class="option">defcontext</code> option.
 			</div><div class="para">
-				The following example mounts a newly-created file system (on <code class="filename">/dev/sda2</code>) to the newly-created <code class="filename">/test/</code> directory. It assumes that there are no rules in <code class="filename">/etc/selinux/targeted/contexts/files/</code> that define a context for the <code class="filename">/test/</code> directory:
+				El siguiente ejemplo monta un sistema de archivo recién creado (en <code class="filename">/dev/sda2</code>) en el directorio recién creado <code class="filename">/prueba/</code>. Asume que no hay reglas en <code class="filename">/etc/selinux/targeted/contexts/files/</code> que definan el contexto del directorio <code class="filename">/prueba/</code>:
 			</div><pre class="screen">
 # mount /dev/sda2 /test/ -o defcontext="system_u:object_r:samba_share_t:s0"
 
 </pre><div class="para">
-				In this example:
+				En este ejemplo:
 			</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-						the <code class="option">defcontext</code> option defines that <code class="computeroutput">system_u:object_r:samba_share_t:s0</code> is "the default security context for unlabeled files"<sup>[<a id="id546655" href="#ftn.id546655" class="footnote">12</a>]</sup>.
+						the <code class="option">defcontext</code> option defines that <code class="computeroutput">system_u:object_r:samba_share_t:s0</code> is "the default security context for unlabeled files"<sup>[<a id="id891190" href="#ftn.id891190" class="footnote">12</a>]</sup>.
 					</div></li><li class="listitem"><div class="para">
-						when mounted, the root directory (<code class="filename">/test/</code>) of the file system is treated as if it is labeled with the context specified by <code class="option">defcontext</code> (this label is not stored on disk). This affects the labeling for files created under <code class="filename">/test/</code>: new files inherit the <code class="computeroutput">samba_share_t</code> type, and these labels are stored on disk.
+						cuando sea montado, el directorio raíz (<code class="filename">/prueba/</code>) del sistema de archivo se trata como si estuviera etiquetado con el contexto especificado por <code class="option">defcontext</code> (esta etiqueta no se guarda en el disco). Esto afecta el etiquetado de archvios creados en <code class="filename">/prueba/</code>: los archivos nuevos heredan el tipo <code class="computeroutput">samba_share_t</code>, y estas etiquetas se guardan en el disco.
 					</div></li><li class="listitem"><div class="para">
-						files created under <code class="filename">/test/</code> while the file system was mounted with a <code class="option">defcontext</code> option retain their labels.
-					</div></li></ul></div></div><div class="section" title="5.9.3. Mounting an NFS File System" id="sect-Security-Enhanced_Linux-Mounting_File_Systems-Mounting_an_NFS_File_System"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.9.3. Mounting an NFS File System</h3></div></div></div><div class="para">
-				By default, NFS mounts on the client side are labeled with a default context defined by policy for NFS file systems. In common policies, this default context uses the <code class="computeroutput">nfs_t</code> type. Depending on policy configuration, services, such as Apache HTTP Server and MySQL, may not be able to read files labeled with the <code class="computeroutput">nfs_t</code> type. This may prevent file systems labeled with this type from being mounted and then read or exported by other services.
+						los archivos creados bajo <code class="filename">/prueba/</code> mientras el sistema de archivo estaba montado con la opción <code class="option">defcontext</code> retendrán sus etiquetas.
+					</div></li></ul></div></div><div class="section" title="5.9.3. Montando un Sistema de Archivos NFS" id="sect-Security-Enhanced_Linux-Mounting_File_Systems-Mounting_an_NFS_File_System"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.9.3. Montando un Sistema de Archivos NFS</h3></div></div></div><div class="para">
+				Por defecto, los montajes NFS en el lado del cliente son etiquetados con un contexto predeterminado por la política para los sistemas de archivo NFS. En políticas comunes, este contexto predeterminado usa el tipo <code class="computeroutput">nfs_t</code>. Dependiendo de la configuración de la política, los servicios, como el Servidor HTTP Apache y MySQL, pueden no poder leer archivos etiquetados con el tipo <code class="computeroutput">nfs_t</code>. Esto puede prevenir que los sistemas de archivos etiquetados con este tipo se monten y sean leídos o exportados por otros servicios.
 			</div><div class="para">
-				If you would like to mount an NFS file system and read or export that file system with another service, use the <code class="option">context</code> option when mounting to override the <code class="computeroutput">nfs_t</code> type. Use the following context option to mount NFS file systems so that they can be shared via the Apache HTTP Server:
+				Si desea montar un sistema de archivo NFS y leer o exportar ese sistema de archivo con otro servicio, use la opción <code class="option">contexto</code> cuando monte para anular el tipo <code class="computeroutput">nfs_t</code>. Use la siguiente opción de contexto para montar sistemas de archivo NFS para que puedan compartirse vía el Servidor HTTP Apache:
 			</div><pre class="screen">mount server:/export /local/mount/point -o\
 context="system_u:object_r:httpd_sys_content_t:s0"
 
 </pre><div class="para">
-				Since context changes are not written to disk for these situations, the context specified with the <code class="option">context</code> option is only retained if the <code class="option">context</code> option is used on the next mount, and if the same context is specified.
+				Dado que los cambios de contexto no se escriben al disco para estas situaciones, el contexto especificado con la opción <code class="option">context</code> sólo se retiene si la opción <code class="option">context</code> se usa en el siguiente montaje, y si el mismo contexto se especifica.
 			</div><div class="para">
-				As an alternative to mounting file systems with <code class="option">context</code> options, Booleans can be turned on to allow services access to file systems labeled with the <code class="computeroutput">nfs_t</code> type. Refer to <a class="xref" href="#sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS" title="5.6.3. Booleans for NFS and CIFS">Sección 5.6.3, “Booleans for NFS and CIFS”</a> for instructions on configuring Booleans to allow services access to the <code class="computeroutput">nfs_t</code> type.
-			</div></div><div class="section" title="5.9.4. Multiple NFS Mounts" id="sect-Security-Enhanced_Linux-Mounting_File_Systems-Multiple_NFS_Mounts"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.9.4. Multiple NFS Mounts</h3></div></div></div><div class="para">
-				When mounting multiple mounts from the same NFS export, attempting to override the SELinux context of each mount with a different context, results in subsequent mount commands failing. In the following example, the NFS server has a single export, <code class="filename">/export</code>, which has two subdirectories, <code class="filename">web/</code> and <code class="filename">database/</code>. The following commands attempt two mounts from a single NFS export, and try to override the context for each one:
+				As an alternative to mounting file systems with <code class="option">context</code> options, Booleans can be turned on to allow services access to file systems labeled with the <code class="computeroutput">nfs_t</code> type. Refer to <a class="xref" href="#sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS" title="5.6.3. Booleanos para NFS y CIFS">Sección 5.6.3, “Booleanos para NFS y CIFS”</a> for instructions on configuring Booleans to allow services access to the <code class="computeroutput">nfs_t</code> type.
+			</div></div><div class="section" title="5.9.4. Montajes NFS Múltiples" id="sect-Security-Enhanced_Linux-Mounting_File_Systems-Multiple_NFS_Mounts"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.9.4. Montajes NFS Múltiples</h3></div></div></div><div class="para">
+				Cuando se monten múltiples montajes desde el mismo NFS exportado, el intento de sobreescribir el contexto de SELinux e cada montaje con un contexto diferente, resulta en fallos de los comandos de montaje subsecuentes. En el siguiente ejemplo, el servidor NFS tiene un exportado único, <code class="filename">/export</code>, que tiene dos subdirectorios, <code class="filename">web/</code> and <code class="filename">database/</code>. El siguiente comando intenta dos montajes desde un único export NFS e intenta sobreescribir el contexto para cada uno:
 			</div><pre class="screen">
 # mount server:/export/web /local/web -o\
 context="system_u:object_r:httpd_sys_content_t:s0"
@@ -1238,12 +1238,12 @@ context="system_u:object_r:httpd_sys_content_t:s0"
 context="system_u:object_r:mysqld_db_t:s0"
 
 </pre><div class="para">
-				The second mount command fails, and the following is logged to <code class="filename">/var/log/messages</code>:
+				El segundo comando mount falla, y se graba lo siguiente en <code class="filename">/var/log/messages</code>:
 			</div><pre class="screen">
 kernel: SELinux: mount invalid.  Same superblock, different security settings for (dev 0:15, type nfs)
 
 </pre><div class="para">
-				To mount multiple mounts from a single NFS export, with each mount having a different context, use the <code class="option">-o nosharecache,context</code> options. The following example mounts multiple mounts from a single NFS export, with a different context for each mount (allowing a single service access to each one):
+				Para montar montajes múltiples de un exportado NFS único, con cada montaje teniendo un contexto diferente, use las opciones <code class="option">-o nosharecache,context</code>. El siguiente ejemplo monta montajes múltiples de un único export de NSF, con un contexto diferente para cada montaje (permitiendo un único acceso de servicio a cada uno):
 			</div><pre class="screen">
 # mount server:/export/web /local/web -o\
 nosharecache,context="system_u:object_r:httpd_sys_content_t:s0"
@@ -1252,27 +1252,27 @@ nosharecache,context="system_u:object_r:httpd_sys_content_t:s0"
 nosharecache,context="system_u:object_r:mysqld_db_t:s0"
 
 </pre><div class="para">
-				In this example, <code class="computeroutput">server:/export/web</code> is mounted locally to <code class="filename">/local/web/</code>, with all files being labeled with the <code class="computeroutput">httpd_sys_content_t</code> type, allowing Apache HTTP Server access. <code class="computeroutput">server:/export/database</code> is mounted locally to <code class="filename">/local/database</code>, with all files being labeled with the <code class="computeroutput">mysqld_db_t</code> type, allowing MySQL access. These type changes are not written to disk.
+				En este ejemplo, <code class="computeroutput">server:/export/web</code> se monta localmente en <code class="filename">/local/web/</code>, con todos los archivos etiquetados con el tipo <code class="computeroutput">httpd_sys_content_t</code>, lo que permite el acceso al Servidor HTTP Apache. <code class="computeroutput">server:/export/database</code> está montado localmente en <code class="filename">/local/database</code>, con los archivos etiquetados con el tipo <code class="computeroutput">mysqld_db_t</code>, lo que permite a MySQL el acceso. Estos cambios de tipo no se escriben en el disco.
 			</div><div class="important"><h2>Importante</h2><div class="para">
-					The <code class="option">nosharecache</code> options allows you to mount the same subdirectory of an export multiple times with different contexts (for example, mounting <code class="filename">/export/web</code> multiple times). Do not mount the same subdirectory from an export multiple times with different contexts, as this creates an overlapping mount, where files are accessible under two different contexts.
-				</div></div></div><div class="section" title="5.9.5. Making Context Mounts Persistent" id="sect-Security-Enhanced_Linux-Mounting_File_Systems-Making_Context_Mounts_Persistent"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.9.5. Making Context Mounts Persistent</h3></div></div></div><div class="para">
-				To make context mounts persistent across remounting and reboots, add entries for the file systems in <code class="filename">/etc/fstab</code> or an automounter map, and use the desired context as a mount option. The following example adds an entry to <code class="filename">/etc/fstab</code> for an NFS context mount:
+					Las opciones <code class="option">nosharecache</code> le permiten montar el mismo subdirectorio de un exportado varias veces con distintos contextos (por ejemplo, montar <code class="filename">/export/web</code> varias veces). No monte el mismo directorio de un exportado varias veces con distintos contextos, dado que esto crea un montado solapado, donde los archivos se pueden acceder con dos contextos diferentes.
+				</div></div></div><div class="section" title="5.9.5. Haciendo Persistente los Contextos de Montajes" id="sect-Security-Enhanced_Linux-Mounting_File_Systems-Making_Context_Mounts_Persistent"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.9.5. Haciendo Persistente los Contextos de Montajes</h3></div></div></div><div class="para">
+				Para hacer que los contextos de montajes persistentes entre remontadas y reiniciadas, agregue las entradas de los sistemas de archivos en <code class="filename">/etc/fstab</code> o un mapa de automontador, y use el contexto deseado como una opción de montaje. El siguiente ejemplo agrega una entrada en <code class="filename">/etc/fstab</code> para un montaje de contexto NFS:
 			</div><pre class="screen">
 server:/export /local/mount/ nfs context="system_u:object_r:httpd_sys_content_t:s0" 0 0
 
 </pre><div class="para">
 				Refer to the <a href="http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.2/html/Deployment_Guide/s1-nfs-client-config.html">Red Hat Enterprise Linux 5 Deployment Guide, Section 19.2. "NFS Client Configuration"</a> for information about mounting NFS file systems.
-			</div></div></div><div class="section" title="5.10. Maintaining SELinux Labels" id="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.10. Maintaining SELinux Labels </h2></div></div></div><div class="para">
-			These sections describe what happens to SELinux contexts when copying, moving, and archiving files and directories. Also, it explains how to preserve contexts when copying and archiving.
-		</div><div class="section" title="5.10.1. Copying Files and Directories" id="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Copying_Files_and_Directories"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.10.1. Copying Files and Directories</h3></div></div></div><div class="para">
-				When a file or directory is copied, a new file or directory is created if it does not exist. That new file or directory's context is based on default-labeling rules, not the original file or directory's context (unless options were used to preserve the original context). For example, files created in user home directories are labeled with the <code class="computeroutput">user_home_t</code> type:
+			</div></div></div><div class="section" title="5.10. Mantención de las Etiquetas de SELinux" id="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.10. Mantención de las Etiquetas de SELinux</h2></div></div></div><div class="para">
+			Estas secciones describen qué les pasa a los contextos SELinux cuando se copia, mueve y compacta archivos y directorios. También explica cómo preservar los contextos cuando se copia o se compacta.
+		</div><div class="section" title="5.10.1. Copia de Directorios y Archivos" id="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Copying_Files_and_Directories"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.10.1. Copia de Directorios y Archivos</h3></div></div></div><div class="para">
+				Cuando se copia un archivo o directorio, se crea uno si no existía. El contexto de ese archivo o directorio nuevo está basado en las reglas de etiquetados predeterminada, y no el contexto original del archivo o directorio (a menos que se usen opciones para preservar el contexto original). Por ejemplo, los archivos creados en los directorios home de los usuarios se etiquetan con el tipo <code class="computeroutput">user_home_t</code>:
 			</div><pre class="screen">
 $ touch file1
 $ ls -Z file1 
 -rw-rw-r--  user1 group1 unconfined_u:object_r:user_home_t:s0 file1
 
 </pre><div class="para">
-				If such a file is copied to another directory, such as <code class="filename">/etc/</code>, the new file is created in accordance to default-labeling rules for the <code class="filename">/etc/</code> directory. Copying a file (without additional options) may not preserve the original context:
+				Si un archivo se copia a otro directorio, tal como <code class="filename">/etc/</code>, el archivo nuevo se crea de acuerdo a las reglas de etiquetado predeterminado del directorio <code class="filename">/etc/</code>. El copiado de un archivo (sin opciones adicionales) puede no preservar el contexto original:
 			</div><pre class="screen">
 $ ls -Z file1 
 -rw-rw-r--  user1 group1 unconfined_u:object_r:user_home_t:s0 file1
@@ -1281,11 +1281,11 @@ $ ls -Z /etc/file1
 -rw-r--r--  root root unconfined_u:object_r:etc_t:s0   /etc/file1
 
 </pre><div class="para">
-				When <code class="filename">file1</code> is copied to <code class="filename">/etc/</code>, if <code class="filename">/etc/file1</code> does not exist, <code class="filename">/etc/file1</code> is created as a new file. As shown in the example above, <code class="filename">/etc/file1</code> is labeled with the <code class="computeroutput">etc_t</code> type, in accordance to default-labeling rules.
+				Cuando el <code class="filename">archivo1</code> se copia a <code class="filename">/etc/</code>, si <code class="filename">/etc/archivo1</code> no existe, <code class="filename">/etc/archivo1</code> se crea como un archivo nuevo. Como se muestra en el ejemplo de arriba, <code class="filename">/etc/archivo1</code> se etiqueta con el tipo <code class="computeroutput">etc_t</code>, de acuerdo con las reglas de etiquetado predeterminadas.
 			</div><div class="para">
-				When a file is copied over an existing file, the existing file's context is preserved, unless the user specified <code class="command">cp</code> options to preserve the context of the original file, such as <code class="option">--preserve=context</code>. SELinux policy may prevent contexts from being preserved during copies.
-			</div><div class="formalpara"><h5 class="formalpara">Copying Without Preserving SELinux Contexts</h5>
-					When copying a file with the <code class="command">cp</code> command, if no options are given, the type is inherited from the targeted, parent directory:
+				Cuando un archivo se copia sobre otro existente, el contexto del archivo existente se preserva, a menos que el usuario especifique opciones de <code class="command">cp</code> para preservar el contexto del archivo original, tal como <code class="option">--preserve=context</code>. La política de SELinux puede prevenir que se preserver los contextos al copiar.
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Copying_Files_and_Directories-Copying_Without_Preserving_SELinux_Contexts"><h5 class="formalpara">Copia sin Preservar los Contextos de SELinux</h5>
+					Cuando se copia un archivo con el comando <code class="command">cp</code>, si no se dan opciones, el tipo se hereda desde el directorio padre destino:
 				</div><pre class="screen">
 $ touch file1
 $ ls -Z file1
@@ -1297,9 +1297,9 @@ $ ls -Z /var/www/html/file1
 -rw-r--r--  root root unconfined_u:object_r:httpd_sys_content_t:s0 /var/www/html/file1
 
 </pre><div class="para">
-				In this example, <code class="filename">file1</code> is created in a user's home directory, and is labeled with the <code class="computeroutput">user_home_t</code> type. The <code class="filename">/var/www/html/</code> directory is labeled with the <code class="computeroutput">httpd_sys_content_t</code> type, as shown with the <code class="command">ls -dZ /var/www/html/</code> command. When <code class="filename">file1</code> is copied to <code class="filename">/var/www/html/</code>, it inherits the <code class="computeroutput">httpd_sys_content_t</code> type, as shown with the <code class="command">ls -Z /var/www/html/file1</code> command.
-			</div><div class="formalpara"><h5 class="formalpara">Preserving SELinux Contexts When Copying</h5>
-					Use the <code class="command">cp --preserve=context</code> command to preserve contexts when copying:
+				En este ejemplo, <code class="filename">archivo1</code> se crea en el directorio de inicio del usuario, y se etiqueta con el tipo <code class="computeroutput">user_home_t</code>. El directorio <code class="filename">/var/www/html/</code> está etiquetado con el tipo <code class="computeroutput">httpd_sys_content_t</code>, como se muestra con el comando <code class="command">ls -dZ /var/www/html/</code>. Cuando el <code class="filename">archivo1</code> se copia a <code class="filename">/var/www/html/</code>, hereda el tipo <code class="computeroutput">httpd_sys_content_t</code>, como se muestra con el comando<code class="command">ls -Z /var/www/html/archivo1</code>.
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Copying_Files_and_Directories-Preserving_SELinux_Contexts_When_Copying"><h5 class="formalpara">Preservación de los Contextos de SELinux cuando se copia</h5>
+					Use el comando <code class="command">cp --preserve=context</code> para preservar los contextos cuando se copia:
 				</div><pre class="screen">
 $ touch file1
 $ ls -Z file1
@@ -1311,9 +1311,9 @@ $ ls -Z /var/www/html/file1
 -rw-r--r--  root root unconfined_u:object_r:user_home_t:s0 /var/www/html/file1
 
 </pre><div class="para">
-				In this example, <code class="filename">file1</code> is created in a user's home directory, and is labeled with the <code class="computeroutput">user_home_t</code> type. The <code class="filename">/var/www/html/</code> directory is labeled with the <code class="computeroutput">httpd_sys_content_t</code> type, as shown with the <code class="command">ls -dZ /var/www/html/</code> command. Using the <code class="option">--preserve=context</code> option preserves SELinux contexts during copy operations. As shown with the <code class="command">ls -Z /var/www/html/file1</code> command, the <code class="filename">file1</code> <code class="computeroutput">user_home_t</code> type was preserved when the file was copied to <code class="filename">/var/www/html/</code>.
-			</div><div class="formalpara"><h5 class="formalpara">Copying and Changing the Context</h5>
-					Use the <code class="command">cp -Z</code> command to change the destination copy's context. The following example was performed in the user's home directory:
+				En este ejemplo, el <code class="filename">archivo1</code> se crea en el directorio de inicio del usuario, y se etiqueta con el tipo <code class="computeroutput">user_home_t</code>. El directorio <code class="filename">/var/www/html/</code> está etiquetado con el tipo <code class="computeroutput">httpd_sys_content_t</code>, como se muestra con el comando <code class="command">ls -dZ /var/www/html/</code>. Usando la opción <code class="option">--preserve=context</code> se mantienen los contextos de SELinux durante operaciones de copia. Como se muestra con el comando <code class="command">ls -Z /var/www/html/archivo1</code>, el tipo <code class="computeroutput">user_home_t</code> del <code class="filename">archivo1</code> fue preservado cuando el archivo se copió a <code class="filename">/var/www/html/</code>.
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Copying_Files_and_Directories-Copying_and_Changing_the_Context"><h5 class="formalpara">Copiado y Cambio del Contexto</h5>
+					Use el comando <code class="command">cp -Z</code> para cambiar el contexto destino de copia. El siguiente ejemplo se realizó en el directorio de inicio del usuario:
 				</div><pre class="screen">
 $ touch file1
 $ cp -Z system_u:object_r:samba_share_t:s0 file1 file2
@@ -1323,9 +1323,9 @@ $ ls -Z file1 file2
 $ rm file1 file2
 
 </pre><div class="para">
-				In this example, the context is defined with the <code class="option">-Z</code> option. Without the <code class="option">-Z</code> option, <code class="filename">file2</code> would be labeled with the <code class="computeroutput">unconfined_u:object_r:user_home_t</code> context.
-			</div><div class="formalpara"><h5 class="formalpara">Copying a File Over an Existing File</h5>
-					When a file is copied over an existing file, the existing file's context is preserved (unless an option is used to preserve contexts). For example:
+				En este ejemplo, el contexto se define en la opción <code class="option">-Z</code>. Sin la opción <code class="option">-Z</code>, <code class="filename">archivo2</code> se etiquetaría con el contexto <code class="computeroutput">unconfined_u:object_r:user_home_t</code>.
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Copying_Files_and_Directories-Copying_a_File_Over_an_Existing_File"><h5 class="formalpara">Copia de un Archivos sobre un otro existente</h5>
+					Cuando un archivo se copia sobre otro existente, el contexto del archivo existente se preserva (a menos que se use una opción para preservar los contextos). Por ejemplo:
 				</div><pre class="screen">
 # touch /etc/file1
 # ls -Z /etc/file1
@@ -1338,37 +1338,37 @@ $ rm file1 file2
 -rw-r--r--  root root unconfined_u:object_r:etc_t:s0   /etc/file1
 
 </pre><div class="para">
-				In this example, two files are created: <code class="filename">/etc/file1</code>, labeled with the <code class="computeroutput">etc_t</code> type, and <code class="filename">/tmp/file2</code>, labeled with the <code class="computeroutput">user_tmp_t</code> type. The <code class="command">cp /tmp/file2 /etc/file1</code> command overwrites <code class="filename">file1</code> with <code class="filename">file2</code>. After copying, the <code class="command">ls -Z /etc/file1</code> command shows <code class="filename">file1</code> labeled with the <code class="computeroutput">etc_t</code> type, not the <code class="computeroutput">user_tmp_t</code> type from <code class="filename">/tmp/file2</code> that replaced <code class="filename">/etc/file1</code>.
+				En este ejemplo, se crean dos archivos: <code class="filename">/etc/archivo1</code>, etiquetado con el tipo <code class="computeroutput">etc_t</code>, y <code class="filename">/tmp/archivo2</code>, etiquetado con el tipo <code class="computeroutput">user_tmp_t</code>. Ell comando <code class="command">cp /tmp/archivo2 /etc/archivo1</code> sobreescribe <code class="filename">archivo1</code> con <code class="filename">archivo2</code>. Después de copiar, el comando <code class="command">ls -Z /etc/archivo1</code> muestra a <code class="filename">archivo1</code> etiquetado con el tipo <code class="computeroutput">etc_t</code>, en vez del <code class="computeroutput">user_tmp_t</code> de <code class="filename">/tmp/archivo2</code> que reemplazó a <code class="filename">/etc/archivo1</code>.
 			</div><div class="important"><h2>Importante</h2><div class="para">
-					Copy files and directories, rather than moving them. This helps ensure they are labeled with the correct SELinux contexts. Incorrect SELinux contexts can prevent processes from accessing such files and directories.
-				</div></div></div><div class="section" title="5.10.2. Moving Files and Directories" id="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Moving_Files_and_Directories"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.10.2. Moving Files and Directories</h3></div></div></div><div class="para">
-				File and directories keep their current SELinux context when they are moved. In many cases, this is incorrect for the location they are being moved to. The following example demonstrates moving a file from a user's home directory to <code class="filename">/var/www/html/</code>, which is used by the Apache HTTP Server. Since the file is moved, it does not inherit the correct SELinux context:
+					Copie archivos y directorios, en vez de moverlos. Esto ayuda a asegurar que se etiquetan con los contextos de SELinux correctos. Los contextos SELinux incorrectos pueden hacer que los procesos no puedan acceder a esos archivos y directorios.
+				</div></div></div><div class="section" title="5.10.2. Movimiento de Archivos y Directorios" id="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Moving_Files_and_Directories"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.10.2. Movimiento de Archivos y Directorios</h3></div></div></div><div class="para">
+				Los archivos y directorios mantienen su contexto SELinux actual cuando se mueven. En muchos casos, esto es incorrecto para la ubicación nueva a donde se los mueve. El siguiente ejemplo muestra la movida de un archivo desde el directorio de inicio del usuario a <code class="filename">/var/www/html/</code>, que es usado por el Servidor HTTP Apache. Dado que el archivo es movido, no hereda el contexto SELinux correcto:
 			</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
-						Run the <code class="command">cd</code> command without any arguments to change into your home directory. Once in your home directory, run the <code class="command">touch file1</code> command to create a file. This file is labeled with the <code class="computeroutput">user_home_t</code> type:
+						Ejecute el comando <code class="command">cd</code> sin ningún argumento para cambiar a su directorio de inicio. Una vez ahí, ejecute el comando <code class="command">touch archivo1</code> para crear un archivo. Este archivo se etiqueta con el tipo <code class="computeroutput">user_home_t</code>:
 					</div><pre class="screen">$ ls -Z file1
 -rw-rw-r--  user1 group1 unconfined_u:object_r:user_home_t:s0 file1
 
 </pre></li><li class="listitem"><div class="para">
-						Run the <code class="command">ls -dZ /var/www/html/</code> command to view the SELinux context of the <code class="filename">/var/www/html/</code> directory:
+						Ejecute el comando <code class="command">ls -dZ /var/www/html/</code> para ver el contexto de SELinux del directorio <code class="filename">/var/www/html/</code>:
 					</div><pre class="screen">$ ls -dZ /var/www/html/
 drwxr-xr-x  root root system_u:object_r:httpd_sys_content_t:s0 /var/www/html/
 
 </pre><div class="para">
-						By default, the <code class="filename">/var/www/html/</code> directory is labeled with the <code class="computeroutput">httpd_sys_content_t</code> type. Files and directories created under the <code class="filename">/var/www/html/</code> directory inherit this type, and as such, they are labeled with this type.
+						Por defecto, el directorio <code class="filename">/var/www/html/</code> se etiqueta con el tipo <code class="computeroutput">httpd_sys_content_t</code>. Los archivos y directorios creados bajo el directorio <code class="filename">/var/www/html/</code> heredan este tipo, y como tal, son etiquetados con este tipo.
 					</div></li><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">mv file1 /var/www/html/</code> command to move <code class="filename">file1</code> to the <code class="filename">/var/www/html/</code> directory. Since this file is moved, it keeps its current <code class="computeroutput">user_home_t</code> type:
+						Como usuario root de Linux, ejecute el comando <code class="command">mv archivo1 /var/www/html/</code> para mover el <code class="filename">archivo1</code> al directorio <code class="filename">/var/www/html/</code>. Dado que el archivo es movido, mantiene su tipo <code class="computeroutput">user_home_t</code> actual:
 					</div><pre class="screen"># mv file1 /var/www/html/
 # ls -Z /var/www/html/file1
 -rw-rw-r--  user1 group1 unconfined_u:object_r:user_home_t:s0 /var/www/html/file1
 
 </pre></li></ol></div><div class="para">
-				By default, the Apache HTTP Server can not read files that are labeled with the <code class="computeroutput">user_home_t</code> type. If all files comprising a web page are labeled with the <code class="computeroutput">user_home_t</code> type, or another type that the Apache HTTP Server can not read, permission is denied when attempting to access them via Firefox or text-based Web browsers.
+				Por defecto, el Servidor HTTP Apache no puede leer archivos etiquetados con el tipo <code class="computeroutput">user_home_t</code>. Si todos los archivos de una página web se etiquetaron con <code class="computeroutput">user_home_t</code>, u otro tipo al que el Servidor HTTP Apache no puede leer, el permiso es negado cuando intente accederlo vía Firefox o algún otro navegador web basado en texto.
 			</div><div class="important"><h2>Importante</h2><div class="para">
-					Moving files and directories with the <code class="command">mv</code> command may result in the wrong SELinux context, preventing processes, such as the Apache HTTP Server and Samba, from accessing such files and directories.
-				</div></div></div><div class="section" title="5.10.3. Checking the Default SELinux Context" id="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.10.3. Checking the Default SELinux Context</h3></div></div></div><div class="para">
-				Use the <code class="command">/usr/sbin/matchpathcon</code> command to check if files and directories have the correct SELinux context. From the <span class="citerefentry"><span class="refentrytitle">matchpathcon</span>(8)</span> manual page: "<code class="command">matchpathcon</code> queries the system policy and outputs the default security context associated with the file path."<sup>[<a id="id673095" href="#ftn.id673095" class="footnote">13</a>]</sup>. The following example demonstrates using the <code class="command">/usr/sbin/matchpathcon</code> command to verify that files in <code class="filename">/var/www/html/</code> directory are labeled correctly:
+					Mover archivos y directorios con el comando <code class="command">mv</code> puede resultar en el contexto SELinux incorrecto, evitando que los procesos tales como el Servidor HTTP Apache y Samba puedan acceder a tales archivos y directorios.
+				</div></div></div><div class="section" title="5.10.3. Chequeando el Contexto SELinux Predeterminado" id="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.10.3. Chequeando el Contexto SELinux Predeterminado</h3></div></div></div><div class="para">
+				Use the <code class="command">/usr/sbin/matchpathcon</code> command to check if files and directories have the correct SELinux context. From the <span class="citerefentry"><span class="refentrytitle">matchpathcon</span>(8)</span> manual page: "<code class="command">matchpathcon</code> queries the system policy and outputs the default security context associated with the file path."<sup>[<a id="id780065" href="#ftn.id780065" class="footnote">13</a>]</sup>. The following example demonstrates using the <code class="command">/usr/sbin/matchpathcon</code> command to verify that files in <code class="filename">/var/www/html/</code> directory are labeled correctly:
 			</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">touch /var/www/html/file{1,2,3}</code> command to create three files (<code class="filename">file1</code>, <code class="filename">file2</code>, and <code class="filename">file3</code>). These files inherit the <code class="computeroutput">httpd_sys_content_t</code> type from the <code class="filename">/var/www/html/</code> directory:
+						Como usuario root de Linux, ejecute el comando <code class="command">touch /var/www/html/archivo{1,2,3}</code> para crear tres archivos (<code class="filename">archivo1</code>, <code class="filename">archivo2</code> y <code class="filename">archivo3</code>). Estos heredan el tipo <code class="computeroutput">httpd_sys_content_t</code> del directorio <code class="filename">/var/www/html/</code>:
 					</div><pre class="screen"># touch /var/www/html/file{1,2,3}
 # ls -Z /var/www/html/
 -rw-r--r--  root root unconfined_u:object_r:httpd_sys_content_t:s0 file1
@@ -1376,34 +1376,34 @@ drwxr-xr-x  root root system_u:object_r:httpd_sys_content_t:s0 /var/www/html/
 -rw-r--r--  root root unconfined_u:object_r:httpd_sys_content_t:s0 file3
 
 </pre></li><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">chcon -t samba_share_t /var/www/html/file1</code> command to change the <code class="filename">file1</code> type to <code class="computeroutput">samba_share_t</code>. Note: the Apache HTTP Server can not read files or directories labeled with the <code class="computeroutput">samba_share_t</code> type.
+						Como usuario root de Linux, ejecute el comando <code class="command">chcon -t samba_share_t /var/www/html/archivo1</code> para cambiar el tipo del <code class="filename">archivo1</code> a <code class="computeroutput">samba_share_t</code>. Nota: El Servidor HTTP Apache no puede leer archivos o directorios etiquetados con el tipo <code class="computeroutput">samba_share_t</code>.
 					</div></li><li class="listitem"><div class="para">
-						The <code class="command">/usr/sbin/matchpathcon</code> <code class="option">-V</code> option compares the current SELinux context to the correct, default context in SELinux policy. Run the <code class="command">/usr/sbin/matchpathcon -V /var/www/html/*</code> command to check all files in the <code class="filename">/var/www/html/</code> directory:
+						La opción <code class="command">/usr/sbin/matchpathcon</code> <code class="option">-V</code> compara el contexto SELinux actual con el contexto predeterminado correcto dado por la política de SELinux. Ejecute el comando <code class="command">/usr/sbin/matchpathcon -V /var/www/html/*</code> para chequear todos los archivos del directorio <code class="filename">/var/www/html/</code>:
 					</div><pre class="screen">$ /usr/sbin/matchpathcon -V /var/www/html/*
 /var/www/html/file1 has context unconfined_u:object_r:samba_share_t:s0, should be system_u:object_r:httpd_sys_content_t:s0
 /var/www/html/file2 verified.
 /var/www/html/file3 verified.
 
 </pre></li></ol></div><div class="para">
-				The following output from the <code class="command">/usr/sbin/matchpathcon</code> command explains that <code class="filename">file1</code> is labeled with the <code class="computeroutput">samba_share_t</code> type, but should be labeled with the <code class="computeroutput">httpd_sys_content_t</code> type:
+				La siguiente salida del comando <code class="command">/usr/sbin/matchpathcon</code> explica que el <code class="filename">archivo1</code> está etiquetado con el tipo <code class="computeroutput">samba_share_t</code>, pero debería estar etiquetado con el tipo <code class="computeroutput">httpd_sys_content_t</code>:
 			</div><pre class="screen">/var/www/html/file1 has context unconfined_u:object_r:samba_share_t:s0, should be system_u:object_r:httpd_sys_content_t:s0
 
 </pre><div class="para">
-				To resolve the label problem and allow the Apache HTTP Server access to <code class="filename">file1</code>, as the Linux root user, run the <code class="command">/sbin/restorecon -v /var/www/html/file1</code> command:
+				Para resolver el problema de etiqueta y permitir al Servidor HTTP Apache acceder a <code class="filename">archivo1</code>, como usuario root de Linux corra el comando <code class="command">/sbin/restorecon -v /var/www/html/archivo1</code>:
 			</div><pre class="screen"># /sbin/restorecon -v /var/www/html/file1
 restorecon reset /var/www/html/file1 context unconfined_u:object_r:samba_share_t:s0-&gt;system_u:object_r:httpd_sys_content_t:s0
 
-</pre></div><div class="section" title="5.10.4. Archiving Files with tar" id="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_tar"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.10.4. Archiving Files with tar</h3></div></div></div><div class="para">
-				<code class="command">tar</code> does not retain extended attributes by default. Since SELinux contexts are stored in extended attributes, contexts can be lost when archiving files. Use <code class="command">tar --selinux</code> to create archives that retain contexts. If a Tar archive contains files without extended attributes, or if you want the extended attributes to match the system defaults, run the archive through <code class="command">/sbin/restorecon</code>:
+</pre></div><div class="section" title="5.10.4. Archivando archivos con tar" id="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_tar"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.10.4. Archivando archivos con tar</h3></div></div></div><div class="para">
+				<code class="command">tar</code> no retiene los atributos extendidos por defecto. Dado que los contextos SELinux se almacenan en los atributos extendidos, los contextos se pueden perder cuando se compactan archivos. Use <code class="command">tar --selinux</code> para crear archivos que retengan los contextos. Si un archivo Tar contiene archivos sin los atributos extendidos, o si quiere que los atributos extendidos coincidan con los predeterminados del sistema, ejecute el archivado a través de <code class="command">/sbin/restorecon</code>:
 			</div><pre class="screen">
 $ tar -xvf <em class="replaceable"><code>archive.tar</code></em> | /sbin/restorecon -f -
 
 </pre><div class="para">
-				Note: depending on the directory, you may need to be the Linux root user to run the <code class="command">/sbin/restorecon</code> command.
+				Nota: dependiendo del directorio, puede necesitar ser el usuario root de Linux para ejecutar el comando <code class="command">/sbin/restorecon</code>.
 			</div><div class="para">
-				The following example demonstrates creating a Tar archive that retains SELinux contexts:
+				El siguiente ejemplo muestra la creación de un archivo Tar que mantiene sus contextos SELinux:
 			</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">touch /var/www/html/file{1,2,3}</code> command to create three files (<code class="filename">file1</code>, <code class="filename">file2</code>, and <code class="filename">file3</code>). These files inherit the <code class="computeroutput">httpd_sys_content_t</code> type from the <code class="filename">/var/www/html/</code> directory:
+						Como usuario root de Linux, ejecute el comando <code class="command">touch /var/www/html/archivo{1,2,3}</code> para crear tres archivos (<code class="filename">archivo1</code>, <code class="filename">archivo2</code> y <code class="filename">archivo3</code>). Estos heredan el tipo <code class="computeroutput">httpd_sys_content_t</code> del directorio <code class="filename">/var/www/html/</code>:
 					</div><pre class="screen">
 # touch /var/www/html/file{1,2,3}
 # ls -Z /var/www/html/
@@ -1412,15 +1412,15 @@ $ tar -xvf <em class="replaceable"><code>archive.tar</code></em> | /sbin/restore
 -rw-r--r--  root root unconfined_u:object_r:httpd_sys_content_t:s0 file3
 
 </pre></li><li class="listitem"><div class="para">
-						Run the <code class="command">cd /var/www/html/</code> command to change into the <code class="filename">/var/www/html/</code> directory. Once in this directory, as the Linux root user, run the <code class="command">tar --selinux -cf test.tar file{1,2,3}</code> command to create a Tar archive named <code class="filename">test.tar</code>.
+						Ejecute el comando <code class="command">cd /var/www/html/</code> para cambiar al directorio <code class="filename">/var/www/html/</code>. Una vez en este directorio, como usuario root de Linux ejecute el comando <code class="command">tar --selinux -cf prueba.tar archivo{1,2,3}</code> para crear un archivo Tar con nombre <code class="filename">prueba.tar</code>.
 					</div></li><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">mkdir /test</code> command to create a new directory, and then, run the <code class="command">chmod 777 /test/</code> command to allow all users full-access to the <code class="filename">/test/</code> directory.
+						Como usuario root de Linux, corra el comando <code class="command">mkdir /prueba</code> para crear un directorio nuevo, y luego ejecute el comando <code class="command">chmod 777 /prueba/</code> para permitir a los usuarios acceso total al directorio <code class="filename">/prueba/</code>.
 					</div></li><li class="listitem"><div class="para">
-						Run the <code class="command">cp /var/www/html/test.tar /test/</code> command to copy the <code class="filename">test.tar</code> file in to the <code class="filename">/test/</code> directory.
+						Ejecute el comando <code class="command">cp /var/www/html/prueba.tar /prueba/</code> para copiar el archivo <code class="filename">prueba.tar</code> en el directorio <code class="filename">/prueba/</code>.
 					</div></li><li class="listitem"><div class="para">
-						Run the <code class="command">cd /test/</code> command to change into the <code class="filename">/test/</code> directory. Once in this directory, run the <code class="command">tar -xvf test.tar</code> command to extract the Tar archive.
+						Ejecute el comando <code class="command">cd /prueba/</code> para cambiar al directorio <code class="filename">/test/</code>. Una vez ahí, ejecute el comando <code class="command">tar -xvf prueba.tar</code> para extraer el archivo Tar.
 					</div></li><li class="listitem"><div class="para">
-						Run the <code class="command">ls -lZ /test/</code> command to view the SELinux contexts. The <code class="computeroutput">httpd_sys_content_t</code> type has been retained, rather than being changed to <code class="computeroutput">default_t</code>, which would have happened had the <code class="option">--selinux</code> not been used:
+						Ejecute el comando <code class="command">ls -lZ /prueba/</code> para ver los contextos SELinux. El tipo <code class="computeroutput">httpd_sys_content_t</code> fue retenido, en vez de haberse cambiado al <code class="computeroutput">default_t</code>, lo que hubiera pasado si la opción <code class="option">--selinux</code> no se hubiera usado:
 					</div><pre class="screen">
 $ ls -lZ /test/
 -rw-r--r--  user1 group1 unconfined_u:object_r:httpd_sys_content_t:s0 file1
@@ -1429,15 +1429,15 @@ $ ls -lZ /test/
 -rw-r--r--  user1 group1 unconfined_u:object_r:default_t:s0 test.tar
 
 </pre></li><li class="listitem"><div class="para">
-						If the <code class="filename">/test/</code> directory is no longer required, as the Linux root user, run the <code class="command"> rm -ri /test/</code> command to remove it, as well as all files in it.
+						Si el directorio <code class="filename">/prueba/</code> no se necesita más, como usuario root de Linux ejecute el comando <code class="command"> rm -ri /prueba/</code> para eliminarlo, así como todos los archivos en él.
 					</div></li></ol></div><div class="para">
-				Refer to the <span class="citerefentry"><span class="refentrytitle">tar</span>(1)</span> manual page for further information about <code class="command">tar</code>, such as the <code class="option">--xattrs</code> option that retains all extended attributes.
-			</div></div><div class="section" title="5.10.5. Archiving Files with star" id="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_star"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.10.5. Archiving Files with star</h3></div></div></div><div class="para">
-				<code class="command">star</code> does not retain extended attributes by default. Since SELinux contexts are stored in extended attributes, contexts can be lost when archiving files. Use <code class="command">star -xattr -H=exustar</code> to create archives that retain contexts. The <span class="package">star</span> package is not installed by default. To install <code class="command">star</code>, run the <code class="command">yum install star</code> command as the Linux root user.
+				Vaya a la página man de <span class="citerefentry"><span class="refentrytitle">tar</span>(1)</span> para información adicional de <code class="command">tar</code>, tal como la opción <code class="option">--xattrs</code> para retener todos los atributos extendidos.
+			</div></div><div class="section" title="5.10.5. Archivando archivos con tar" id="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_star"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.10.5. Archivando archivos con tar</h3></div></div></div><div class="para">
+				<code class="command">star</code> no retiene los atributos extendidos por defecto. Dado que los contextos SELinux se almacenan en los atributos extendidos, los contextos se pueden perder cuando se crean esos archivos. Use <code class="command">star -xattr -H=exustar</code> para crear archivos que retengan los contextos. El paquete <span class="package">star</span> no se instala por defecto. Para instalar <code class="command">star</code>, ejecute el comando <code class="command">yum install star</code> como usuario root de Linux.
 			</div><div class="para">
-				The following example demonstrates creating a Star archive that retains SELinux contexts:
+				El siguiente ejemplo muestra la creación de un archivo Star que retiene los contextos SELinux:
 			</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">touch /var/www/html/file{1,2,3}</code> command to create three files (<code class="filename">file1</code>, <code class="filename">file2</code>, and <code class="filename">file3</code>). These files inherit the <code class="computeroutput">httpd_sys_content_t</code> type from the <code class="filename">/var/www/html/</code> directory:
+						Como usuario root de Linux, ejecute el comando <code class="command">touch /var/www/html/archivo{1,2,3}</code> para crear tres archivos (<code class="filename">archivo1</code>, <code class="filename">archivo2</code> y <code class="filename">archivo3</code>). Estos heredan el tipo <code class="computeroutput">httpd_sys_content_t</code> del directorio <code class="filename">/var/www/html/</code>:
 					</div><pre class="screen">
 # touch /var/www/html/file{1,2,3}
 # ls -Z /var/www/html/
@@ -1446,23 +1446,23 @@ $ ls -lZ /test/
 -rw-r--r--  root root unconfined_u:object_r:httpd_sys_content_t:s0 file3
 
 </pre></li><li class="listitem"><div class="para">
-						Run the <code class="command">cd /var/www/html/</code> command to change into the <code class="filename">/var/www/html/</code> directory. Once in this directory, as the Linux root user, run the <code class="command">star -xattr -H=exustar -c -f=test.star file{1,2,3}</code> command to create a Star archive named <code class="filename">test.star</code>:
+						Ejecute el comando <code class="command">cd /var/www/html/</code> para cambiar al directorio <code class="filename">/var/www/html/</code>. Una vez en este directorio, como usuario root de Linux ejecute el comando <code class="command">star -xattr -H=exustar -c -f=prueba.star archivo{1,2,3}</code> para crear un archivo Star llamado <code class="filename">prueba.star</code>:
 					</div><pre class="screen">
 # star -xattr -H=exustar -c -f=test.star file{1,2,3}
 star: 1 blocks + 0 bytes (total of 10240 bytes = 10.00k).
 
 </pre></li><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">mkdir /test</code> command to create a new directory, and then, run the <code class="command">chmod 777 /test/</code> command to allow all users full-access to the <code class="filename">/test/</code> directory.
+						Como usuario root de Linux, corra el comando <code class="command">mkdir /prueba</code> para crear un directorio nuevo, y luego ejecute el comando <code class="command">chmod 777 /prueba/</code> para permitir a los usuarios acceso total al directorio <code class="filename">/prueba/</code>.
 					</div></li><li class="listitem"><div class="para">
-						Run the <code class="command">cp /var/www/html/test.star /test/</code> command to copy the <code class="filename">test.star</code> file in to the <code class="filename">/test/</code> directory.
+						Ejecute el comando <code class="command">cp /var/www/html/prueba.star /prueba/</code> para copiar el archivo <code class="filename">prueba.star</code> al directorio <code class="filename">/prueba/</code>.
 					</div></li><li class="listitem"><div class="para">
-						Run the <code class="command">cd /test/</code> command to change into the <code class="filename">/test/</code> directory. Once in this directory, run the <code class="command">star -x -f=test.star</code> command to extract the Star archive:
+						Ejecute el comando <code class="command">cd /prueba/</code> para cambiar al directorio <code class="filename">/prueba/</code>. Una vez ahí, ejecute el comando <code class="command">star -x -f=prueba.star</code> para extraer el archivo Star:
 					</div><pre class="screen">
 $ star -x -f=test.star 
 star: 1 blocks + 0 bytes (total of 10240 bytes = 10.00k).
 
 </pre></li><li class="listitem"><div class="para">
-						Run the <code class="command">ls -lZ /test/</code> command to view the SELinux contexts. The <code class="computeroutput">httpd_sys_content_t</code> type has been retained, rather than being changed to <code class="computeroutput">default_t</code>, which would have happened had the <code class="option">--selinux</code> not been used:
+						Ejecute el comando <code class="command">ls -lZ /prueba/</code> para ver los contextos SELinux. El tipo <code class="computeroutput">httpd_sys_content_t</code> fue retenido, en vez de haberse cambiado al <code class="computeroutput">default_t</code>, lo que hubiera pasado si la opción <code class="option">--selinux</code> no se hubiera usado:
 					</div><pre class="screen">
 $ ls -lZ /test/
 -rw-r--r--  user1 group1 unconfined_u:object_r:httpd_sys_content_t:s0 file1
@@ -1471,27 +1471,27 @@ $ ls -lZ /test/
 -rw-r--r--  user1 group1 unconfined_u:object_r:default_t:s0 test.star
 
 </pre></li><li class="listitem"><div class="para">
-						If the <code class="filename">/test/</code> directory is no longer required, as the Linux root user, run the <code class="command"> rm -ri /test/</code> command to remove it, as well as all files in it.
+						Si el directorio <code class="filename">/prueba/</code> no se necesita más, como usuario root de Linux ejecute el comando <code class="command"> rm -ri /prueba/</code> para eliminarlo, así como todos los archivos en él.
 					</div></li><li class="listitem"><div class="para">
-						If <code class="command">star</code> is no longer required, as the Linux root user, run the <code class="command">yum remove star</code> command to remove the package.
+						Si <code class="command">star</code> ya no se necesita, como usuario root de Linux, ejecute el comando <code class="command">yum remove star</code> para eliminar el paquete.
 					</div></li></ol></div><div class="para">
-				Refer to the <span class="citerefentry"><span class="refentrytitle">star</span>(1)</span> manual page for further information about <code class="command">star</code>.
-			</div></div></div><div class="footnotes"><br /><hr width="100" align="left" /><div class="footnote"><p><sup>[<a id="ftn.id1588199" href="#id1588199" class="para">8</a>] </sup>
+				Vaya a la página man de <span class="citerefentry"><span class="refentrytitle">star</span>(1)</span> para más información acerca de <code class="command">star</code>.
+			</div></div></div><div class="footnotes"><br /><hr width="100" align="left" /><div class="footnote"><p><sup>[<a id="ftn.id820736" href="#id820736" class="para">8</a>] </sup>
 				Brindle, Joshua. "Re: blurb for fedora setools packages" Email to Murray McAllister. 1 November 2008. Any edits or changes in this version were done by Murray McAllister.
-			</p></div><div class="footnote"><p><sup>[<a id="ftn.id708842" href="#id708842" class="para">9</a>] </sup>
-				Managing Software with yum, written by Stuart Ellis, edited by Paul W. Frields, Rodrigo Menezes, and Hugo Cisneiros.
-			</p></div><div class="footnote"><p><sup>[<a id="ftn.id556305" href="#id556305" class="para">10</a>] </sup>
+			</p></div><div class="footnote"><p><sup>[<a id="ftn.id778158" href="#id778158" class="para">9</a>] </sup>
+				Administración de Software con yum, escrito por Stuart Ellis, editado por Paul W. Frields, Rodrigo Menezes y Hugo Cisneiros.
+			</p></div><div class="footnote"><p><sup>[<a id="ftn.id852675" href="#id852675" class="para">10</a>] </sup>
 							Refer to <a href="http://en.wikipedia.org/wiki/Runlevel">http://en.wikipedia.org/wiki/Runlevel</a> for information about runlevels.
-						</p></div><div class="footnote"><p><sup>[<a id="ftn.id1847598" href="#id1847598" class="para">11</a>] </sup>
-				Files in <code class="filename">/etc/selinux/targeted/contexts/files/</code> define contexts for files and directories. Files in this directory are read by <code class="command">restorecon</code> and <code class="command">setfiles</code> to restore files and directories to their default contexts.
-			</p></div><div class="footnote"><p><sup>[<a id="ftn.id546655" href="#id546655" class="para">12</a>] </sup>
+						</p></div><div class="footnote"><p><sup>[<a id="ftn.id890908" href="#id890908" class="para">11</a>] </sup>
+				Los archivos en <code class="filename">/etc/selinux/targeted/contexts/files/</code> definen los contextos de los archivos y directorios. Los archivos en este directorio son accedidos por <code class="command">restorecon</code> y por <code class="command">setfiles</code> para restaurar al valor predeterminado los contextos de los archivos y directorios.
+			</p></div><div class="footnote"><p><sup>[<a id="ftn.id891190" href="#id891190" class="para">12</a>] </sup>
 							Morris, James. "Filesystem Labeling in SELinux". Published 1 October 2004. Accessed 14 October 2008: <a href="http://www.linuxjournal.com/article/7426">http://www.linuxjournal.com/article/7426</a>.
-						</p></div><div class="footnote"><p><sup>[<a id="ftn.id673095" href="#id673095" class="para">13</a>] </sup>
+						</p></div><div class="footnote"><p><sup>[<a id="ftn.id780065" href="#id780065" class="para">13</a>] </sup>
 					The <span class="citerefentry"><span class="refentrytitle">matchpathcon</span>(8)</span> manual page, as shipped with the <span class="package">libselinux-utils</span> package in Fedora, is written by Daniel Walsh. Any edits or changes in this version were done by Murray McAllister.
-				</p></div></div></div><div xml:lang="es-ES" class="chapter" title="Capítulo 6. Confining Users" id="chap-Security-Enhanced_Linux-Confining_Users" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 6. Confining Users</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Confining_Users-Linux_and_SELinux_User_Mappings">6.1. Linux and SELinux User Mappings</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Confining_Users-Confining_New_Linux_Users_useradd">6.2. Confining New Linux Users: useradd</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Confining_Users-Confining_Existing_Linux_Users_semanage_login">6.3. Confining Existing Linux Users: semanage login</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Confining_Users-Changing_the_Default_Mapping">6.4. Changing the Default Mapping</a></span></dt><dt><span 
 class="section"><a href="#sect-Security-Enhanced_Linux-Confining_Users-xguest_Kiosk_Mode">6.5. xguest: Kiosk Mode</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications">6.6. Booleans for Users Executing Applications</a></span></dt></dl></div><div class="para">
-		A number of confined SELinux users are available in Fedora 11. Each Linux user is mapped to an SELinux user via SELinux policy, allowing Linux users to inherit the restrictions on SELinux users, for example (depending on the user), not being able to: run the X Window System; use networking; run setuid applications (unless SELinux policy permits it); or run the <code class="command">su</code> and <code class="command">sudo</code> commands to become the Linux root user. This helps protect the system from the user. Refer to <a class="xref" href="#sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users" title="4.3. Confined and Unconfined Users">Sección 4.3, “Confined and Unconfined Users”</a> for further information about confined users in Fedora 11.
-	</div><div class="section" title="6.1. Linux and SELinux User Mappings" id="sect-Security-Enhanced_Linux-Confining_Users-Linux_and_SELinux_User_Mappings"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.1. Linux and SELinux User Mappings</h2></div></div></div><div class="para">
-			As the Linux root user, run the <code class="command">semanage login -l</code> command to view the mapping between Linux users and SELinux users:
+				</p></div></div></div><div xml:lang="es-ES" class="chapter" title="Capítulo 6. Confinando a los Usuarios" id="chap-Security-Enhanced_Linux-Confining_Users" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 6. Confinando a los Usuarios</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Confining_Users-Linux_and_SELinux_User_Mappings">6.1. Linux y los Mapeos de Usuarios de SELinux</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Confining_Users-Confining_New_Linux_Users_useradd">6.2. Confinando Usuarios Nuevos de Linux: useradd</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Confining_Users-Confining_Existing_Linux_Users_semanage_login">6.3. Confinando Usuarios Linux Existentes: semanage login</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Confining_Users-Changing_the_Default_Mapping">6.4. Cambiand
 o el Mapeo Predeterminado</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Confining_Users-xguest_Kiosk_Mode">6.5. xguest: Modo Kiosk</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications">6.6. Booleanos para que los Usuarios Ejecuten Aplicaciones</a></span></dt></dl></div><div class="para">
+		A number of confined SELinux users are available in Fedora 11. Each Linux user is mapped to an SELinux user via SELinux policy, allowing Linux users to inherit the restrictions on SELinux users, for example (depending on the user), not being able to: run the X Window System; use networking; run setuid applications (unless SELinux policy permits it); or run the <code class="command">su</code> and <code class="command">sudo</code> commands to become the Linux root user. This helps protect the system from the user. Refer to <a class="xref" href="#sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users" title="4.3. Usuarios Confinados y no Confinados">Sección 4.3, “Usuarios Confinados y no Confinados”</a> for further information about confined users in Fedora 11.
+	</div><div class="section" title="6.1. Linux y los Mapeos de Usuarios de SELinux" id="sect-Security-Enhanced_Linux-Confining_Users-Linux_and_SELinux_User_Mappings"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.1. Linux y los Mapeos de Usuarios de SELinux</h2></div></div></div><div class="para">
+			Como usuario root de Linux, corra el comando <code class="command">semanage login -l</code> para ver el mapeo entre los usuarios de Linux y los usuarios de SELinux:
 		</div><pre class="screen"># /usr/sbin/semanage login -l
 
 Login Name                SELinux User              MLS/MCS Range
@@ -1501,24 +1501,24 @@ root                      unconfined_u              s0-s0:c0.c1023
 system_u                  system_u                  s0-s0:c0.c1023
 
 </pre><div class="para">
-			In Fedora 11, Linux users are mapped to the SELinux <code class="computeroutput">__default__</code> login by default (which is mapped to the SELinux <code class="computeroutput">unconfined_u</code> user). When a Linux user is created with the <code class="command">useradd</code> command, if no options are specified, they are mapped to the SELinux <code class="computeroutput">unconfined_u</code> user. The following defines the default-mapping:
+			En Fedora 11, los usuarios Linux se mapean al ingreso SELinux <code class="computeroutput">__default__</code> por defecto (que se mapea al usuario SELinux <code class="computeroutput">unconfined_u</code>). Cuando se crea un usuario Linux con el comando <code class="command">useradd</code>, si no se especifica ninguna opcion, son mapeados al usuario SELinux <code class="computeroutput">unconfined_u</code>. Lo siguiente define el mapeo por defecto:
 		</div><pre class="screen">
 __default__               unconfined_u              s0-s0:c0.c1023
 
-</pre></div><div class="section" title="6.2. Confining New Linux Users: useradd" id="sect-Security-Enhanced_Linux-Confining_Users-Confining_New_Linux_Users_useradd"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.2. Confining New Linux Users: useradd</h2></div></div></div><div class="para">
-			Linux users mapped to the SELinux <code class="computeroutput">unconfined_u</code> user run in the <code class="computeroutput">unconfined_t</code> domain. This is seen by running the <code class="command">id -Z</code> command while logged-in as a Linux user mapped to <code class="computeroutput">unconfined_u</code>:
+</pre></div><div class="section" title="6.2. Confinando Usuarios Nuevos de Linux: useradd" id="sect-Security-Enhanced_Linux-Confining_Users-Confining_New_Linux_Users_useradd"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.2. Confinando Usuarios Nuevos de Linux: useradd</h2></div></div></div><div class="para">
+			Los usuarios Linux mapeados al usuario SELinux <code class="computeroutput">unconfined_u</code> corren en el dominio <code class="computeroutput">unconfined_t</code>. Esto se ve ejecutando el comando <code class="command">id -Z</code> luego de haber ingresado como el usuario Linux que se mapea a <code class="computeroutput">unconfined_u</code>:
 		</div><pre class="screen">
 $ id -Z
 unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
 
 </pre><div class="para">
-			When Linux users run in the <code class="computeroutput">unconfined_t</code> domain, SELinux policy rules are applied, but policy rules exist that allow Linux users running in the <code class="computeroutput">unconfined_t</code> domain almost all access. If unconfined Linux users execute an application that SELinux policy defines can transition from the <code class="computeroutput">unconfined_t</code> domain to its own confined domain, unconfined Linux users are still subject to the restrictions of that confined domain. The security benefit of this is that, even though a Linux user is running unconfined, the application remains confined, and therefore, the exploitation of a flaw in the application can be limited by policy. Note: this does not protect the system from the user. Instead, the user and the system are being protected from possible damage caused by a flaw in the application.
+			Cuando los usuarios linux ejecuten en el dominio <code class="computeroutput">unconfined_t</code>, se aplican las reglas de la política de SELinux, pero las reglas de políticas que existen para usuarios Linux que corren en el dominio <code class="computeroutput">unconfined_t</code> permiten casi todos los accesos. Si los usuarios Linux no confinados ejecutan una aplicación que la política de SELinux define pueden transicionar desde el dominio <code class="computeroutput">unconfined_t</code> a su propio dominio confinado, los usuarios Linux no confinados todavía pueden ser sujetos a restricciones del dominio confinado. El beneficio de seguridad de esto es que, aunque el usuario Linux corre en un dominio confinado, la aplicación permanece confinada, y por lo tanto, la explotación de una brecha en la aplicación se puede limitar por la política. Nota: esto no protege al sistema del usuario. En su lugar, el usuario y el sistema están siendo protegido de posibles dañ
 os causados en alguna debilidad en la aplicación.
 		</div><div class="para">
-			When creating Linux users with <code class="command">useradd</code>, use the <code class="option">-Z</code> option to specify which SELinux user they are mapped to. The following example creates a new Linux user, useruuser, and maps that user to the SELinux <code class="computeroutput">user_u</code> user. Linux users mapped to the SELinux <code class="computeroutput">user_u</code> user run in the <code class="computeroutput">user_t</code> domain. In this domain, Linux users are unable to run setuid applications unless SELinux policy permits it (such as <code class="command">passwd</code>), and can not run <code class="command">su</code> or <code class="command">sudo</code>, preventing them from becoming the Linux root user with these commands.
+			Cuando se crean usuarios LInux con <code class="command">useradd</code>, use la opción <code class="option">-Z</code> para especificar a qué usuario SELinux se debe mapear. El siguiente ejemplo crea un usuario Linux nuevo, useruuser, y mapea ese usuario al usuario SELinux <code class="computeroutput">user_u</code>. Los usuarios Linux mapeados al usuario SELinux <code class="computeroutput">user_u</code> corren en el dominio <code class="computeroutput">user_t</code>. En este dominio, los usuarios Linux no pueden correr aplicaciones setuid a menos que la política de SELinux lo permita (tal como <code class="command">passwd</code>), y tampoco pueden correr <code class="command">su</code> o <code class="command">sudo</code>, lo que evita que se puedan volver usuarios root de Linux con estos comandos.
 		</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
-					As the Linux root user, run the <code class="command">/usr/sbin/useradd -Z user_u useruuser</code> command to create a new Linux user (useruuser) that is mapped to the SELinux <code class="computeroutput">user_u</code> user.
+					Como usuario root de Linux, corra el comando <code class="command">/usr/sbin/useradd -Z user_u useruuser</code> para crear el usuario Linux nuevo (useruuser) que se mapeará al usuario SELinux <code class="computeroutput">user_u</code>.
 				</div></li><li class="listitem"><div class="para">
-					As the Linux root user, run the <code class="command">semanage login -l</code> command to view the mapping between the Linux <code class="computeroutput">useruuser</code> user and <code class="computeroutput">user_u</code>:
+					Como usuario root de Linux, corra el comando <code class="command">semanage login -l</code> para ver el mapeo entre el usuario Linux <code class="computeroutput">useruuser</code> y <code class="computeroutput">user_u</code>:
 				</div><pre class="screen">
 # /usr/sbin/semanage login -l
 
@@ -1530,7 +1530,7 @@ system_u                  system_u                  s0-s0:c0.c1023
 useruuser                 user_u                    s0
 
 </pre></li><li class="listitem"><div class="para">
-					As the Linux root user, run the <code class="command">passwd useruuser</code> command to assign a password to the Linux useruuser user:
+					Como usuario root de Linux, corra el comando <code class="command">passwd useruuser</code> para asignar una contraseña para el usuario useruuser de Linux:
 				</div><pre class="screen">
 # passwd useruuser
 Changing password for user useruuser.
@@ -1539,17 +1539,17 @@ Retype new UNIX password: <em class="replaceable"><code>Enter the same password
 passwd: all authentication tokens updated successfully.
 
 </pre></li><li class="listitem"><div class="para">
-					Log out of your current session, and log in as the Linux useruuser user. When you log in, pam_selinux maps the Linux user to an SELinux user (in this case, <code class="computeroutput">user_u</code>), and sets up the resulting SELinux context. The Linux user's shell is then launched with this context. Run the <code class="command">id -Z</code> command to view the context of a Linux user:
+					Salga de su sesión actual, e ingrese como el usuario useruuser de Linux. Cuando ingrese, pam_selinux mapea el usuario Linux a un usuario SELinux (en este caso, <code class="computeroutput">user_u</code>), y configura el contexto SELinux resultante. El shell del usuario Linux es luego lanzado con este contexto. Corra el comando <code class="command">id -Z</code> para ver el contexto de un usuario Linux:
 				</div><pre class="screen">
 [useruuser at localhost ~]$ id -Z
 user_u:user_r:user_t:s0
 
 </pre></li><li class="listitem"><div class="para">
-					Log out of the Linux useruuser's session, and log back in with your account. If you do not want the Linux useruuser user, run the <code class="command">/usr/sbin/userdel -r useruuser</code> command as the Linux root user to remove it, along with its home directory.
-				</div></li></ol></div></div><div class="section" title="6.3. Confining Existing Linux Users: semanage login" id="sect-Security-Enhanced_Linux-Confining_Users-Confining_Existing_Linux_Users_semanage_login"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.3. Confining Existing Linux Users: semanage login</h2></div></div></div><div class="para">
-			If a Linux user is mapped to the SELinux <code class="computeroutput">unconfined_u</code> user (the default behavior), and you would like to change which SELinux user they are mapped to, use the <code class="command">semanage login</code> command. The following example creates a new Linux user named newuser, then maps that Linux user to the SELinux <code class="computeroutput">user_u</code> user:
+					Salga de la sesión useruuser de Linux, y vuelva a ingresar en su cuenta. Si no quiere el usuario useruuser, ejecute el comando <code class="command">/usr/sbin/userdel -r useruuser</code> como usuario root de Linux para borrarlo junto con su directorio de inicio.
+				</div></li></ol></div></div><div class="section" title="6.3. Confinando Usuarios Linux Existentes: semanage login" id="sect-Security-Enhanced_Linux-Confining_Users-Confining_Existing_Linux_Users_semanage_login"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.3. Confinando Usuarios Linux Existentes: semanage login</h2></div></div></div><div class="para">
+			Si un usuario Linux se mapea al usuario <code class="computeroutput">unconfined_u</code> (el comportamiento predeterminado), y desea cambiar le usuario SELinux al que se mapea, use el comando <code class="command">semanage login</code>. El siguiente ejemplo crea un usuario de Linux nuevo llamado usuarionuevo, luego lo mapea al usuario SELinux <code class="computeroutput">user_u</code>:
 		</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
-					As the Linux root user, run the <code class="command">/usr/sbin/useradd newuser</code> command to create a new Linux user (newuser). Since this user uses the default mapping, it does not appear in the <code class="command">/usr/sbin/semanage login -l</code> output:
+					Como usuario root de Linux, ejecute el comando <code class="command">/usr/sbin/useradd usuarionuevo</code> para crear un nuevo usuario (usuarionuevo). Dado que este usuario usa el mapeo por defecto, no aparece en la salida de <code class="command">/usr/sbin/semanage login -l</code>:
 				</div><pre class="screen">
 # /usr/sbin/semanage login -l
 
@@ -1560,13 +1560,13 @@ root                      unconfined_u              s0-s0:c0.c1023
 system_u                  system_u                  s0-s0:c0.c1023
 
 </pre></li><li class="listitem"><div class="para">
-					To map the Linux newuser user to the SELinux <code class="computeroutput">user_u</code> user, run the following command as the Linux root user:
+					Para mapear un usuario usuarionuevo de Linux al usuario <code class="computeroutput">user_u</code> de SELinux, corra el siguiente comando como usuario root de Linux:
 				</div><div class="para">
 					<code class="command">/usr/sbin/semanage login -a -s user_u newuser</code>
 				</div><div class="para">
-					The <code class="option">-a</code> option adds a new record, and the <code class="option">-s</code> option specifies the SELinux user to map a Linux user to. The last argument, <code class="computeroutput">newuser</code>, is the Linux user you want mapped to the specified SELinux user.
+					La opción <code class="option">-a</code> agrega un registro nuevo y la opción <code class="option">-s</code> especifica el usuario SELinux al que mapea el usuario Linux. El último argumento <code class="computeroutput">usuarionuevo</code>, es el usuario Linux al que quiere que se mapee el usuario SELinux especificado.
 				</div></li><li class="listitem"><div class="para">
-					To view the mapping between the Linux newuser user and <code class="computeroutput">user_u</code>, run the <code class="command">semanage login -l</code> command as the Linux root user:
+					Para ver el mapeo entre el usuario usarionuevo de Linux y <code class="computeroutput">user_u</code>, corra el comando <code class="command">semanage login -l</code> como usuario root de Linux:
 				</div><pre class="screen">
 # /usr/sbin/semanage login -l
 
@@ -1587,13 +1587,13 @@ Retype new UNIX password: <em class="replaceable"><code>Enter the same password
 passwd: all authentication tokens updated successfully.
 
 </pre></li><li class="listitem"><div class="para">
-					Log out of your current session, and log in as the Linux newuser user. Run the <code class="command">id -Z</code> command to view the newuser's SELinux context:
+					Salga de su sesión actual e ingrese como el usuario de Linux usuarionuevo. Corra el comando <code class="command">id -Z</code> para ver el contexto SELinux de usuarionuevo:
 				</div><pre class="screen">
 [newuser at rlocalhost ~]$ id -Z
 user_u:user_r:user_t:s0
 
 </pre></li><li class="listitem"><div class="para">
-					Log out of the Linux newuser's session, and log back in with your account. If you do not want the Linux newuser user, run the <code class="command">userdel -r newuser</code> command as the Linux root user to remove it, along with its home directory. Also, the mapping between the Linux newuser user and <code class="computeroutput">user_u</code> is removed:
+					Salga de la sesión de Linux del usuarionuevo y vuelva a ingresar en su cuenta. Si no quiere el usuarionuevo de Linux, corra el comando <code class="command">userdel -r usuarionuevo</code> como usuario root de Linux, junto con su directorio de inicio. También, el mapeo del usuario Linux usuarionuevo y <code class="computeroutput">user_u</code> se elimina:
 				</div><pre class="screen">
 # /usr/sbin/userdel -r newuser
 # /usr/sbin/semanage login -l
@@ -1604,14 +1604,14 @@ __default__               unconfined_u              s0-s0:c0.c1023
 root                      unconfined_u              s0-s0:c0.c1023
 system_u                  system_u                  s0-s0:c0.c1023
 
-</pre></li></ol></div></div><div class="section" title="6.4. Changing the Default Mapping" id="sect-Security-Enhanced_Linux-Confining_Users-Changing_the_Default_Mapping"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.4. Changing the Default Mapping</h2></div></div></div><div class="para">
-			In Fedora 11, Linux users are mapped to the SELinux <code class="computeroutput">__default__</code> login by default (which is mapped to the SELinux <code class="computeroutput">unconfined_u</code> user). If you would like new Linux users, and Linux users not specifically mapped to an SELinux user to be confined by default, change the default mapping with the <code class="command">semanage login</code> command.
+</pre></li></ol></div></div><div class="section" title="6.4. Cambiando el Mapeo Predeterminado" id="sect-Security-Enhanced_Linux-Confining_Users-Changing_the_Default_Mapping"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.4. Cambiando el Mapeo Predeterminado</h2></div></div></div><div class="para">
+			En Fedora 11, los usuarios Linux se mapean al ingreso SELinux <code class="computeroutput">__default__</code> por defecto (que se mapea al usuario SELinux <code class="computeroutput">unconfined_u</code>). Si quiere que los usuarios nuevos de Linux y los usuarios Linux no mapeados específicamente a un usuario SELinux sean confinados por defecto, cambie el mapeo predeterminado con el comando <code class="command">semanage login</code>.
 		</div><div class="para">
-			For example, run the following command as the Linux root user to change the default mapping from <code class="computeroutput">unconfined_u</code> to <code class="computeroutput">user_u</code>:
+			Por ejemplo, corra el siguiente comando como usuario root de Linux para cambiar el mapeo predeterminado de <code class="computeroutput">unconfined_u</code> a <code class="computeroutput">user_u</code>:
 		</div><div class="para">
 			<code class="command">/usr/sbin/semanage login -m -S targeted -s "user_u" -r s0 __default__</code>
 		</div><div class="para">
-			Run the <code class="command">semanage login -l</code> command as the Linux root user to verify the <code class="computeroutput">__default__</code> login is mapped to <code class="computeroutput">user_u</code>:
+			Corra el comando <code class="command">semanage login -l</code> como usuario root de Linux para verificar que el ingreso <code class="computeroutput">__default__</code> se mapea a <code class="computeroutput">user_u</code>:
 		</div><pre class="screen">
 # /usr/sbin/semanage login -l
 
@@ -1622,9 +1622,9 @@ root                      unconfined_u              s0-s0:c0.c1023
 system_u                  system_u                  s0-s0:c0.c1023
 
 </pre><div class="para">
-			If a new Linux user is created and an SELinux user is not specified, or if an existing Linux user logs in and does not match a specific entry from the <code class="command">semanage login -l</code> output, they are mapped to <code class="computeroutput">user_u</code>, as per the <code class="computeroutput">__default__</code> login.
+			Si un usuario Linux nuevo se crea y el usuario SELinux no se especifica, o si un usuario Linux existente ingresa y no coincide una entrada específica de la salida de <code class="command">semanage login -l</code>, se mapean a <code class="computeroutput">user_u</code>, según el ingreso <code class="computeroutput">__default__</code>.
 		</div><div class="para">
-			To change back to the default behavior, run the following command as the Linux root user to map the <code class="computeroutput">__default__</code> login to the SELinux <code class="computeroutput">unconfined_u</code> user:
+			Para volver al comportamiento predeterminado, corra el siguiente comando como usuario root de Linux para mapear el ingreso <code class="computeroutput">__default__</code> al usuario SELinux <code class="computeroutput">unconfined_u</code>:
 		</div><div class="para">
 			
 <pre class="screen">/usr/sbin/semanage login -m -S targeted -s "unconfined_u" -r\
@@ -1632,50 +1632,50 @@ s0-s0:c0.c1023 __default__
 
 </pre>
 
-		</div></div><div class="section" title="6.5. xguest: Kiosk Mode" id="sect-Security-Enhanced_Linux-Confining_Users-xguest_Kiosk_Mode"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.5. xguest: Kiosk Mode</h2></div></div></div><div class="para">
-			The <span class="package">xguest</span> package provides a kiosk user account. This account is used to secure machines that people walk up to and use, such as those at libraries, banks, airports, information kiosks, and coffee shops. The kiosk user account is very locked down: essentially, it only allows users to log in and use <span class="application"><strong>Firefox</strong></span> to browse Internet websites. Any changes made while logged in with his account, such as creating files or changing settings, are lost when you log out.
+		</div></div><div class="section" title="6.5. xguest: Modo Kiosk" id="sect-Security-Enhanced_Linux-Confining_Users-xguest_Kiosk_Mode"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.5. xguest: Modo Kiosk</h2></div></div></div><div class="para">
+			El paquete <span class="package">xguest</span> provee una cuenta de usuario kiosk. Esta cuenta se usa para asegurar máquinas a las que ingresan personas y las usan, como las de las bibliotecas, bancos, aeropuertos, quioscos de información y cyber cafés. La cuenta de usuario kiosk está muy bloqueada: escencialmente, s´olo permite a los usuarios ingresar y usar <span class="application"><strong>Firefox</strong></span> para navegar sitios de Internet. Cualquier cambio hecho mientras se ingresó con esa cuenta, tal como la creación y cambio de la configuración, se pierde cuando se sale.
 		</div><div class="para">
-			To set up the kiosk account:
+			Para configurar la cuenta kiosk:
 		</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
-					As the Linux root user, run <code class="command">yum install xguest</code> command to install the <span class="package">xguest</span> package. Install dependencies as required.
+					Como usuario root de Linux, corra el comando <code class="command">yum install xguest</code> para instalar el paquete <span class="package">xguest</span>. Instale las dependencias requeridas.
 				</div></li><li class="listitem"><div class="para">
-					In order to allow the kiosk account to be used by a variety of people, the account is not password-protected, and as such, the account can only be protected if SELinux is running in enforcing mode. Before logging in with this account, use the <code class="command">getenforce</code> command to confirm that SELinux is running in enforcing mode:
+					Para permitir a la cuenta kiosk usarse para una variedad de personas, la cuenta no se protege con contraseña, y como tal, la cuenta sólo se puede proteger si SELinux está funcionando en modo obediente. Antes de ingresar con esta cuenta, use el comando <code class="command">getenforce</code> para confirmar que SELinux está funcionando en modo obediente:
 				</div><pre class="screen">
 $ /usr/sbin/getenforce
 Enforcing
 
 </pre><div class="para">
-					If this is not the case, refer to <a class="xref" href="#sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes" title="5.5. SELinux Modes">Sección 5.5, “SELinux Modes”</a> for information about changing to enforcing mode. It is not possible to log in with this account if SELinux is in permissive mode or disabled.
+					If this is not the case, refer to <a class="xref" href="#sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes" title="5.5. Modos de SELinux">Sección 5.5, “Modos de SELinux”</a> for information about changing to enforcing mode. It is not possible to log in with this account if SELinux is in permissive mode or disabled.
 				</div></li><li class="listitem"><div class="para">
-					You can only log in to this account via the GNOME Display Manager (GDM). Once the <span class="package">xguest</span> package is installed, a <code class="computeroutput">Guest</code> account is added to GDM. To log in, click on the <code class="computeroutput">Guest</code> account:
-				</div><div class="mediaobject"><img src="./images/xguest.png" /></div></li></ol></div></div><div class="section" title="6.6. Booleans for Users Executing Applications" id="sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.6. Booleans for Users Executing Applications</h2></div></div></div><div class="para">
-			Not allowing Linux users to execute applications (which inherit users' permissions) in their home directories and <code class="filename">/tmp/</code>, which they have write access to, helps prevent flawed or malicious applications from modifying files users' own. In Fedora 11, by default, Linux users in the <code class="computeroutput">guest_t</code> and <code class="computeroutput">xguest_t</code> domains can not execute applications in their home directories or <code class="filename">/tmp/</code>; however, by default, Linux users in the <code class="computeroutput">user_t</code> and <code class="computeroutput">staff_t</code> domains can.
+					Solamente puede ingresar a esta cuenta a través del Administración de Pantalla de GNOME (GDM). Una vez que el paquete <span class="package">xguest</span> se instala, se agrega una cuenta <code class="computeroutput">Invitado</code> a GDM. Para ingresar, haga clic en la cuenta <code class="computeroutput">Invitado</code>:
+				</div><div class="mediaobject"><img src="./images/xguest.png" /></div></li></ol></div></div><div class="section" title="6.6. Booleanos para que los Usuarios Ejecuten Aplicaciones" id="sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.6. Booleanos para que los Usuarios Ejecuten Aplicaciones</h2></div></div></div><div class="para">
+			No permitir que los usuarios Linux ejecuten aplicaciones (que heredan los permisos del usuario) en sus directorios de inicio (home) y <code class="filename">/tmp/</code>, a los que tienen acceso de escritura, lo que ayuda a evitar que aplicaciones con brechas o maliciosas puedan modificar archivos del usuario. En Fedora 11, por defecto, los usuarios Linux en los dominios <code class="computeroutput">guest_t</code> y <code class="computeroutput">xguest_t</code> no pueden ejecutar aplicaciones en los directorios de inicio o en <code class="filename">/tmp/</code>; however, por defecto, los usuarios Linux en los dominios <code class="computeroutput">user_t</code> and <code class="computeroutput">staff_t</code> si pueden.
 		</div><div class="para">
-			Booleans are available to change this behavior, and are configured with the <code class="command">setsebool</code> command. The <code class="command">setsebool</code> command must be run as the Linux root user. The <code class="command">setsebool -P</code> command makes persistent changes. Do not use the <code class="option">-P</code> option if you do not want changes to persist across reboots:
-		</div><div class="formalpara"><h5 class="formalpara">guest_t</h5>
-				To <span class="emphasis"><em>allow</em></span> Linux users in the <code class="computeroutput">guest_t</code> domain to execute applications in their home directories and <code class="filename">/tmp/</code>:
+			Hay booleanos disponibles para cambiar este comportamiento, y se configuran con el comando <code class="command">setsebool</code>. El comando <code class="command">setsebool</code> se debe usar con el usuario root de Linux. El comando <code class="command">setsebool -P</code> hace los cambios persistentes. No use la opción <code class="option">-P</code> si no quiere que los cambios persistan entre reiniciadas:
+		</div><div class="formalpara" id="form-Security-Enhanced_Linux-Booleans_for_Users_Executing_Applications-guest_t"><h5 class="formalpara">guest_t</h5>
+				Para <span class="emphasis"><em>permitir</em></span> a los usuarios Linux en el dominio <code class="computeroutput">guest_t</code> que ejecuten aplicaciones en sus directorios de inicio y en <code class="filename">/tmp/</code>:
 			</div><div class="para">
 			<code class="command">/usr/sbin/setsebool -P allow_guest_exec_content on</code>
-		</div><div class="formalpara"><h5 class="formalpara">xguest_t</h5>
-				To <span class="emphasis"><em>allow</em></span> Linux users in the <code class="computeroutput">xguest_t</code> domain to execute applications in their home directories and <code class="filename">/tmp/</code>:
+		</div><div class="formalpara" id="form-Security-Enhanced_Linux-Booleans_for_Users_Executing_Applications-xguest_t"><h5 class="formalpara">xguest_t</h5>
+				Para <span class="emphasis"><em>permitir</em></span> a los usuarios Linux en el dominio <code class="computeroutput">xguest_t</code> ejecutar aplicaciones en sus directorios inicios y <code class="filename">/tmp/</code>:
 			</div><div class="para">
 			<code class="command">/usr/sbin/setsebool -P allow_xguest_exec_content on</code>
-		</div><div class="formalpara"><h5 class="formalpara">user_t</h5>
-				To <span class="emphasis"><em>prevent</em></span> Linux users in the <code class="computeroutput">user_t</code> domain from executing applications in their home directories and <code class="filename">/tmp/</code>:
+		</div><div class="formalpara" id="form-Security-Enhanced_Linux-Booleans_for_Users_Executing_Applications-user_t"><h5 class="formalpara">user_t</h5>
+				Para <span class="emphasis"><em>impedir</em></span> que los usuarios Linux en el dominio <code class="computeroutput">user_t</code> ejecuten aplicaciones en sus directorios de inicio y <code class="filename">/tmp/</code>:
 			</div><div class="para">
 			<code class="command">/usr/sbin/setsebool -P allow_user_exec_content off</code>
-		</div><div class="formalpara"><h5 class="formalpara">staff_t</h5>
-				To <span class="emphasis"><em>prevent</em></span> Linux users in the <code class="computeroutput">staff_t</code> domain from executing applications in their home directories and <code class="filename">/tmp/</code>:
+		</div><div class="formalpara" id="form-Security-Enhanced_Linux-Booleans_for_Users_Executing_Applications-staff_t"><h5 class="formalpara">staff_t</h5>
+				Para <span class="emphasis"><em>impedir</em></span> que los usuarios Linux en el dominio <code class="computeroutput">staff_t</code> ejecuten aplicaciones en sus directorios de inicio y en <code class="filename">/tmp/</code>:
 			</div><div class="para">
 			<code class="command">/usr/sbin/setsebool -P allow_staff_exec_content off</code>
-		</div></div></div><div xml:lang="es-ES" class="chapter" title="Capítulo 7. Troubleshooting" id="chap-Security-Enhanced_Linux-Troubleshooting" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 7. Troubleshooting</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Troubleshooting-What_Happens_when_Access_is_Denied">7.1. What Happens when Access is Denied</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems">7.2. Top Three Causes of Problems</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Labeling_Problems">7.2.1. Labeling Problems</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running">7.2.2. How are Confined Services Running?</a></span></dt><dt><span class="section"><a 
 href="#sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Evolving_Rules_and_Broken_Applications">7.2.3. Evolving Rules and Broken Applications</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems">7.3. Fixing Problems</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Linux_Permissions">7.3.1. Linux Permissions</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Possible_Causes_of_Silent_Denials">7.3.2. Possible Causes of Silent Denials</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services">7.3.3. Manual Pages for Services</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains">7.3.4. Permissive Domains</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Li
 nux-Fixing_Problems-Searching_For_and_Viewing_Denials">7.3.5. Searching For and Viewing Denials</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages">7.3.6. Raw Audit Messages</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages">7.3.7. sealert Messages</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow">7.3.8. Allowing Access: audit2allow</a></span></dt></dl></dd></dl></div><div class="para">
-		The following chapter describes what happens when SELinux denies access; the top three causes of problems; where to find information about correct labeling; analyzing SELinux denials; and creating custom policy modules with <code class="command">audit2allow</code>.
-	</div><div class="section" title="7.1. What Happens when Access is Denied" id="sect-Security-Enhanced_Linux-Troubleshooting-What_Happens_when_Access_is_Denied"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">7.1. What Happens when Access is Denied</h2></div></div></div><div class="para">
+		</div></div></div><div xml:lang="es-ES" class="chapter" title="Capítulo 7. Solución a Problemas" id="chap-Security-Enhanced_Linux-Troubleshooting" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 7. Solución a Problemas</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Troubleshooting-What_Happens_when_Access_is_Denied">7.1. Qué pasa cuando el Acceso es Denegado</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems">7.2. Tres Principales Causas de Problemas</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Labeling_Problems">7.2.1. Problemas de Etiquetados</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running">7.2.2. ¿Cómo se Ejecutan los Servicios Confinados?</a
 ></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Evolving_Rules_and_Broken_Applications">7.2.3. Evolucionando las Reglas y las Aplicaciones Rotas</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems">7.3. Corrección de Problemas</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Linux_Permissions">7.3.1. Permisos de Linux</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Possible_Causes_of_Silent_Denials">7.3.2. Posibles Causas de las Negaciones Silenciosas</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services">7.3.3. Páginas de Manual para Servicios</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains">7.3.4. Dominios Perm
 isivos</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Searching_For_and_Viewing_Denials">7.3.5. Búsqueda y Revisión de Negaciones</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages">7.3.6. Raw Audit Messages</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages">7.3.7. Mensajes sealert</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow">7.3.8. Permitiendo el Acceso: audit2allow</a></span></dt></dl></dd></dl></div><div class="para">
+		El siguiente capítulo describe qué pasa cuando SELinux niega el acceso; las principales tres causas de problemas; dónde encontrar información acerca del correcto etiquetado; análisis de las negaciones de SELinux; y creación de módulos de políticas personalizados con <code class="command">audit2allow</code>.
+	</div><div class="section" title="7.1. Qué pasa cuando el Acceso es Denegado" id="sect-Security-Enhanced_Linux-Troubleshooting-What_Happens_when_Access_is_Denied"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">7.1. Qué pasa cuando el Acceso es Denegado</h2></div></div></div><div class="para">
 			SELinux decisions, such as allowing or disallowing access, are cached. This cache is known as the Access Vector Cache (AVC). Denial messages are logged when SELinux denies access. These denials are also known as "AVC denials", and are logged to a different location, depending on which daemons are running:
 		</div><div class="segmentedlist"><table border="0"><thead><tr class="segtitle"><th>Daemon</th><th>Log Location</th></tr></thead><tbody><tr class="seglistitem"><td class="seg">auditd on</td><td class="seg"><code class="filename">/var/log/audit/audit.log</code></td></tr><tr class="seglistitem"><td class="seg">auditd off; rsyslogd on</td><td class="seg"><code class="filename">/var/log/messages</code></td></tr><tr class="seglistitem"><td class="seg">setroubleshootd, rsyslogd, and auditd on</td><td class="seg"><code class="filename">/var/log/audit/audit.log</code>. Easier-to-read denial messages also sent to <code class="filename">/var/log/messages</code></td></tr></tbody></table></div><div class="para">
-			If you are running the X Window System, have the <span class="package">setroubleshoot</span> and <span class="package">setroubleshoot-server</span> packages installed, and the <code class="systemitem">setroubleshootd</code> and <code class="systemitem">auditd</code> daemons are running, a yellow star and a warning are displayed when access is denied by SELinux:
+			Si está corriendo el Sistema de Ventanas X, ya tienen los paquetes <span class="package">setroubleshoot</span> y <span class="package">setroubleshoot-server</span> instalados, y los demonios <code class="systemitem">setroubleshootd</code> y <code class="systemitem">auditd</code> están ejecutándose, se muestra una estrella amarilla y una advertencia cuando SELinux deniega el acceso:
 		</div><div class="mediaobject"><img src="./images/setroubleshoot_denial.png" /></div><div class="para">
-			Clicking on the star presents a detailed analysis of why SELinux denied access, and a possible solution for allowing access. If you are not running the X Window System, it is less obvious when access is denied by SELinux. For example, users browsing your website may receive an error similar to the following:
+			Haciendo clic en las estrelas se presenta un análisis detallado de por qué SELinux negó el acceso, y una posible solución para permitir el acceso. Si no está corriendo el Sistema de Ventanas X, es menos obvio cuando un acceso es negado por SELinux. Por ejemplo, los usuarios navegando su sitio web pueden recibir un error similar al siguiente:
 		</div><pre class="screen">
 Forbidden
 
@@ -1687,54 +1687,54 @@ You don't have permission to access <em class="replaceable"><code>file name</cod
 			<code class="command">grep "SELinux is preventing" /var/log/messages</code>
 		</div><div class="para">
 			<code class="command">grep "denied" /var/log/audit/audit.log</code>
-		</div></div><div class="section" title="7.2. Top Three Causes of Problems" id="sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">7.2. Top Three Causes of Problems</h2></div></div></div><div class="para">
-			The following sections describe the top three causes of problems: labeling problems, configuring Booleans and ports for services, and evolving SELinux rules.
-		</div><div class="section" title="7.2.1. Labeling Problems" id="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Labeling_Problems"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.2.1. Labeling Problems</h3></div></div></div><div class="para">
-				On systems running SELinux, all processes and files are labeled with a label that contains security-relevant information. This information is called the SELinux context. If these labels are wrong, access may be denied. If an application is labeled incorrectly, the process it transitions to may not have the correct label, possibly causing SELinux to deny access, and the process being able to create mislabeled files.
+		</div></div><div class="section" title="7.2. Tres Principales Causas de Problemas" id="sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">7.2. Tres Principales Causas de Problemas</h2></div></div></div><div class="para">
+			Las siguientes secciones describen las tres principales causas de problemas: problemas de etiquetados, configuración de Booleanos y puertos para servicios, y la evolución de las reglas SELinux.
+		</div><div class="section" title="7.2.1. Problemas de Etiquetados" id="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Labeling_Problems"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.2.1. Problemas de Etiquetados</h3></div></div></div><div class="para">
+				En sistemas que corren SELinux, todos los procesosy archivos se etiquetan con una etiqueta que contiene información de seguridad relevante. Esta información se llama contexto de SELinux. Si estas etiquetas están mal, el acceso puede ser negado. Si una aplicación se etiqueta incorrectamente, el proceso al que transiciona puede no tener la etiqueta correcta, causando negaciones de acceso de SELinux, y los procesos pueden crear archivo con las etiquetas incorrectas.
 			</div><div class="para">
-				A common cause of labeling problems is when a non-standard directory is used for a service. For example, instead of using <code class="filename">/var/www/html/</code> for a website, an administrator wants to use <code class="filename">/srv/myweb/</code>. On Fedora 11, the <code class="filename">/srv/</code> directory is labeled with the <code class="computeroutput">var_t</code> type. Files and directories created and <code class="filename">/srv/</code> inherit this type. Also, newly-created top-level directories (such as <code class="filename">/myserver/</code>) may be labeled with the <code class="computeroutput">default_t</code> type. SELinux prevents the Apache HTTP Server (<code class="systemitem">httpd</code>) from accessing both of these types. To allow access, SELinux must know that the files in <code class="filename">/srv/myweb/</code> are to be accessible to <code class="systemitem">httpd</code>:
+				Una causa común de problemas de etiquetados es cuando un directorio no estandar se usa para un servicio. Por ejemplo, en vez de usar <code class="filename">/var/www/html/</code> para un sitio web, un administrador prefiere usar <code class="filename">/srv/miweb/</code>. En Fedora 11, el directorio <code class="filename">/srv/</code> se etiqueta con el tipo <code class="computeroutput">var_t</code>. Los archivos y directorios creados en <code class="filename">/srv/</code> heredan este tipo. También, los directorios de alto nivel recién creados (como <code class="filename">/miservidor/</code>) puede ser etiquetado con el tipo <code class="computeroutput">default_t</code>. SELinux impide al Servidor HTTP Apache (<code class="systemitem">httpd</code>) el acceso a estos dos tipos. Para permitirle el acceso, SELinux debe saber qué archivos en <code class="filename">/srv/miweb/</code> son accesibles a <code class="systemitem">httpd</code>:
 			</div><pre class="screen">
 # /usr/sbin/semanage fcontext -a -t httpd_sys_content_t \
 "/srv/myweb(/.*)?"
 
 </pre><div class="para">
-				This <code class="command">semanage</code> command adds the context for the <code class="filename">/srv/myweb/</code> directory (and all files and directories under it) to the SELinux file-context configuration<sup>[<a id="id1832245" href="#ftn.id1832245" class="footnote">14</a>]</sup>. The <code class="command">semanage</code> command does not change the context. As the Linux root user, run the <code class="command">restorecon</code> command to apply the changes:
+				Este comando <code class="command">semanage</code> agrega el contexto para el directorio <code class="filename">/srv/miweb/</code> (y todos los archivos dentro de él) a la configuración de contexto de archivos de SELinux <sup>[<a id="id824735" href="#ftn.id824735" class="footnote">14</a>]</sup>. El comando <code class="command">semanage</code> no cambia el contexto. Como usuario root de Linux, ejecute el comando <code class="command">restorecon</code> para aplicar los cambios:
 			</div><pre class="screen">
 # /sbin/restorecon -R -v /srv/myweb
 
 </pre><div class="para">
-				Refer to <a class="xref" href="#sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext" title="5.7.2. Persistent Changes: semanage fcontext">Sección 5.7.2, “Persistent Changes: semanage fcontext”</a> for further information about adding contexts to the file-context configuration.
-			</div><div class="section" title="7.2.1.1. What is the Correct Context?" id="sect-Security-Enhanced_Linux-Labeling_Problems-What_is_the_Correct_Context"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">7.2.1.1. What is the Correct Context?</h4></div></div></div><div class="para">
-					The <code class="command">matchpathcon</code> command checks the context of a file path and compares it to the default label for that path. The following example demonstrates using <code class="command">matchpathcon</code> on a directory that contains incorrectly labeled files:
+				Refer to <a class="xref" href="#sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext" title="5.7.2. Cambios Persistentes: semanage fcontext">Sección 5.7.2, “Cambios Persistentes: semanage fcontext”</a> for further information about adding contexts to the file-context configuration.
+			</div><div class="section" title="7.2.1.1. ¿Cuál es el contexto correcto?" id="sect-Security-Enhanced_Linux-Labeling_Problems-What_is_the_Correct_Context"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">7.2.1.1. ¿Cuál es el contexto correcto?</h4></div></div></div><div class="para">
+					El comando <code class="command">matchpathcon</code> chequea el contexto de un nombre completo de archivo y lo compara con la etiqueta por defecto para esa dirección. El siguiente ejemplo muestra el uso de <code class="command">matchpathcon</code> en un directorio con archivos etiquetados incorrectamente:
 				</div><pre class="screen">
 $ /usr/sbin/matchpathcon -V /var/www/html/*
 /var/www/html/index.html has context unconfined_u:object_r:user_home_t:s0, should be system_u:object_r:httpd_sys_content_t:s0
 /var/www/html/page1.html has context unconfined_u:object_r:user_home_t:s0, should be system_u:object_r:httpd_sys_content_t:s0
 
 </pre><div class="para">
-					In this example, the <code class="filename">index.html</code> and <code class="filename">page1.html</code> files are labeled with the <code class="computeroutput">user_home_t</code> type. This type is used for files in user home directories. Using the <code class="command">mv</code> command to move files from your home directory may result in files being labeled with the <code class="computeroutput">user_home_t</code> type. This type should not exist outside of home directories. Use the <code class="command">restorecon</code> command to restore such files to their correct type:
+					En este ejemplo, los archivos <code class="filename">index.html</code> and <code class="filename">pagina1.html</code> se etiquetan con el tipo <code class="computeroutput">user_home_t</code>. Este tipo se usa para archivos en los directorios de inicio de los usuarios. Usando el comando <code class="command">mv</code> para mover archivos puede resultar en archivos etiquetados con el tipo <code class="computeroutput">user_home_t</code>. Este tipo no debería existir fuera de los directorios home. Use el comando <code class="command">restorecon</code> para restaurar tales archivos a su tipo correcto:
 				</div><pre class="screen">
 # /sbin/restorecon -v /var/www/html/index.html 
 restorecon reset /var/www/html/index.html context unconfined_u:object_r:user_home_t:s0-&gt;system_u:object_r:httpd_sys_content_t:s0
 
 </pre><div class="para">
-					To restore the context for all files under a directory, use the <code class="option">-R</code> option:
+					Para restaurar el contexto de todos los archivos bajo un directorio, use la opción <code class="option">-R</code>:
 				</div><pre class="screen">
 # /sbin/restorecon -R -v /var/www/html/
 restorecon reset /var/www/html/page1.html context unconfined_u:object_r:samba_share_t:s0-&gt;system_u:object_r:httpd_sys_content_t:s0
 restorecon reset /var/www/html/index.html context unconfined_u:object_r:samba_share_t:s0-&gt;system_u:object_r:httpd_sys_content_t:s0
 
 </pre><div class="para">
-					Refer to <a class="xref" href="#sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context" title="5.10.3. Checking the Default SELinux Context">Sección 5.10.3, “Checking the Default SELinux Context”</a> for a more detailed example of <code class="command">matchpathcon</code>.
-				</div></div></div><div class="section" title="7.2.2. How are Confined Services Running?" id="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.2.2. How are Confined Services Running?</h3></div></div></div><div class="para">
-				Services can be run in a variety of ways. To cater for this, you must tell SELinux how you are running services. This can be achieved via Booleans that allow parts of SELinux policy to be changed at runtime, without any knowledge of SELinux policy writing. This allows changes, such as allowing services access to NFS file systems, without reloading or recompiling SELinux policy. Also, running services on non-default port numbers requires policy configuration to be updated via the <code class="command">semanage</code> command.
+					Refer to <a class="xref" href="#sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context" title="5.10.3. Chequeando el Contexto SELinux Predeterminado">Sección 5.10.3, “Chequeando el Contexto SELinux Predeterminado”</a> for a more detailed example of <code class="command">matchpathcon</code>.
+				</div></div></div><div class="section" title="7.2.2. ¿Cómo se Ejecutan los Servicios Confinados?" id="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.2.2. ¿Cómo se Ejecutan los Servicios Confinados?</h3></div></div></div><div class="para">
+				Los servicios se pueden ejecutar en una variedad de formas. Para cambiar esto, debe decirle a SELinux cómo correrá los servicios. Esto se puede conseguir vía los Booleanos que permiten que parte de las políticas de SELinux se cambien en tiempo de ejecución, sin ningún conocimiento sobre la escritura de políticas de SELinux. Esto permite cambios, tales como permitir a servicios que accedan a sistemas de archivo NFS, sin recargar o recompilar una política SELinux. También, correr servicios en números de puerto no predeterminados requiere que la configuración de la política se actualice vía el comando <code class="command">semanage</code>.
 			</div><div class="para">
-				For example, to allow the Apache HTTP Server to communicate with MySQL, turn the <code class="computeroutput">httpd_can_network_connect_db</code> Boolean on:
+				Por ejemplo, para permitir al Servidor HTTP Apache comunicarse con MySQL, active el Booleano <code class="computeroutput">httpd_can_network_connect_db</code>:
 			</div><pre class="screen">
 # /usr/sbin/setsebool -P httpd_can_network_connect_db on
 
 </pre><div class="para">
-				If access is denied for a particular service, use the <code class="command">getsebool</code> and <code class="command">grep</code> commands to see if any Booleans are available to allow access. For example, use the <code class="command">getsebool -a | grep ftp</code> command to search for FTP related Booleans:
+				Si el acceso es denegado para un servicio particular, use los comandos <code class="command">getsebool</code> y <code class="command">grep</code> para ver si algún Booleano está disponible para permitir el acceso. Por ejemplo, use el comando <code class="command">getsebool -a | grep ftp</code> para buscar un Booleano relacionado con FTP:
 			</div><pre class="screen">
 $ /usr/sbin/getsebool -a | grep ftp
 allow_ftpd_anon_write --&gt; off
@@ -1746,9 +1746,9 @@ httpd_enable_ftp_server --&gt; off
 tftp_anon_write --&gt; off
 
 </pre><div class="para">
-				For a list of Booleans and whether they are on or off, run the <code class="command">/usr/sbin/getsebool -a</code> command. For a list of Booleans, an explanation of what each one is, and whether they are on or off, run the <code class="command">/usr/sbin/semanage boolean -l</code> command as the Linux root user. Refer to <a class="xref" href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans" title="5.6. Booleans">Sección 5.6, “Booleans”</a> for information about listing and configuring Booleans.
-			</div><div class="formalpara"><h5 class="formalpara">Port Numbers</h5>
-					Depending on policy configuration, services may only be allowed to run on certain port numbers. Attempting to change the port a service runs on without changing policy may result in the service failing to start. For example, run the <code class="command">semanage port -l | grep http</code> command as the Linux root user to list <code class="systemitem">http</code> related ports:
+				For a list of Booleans and whether they are on or off, run the <code class="command">/usr/sbin/getsebool -a</code> command. For a list of Booleans, an explanation of what each one is, and whether they are on or off, run the <code class="command">/usr/sbin/semanage boolean -l</code> command as the Linux root user. Refer to <a class="xref" href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans" title="5.6. Booleanos">Sección 5.6, “Booleanos”</a> for information about listing and configuring Booleans.
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-How_are_Confined_Services_Running-Port_Numbers"><h5 class="formalpara">Números de Puertos</h5>
+					Dependiendo de la configuración de la política, los servicios pueden tener permitido correr sobre ciertos números de puerto. Intentar cambiar el puerto en el que corre un servicio sin cambiar la política puede resultar en un fallo al iniciar el servicio. Por ejemplo, ejecute el comando <code class="command">semanage port -l | grep http</code> como usuario root de Linux para listar los puertos relacionados con <code class="systemitem">http</code>:
 				</div><pre class="screen">
 # /usr/sbin/semanage port -l | grep http
 http_cache_port_t              tcp      3128, 8080, 8118
@@ -1758,7 +1758,7 @@ pegasus_http_port_t            tcp      5988
 pegasus_https_port_t           tcp      5989
 
 </pre><div class="para">
-				The <code class="computeroutput">http_port_t</code> port type defines the ports Apache HTTP Server can listen on, which in this case, are TCP ports 80, 443, 488, 8008, 8009, and 8443. If an administrator configures <code class="filename">httpd.conf</code> so that <code class="systemitem">httpd</code> listens on port 9876 (<code class="option">Listen 9876</code>), but policy is not updated to reflect this, the <code class="command">service httpd start</code> command fails:
+				El tipo de puerto <code class="computeroutput">http_port_t</code> define los puertos en los que el Servidor HTTP Apache puede escuchar, que en este caso son los puertos TCP 80, 443, 488, 8008, 8009, y 8443. Si un administrador configura <code class="filename">httpd.conf</code> para que <code class="systemitem">httpd</code> escuche en el puerto 9876 (<code class="option">Listen 9876</code>), pero la política no fue actualizada para reflejar esto, el comando <code class="command">service httpd start</code> falla:
 			</div><pre class="screen">
 # /sbin/service httpd start
 Starting httpd: (13)Permission denied: make_sock: could not bind to address [::]:9876
@@ -1768,54 +1768,54 @@ Unable to open logs
 						            [FAILED]
 
 </pre><div class="para">
-				An SELinux denial similar to the following is logged to <code class="filename">/var/log/audit/audit.log</code>:
+				Una negación de SELinux es similar a la siguiente y se guarda en <code class="filename">/var/log/audit/audit.log</code>:
 			</div><pre class="screen">
 type=AVC msg=audit(1225948455.061:294): avc:  denied  { name_bind } for  pid=4997 comm="httpd" src=9876 scontext=unconfined_u:system_r:httpd_t:s0 tcontext=system_u:object_r:port_t:s0 tclass=tcp_socket
 
 </pre><div class="para">
-				To allow <code class="systemitem">httpd</code> to listen on a port that is not listed for the <code class="computeroutput">http_port_t</code> port type, run the <code class="command">semanage port</code> command to add a port to policy configuration<sup>[<a id="id1846320" href="#ftn.id1846320" class="footnote">15</a>]</sup>:
+				Para permitir a <code class="systemitem">httpd</code> escuchar en un puerto que no está listado en el tipo de puerto <code class="computeroutput">http_port_t</code>, ejecute el comando <code class="command">semanage port</code> para agregar un puerto a la configuración de la política <sup>[<a id="id805508" href="#ftn.id805508" class="footnote">15</a>]</sup>:
 			</div><pre class="screen">
 # /usr/sbin/semanage port -a -t http_port_t -p tcp 9876
 
 </pre><div class="para">
-				The <code class="option">-a</code> option adds a new record; the <code class="option">-t</code> option defines a type; and the <code class="option">-p</code> option defines a protocol. The last argument is the port number to add.
-			</div></div><div class="section" title="7.2.3. Evolving Rules and Broken Applications" id="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Evolving_Rules_and_Broken_Applications"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.2.3. Evolving Rules and Broken Applications</h3></div></div></div><div class="para">
-				Applications may be broken, causing SELinux to deny access. Also, SELinux rules are evolving - SELinux may not have seen an application running in a certain way, possibly causing it to deny access, even though the application is working as expected. For example, if a new version of PostgreSQL is released, it may perform actions the current policy has not seen before, causing access to be denied, even though access should be allowed.
+				La opción <code class="option">-a</code> agrega un nuevo registro; la opción <code class="option">-t</code> define un tipo; y la opción <code class="option">-p</code> define un protocolo. El último argumento es el número de puerto a agregar.
+			</div></div><div class="section" title="7.2.3. Evolucionando las Reglas y las Aplicaciones Rotas" id="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Evolving_Rules_and_Broken_Applications"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.2.3. Evolucionando las Reglas y las Aplicaciones Rotas</h3></div></div></div><div class="para">
+				Las aplicaciones se pueden romper, provocando que SELinux niegue el acceso. También, las reglas de SELinux evolucionan - SELinux no se debe ver como una aplicación que se ejecuta en una cierta forma, haciendo que deniegue el acceso, aún cuando la aplicación está funcionado como se espera que lo haga. Por ejemplo, si una nueva versión de PostgreSQL se lanza, puede realizar acciones sobre la política actual que no han sido vistas antes, haciendo que el acceso sea denegado, aún cuando el acceso debería ser permitido.
 			</div><div class="para">
-				For these situations, after access is denied, use <code class="command">audit2allow</code> to create a custom policy module to allow access. Refer to <a class="xref" href="#sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow" title="7.3.8. Allowing Access: audit2allow">Sección 7.3.8, “Allowing Access: audit2allow”</a> for information about using <code class="command">audit2allow</code>.
-			</div></div></div><div class="section" title="7.3. Fixing Problems" id="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">7.3. Fixing Problems</h2></div></div></div><div class="para">
-			The following sections help troubleshoot issues. They go over: checking Linux permissions, which are checked before SELinux rules; possible causes of SELinux denying access, but no denials being logged; manual pages for services, which contain information about labeling and Booleans; permissive domains, for allowing one process to run permissive, rather than the whole system; how to search for and view denial messages; analyzing denials; and creating custom policy modules with <code class="command">audit2allow</code>.
-		</div><div class="section" title="7.3.1. Linux Permissions" id="sect-Security-Enhanced_Linux-Fixing_Problems-Linux_Permissions"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.3.1. Linux Permissions</h3></div></div></div><div class="para">
-				When access is denied, check standard Linux permissions. As mentioned in <a class="xref" href="#chap-Security-Enhanced_Linux-Introduction" title="Capítulo 2. Introduction">Capítulo 2, <i>Introduction</i></a>, most operating systems use a Discretionary Access Control (DAC) system to control access, allowing users to control the permissions of files that they own. SELinux policy rules are checked after DAC rules. SELinux policy rules are not used if DAC rules deny access first.
+				For these situations, after access is denied, use <code class="command">audit2allow</code> to create a custom policy module to allow access. Refer to <a class="xref" href="#sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow" title="7.3.8. Permitiendo el Acceso: audit2allow">Sección 7.3.8, “Permitiendo el Acceso: audit2allow”</a> for information about using <code class="command">audit2allow</code>.
+			</div></div></div><div class="section" title="7.3. Corrección de Problemas" id="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">7.3. Corrección de Problemas</h2></div></div></div><div class="para">
+			Las siguientes secciones ayudan a resolver problemas. Cubren los temas: chequeo de los permisos de Linux, que se chequean antes que las reglas de SELinux; posibles causas de negaciones de acceso de SELinux, pero no negaciones que se estén guardando; páginas man de los servicios, que contienen información sobre etiquetado y Booleanos; dominios permisivos, para permitir a un proceso correr en modo permisivo, en vez de todo el sistema; cómo buscar y encontrar mensajes; análisis de negaciones; y creación de módulos de políticas personalizados con <code class="command">audit2allow</code>.
+		</div><div class="section" title="7.3.1. Permisos de Linux" id="sect-Security-Enhanced_Linux-Fixing_Problems-Linux_Permissions"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.3.1. Permisos de Linux</h3></div></div></div><div class="para">
+				When access is denied, check standard Linux permissions. As mentioned in <a class="xref" href="#chap-Security-Enhanced_Linux-Introduction" title="Capítulo 2. Introducción">Capítulo 2, <i>Introducción</i></a>, most operating systems use a Discretionary Access Control (DAC) system to control access, allowing users to control the permissions of files that they own. SELinux policy rules are checked after DAC rules. SELinux policy rules are not used if DAC rules deny access first.
 			</div><div class="para">
-				If access is denied and no SELinux denials are logged, use the <code class="command">ls -l</code> command to view the standard Linux permissions:
+				Si el acceso es denegado y no hay negaciones SELinux guardadas, use el comando <code class="command">ls -l</code> para ver los permisos estándares de Linux:
 			</div><pre class="screen">
 $ ls -l /var/www/html/index.html
 -rw-r----- 1 root root 0 2009-05-07 11:06 index.html
 
 </pre><div class="para">
-				In this example, <code class="filename">index.html</code> is owned by the root user and group. The root user has read and write permissions (<code class="computeroutput">-rw</code>), and members of the root group have read permissions (<code class="computeroutput">-r-</code>). Everyone else has no access (<code class="computeroutput">---</code>). By default, such permissions do not allow <code class="systemitem">httpd</code> to read this file. To resolve this issue, use the <code class="command">chown</code> command to change the owner and group. This command must be run as the Linux root user:
+				En este ejemplo, <code class="filename">index.html</code> pertenece al usuario y al grupo root. El usuario root tiene permisos de lectura y escritura (<code class="computeroutput">-rw</code>), y los miembros del grupo root tienen permisos de lectura (<code class="computeroutput">-r-</code>). Cualquier otro no tiene acceso (<code class="computeroutput">---</code>). Por defecto, tales permisos no permiten a <code class="systemitem">httpd</code> leer este archivo. Para resolver esto, use el comando <code class="command">chown</code> el dueño y el grupo. Este comando se debe ejecutar como usuario root de Linux:
 			</div><pre class="screen">
 # chown apache:apache /var/www/html/index.html
 
 </pre><div class="para">
-				This assumes the default configuration, in which <code class="systemitem">httpd</code> runs as the Linux apache user. If you run <code class="systemitem">httpd</code> with a different user, replace <code class="computeroutput">apache:apache</code> with that user.
+				Esto asume la configuración predeterminada, en la que <code class="systemitem">httpd</code> corre como usuario apache de Linux. Si corre <code class="systemitem">httpd</code> con un usuario diferente, reemplace <code class="computeroutput">apache:apache</code> con ese usuario.
 			</div><div class="para">
 				Refer to the <a href="http://fedoraproject.org/wiki/Docs/Drafts/AdministrationGuide/Permissions">Fedora Documentation Project "Permissions"</a> draft for information about managing Linux permissions.
-			</div></div><div class="section" title="7.3.2. Possible Causes of Silent Denials" id="sect-Security-Enhanced_Linux-Fixing_Problems-Possible_Causes_of_Silent_Denials"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.3.2. Possible Causes of Silent Denials</h3></div></div></div><div class="para">
-				In certain situations, AVC denials may not be logged when SELinux denies access. Applications and system library functions often probe for more access than required to perform their tasks. To maintain least privilege without filling audit logs with AVC denials for harmless application probing, the policy can silence AVC denials without allowing a permission by using <code class="computeroutput">dontaudit</code> rules. These rules are common in standard policy. The downside of <code class="computeroutput">dontaudit</code> is that, although SELinux denies access, denial messages are not logged, making troubleshooting hard.
+			</div></div><div class="section" title="7.3.2. Posibles Causas de las Negaciones Silenciosas" id="sect-Security-Enhanced_Linux-Fixing_Problems-Possible_Causes_of_Silent_Denials"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.3.2. Posibles Causas de las Negaciones Silenciosas</h3></div></div></div><div class="para">
+				En ciertas situaciones, las negaciones AVC pueden no ser guardadas cuando SELinux niega el acceso. Las aplicaciones y las funciones de las bibliotecas del sistema a menudo prueban más accesos que los pedidos para realizar sus tareas. Para mantener el menor privilegio sin llenar los informes de auditoría con negaciones AVC para pruebas sin peligro de las aplicaciones, la política puede silenciar las negaciones AVC sin permitir el uso de reglas <code class="computeroutput">dontaudit</code>. Estas reglas son comúnes en la política estándar. La contraparte de <code class="computeroutput">dontaudit</code> es que, aunque SELinux niega el acceso, los mensajes no se guardan, lo que dificulta resolver el problema.
 			</div><div class="para">
-				To temporarily disable <code class="computeroutput">dontaudit</code> rules, allowing all denials to be logged, run the following command as the Linux root user:
+				Deshabilite temporalmente las reglas <code class="computeroutput">dontaudit</code>, permitiendo que se guarden todas las negaciones, ejecute el siguiente comando como usuario root de Linux:
 			</div><div class="para">
 				<code class="command">/usr/sbin/semodule -DB</code>
 			</div><div class="para">
-				The <code class="option">-D</code> option disables <code class="computeroutput">dontaudit</code> rules; the <code class="option">-B</code> option rebuilds policy. After running <code class="command">semodule -DB</code>, try exercising the application that was encountering permission problems, and see if SELinux denials — relevant to the application — are now being logged. Take care in deciding which denials should be allowed, as some should be ignored and handled via <code class="computeroutput">dontaudit</code> rules. If in doubt, or in search of guidance, contact other SELinux users and developers on an SELinux list, such as <a href="http://www.redhat.com/mailman/listinfo/fedora-selinux-list">fedora-selinux-list</a>.
+				La opción <code class="option">-D</code> deshabilita las reglas <code class="computeroutput">dontaudit</code>; la opción <code class="option">-B</code> reconstruye la política. Después de ejcutar <code class="command">semodule -DB</code>, pruebe ejercitar la aplicación que tuvo problemas de permisos, y vea si ahora se guardan negaciones de SELinux relacionadas con la aplicación. Tenga cuidado con la decición de qué negaciones se deben permitir, dado que algunas se deben ignorar y manejarse vía reglas <code class="computeroutput">dontaudit</code>. Si tiene duda, o busca alguna guía, contacte a otros usuarios y desarrolladores de SELinux en una lista de SELinux, tal como <a href="http://www.redhat.com/mailman/listinfo/fedora-selinux-list">fedora-selinux-list</a>.
 			</div><div class="para">
-				To rebuild policy and enable <code class="computeroutput">dontaudit</code> rules, run the following command as the Linux root user:
+				Para reconstruir la política y habilitar las reglas <code class="computeroutput">dontaudit</code>, ejecute el siguiente comando como usuario root de Linux:
 			</div><div class="para">
 				<code class="command">/usr/sbin/semodule -B</code>
 			</div><div class="para">
-				This restores the policy to its original state. For a full list of <code class="computeroutput">dontaudit</code> rules, run the <code class="command">sesearch --dontaudit</code> command. Narrow down searches using the <code class="option">-s <em class="replaceable"><code>domain</code></em></code> option and the <code class="command">grep</code> command. For example:
+				Esto restaura la política a su estado original. Para una lista completa de las reglas <code class="computeroutput">dontaudit</code>, corra el comando <code class="command">sesearch --dontaudit</code>. Búsquedas más refinadas usando la opción <code class="option">-s <em class="replaceable"><code>dominio</code></em></code> y el comando <code class="command">grep</code>. Por ejemplo:
 			</div><pre class="screen">
 $ sesearch --dontaudit -s smbd_t | grep squid
 WARNING: This policy contained disabled aliases; they have been removed.
@@ -1823,83 +1823,83 @@ dontaudit smbd_t squid_port_t : tcp_socket name_bind ;
 dontaudit smbd_t squid_port_t : udp_socket name_bind ;
 
 </pre><div class="para">
-				Refer to <a class="xref" href="#sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages" title="7.3.6. Raw Audit Messages">Sección 7.3.6, “Raw Audit Messages”</a> and <a class="xref" href="#sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages" title="7.3.7. sealert Messages">Sección 7.3.7, “sealert Messages”</a> for information about analyzing denials.
-			</div></div><div class="section" title="7.3.3. Manual Pages for Services" id="sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.3.3. Manual Pages for Services</h3></div></div></div><div class="para">
-				Manual pages for services contain valuable information, such as what file type to use for a given situation, and Booleans to change the access a service has (such as <code class="systemitem">httpd</code> accessing NFS file systems). This information may be in the standard manual page, or a manual page with <code class="computeroutput">selinux</code> prepended or appended.
+				Refer to <a class="xref" href="#sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages" title="7.3.6. Raw Audit Messages">Sección 7.3.6, “Raw Audit Messages”</a> and <a class="xref" href="#sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages" title="7.3.7. Mensajes sealert">Sección 7.3.7, “Mensajes sealert”</a> for information about analyzing denials.
+			</div></div><div class="section" title="7.3.3. Páginas de Manual para Servicios" id="sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.3.3. Páginas de Manual para Servicios</h3></div></div></div><div class="para">
+				Las páginas de manual para los servicios conteniendo información valiosa, tal como qué tipo de archivo usar para una situación dada, y los Booleanos para cambiar el acceso que un servicio tiene (tal como <code class="systemitem">httpd</code> para acceder sistemas de archivos NFS). Esta información puede estar en la página de manual estándar o una página de manual con <code class="computeroutput">selinux</code> como prefijo o sufijo.
 			</div><div class="para">
-				For example, the <span class="citerefentry"><span class="refentrytitle">httpd_selinux</span>(8)</span> manual page has information about what file type to use for a given situation, as well as Booleans to allow scripts, sharing files, accessing directories inside user home directories, and so on. Other manual pages with SELinux information for services include:
+				Por ejemplo, la página de manual <span class="citerefentry"><span class="refentrytitle">httpd_selinux</span>(8)</span> tiene información sobre qué tipo de archivo usar para una situación dada, así como los Booleanos para permitir scripts, compartir archivos, acceder directorios dentro de los directorios home, y así sucesivamente. Otras páginas de manual con información de SELinux para servicios incluyen a:
 			</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-						Samba: the <span class="citerefentry"><span class="refentrytitle">samba_selinux</span>(8)</span> manual page describes that files and directories to be exported via Samba must be labeled with the <code class="computeroutput">samba_share_t</code> type, as well as Booleans to allow files labeled with types other than <code class="computeroutput">samba_share_t</code> to be exported via Samba.
+						Samba: la página de manual <span class="citerefentry"><span class="refentrytitle">samba_selinux</span>(8)</span> describe que los archivos y directorios exportar vía Samba deben ser etiquetados con el tipo <code class="computeroutput">samba_share_t</code>, así como los Booleanos para permitir archivos etiquetados con otros tipos distintos a <code class="computeroutput">samba_share_t</code> para exportarlos vía Samba.
 					</div></li><li class="listitem"><div class="para">
-						NFS: the <span class="citerefentry"><span class="refentrytitle">nfs_selinux</span>(8)</span> manual page describes that, by default, file systems can not be exported via NFS, and that to allow file systems to be exported, Booleans such as <code class="computeroutput">nfs_export_all_ro</code> or <code class="computeroutput">nfs_export_all_rw</code> must be turned on.
+						NFS: la página de manual <span class="citerefentry"><span class="refentrytitle">nfs_selinux</span>(8)</span> describe que, por defecto, los sistemas de archivo no se pueden exportar vía NFS, y que no se permite exportar sistemas de archivos. Los Booleanos como <code class="computeroutput">nfs_export_all_ro</code> o <code class="computeroutput">nfs_export_all_rw</code> deben activarse.
 					</div></li><li class="listitem"><div class="para">
-						Berkeley Internet Name Domain (BIND): the <span class="citerefentry"><span class="refentrytitle">named</span>(8)</span> manual page describes what file type to use for a given situation (see the <code class="computeroutput">Red Hat SELinux BIND Security Profile</code> section). The <span class="citerefentry"><span class="refentrytitle">named_selinux</span>(8)</span> manual page describes that, by default, <code class="systemitem">named</code> can not write to master zone files, and to allow such access, the <code class="computeroutput">named_write_master_zones</code> Boolean must be turned on.
+						Berkeley Internet Name Domain (BIND): la página de manual de <span class="citerefentry"><span class="refentrytitle">named</span>(8)</span> describe qué tipo de archivo usar para una situación dada (vea la sección <code class="computeroutput">Perfil de Seguridad de SELinux para BIND de Red Hat</code> section). La página man de <span class="citerefentry"><span class="refentrytitle">named_selinux</span>(8)</span> describe que, por defecto, <code class="systemitem">named</code> no puede escribir a archivos de zona maestros y que, para permitir ese acceso, el Booleano <code class="computeroutput">named_write_master_zones</code> debe ser puesto en 1.
 					</div></li></ul></div><div class="para">
-				The information in manual pages helps you configure the correct file types and Booleans, helping to prevent SELinux from denying access.
-			</div></div><div class="section" title="7.3.4. Permissive Domains" id="sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.3.4. Permissive Domains</h3></div></div></div><div class="para">
-				When SELinux is running in permissive mode, SELinux does not deny access, but denials are logged for actions that would have been denied if running in enforcing mode. Previously, it was not possible to make a single domain permissive (remember: processes run in domains). In certain situations, this led to making the whole system permissive to troubleshoot issues.
+				La información en las páginas del manual le ayudan a configurar los tipos de archivos correctos y los Booleanos, ayudándolo a prevenir las negaciones de acceso por parte de SELinux.
+			</div></div><div class="section" title="7.3.4. Dominios Permisivos" id="sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.3.4. Dominios Permisivos</h3></div></div></div><div class="para">
+				Cuando SELinux se ejecuta en modo permisivo, SELinux no niega el acceso, sino que las negaciones para las acciones se guardan como si fuera que corre en modo obediente. Previamente, no era posible hacer permisivo un único dominio (recuerde: los procesos corren en dominios). En ciertas situaciones, esto llevó a hacer el sistema permisivo para poder corregir los problemas.
 			</div><div class="para">
-				Fedora 11 introduces permissive domains, where an administrator can configure a single process (domain) to run permissive, rather than making the whole system permissive. SELinux checks are still performed for permissive domains; however, the kernel allows access and reports an AVC denial for situations where SELinux would have denied access. Permissive domains are also available in Fedora 9 (with the latest updates applied).
+				Fedora 11 introduce los dominios permisivos, donde un administrador puede configurar un único proceso (dominio) para que corra permisivo, en vez de hacer todo el sistema permisivo. Los chequeos de SELinux se realizan igualmente para dominios permisivos; sin embargo, el kernel permite el acceso e informa la negación AVC para situaciones donde SELinux hubiera negado el acceso. Los dominios permisivos están también disponibles en Fedora 9 (con las últimas actualizaciones aplicadas).
 			</div><div class="para">
-				In Red Hat Enterprise Linux 4 and 5, <code class="computeroutput"><em class="replaceable"><code>domain</code></em>_disable_trans</code> Booleans are available to prevent an application from transitioning to a confined domain, and therefore, the process runs in an unconfined domain, such as <code class="computeroutput">initrc_t</code>. Turning such Booleans on can cause major problems. For example, if the <code class="computeroutput">httpd_disable_trans</code> Boolean is turned on:
+				En el Linux para Empresas de Red Hat 4 y 5, los Booleanos <code class="computeroutput"><em class="replaceable"><code>dominio</code></em>_disable_trans</code> están disponibles para prevenir que una aplicación transicione a un dominio confinado, y por lo tanto, el proceso se ejecute en un dominio no confinado, tal como <code class="computeroutput">initrc_t</code>. Poniendo en 1 tales booleanos pueden causar problemas serios. Por ejemplo, si el Booleano <code class="computeroutput">httpd_disable_trans</code> se pone en 1:
 			</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-						<code class="systemitem">httpd</code> runs in the unconfined <code class="computeroutput">initrc_t</code> domain. Files created by processes running in the <code class="computeroutput">initrc_t</code> domain may not have the same labeling rules applied as files created by a process running in the <code class="computeroutput">httpd_t</code> domain, potentially allowing processes to create mislabeled files. This causes access problems later on.
+						<code class="systemitem">httpd</code> corre en el dominio no confinado <code class="computeroutput">initrc_t</code>. Los archivos creados por los procesos en el dominio <code class="computeroutput">initrc_t</code> puede no tener aplicadas las mismas reglas de etiquetados como los archivos creados por el proceso corriendo en el dominio <code class="computeroutput">httpd_t</code>, permitiendo que los procesos puedan potencialmente crear archivos mal etiquetados. Esto causa problemas más adelante.
 					</div></li><li class="listitem"><div class="para">
-						confined domains that are allowed to communicate with <code class="computeroutput">httpd_t</code> can not communicate with <code class="computeroutput">initrc_t</code>, possibly causing additional failures.
+						dominios confinados que pueden comunicarse con <code class="computeroutput">httpd_t</code> no pueden comunicarse con <code class="computeroutput">initrc_t</code>, posiblemente causan fallas adicionales.
 					</div></li></ul></div><div class="para">
-				The <code class="computeroutput"><em class="replaceable"><code>domain</code></em>_disable_trans</code> Booleans were removed from Fedora 7, even though there was no replacement. Permissive domains solve the above issues: transition rules apply, and files are created with the correct labels.
+				Los Booleanos <code class="computeroutput"><em class="replaceable"><code>domain</code></em>_disable_trans</code> fueron eliminados de Fedora 7, y no se pusieron reemplazos. Los dominios permisivos pueden resolver esos problemas: se aplican las reglas de transición y los archivos se crean con las etiquetas correctas.
 			</div><div class="para">
-				Permissive domains can be used for:
+				Los dominios permisivos se pueden usar para:
 			</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-						making a single process (domain) run permissive to troubleshoot an issue, rather than putting the entire system at risk by making the entire system permissive.
+						hacer que un único proceso (dominio) corra permisivo para solucionar alguna cuestión, en vez de poner todo el sistema en riesgo haciendo permisivo a todo el sistema.
 					</div></li><li class="listitem"><div class="para">
-						creating policies for new applications. Previously, it was recommended that a minimal policy be created, and then the entire machine put into permissive mode, so that the application could run, but SELinux denials still logged. <code class="command">audit2allow</code> could then be used to help write the policy. This put the whole system at risk. With permissive domains, only the domain in the new policy can be marked permissive, without putting the whole system at risk.
-					</div></li></ul></div><div class="section" title="7.3.4.1. Making a Domain Permissive" id="sect-Security-Enhanced_Linux-Permissive_Domains-Making_a_Domain_Permissive"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">7.3.4.1. Making a Domain Permissive</h4></div></div></div><div class="para">
-					To make a domain permissive, run the <code class="command">semanage permissive -a <em class="replaceable"><code>domain</code></em></code> command, where <em class="replaceable"><code>domain</code></em> is the domain you want to make permissive. For example, run the following command as the Linux root user to make the <code class="computeroutput">httpd_t</code> domain (the domain the Apache HTTP Server runs in) permissive:
+						creación de políticas para nuevas aplicaciones. Previamente, era recomendado crear una política mínima, y luego poner la máquina completa en modo permisivo, para que la aplicación pudiera funcionar, pero las negaciones de SELinux eran igualmente grabadas. <code class="command">audit2allow</code> podría usarse luego para ayudar a escribir la política. Esto pone todo el sistema en riesgo. Con dominios permisivos, sólo el dominio en la nueva política puede marcarse como permisivo, sin poner en riesgo todo el sistema.
+					</div></li></ul></div><div class="section" title="7.3.4.1. Creando un Dominio Permisivo" id="sect-Security-Enhanced_Linux-Permissive_Domains-Making_a_Domain_Permissive"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">7.3.4.1. Creando un Dominio Permisivo</h4></div></div></div><div class="para">
+					Para hacer un dominio permisivo, ejecute el comando <code class="command">semanage permissive -a <em class="replaceable"><code>dominio</code></em></code>, donde <em class="replaceable"><code>dominio</code></em> es el dominio que quiere hacer permisivo. Por ejemplo, ejecute el siguiente comando como usuario root de Linux para hacer permisivo el dominio <code class="computeroutput">httpd_t</code> (el dominio en el que corre el Servidor HTTP Apache):
 				</div><div class="para">
 					<code class="command">/usr/sbin/semanage permissive -a httpd_t</code>
 				</div><div class="para">
-					To view a list of domains you have made permissive, run the <code class="command">semodule -l | grep permissive</code> command as the Linux root user. For example:
+					Para ver una lista de los dominios que hizo permisivos, corra el comando <code class="command">semodule -l | grep permissive</code> como usuario root de Linux. Por ejemplo:
 				</div><pre class="screen">
 # /usr/sbin/semodule -l | grep permissive
 permissive_httpd_t      1.0
 
 </pre><div class="para">
-					If you no longer want a domain to be permissive, run the <code class="command">semanage permissive -d <em class="replaceable"><code>domain</code></em></code> command as the Linux root user. For example:
+					Si ya no quiere que un dominio sea permisivo, corra el comando <code class="command">semanage permissive -d <em class="replaceable"><code>dominio</code></em></code> como usuario root de Linux. Por ejemplo:
 				</div><div class="para">
 					<code class="command">/usr/sbin/semanage permissive -d httpd_t</code>
-				</div></div><div class="section" title="7.3.4.2. Denials for Permissive Domains" id="sect-Security-Enhanced_Linux-Permissive_Domains-Denials_for_Permissive_Domains"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">7.3.4.2. Denials for Permissive Domains</h4></div></div></div><div class="para">
-					The <code class="computeroutput">SYSCALL</code> message is different for permissive domains. The following is an example AVC denial (and the associated system call) from the Apache HTTP Server:
+				</div></div><div class="section" title="7.3.4.2. Negaciones para Dominios Permisivos" id="sect-Security-Enhanced_Linux-Permissive_Domains-Denials_for_Permissive_Domains"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">7.3.4.2. Negaciones para Dominios Permisivos</h4></div></div></div><div class="para">
+					El mensaje <code class="computeroutput">SYSCALL</code> es diferente para dominios permisivos. El siguiente es un ejemplo de una negación de AVC (y la llamada a sistema asociada) desde el Servidor HTTP Apache:
 				</div><pre class="screen">
 type=AVC msg=audit(1226882736.442:86): avc:  denied  { getattr } for  pid=2427 comm="httpd" path="/var/www/html/file1" dev=dm-0 ino=284133 scontext=unconfined_u:system_r:httpd_t:s0 tcontext=unconfined_u:object_r:samba_share_t:s0 tclass=file
 	
 type=SYSCALL msg=audit(1226882736.442:86): arch=40000003 syscall=196 success=no exit=-13 a0=b9a1e198 a1=bfc2921c a2=54dff4 a3=2008171 items=0 ppid=2425 pid=2427 auid=502 uid=48 gid=48 euid=48 suid=48 fsuid=48 egid=48 sgid=48 fsgid=48 tty=(none) ses=4 comm="httpd" exe="/usr/sbin/httpd" subj=unconfined_u:system_r:httpd_t:s0 key=(null)
 
 </pre><div class="para">
-					By default, the <code class="computeroutput">httpd_t</code> domain is not permissive, and as such, the action is denied, and the <code class="computeroutput">SYSCALL</code> message contains <code class="computeroutput">success=no</code>. The following is an example AVC denial for the same situation, except the <code class="command">semanage permissive -a httpd_t</code> command has been run to make the <code class="computeroutput">httpd_t</code> domain permissive:
+					Por defecto, el dominio <code class="computeroutput">httpd_t</code> es no permisivo, y como tal, la acción es negada, y el mensaje <code class="computeroutput">SYSCALL</code> contiene <code class="computeroutput">success=no</code>. El siguiente es un ejemplo de negación AVC para la misma situación, excepto que el comando <code class="command">semanage permissive -a httpd_t</code> se ejecutó para hacer el dominio <code class="computeroutput">httpd_t</code> permisivo:
 				</div><pre class="screen">
 type=AVC msg=audit(1226882925.714:136): avc:  denied  { read } for  pid=2512 comm="httpd" name="file1" dev=dm-0 ino=284133 scontext=unconfined_u:system_r:httpd_t:s0 tcontext=unconfined_u:object_r:samba_share_t:s0 tclass=file
 	
 type=SYSCALL msg=audit(1226882925.714:136): arch=40000003 syscall=5 success=yes exit=11 a0=b962a1e8 a1=8000 a2=0 a3=8000 items=0 ppid=2511 pid=2512 auid=502 uid=48 gid=48 euid=48 suid=48 fsuid=48 egid=48 sgid=48 fsgid=48 tty=(none) ses=4 comm="httpd" exe="/usr/sbin/httpd" subj=unconfined_u:system_r:httpd_t:s0 key=(null)
 
 </pre><div class="para">
-					In this case, although an AVC denial was logged, access was not denied, as shown by <code class="computeroutput">success=yes</code> in the <code class="computeroutput">SYSCALL</code> message.
+					En este caso, aunque la negación AVC fue grabada, el acceso no fue negado, como se muestra en el mensaje <code class="computeroutput">SYSCALL</code> <code class="computeroutput">success=yes</code>.
 				</div><div class="para">
 					Refer to Dan Walsh's <a href="http://danwalsh.livejournal.com/24537.html">"Permissive Domains"</a> blog entry for further information about permissive domains.
-				</div></div></div><div class="section" title="7.3.5. Searching For and Viewing Denials" id="sect-Security-Enhanced_Linux-Fixing_Problems-Searching_For_and_Viewing_Denials"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.3.5. Searching For and Viewing Denials</h3></div></div></div><div class="para">
-				This section assumes the <span class="package">setroubleshoot</span>, <span class="package">setroubleshoot-server</span>, and <span class="package">audit</span> packages are installed, and that the <code class="systemitem">auditd</code>, <code class="systemitem">rsyslogd</code>, and <code class="systemitem">setroubleshootd</code> daemons are running. Refer to <a class="xref" href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used" title="5.2. Which Log File is Used">Sección 5.2, “Which Log File is Used”</a> for information about starting these daemons. A number of tools are available for searching for and viewing SELinux denials, such as <code class="command">ausearch</code>, <code class="command">aureport</code>, and <code class="command">sealert</code>.
-			</div><div class="formalpara"><h5 class="formalpara">ausearch</h5>
-					The <span class="package">audit</span> package provides <code class="command">ausearch</code>. From the <span class="citerefentry"><span class="refentrytitle">ausearch</span>(8)</span> manual page: "<code class="command">ausearch</code> is a tool that can query the audit daemon logs based for events based on different search criteria"<sup>[<a id="id440644" href="#ftn.id440644" class="footnote">16</a>]</sup>. The <code class="command">ausearch</code> tool accesses <code class="filename">/var/log/audit/audit.log</code>, and as such, must be run as the Linux root user:
-				</div><div class="segmentedlist"><table border="0"><thead><tr class="segtitle"><th>Searching For</th><th>Command</th></tr></thead><tbody><tr class="seglistitem"><td class="seg">all denials</td><td class="seg"><code class="command">/sbin/ausearch -m avc</code></td></tr><tr class="seglistitem"><td class="seg">denials for that today</td><td class="seg"><code class="command">/sbin/ausearch -m avc -ts today</code></td></tr><tr class="seglistitem"><td class="seg">denials from the last 10 minutes</td><td class="seg"><code class="command">/sbin/ausearch -m avc -ts recent</code></td></tr></tbody></table></div><div class="para">
-				To search for SELinux denials for a particular service, use the <code class="option">-c <em class="replaceable"><code>comm-name</code></em></code> option, where <em class="replaceable"><code>comm-name</code></em> "is the executable’s name"<sup>[<a id="id440741" href="#ftn.id440741" class="footnote">17</a>]</sup>, for example, <code class="systemitem">httpd</code> for the Apache HTTP Server, and <code class="systemitem">smbd</code> for Samba:
+				</div></div></div><div class="section" title="7.3.5. Búsqueda y Revisión de Negaciones" id="sect-Security-Enhanced_Linux-Fixing_Problems-Searching_For_and_Viewing_Denials"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.3.5. Búsqueda y Revisión de Negaciones</h3></div></div></div><div class="para">
+				This section assumes the <span class="package">setroubleshoot</span>, <span class="package">setroubleshoot-server</span>, and <span class="package">audit</span> packages are installed, and that the <code class="systemitem">auditd</code>, <code class="systemitem">rsyslogd</code>, and <code class="systemitem">setroubleshootd</code> daemons are running. Refer to <a class="xref" href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used" title="5.2. Qué Archivo Log se usa">Sección 5.2, “Qué Archivo Log se usa”</a> for information about starting these daemons. A number of tools are available for searching for and viewing SELinux denials, such as <code class="command">ausearch</code>, <code class="command">aureport</code>, and <code class="command">sealert</code>.
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Searching_For_and_Viewing_Denials-ausearch"><h5 class="formalpara">ausearch</h5>
+					The <span class="package">audit</span> package provides <code class="command">ausearch</code>. From the <span class="citerefentry"><span class="refentrytitle">ausearch</span>(8)</span> manual page: "<code class="command">ausearch</code> is a tool that can query the audit daemon logs based for events based on different search criteria"<sup>[<a id="id739080" href="#ftn.id739080" class="footnote">16</a>]</sup>. The <code class="command">ausearch</code> tool accesses <code class="filename">/var/log/audit/audit.log</code>, and as such, must be run as the Linux root user:
+				</div><div class="segmentedlist"><table border="0"><thead><tr class="segtitle"><th>Buscando</th><th>Comando</th></tr></thead><tbody><tr class="seglistitem"><td class="seg">todas las negaciones</td><td class="seg"><code class="command">/sbin/ausearch -m avc</code></td></tr><tr class="seglistitem"><td class="seg">negaciones de hoy</td><td class="seg"><code class="command">/sbin/ausearch -m avc -ts today</code></td></tr><tr class="seglistitem"><td class="seg">negaciones desde los últimos 10 minutos</td><td class="seg"><code class="command">/sbin/ausearch -m avc -ts recent</code></td></tr></tbody></table></div><div class="para">
+				To search for SELinux denials for a particular service, use the <code class="option">-c <em class="replaceable"><code>comm-name</code></em></code> option, where <em class="replaceable"><code>comm-name</code></em> "is the executable’s name"<sup>[<a id="id739175" href="#ftn.id739175" class="footnote">17</a>]</sup>, for example, <code class="systemitem">httpd</code> for the Apache HTTP Server, and <code class="systemitem">smbd</code> for Samba:
 			</div><div class="para">
 				<code class="command">/sbin/ausearch -m avc -c httpd</code>
 			</div><div class="para">
 				<code class="command">/sbin/ausearch -m avc -c smbd</code>
 			</div><div class="para">
-				Refer to the <span class="citerefentry"><span class="refentrytitle">ausearch</span>(8)</span> manual page for further <code class="command">ausearch</code> options.
-			</div><div class="formalpara"><h5 class="formalpara">aureport</h5>
-					The <span class="package">audit</span> package provides <code class="command">aureport</code>. From the <span class="citerefentry"><span class="refentrytitle">aureport</span>(8)</span> manual page: "<code class="command">aureport</code> is a tool that produces summary reports of the audit system logs"<sup>[<a id="id437758" href="#ftn.id437758" class="footnote">18</a>]</sup>. The <code class="command">aureport</code> tool accesses <code class="filename">/var/log/audit/audit.log</code>, and as such, must be run as the Linux root user. To view a list of SELinux denials and how often each one occurred, run the <code class="command">aureport -a</code> command. The following is example output that includes two denials:
+				Vaya a la página de manual de <span class="citerefentry"><span class="refentrytitle">ausearch</span>(8)</span> para más opciones de <code class="command">ausearch</code>.
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Searching_For_and_Viewing_Denials-aureport"><h5 class="formalpara">aureport</h5>
+					The <span class="package">audit</span> package provides <code class="command">aureport</code>. From the <span class="citerefentry"><span class="refentrytitle">aureport</span>(8)</span> manual page: "<code class="command">aureport</code> is a tool that produces summary reports of the audit system logs"<sup>[<a id="id739276" href="#ftn.id739276" class="footnote">18</a>]</sup>. The <code class="command">aureport</code> tool accesses <code class="filename">/var/log/audit/audit.log</code>, and as such, must be run as the Linux root user. To view a list of SELinux denials and how often each one occurred, run the <code class="command">aureport -a</code> command. The following is example output that includes two denials:
 				</div><pre class="screen">
 # /sbin/aureport -a
 
@@ -1911,58 +1911,58 @@ AVC Report
 2. 05/03/2009 22:00:25 vsftpd unconfined_u:system_r:ftpd_t:s0 5 file read unconfined_u:object_r:cifs_t:s0 denied 4
 
 </pre><div class="para">
-				Refer to the <span class="citerefentry"><span class="refentrytitle">aureport</span>(8)</span> manual page for further <code class="command">aureport</code> options.
-			</div><div class="formalpara"><h5 class="formalpara">sealert</h5>
-					The <span class="package">setroubleshoot-server</span> package provides <code class="command">sealert</code>, which reads denial messages translated by <span class="package">setroubleshoot-server</span>. Denials are assigned IDs, as seen in <code class="filename">/var/log/messages</code>. The following is an example denial from <code class="filename">messages</code>:
+				Vaya a la página de manual de <span class="citerefentry"><span class="refentrytitle">aureport</span>(8)</span> para más opciones de <code class="command">aureport</code>.
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Searching_For_and_Viewing_Denials-sealert"><h5 class="formalpara">sealert</h5>
+					El paquete <span class="package">setroubleshoot-server</span> provee <code class="command">sealert</code>, que lee los mensajes de negación traducidos por <span class="package">setroubleshoot-server</span>. A las negaciones se le asignan IDs, como se ve en <code class="filename">/var/log/messages</code>. El siguiente es un ejemplo de negación en <code class="filename">messages</code>:
 				</div><pre class="screen">
 setroubleshoot: SELinux is preventing httpd (httpd_t) "getattr" to /var/www/html/file1 (samba_share_t). For complete SELinux messages. run sealert -l 84e0b04d-d0ad-4347-8317-22e74f6cd020
 
 </pre><div class="para">
-				In this example, the denial ID is <code class="computeroutput">84e0b04d-d0ad-4347-8317-22e74f6cd020</code>. The <code class="option">-l</code> option takes an ID as an argument. Running the <code class="command">sealert -l 84e0b04d-d0ad-4347-8317-22e74f6cd020</code> command presents a detailed analysis of why SELinux denied access, and a possible solution for allowing access.
+				En este ejemplo, el ID de negación es <code class="computeroutput">84e0b04d-d0ad-4347-8317-22e74f6cd020</code>. La opción <code class="option">-l</code> toma un ID como argumento. Ejecutando el comando <code class="command">sealert -l 84e0b04d-d0ad-4347-8317-22e74f6cd020</code> le presenta un análisis detallado de por qué SELinux negó el acceso, y una posible solución para permitir el acceso.
 			</div><div class="para">
-				If you are running the X Window System, have the <span class="package">setroubleshoot</span> and <span class="package">setroubleshoot-server</span> packages installed, and the <code class="systemitem">setroubleshootd</code> and <code class="systemitem">auditd</code> daemons are running, a yellow star and a warning are displayed when access is denied by SELinux. Clicking on the star launches the <code class="command">sealert</code> GUI, and displays denials in HTML output:
+				Si está corriendo el Sistema de Ventanas X, tenga los paquetes <span class="package">setroubleshoot</span> y <span class="package">setroubleshoot-server</span> instalados, y los demonios <code class="systemitem">setroubleshootd</code> y <code class="systemitem">auditd</code> ejecutándose, una estrella amarilla y una advertencia se muestran cuando un acceso es negado por SELinux. Con clic sobre la estrella se lanza <code class="command">sealert</code> modo gráfico y se muestra la negación como HTML:
 			</div><div class="mediaobject"><img src="./images/sealert_gui.png" /></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-						Run the <code class="command">sealert -b</code> command to launch the <code class="command">sealert</code> GUI.
+						Ejecute el comando <code class="command">sealert -b</code> para lanzar la GUI de <code class="command">sealert</code>.
 					</div></li><li class="listitem"><div class="para">
-						Run the <code class="command">sealert -l \*</code> command to view a detailed analysis of all denials.
+						Ejecute el comando <code class="command">sealert -l \*</code> para ver un análisis detallado de todas las negaciones.
 					</div></li><li class="listitem"><div class="para">
 						As the Linux root user, run the <code class="command">sealert -a /var/log/audit/audit.log -H &gt; audit.html</code> command to create a HTML version of the <code class="command">sealert</code> analysis, as seen with the <code class="command">sealert</code> GUI.
 					</div></li></ul></div><div class="para">
-				Refer to the <span class="citerefentry"><span class="refentrytitle">sealert</span>(8)</span> manual page for further <code class="command">sealert</code> options.
+				Vaya a la página man de <span class="citerefentry"><span class="refentrytitle">sealert</span>(8)</span> para más opciones de <code class="command">sealert</code>.
 			</div></div><div class="section" title="7.3.6. Raw Audit Messages" id="sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.3.6. Raw Audit Messages</h3></div></div></div><div class="para">
-				Raw audit messages are logged to <code class="filename">/var/log/audit/audit.log</code>. The following is an example AVC denial (and the associated system call) that occurred when the Apache HTTP Server (running in the <code class="computeroutput">httpd_t</code> domain) attempted to access the <code class="filename">/var/www/html/file1</code> file (labeled with the <code class="computeroutput">samba_share_t</code> type):
+				Los mensajes crudos de auditoría se guardan en <code class="filename">/var/log/audit/audit.log</code>. El siguiente es un ejemplo de negación AVC (y su llamada a sistema asociado) que ocurrío cuando el Servidor HTTP Apache (corriendo en el dominio <code class="computeroutput">httpd_t</code>) intentó acceder el <code class="filename">/var/www/html/archivo1</code> (etiquetado con el tipo <code class="computeroutput">samba_share_t</code>):
 			</div><pre class="screen">
 type=AVC msg=audit(1226874073.147:96): avc:  denied  { getattr } for  pid=2465 comm="httpd" path="/var/www/html/file1" dev=dm-0 ino=284133 scontext=unconfined_u:system_r:httpd_t:s0 tcontext=unconfined_u:object_r:samba_share_t:s0 tclass=file
 
 type=SYSCALL msg=audit(1226874073.147:96): arch=40000003 syscall=196 success=no exit=-13 a0=b98df198 a1=bfec85dc a2=54dff4 a3=2008171 items=0 ppid=2463 pid=2465 auid=502 uid=48 gid=48 euid=48 suid=48 fsuid=48 egid=48 sgid=48 fsgid=48 tty=(none) ses=6 comm="httpd" exe="/usr/sbin/httpd" subj=unconfined_u:system_r:httpd_t:s0 key=(null)
 
 </pre><div class="variablelist"><dl><dt><span class="term"><em class="replaceable"><code>{ getattr }</code></em></span></dt><dd><div class="para">
-							The item in braces indicates the permission that was denied. <code class="computeroutput">getattr</code> indicates the source process was trying to read the target file's status information. This occurs before reading files. This action is denied due to the file being accessed having the wrong label. Commonly seen permissions include <code class="computeroutput">getattr</code>, <code class="computeroutput">read</code>, and <code class="computeroutput">write</code>.
+							El item entre llaves indica el permiso que fue negado. <code class="computeroutput">getattr</code> indica el proceso fuente que intentó leer la información de estado del archivo destino. Esto ocurre antes de leer archivos. Esta acción es negada dado que el archivo está siendo accedido con la etiqueta equivocada. Los permisos vistos comúnmente incluyen a <code class="computeroutput">getattr</code>, <code class="computeroutput">read</code> y <code class="computeroutput">write</code>.
 						</div></dd><dt><span class="term">comm="<em class="replaceable"><code>httpd</code></em>"</span></dt><dd><div class="para">
 							The executable that launched the process. The full path of the executable is found in the <code class="computeroutput">exe=</code> section of the system call (<code class="computeroutput">SYSCALL</code>) message, which in this case, is <code class="computeroutput">exe="/usr/sbin/httpd"</code>.
 						</div></dd><dt><span class="term">path="<em class="replaceable"><code>/var/www/html/file1</code></em>"</span></dt><dd><div class="para">
-							The path to the object (target) the process attempted to access.
+							La dirección al objeto (destino) al que quiere acceder el proceso.
 						</div></dd><dt><span class="term">scontext="<em class="replaceable"><code>unconfined_u:system_r:httpd_t:s0</code></em>"</span></dt><dd><div class="para">
-							The SELinux context of the process that attempted the denied action. In this case, it is the SELinux context of the Apache HTTP Server, which is running in the <code class="computeroutput">httpd_t</code> domain.
+							El contexto de SELinux del proceso que intentó la acción denegada. En este caso, es el contexto SELinux del Servidor HTTP Apache, que core en el dominio <code class="computeroutput">httpd_t</code>.
 						</div></dd><dt><span class="term">tcontext="<em class="replaceable"><code>unconfined_u:object_r:samba_share_t:s0</code></em>"</span></dt><dd><div class="para">
-							The SELinux context of the object (target) the process attempted to access. In this case, it is the SELinux context of <code class="filename">file1</code>. Note: the <code class="computeroutput">samba_share_t</code> type is not accessible to processes running in the <code class="computeroutput">httpd_t</code> domain.
+							El contexto de SELinux del objeto (destino) al que intentó acceder el proceso. En este caso, es el contexto SELinux del <code class="filename">archivo1</code>. Nota: el tipo <code class="computeroutput">samba_share_t</code> no es accesible para procesos que corren el dominio <code class="computeroutput">httpd_t</code>.
 						</div><div class="para">
-							In certain situations, the <code class="computeroutput">tcontext</code> may match the <code class="computeroutput">scontext</code>, for example, when a process attempts to execute a system service that will change characteristics of that running process, such as the user ID. Also, the <code class="computeroutput">tcontext</code> may match the <code class="computeroutput">scontext</code> when a process tries to use more resources (such as memory) than normal limits allow, resulting in a security check to see if that process is allowed to break those limits.
+							En ciertas cituaciónes, el <code class="computeroutput">tcontext</code> puede coincidir con <code class="computeroutput">scontext</code>, por ejemplo, cuando un proceso intenta ejecutar un servicio del sistema que cambiará las características de ese proceso en ejecución, tales como el ID del usuario. También el <code class="computeroutput">tcontext</code> puede coincidir con el <code class="computeroutput">scontext</code> cuando un proceso intenta usar más recursos (como la memoria) más allá de los límites normales permitidos, lo que resulta en un chequeo de seguridad para ver si el proceso tiene permitido romper esos límites.
 						</div></dd></dl></div><div class="para">
-				From the system call (<code class="computeroutput">SYSCALL</code>) message, two items are of interest:
+				Desde el mensaje de llamado al sistema (<code class="computeroutput">SYSCALL</code>) nos interesan dos ítems:
 			</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-						<code class="computeroutput">success=<em class="replaceable"><code>no</code></em></code>: indicates whether the denial (AVC) was enforced or not. <code class="computeroutput">success=no</code> indicates the system call was not successful (SELinux denied access). <code class="computeroutput">success=yes</code> indicates the system call was successful - this can be seen for permissive domains or unconfined domains, such as <code class="computeroutput">initrc_t</code> and <code class="computeroutput">kernel_t</code>.
+						<code class="computeroutput">success=<em class="replaceable"><code>no</code></em></code>: indica si la negación (AVC) fue aplicada o no. <code class="computeroutput">success=no</code> indica que la llamada al sistema no fue exitosa(SELinux negó el acceso). <code class="computeroutput">success=yes</code> indica que la llamada al sistema fue exitosa - esto se puede ver en dominios permisivos o en dominios no confinados, tales como <code class="computeroutput">initrc_t</code> y <code class="computeroutput">kernel_t</code>.
 					</div></li><li class="listitem"><div class="para">
 						<code class="computeroutput">exe="<em class="replaceable"><code>/usr/sbin/httpd</code></em>"</code>: the full path to the executable that launched the process, which in this case, is <code class="computeroutput">exe="/usr/sbin/httpd"</code>.
 					</div></li></ul></div><div class="para">
-				An incorrect file type is a common cause for SELinux denying access. To start troubleshooting, compare the source context (<code class="computeroutput">scontext</code>) with the target context (<code class="computeroutput">tcontext</code>). Should the process (<code class="computeroutput">scontext</code>) be accessing such an object (<code class="computeroutput">tcontext</code>)? For example, the Apache HTTP Server (<code class="computeroutput">httpd_t</code>) should only be accessing types specified in the <span class="citerefentry"><span class="refentrytitle">httpd_selinux</span>(8)</span> manual page, such as <code class="computeroutput">httpd_sys_content_t</code>, <code class="computeroutput">public_content_t</code>, and so on, unless configured otherwise.
-			</div></div><div class="section" title="7.3.7. sealert Messages" id="sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.3.7. sealert Messages</h3></div></div></div><div class="para">
-				Denials are assigned IDs, as seen in <code class="filename">/var/log/messages</code>. The following is an example AVC denial (logged to <code class="filename">messages</code>) that occurred when the Apache HTTP Server (running in the <code class="computeroutput">httpd_t</code> domain) attempted to access the <code class="filename">/var/www/html/file1</code> file (labeled with the <code class="computeroutput">samba_share_t</code> type):
+				Un tipo de archivo incorrecto es una causa común de que SELinux niegue el acceso. Para comenzar a resolver el problema, compare el contexto fuente (<code class="computeroutput">scontext</code>) con el contexto destino (<code class="computeroutput">tcontext</code>). ¿Debería el proceso (<code class="computeroutput">scontext</code>) acceder a un objeto (<code class="computeroutput">tcontext</code>)? Por ejemplo, el Servidor HTTP Apache (<code class="computeroutput">httpd_t</code>) sólo debería acceder tipos especificados en la página man <span class="citerefentry"><span class="refentrytitle">httpd_selinux</span>(8)</span>, tales como <code class="computeroutput">httpd_sys_content_t</code>, <code class="computeroutput">public_content_t</code>, y así sucesivamente, a menos que se configure de otra forma.
+			</div></div><div class="section" title="7.3.7. Mensajes sealert" id="sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.3.7. Mensajes sealert</h3></div></div></div><div class="para">
+				Las negaciones tienen IDs asignados, como se ve en <code class="filename">/var/log/messages</code>. El siguiente es un ejemplo de negación AVC (guardado en <code class="filename">messages</code>) que ocurrió cuando el Servidor HTTP Apache (corriendo en el dominio <code class="computeroutput">httpd_t</code> domain) intentó acceder el <code class="filename">/var/www/html/archivo1</code> (etiquetado con el tipo <code class="computeroutput">samba_share_t</code>):
 			</div><pre class="screen">
 <em class="replaceable"><code>hostname</code></em> setroubleshoot: SELinux is preventing httpd (httpd_t) "getattr" to /var/www/html/file1 (samba_share_t). For complete SELinux messages. run sealert -l 84e0b04d-d0ad-4347-8317-22e74f6cd020
 
 </pre><div class="para">
-				As suggested, run the <code class="command">sealert -l 84e0b04d-d0ad-4347-8317-22e74f6cd020</code> command to view the complete message. This command only works on the local machine, and presents the same information as the <code class="command">sealert</code> GUI:
+				Como se sugirió, ejecute el comando <code class="command">sealert -l 84e0b04d-d0ad-4347-8317-22e74f6cd020</code> para ver el mensaje completo. Este comando sólo funciona en la máquina local, y presenta la misma información que la interfase gráfica de <code class="command">sealert</code>:
 			</div><pre class="screen">
 $ sealert -l 84e0b04d-d0ad-4347-8317-22e74f6cd020
 
@@ -2020,35 +2020,35 @@ node=<em class="replaceable"><code>hostname</code></em> type=AVC msg=audit(12258
 
 node=<em class="replaceable"><code>hostname</code></em> type=SYSCALL msg=audit(1225812178.788:101): arch=40000003 syscall=196 success=no exit=-13 a0=b8e97188 a1=bf87aaac a2=54dff4 a3=2008171 items=0 ppid=2439 pid=2441 auid=502 uid=48 gid=48 euid=48 suid=48 fsuid=48 egid=48 sgid=48 fsgid=48 tty=(none) ses=3 comm="httpd" exe="/usr/sbin/httpd" subj=unconfined_u:system_r:httpd_t:s0 key=(null)
 
-</pre><div class="variablelist"><dl><dt><span class="term">Summary</span></dt><dd><div class="para">
-							A brief summary of the denied action. This is the same as the denial in <code class="filename">/var/log/messages</code>. In this example, the <code class="systemitem">httpd</code> process was denied access to a file (<code class="filename">file1</code>), which is labeled with the <code class="computeroutput">samba_share_t</code> type.
-						</div></dd><dt><span class="term">Detailed Description</span></dt><dd><div class="para">
-							A more verbose description. In this example, <code class="filename">file1</code> is labeled with the <code class="computeroutput">samba_share_t</code> type. This type is used for files and directories that you want to export via Samba. The description suggests changing the type to a type that can be accessed by the Apache HTTP Server and Samba, if such access is desired.
-						</div></dd><dt><span class="term">Allowing Access</span></dt><dd><div class="para">
-							A suggestion for how to allow access. This may be relabeling files, turning a Boolean on, or making a local policy module. In this case, the suggestion is to label the file with a type accessible to both the Apache HTTP Server and Samba.
-						</div></dd><dt><span class="term">Fix Command</span></dt><dd><div class="para">
-							A suggested command to allow access and resolve the denial. In this example, it gives the command to change the <code class="filename">file1</code> type to <code class="computeroutput">public_content_t</code>, which is accessible to the Apache HTTP Server and Samba.
-						</div></dd><dt><span class="term">Additional Information</span></dt><dd><div class="para">
-							Information that is useful in bug reports, such as the policy package name and version (<code class="computeroutput">selinux-policy-3.5.13-11.fc11</code>), but may not help towards solving why the denial occurred.
+</pre><div class="variablelist"><dl><dt><span class="term">Resumen</span></dt><dd><div class="para">
+							Un breve resumen de la acción negada. Esto es lo mismo que la negación en <code class="filename">/var/log/messages</code>. En este ejemplo, al proceso <code class="systemitem">httpd</code> se le negó el acceso al (<code class="filename">archivo1</code>), que está etiquetado con el tipo <code class="computeroutput">samba_share_t</code>.
+						</div></dd><dt><span class="term">Descripción Detallada</span></dt><dd><div class="para">
+							Una descripción más detallada. En este ejemplo <code class="filename">archivo1</code> está etiquetado con el tipo <code class="computeroutput">samba_share_t</code>. Este tipo se usa para archivos y directorios que quiere exportar vía Samba. La descripción sugiere cambiar el tipo a un tipo que pueda ser accedido por Samba y por el Servidor HTTP Apache, si tal acceso es deseado.
+						</div></dd><dt><span class="term">Permitiendo Acceso</span></dt><dd><div class="para">
+							Una sugerencia sobre cómo permitir el acceso. Esto puede hacerse reetiquetando archivos, poniendo en 1 un Booleano, o creando un módulo de política local. En este caso, la sugerencia es etiquetar el archivo con un tipo accesible por el Servidor HTTP Apache y por Samba.
+						</div></dd><dt><span class="term">Comando para Corregir</span></dt><dd><div class="para">
+							Un comando sugerido para permitir el acceso y resolver la negación. En este ejemplo, se dá el comando para cambiar el tipo del <code class="filename">archivo1</code> a <code class="computeroutput">public_content_t</code>, que es accesible por el Servidor HTTP Apache y por Samba.
+						</div></dd><dt><span class="term">Información Adicional</span></dt><dd><div class="para">
+							Información que es útil en los informes de errores, como el nombre de paquete de política y la versión (<code class="computeroutput">selinux-policy-3.5.13-11.fc11</code>), pero que no puede ser de ayuda para resolver por qué ocurrió la negación.
 						</div></dd><dt><span class="term">Raw Audit Messages</span></dt><dd><div class="para">
 							The raw audit messages from <code class="filename">/var/log/audit/audit.log</code> that are associated with the denial. Refer to <a class="xref" href="#sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages" title="7.3.6. Raw Audit Messages">Sección 7.3.6, “Raw Audit Messages”</a> for information about each item in the AVC denial.
-						</div></dd></dl></div></div><div class="section" title="7.3.8. Allowing Access: audit2allow" id="sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.3.8. Allowing Access: audit2allow</h3></div></div></div><div class="para">
-				Do not use the example in this section in production. It is used only to demonstrate the use of <code class="command">audit2allow</code>.
+						</div></dd></dl></div></div><div class="section" title="7.3.8. Permitiendo el Acceso: audit2allow" id="sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.3.8. Permitiendo el Acceso: audit2allow</h3></div></div></div><div class="para">
+				No use el ejemplo en esta sección en producción. Se usa sólo para mostrar el uso de <code class="command">audit2allow</code>.
 			</div><div class="para">
-				From the <span class="citerefentry"><span class="refentrytitle">audit2allow</span>(1)</span> manual page: "<code class="command">audit2allow</code> - generate SELinux policy allow rules from logs of denied operations"<sup>[<a id="id1051803" href="#ftn.id1051803" class="footnote">19</a>]</sup>. After analyzing denials as per <a class="xref" href="#sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages" title="7.3.7. sealert Messages">Sección 7.3.7, “sealert Messages”</a>, and if no label changes or Booleans allowed access, use <code class="command">audit2allow</code> to create a local policy module. After access is denied by SELinux, running the <code class="command">audit2allow</code> command presents Type Enforcement rules that allow the previously denied access.
+				From the <span class="citerefentry"><span class="refentrytitle">audit2allow</span>(1)</span> manual page: "<code class="command">audit2allow</code> - generate SELinux policy allow rules from logs of denied operations"<sup>[<a id="id740750" href="#ftn.id740750" class="footnote">19</a>]</sup>. After analyzing denials as per <a class="xref" href="#sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages" title="7.3.7. Mensajes sealert">Sección 7.3.7, “Mensajes sealert”</a>, and if no label changes or Booleans allowed access, use <code class="command">audit2allow</code> to create a local policy module. After access is denied by SELinux, running the <code class="command">audit2allow</code> command presents Type Enforcement rules that allow the previously denied access.
 			</div><div class="para">
-				The following example demonstrates using <code class="command">audit2allow</code> to create a policy module:
+				El siguiente ejemplo muestra el uso de <code class="command">audit2allow</code> para crear un módulo de política:
 			</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
-						A denial and the associated system call are logged to <code class="filename">/var/log/audit/audit.log</code>:
+						Una negación y la llamada al sistema asociado se graban en <code class="filename">/var/log/audit/audit.log</code>:
 					</div><pre class="screen">
 type=AVC msg=audit(1226270358.848:238): avc:  denied  { write } for  pid=13349 comm="certwatch" name="cache" dev=dm-0 ino=218171 scontext=system_u:system_r:certwatch_t:s0 tcontext=system_u:object_r:var_t:s0 tclass=dir
 
 type=SYSCALL msg=audit(1226270358.848:238): arch=40000003 syscall=39 success=no exit=-13 a0=39a2bf a1=3ff a2=3a0354 a3=94703c8 items=0 ppid=13344 pid=13349 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="certwatch" exe="/usr/bin/certwatch" subj=system_u:system_r:certwatch_t:s0 key=(null)
 
 </pre><div class="para">
-						In this example, <span class="application"><strong>certwatch</strong></span> (<code class="computeroutput">comm="certwatch"</code>) was denied write access (<code class="computeroutput">{ write }</code>) to a directory labeled with the <code class="computeroutput">var_t</code> type (<code class="computeroutput">tcontext=system_u:object_r:var_t:s0</code>). Analyze the denial as per <a class="xref" href="#sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages" title="7.3.7. sealert Messages">Sección 7.3.7, “sealert Messages”</a>. If no label changes or Booleans allowed access, use <code class="command">audit2allow</code> to create a local policy module.
+						In this example, <span class="application"><strong>certwatch</strong></span> (<code class="computeroutput">comm="certwatch"</code>) was denied write access (<code class="computeroutput">{ write }</code>) to a directory labeled with the <code class="computeroutput">var_t</code> type (<code class="computeroutput">tcontext=system_u:object_r:var_t:s0</code>). Analyze the denial as per <a class="xref" href="#sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages" title="7.3.7. Mensajes sealert">Sección 7.3.7, “Mensajes sealert”</a>. If no label changes or Booleans allowed access, use <code class="command">audit2allow</code> to create a local policy module.
 					</div></li><li class="listitem"><div class="para">
-						With a denial logged, such as the <code class="computeroutput">certwatch</code> denial in step 1, run the <code class="command">audit2allow -w -a</code> command to produce a human-readable description of why access was denied. The <code class="option">-a</code> option causes all audit logs to be read. The <code class="option">-w</code> option produces the human-readable description. The <code class="command">audit2allow</code> tool accesses <code class="filename">/var/log/audit/audit.log</code>, and as such, must be run as the Linux root user:
+						Con una negación grabada, tal como la negación de <code class="computeroutput">certwatch</code> en el paso 1, corra el comando <code class="command">audit2allow -w -a</code> para producir una descripción legible al humano sobre por qué el acceso fue negado. La opción <code class="option">-a</code> hace que se lean todos los registros de autidoría. La opción <code class="option">-w</code> produce una descripción legible al humano. La herramienta <code class="command">audit2allow</code> accede a <code class="filename">/var/log/audit/audit.log</code>, y como tal, debe ser ejecutada como usuario root de Linux:
 					</div><pre class="screen">
 # audit2allow -w -a
 type=AVC msg=audit(1226270358.848:238): avc:  denied  { write } for  pid=13349 comm="certwatch" name="cache" dev=dm-0 ino=218171 scontext=system_u:system_r:certwatch_t:s0 tcontext=system_u:object_r:var_t:s0 tclass=dir
@@ -2058,9 +2058,9 @@ type=AVC msg=audit(1226270358.848:238): avc:  denied  { write } for  pid=13349 c
 	You can use audit2allow to generate a loadable module to allow this access.
 
 </pre><div class="para">
-						As shown, access was denied due to a missing Type Enforcement rule.
+						Como se muestra, el acceso fue negado debido a que falta una regla de Obligación de Tipo.
 					</div></li><li class="listitem"><div class="para">
-						Run the <code class="command">audit2allow -a</code> command to view the Type Enforcement rule that allows the denied access:
+						Ejecute el comando <code class="command">audit2allow -a</code> para ver la regla de Obligación de Tipo que permite el acceso negado:
 					</div><pre class="screen">
 # audit2allow -a
 
@@ -2069,9 +2069,9 @@ type=AVC msg=audit(1226270358.848:238): avc:  denied  { write } for  pid=13349 c
 allow certwatch_t var_t:dir write;
 
 </pre><div class="important"><h2>Importante</h2><div class="para">
-							Missing Type Enforcement rules are usually caused by bugs in SELinux policy, and should be reported in <a href="https://bugzilla.redhat.com/">Red Hat Bugzilla</a>. For Fedora, create bugs against the <code class="computeroutput">Fedora</code> product, and select the <code class="computeroutput">selinux-policy</code> component. Include the output of the <code class="command">audit2allow -w -a</code> and <code class="command">audit2allow -a</code> commands in such bug reports.
+							La falta de reglas de Ejecución de Tipos son usualmente causados por errores en la política de SELinux, y deben ser informadas en el <a href="https://bugzilla.redhat.com/">Bugzilla de Red Hat</a>. Para Fedora, crear informes sobre el producto <code class="computeroutput">Fedora</code>, y seleccione el componente <code class="computeroutput">selinux-policy</code>. Incluya la salida de los comandos <code class="command">audit2allow -w -a</code> y <code class="command">audit2allow -a</code> en el informe del error.
 						</div></div></li><li class="listitem"><div class="para">
-						To use the rule displayed by <code class="command">audit2allow -a</code>, run the <code class="command">audit2allow -a -M <em class="replaceable"><code>mycertwatch</code></em></code> command as the Linux root user to create custom module. The <code class="option">-M</code> option creates a Type Enforcement file (<code class="filename">.te</code>) with the name specified with <code class="option">-M</code>, in your current working directory:
+						Para usar la regla mostrada por <code class="command">audit2allow -a</code>, ejecute el comando <code class="command">audit2allow -a -M <em class="replaceable"><code>mycertwatch</code></em></code> como usuario root de Linux. La opción <code class="option">-M</code> crea un archivo de Obligación de Tipo (<code class="filename">.te</code>) con el nombre especificado en <code class="option">-M</code>, en su directorio actual de trabajo:
 					</div><pre class="screen">
 # audit2allow -a -M mycertwatch
 
@@ -2084,11 +2084,11 @@ semodule -i mycertwatch.pp
 mycertwatch.pp  mycertwatch.te
 
 </pre><div class="para">
-						Also, <code class="command">audit2allow</code> compiles the Type Enforcement rule into a policy package (<code class="filename">.pp</code>). To install the module, run the <code class="command">/usr/sbin/semodule -i <em class="replaceable"><code>mycertwatch.pp</code></em></code> command as the Linux root user.
+						También, <code class="command">audit2allow</code> compila la regla de Obediencia de Tipo en un paquete de política (<code class="filename">.pp</code>). Para instalar el módulo, ejecute el comando <code class="command">/usr/sbin/semodule -i <em class="replaceable"><code>mycertwatch.pp</code></em></code> como usuario root de Linux.
 					</div><div class="important"><h2>Importante</h2><div class="para">
-							Modules created with <code class="command">audit2allow</code> may allow more access than required. It is recommended that policy created with <code class="command">audit2allow</code> be posted to an SELinux list, such as <a href="http://www.redhat.com/mailman/listinfo/fedora-selinux-list">fedora-selinux-list</a>, for review. If you believe their is a bug in policy, create a bug in <a href="https://bugzilla.redhat.com/">Red Hat Bugzilla</a>.
+							Los módulos creados con <code class="command">audit2allow</code> pueden permitir más acceso que el requerido. Se recomienda que la política creada con <code class="command">audit2allow</code> sea enviada a una lista de SELinux, tal como <a href="http://www.redhat.com/mailman/listinfo/fedora-selinux-list">fedora-selinux-list</a>, para su revisión. Si cree que hay un error en la política, informe un error en <a href="https://bugzilla.redhat.com/">Bugzilla de Red Hat</a>.
 						</div></div></li></ol></div><div class="para">
-				If you have multiple denials from multiple processes, but only want to create a custom policy for a single process, use the <code class="command">grep</code> command to narrow down the input for <code class="command">audit2allow</code>. The following example demonstrates using <code class="command">grep</code> to only send denials related to <code class="command">certwatch</code> through <code class="command">audit2allow</code>:
+				Si tiene múltiples negaciones de múltiples procesos, pero solo quiere crear una política personalizada para un proceso único, use el comando <code class="command">grep</code> para una búsqueda más refinada de <code class="command">audit2allow</code>. El siguiente ejemplo muestra el uso de <code class="command">grep</code> para sólo enviar negaciones de <code class="command">certwatch</code> a <code class="command">audit2allow</code>:
 			</div><pre class="screen">
 # grep certwatch /var/log/audit/audit.log | audit2allow -M mycertwatch2
 ******************** IMPORTANT ***********************
@@ -2098,26 +2098,26 @@ To make this policy package active, execute:
 
 </pre><div class="para">
 				Refer to Dan Walsh's <a href="http://danwalsh.livejournal.com/24750.html">"Using audit2allow to build policy modules. Revisited."</a> blog entry for further information about using <code class="command">audit2allow</code> to build policy modules.
-			</div></div></div><div class="footnotes"><br /><hr width="100" align="left" /><div class="footnote"><p><sup>[<a id="ftn.id1832245" href="#id1832245" class="para">14</a>] </sup>
-					Files in <code class="filename">/etc/selinux/targeted/contexts/files/</code> define contexts for files and directories. Files in this directory are read by <code class="command">restorecon</code> and <code class="command">setfiles</code> to restore files and directories to their default contexts.
-				</p></div><div class="footnote"><p><sup>[<a id="ftn.id1846320" href="#id1846320" class="para">15</a>] </sup>
-					The <code class="command">semanage port -a</code> command adds an entry to the <code class="filename">/etc/selinux/targeted/modules/active/ports.local</code> file. Note: by default, this file can only be viewed by the Linux root user.
-				</p></div><div class="footnote"><p><sup>[<a id="ftn.id440644" href="#id440644" class="para">16</a>] </sup>
+			</div></div></div><div class="footnotes"><br /><hr width="100" align="left" /><div class="footnote"><p><sup>[<a id="ftn.id824735" href="#id824735" class="para">14</a>] </sup>
+					Los archivos en <code class="filename">/etc/selinux/targeted/contexts/files/</code> definen los contextos de archivos y directorios. Los archivos en este directorio son leídos por <code class="command">restorecon</code> y <code class="command">setfiles</code> para restaurar archivos y directorios a sus contextos predeterminados.
+				</p></div><div class="footnote"><p><sup>[<a id="ftn.id805508" href="#id805508" class="para">15</a>] </sup>
+					El comando <code class="command">semanage port -a</code> agrega una entrada al archivo <code class="filename">/etc/selinux/targeted/modules/active/ports.local</code>. Nota: por defecto, este archivo sólo puede ser visto por el usuario root de Linux.
+				</p></div><div class="footnote"><p><sup>[<a id="ftn.id739080" href="#id739080" class="para">16</a>] </sup>
 						From the <span class="citerefentry"><span class="refentrytitle">ausearch</span>(8)</span> manual page, as shipped with the <span class="package">audit</span> package in Fedora 11.
-					</p></div><div class="footnote"><p><sup>[<a id="ftn.id440741" href="#id440741" class="para">17</a>] </sup>
+					</p></div><div class="footnote"><p><sup>[<a id="ftn.id739175" href="#id739175" class="para">17</a>] </sup>
 					From the <span class="citerefentry"><span class="refentrytitle">ausearch</span>(8)</span> manual page, as shipped with the <span class="package">audit</span> package in Fedora 11.
-				</p></div><div class="footnote"><p><sup>[<a id="ftn.id437758" href="#id437758" class="para">18</a>] </sup>
+				</p></div><div class="footnote"><p><sup>[<a id="ftn.id739276" href="#id739276" class="para">18</a>] </sup>
 						From the <span class="citerefentry"><span class="refentrytitle">aureport</span>(8)</span> manual page, as shipped with the <span class="package">audit</span> package in Fedora 11.
-					</p></div><div class="footnote"><p><sup>[<a id="ftn.id1051803" href="#id1051803" class="para">19</a>] </sup>
+					</p></div><div class="footnote"><p><sup>[<a id="ftn.id740750" href="#id740750" class="para">19</a>] </sup>
 					From the <span class="citerefentry"><span class="refentrytitle">audit2allow</span>(1)</span> manual page, as shipped with the <span class="package">policycoreutils</span> package in Fedora 11.
-				</p></div></div></div><div xml:lang="es-ES" class="chapter" title="Capítulo 8. Further Information" id="chap-Security-Enhanced_Linux-Further_Information" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 8. Further Information</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Further_Information-Contributors">8.1. Contributors</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Further_Information-Other_Resources">8.2. Other Resources</a></span></dt></dl></div><div class="section" title="8.1. Contributors" id="sect-Security-Enhanced_Linux-Further_Information-Contributors"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">8.1. Contributors</h2></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+				</p></div></div></div><div xml:lang="es-ES" class="chapter" title="Capítulo 8. Información Adicional" id="chap-Security-Enhanced_Linux-Further_Information" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 8. Información Adicional</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Further_Information-Contributors">8.1. Contributors</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Further_Information-Other_Resources">8.2. Other Resources</a></span></dt></dl></div><div class="section" title="8.1. Contributors" id="sect-Security-Enhanced_Linux-Further_Information-Contributors"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">8.1. Contributors</h2></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
 					<a href="http://fedoraproject.org/wiki/GeertWarrink">Geert Warrink</a> (translation - Dutch)
 				</div></li><li class="listitem"><div class="para">
 					<a href="http://fedoraproject.org/wiki/User:Beckerde">Domingo Becker</a> (translation - Spanish)
 				</div></li><li class="listitem"><div class="para">
 					<a href="http://fedoraproject.org/wiki/User:Logan">Daniel Cabrera</a> (translation - Spanish)
-				</div></li></ul></div></div><div class="section" title="8.2. Other Resources" id="sect-Security-Enhanced_Linux-Further_Information-Other_Resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">8.2. Other Resources</h2></div></div></div><div class="formalpara"><h5 class="formalpara">The National Security Agency (NSA)</h5>
-				From the NSA <a href="http://www.nsa.gov/research/selinux/contrib.shtml">Contributors to SELinux</a> page:
+				</div></li></ul></div></div><div class="section" title="8.2. Other Resources" id="sect-Security-Enhanced_Linux-Further_Information-Other_Resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">8.2. Other Resources</h2></div></div></div><div class="formalpara" id="form-Security-Enhanced_Linux-Further_Information-The_National_Security_Agency_NSA"><h5 class="formalpara">La Agencia de Seguridad Nacional (NSA)</h5>
+				De la página <a href="http://www.nsa.gov/research/selinux/contrib.shtml">Contribuyentes de SELinux</a>:
 			</div><div class="para">
 			<span class="emphasis"><em>Researchers in NSA's National Information Assurance Research Laboratory (NIARL) designed and implemented flexible mandatory access controls in the major subsystems of the Linux kernel and implemented the new operating system components provided by the Flask architecture, namely the security server and the access vector cache. The NSA researchers reworked the LSM-based SELinux for inclusion in Linux 2.6. NSA has also led the development of similar controls for the X Window System (XACE/XSELinux) and for Xen (XSM/Flask).</em></span>
 		</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
@@ -2126,34 +2126,34 @@ To make this policy package active, execute:
 					SELinux documentation: <a href="http://www.nsa.gov/research/selinux/docs.shtml">http://www.nsa.gov/research/selinux/docs.shtml</a>.
 				</div></li><li class="listitem"><div class="para">
 					SELinux background: <a href="http://www.nsa.gov/research/selinux/background.shtml">http://www.nsa.gov/research/selinux/background.shtml</a>.
-				</div></li></ul></div><div class="formalpara"><h5 class="formalpara">Tresys Technology</h5>
-				<a href="http://www.tresys.com/">Tresys Technology</a> are the upstream for:
+				</div></li></ul></div><div class="formalpara" id="form-Security-Enhanced_Linux-Further_Information-Tresys_Technology"><h5 class="formalpara">Tecnología de Tresys</h5>
+				<a href="http://www.tresys.com/">Tresys Technology</a> son los desarrolladores de:
 			</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-					<a href="http://userspace.selinuxproject.org/trac/">SELinux userland libraries and tools</a>.
+					<a href="http://userspace.selinuxproject.org/trac/">Herramientas y bibliotecas en el espacio del usuario para SELinux</a>.
 				</div></li><li class="listitem"><div class="para">
-					<a href="http://oss.tresys.com/projects/refpolicy">SELinux Reference Policy</a>.
-				</div></li></ul></div><div class="formalpara"><h5 class="formalpara">SELinux News</h5>
+					<a href="http://oss.tresys.com/projects/refpolicy">Política de Referencia de SELinux</a>.
+				</div></li></ul></div><div class="formalpara" id="form-Security-Enhanced_Linux-Further_Information-SELinux_News"><h5 class="formalpara">Noticias de SELinux</h5>
 				<div class="itemizedlist"><ul><li class="listitem"><div class="para">
 							News: <a href="http://selinuxnews.org/wp/">http://selinuxnews.org/wp/</a>.
 						</div></li><li class="listitem"><div class="para">
 							Planet SELinux (blogs): <a href="http://selinuxnews.org/planet/">http://selinuxnews.org/planet/</a>.
 						</div></li></ul></div>
 
-			</div><div class="formalpara"><h5 class="formalpara">SELinux Project Wiki</h5>
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Further_Information-SELinux_Project_Wiki"><h5 class="formalpara">Wiki del Proyecto SELinux</h5>
 				<div class="itemizedlist"><ul><li class="listitem"><div class="para">
 							Main page: <a href="http://selinuxproject.org/page/Main_Page">http://selinuxproject.org/page/Main_Page</a>.
 						</div></li><li class="listitem"><div class="para">
 							User resources, including links to documentation, mailing lists, websites, and tools: <a href="http://selinuxproject.org/page/User_Resources">http://selinuxproject.org/page/User_Resources</a>.
 						</div></li></ul></div>
 
-			</div><div class="formalpara"><h5 class="formalpara">Red Hat Enterprise Linux</h5>
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Further_Information-Red_Hat_Enterprise_Linux"><h5 class="formalpara">Linux para Empresas de Red Hat</h5>
 				<div class="itemizedlist"><ul><li class="listitem"><div class="para">
-							The <a href="http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.2/html/Deployment_Guide/index.html">Red Hat Enterprise Linux Deployment Guide</a> contains an SELinux <a href="http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.2/html/Deployment_Guide/selg-chapter-0054.html">References</a> section, that has links to SELinux tutorials, general information, and the technology behind SELinux.
+							La <a href="http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.2/html/Deployment_Guide/index.html">Guía de Despliegue del Linux para Empresas de Red Hat</a> contiene una sección de <a href="http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.2/html/Deployment_Guide/selg-chapter-0054.html">Referencias</a> SELinux, que tiene enlaces a tutoriales de SELinux, información general y la tecnología detrás de SELinux.
 						</div></li><li class="listitem"><div class="para">
-							The <a href="http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/selinux-guide/index.html">Red Hat Enterprise Linux 4 SELinux Guide</a>.
+							La <a href="http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/selinux-guide/index.html">Guía de SELinux del Linux para Empresas de Red Hat 4</a>.
 						</div></li></ul></div>
 
-			</div><div class="formalpara"><h5 class="formalpara">Fedora</h5>
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Further_Information-Fedora"><h5 class="formalpara">Fedora</h5>
 				<div class="itemizedlist"><ul><li class="listitem"><div class="para">
 							Main page: <a href="http://fedoraproject.org/wiki/SELinux">http://fedoraproject.org/wiki/SELinux</a>.
 						</div></li><li class="listitem"><div class="para">
@@ -2162,23 +2162,23 @@ To make this policy package active, execute:
 							Fedora Core 5 SELinux FAQ: <a href="http://docs.fedoraproject.org/selinux-faq-fc5/">http://docs.fedoraproject.org/selinux-faq-fc5/</a>.
 						</div></li></ul></div>
 
-			</div><div class="formalpara"><h5 class="formalpara">The UnOfficial SELinux FAQ</h5>
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Further_Information-The_UnOfficial_SELinux_FAQ"><h5 class="formalpara">Las Preguntas Frecuentes No Oficiales de SELinux</h5>
 				<a href="http://www.crypt.gen.nz/selinux/faq.html">http://www.crypt.gen.nz/selinux/faq.html</a>
-			</div><div class="formalpara"><h5 class="formalpara">IRC</h5>
-				On <a href="http://freenode.net/">Freenode</a>:
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Further_Information-IRC"><h5 class="formalpara">IRC</h5>
+				En <a href="http://freenode.net/">Freenode</a>:
 			</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
 					#selinux
 				</div></li><li class="listitem"><div class="para">
 					#fedora-selinux
 				</div></li></ul></div></div></div><div xml:lang="es-ES" class="appendix" title="Apéndice A. Revision History" id="appe-Security-Enhanced_Linux-Revision_History" lang="es-ES"><div class="titlepage"><div><div><h1 class="title">Revision History</h1></div></div></div><div class="para">
 		<div class="revhistory"><table border="0" width="100%" summary="Revision history"><tr><th align="left" valign="top" colspan="3"><b>Historial de revisiones</b></th></tr><tr><td align="left">Revisión 1.3</td><td align="left">Tue May 12 2009</td><td align="left"><span class="author"><span class="firstname">Scott</span> <span class="surname">Radvan</span></span></td></tr><tr><td align="left" colspan="3">
-					<table border="0" summary="Simple list" class="simplelist"><tr><td>Revision for Fedora 11</td></tr></table>
+					<table border="0" summary="Simple list" class="simplelist"><tr><td>Revisión para Fedora 11</td></tr></table>
 
 				</td></tr><tr><td align="left">Revisión 1.2</td><td align="left">Mon Jan 19 2009</td><td align="left"><span class="author"><span class="firstname">Murray</span> <span class="surname">McAllister</span></span></td></tr><tr><td align="left" colspan="3">
-					<table border="0" summary="Simple list" class="simplelist"><tr><td>Updating hyperlinks to NSA websites</td></tr></table>
+					<table border="0" summary="Simple list" class="simplelist"><tr><td>Actualización de los enlaces a sitios web de la NSA</td></tr></table>
 
 				</td></tr><tr><td align="left">Revisión 1.1</td><td align="left">Sat Dec 6 2008</td><td align="left"><span class="author"><span class="firstname">Murray</span> <span class="surname">McAllister</span></span></td></tr><tr><td align="left" colspan="3">
-					<table border="0" summary="Simple list" class="simplelist"><tr><td>Resolving <a href="https://bugzilla.redhat.com/show_bug.cgi?id=472986">Red Hat Bugzilla #472986, "httpd does not write to /etc/httpd/logs/"</a></td></tr><tr><td>Added new section, "6.6. Booleans for Users Executing Applications"</td></tr><tr><td>Minor text revisions</td></tr></table>
+					<table border="0" summary="Simple list" class="simplelist"><tr><td>Resolving <a href="https://bugzilla.redhat.com/show_bug.cgi?id=472986">Red Hat Bugzilla #472986, "httpd does not write to /etc/httpd/logs/"</a></td></tr><tr><td>Added new section, "6.6. Booleans for Users Executing Applications"</td></tr><tr><td>Revisiones menores del texto</td></tr></table>
 
 				</td></tr><tr><td align="left">Revisión 1.0</td><td align="left">Tue Nov 25 2008</td><td align="left"><span class="author"><span class="firstname">Murray</span> <span class="surname">McAllister</span></span></td></tr><tr><td align="left" colspan="3">
 					<table border="0" summary="Simple list" class="simplelist"><tr><td>Initial content release on <a href="http://docs.fedoraproject.org/">http://docs.fedoraproject.org/</a></td></tr></table>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/Common_Content/css/common.css b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/Common_Content/css/common.css
index e1f4d9f..d8a380f 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/Common_Content/css/common.css
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/Common_Content/css/common.css
@@ -50,7 +50,8 @@ body.desktop .book > .toc {
 	line-height:1.35em;
 }
 
-.toc .chapter, .toc .appendix, .toc .glossary {
+ .toc .glossary,
+.toc .chapter, .toc .appendix {
 	margin-top:1em;
 }
 
@@ -59,7 +60,8 @@ body.desktop .book > .toc {
 	display:block;
 }
 
-span.appendix, span.glossary {
+span.glossary,
+span.appendix {
 	display:block;
 	margin-top:0.5em;
 }
@@ -346,7 +348,6 @@ a.version:focus, a.version:hover {
 	clear:both;
 }
 
-
 /*revision history*/
 .revhistory {
 	display:block;
@@ -362,34 +363,24 @@ a.version:focus, a.version:hover {
 }
 
 .revhistory td {
-	text-align:right;
+	text-align :left;
 	padding:0em;
 	border: none;
 	border-top: 1px solid #fff;
+	font-weight: bold;
 }
 
-
-.revhistory tr td:first-child {
-	text-align:left;
+.revhistory .simplelist td {
+	font-weight: normal;
 }
 
-.revhistory tr td p, .revhistory tr td div.para {
-	text-align:left;
-	font-weight:bold;
-	display:block;
-	margin:0em;
-	padding:0em;
-	padding-bottom:0.7em;
-	border-bottom:1px solid #eee;
+.revhistory .simplelist {
+	margin-bottom: 1.5em;
+	margin-left: 1em;
 }
 
 .revhistory table th {
-	background-color:transparent;
-	color:#336699;
-	font-size:2em;
-	padding: 1em 0em;
-	border: none;
-	border-bottom:1px solid #eee;
+	display: none;
 }
 
 
@@ -901,6 +892,10 @@ th, td {
 	border: 1px solid #000;
 }
 
+.simplelist th, .simplelist td {
+	border: none;
+}
+
 table table td {
 	border-bottom:1px dotted #aaa;
 	background-color:white;
@@ -1007,7 +1002,8 @@ span.chapter {
 	margin-bottom:1em;
 }
 
-.glossary dt, .index dt {
+.glossary dt,
+.index dt {
 	color:#444;
 	padding-top:.5em;
 }
@@ -1375,10 +1371,6 @@ pre {
 	border-radius: 15px;
 }
 
-.term{
-	color:#336699;
-}
-
 .package, .citetitle {
 	font-style: italic;
 }
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/Common_Content/css/lang.css b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/Common_Content/css/lang.css
index e69de29..81c3115 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/Common_Content/css/lang.css
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/Common_Content/css/lang.css
@@ -0,0 +1,2 @@
+/* place holder */
+
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/appe-Security-Enhanced_Linux-Revision_History.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/appe-Security-Enhanced_Linux-Revision_History.html
index 31e24d9..c396d01 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/appe-Security-Enhanced_Linux-Revision_History.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/appe-Security-Enhanced_Linux-Revision_History.html
@@ -1,14 +1,14 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Apéndice A. Revision History</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="index.html" title="Security-Enhanced Linux" /><link rel="prev" href="sect-Security-Enhanced_Linux-Further_Information-Other_Resources.html" title="8.2. Other Resources" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedora
 project.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Further_Information-Other_Resources.html"><strong>Anterior</strong></a></li><li class="next"></li></ul><div xml:lang="es-ES" class="appendix" title="Apéndice A. Revision History" id="appe-Security-Enhanced_Linux-Revision_History" lang="es-ES"><div class="titlepage"><div><div><h1 class="title">Revision History</h1></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Apéndice A. Revision History</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="prev" href="sect-Security-Enhanced_Linux-Further_Information-Other_Resources.html" title="8.2. Other Resources" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://
 www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Further_Information-Other_Resources.html"><strong>Anterior</strong></a></li><li class="next"></li></ul><div xml:lang="es-ES" class="appendix" title="Apéndice A. Revision History" id="appe-Security-Enhanced_Linux-Revision_History" lang="es-ES"><div class="titlepage"><div><div><h1 class="title">Revision History</h1></div></div></div><div class="para">
 		<div class="revhistory"><table border="0" width="100%" summary="Revision history"><tr><th align="left" valign="top" colspan="3"><b>Historial de revisiones</b></th></tr><tr><td align="left">Revisión 1.3</td><td align="left">Tue May 12 2009</td><td align="left"><span class="author"><span class="firstname">Scott</span> <span class="surname">Radvan</span></span></td></tr><tr><td align="left" colspan="3">
-					<table border="0" summary="Simple list" class="simplelist"><tr><td>Revision for Fedora 11</td></tr></table>
+					<table border="0" summary="Simple list" class="simplelist"><tr><td>Revisión para Fedora 11</td></tr></table>
 
 				</td></tr><tr><td align="left">Revisión 1.2</td><td align="left">Mon Jan 19 2009</td><td align="left"><span class="author"><span class="firstname">Murray</span> <span class="surname">McAllister</span></span></td></tr><tr><td align="left" colspan="3">
-					<table border="0" summary="Simple list" class="simplelist"><tr><td>Updating hyperlinks to NSA websites</td></tr></table>
+					<table border="0" summary="Simple list" class="simplelist"><tr><td>Actualización de los enlaces a sitios web de la NSA</td></tr></table>
 
 				</td></tr><tr><td align="left">Revisión 1.1</td><td align="left">Sat Dec 6 2008</td><td align="left"><span class="author"><span class="firstname">Murray</span> <span class="surname">McAllister</span></span></td></tr><tr><td align="left" colspan="3">
-					<table border="0" summary="Simple list" class="simplelist"><tr><td>Resolving <a href="https://bugzilla.redhat.com/show_bug.cgi?id=472986">Red Hat Bugzilla #472986, "httpd does not write to /etc/httpd/logs/"</a></td></tr><tr><td>Added new section, "6.6. Booleans for Users Executing Applications"</td></tr><tr><td>Minor text revisions</td></tr></table>
+					<table border="0" summary="Simple list" class="simplelist"><tr><td>Resolving <a href="https://bugzilla.redhat.com/show_bug.cgi?id=472986">Red Hat Bugzilla #472986, "httpd does not write to /etc/httpd/logs/"</a></td></tr><tr><td>Added new section, "6.6. Booleans for Users Executing Applications"</td></tr><tr><td>Revisiones menores del texto</td></tr></table>
 
 				</td></tr><tr><td align="left">Revisión 1.0</td><td align="left">Tue Nov 25 2008</td><td align="left"><span class="author"><span class="firstname">Murray</span> <span class="surname">McAllister</span></span></td></tr><tr><td align="left" colspan="3">
 					<table border="0" summary="Simple list" class="simplelist"><tr><td>Initial content release on <a href="http://docs.fedoraproject.org/">http://docs.fedoraproject.org/</a></td></tr></table>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Confining_Users.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Confining_Users.html
index dcd6550..e3597a6 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Confining_Users.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Confining_Users.html
@@ -1,9 +1,9 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Capítulo 6. Confining Users</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="index.html" title="Security-Enhanced Linux" /><link rel="prev" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_star.html" title="5.10.5. Archiving Files with star" /><link rel="next" href="sect-Security-Enhanced_Linux-Confining_Users-Confining_New_Linux_Users_useradd.html" title="6.2. Confining New Linux Users: useradd" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocfr
 ame" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_star.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Confining_Users-Confining_New_Linux_Users_useradd.html"><strong>Siguiente</strong></a></li></ul><div xml:lang="es-ES" class="chapter" title="Capítulo 6. Confining Users" id="chap-Security-Enhanced_Linux-Confining_Users" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 6. Confining Users</h2></di
 v></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-Confining_Users.html#sect-Security-Enhanced_Linux-Confining_Users-Linux_and_SELinux_User_Mappings">6.1. Linux and SELinux User Mappings</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Confining_Users-Confining_New_Linux_Users_useradd.html">6.2. Confining New Linux Users: useradd</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Confining_Users-Confining_Existing_Linux_Users_semanage_login.html">6.3. Confining Existing Linux Users: semanage login</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Confining_Users-Changing_the_Default_Mapping.html">6.4. Changing the Default Mapping</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Confining_Users-xguest_Kiosk_Mode.html">6.5. xguest: Kiosk Mode</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_
 Linux-Confining_Users-Booleans_for_Users_Executing_Applications.html">6.6. Booleans for Users Executing Applications</a></span></dt></dl></div><div class="para">
-		A number of confined SELinux users are available in Fedora 11. Each Linux user is mapped to an SELinux user via SELinux policy, allowing Linux users to inherit the restrictions on SELinux users, for example (depending on the user), not being able to: run the X Window System; use networking; run setuid applications (unless SELinux policy permits it); or run the <code class="command">su</code> and <code class="command">sudo</code> commands to become the Linux root user. This helps protect the system from the user. Refer to <a class="xref" href="sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users.html" title="4.3. Confined and Unconfined Users">Sección 4.3, “Confined and Unconfined Users”</a> for further information about confined users in Fedora 11.
-	</div><div class="section" title="6.1. Linux and SELinux User Mappings" id="sect-Security-Enhanced_Linux-Confining_Users-Linux_and_SELinux_User_Mappings"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.1. Linux and SELinux User Mappings</h2></div></div></div><div class="para">
-			As the Linux root user, run the <code class="command">semanage login -l</code> command to view the mapping between Linux users and SELinux users:
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Capítulo 6. Confinando a los Usuarios</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="prev" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_star.html" title="5.10.5. Archivando archivos con tar" /><link rel="next" href="sect-Security-Enhanced_Linux-Confining_Users-Confining_New_Linux_Users_useradd.html" title="6.2. Confinando Usuarios Nuevos de Linux: useradd" /></head><body class="toc_embeded "><div id="tocdi
 v" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_star.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Confining_Users-Confining_New_Linux_Users_useradd.html"><strong>Siguiente</strong></a></li></ul><div xml:lang="es-ES" class="chapter" title="Capítulo 6. Confinando a los Usuarios" id="chap-Security-Enhanced_Linux-Confining_Users" lang="es-ES"><div class="titlepage"><div><div><h2 class="ti
 tle">Capítulo 6. Confinando a los Usuarios</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-Confining_Users.html#sect-Security-Enhanced_Linux-Confining_Users-Linux_and_SELinux_User_Mappings">6.1. Linux y los Mapeos de Usuarios de SELinux</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Confining_Users-Confining_New_Linux_Users_useradd.html">6.2. Confinando Usuarios Nuevos de Linux: useradd</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Confining_Users-Confining_Existing_Linux_Users_semanage_login.html">6.3. Confinando Usuarios Linux Existentes: semanage login</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Confining_Users-Changing_the_Default_Mapping.html">6.4. Cambiando el Mapeo Predeterminado</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Confining_Users-xguest_Kiosk_Mode.html">6.5. xguest: M
 odo Kiosk</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications.html">6.6. Booleanos para que los Usuarios Ejecuten Aplicaciones</a></span></dt></dl></div><div class="para">
+		A number of confined SELinux users are available in Fedora 11. Each Linux user is mapped to an SELinux user via SELinux policy, allowing Linux users to inherit the restrictions on SELinux users, for example (depending on the user), not being able to: run the X Window System; use networking; run setuid applications (unless SELinux policy permits it); or run the <code class="command">su</code> and <code class="command">sudo</code> commands to become the Linux root user. This helps protect the system from the user. Refer to <a class="xref" href="sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users.html" title="4.3. Usuarios Confinados y no Confinados">Sección 4.3, “Usuarios Confinados y no Confinados”</a> for further information about confined users in Fedora 11.
+	</div><div class="section" title="6.1. Linux y los Mapeos de Usuarios de SELinux" id="sect-Security-Enhanced_Linux-Confining_Users-Linux_and_SELinux_User_Mappings"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.1. Linux y los Mapeos de Usuarios de SELinux</h2></div></div></div><div class="para">
+			Como usuario root de Linux, corra el comando <code class="command">semanage login -l</code> para ver el mapeo entre los usuarios de Linux y los usuarios de SELinux:
 		</div><pre class="screen"># /usr/sbin/semanage login -l
 
 Login Name                SELinux User              MLS/MCS Range
@@ -13,8 +13,8 @@ root                      unconfined_u              s0-s0:c0.c1023
 system_u                  system_u                  s0-s0:c0.c1023
 
 </pre><div class="para">
-			In Fedora 11, Linux users are mapped to the SELinux <code class="computeroutput">__default__</code> login by default (which is mapped to the SELinux <code class="computeroutput">unconfined_u</code> user). When a Linux user is created with the <code class="command">useradd</code> command, if no options are specified, they are mapped to the SELinux <code class="computeroutput">unconfined_u</code> user. The following defines the default-mapping:
+			En Fedora 11, los usuarios Linux se mapean al ingreso SELinux <code class="computeroutput">__default__</code> por defecto (que se mapea al usuario SELinux <code class="computeroutput">unconfined_u</code>). Cuando se crea un usuario Linux con el comando <code class="command">useradd</code>, si no se especifica ninguna opcion, son mapeados al usuario SELinux <code class="computeroutput">unconfined_u</code>. Lo siguiente define el mapeo por defecto:
 		</div><pre class="screen">
 __default__               unconfined_u              s0-s0:c0.c1023
 
-</pre></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_star.html"><strong>Anterior</strong>5.10.5. Archiving Files with star</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Confining_Users-Confining_New_Linux_Users_useradd.html"><strong>Siguiente</strong>6.2. Confining New Linux Users: useradd</a></li></ul></body></html>
+</pre></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_star.html"><strong>Anterior</strong>5.10.5. Archivando archivos con tar</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Confining_Users-Confining_New_Linux_Users_useradd.html"><strong>Siguiente</strong>6.2. Confinando Usuarios Nuevos de Linux: useradd</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Further_Information.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Further_Information.html
index 146af45..41609d8 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Further_Information.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Further_Information.html
@@ -1,9 +1,9 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Capítulo 8. Further Information</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="index.html" title="Security-Enhanced Linux" /><link rel="prev" href="sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow.html" title="7.3.8. Allowing Access: audit2allow" /><link rel="next" href="sect-Security-Enhanced_Linux-Further_Information-Other_Resources.html" title="8.2. Other Resources" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc
 .html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Further_Information-Other_Resources.html"><strong>Siguiente</strong></a></li></ul><div xml:lang="es-ES" class="chapter" title="Capítulo 8. Further Information" id="chap-Security-Enhanced_Linux-Further_Information" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 8. Further Information</h2></div></div></div><div class="toc"><dl><dt><span clas
 s="section"><a href="chap-Security-Enhanced_Linux-Further_Information.html#sect-Security-Enhanced_Linux-Further_Information-Contributors">8.1. Contributors</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Further_Information-Other_Resources.html">8.2. Other Resources</a></span></dt></dl></div><div class="section" title="8.1. Contributors" id="sect-Security-Enhanced_Linux-Further_Information-Contributors"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">8.1. Contributors</h2></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Capítulo 8. Información Adicional</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="prev" href="sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow.html" title="7.3.8. Permitiendo el Acceso: audit2allow" /><link rel="next" href="sect-Security-Enhanced_Linux-Further_Information-Other_Resources.html" title="8.2. Other Resources" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" s
 rc="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Further_Information-Other_Resources.html"><strong>Siguiente</strong></a></li></ul><div xml:lang="es-ES" class="chapter" title="Capítulo 8. Información Adicional" id="chap-Security-Enhanced_Linux-Further_Information" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 8. Información Adicional</h2></div></div></div><div class
 ="toc"><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-Further_Information.html#sect-Security-Enhanced_Linux-Further_Information-Contributors">8.1. Contributors</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Further_Information-Other_Resources.html">8.2. Other Resources</a></span></dt></dl></div><div class="section" title="8.1. Contributors" id="sect-Security-Enhanced_Linux-Further_Information-Contributors"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">8.1. Contributors</h2></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
 					<a href="http://fedoraproject.org/wiki/GeertWarrink">Geert Warrink</a> (translation - Dutch)
 				</div></li><li class="listitem"><div class="para">
 					<a href="http://fedoraproject.org/wiki/User:Beckerde">Domingo Becker</a> (translation - Spanish)
 				</div></li><li class="listitem"><div class="para">
 					<a href="http://fedoraproject.org/wiki/User:Logan">Daniel Cabrera</a> (translation - Spanish)
-				</div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow.html"><strong>Anterior</strong>7.3.8. Allowing Access: audit2allow</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Further_Information-Other_Resources.html"><strong>Siguiente</strong>8.2. Other Resources</a></li></ul></body></html>
+				</div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow.html"><strong>Anterior</strong>7.3.8. Permitiendo el Acceso: audit2allow</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Further_Information-Other_Resources.html"><strong>Siguiente</strong>8.2. Other Resources</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Introduction.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Introduction.html
index 1783973..6d30b98 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Introduction.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Introduction.html
@@ -1,49 +1,49 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Capítulo 2. Introduction</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="index.html" title="Security-Enhanced Linux" /><link rel="prev" href="chap-Security-Enhanced_Linux-Trademark_Information.html" title="Capítulo 1. Trademark Information" /><link rel="next" href="sect-Security-Enhanced_Linux-Introduction-Examples.html" title="2.2. Examples" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your b
 rowser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-Trademark_Information.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Introduction-Examples.html"><strong>Siguiente</strong></a></li></ul><div xml:lang="es-ES" class="chapter" title="Capítulo 2. Introduction" id="chap-Security-Enhanced_Linux-Introduction" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 2. Introduction</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-Introduction.html#sect-Security-Enhanced_Linux-Introductio
 n-Benefits_of_running_SELinux">2.1. Benefits of running SELinux</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Introduction-Examples.html">2.2. Examples</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture.html">2.3. SELinux Architecture</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Introduction-SELinux_on_Other_Operating_Systems.html">2.4. SELinux on Other Operating Systems</a></span></dt></dl></div><div class="para">
-		Files, such as directories and devices, are called objects. Processes, such as a user running a command or the <span class="trademark">Mozilla</span>®<span class="trademark"> Firefox</span>® application, are called subjects. Most operating systems use a Discretionary Access Control (DAC) system that controls how subjects interact with objects, and how subjects interact with each other. On operating systems using DAC, users control the permissions of files (objects) that they own. For example, on <span class="trademark">Linux</span>® operating systems, users can make their home directories world-readable, giving users and processes (subjects) access to potentially sensitive information.
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Capítulo 2. Introducción</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="prev" href="chap-Security-Enhanced_Linux-Trademark_Information.html" title="Capítulo 1. Información de Marca Comercial" /><link rel="next" href="sect-Security-Enhanced_Linux-Introduction-Examples.html" title="2.2. Ejemplos" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to v
 iew it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-Trademark_Information.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Introduction-Examples.html"><strong>Siguiente</strong></a></li></ul><div xml:lang="es-ES" class="chapter" title="Capítulo 2. Introducción" id="chap-Security-Enhanced_Linux-Introduction" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 2. Introducción</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-Introduction.html#sect-Security-Enh
 anced_Linux-Introduction-Benefits_of_running_SELinux">2.1. Beneficios de usar SELinux</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Introduction-Examples.html">2.2. Ejemplos</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture.html">2.3. Arquitectura de SELinux</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Introduction-SELinux_on_Other_Operating_Systems.html">2.4. SELinux en otros Sistemas Operativos</a></span></dt></dl></div><div class="para">
+		Los Archivos, tales como directorios y dispositivos, se llaman objetos. Los procesos, tal como un comando que ejecuta el usuario o la aplicación <span class="trademark">Mozilla</span>®<span class="trademark"> Firefox</span>®, se llaman sujetos. La mayoría de los sistemas oeprativos usan un sistema de Control de Acceso Discrecional (DAC), que controla cómo interactuan los sujetos con los objetos, y cómo los sujetos interactuan entre sí. En sistemas operativos que usan DAC, los usuarios controlan los permisos de archivos (objetos) de los que son dueños. Por ejemplo, en sistemas operativos <span class="trademark">Linux</span>®, los usuarios pueden hacer sus directorios legibles para el resto del mundo, dando a los usuarios y procesos (sujetos) acceso a información potencialmente sensible.
 	</div><div class="para">
-		DAC mechanisms are fundamentally inadequate for strong system security. DAC access decisions are only based on user identity and ownership, ignoring other security-relevant information such as the role of the user, the function and trustworthiness of the program, and the sensitivity and integrity of the data. Each user has complete discretion over their files, making it impossible to enforce a system-wide security policy. Furthermore, every program run by a user inherits all of the permissions granted to the user and is free to change access to the user's files, so no protection is provided against malicious software. Many system services and privileged programs must run with coarse-grained privileges that far exceed their requirements, so that a flaw in any one of these programs can be exploited to obtain complete system access.<sup>[<a id="id438233" href="#ftn.id438233" class="footnote">1</a>]</sup>
+		DAC mechanisms are fundamentally inadequate for strong system security. DAC access decisions are only based on user identity and ownership, ignoring other security-relevant information such as the role of the user, the function and trustworthiness of the program, and the sensitivity and integrity of the data. Each user has complete discretion over their files, making it impossible to enforce a system-wide security policy. Furthermore, every program run by a user inherits all of the permissions granted to the user and is free to change access to the user's files, so no protection is provided against malicious software. Many system services and privileged programs must run with coarse-grained privileges that far exceed their requirements, so that a flaw in any one of these programs can be exploited to obtain complete system access.<sup>[<a id="id1022406" href="#ftn.id1022406" class="footnote">1</a>]</sup>
 	</div><div class="para">
-		The following is an example of permissions used on Linux operating systems that do not run Security-Enhanced Linux (SELinux). The permissions in these examples may differ from your system. Use the <code class="command">ls -l</code> command to view file permissions:
+		El siguiente es un ejemplo de permisos usados en sistemas operativos Linux que no corren el Linux de Seguridad Mejorada (SELinux). Los permisos en estos ejemplos pueden diferir de su sistema. Use el comando <code class="command">ls -l</code> para ver los permisos de archivos:
 	</div><pre class="screen">$ ls -l file1
 -rwxrw-r-- 1 user1 group1 0 2009-04-30 15:42 file1
 
 </pre><div class="para">
-		The first three permission bits, <code class="computeroutput">rwx</code>, control the access the Linux <code class="computeroutput">user1</code> user (in this case, the owner) has to <code class="filename">file1</code>. The next three permission bits, <code class="computeroutput">rw-</code>, control the access the Linux <code class="computeroutput">group1</code> group has to <code class="filename">file1</code>. The last three permission bits, <code class="computeroutput">r--</code>, control the access everyone else has to <code class="filename">file1</code>, which includes all users and processes.
+		Los primeros tres bits de permisos, <code class="computeroutput">rwx</code>, controlan el acceso que el usuario Linux <code class="computeroutput">usuario1</code> (en este caso, el dueño) tiene para el <code class="filename">archivo1</code>. Los siguientes tres bits de permisos, <code class="computeroutput">rw-</code>, controlan el acceso que el grupo Linux <code class="computeroutput">grupo1</code> tiene para el <code class="filename">archivo1</code>. Los últimos tres bits de permisos, <code class="computeroutput">r--</code>, controlan el acceso que todo el mundo tiene para el <code class="filename">archivo1</code>, que incluyen a todos los usuarios y procesos.
 	</div><div class="para">
-		Security-Enhanced Linux (SELinux) adds Mandatory Access Control (MAC) to the Linux kernel, and is enabled by default in Fedora. A general purpose MAC architecture needs the ability to enforce an administratively-set security policy over all processes and files in the system, basing decisions on labels containing a variety of security-relevant information. When properly implemented, it enables a system to adequately defend itself and offers critical support for application security by protecting against the tampering with, and bypassing of, secured applications. MAC provides strong separation of applications that permits the safe execution of untrustworthy applications. Its ability to limit the privileges associated with executing processes limits the scope of potential damage that can result from the exploitation of vulnerabilities in applications and system services. MAC enables information to be protected from legitimate users with limited authorization as well as from a
 uthorized users who have unwittingly executed malicious applications.<sup>[<a id="id1607935" href="#ftn.id1607935" class="footnote">2</a>]</sup>
+		Security-Enhanced Linux (SELinux) adds Mandatory Access Control (MAC) to the Linux kernel, and is enabled by default in Fedora. A general purpose MAC architecture needs the ability to enforce an administratively-set security policy over all processes and files in the system, basing decisions on labels containing a variety of security-relevant information. When properly implemented, it enables a system to adequately defend itself and offers critical support for application security by protecting against the tampering with, and bypassing of, secured applications. MAC provides strong separation of applications that permits the safe execution of untrustworthy applications. Its ability to limit the privileges associated with executing processes limits the scope of potential damage that can result from the exploitation of vulnerabilities in applications and system services. MAC enables information to be protected from legitimate users with limited authorization as well as from a
 uthorized users who have unwittingly executed malicious applications.<sup>[<a id="id776804" href="#ftn.id776804" class="footnote">2</a>]</sup>
 	</div><div class="para">
-		The following is an example of the labels containing security-relevant information that are used on processes, Linux users, and files, on Linux operating systems that run SELinux. This information is called the SELinux context, and is viewed using the <code class="command">ls -Z</code> command:
+		El siguiente es un ejemplo de las etiquetas que contienen información de seguridad relevante que se usa en los procesos, usuarios Linux y archivos, en sistemas operativos Linux que corren SELinux. Esta información se llama contexto de SELinux y se visualiza usando el comando <code class="command">ls -Z</code>:
 	</div><pre class="screen">$ ls -Z file1
 -rwxrw-r--  user1 group1 unconfined_u:object_r:user_home_t:s0      file1
 
 </pre><div class="para">
-		In this example, SELinux provides a user (<code class="computeroutput">unconfined_u</code>), a role (<code class="computeroutput">object_r</code>), a type (<code class="computeroutput">user_home_t</code>), and a level (<code class="computeroutput">s0</code>). This information is used to make access control decisions. With DAC, access is controlled based only on Linux user and group IDs. SELinux policy rules are checked after DAC rules. SELinux policy rules are not used if DAC rules deny access first.
-	</div><div class="formalpara"><h5 class="formalpara">Linux and SELinux Users</h5>
+		En este ejemplo, SELinux provee un usuario (<code class="computeroutput">unconfined_u</code>), un rol (<code class="computeroutput">object_r</code>), un tipo (<code class="computeroutput">user_home_t</code>), y un nivel (<code class="computeroutput">s0</code>). Esta información se usa para tomar decisiones sobre el control de acceso. Con DAC, el acceso se controla basado sólo en los IDs de usuarios y grupos de Linux. Las reglas de políticas de SELinux se chequean después de las reglas DAC. Las reglas de políticas de SELInux no se usan si las reglas DAC niegan el acceso al principio.
+	</div><div class="formalpara" id="form-Security-Enhanced_Linux-Introduction-Linux_and_SELinux_Users"><h5 class="formalpara">Linux y los Usuarios SELinux</h5>
 			On Linux operating systems that run SELinux, there are Linux users as well as SELinux users. SELinux users are part of SELinux policy. Linux users are mapped to SELinux users. To avoid confusion, this guide uses "Linux user" and "SELinux user" to differentiate between the two.
-		</div><div class="section" title="2.1. Benefits of running SELinux" id="sect-Security-Enhanced_Linux-Introduction-Benefits_of_running_SELinux"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.1. Benefits of running SELinux</h2></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-					All processes and files are labeled with a type. A type defines a domain for processes, and a type for files. Processes are separated from each other by running in their own domains, and SELinux policy rules define how processes interact with files, as well as how processes interact with each other. Access is only allowed if an SELinux policy rule exists that specifically allows it.
+		</div><div class="section" title="2.1. Beneficios de usar SELinux" id="sect-Security-Enhanced_Linux-Introduction-Benefits_of_running_SELinux"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.1. Beneficios de usar SELinux</h2></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+					Todos los procesos y archivos se etiquetan con un tipo. Un tipo define un dominio para los procesos y un tipo para los archivos. Los procesos se separan entre sí corriéndolos en sus propios dominios, y las reglas de políticas de SELinux define cómo interactúan los procesos con los archivos, así como la forma en que interactúan entre sí. El acceso sólo se permite si existe una regla de política de SELinux que específicamente lo permita.
 				</div></li><li class="listitem"><div class="para">
-					Fine-grained access control. Stepping beyond traditional <span class="trademark">UNIX</span>® permissions that are controlled at user discretion and based on Linux user and group IDs, SELinux access decisions are based on all available information, such as an SELinux user, role, type, and, optionally, a level.
+					Control de acceso más fino. Yendo un paso más alla de los permisos tradicionales de <span class="trademark">UNIX</span>® que se controlan a discreción del usuario y se basa en los IDs de usuario y de grupos de Linux, las decisiones de accesos de SELinux se basan en toda la información disponible, tales como un usuario SELinux, el rol, el tipo y, opcionalmente, un nivel.
 				</div></li><li class="listitem"><div class="para">
-					SELinux policy is administratively-defined, enforced system-wide, and is not set at user discretion.
+					La política de SELinux se define administrativamente, obligando a todo el sistema, y no se pone a discreción del usuario.
 				</div></li><li class="listitem"><div class="para">
-					Reduced vulnerability to privilege escalation attacks. One example: since processes run in domains, and are therefore separated from each other, and SELinux policy rules define how processes access files and other processes, if a process is compromised, the attacker only has access to the normal functions of that process, and to files the process has been configured to have access to. For example, if the Apache HTTP Server is compromised, an attacker can not use that process to read files in user home directories, unless a specific SELinux policy rule was added or configured to allow such access.
+					Vulnerabilidad reducida para ataques de escalamiento de privilegios. Un ejemplo: dado que los procesos corren en dominios, y son por lo tanto separados entresi, y las reglas de la política de SELinux definen cómo los procesos acceden a los archivos y a otros procesos, si un proceso queda comprometido, el atacante sólo tiene acceso a las funciones normales de ese proceso, y a archivos a los que el proceso tiene configurado que puede acceder. Por ejemplo, si el Servidor HTTP Apache es comprometido, un atacante no puede usar el proceso para leer archivos en los directorios home de los usuarios, a menos que una regla específica de la política de SELinux haya sido agregada o configurada para permitir tal acceso.
 				</div></li><li class="listitem"><div class="para">
-					SELinux can be used to enforce data confidentiality and integrity, as well as protecting processes from untrusted inputs.
+					Se linux se puede usar para asegurar la confidencialidad e integridad de los datos, así como proteger los procesos de entradas no confiables.
 				</div></li></ul></div><div class="para">
-			SELinux is not:
+			SELinux no es:
 		</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-					antivirus software.
+					software antivirus.
 				</div></li><li class="listitem"><div class="para">
-					a replacement for passwords, firewalls, or other security systems.
+					un reemplazo para las contraseñas, cortafuegos y otros sistemas de seguridad.
 				</div></li><li class="listitem"><div class="para">
-					an all-in-one security solution.
+					una solución todo en uno.
 				</div></li></ul></div><div class="para">
-			SELinux is designed to enhance existing security solutions, not replace them. Even when running SELinux, continue to follow good security practices, such as keeping software up-to-date, using hard-to-guess passwords, firewalls, and so on.
-		</div></div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id438233" href="#id438233" class="para">1</a>] </sup>
+			SELinux está diseñado para mejorar las soluciones de seguridad existentes, no reemplazarlas. Aún cuando corra SELinux, siga las buenas prácticas de seguridad, tales como mantener el software actualizado, usar contraseñas difíciles de adivinar, cortafuegos y demás.
+		</div></div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id1022406" href="#id1022406" class="para">1</a>] </sup>
 			"Integrating Flexible Support for Security Policies into the Linux Operating System", by Peter Loscocco and Stephen Smalley. This paper was originally prepared for the National Security Agency and is, consequently, in the public domain. Refer to the <a href="http://www.nsa.gov/research/_files/selinux/papers/freenix01/index.shtml">original paper</a> for details and the document as it was first released. Any edits and changes were done by Murray McAllister.
-		</p></div><div class="footnote"><p><sup>[<a id="ftn.id1607935" href="#id1607935" class="para">2</a>] </sup>
+		</p></div><div class="footnote"><p><sup>[<a id="ftn.id776804" href="#id776804" class="para">2</a>] </sup>
 			"Meeting Critical Security Objectives with Security-Enhanced Linux", by Peter Loscocco and Stephen Smalley. This paper was originally prepared for the National Security Agency and is, consequently, in the public domain. Refer to the <a href="http://www.nsa.gov/research/_files/selinux/papers/ottawa01/index.shtml">original paper</a> for details and the document as it was first released. Any edits and changes were done by Murray McAllister.
-		</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-Trademark_Information.html"><strong>Anterior</strong>Capítulo 1. Trademark Information</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Introduction-Examples.html"><strong>Siguiente</strong>2.2. Examples</a></li></ul></body></html>
+		</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-Trademark_Information.html"><strong>Anterior</strong>Capítulo 1. Información de Marca Comercial</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Introduction-Examples.html"><strong>Siguiente</strong>2.2. Ejemplos</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-SELinux_Contexts.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-SELinux_Contexts.html
index bb90cd2..5b61dfa 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-SELinux_Contexts.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-SELinux_Contexts.html
@@ -1,16 +1,16 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Capítulo 3. SELinux Contexts</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="index.html" title="Security-Enhanced Linux" /><link rel="prev" href="sect-Security-Enhanced_Linux-Introduction-SELinux_on_Other_Operating_Systems.html" title="2.4. SELinux on Other Operating Systems" /><link rel="next" href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Processes.html" title="3.2. SELinux Contexts for Processes" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" 
 class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Introduction-SELinux_on_Other_Operating_Systems.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Processes.html"><strong>Siguiente</strong></a></li></ul><div xml:lang="es-ES" class="chapter" title="Capítulo 3. SELinux Contexts" id="chap-Security-Enhanced_Linux-SELinux_Contexts" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 3. SELinux Contexts</h2></div></div></
 div><div class="toc"><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-SELinux_Contexts.html#sect-Security-Enhanced_Linux-SELinux_Contexts-Domain_Transitions">3.1. Domain Transitions</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Processes.html">3.2. SELinux Contexts for Processes</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Users.html">3.3. SELinux Contexts for Users</a></span></dt></dl></div><div class="para">
-		Processes and files are labeled with an SELinux context that contains additional information, such as an SELinux user, role, type, and, optionally, a level. When running SELinux, all of this information is used to make access control decisions. In Fedora 11, SELinux provides a combination of Role-Based Access Control (RBAC), <span class="trademark">Type Enforcement</span>® (TE), and, optionally, Multi-Level Security (MLS).
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Capítulo 3. Contextos de SELinux</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="prev" href="sect-Security-Enhanced_Linux-Introduction-SELinux_on_Other_Operating_Systems.html" title="2.4. SELinux en otros Sistemas Operativos" /><link rel="next" href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Processes.html" title="3.2. Contextos de SELinux para los Procesos" /></head><body class="toc_embeded "><div id="tocdiv" class="toc
 "><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Introduction-SELinux_on_Other_Operating_Systems.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Processes.html"><strong>Siguiente</strong></a></li></ul><div xml:lang="es-ES" class="chapter" title="Capítulo 3. Contextos de SELinux" id="chap-Security-Enhanced_Linux-SELinux_Contexts" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 3. Context
 os de SELinux</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-SELinux_Contexts.html#sect-Security-Enhanced_Linux-SELinux_Contexts-Domain_Transitions">3.1. Transiciones de Dominios</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Processes.html">3.2. Contextos de SELinux para los Procesos</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Users.html">3.3. Contextos de SELinux para los Usuarios</a></span></dt></dl></div><div class="para">
+		Los procesos y archivos se etiquetan con un contexto SELinux que contiene información adicional, tal como un usuario SELinux, rol, tipo y, opcionalmente, un nivel. Cuando se ejecuta SELinux, toda esta información se usa para tomar decisiones de control de acceso. En Fedora 11, SELinux provee una combinación de Control de Acceso Basado en Roles (RBAC en inglés), <span class="trademark">Obligación de Tipos</span>® (TE en inglés), y, opcionalmente, Seguridad Multi-nivel (MLS en inglés).
 	</div><div class="para">
-		The following is an example SELinux context. SELinux contexts are used on processes, Linux users, and files, on Linux operating systems that run SELinux. Use the <code class="command">ls -Z</code> command to view the SELinux context of files and directories:
+		El siguiente es un ejemplo de contexto de SELinux. Los contextos de SELinux se usan en procesos, usuarios de Linux y archivos, en sistemas operativos Linux que corren SELinux. Use el comando <code class="command">ls -Z</code> para ver el contexto SELinux de archivos y directorios:
 	</div><pre class="screen">$ ls -Z file1
 -rwxrw-r--  user1 group1 unconfined_u:object_r:user_home_t:s0      file1
 
 </pre><div class="para">
-		SELinux contexts follow the <span class="emphasis"><em>SELinux user:role:type:level</em></span> syntax:
+		Los contextos de SELinux siguen la <span class="emphasis"><em>SELinux nombre-de-usuario:role:type:level</em></span> sintaxis:
 	</div><div class="variablelist"><dl><dt><span class="term"><span class="emphasis"><em>SELinux user</em></span></span></dt><dd><div class="para">
-					The SELinux user identity is an identity known to the policy that is authorized for a specific set of roles, and for a specific MLS range. Each Linux user is mapped to an SELinux user via SELinux policy. This allows Linux users to inherit the restrictions on SELinux users. The mapped SELinux user identity is used in the SELinux context for processes in that session, in order to bound what roles and levels they can enter. Run the <code class="command">semanage login -l</code> command as the Linux root user to view a list of mappings between SELinux and Linux user accounts:
+					La identidad de usuario SELinux es una identidad conocida para la política a la que se le autoriza un conjunto específico de roles, y un rango específico de MLS. Cada usuario Linux se mapea a un usuario SELinux vía la política de SELinux. Esto permite a los usuarios de LInux heredar las restricciones de los usuarios SELinux. La identidad del usuario SELinux mapeado se usa en el contexto de SELinux para procesos en esa sesión, para agrupar a qué roles y niveles pueden ingresar. Ejecute el comando <code class="command">semanage login -l</code> como usuario root de Linux para ver una lista de mapeos entre cuentas de usuarios Linux y SELinux:
 				</div><pre class="screen">
 # /usr/sbin/semanage login -l
 
@@ -21,43 +21,43 @@ root                      unconfined_u              s0-s0:c0.c1023
 system_u                  system_u                  s0-s0:c0.c1023
 
 </pre><div class="para">
-					Output may differ from system to system. The <code class="computeroutput">Login Name</code> column lists Linux users, and the the <code class="computeroutput">SELinux User</code> column lists which SELinux user is mapped to which Linux user. For processes, the SELinux user limits which roles and levels are accessible. The last column, <code class="computeroutput">MLS/MCS Range</code>, is the level used by Multi-Level Security (MLS) and Multi-Category Security (MCS). Levels are briefly discussed later.
+					La salida puede ser distinta de sistema a sistema. La columna <code class="computeroutput">Nombre de Ingreso</code> lista los usuarios Linux, y la columna <code class="computeroutput">Usuario SELinux</code> lista qué a usuario SELinux es mapeado un usuario Linux. Para procesos, el usuario SELinux limita qué roles y niveles son accesibles. La última columna, <code class="computeroutput">Rango MLS/MCS</code>, es el nivel usado por la Seguridad Multi Nivel (MLS) y por la Seguridad Multi Categoría (MCS). Los niveles se describen brevemente más adelante.
 				</div></dd><dt><span class="term"><span class="emphasis"><em>role</em></span></span></dt><dd><div class="para">
-					Part of SELinux is the Role-Based Access Control (RBAC) security model. The role is an attribute of RBAC. SELinux users are authorized for roles, and roles are authorized for domains. The role serves as an intermediary between domains and SELinux users. The roles that can be entered determine which domains can be entered - ultimately, this controls which object types can be accessed. This helps reduce vulnerability to privilege escalation attacks.
+					Parte de SELinux es el modelo de seguridad de Control de Acceso Basado en Roles (RBAC). El rol es un atributo de RBAC. Los usuarios de SELinux son autorizados para ciertos roles y los roles son autorizados para ciertos dominios. Los roles sirven como un intermediario entre dominios y usarios SELinux. Los roles en los que se puede ingresar determinan los dominios a los que se ingresan - al final, esto controla los tipos de objetos que se pueden acceder. Esto ayuda a reducir la vulnerabilidad de ataques de escalada de privilegios.
 				</div></dd><dt><span class="term"><span class="emphasis"><em>type</em></span></span></dt><dd><div class="para">
-					The type is an attribute of Type Enforcement. The type defines a domain for processes, and a type for files. SELinux policy rules define how types access each other, whether it be a domain accessing a type, or a domain accessing another domain. Access is only allowed if a specific SELinux policy rule exists that allows it.
+					El tipo es un atributo de la Obligación de Tipos. El tipo define un dominio para procesos y un tipo para los archivos. Las reglas de políticas de SELinux define cómo se acceden los tipos entre si, ya sea un dominio que accede a un tipo o un dominio que accede a otro dominio. Los acceso sólo se permiten si existe una regla de política de SELinux que lo permita.
 				</div></dd><dt><span class="term"><span class="emphasis"><em>level</em></span></span></dt><dd><div class="para">
-					The level is an attribute of MLS and Multi-Category Security (MCS). An MLS range is a pair of levels, written as <span class="emphasis"><em>lowlevel-highlevel</em></span> if the levels differ, or <span class="emphasis"><em>lowlevel</em></span> if the levels are identical (<code class="computeroutput">s0-s0</code> is the same as <code class="computeroutput">s0</code>). Each level is a sensitivity-category pair, with categories being optional. If there are categories, the level is written as <span class="emphasis"><em>sensitivity:category-set</em></span>. If there are no categories, it is written as <span class="emphasis"><em>sensitivity</em></span>.
+					El nivel es un atributo de MLS y la Seguridad Multi Categoría (MCS). Un rango MLS es un par de niveles, escrito como <span class="emphasis"><em>bajonivel-altonivel</em></span> si los niveles sin distintos, o <span class="emphasis"><em>bajonivel</em></span> si los niveles son idénticos (<code class="computeroutput">s0-s0</code> es lo mismo que <code class="computeroutput">s0</code>). Cada nivel es un par sensible a categorías, donde las categorías son opcionales. Si no hay categorías, el nivel se escribe como <span class="emphasis"><em>sensibilidad:conjunto-de-categoría</em></span>. Si no hay categorías, se escribe como <span class="emphasis"><em>sensibilidad</em></span>.
 				</div><div class="para">
-					If the category set is a contiguous series, it can be abbreviated. For example, <code class="computeroutput">c0.c3</code> is the same as <code class="computeroutput">c0,c1,c2,c3</code>. The <code class="filename">/etc/selinux/targeted/setrans.conf</code> file maps levels (<code class="computeroutput">s0:c0</code>) to human-readable form (<code class="computeroutput">CompanyConfidential</code>). Do not edit <code class="filename">setrans.conf</code> with a text editor: use <code class="command">semanage</code> to make changes. Refer to the <span class="citerefentry"><span class="refentrytitle">semanage</span>(8)</span> manual page for further information. In Fedora 11, targeted policy enforces MCS, and in MCS, there is one sensitivity, <code class="computeroutput">s0</code>. MCS in Fedora 11 supports 1024 different categories: <code class="computeroutput">c0</code> through to <code class="computeroutput">c1023</code>. <code class="computeroutput">s0-s0:c0.c1023</code> is
  sensitivity <code class="computeroutput">s0</code> and authorized for all categories.
+					Si el conjunto de categoría es una serie contigua, se puede abreviar. Por ejemplo, <code class="computeroutput">c0.c3</code> es lo mismo que <code class="computeroutput">c0,c1,c2,c3</code>. El archivo <code class="filename">/etc/selinux/targeted/setrans.conf</code> mapea los niveles (<code class="computeroutput">s0:c0</code>) a una forma legible al humano (<code class="computeroutput">CompanyConfidential</code>). No edite <code class="filename">setrans.conf</code> con un editor de texto: use <code class="command">semanage</code> para hacer cambios. Vaya a la página de manual de <span class="citerefentry"><span class="refentrytitle">semanage</span>(8)</span> para más información. En Fedora 11, la política destinada obglica MCS, y en MCS hay sólo una sensibilidad, la <code class="computeroutput">s0</code>. MCS en Fedora 11 soporta 1024 categorías distintas: <code class="computeroutput">c0</code> a <code class="computeroutput">c1023</code>. <code class="computeroutp
 ut">s0-s0:c0.c1023</code> es la sensibilidad <code class="computeroutput">s0</code> y autorizado para todas las categorías.
 				</div><div class="para">
-					MLS enforces the <a href="http://en.wikipedia.org/wiki/Bell-LaPadula_model">Bell-LaPadula Mandatory Access Model</a>, and is used in Labeled Security Protection Profile (LSPP) environments. To use MLS restrictions, install the <span class="package">selinux-policy-mls</span> package, and configure MLS to be the default SELinux policy. The MLS policy shipped with Fedora omits many program domains that were not part of the evaluated configuration, and therefore, MLS on a desktop workstation is unusable (no support for the X Window System); however, an MLS policy from the <a href="http://oss.tresys.com/projects/refpolicy">upstream SELinux Reference Policy</a> can be built that includes all program domains.
-				</div></dd></dl></div><div class="section" title="3.1. Domain Transitions" id="sect-Security-Enhanced_Linux-SELinux_Contexts-Domain_Transitions"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">3.1. Domain Transitions</h2></div></div></div><div class="para">
-			A process in one domain transitions to another domain by executing an application that has the <code class="computeroutput">entrypoint</code> type for the new domain. The <code class="computeroutput">entrypoint</code> permission is used in SELinux policy, and controls which applications can be used to enter a domain. The following example demonstrates a domain transition:
+					MLS aplica el <a href="http://en.wikipedia.org/wiki/Bell-LaPadula_model">Modelo de Acceso Obligatorio Bell-LaPadula</a>, y se usa en entornos de Perfil de Protección de Seguirdad Etiquetada (LSPP en inglés). Para usar las restricciones MLS, instale el paquete <span class="package">selinux-policy-mls</span>, y configure a MLS como la política de SELinux predeterminada. La política MLS puesta en Fedora mite muchos dominios de programa que no eran parte de la configuración evaluada, y por lo tanto, MLS es inútil en un escritorio (no hay soporte para el Sistema de Ventanas X); sin embargo, una política MLS se puede incluir desde los <a href="http://oss.tresys.com/projects/refpolicy">desarrolladores de la Política de Referencia de SELinux</a> que incluya todos los dominios de programa.
+				</div></dd></dl></div><div class="section" title="3.1. Transiciones de Dominios" id="sect-Security-Enhanced_Linux-SELinux_Contexts-Domain_Transitions"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">3.1. Transiciones de Dominios</h2></div></div></div><div class="para">
+			Un proceso transiciona de un dominio a otro ejecutando una aplicación que tiene el tipo <code class="computeroutput">entrypoint</code> en el nuevo dominio. Los permisos <code class="computeroutput">entrypoint</code> se usan en las políticas de SELinux, y controlan qué aplicaciones pueden usarse para ingresar a un dominio. El siguiente ejemplo muestra una transición de dominio.
 		</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
-					A users wants to change their password. To change their password, they run the <code class="command">passwd</code> application. The <code class="filename">/usr/bin/passwd</code> executable is labeled with the <code class="computeroutput">passwd_exec_t</code> type:
+					Un usuario desea cambiar su contraseña. Para cambiar sus contraseñas, corren la aplicación <code class="command">passwd</code>. El ejecutable <code class="filename">/usr/bin/passwd</code> está etiquetado con el tipo <code class="computeroutput">passwd_exec_t</code>:
 				</div><pre class="screen">$ ls -Z /usr/bin/passwd
 -rwsr-xr-x  root root system_u:object_r:passwd_exec_t:s0 /usr/bin/passwd
 
 </pre><div class="para">
-					The <span class="application"><strong>passwd</strong></span> application accesses <code class="filename">/etc/shadow</code>, which is labeled with the <code class="computeroutput">shadow_t</code> type:
+					La aplicación <span class="application"><strong>passwd</strong></span> accede <code class="filename">/etc/shadow</code>, que está etiquetado con el tipo <code class="computeroutput">shadow_t</code>:
 				</div><pre class="screen">$ ls -Z /etc/shadow
 -r--------  root root system_u:object_r:shadow_t:s0    /etc/shadow
 
 </pre></li><li class="listitem"><div class="para">
-					An SELinux policy rule states that processes running in the <code class="computeroutput">passwd_t</code> domain are allowed to read and write to files labeled with the <code class="computeroutput">shadow_t</code> type. The <code class="computeroutput">shadow_t</code> type is only applied to files that are required for a password change. This includes <code class="filename">/etc/gshadow</code>, <code class="filename">/etc/shadow</code>, and their backup files.
+					Una regla de política de SELinux dice que los procesos que se ejecutan en el dominio <code class="computeroutput">passwd_t</code> no pueden leer y escribir archivos etiquetados con el tipo <code class="computeroutput">shadow_t</code>. El tipo <code class="computeroutput">shadow_t</code> sólo se aplica a archivos que necesitan un cambio de contraseñas. Esto incluye a <code class="filename">/etc/gshadow</code>, <code class="filename">/etc/shadow</code>, y sus archivos de respaldo.
 				</div></li><li class="listitem"><div class="para">
-					An SELinux policy rule states that the <code class="computeroutput">passwd_t</code> domain has <code class="computeroutput">entrypoint</code> permission to the <code class="computeroutput">passwd_exec_t</code> type.
+					Una regla de política de SELinux fija que el dominio <code class="computeroutput">passwd_t</code> tiene permiso de <code class="computeroutput">entrypoint</code> al tipo <code class="computeroutput">passwd_exec_t</code>.
 				</div></li><li class="listitem"><div class="para">
-					When a user runs the <code class="command">/usr/bin/passwd</code> application, the user's shell process transitions to the <code class="computeroutput">passwd_t</code> domain. With SELinux, since the default action is to deny, and a rule exists that allows (among other things) applications running in the <code class="computeroutput">passwd_t</code> domain to access files labeled with the <code class="computeroutput">shadow_t</code> type, the <span class="application"><strong>passwd</strong></span> application is allowed to access <code class="filename">/etc/shadow</code>, and update the user's password.
+					Cuando un usuario ejecuta la aplicación <code class="command">/usr/bin/passwd</code>, el proceso shell del usuario transiciona al dominio <code class="computeroutput">passwd_t</code>. Con SELinux, dado que la acción por defecto es negar, y existe una regla que permite (entre otras cosas) a aplicaciones que corran en el dominio <code class="computeroutput">passwd_t</code> acceder a archivos etiquetados con el tipo <code class="computeroutput">shadow_t</code>, se le permite a <span class="application"><strong>passwd</strong></span> acceder a <code class="filename">/etc/shadow</code>, y actualizar la contraseña del usuario.
 				</div></li></ol></div><div class="para">
-			This example is not exhaustive, and is used as a basic example to explain domain transition. Although there is an actual rule that allows subjects running in the <code class="computeroutput">passwd_t</code> domain to access objects labeled with the <code class="computeroutput">shadow_t</code> file type, other SELinux policy rules must be met before the subject can transition to a new domain. In this example, Type Enforcement ensures:
+			Este ejemplo no es exhaustivo, y se usa como un ejemplo básico para explicar la transición de dominio. Aunque hay una regla actual que permite a sujetos corriendo en el dominio <code class="computeroutput">passwd_t</code> accedan objetos etiquetados con el tipo de archivo <code class="computeroutput">shadow_t</code>, otras reglas de política de SELinux se deben cumplir para que el sujeto pueda transicionar a un nuevo dominio. En este ejemplo, la Obligación de Tipo asegura:
 		</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-					the <code class="computeroutput">passwd_t</code> domain can only be entered by executing an application labeled with the <code class="computeroutput">passwd_exec_t</code> type; can only execute from authorized shared libraries, such as the <code class="computeroutput">lib_t</code> type; and can not execute any other applications.
+					el dominio <code class="computeroutput">passwd_t</code> sólo se puede ingresar ejecutando una aplicación con la etiqueta del tipo <code class="computeroutput">passwd_exec_t</code>; sólo pueden ejecutar desde bibliotecas compartidas autorizadas, tales como las del tipo <code class="computeroutput">lib_t</code>; y no pueden ejecutar ninguna otra aplicación.
 				</div></li><li class="listitem"><div class="para">
-					only authorized domains, such as <code class="computeroutput">passwd_t</code>, can write to files labeled with the <code class="computeroutput">shadow_t</code> type. Even if other processes are running with superuser privileges, those processes can not write to files labeled with the <code class="computeroutput">shadow_t</code> type, as they are not running in the <code class="computeroutput">passwd_t</code> domain.
+					sólo los dominios autorizados, tales como <code class="computeroutput">passwd_t</code>, pueden escribir en archivos con la etiqueta del tipo <code class="computeroutput">shadow_t</code>. Aún si otros procesos corren con privilegios de superusuario, esos procesos no podrán escribir archivos etiquetados con el tipo <code class="computeroutput">shadow_t</code>, porque no están corriendo en el dominio <code class="computeroutput">passwd_t</code>.
 				</div></li><li class="listitem"><div class="para">
-					only authorized domains can transition to the <code class="computeroutput">passwd_t</code> domain. For example, the <code class="systemitem">sendmail</code> process running in the <code class="computeroutput">sendmail_t</code> domain does not have a legitimate reason to execute <code class="command">passwd</code>; therefore, it can never transition to the <code class="computeroutput">passwd_t</code> domain.
+					sólo los dominios autorizados pueden transicionar al dominio <code class="computeroutput">passwd_t</code>. Por ejemplo, el proceso <code class="systemitem">sendmail</code> corriendo en el dominio <code class="computeroutput">sendmail_t</code> no tiene una razón legítima para ejecutar <code class="command">passwd</code>; por lo tanto, no puede transicionar nunca al dominio <code class="computeroutput">passwd_t</code>.
 				</div></li><li class="listitem"><div class="para">
-					processes running in the <code class="computeroutput">passwd_t</code> domain can only read and write to authorized types, such as files labeled with the <code class="computeroutput">etc_t</code> or <code class="computeroutput">shadow_t</code> types. This prevents the <span class="application"><strong>passwd</strong></span> application from being tricked into reading or writing arbitrary files.
-				</div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Introduction-SELinux_on_Other_Operating_Systems.html"><strong>Anterior</strong>2.4. SELinux on Other Operating Systems</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Processes.html"><strong>Siguiente</strong>3.2. SELinux Contexts for Processes</a></li></ul></body></html>
+					los procesos que se ejecutan en el dominio <code class="computeroutput">passwd_t</code> sólo pueden leer y escribir a tipos autorizados, tales como archivos etiquetados con los tipos <code class="computeroutput">etc_t</code> o <code class="computeroutput">shadow_t</code>. Esto impide a la aplicación <span class="application"><strong>passwd</strong></span> de ser modificada para leer o escribir en archivos arbitrarios.
+				</div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Introduction-SELinux_on_Other_Operating_Systems.html"><strong>Anterior</strong>2.4. SELinux en otros Sistemas Operativos</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Processes.html"><strong>Siguiente</strong>3.2. Contextos de SELinux para los Procesos</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Targeted_Policy.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Targeted_Policy.html
index 241ba26..04894b5 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Targeted_Policy.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Targeted_Policy.html
@@ -1,15 +1,15 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Capítulo 4. Targeted Policy</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="index.html" title="Security-Enhanced Linux" /><link rel="prev" href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Users.html" title="3.3. SELinux Contexts for Users" /><link rel="next" href="sect-Security-Enhanced_Linux-Targeted_Policy-Unconfined_Processes.html" title="4.2. Unconfined Processes" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.h
 tml">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Users.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Targeted_Policy-Unconfined_Processes.html"><strong>Siguiente</strong></a></li></ul><div xml:lang="es-ES" class="chapter" title="Capítulo 4. Targeted Policy" id="chap-Security-Enhanced_Linux-Targeted_Policy" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 4. Targeted Policy</h2></div></div></div><div class="toc"><dl><dt><span class="section"><
 a href="chap-Security-Enhanced_Linux-Targeted_Policy.html#sect-Security-Enhanced_Linux-Targeted_Policy-Confined_Processes">4.1. Confined Processes</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Targeted_Policy-Unconfined_Processes.html">4.2. Unconfined Processes</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users.html">4.3. Confined and Unconfined Users</a></span></dt></dl></div><div class="para">
-		Targeted policy is the default SELinux policy used in Fedora 11. When using targeted policy, processes that are targeted run in a confined domain, and processes that are not targeted run in an unconfined domain. For example, by default, logged in users run in the <code class="computeroutput">unconfined_t</code> domain, and system processes started by init run in the <code class="computeroutput">initrc_t</code> domain - both of these domains are unconfined.
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Capítulo 4. Política Destinado</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="prev" href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Users.html" title="3.3. Contextos de SELinux para los Usuarios" /><link rel="next" href="sect-Security-Enhanced_Linux-Targeted_Policy-Unconfined_Processes.html" title="4.2. Procesos no Confinados" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class=
 "toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Users.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Targeted_Policy-Unconfined_Processes.html"><strong>Siguiente</strong></a></li></ul><div xml:lang="es-ES" class="chapter" title="Capítulo 4. Política Destinado" id="chap-Security-Enhanced_Linux-Targeted_Policy" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 4. Política Destinado</h2></div></div></div><div class="
 toc"><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-Targeted_Policy.html#sect-Security-Enhanced_Linux-Targeted_Policy-Confined_Processes">4.1. Procesos Confinados</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Targeted_Policy-Unconfined_Processes.html">4.2. Procesos no Confinados</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users.html">4.3. Usuarios Confinados y no Confinados</a></span></dt></dl></div><div class="para">
+		La política destinada es la política predeterminada de SELinux usada en Fedora 11. Cuando la política destinada está en uso, los procesos son destinados a correr en dominios confinados, y los procesos que no son destinados a correr en un dominio corren en un dominio no confinado. Por ejemplo, por defecto, los usuarios que ingresaron corren en el dominio <code class="computeroutput">unconfined_t</code>, y los procesos del sistema iniciado por init corren en el dominio <code class="computeroutput">initrc_t</code> - ambos dominios están no confinados.
 	</div><div class="para">
 		Unconfined domains (as well as confined domains) are subject to executable and writeable memory checks. By default, subjects running in an unconfined domain can not allocate writeable memory and execute it. This reduces vulnerability to <a href="http://en.wikipedia.org/wiki/Buffer_overflow">buffer overflow attacks</a>. These memory checks are disabled by setting Booleans, which allow the SELinux policy to be modified at runtime. Boolean configuration is discussed later.
-	</div><div class="section" title="4.1. Confined Processes" id="sect-Security-Enhanced_Linux-Targeted_Policy-Confined_Processes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.1. Confined Processes</h2></div></div></div><div class="para">
-			Almost every service that listens on a network is confined in Fedora 11. Also, most processes that run as the Linux root user and perform tasks for users, such as the <span class="application"><strong>passwd</strong></span> application, are confined. When a process is confined, it runs in its own domain, such as the <code class="systemitem">httpd</code> process running in the <code class="computeroutput">httpd_t</code> domain. If a confined process is compromised by an attacker, depending on SELinux policy configuration, an attacker's access to resources and the possible damage they can do is limited.
+	</div><div class="section" title="4.1. Procesos Confinados" id="sect-Security-Enhanced_Linux-Targeted_Policy-Confined_Processes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.1. Procesos Confinados</h2></div></div></div><div class="para">
+			Casi todos los servicios que escuchan en la red se confinan en Fedora 11. También, la mayoría de los procesos que corren como usuario root de Linux y realizan tareas para los usuarios, tales como la aplicación <span class="application"><strong>passwd</strong></span>, están confinadas. Cuando un proceso se confina, corre en su propio dominio, tal como el proceso <code class="systemitem">httpd</code> ejecutándose en el domino <code class="computeroutput">httpd_t</code>. Si un proceso confinado es comprometido por un atacante, dependiendo de la configuración de política de SELinux, el acceso del atacante a recursos y el posible daño que puedan causar es limitado.
 		</div><div class="para">
-			The following example demonstrates how SELinux prevents the Apache HTTP Server (<code class="systemitem">httpd</code>) from reading files that are not correctly labeled, such as files intended for use by Samba. This is an example, and should not be used in production. It assumes that the <span class="package">httpd</span>, <span class="package">wget</span>, <span class="package">setroubleshoot-server</span>, and <span class="package">audit</span> packages are installed, that the SELinux targeted policy is used, and that SELinux is running in enforcing mode:
+			El siguiente ejemplo muestra cómo previene SELinux la lectura por parte del Servidor HTTP Apache (<code class="systemitem">httpd</code>) de archivos que no se etiquetaron correctamente, tales como archivos a usar con Samba. Este es un ejemplo, y no se debe usar en producción. Asume que los paquetes <span class="package">httpd</span>, <span class="package">wget</span>, <span class="package">setroubleshoot-server</span> y <span class="package">audit</span> están instalados, que se usa la política destinada de SELinux y que SELinux está corriendo en modo obligatorio:
 		</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
-					Run the <code class="command">sestatus</code> command to confirm that SELinux is enabled, is running in enforcing mode, and that targeted policy is being used:
+					Ejecute el comando <code class="command">sestatus</code> para confirmar que SELinux está activado, se ejecuta en modo obligatorio y que la política destinada se está usando:
 				</div><pre class="screen">
 $ /usr/sbin/sestatus
 SELinux status:                 enabled
@@ -22,20 +22,20 @@ Policy from config file:        targeted
 </pre><div class="para">
 					<code class="computeroutput">SELinux status: enabled</code> is returned when SELinux is enabled. <code class="computeroutput">Current mode: enforcing</code> is returned when SELinux is running in enforcing mode. <code class="computeroutput">Policy from config file: targeted</code> is returned when the SELinux targeted policy is used.
 				</div></li><li class="listitem"><div class="para">
-					As the Linux root user, run the <code class="command">touch /var/www/html/testfile</code> command to create a file.
+					Como usuario root de Linux, ejecute el comando <code class="command">touch /var/www/html/prueba</code> para crear un archivo.
 				</div></li><li class="listitem"><div class="para">
-					Run the <code class="command">ls -Z /var/www/html/testfile</code> command to view the SELinux context:
+					Ejecute el comando <code class="command">ls -Z /var/www/html/prueba</code> para ver el contexto SELinux:
 				</div><pre class="screen">-rw-r--r--  root root unconfined_u:object_r:httpd_sys_content_t:s0 /var/www/html/testfile
 
 </pre><div class="para">
-					By default, Linux users run unconfined in Fedora 11, which is why the <code class="filename">testfile</code> file is labeled with the SELinux <code class="computeroutput">unconfined_u</code> user. RBAC is used for processes, not files. Roles do not have a meaning for files - the <code class="computeroutput">object_r</code> role is a generic role used for files (on persistent storage and network file systems). Under the <code class="filename">/proc/</code> directory, files related to processes may use the <code class="computeroutput">system_r</code> role.<sup>[<a id="id554585" href="#ftn.id554585" class="footnote">6</a>]</sup> The <code class="computeroutput">httpd_sys_content_t</code> type allows the <code class="systemitem">httpd</code> process to access this file.
+					Por defecto, los usuarios Linux corren no confinados en Fedora 11, razón por la cual el archivo <code class="filename">prueba</code> se etiqueta con el usuario SELinux <code class="computeroutput">unconfined_u</code>. RBAC se usa para procesos, y no para archivos. Los roles no tienen significado para archivos - el rol <code class="computeroutput">object_r</code> es un rol genérico usado para archivos (en sistemas de archivos persistentes y de red). Bajo el directorio <code class="filename">/proc/</code>, los archivos relacionados con procesos pueden usar el rol <code class="computeroutput">system_r</code>.<sup>[<a id="id1079428" href="#ftn.id1079428" class="footnote">6</a>]</sup> El tipo <code class="computeroutput">httpd_sys_content_t</code> permite al proceso <code class="systemitem">httpd</code> acceder a este archivo.
 				</div></li><li class="listitem"><div class="para">
-					As the Linux root user, run the <code class="command">service httpd start</code> command to start the <code class="systemitem">httpd</code> process. The output is as follows if <code class="systemitem">httpd</code> starts successfully:
+					Como usuario root de Linux, ejecute el comando <code class="command">service httpd start</code> para iniciar el proceso <code class="systemitem">httpd</code>. La salida escomo sigue si <code class="systemitem">httpd</code> inicia con éxito:
 				</div><pre class="screen"># /sbin/service httpd start
 Starting httpd:                                            [  OK  ]
 
 </pre></li><li class="listitem"><div class="para">
-					Change into a directory where your Linux user has write access to, and run the <code class="command">wget http://localhost/testfile</code> command. Unless there are changes to the default configuration, this command succeeds:
+					Cambie al directorio donde su usuario Linux tenga acceso de escritura y ejecute el comando <code class="command">wget http://localhost/prueba</code>. A menos que hubieran cambios en la configuración predeterminada, este comando tiene éxito:
 				</div><pre class="screen">--2009-05-06 23:00:01--  http://localhost/testfile
 Resolving localhost... 127.0.0.1
 Connecting to localhost|127.0.0.1|:80... connected.
@@ -48,15 +48,15 @@ Saving to: `testfile'
 2009-05-06 23:00:01 (0.00 B/s) - `testfile' saved [0/0]
 
 </pre></li><li class="listitem"><div class="para">
-					The <code class="command">chcon</code> command relabels files; however, such label changes do not survive when the file system is relabeled. For permanent changes that survive a file system relabel, use the <code class="command">semanage</code> command, which is discussed later. As the Linux root user, run the following command to change the type to a type used by Samba:
+					El comando <code class="command">chcon</code> reetiqueta archivos; sin embargo, tales cambios de etiquetas no sobreviven cuando el sistema se reetiqueta. Para que los cambios sobrevivan un reetiquetado del sistema, use el comando <code class="command">semanage</code>, que se discute más adelante. Como usuario root de Linux, corra el siguiente comando para cambiar el tipo a un tipo usado por Samba:
 				</div><div class="para">
 					<code class="command">chcon -t samba_share_t /var/www/html/testfile</code>
 				</div><div class="para">
-					Run the <code class="command">ls -Z /var/www/html/testfile</code> command to view the changes:
+					Ejecute el comando <code class="command">ls -Z /var/www/html/prueba</code> para ver los cambios:
 				</div><pre class="screen">-rw-r--r--  root root unconfined_u:object_r:samba_share_t:s0 /var/www/html/testfile
 
 </pre></li><li class="listitem"><div class="para">
-					Note: the current DAC permissions allow the <code class="systemitem">httpd</code> process access to <code class="filename">testfile</code>. Change into a directory where your Linux user has write access to, and run the <code class="command">wget http://localhost/testfile</code> command. Unless there are changes to the default configuration, this command fails:
+					Nota: los permisos de DAC actuales permiten al proceso <code class="systemitem">httpd</code> acceder al <code class="filename">prueba</code>. Cambie al directorio donde el usuario Linux tenga permiso de escritura y ejecute el comando <code class="command">wget http://localhost/prueba</code>. A menos que hayan cambios en la configuración predeterminada, este comando fallará:
 				</div><pre class="screen">--2009-05-06 23:00:54--  http://localhost/testfile
 Resolving localhost... 127.0.0.1
 Connecting to localhost|127.0.0.1|:80... connected.
@@ -64,30 +64,30 @@ HTTP request sent, awaiting response... 403 Forbidden
 2009-05-06 23:00:54 ERROR 403: Forbidden.
 
 </pre></li><li class="listitem"><div class="para">
-					As the Linux root user, run the <code class="command">rm -i /var/www/html/testfile</code> command to remove <code class="filename">testfile</code>.
+					Como usuario root de Linux, corra el comando <code class="command">rm -i /var/www/html/prueba</code> para borrar <code class="filename">prueba</code>.
 				</div></li><li class="listitem"><div class="para">
-					If you do not require <code class="systemitem">httpd</code> to be running, as the Linux root user, run the <code class="command">service httpd stop</code> command to stop <code class="systemitem">httpd</code>:
+					Si no necesita que corra <code class="systemitem">httpd</code>, como usuario root de Linux corra el comando <code class="command">service httpd stop</code> para detener a <code class="systemitem">httpd</code>:
 				</div><pre class="screen"># /sbin/service httpd stop
 Stopping httpd:                                            [  OK  ]
 
 </pre></li></ol></div><div class="para">
-			This example demonstrates the additional security added by SELinux. Although DAC rules allowed the <code class="systemitem">httpd</code> process access to <code class="filename">testfile</code> in step 7, because the file was labeled with a type that the <code class="systemitem">httpd</code> process does not have access to, SELinux denied access. After step 7, an error similar to the following is logged to <code class="filename">/var/log/messages</code>:
+			Este ejemplo muestra la seguridad adicional agregada por SELinux. Aunque las reglas de DAC permitieron al proceso <code class="systemitem">httpd</code> acceder a <code class="filename">prueba</code> en el paso 7, dado que estaba etiquetado con un tipo al que el proceso <code class="systemitem">httpd</code> no tenía acceso, SELinux negó el acceso. Después del paso 7, un error similar al siguiente se guarda en <code class="filename">/var/log/messages</code>:
 		</div><pre class="screen">May 6 23:00:54 localhost setroubleshoot: SELinux is preventing httpd (httpd_t) "getattr"
 to /var/www/html/testfile (samba_share_t). For complete SELinux messages.
 run sealert -l c05911d3-e680-4e42-8e36-fe2ab9f8e654
 
 </pre><div class="para">
-			Previous log files may use a <code class="filename">/var/log/messages.<em class="replaceable"><code>YYYYMMDD</code></em></code> format. When running <span class="application"><strong>syslog-ng</strong></span>, previous log files may use a <code class="filename">/var/log/messages.<em class="replaceable"><code>X</code></em></code> format. If the <code class="systemitem">setroubleshootd</code> and <code class="systemitem">auditd</code> processes are running, errors similar to the following are logged to <code class="filename">/var/log/audit/audit.log</code>:
+			Archivos log previos pueden usar el formato <code class="filename">/var/log/messages.<em class="replaceable"><code>YYYYMMDD</code></em></code>. Cuando se ejecuta <span class="application"><strong>syslog-ng</strong></span>, los archivos log previos pueden usar el formato <code class="filename">/var/log/messages.<em class="replaceable"><code>X</code></em></code>. Si los procesos <code class="systemitem">setroubleshootd</code> y <code class="systemitem">auditd</code> están ejecutándose, errores similares a los siguientes se registran en <code class="filename">/var/log/audit/audit.log</code>:
 		</div><pre class="screen">type=AVC msg=audit(1220706212.937:70): avc:  denied  { getattr } for  pid=1904 comm="httpd" path="/var/www/html/testfile" dev=sda5 ino=247576 scontext=unconfined_u:system_r:httpd_t:s0 tcontext=unconfined_u:object_r:samba_share_t:s0  tclass=file
 
 type=SYSCALL msg=audit(1220706212.937:70): arch=40000003 syscall=196 success=no exit=-13 a0=b9e21da0 a1=bf9581dc a2=555ff4 a3=2008171 items=0 ppid=1902 pid=1904 auid=500 uid=48 gid=48 euid=48 suid=48 fsuid=48 egid=48 sgid=48 fsgid=48 tty=(none) ses=1 comm="httpd" exe="/usr/sbin/httpd" subj=unconfined_u:system_r:httpd_t:s0 key=(null)
 
 </pre><div class="para">
-			Also, an error similar to the following is logged to <code class="filename">/var/log/httpd/error_log</code>:
+			También, un error similar al siguiente se registra en <code class="filename">/var/log/httpd/error_log</code>:
 		</div><pre class="screen">[Wed May 06 23:00:54 2009] [error] [client <em class="replaceable"><code>127.0.0.1</code></em>] (13)Permission denied: access to /testfile denied
 
 </pre><div class="note"><h2>Nota</h2><div class="para">
-				In Fedora 11, the <span class="package">setroubleshoot-server</span> and <span class="package">audit</span> packages are installed by default. These packages include the <code class="systemitem">setroubleshootd</code> and <code class="systemitem">auditd</code> daemons respectively. These daemons run by default. Stopping either of these daemons changes where SELinux denials are written to. Refer to <a class="xref" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used.html" title="5.2. Which Log File is Used">Sección 5.2, “Which Log File is Used”</a> for further information.
-			</div></div></div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id554585" href="#id554585" class="para">6</a>] </sup>
-						When using other policies, such as MLS, other roles may be used, for example, <code class="computeroutput">secadm_r</code>.
-					</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Users.html"><strong>Anterior</strong>3.3. SELinux Contexts for Users</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Targeted_Policy-Unconfined_Processes.html"><strong>Siguiente</strong>4.2. Unconfined Processes</a></li></ul></body></html>
+				In Fedora 11, the <span class="package">setroubleshoot-server</span> and <span class="package">audit</span> packages are installed by default. These packages include the <code class="systemitem">setroubleshootd</code> and <code class="systemitem">auditd</code> daemons respectively. These daemons run by default. Stopping either of these daemons changes where SELinux denials are written to. Refer to <a class="xref" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used.html" title="5.2. Qué Archivo Log se usa">Sección 5.2, “Qué Archivo Log se usa”</a> for further information.
+			</div></div></div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id1079428" href="#id1079428" class="para">6</a>] </sup>
+						cuando se usan otras políticas, tal como MLS, se pueden usar otros roles, por ejemplo <code class="computeroutput">secadm_r</code>.
+					</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Users.html"><strong>Anterior</strong>3.3. Contextos de SELinux para los Usuarios</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Targeted_Policy-Unconfined_Processes.html"><strong>Siguiente</strong>4.2. Procesos no Confinados</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Trademark_Information.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Trademark_Information.html
index 8691e74..7875cfa 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Trademark_Information.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Trademark_Information.html
@@ -1,15 +1,15 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Capítulo 1. Trademark Information</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="index.html" title="Security-Enhanced Linux" /><link rel="prev" href="pr01s02.html" title="2. ¡Necesitamos sus comentarios!" /><link rel="next" href="chap-Security-Enhanced_Linux-Introduction.html" title="Capítulo 2. Introduction" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.
 </iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="pr01s02.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-Introduction.html"><strong>Siguiente</strong></a></li></ul><div xml:lang="es-ES" class="chapter" title="Capítulo 1. Trademark Information" id="chap-Security-Enhanced_Linux-Trademark_Information" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 1. Trademark Information</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-Trademark_Information.html#chap-Security-Enhanced_Linux-Trademark_Information-Source_Code">1.1. Source Code</a></sp
 an></dt></dl></div><div class="para">
-		<span class="trademark">Linux</span>® is the registered trademark of Linus Torvalds in the U.S. and other countries.
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Capítulo 1. Información de Marca Comercial</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="prev" href="pr01s02.html" title="2. ¡Necesitamos sus comentarios!" /><link rel="next" href="chap-Security-Enhanced_Linux-Introduction.html" title="Capítulo 2. Introducción" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or e
 nable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="pr01s02.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-Introduction.html"><strong>Siguiente</strong></a></li></ul><div xml:lang="es-ES" class="chapter" title="Capítulo 1. Información de Marca Comercial" id="chap-Security-Enhanced_Linux-Trademark_Information" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 1. Información de Marca Comercial</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-Trademark_Information.html#chap-Security-Enhanced_Linux-Trademark_Informat
 ion-Source_Code">1.1. Source Code</a></span></dt></dl></div><div class="para">
+		<span class="trademark">Linux</span>® es una marca comercial registrada de Linus Torvalds en los EEUU y en otros países.
 	</div><div class="para">
-		UNIX is a registered trademark of The Open Group.
+		UNIX es una marca comercial registrada de El Grupo Abierto.
 	</div><div class="para">
-		Type Enforcement is a trademark of Secure Computing, LLC, a wholly owned subsidiary of McAfee, Inc., registered in the U.S. and in other countries. Neither McAfee nor Secure Computing, LLC, has consented to the use or reference to this trademark by the author outside of this guide.
+		Type Enforcement (Obligación de Tipos) es una marca comercial de Secure Computing, LLC, una subsidiaria de McAfee, Inc., registrada en los EEUU y en otros países. Ni McAfee ni Secure Computing, LLC, ha consentido el uso o referencia de esta marca comercial para el autor fuera de esta guía.
 	</div><div class="para">
-		Apache is a trademark of The Apache Software Foundation.
+		Apache es una marca comercial de La Fundación de Software Apache.
 	</div><div class="para">
-		MySQL is a trademark or registered trademark of MySQL AB in the U.S. and other countries.
+		MySQL es una marca comercial o marca comercial registrada de MySQL AB en los EEUU y en otros países.
 	</div><div class="section" title="1.1. Source Code" id="chap-Security-Enhanced_Linux-Trademark_Information-Source_Code"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">1.1. Source Code</h2></div></div></div><div class="para">
 			The XML source for this guide is available at <a href="http://svn.fedorahosted.org/svn/selinuxguide/">http://svn.fedorahosted.org/svn/selinuxguide/</a>
-		</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="pr01s02.html"><strong>Anterior</strong>2. ¡Necesitamos sus comentarios!</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-Introduction.html"><strong>Siguiente</strong>Capítulo 2. Introduction</a></li></ul></body></html>
+		</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="pr01s02.html"><strong>Anterior</strong>2. ¡Necesitamos sus comentarios!</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-Introduction.html"><strong>Siguiente</strong>Capítulo 2. Introducción</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Troubleshooting.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Troubleshooting.html
index fdf3d3a..1109d65 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Troubleshooting.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Troubleshooting.html
@@ -1,13 +1,13 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Capítulo 7. Troubleshooting</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="index.html" title="Security-Enhanced Linux" /><link rel="prev" href="sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications.html" title="6.6. Booleans for Users Executing Applications" /><link rel="next" href="sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html" title="7.2. Top Three Causes of Problems" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id=
 "tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html"><strong>Siguiente</strong></a></li></ul><div xml:lang="es-ES" class="chapter" title="Capítulo 7. Troubleshooting" id="chap-Security-Enhanced_Linux-Troubleshooting" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 7. Troubleshooting</h2
 ></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-Troubleshooting.html#sect-Security-Enhanced_Linux-Troubleshooting-What_Happens_when_Access_is_Denied">7.1. What Happens when Access is Denied</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html">7.2. Top Three Causes of Problems</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html#sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Labeling_Problems">7.2.1. Labeling Problems</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running.html">7.2.2. How are Confined Services Running?</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Evolving_Rules_and_Broken_Applications.htm
 l">7.2.3. Evolving Rules and Broken Applications</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html">7.3. Fixing Problems</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html#sect-Security-Enhanced_Linux-Fixing_Problems-Linux_Permissions">7.3.1. Linux Permissions</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-Possible_Causes_of_Silent_Denials.html">7.3.2. Possible Causes of Silent Denials</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services.html">7.3.3. Manual Pages for Services</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains.html">7.3.4. Permissive Domains</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-Se
 arching_For_and_Viewing_Denials.html">7.3.5. Searching For and Viewing Denials</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages.html">7.3.6. Raw Audit Messages</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages.html">7.3.7. sealert Messages</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow.html">7.3.8. Allowing Access: audit2allow</a></span></dt></dl></dd></dl></div><div class="para">
-		The following chapter describes what happens when SELinux denies access; the top three causes of problems; where to find information about correct labeling; analyzing SELinux denials; and creating custom policy modules with <code class="command">audit2allow</code>.
-	</div><div class="section" title="7.1. What Happens when Access is Denied" id="sect-Security-Enhanced_Linux-Troubleshooting-What_Happens_when_Access_is_Denied"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">7.1. What Happens when Access is Denied</h2></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Capítulo 7. Solución a Problemas</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="prev" href="sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications.html" title="6.6. Booleanos para que los Usuarios Ejecuten Aplicaciones" /><link rel="next" href="sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html" title="7.2. Tres Principales Causas de Problemas" /></head><body class="toc_embeded "><div
  id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html"><strong>Siguiente</strong></a></li></ul><div xml:lang="es-ES" class="chapter" title="Capítulo 7. Solución a Problemas" id="chap-Security-Enhanced_Linux-Troubleshooting" lang="es-ES"><div class="titlepage"><div><div><h2 clas
 s="title">Capítulo 7. Solución a Problemas</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-Troubleshooting.html#sect-Security-Enhanced_Linux-Troubleshooting-What_Happens_when_Access_is_Denied">7.1. Qué pasa cuando el Acceso es Denegado</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html">7.2. Tres Principales Causas de Problemas</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html#sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Labeling_Problems">7.2.1. Problemas de Etiquetados</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running.html">7.2.2. ¿Cómo se Ejecutan los Servicios Confinados?</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced
 _Linux-Top_Three_Causes_of_Problems-Evolving_Rules_and_Broken_Applications.html">7.2.3. Evolucionando las Reglas y las Aplicaciones Rotas</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html">7.3. Corrección de Problemas</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html#sect-Security-Enhanced_Linux-Fixing_Problems-Linux_Permissions">7.3.1. Permisos de Linux</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-Possible_Causes_of_Silent_Denials.html">7.3.2. Posibles Causas de las Negaciones Silenciosas</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services.html">7.3.3. Páginas de Manual para Servicios</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains.html">7.3.4
 . Dominios Permisivos</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-Searching_For_and_Viewing_Denials.html">7.3.5. Búsqueda y Revisión de Negaciones</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages.html">7.3.6. Raw Audit Messages</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages.html">7.3.7. Mensajes sealert</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow.html">7.3.8. Permitiendo el Acceso: audit2allow</a></span></dt></dl></dd></dl></div><div class="para">
+		El siguiente capítulo describe qué pasa cuando SELinux niega el acceso; las principales tres causas de problemas; dónde encontrar información acerca del correcto etiquetado; análisis de las negaciones de SELinux; y creación de módulos de políticas personalizados con <code class="command">audit2allow</code>.
+	</div><div class="section" title="7.1. Qué pasa cuando el Acceso es Denegado" id="sect-Security-Enhanced_Linux-Troubleshooting-What_Happens_when_Access_is_Denied"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">7.1. Qué pasa cuando el Acceso es Denegado</h2></div></div></div><div class="para">
 			SELinux decisions, such as allowing or disallowing access, are cached. This cache is known as the Access Vector Cache (AVC). Denial messages are logged when SELinux denies access. These denials are also known as "AVC denials", and are logged to a different location, depending on which daemons are running:
 		</div><div class="segmentedlist"><table border="0"><thead><tr class="segtitle"><th>Daemon</th><th>Log Location</th></tr></thead><tbody><tr class="seglistitem"><td class="seg">auditd on</td><td class="seg"><code class="filename">/var/log/audit/audit.log</code></td></tr><tr class="seglistitem"><td class="seg">auditd off; rsyslogd on</td><td class="seg"><code class="filename">/var/log/messages</code></td></tr><tr class="seglistitem"><td class="seg">setroubleshootd, rsyslogd, and auditd on</td><td class="seg"><code class="filename">/var/log/audit/audit.log</code>. Easier-to-read denial messages also sent to <code class="filename">/var/log/messages</code></td></tr></tbody></table></div><div class="para">
-			If you are running the X Window System, have the <span class="package">setroubleshoot</span> and <span class="package">setroubleshoot-server</span> packages installed, and the <code class="systemitem">setroubleshootd</code> and <code class="systemitem">auditd</code> daemons are running, a yellow star and a warning are displayed when access is denied by SELinux:
+			Si está corriendo el Sistema de Ventanas X, ya tienen los paquetes <span class="package">setroubleshoot</span> y <span class="package">setroubleshoot-server</span> instalados, y los demonios <code class="systemitem">setroubleshootd</code> y <code class="systemitem">auditd</code> están ejecutándose, se muestra una estrella amarilla y una advertencia cuando SELinux deniega el acceso:
 		</div><div class="mediaobject"><img src="./images/setroubleshoot_denial.png" /></div><div class="para">
-			Clicking on the star presents a detailed analysis of why SELinux denied access, and a possible solution for allowing access. If you are not running the X Window System, it is less obvious when access is denied by SELinux. For example, users browsing your website may receive an error similar to the following:
+			Haciendo clic en las estrelas se presenta un análisis detallado de por qué SELinux negó el acceso, y una posible solución para permitir el acceso. Si no está corriendo el Sistema de Ventanas X, es menos obvio cuando un acceso es negado por SELinux. Por ejemplo, los usuarios navegando su sitio web pueden recibir un error similar al siguiente:
 		</div><pre class="screen">
 Forbidden
 
@@ -19,4 +19,4 @@ You don't have permission to access <em class="replaceable"><code>file name</cod
 			<code class="command">grep "SELinux is preventing" /var/log/messages</code>
 		</div><div class="para">
 			<code class="command">grep "denied" /var/log/audit/audit.log</code>
-		</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications.html"><strong>Anterior</strong>6.6. Booleans for Users Executing Applications</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html"><strong>Siguiente</strong>7.2. Top Three Causes of Problems</a></li></ul></body></html>
+		</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications.html"><strong>Anterior</strong>6.6. Booleanos para que los Usuarios Ejecuten Apl...</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html"><strong>Siguiente</strong>7.2. Tres Principales Causas de Problemas</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Working_with_SELinux.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Working_with_SELinux.html
index 534b1bf..118f795 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Working_with_SELinux.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Working_with_SELinux.html
@@ -1,33 +1,33 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Capítulo 5. Working with SELinux</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="index.html" title="Security-Enhanced Linux" /><link rel="prev" href="sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users.html" title="4.3. Confined and Unconfined Users" /><link rel="next" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used.html" title="5.2. Which Log File is Used" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src
 ="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used.html"><strong>Siguiente</strong></a></li></ul><div xml:lang="es-ES" class="chapter" title="Capítulo 5. Working with SELinux" id="chap-Security-Enhanced_Linux-Working_with_SELinux" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 5. Working with SELinux</h2></div></div></div><div 
 class="toc"><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-Working_with_SELinux.html#sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Packages">5.1. SELinux Packages</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used.html">5.2. Which Log File is Used</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Main_Configuration_File.html">5.3. Main Configuration File</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html">5.4. Enabling and Disabling SELinux</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html#sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Enabling_SELinux">5.4.1. Enabling SELinux</a></span></dt><dt><span class="section"><a href="sect-Sec
 urity-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux.html">5.4.2. Disabling SELinux</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes.html">5.5. SELinux Modes</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html">5.6. Booleans</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html#sect-Security-Enhanced_Linux-Booleans-Listing_Booleans">5.6.1. Listing Booleans</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Booleans-Configuring_Booleans.html">5.6.2. Configuring Booleans</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS.html">5.6.3. Booleans for NFS and CIFS</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-SE
 Linux_Contexts_Labeling_Files.html">5.7. SELinux Contexts - Labeling Files</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files.html#sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Temporary_Changes_chcon">5.7.1. Temporary Changes: chcon</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext.html">5.7.2. Persistent Changes: semanage fcontext</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types.html">5.8. The file_t and default_t Types</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html">5.9. Mounting File Systems</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounti
 ng_File_Systems.html#sect-Security-Enhanced_Linux-Mounting_File_Systems-Context_Mounts">5.9.1. Context Mounts</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Changing_the_Default_Context.html">5.9.2. Changing the Default Context</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Mounting_an_NFS_File_System.html">5.9.3. Mounting an NFS File System</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Multiple_NFS_Mounts.html">5.9.4. Multiple NFS Mounts</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Making_Context_Mounts_Persistent.html">5.9.5. Making Context Mounts Persistent</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html">5.10. Maintaining SELinux Labels </a></span></dt><dd><dl><d
 t><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html#sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Copying_Files_and_Directories">5.10.1. Copying Files and Directories</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Moving_Files_and_Directories.html">5.10.2. Moving Files and Directories</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context.html">5.10.3. Checking the Default SELinux Context</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_tar.html">5.10.4. Archiving Files with tar</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_star.html">5.10.5. Archiving Files with star</a></span></dt></dl></dd></dl
 ></div><div class="para">
-		The following sections give a brief overview of the main SELinux packages in Fedora 11; installing and updating packages; which log files are used; the main SELinux configuration file; enabling and disabling SELinux; SELinux modes; configuring Booleans; temporarily and persistently changing file and directory labels; overriding file system labels with the <code class="command">mount</code> command; mounting NFS file systems; and how to preserve SELinux contexts when copying and archiving files and directories.
-	</div><div class="section" title="5.1. SELinux Packages" id="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Packages"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.1. SELinux Packages</h2></div></div></div><div class="para">
-			In Fedora 11, the SELinux packages are installed by default, unless they are manually excluded during installation. By default, SELinux targeted policy is used, and SELinux runs in enforcing mode. The following is a brief description of the main SELinux packages:
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Capítulo 5. Trabajando con SELinux</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="prev" href="sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users.html" title="4.3. Usuarios Confinados y no Confinados" /><link rel="next" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used.html" title="5.2. Qué Archivo Log se usa" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocfra
 me" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used.html"><strong>Siguiente</strong></a></li></ul><div xml:lang="es-ES" class="chapter" title="Capítulo 5. Trabajando con SELinux" id="chap-Security-Enhanced_Linux-Working_with_SELinux" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 5. Trabajando con SELinux</h2>
 </div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-Working_with_SELinux.html#sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Packages">5.1. Paquetes de SELinux</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used.html">5.2. Qué Archivo Log se usa</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Main_Configuration_File.html">5.3. Archivo de Configuración Principal</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html">5.4. Habilitando y Deshabilitando SELinux</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html#sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Enabling_SELinux">5.4.1. Habilitando SELinux</a></span>
 </dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux.html">5.4.2. Deshabilitando SELinux</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes.html">5.5. Modos de SELinux</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html">5.6. Booleanos</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html#sect-Security-Enhanced_Linux-Booleans-Listing_Booleans">5.6.1. Listando los Booleanos</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Booleans-Configuring_Booleans.html">5.6.2. Configurando los Booleanos</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS.html">5.6.3. Booleanos para NFS y CIFS</a></span></dt></dl></dd><dt><span class="s
 ection"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files.html">5.7. Contextos de SELinux - Etiquetado de Archivos</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files.html#sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Temporary_Changes_chcon">5.7.1. Cambios Temporales: chcon</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext.html">5.7.2. Cambios Persistentes: semanage fcontext</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types.html">5.8. Los tipos file_t y default_t</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html">5.9. Montaje de Sistemas de Archivos</a></span></dt><dd><dl
 ><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html#sect-Security-Enhanced_Linux-Mounting_File_Systems-Context_Mounts">5.9.1. Montajes de Contexto</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Changing_the_Default_Context.html">5.9.2. Cambio del Contexto Predeterminado</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Mounting_an_NFS_File_System.html">5.9.3. Montando un Sistema de Archivos NFS</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Multiple_NFS_Mounts.html">5.9.4. Montajes NFS Múltiples</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Making_Context_Mounts_Persistent.html">5.9.5. Haciendo Persistente los Contextos de Montajes</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Security
 -Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html">5.10. Mantención de las Etiquetas de SELinux</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html#sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Copying_Files_and_Directories">5.10.1. Copia de Directorios y Archivos</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Moving_Files_and_Directories.html">5.10.2. Movimiento de Archivos y Directorios</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context.html">5.10.3. Chequeando el Contexto SELinux Predeterminado</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_tar.html">5.10.4. Archivando archivos con tar</a></span></dt><dt><span class="sectio
 n"><a href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_star.html">5.10.5. Archivando archivos con tar</a></span></dt></dl></dd></dl></div><div class="para">
+		Las siguientes secciones dan un breve repaso de los paquetes de SELinux principales en Fedora 11; instalación y actualización de paquetes; qué archivos de registro se usan; el archivo de configuración principal de SELinux; habilitación y deshabilitación de SELinux; modos de SELinux; configuración de Booleanos; cambios temporales y permanentes de etiquetas de archivos y directorios; superposición de las etiquetas de sistemas de archivos con el comando <code class="command">mount</code>; montaje de sistemas de archivos NFS; y cómo preservar contextos de SELinux cuando se copia y compacta archivos y directorios.
+	</div><div class="section" title="5.1. Paquetes de SELinux" id="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Packages"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.1. Paquetes de SELinux</h2></div></div></div><div class="para">
+			En Fedora 11, los paquetes SELinux se instalan por defecto, a menos que hayan sido manualmente excluídos durante la instalación. Por defecto, la política destinada de SELinux se usa y SELinux corre en modo Obediente. La siguiente es una descripción breve de los paquetes SELinux principales:
 		</div><div class="para">
-			<span class="package">policycoreutils</span>: provides utilities, such as <code class="command">semanage</code>, <code class="command">restorecon</code>, <code class="command">audit2allow</code>, <code class="command">semodule</code>, <code class="command">load_policy</code>, and <code class="command">setsebool</code>, for operating and managing SELinux.
+			<span class="package">policycoreutils</span>: provee utilitarios, tales como <code class="command">semanage</code>, <code class="command">restorecon</code>, <code class="command">audit2allow</code>, <code class="command">semodule</code>, <code class="command">load_policy</code> y <code class="command">setsebool</code>, para la operación y administración de SELinux.
 		</div><div class="para">
-			<span class="package">policycoreutils-gui</span>: provides <code class="command">system-config-selinux</code>, a graphical tool for managing SELinux.
+			<span class="package">policycoreutils-gui</span>: provee <code class="command">system-config-selinux</code>, una herramienta gráfica para la administración de SELinux.
 		</div><div class="para">
-			<span class="package">selinux-policy</span>: provides the SELinux Reference Policy. The SELinux Reference Policy is a complete SELinux policy, and is used as a basis for other policies, such as the SELinux targeted policy. Refer to the Tresys Technology <a href="http://oss.tresys.com/projects/refpolicy">SELinux Reference Policy</a> page for further information. The <span class="package">selinux-policy-devel</span> package provides development tools, such as <code class="command">/usr/share/selinux/devel/policygentool</code> and <code class="command">/usr/share/selinux/devel/policyhelp</code>, as well as example policy files. This package was merged into the <span class="package">selinux-policy</span> package.
+			<span class="package">selinux-policy</span>: provee una Política de Referencia de SELinux. La Política de Referencia de SELinux en una política de SELinux completa, y se usa como base para otras políticas, tales como la política destinada de SELinux. Vaya a la página <a href="http://oss.tresys.com/projects/refpolicy">Política de Referencia de SELinux</a> de Tresys Technology para más información. El paquete <span class="package">selinux-policy-devel</span> provee herramientas de desarrollo, tales como<code class="command">/usr/share/selinux/devel/policygentool</code> y <code class="command">/usr/share/selinux/devel/policyhelp</code>, así como archivos de política ejemplos. Este paquete fue mezclado con el paquete <span class="package">selinux-policy</span>.
 		</div><div class="para">
-			<span class="package">selinux-policy-<em class="replaceable"><code>policy</code></em></span>: provides SELinux policies. For targeted policy, install <span class="package">selinux-policy-targeted</span>. For MLS, install <span class="package">selinux-policy-mls</span>. In Fedora 8, the strict policy was merged into targeted policy, allowing confined and unconfined users to co-exist on the same system.
+			<span class="package">selinux-policy-<em class="replaceable"><code>policy</code></em></span>: provee las políticas de SELinux. Para la política destinada, instale <span class="package">selinux-policy-targeted</span>. Para MLS, instale <span class="package">selinux-policy-mls</span>. En Fedora 8, la política estricta fue mezclada con la política destinada, permitiendo a los usuarios confinados y no confinados coexistir en el mismo sistema.
 		</div><div class="para">
-			<span class="package">setroubleshoot-server</span>: translates denial messages, produced when access is denied by SELinux, into detailed descriptions that are viewed with <code class="command">sealert</code> (which is provided by this package).
+			<span class="package">setroubleshoot-server</span>: traduce mensajes de negaciones, producidos cuando el acceso es denegado por SELinux, en descripciones detalladas que se ven con <code class="command">sealert</code> (que se provee en este paquete).
 		</div><div class="para">
-			<span class="package">setools</span>, <span class="package">setools-gui</span>, and <span class="package">setools-console</span>: these packages provide the <a href="http://oss.tresys.com/projects/setools">Tresys Technology SETools distribution</a>, a number of tools and libraries for analyzing and querying policy, audit log monitoring and reporting, and file context management<sup>[<a id="id707452" href="#ftn.id707452" class="footnote">8</a>]</sup>. The <span class="package">setools</span> package is a meta-package for SETools. The <span class="package">setools-gui</span> package provides the <code class="command">apol</code>, <code class="command">seaudit</code>, and <code class="command">sediffx</code> tools. The <span class="package">setools-console</span> package provides the <code class="command">seaudit-report</code>, <code class="command">sechecker</code>, <code class="command">sediff</code>, <code class="command">seinfo</code>, <code class="command">sesearch</cod
 e>, <code class="command">findcon</code>, <code class="command">replcon</code>, and <code class="command">indexcon</code> command line tools. Refer to the <a href="http://oss.tresys.com/projects/setools">Tresys Technology SETools</a> page for information about these tools.
+			<span class="package">setools</span>, <span class="package">setools-gui</span>, and <span class="package">setools-console</span>: these packages provide the <a href="http://oss.tresys.com/projects/setools">Tresys Technology SETools distribution</a>, a number of tools and libraries for analyzing and querying policy, audit log monitoring and reporting, and file context management<sup>[<a id="id1032040" href="#ftn.id1032040" class="footnote">8</a>]</sup>. The <span class="package">setools</span> package is a meta-package for SETools. The <span class="package">setools-gui</span> package provides the <code class="command">apol</code>, <code class="command">seaudit</code>, and <code class="command">sediffx</code> tools. The <span class="package">setools-console</span> package provides the <code class="command">seaudit-report</code>, <code class="command">sechecker</code>, <code class="command">sediff</code>, <code class="command">seinfo</code>, <code class="command">sesearch</c
 ode>, <code class="command">findcon</code>, <code class="command">replcon</code>, and <code class="command">indexcon</code> command line tools. Refer to the <a href="http://oss.tresys.com/projects/setools">Tresys Technology SETools</a> page for information about these tools.
 		</div><div class="para">
-			<span class="package">libselinux-utils</span>: provides the <code class="command">avcstat</code>, <code class="command">getenforce</code>, <code class="command">getsebool</code>, <code class="command">matchpathcon</code>, <code class="command">selinuxconlist</code>, <code class="command">selinuxdefcon</code>, <code class="command">selinuxenabled</code>, <code class="command">setenforce</code>, <code class="command">togglesebool</code> tools.
+			<span class="package">libselinux-utils</span>: provee las herramientas <code class="command">avcstat</code>, <code class="command">getenforce</code>, <code class="command">getsebool</code>, <code class="command">matchpathcon</code>, <code class="command">selinuxconlist</code>, <code class="command">selinuxdefcon</code>, <code class="command">selinuxenabled</code>, <code class="command">setenforce</code>, <code class="command">togglesebool</code>.
 		</div><div class="para">
-			<span class="package">mcstrans</span>: translates levels, such as <code class="computeroutput">s0-s0:c0.c1023</code>, to an easier to read form, such as <code class="computeroutput">SystemLow-SystemHigh</code>. This package is not installed by default.
+			<span class="package">mcstrans</span>: traduce niveles, tales como <code class="computeroutput">s0-s0:c0.c1023</code>, a una forma legible como <code class="computeroutput">SystemLow-SystemHigh</code>. Este paquete no se instala por defecto.
 		</div><div class="para">
-			To install packages in Fedora 11, as the Linux root user, run the <code class="command">yum install <em class="replaceable"><code>package-name</code></em></code> command. For example, to install the <span class="package">mcstrans</span> package, run the <code class="command">yum install mcstrans</code> command. To upgrade all installed packages in Fedora 11, run the <code class="command">yum update</code> command.
+			Para instalar paquetes en Fedora 11, como usuario root de Linux ejecute el comando <code class="command">yum install <em class="replaceable"><code>nombre-de-paquete</code></em></code>. Por ejemplo, para instalar el paquete <span class="package">mcstrans</span>, ejecute el comando <code class="command">yum install mcstrans</code>. Para actualizar todos los paquetes instalados en Fedora 11, ejecute el comando <code class="command">yum update</code>.
 		</div><div class="para">
-			Refer to <a href="http://docs.fedoraproject.org/yum/en/">Managing Software with yum</a><sup>[<a id="id438042" href="#ftn.id438042" class="footnote">9</a>]</sup> for further information about using <code class="command">yum</code> to manage packages.
+			Vaya a <a href="http://docs.fedoraproject.org/yum/en/">Administración de Software con yum</a><sup>[<a id="id1148838" href="#ftn.id1148838" class="footnote">9</a>]</sup> para más información sobre el uso de <code class="command">yum</code> para administrar paquetes.
 		</div><div class="note"><h2>Nota</h2><div class="para">
-				In previous versions of Fedora, the <span class="package">selinux-policy-devel</span> package is required when making a local policy module with <code class="command">audit2allow -M</code>.
-			</div></div></div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id707452" href="#id707452" class="para">8</a>] </sup>
+				En versiones anteriores de Fedora, el paquete <span class="package">selinux-policy-devel</span> es necesario cuando se crea un módulo de política local con <code class="command">audit2allow -M</code>.
+			</div></div></div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id1032040" href="#id1032040" class="para">8</a>] </sup>
 				Brindle, Joshua. "Re: blurb for fedora setools packages" Email to Murray McAllister. 1 November 2008. Any edits or changes in this version were done by Murray McAllister.
-			</p></div><div class="footnote"><p><sup>[<a id="ftn.id438042" href="#id438042" class="para">9</a>] </sup>
-				Managing Software with yum, written by Stuart Ellis, edited by Paul W. Frields, Rodrigo Menezes, and Hugo Cisneiros.
-			</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users.html"><strong>Anterior</strong>4.3. Confined and Unconfined Users</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used.html"><strong>Siguiente</strong>5.2. Which Log File is Used</a></li></ul></body></html>
+			</p></div><div class="footnote"><p><sup>[<a id="ftn.id1148838" href="#id1148838" class="para">9</a>] </sup>
+				Administración de Software con yum, escrito por Stuart Ellis, editado por Paul W. Frields, Rodrigo Menezes y Hugo Cisneiros.
+			</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users.html"><strong>Anterior</strong>4.3. Usuarios Confinados y no Confinados</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used.html"><strong>Siguiente</strong>5.2. Qué Archivo Log se usa</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/index.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/index.html
index 91bd75d..456cf0c 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/index.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/index.html
@@ -1,9 +1,9 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Security-Enhanced Linux</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><meta name="description" content="This book is about managing and using Security-Enhanced Linux." /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="next" href="pref-Security-Enhanced_Linux-Preface.html" title="Preface" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><
 img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"></li><li class="next"><a accesskey="n" href="pref-Security-Enhanced_Linux-Preface.html"><strong>Siguiente</strong></a></li></ul><div xml:lang="es-ES" class="book" title="Security-Enhanced Linux" lang="es-ES"><div class="titlepage"><div><div class="producttitle" font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><span class="productname">Fedora</span> <span class="productnumber">11</span></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h1 id="id391277" class="title">Security-Enhanced Linux</h1></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h2 class="subt
 itle">User Guide</h2></div><p class="edition">Edición 1.3</p><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h3 class="corpauthor">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Linux con Seguridad Mejorada</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><meta name="description" content="Este libro es acerca de la administración y uso del Linux de Seguridad Mejorada." /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="next" href="pref-Security-Enhanced_Linux-Preface.html" title="Prefacio" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="h
 ttp://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"></li><li class="next"><a accesskey="n" href="pref-Security-Enhanced_Linux-Preface.html"><strong>Siguiente</strong></a></li></ul><div xml:lang="es-ES" class="book" title="Linux con Seguridad Mejorada" lang="es-ES"><div class="titlepage"><div><div class="producttitle" font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><span class="productname">Fedora</span> <span class="productnumber">11</span></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h1 id="id647980" class="title">Linux con Seguridad Mejorada</h1></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="1
 2pt" text-align="center"><h2 class="subtitle">Guía del Usuario</h2></div><p class="edition">Edición 1.3</p><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h3 class="corpauthor">
 		<span class="inlinemediaobject"><object data="Common_Content/images/title_logo.svg" type="image/svg+xml"> Fedora Documentation Project</object></span>
 
-	</h3></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div xml:lang="es-ES" class="authorgroup" lang="es-ES"><div class="author"><h3 class="author"><span class="firstname">Murray</span> <span class="surname">McAllister</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:mmcallis at redhat.com">mmcallis at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Daniel</span> <span class="surname">Walsh</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Security Engineering</span></div><code class="email"><a class="email" href="mailto:dwalsh at redhat.com">dwalsh at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Dominick</span> <span class="surname">Grift</span></h3><span class
 ="contrib">Technical editor for the Introduction, SELinux Contexts, Targeted Policy, Working with SELinux, Confining Users, and Troubleshooting chapters.</span> <div class="affiliation"><span class="orgname"></span> <span class="orgdiv"></span></div><code class="email"><a class="email" href="mailto:domg472 at gmail.com">domg472 at gmail.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Eric</span> <span class="surname">Paris</span></h3><span class="contrib">Technical editor for the Mounting File Systems and Raw Audit Messages sections.</span> <div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Security Engineering</span></div><code class="email"><a class="email" href="mailto:eparis at parisplace.org">eparis at parisplace.org</a></code></div><div class="author"><h3 class="author"><span class="firstname">James</span> <span class="surname">Morris</span></h3><span class="contrib">Technical editor for the Introduction and Targ
 eted Policy chapters.</span> <div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Security Engineering</span></div><code class="email"><a class="email" href="mailto:jmorris at redhat.com">jmorris at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Scott</span> <span class="surname">Radvan</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:sradvan at redhat.com">sradvan at redhat.com</a></code></div></div></div><hr /><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div id="id1831080" class="legalnotice"><h1 class="legalnotice">Aviso Legal</h1><div class="para">
+	</h3></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div xml:lang="es-ES" class="authorgroup" lang="es-ES"><div class="author"><h3 class="author"><span class="firstname">Murray</span> <span class="surname">McAllister</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:mmcallis at redhat.com">mmcallis at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Daniel</span> <span class="surname">Walsh</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Security Engineering</span></div><code class="email"><a class="email" href="mailto:dwalsh at redhat.com">dwalsh at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Dominick</span> <span class="surname">Grift</span></h3><span class
 ="contrib">Technical editor for the Introduction, SELinux Contexts, Targeted Policy, Working with SELinux, Confining Users, and Troubleshooting chapters.</span> <div class="affiliation"><span class="orgname"></span> <span class="orgdiv"></span></div><code class="email"><a class="email" href="mailto:domg472 at gmail.com">domg472 at gmail.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Eric</span> <span class="surname">Paris</span></h3><span class="contrib">Technical editor for the Mounting File Systems and Raw Audit Messages sections.</span> <div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Security Engineering</span></div><code class="email"><a class="email" href="mailto:eparis at parisplace.org">eparis at parisplace.org</a></code></div><div class="author"><h3 class="author"><span class="firstname">James</span> <span class="surname">Morris</span></h3><span class="contrib">Technical editor for the Introduction and Targ
 eted Policy chapters.</span> <div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Security Engineering</span></div><code class="email"><a class="email" href="mailto:jmorris at redhat.com">jmorris at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Scott</span> <span class="surname">Radvan</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:sradvan at redhat.com">sradvan at redhat.com</a></code></div></div></div><hr /><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div id="id1020016" class="legalnotice"><h1 class="legalnotice">Aviso Legal</h1><div class="para">
 		Copyright <span class="trademark"></span>© 2009 Red Hat, Inc. and others.
 	</div><div class="para">
 		The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at <a href="http://creativecommons.org/licenses/by-sa/3.0/">http://creativecommons.org/licenses/by-sa/3.0/</a>. The original authors of this document, and Red Hat, designate the Fedora Project as the "Attribution Party" for purposes of CC-BY-SA. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
@@ -22,5 +22,5 @@
 	</div><div class="para">
 		All other trademarks are the property of their respective owners.
 	</div></div></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div class="abstract" title="Resumen"><h6>Resumen</h6><div class="para">
-			This book is about managing and using Security-Enhanced <span class="trademark">Linux</span>®.
-		</div></div></div></div><hr /></div><div class="toc"><dl><dt><span class="preface"><a href="pref-Security-Enhanced_Linux-Preface.html">Preface</a></span></dt><dd><dl><dt><span class="section"><a href="pref-Security-Enhanced_Linux-Preface.html#id537810">1. Convenciones del Documento</a></span></dt><dd><dl><dt><span class="section"><a href="pref-Security-Enhanced_Linux-Preface.html#id434297">1.1. Convenciones Tipográficas</a></span></dt><dt><span class="section"><a href="pref-Security-Enhanced_Linux-Preface.html#id437632">1.2. Convenciones del documento</a></span></dt><dt><span class="section"><a href="pref-Security-Enhanced_Linux-Preface.html#id414752">1.3. Notas y Advertencias</a></span></dt></dl></dd><dt><span class="section"><a href="pr01s02.html">2. ¡Necesitamos sus comentarios!</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Security-Enhanced_Linux-Trademark_Information.html">1. Trademark Information</a></span></dt><dd><dl><dt><span class="section"><
 a href="chap-Security-Enhanced_Linux-Trademark_Information.html#chap-Security-Enhanced_Linux-Trademark_Information-Source_Code">1.1. Source Code</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Security-Enhanced_Linux-Introduction.html">2. Introduction</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-Introduction.html#sect-Security-Enhanced_Linux-Introduction-Benefits_of_running_SELinux">2.1. Benefits of running SELinux</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Introduction-Examples.html">2.2. Examples</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture.html">2.3. SELinux Architecture</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Introduction-SELinux_on_Other_Operating_Systems.html">2.4. SELinux on Other Operating Systems</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Securit
 y-Enhanced_Linux-SELinux_Contexts.html">3. SELinux Contexts</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-SELinux_Contexts.html#sect-Security-Enhanced_Linux-SELinux_Contexts-Domain_Transitions">3.1. Domain Transitions</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Processes.html">3.2. SELinux Contexts for Processes</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Users.html">3.3. SELinux Contexts for Users</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Security-Enhanced_Linux-Targeted_Policy.html">4. Targeted Policy</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-Targeted_Policy.html#sect-Security-Enhanced_Linux-Targeted_Policy-Confined_Processes">4.1. Confined Processes</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_
 Linux-Targeted_Policy-Unconfined_Processes.html">4.2. Unconfined Processes</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users.html">4.3. Confined and Unconfined Users</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Security-Enhanced_Linux-Working_with_SELinux.html">5. Working with SELinux</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-Working_with_SELinux.html#sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Packages">5.1. SELinux Packages</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used.html">5.2. Which Log File is Used</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Main_Configuration_File.html">5.3. Main Configuration File</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_wi
 th_SELinux-Enabling_and_Disabling_SELinux.html">5.4. Enabling and Disabling SELinux</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html#sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Enabling_SELinux">5.4.1. Enabling SELinux</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux.html">5.4.2. Disabling SELinux</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes.html">5.5. SELinux Modes</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html">5.6. Booleans</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html#sect-Security-Enhanced_Linux-Booleans-Listing_Booleans">5.6.1. Listing Booleans</a></span></dt><dt><
 span class="section"><a href="sect-Security-Enhanced_Linux-Booleans-Configuring_Booleans.html">5.6.2. Configuring Booleans</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS.html">5.6.3. Booleans for NFS and CIFS</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files.html">5.7. SELinux Contexts - Labeling Files</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files.html#sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Temporary_Changes_chcon">5.7.1. Temporary Changes: chcon</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext.html">5.7.2. Persistent Changes: semanage fcontext</a></span></dt></dl></dd><dt><span class="section"><a href="sect
 -Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types.html">5.8. The file_t and default_t Types</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html">5.9. Mounting File Systems</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html#sect-Security-Enhanced_Linux-Mounting_File_Systems-Context_Mounts">5.9.1. Context Mounts</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Changing_the_Default_Context.html">5.9.2. Changing the Default Context</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Mounting_an_NFS_File_System.html">5.9.3. Mounting an NFS File System</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Multiple_NFS_Mounts.html">5.9.4. Multiple NFS Mo
 unts</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Making_Context_Mounts_Persistent.html">5.9.5. Making Context Mounts Persistent</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html">5.10. Maintaining SELinux Labels </a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html#sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Copying_Files_and_Directories">5.10.1. Copying Files and Directories</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Moving_Files_and_Directories.html">5.10.2. Moving Files and Directories</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context.html">5.10.3. Checking the Default S
 ELinux Context</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_tar.html">5.10.4. Archiving Files with tar</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_star.html">5.10.5. Archiving Files with star</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="chap-Security-Enhanced_Linux-Confining_Users.html">6. Confining Users</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-Confining_Users.html#sect-Security-Enhanced_Linux-Confining_Users-Linux_and_SELinux_User_Mappings">6.1. Linux and SELinux User Mappings</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Confining_Users-Confining_New_Linux_Users_useradd.html">6.2. Confining New Linux Users: useradd</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Confining_Use
 rs-Confining_Existing_Linux_Users_semanage_login.html">6.3. Confining Existing Linux Users: semanage login</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Confining_Users-Changing_the_Default_Mapping.html">6.4. Changing the Default Mapping</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Confining_Users-xguest_Kiosk_Mode.html">6.5. xguest: Kiosk Mode</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications.html">6.6. Booleans for Users Executing Applications</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Security-Enhanced_Linux-Troubleshooting.html">7. Troubleshooting</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-Troubleshooting.html#sect-Security-Enhanced_Linux-Troubleshooting-What_Happens_when_Access_is_Denied">7.1. What Happens when Access is Denied</a></span></dt><dt><span c
 lass="section"><a href="sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html">7.2. Top Three Causes of Problems</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html#sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Labeling_Problems">7.2.1. Labeling Problems</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running.html">7.2.2. How are Confined Services Running?</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Evolving_Rules_and_Broken_Applications.html">7.2.3. Evolving Rules and Broken Applications</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html">7.3. Fixing Problems</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enh
 anced_Linux-Troubleshooting-Fixing_Problems.html#sect-Security-Enhanced_Linux-Fixing_Problems-Linux_Permissions">7.3.1. Linux Permissions</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-Possible_Causes_of_Silent_Denials.html">7.3.2. Possible Causes of Silent Denials</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services.html">7.3.3. Manual Pages for Services</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains.html">7.3.4. Permissive Domains</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-Searching_For_and_Viewing_Denials.html">7.3.5. Searching For and Viewing Denials</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages.html">7.3.6. Raw Audit Messages</a></span></dt><dt><span class="section"><a hre
 f="sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages.html">7.3.7. sealert Messages</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow.html">7.3.8. Allowing Access: audit2allow</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="chap-Security-Enhanced_Linux-Further_Information.html">8. Further Information</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-Further_Information.html#sect-Security-Enhanced_Linux-Further_Information-Contributors">8.1. Contributors</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Further_Information-Other_Resources.html">8.2. Other Resources</a></span></dt></dl></dd><dt><span class="appendix"><a href="appe-Security-Enhanced_Linux-Revision_History.html">A. Revision History</a></span></dt></dl></div></div><ul class="docnav"><li class="previous"></li><li class="next"><a accesskey="n" hr
 ef="pref-Security-Enhanced_Linux-Preface.html"><strong>Siguiente</strong>Preface</a></li></ul></body></html>
+			Este libro es acerca de la administración y uso del <span class="trademark">Linux</span>® de Seguridad Mejorada.
+		</div></div></div></div><hr /></div><div class="toc"><dl><dt><span class="preface"><a href="pref-Security-Enhanced_Linux-Preface.html">Prefacio</a></span></dt><dd><dl><dt><span class="section"><a href="pref-Security-Enhanced_Linux-Preface.html#id938858">1. Convenciones del Documento</a></span></dt><dd><dl><dt><span class="section"><a href="pref-Security-Enhanced_Linux-Preface.html#id1199191">1.1. Convenciones Tipográficas</a></span></dt><dt><span class="section"><a href="pref-Security-Enhanced_Linux-Preface.html#id843248">1.2. Convenciones del documento</a></span></dt><dt><span class="section"><a href="pref-Security-Enhanced_Linux-Preface.html#id1038328">1.3. Notas y Advertencias</a></span></dt></dl></dd><dt><span class="section"><a href="pr01s02.html">2. ¡Necesitamos sus comentarios!</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Security-Enhanced_Linux-Trademark_Information.html">1. Información de Marca Comercial</a></span></dt><dd><dl><dt><span clas
 s="section"><a href="chap-Security-Enhanced_Linux-Trademark_Information.html#chap-Security-Enhanced_Linux-Trademark_Information-Source_Code">1.1. Source Code</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Security-Enhanced_Linux-Introduction.html">2. Introducción</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-Introduction.html#sect-Security-Enhanced_Linux-Introduction-Benefits_of_running_SELinux">2.1. Beneficios de usar SELinux</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Introduction-Examples.html">2.2. Ejemplos</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture.html">2.3. Arquitectura de SELinux</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Introduction-SELinux_on_Other_Operating_Systems.html">2.4. SELinux en otros Sistemas Operativos</a></span></dt></dl></dd><dt><span class="chapter"><a 
 href="chap-Security-Enhanced_Linux-SELinux_Contexts.html">3. Contextos de SELinux</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-SELinux_Contexts.html#sect-Security-Enhanced_Linux-SELinux_Contexts-Domain_Transitions">3.1. Transiciones de Dominios</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Processes.html">3.2. Contextos de SELinux para los Procesos</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Users.html">3.3. Contextos de SELinux para los Usuarios</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Security-Enhanced_Linux-Targeted_Policy.html">4. Política Destinado</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-Targeted_Policy.html#sect-Security-Enhanced_Linux-Targeted_Policy-Confined_Processes">4.1. Procesos Confinados</a></span></dt><dt><
 span class="section"><a href="sect-Security-Enhanced_Linux-Targeted_Policy-Unconfined_Processes.html">4.2. Procesos no Confinados</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users.html">4.3. Usuarios Confinados y no Confinados</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Security-Enhanced_Linux-Working_with_SELinux.html">5. Trabajando con SELinux</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-Working_with_SELinux.html#sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Packages">5.1. Paquetes de SELinux</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used.html">5.2. Qué Archivo Log se usa</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Main_Configuration_File.html">5.3. Archivo de Configuración Principal</a></span>
 </dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html">5.4. Habilitando y Deshabilitando SELinux</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html#sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Enabling_SELinux">5.4.1. Habilitando SELinux</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux.html">5.4.2. Deshabilitando SELinux</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes.html">5.5. Modos de SELinux</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html">5.6. Booleanos</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html#sec
 t-Security-Enhanced_Linux-Booleans-Listing_Booleans">5.6.1. Listando los Booleanos</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Booleans-Configuring_Booleans.html">5.6.2. Configurando los Booleanos</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS.html">5.6.3. Booleanos para NFS y CIFS</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files.html">5.7. Contextos de SELinux - Etiquetado de Archivos</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files.html#sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Temporary_Changes_chcon">5.7.1. Cambios Temporales: chcon</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fc
 ontext.html">5.7.2. Cambios Persistentes: semanage fcontext</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types.html">5.8. Los tipos file_t y default_t</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html">5.9. Montaje de Sistemas de Archivos</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html#sect-Security-Enhanced_Linux-Mounting_File_Systems-Context_Mounts">5.9.1. Montajes de Contexto</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Changing_the_Default_Context.html">5.9.2. Cambio del Contexto Predeterminado</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Mounting_an_NFS_File_System.html">5.9.3. Montando un Sistema de Archivos N
 FS</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Multiple_NFS_Mounts.html">5.9.4. Montajes NFS Múltiples</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Making_Context_Mounts_Persistent.html">5.9.5. Haciendo Persistente los Contextos de Montajes</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html">5.10. Mantención de las Etiquetas de SELinux</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html#sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Copying_Files_and_Directories">5.10.1. Copia de Directorios y Archivos</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Moving_Files_and_Directories.html">5.10.2. Movimiento de Archivos y 
 Directorios</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context.html">5.10.3. Chequeando el Contexto SELinux Predeterminado</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_tar.html">5.10.4. Archivando archivos con tar</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_star.html">5.10.5. Archivando archivos con tar</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="chap-Security-Enhanced_Linux-Confining_Users.html">6. Confinando a los Usuarios</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-Confining_Users.html#sect-Security-Enhanced_Linux-Confining_Users-Linux_and_SELinux_User_Mappings">6.1. Linux y los Mapeos de Usuarios de SELinux</a></span></dt><dt><span class="section">
 <a href="sect-Security-Enhanced_Linux-Confining_Users-Confining_New_Linux_Users_useradd.html">6.2. Confinando Usuarios Nuevos de Linux: useradd</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Confining_Users-Confining_Existing_Linux_Users_semanage_login.html">6.3. Confinando Usuarios Linux Existentes: semanage login</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Confining_Users-Changing_the_Default_Mapping.html">6.4. Cambiando el Mapeo Predeterminado</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Confining_Users-xguest_Kiosk_Mode.html">6.5. xguest: Modo Kiosk</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications.html">6.6. Booleanos para que los Usuarios Ejecuten Aplicaciones</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Security-Enhanced_Linux-Troubleshooting.html">7. Solución a 
 Problemas</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-Troubleshooting.html#sect-Security-Enhanced_Linux-Troubleshooting-What_Happens_when_Access_is_Denied">7.1. Qué pasa cuando el Acceso es Denegado</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html">7.2. Tres Principales Causas de Problemas</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html#sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Labeling_Problems">7.2.1. Problemas de Etiquetados</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running.html">7.2.2. ¿Cómo se Ejecutan los Servicios Confinados?</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Evolving_Rules_and_
 Broken_Applications.html">7.2.3. Evolucionando las Reglas y las Aplicaciones Rotas</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html">7.3. Corrección de Problemas</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html#sect-Security-Enhanced_Linux-Fixing_Problems-Linux_Permissions">7.3.1. Permisos de Linux</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-Possible_Causes_of_Silent_Denials.html">7.3.2. Posibles Causas de las Negaciones Silenciosas</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services.html">7.3.3. Páginas de Manual para Servicios</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains.html">7.3.4. Dominios Permisivos</a></span></dt><dt><span class="s
 ection"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-Searching_For_and_Viewing_Denials.html">7.3.5. Búsqueda y Revisión de Negaciones</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages.html">7.3.6. Raw Audit Messages</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages.html">7.3.7. Mensajes sealert</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow.html">7.3.8. Permitiendo el Acceso: audit2allow</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="chap-Security-Enhanced_Linux-Further_Information.html">8. Información Adicional</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-Further_Information.html#sect-Security-Enhanced_Linux-Further_Information-Contributors">8.1. Contributors</a></span></dt><dt><span class="section">
 <a href="sect-Security-Enhanced_Linux-Further_Information-Other_Resources.html">8.2. Other Resources</a></span></dt></dl></dd><dt><span class="appendix"><a href="appe-Security-Enhanced_Linux-Revision_History.html">A. Revision History</a></span></dt></dl></div></div><ul class="docnav"><li class="previous"></li><li class="next"><a accesskey="n" href="pref-Security-Enhanced_Linux-Preface.html"><strong>Siguiente</strong>Prefacio</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/pr01s02.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/pr01s02.html
index 92b581f..43a28c1 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/pr01s02.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/pr01s02.html
@@ -1,9 +1,9 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2. ¡Necesitamos sus comentarios!</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="pref-Security-Enhanced_Linux-Preface.html" title="Preface" /><link rel="prev" href="pref-Security-Enhanced_Linux-Preface.html" title="Preface" /><link rel="next" href="chap-Security-Enhanced_Linux-Trademark_Information.html" title="Capítulo 1. Trademark Information" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade you
 r browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="pref-Security-Enhanced_Linux-Preface.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-Trademark_Information.html"><strong>Siguiente</strong></a></li></ul><div xml:lang="es-ES" class="section" title="2. ¡Necesitamos sus comentarios!" lang="es-ES"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id485000">2. ¡Necesitamos sus comentarios!</h2></div></div></div><a id="id485012" class="indexterm"></a><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2. ¡Necesitamos sus comentarios!</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="pref-Security-Enhanced_Linux-Preface.html" title="Prefacio" /><link rel="prev" href="pref-Security-Enhanced_Linux-Preface.html" title="Prefacio" /><link rel="next" href="chap-Security-Enhanced_Linux-Trademark_Information.html" title="Capítulo 1. Información de Marca Comercial" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to vi
 ew it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="pref-Security-Enhanced_Linux-Preface.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-Trademark_Information.html"><strong>Siguiente</strong></a></li></ul><div xml:lang="es-ES" class="section" title="2. ¡Necesitamos sus comentarios!" lang="es-ES"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id822198">2. ¡Necesitamos sus comentarios!</h2></div></div></div><a id="id822207" class="indexterm"></a><div class="para">
 		Si encuentra un error tipográfico en este manual o si sabe de alguna manera de mejorarlo, nos gustaría escuchar sus sugerencias. Por favor complete un reporte en Bugzilla: <a href="http://bugzilla.redhat.com/bugzilla/">http://bugzilla.redhat.com/bugzilla/</a> usando el producto <span class="application"><strong>Fedora Documentation</strong></span>.
 	</div><div class="para">
 		Cuando envíe un reporte de error no olvide mencionar el identificador del manual: <em class="citetitle">selinux-user-guide</em>
 	</div><div class="para">
 		Si tiene una sugerencia para mejorar la documentación, intente ser tan específico como sea posible cuando describa su sugerencia. Si ha encontrado un error, por favor incluya el número de sección y parte del texto que rodea el error para que podamos encontrarlo más fácilmente.
-	</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="pref-Security-Enhanced_Linux-Preface.html"><strong>Anterior</strong>Preface</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-Trademark_Information.html"><strong>Siguiente</strong>Capítulo 1. Trademark Information</a></li></ul></body></html>
+	</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="pref-Security-Enhanced_Linux-Preface.html"><strong>Anterior</strong>Prefacio</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-Trademark_Information.html"><strong>Siguiente</strong>Capítulo 1. Información de Marca Comercial</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/pref-Security-Enhanced_Linux-Preface.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/pref-Security-Enhanced_Linux-Preface.html
index e6de83a..2454e00 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/pref-Security-Enhanced_Linux-Preface.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/pref-Security-Enhanced_Linux-Preface.html
@@ -1,22 +1,22 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Preface</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="index.html" title="Security-Enhanced Linux" /><link rel="prev" href="index.html" title="Security-Enhanced Linux" /><link rel="next" href="pr01s02.html" title="2. ¡Necesitamos sus comentarios!" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fed
 oraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="index.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="pr01s02.html"><strong>Siguiente</strong></a></li></ul><div xml:lang="es-ES" class="preface" title="Preface" id="pref-Security-Enhanced_Linux-Preface" lang="es-ES"><div class="titlepage"><div><div><h1 class="title">Preface</h1></div></div></div><div class="para">
-		The Fedora 11 SELinux User Guide is for people with minimal or no experience with SELinux. Although system administration experience is not necessary, content in this guide is written for system administration tasks. This guide provides an introduction to fundamental concepts and practical applications of SELinux. After reading this guide you should have an intermediate understanding of SELinux.
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Prefacio</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="prev" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="next" href="pr01s02.html" title="2. ¡Necesitamos sus comentarios!" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href
 ="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="index.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="pr01s02.html"><strong>Siguiente</strong></a></li></ul><div xml:lang="es-ES" class="preface" title="Prefacio" id="pref-Security-Enhanced_Linux-Preface" lang="es-ES"><div class="titlepage"><div><div><h1 class="title">Prefacio</h1></div></div></div><div class="para">
+		La Guía del Usuario de SELinux de Fedora 11 es para gente sin o con mínima experiencia con SELinux. Aunque la experiencia de administración de sistema no es necesario, el contenido de esta guía se escribe para tareas de administración del sistema. Esta guía provee una introducción a los conceptos fundamentales y aplicaciones prácticas de SELinux. Después de leer esta guía debe tener un entendimiento intermedio de SELinux.
 	</div><div class="para">
-		Thank you to everyone who offered encouragement, help, and testing - it is most appreciated. Very special thanks to:
+		Gracias a todos los que nos alentaron, ofrecieron ayuda y lo probaron - la ayuda es muy apreciada. Agradecimientos muy especiales a:
 	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-				Dominick Grift, Stephen Smalley, and Russell Coker for their contributions, help, and patience.
+				Dominick Grift, Stephen Smalley y Russell Coker por sus contribuciones, ayuda y paciencia.
 			</div></li><li class="listitem"><div class="para">
 				Karsten Wade for his help, adding a component for this guide to <a href="https://bugzilla.redhat.com/"> Red Hat Bugzilla</a>, and sorting out web hosting on <a href="http://docs.fedoraproject.org/">http://docs.fedoraproject.org/</a>.
 			</div></li><li class="listitem"><div class="para">
-				The <a href="http://fedoraproject.org/wiki/Infrastructure">Fedora Infrastructure Team</a> for providing hosting.
+				Al <a href="http://fedoraproject.org/wiki/Infrastructure">Equipo de Infraestructura de Fedora</a> por proveer el alojamiento.
 			</div></li><li class="listitem"><div class="para">
-				Jens-Ulrik Petersen for making sure the Red Hat Brisbane office has up-to-date Fedora mirrors.
-			</div></li></ul></div><div xml:lang="es-ES" class="section" title="1. Convenciones del Documento" lang="es-ES"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id537810">1. Convenciones del Documento</h2></div></div></div><div class="para">
+				Jens-Ulrik Petersen por asegurar que la oficina de Brisbane de Red Hat tenga espejos de Fedora actualizados.
+			</div></li></ul></div><div xml:lang="es-ES" class="section" title="1. Convenciones del Documento" lang="es-ES"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id938858">1. Convenciones del Documento</h2></div></div></div><div class="para">
 		Este manual utiliza varias convenciones para resaltar algunas palabras y frases y llamar la atención sobre ciertas partes específicas de información.
 	</div><div class="para">
 		En ediciones PDF y de papel, este manual utiliza tipos de letra procedentes de <a href="https://fedorahosted.org/liberation-fonts/">Liberation Fonts</a>. Liberation Fonts también se utilizan en ediciones de HTML si están instalados en su sistema. Si no, se muestran tipografías alternativas pero equivalentes. Nota: Red Hat Enterprise Linux 5 y siguientes incluyen Liberation Fonts predeterminadas.
-	</div><div class="section" title="1.1. Convenciones Tipográficas"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id434297">1.1. Convenciones Tipográficas</h3></div></div></div><div class="para">
+	</div><div class="section" title="1.1. Convenciones Tipográficas"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id1199191">1.1. Convenciones Tipográficas</h3></div></div></div><div class="para">
 			Se utilizan cuatro convenciones tipográficas para llamar la atención sobre palabras o frases específicas. Dichas convenciones y las circunstancias en que se aplican son las siguientes:
 		</div><div class="para">
 			<code class="literal">Negrita monoespaciado</code>
@@ -64,7 +64,7 @@
 			Aparte del uso estándar para presentar el título de un trabajo, las itálicas denotan el primer uso de un término nuevo e importante. Por ejemplo:
 		</div><div class="blockquote"><blockquote class="blockquote"><div class="para">
 				Publican es un sistema de publicación de <em class="firstterm">DocBook</em>.
-			</div></blockquote></div></div><div class="section" title="1.2. Convenciones del documento"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id437632">1.2. Convenciones del documento</h3></div></div></div><div class="para">
+			</div></blockquote></div></div><div class="section" title="1.2. Convenciones del documento"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id843248">1.2. Convenciones del documento</h3></div></div></div><div class="para">
 			Los mensajes de salida de la terminal o fragmentos de código fuente se distinguen visualmente del texto circundante.
 		</div><div class="para">
 			Los mensajes de salida enviados a una terminal se muestran en <code class="computeroutput">romano monoespaciado</code> y se presentan así:
@@ -93,7 +93,7 @@ books_tests  Desktop1  downloads      images  notes  scripts  svgs
    }
 }
 
-</pre></div><div class="section" title="1.3. Notas y Advertencias"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id414752">1.3. Notas y Advertencias</h3></div></div></div><div class="para">
+</pre></div><div class="section" title="1.3. Notas y Advertencias"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id1038328">1.3. Notas y Advertencias</h3></div></div></div><div class="para">
 			Finalmente, utilizamos tres estilos visuales para llamar la atención sobre la información que de otro modo se podría pasar por alto.
 		</div><div class="note"><h2>Nota</h2><div class="para">
 				Una nota es una sugerencia, atajo o enfoque alternativo para una tarea determinada. Ignorar una nota no debería tener consecuencias negativas, pero podría perderse de algunos trucos que pueden facilitarle las cosas.
@@ -101,4 +101,4 @@ books_tests  Desktop1  downloads      images  notes  scripts  svgs
 				Important boxes detail things that are easily missed: configuration changes that only apply to the current session, or services that need restarting before an update will apply. Ignoring a box labeled 'Important' won't cause data loss but may cause irritation and frustration.
 			</div></div><div class="warning"><h2>Advertencia</h2><div class="para">
 				Las advertencias no deben ignorarse. Ignorarlas muy probablemente ocasionará pérdida de datos.
-			</div></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="index.html"><strong>Anterior</strong>Security-Enhanced Linux</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="pr01s02.html"><strong>Siguiente</strong>2. ¡Necesitamos sus comentarios!</a></li></ul></body></html>
+			</div></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="index.html"><strong>Anterior</strong>Linux con Seguridad Mejorada</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="pr01s02.html"><strong>Siguiente</strong>2. ¡Necesitamos sus comentarios!</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS.html
index a7486c2..38602b3 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS.html
@@ -1,39 +1,39 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.6.3. Booleans for NFS and CIFS</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html" title="5.6. Booleans" /><link rel="prev" href="sect-Security-Enhanced_Linux-Booleans-Configuring_Booleans.html" title="5.6.2. Configuring Booleans" /><link rel="next" href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files.html" title="5.7. SELinux Contexts - Labeling Files" /></head><body class="toc_embeded "><div id="tocdiv" class="toc
 "><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Booleans-Configuring_Booleans.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.6.3. Booleans for NFS and CIFS" id="sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.6.3. Bo
 oleans for NFS and CIFS</h3></div></div></div><div class="para">
-				By default, NFS mounts on the client side are labeled with a default context defined by policy for NFS file systems. In common policies, this default context uses the <code class="computeroutput">nfs_t</code> type. Also, by default, Samba shares mounted on the client side are labeled with a default context defined by policy. In common policies, this default context uses the <code class="computeroutput">cifs_t</code> type.
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.6.3. Booleanos para NFS y CIFS</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html" title="5.6. Booleanos" /><link rel="prev" href="sect-Security-Enhanced_Linux-Booleans-Configuring_Booleans.html" title="5.6.2. Configurando los Booleanos" /><link rel="next" href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files.html" title="5.7. Contextos de SELinux - Etiquetado de Archivos" /></head><body class="toc_embeded "><di
 v id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Booleans-Configuring_Booleans.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.6.3. Booleanos para NFS y CIFS" id="sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS"><div class="titlepage"><div><div keep-together.within-column="always"><h3
  class="title">5.6.3. Booleanos para NFS y CIFS</h3></div></div></div><div class="para">
+				Por defecto, los montajes NFS en el lado del cliente se etiquetan con el contexto predeterminado definido por la política para sistemas de archivos NFS. En políticas comúnes, este contexto predeterminado usa el tipo <code class="computeroutput">nfs_t</code>. También, por defecto, los compartidos de Samba en el lado del cliente se etiquetan con el contexto predeterminado definido por la política. En políticas comúnes, este contexto predeterminado usa el tipo <code class="computeroutput">cifs_t</code>.
 			</div><div class="para">
-				Depending on policy configuration, services may not be able to read files labeled with the <code class="computeroutput">nfs_t</code> or <code class="computeroutput">cifs_t</code> types. This may prevent file systems labeled with these types from being mounted and then read or exported by other services. Booleans can be turned on or off to control which services are allowed to access the <code class="computeroutput">nfs_t</code> and <code class="computeroutput">cifs_t</code> types.
+				Dependiendo en la configuración de la política, los servicios pueden tener bloqueado la lectura a archivos con la etiqueta de los tipos <code class="computeroutput">nfs_t</code> o <code class="computeroutput">cifs_t</code>. Esto puede prevenir que los sistemas de archivo etiquetados con estas etiquetas se monten y sean leídos o exportados por otros servicios. Hay Booleanos que se pueden poner en 1 o 0 para controlar qué servicios pueden acceder los tipos <code class="computeroutput">nfs_t</code> y <code class="computeroutput">cifs_t</code>.
 			</div><div class="para">
-				The <code class="command">setsebool</code> and <code class="command">semanage</code> commands must be run as the Linux root user. The <code class="command">setsebool -P</code> command makes persistent changes. Do not use the <code class="option">-P</code> option if you do not want changes to persist across reboots:
-			</div><div class="formalpara"><h5 class="formalpara">Apache HTTP Server</h5>
-					To allow access to NFS file systems (files labeled with the <code class="computeroutput">nfs_t</code> type):
+				Los comandos <code class="command">setsebool</code> y <code class="command">semanage</code> se deben ejecutar como usuario root de Linux. El comando <code class="command">setsebool -P</code> hace persistentes a los cambios. No use la opción <code class="option">-P</code> si no quiere que los cambios persistan entre reiniciadas:
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Booleans_for_NFS_and_CIFS-Apache_HTTP_Server"><h5 class="formalpara">Servidor HTTP Apache</h5>
+					Para permitir el acceso a sistemas de archivo NFS (archivos etiquetados con el tipo <code class="computeroutput">nfs_t</code>):
 				</div><div class="para">
 				<code class="command">/usr/sbin/setsebool -P httpd_use_nfs on</code>
 			</div><div class="para">
-				To allow access to Samba file systems (files labeled with the <code class="computeroutput">cifs_t</code> type):
+				Para permitir el acceso a sistemas de archivos SAMBA (archivos etiquetados con el tipo <code class="computeroutput">cifs_t</code>):
 			</div><div class="para">
 				<code class="command">/usr/sbin/setsebool -P httpd_use_cifs on</code>
-			</div><div class="formalpara"><h5 class="formalpara">Samba</h5>
-					To export NFS file systems:
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Booleans_for_NFS_and_CIFS-Samba"><h5 class="formalpara">Samba</h5>
+					Para exportar sistemas de archivo NFS:
 				</div><div class="para">
 				<code class="command">/usr/sbin/setsebool -P samba_share_nfs on</code>
-			</div><div class="formalpara"><h5 class="formalpara">FTP (<code class="systemitem">vsftpd</code>)</h5>
-					To allow access to NFS file systems:
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Booleans_for_NFS_and_CIFS-FTP_vsftpd"><h5 class="formalpara">FTP (<code class="systemitem">vsftpd</code>)</h5>
+					Para permitir el acceso a sistemas de archivo NFS:
 				</div><div class="para">
 				<code class="command">/usr/sbin/setsebool -P allow_ftpd_use_nfs on</code>
 			</div><div class="para">
-				To allow access to Samba file systems:
+				Para permitir el acceso a sistemas de archivo Samba:
 			</div><div class="para">
 				<code class="command">/usr/sbin/setsebool -P allow_ftpd_use_cifs on</code>
-			</div><div class="formalpara"><h5 class="formalpara">Other Services</h5>
-					For a list of NFS related Booleans for other services:
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Booleans_for_NFS_and_CIFS-Other_Services"><h5 class="formalpara">Otros Servicios</h5>
+					Para una lista de los Booleanos relacionados con NFS para otros servicios:
 				</div><div class="para">
 				<code class="command">/usr/sbin/semanage boolean -l | grep nfs</code>
 			</div><div class="para">
-				For a list of Samba related Booleans for other services:
+				Para una lista de los Booleanos relacionados con SAMBA para otros servicios:
 			</div><div class="para">
 				<code class="command">/usr/sbin/semanage boolean -l | grep cifs</code>
 			</div><div class="note"><h2>Nota</h2><div class="para">
-					These Booleans exist in SELinux policy as shipped with Fedora 11. They may not exist in policy shipped with other versions of Fedora or other operating systems.
-				</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Booleans-Configuring_Booleans.html"><strong>Anterior</strong>5.6.2. Configuring Booleans</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files.html"><strong>Siguiente</strong>5.7. SELinux Contexts - Labeling Files</a></li></ul></body></html>
+					Estos Booleanos existen en la política de SELinux tal cual fueron puestos en Fedora 11. No pu eden existir en la política puesta en otras versiones de Fedora o de otros sistemas operativos.
+				</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Booleans-Configuring_Booleans.html"><strong>Anterior</strong>5.6.2. Configurando los Booleanos</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files.html"><strong>Siguiente</strong>5.7. Contextos de SELinux - Etiquetado de Archivos</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Booleans-Configuring_Booleans.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Booleans-Configuring_Booleans.html
index f9a0202..f023684 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Booleans-Configuring_Booleans.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Booleans-Configuring_Booleans.html
@@ -1,27 +1,27 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.6.2. Configuring Booleans</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html" title="5.6. Booleans" /><link rel="prev" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html" title="5.6. Booleans" /><link rel="next" href="sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS.html" title="5.6.3. Booleans for NFS and CIFS" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="..
 /../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.6.2. Configuring Booleans" id="sect-Security-Enhanced_Linux-Booleans-Configuring_Booleans"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.6.2. Configuring Booleans</h3></div></div></div><div class="para">
-				The <code class="command">setsebool <em class="replaceable"><code>boolean-name</code></em> <em class="replaceable"><code>x</code></em></code> command turns Booleans on or off, where <em class="replaceable"><code>boolean-name</code></em> is a Boolean name, and <em class="replaceable"><code>x</code></em> is either <code class="option">on</code> to turn the Boolean on, or <code class="option">off</code> to turn it off.
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.6.2. Configurando los Booleanos</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html" title="5.6. Booleanos" /><link rel="prev" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html" title="5.6. Booleanos" /><link rel="next" href="sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS.html" title="5.6.3. Booleanos para NFS y CIFS" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class=
 "toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.6.2. Configurando los Booleanos" id="sect-Security-Enhanced_Linux-Booleans-Configuring_Booleans"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.6.2. Configurando los Booleanos</h3></div></div></div><div 
 class="para">
+				El comando <code class="command">setsebool <em class="replaceable"><code>nombre-de-booleano</code></em> <em class="replaceable"><code>x</code></em></code> activa o desactiva Booleanos, donde <em class="replaceable"><code>nombre-de-booleano</code></em> es un nombre de Booleano, y <em class="replaceable"><code>x</code></em> es <code class="option">on</code> para activar, u <code class="option">off</code> para desactivar.
 			</div><div class="para">
-				The following example demonstrates configuring the <code class="computeroutput">httpd_can_network_connect_db</code> Boolean:
+				El siguiente ejemplo muestra la configuración de Booleano <code class="computeroutput">httpd_can_network_connect_db</code>:
 			</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
-						By default, the <code class="computeroutput">httpd_can_network_connect_db</code> Boolean is off, preventing Apache HTTP Server scripts and modules from connecting to database servers:
+						Por defecto, el booleano <code class="computeroutput">httpd_can_network_connect_db</code> está apagado, impidiendo a los scripts y módulos del Servidor HTTP Apache conectarse a servidores de bases de datos:
 					</div><pre class="screen">$ /usr/sbin/getsebool httpd_can_network_connect_db
 httpd_can_network_connect_db --&gt; off
 
 </pre></li><li class="listitem"><div class="para">
-						To temporarily enable Apache HTTP Server scripts and modules to connect to database servers, run the <code class="command">setsebool httpd_can_network_connect_db on</code> command as the Linux root user.
+						Para permitir temporalmente a los scripts y módulos del Servidor HTTP Apache conectarse a servidores de bases de datos, ejecute el comando <code class="command">setsebool httpd_can_network_connect_db on</code> como usuario root de Linux.
 					</div></li><li class="listitem"><div class="para">
-						Use the <code class="command">getsebool httpd_can_network_connect_db</code> command to verify the Boolean is turned on:
+						Use el comando <code class="command">getsebool httpd_can_network_connect_db</code> para verificar que el Booleano está activado:
 					</div><pre class="screen">$ /usr/sbin/getsebool httpd_can_network_connect_db
 httpd_can_network_connect_db --&gt; on
 
 </pre><div class="para">
-						This allows Apache HTTP Server scripts and modules to connect to database servers.
+						Esto permite a los scripts y módulos del Servidor HTTP Apache conectarse a servidores de bases de datos.
 					</div></li><li class="listitem"><div class="para">
-						This change is not persistent across reboots. To make changes persistent across reboots, run the <code class="command">setsebool -P <em class="replaceable"><code>boolean-name</code></em> on</code> command as the Linux root user:
+						Este cambio no es persistente entre reinicios. Para hacer los cambios persistentes, corra el comando <code class="command">setsebool -P <em class="replaceable"><code>boolean-name</code></em> on</code> como usuario root de Linux:
 					</div><pre class="screen"># /usr/sbin/setsebool -P httpd_can_network_connect_db on
 
 </pre></li><li class="listitem"><div class="para">
-						To temporarily revert to the default behavior, as the Linux root user, run the <code class="command">setsebool httpd_can_network_connect_db off</code> command. For changes that persist across reboots, run the <code class="command">setsebool -P httpd_can_network_connect_db off</code> command.
-					</div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html"><strong>Anterior</strong>5.6. Booleans</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS.html"><strong>Siguiente</strong>5.6.3. Booleans for NFS and CIFS</a></li></ul></body></html>
+						Para revertir temporalmente el comportamiento por defecto, como usuario root de Linux, corra el comando <code class="command">setsebool httpd_can_network_connect_db off</code>. Para que los cambios sean persistentes entre reiniciadas, ejecute el comando <code class="command">setsebool -P httpd_can_network_connect_db off</code>.
+					</div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html"><strong>Anterior</strong>5.6. Booleanos</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS.html"><strong>Siguiente</strong>5.6.3. Booleanos para NFS y CIFS</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications.html
index 2d2e12e..b718bdb 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications.html
@@ -1,23 +1,23 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.6. Booleans for Users Executing Applications</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="chap-Security-Enhanced_Linux-Confining_Users.html" title="Capítulo 6. Confining Users" /><link rel="prev" href="sect-Security-Enhanced_Linux-Confining_Users-xguest_Kiosk_Mode.html" title="6.5. xguest: Kiosk Mode" /><link rel="next" href="chap-Security-Enhanced_Linux-Troubleshooting.html" title="Capítulo 7. Troubleshooting" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="t
 oc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Confining_Users-xguest_Kiosk_Mode.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-Troubleshooting.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="6.6. Booleans for Users Executing Applications" id="sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.6. Booleans for Users Executing App
 lications</h2></div></div></div><div class="para">
-			Not allowing Linux users to execute applications (which inherit users' permissions) in their home directories and <code class="filename">/tmp/</code>, which they have write access to, helps prevent flawed or malicious applications from modifying files users' own. In Fedora 11, by default, Linux users in the <code class="computeroutput">guest_t</code> and <code class="computeroutput">xguest_t</code> domains can not execute applications in their home directories or <code class="filename">/tmp/</code>; however, by default, Linux users in the <code class="computeroutput">user_t</code> and <code class="computeroutput">staff_t</code> domains can.
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.6. Booleanos para que los Usuarios Ejecuten Aplicaciones</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Confining_Users.html" title="Capítulo 6. Confinando a los Usuarios" /><link rel="prev" href="sect-Security-Enhanced_Linux-Confining_Users-xguest_Kiosk_Mode.html" title="6.5. xguest: Modo Kiosk" /><link rel="next" href="chap-Security-Enhanced_Linux-Troubleshooting.html" title="Capítulo 7. Solución a Problemas" /></head><body class="toc_embeded "><div id="tocdiv" class="to
 c"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Confining_Users-xguest_Kiosk_Mode.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-Troubleshooting.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="6.6. Booleanos para que los Usuarios Ejecuten Aplicaciones" id="sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class=
 "title">6.6. Booleanos para que los Usuarios Ejecuten Aplicaciones</h2></div></div></div><div class="para">
+			No permitir que los usuarios Linux ejecuten aplicaciones (que heredan los permisos del usuario) en sus directorios de inicio (home) y <code class="filename">/tmp/</code>, a los que tienen acceso de escritura, lo que ayuda a evitar que aplicaciones con brechas o maliciosas puedan modificar archivos del usuario. En Fedora 11, por defecto, los usuarios Linux en los dominios <code class="computeroutput">guest_t</code> y <code class="computeroutput">xguest_t</code> no pueden ejecutar aplicaciones en los directorios de inicio o en <code class="filename">/tmp/</code>; however, por defecto, los usuarios Linux en los dominios <code class="computeroutput">user_t</code> and <code class="computeroutput">staff_t</code> si pueden.
 		</div><div class="para">
-			Booleans are available to change this behavior, and are configured with the <code class="command">setsebool</code> command. The <code class="command">setsebool</code> command must be run as the Linux root user. The <code class="command">setsebool -P</code> command makes persistent changes. Do not use the <code class="option">-P</code> option if you do not want changes to persist across reboots:
-		</div><div class="formalpara"><h5 class="formalpara">guest_t</h5>
-				To <span class="emphasis"><em>allow</em></span> Linux users in the <code class="computeroutput">guest_t</code> domain to execute applications in their home directories and <code class="filename">/tmp/</code>:
+			Hay booleanos disponibles para cambiar este comportamiento, y se configuran con el comando <code class="command">setsebool</code>. El comando <code class="command">setsebool</code> se debe usar con el usuario root de Linux. El comando <code class="command">setsebool -P</code> hace los cambios persistentes. No use la opción <code class="option">-P</code> si no quiere que los cambios persistan entre reiniciadas:
+		</div><div class="formalpara" id="form-Security-Enhanced_Linux-Booleans_for_Users_Executing_Applications-guest_t"><h5 class="formalpara">guest_t</h5>
+				Para <span class="emphasis"><em>permitir</em></span> a los usuarios Linux en el dominio <code class="computeroutput">guest_t</code> que ejecuten aplicaciones en sus directorios de inicio y en <code class="filename">/tmp/</code>:
 			</div><div class="para">
 			<code class="command">/usr/sbin/setsebool -P allow_guest_exec_content on</code>
-		</div><div class="formalpara"><h5 class="formalpara">xguest_t</h5>
-				To <span class="emphasis"><em>allow</em></span> Linux users in the <code class="computeroutput">xguest_t</code> domain to execute applications in their home directories and <code class="filename">/tmp/</code>:
+		</div><div class="formalpara" id="form-Security-Enhanced_Linux-Booleans_for_Users_Executing_Applications-xguest_t"><h5 class="formalpara">xguest_t</h5>
+				Para <span class="emphasis"><em>permitir</em></span> a los usuarios Linux en el dominio <code class="computeroutput">xguest_t</code> ejecutar aplicaciones en sus directorios inicios y <code class="filename">/tmp/</code>:
 			</div><div class="para">
 			<code class="command">/usr/sbin/setsebool -P allow_xguest_exec_content on</code>
-		</div><div class="formalpara"><h5 class="formalpara">user_t</h5>
-				To <span class="emphasis"><em>prevent</em></span> Linux users in the <code class="computeroutput">user_t</code> domain from executing applications in their home directories and <code class="filename">/tmp/</code>:
+		</div><div class="formalpara" id="form-Security-Enhanced_Linux-Booleans_for_Users_Executing_Applications-user_t"><h5 class="formalpara">user_t</h5>
+				Para <span class="emphasis"><em>impedir</em></span> que los usuarios Linux en el dominio <code class="computeroutput">user_t</code> ejecuten aplicaciones en sus directorios de inicio y <code class="filename">/tmp/</code>:
 			</div><div class="para">
 			<code class="command">/usr/sbin/setsebool -P allow_user_exec_content off</code>
-		</div><div class="formalpara"><h5 class="formalpara">staff_t</h5>
-				To <span class="emphasis"><em>prevent</em></span> Linux users in the <code class="computeroutput">staff_t</code> domain from executing applications in their home directories and <code class="filename">/tmp/</code>:
+		</div><div class="formalpara" id="form-Security-Enhanced_Linux-Booleans_for_Users_Executing_Applications-staff_t"><h5 class="formalpara">staff_t</h5>
+				Para <span class="emphasis"><em>impedir</em></span> que los usuarios Linux en el dominio <code class="computeroutput">staff_t</code> ejecuten aplicaciones en sus directorios de inicio y en <code class="filename">/tmp/</code>:
 			</div><div class="para">
 			<code class="command">/usr/sbin/setsebool -P allow_staff_exec_content off</code>
-		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Confining_Users-xguest_Kiosk_Mode.html"><strong>Anterior</strong>6.5. xguest: Kiosk Mode</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-Troubleshooting.html"><strong>Siguiente</strong>Capítulo 7. Troubleshooting</a></li></ul></body></html>
+		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Confining_Users-xguest_Kiosk_Mode.html"><strong>Anterior</strong>6.5. xguest: Modo Kiosk</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-Troubleshooting.html"><strong>Siguiente</strong>Capítulo 7. Solución a Problemas</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Confining_Users-Changing_the_Default_Mapping.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Confining_Users-Changing_the_Default_Mapping.html
index c9b6caa..2ff453a 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Confining_Users-Changing_the_Default_Mapping.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Confining_Users-Changing_the_Default_Mapping.html
@@ -1,13 +1,13 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.4. Changing the Default Mapping</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="chap-Security-Enhanced_Linux-Confining_Users.html" title="Capítulo 6. Confining Users" /><link rel="prev" href="sect-Security-Enhanced_Linux-Confining_Users-Confining_Existing_Linux_Users_semanage_login.html" title="6.3. Confining Existing Linux Users: semanage login" /><link rel="next" href="sect-Security-Enhanced_Linux-Confining_Users-xguest_Kiosk_Mode.html" title="6.5. xguest: Kiosk Mode" /></head><body class="toc_embeded "><di
 v id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Confining_Users-Confining_Existing_Linux_Users_semanage_login.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Confining_Users-xguest_Kiosk_Mode.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="6.4. Changing the Default Mapping" id="sect-Security-Enhanced_Linux-Confining_Users-Changing_the_Default_Mapping"><div class="titlepage"><div><div keep-together.wi
 thin-column="always"><h2 class="title">6.4. Changing the Default Mapping</h2></div></div></div><div class="para">
-			In Fedora 11, Linux users are mapped to the SELinux <code class="computeroutput">__default__</code> login by default (which is mapped to the SELinux <code class="computeroutput">unconfined_u</code> user). If you would like new Linux users, and Linux users not specifically mapped to an SELinux user to be confined by default, change the default mapping with the <code class="command">semanage login</code> command.
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.4. Cambiando el Mapeo Predeterminado</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Confining_Users.html" title="Capítulo 6. Confinando a los Usuarios" /><link rel="prev" href="sect-Security-Enhanced_Linux-Confining_Users-Confining_Existing_Linux_Users_semanage_login.html" title="6.3. Confinando Usuarios Linux Existentes: semanage login" /><link rel="next" href="sect-Security-Enhanced_Linux-Confining_Users-xguest_Kiosk_Mode.html" title="6.5. xguest: Modo Kiosk" /></head><bod
 y class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Confining_Users-Confining_Existing_Linux_Users_semanage_login.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Confining_Users-xguest_Kiosk_Mode.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="6.4. Cambiando el Mapeo Predeterminado" id="sect-Security-Enhanced_Linux-Confining_Users-Changing_the_Default_Mapping"><div class="titlep
 age"><div><div keep-together.within-column="always"><h2 class="title">6.4. Cambiando el Mapeo Predeterminado</h2></div></div></div><div class="para">
+			En Fedora 11, los usuarios Linux se mapean al ingreso SELinux <code class="computeroutput">__default__</code> por defecto (que se mapea al usuario SELinux <code class="computeroutput">unconfined_u</code>). Si quiere que los usuarios nuevos de Linux y los usuarios Linux no mapeados específicamente a un usuario SELinux sean confinados por defecto, cambie el mapeo predeterminado con el comando <code class="command">semanage login</code>.
 		</div><div class="para">
-			For example, run the following command as the Linux root user to change the default mapping from <code class="computeroutput">unconfined_u</code> to <code class="computeroutput">user_u</code>:
+			Por ejemplo, corra el siguiente comando como usuario root de Linux para cambiar el mapeo predeterminado de <code class="computeroutput">unconfined_u</code> a <code class="computeroutput">user_u</code>:
 		</div><div class="para">
 			<code class="command">/usr/sbin/semanage login -m -S targeted -s "user_u" -r s0 __default__</code>
 		</div><div class="para">
-			Run the <code class="command">semanage login -l</code> command as the Linux root user to verify the <code class="computeroutput">__default__</code> login is mapped to <code class="computeroutput">user_u</code>:
+			Corra el comando <code class="command">semanage login -l</code> como usuario root de Linux para verificar que el ingreso <code class="computeroutput">__default__</code> se mapea a <code class="computeroutput">user_u</code>:
 		</div><pre class="screen">
 # /usr/sbin/semanage login -l
 
@@ -18,9 +18,9 @@ root                      unconfined_u              s0-s0:c0.c1023
 system_u                  system_u                  s0-s0:c0.c1023
 
 </pre><div class="para">
-			If a new Linux user is created and an SELinux user is not specified, or if an existing Linux user logs in and does not match a specific entry from the <code class="command">semanage login -l</code> output, they are mapped to <code class="computeroutput">user_u</code>, as per the <code class="computeroutput">__default__</code> login.
+			Si un usuario Linux nuevo se crea y el usuario SELinux no se especifica, o si un usuario Linux existente ingresa y no coincide una entrada específica de la salida de <code class="command">semanage login -l</code>, se mapean a <code class="computeroutput">user_u</code>, según el ingreso <code class="computeroutput">__default__</code>.
 		</div><div class="para">
-			To change back to the default behavior, run the following command as the Linux root user to map the <code class="computeroutput">__default__</code> login to the SELinux <code class="computeroutput">unconfined_u</code> user:
+			Para volver al comportamiento predeterminado, corra el siguiente comando como usuario root de Linux para mapear el ingreso <code class="computeroutput">__default__</code> al usuario SELinux <code class="computeroutput">unconfined_u</code>:
 		</div><div class="para">
 			
 <pre class="screen">/usr/sbin/semanage login -m -S targeted -s "unconfined_u" -r\
@@ -28,4 +28,4 @@ s0-s0:c0.c1023 __default__
 
 </pre>
 
-		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Confining_Users-Confining_Existing_Linux_Users_semanage_login.html"><strong>Anterior</strong>6.3. Confining Existing Linux Users: semanage log...</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Confining_Users-xguest_Kiosk_Mode.html"><strong>Siguiente</strong>6.5. xguest: Kiosk Mode</a></li></ul></body></html>
+		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Confining_Users-Confining_Existing_Linux_Users_semanage_login.html"><strong>Anterior</strong>6.3. Confinando Usuarios Linux Existentes: semana...</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Confining_Users-xguest_Kiosk_Mode.html"><strong>Siguiente</strong>6.5. xguest: Modo Kiosk</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Confining_Users-Confining_Existing_Linux_Users_semanage_login.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Confining_Users-Confining_Existing_Linux_Users_semanage_login.html
index 38875fb..36c238d 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Confining_Users-Confining_Existing_Linux_Users_semanage_login.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Confining_Users-Confining_Existing_Linux_Users_semanage_login.html
@@ -1,9 +1,9 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.3. Confining Existing Linux Users: semanage login</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="chap-Security-Enhanced_Linux-Confining_Users.html" title="Capítulo 6. Confining Users" /><link rel="prev" href="sect-Security-Enhanced_Linux-Confining_Users-Confining_New_Linux_Users_useradd.html" title="6.2. Confining New Linux Users: useradd" /><link rel="next" href="sect-Security-Enhanced_Linux-Confining_Users-Changing_the_Default_Mapping.html" title="6.4. Changing the Default Mapping" /></head><body class="to
 c_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Confining_Users-Confining_New_Linux_Users_useradd.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Confining_Users-Changing_the_Default_Mapping.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="6.3. Confining Existing Linux Users: semanage login" id="sect-Security-Enhanced_Linux-Confining_Users-Confining_Existing_Linux_Users_semanage_login">
 <div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.3. Confining Existing Linux Users: semanage login</h2></div></div></div><div class="para">
-			If a Linux user is mapped to the SELinux <code class="computeroutput">unconfined_u</code> user (the default behavior), and you would like to change which SELinux user they are mapped to, use the <code class="command">semanage login</code> command. The following example creates a new Linux user named newuser, then maps that Linux user to the SELinux <code class="computeroutput">user_u</code> user:
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.3. Confinando Usuarios Linux Existentes: semanage login</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Confining_Users.html" title="Capítulo 6. Confinando a los Usuarios" /><link rel="prev" href="sect-Security-Enhanced_Linux-Confining_Users-Confining_New_Linux_Users_useradd.html" title="6.2. Confinando Usuarios Nuevos de Linux: useradd" /><link rel="next" href="sect-Security-Enhanced_Linux-Confining_Users-Changing_the_Default_Mapping.html" title="6.4. Cambiando el Mapeo Pred
 eterminado" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Confining_Users-Confining_New_Linux_Users_useradd.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Confining_Users-Changing_the_Default_Mapping.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="6.3. Confinando Usuarios Linux Existentes: semanage login" id="sect-Security-Enhanced_Linux-Confining_Users-Confi
 ning_Existing_Linux_Users_semanage_login"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.3. Confinando Usuarios Linux Existentes: semanage login</h2></div></div></div><div class="para">
+			Si un usuario Linux se mapea al usuario <code class="computeroutput">unconfined_u</code> (el comportamiento predeterminado), y desea cambiar le usuario SELinux al que se mapea, use el comando <code class="command">semanage login</code>. El siguiente ejemplo crea un usuario de Linux nuevo llamado usuarionuevo, luego lo mapea al usuario SELinux <code class="computeroutput">user_u</code>:
 		</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
-					As the Linux root user, run the <code class="command">/usr/sbin/useradd newuser</code> command to create a new Linux user (newuser). Since this user uses the default mapping, it does not appear in the <code class="command">/usr/sbin/semanage login -l</code> output:
+					Como usuario root de Linux, ejecute el comando <code class="command">/usr/sbin/useradd usuarionuevo</code> para crear un nuevo usuario (usuarionuevo). Dado que este usuario usa el mapeo por defecto, no aparece en la salida de <code class="command">/usr/sbin/semanage login -l</code>:
 				</div><pre class="screen">
 # /usr/sbin/semanage login -l
 
@@ -14,13 +14,13 @@ root                      unconfined_u              s0-s0:c0.c1023
 system_u                  system_u                  s0-s0:c0.c1023
 
 </pre></li><li class="listitem"><div class="para">
-					To map the Linux newuser user to the SELinux <code class="computeroutput">user_u</code> user, run the following command as the Linux root user:
+					Para mapear un usuario usuarionuevo de Linux al usuario <code class="computeroutput">user_u</code> de SELinux, corra el siguiente comando como usuario root de Linux:
 				</div><div class="para">
 					<code class="command">/usr/sbin/semanage login -a -s user_u newuser</code>
 				</div><div class="para">
-					The <code class="option">-a</code> option adds a new record, and the <code class="option">-s</code> option specifies the SELinux user to map a Linux user to. The last argument, <code class="computeroutput">newuser</code>, is the Linux user you want mapped to the specified SELinux user.
+					La opción <code class="option">-a</code> agrega un registro nuevo y la opción <code class="option">-s</code> especifica el usuario SELinux al que mapea el usuario Linux. El último argumento <code class="computeroutput">usuarionuevo</code>, es el usuario Linux al que quiere que se mapee el usuario SELinux especificado.
 				</div></li><li class="listitem"><div class="para">
-					To view the mapping between the Linux newuser user and <code class="computeroutput">user_u</code>, run the <code class="command">semanage login -l</code> command as the Linux root user:
+					Para ver el mapeo entre el usuario usarionuevo de Linux y <code class="computeroutput">user_u</code>, corra el comando <code class="command">semanage login -l</code> como usuario root de Linux:
 				</div><pre class="screen">
 # /usr/sbin/semanage login -l
 
@@ -41,13 +41,13 @@ Retype new UNIX password: <em class="replaceable"><code>Enter the same password
 passwd: all authentication tokens updated successfully.
 
 </pre></li><li class="listitem"><div class="para">
-					Log out of your current session, and log in as the Linux newuser user. Run the <code class="command">id -Z</code> command to view the newuser's SELinux context:
+					Salga de su sesión actual e ingrese como el usuario de Linux usuarionuevo. Corra el comando <code class="command">id -Z</code> para ver el contexto SELinux de usuarionuevo:
 				</div><pre class="screen">
 [newuser at rlocalhost ~]$ id -Z
 user_u:user_r:user_t:s0
 
 </pre></li><li class="listitem"><div class="para">
-					Log out of the Linux newuser's session, and log back in with your account. If you do not want the Linux newuser user, run the <code class="command">userdel -r newuser</code> command as the Linux root user to remove it, along with its home directory. Also, the mapping between the Linux newuser user and <code class="computeroutput">user_u</code> is removed:
+					Salga de la sesión de Linux del usuarionuevo y vuelva a ingresar en su cuenta. Si no quiere el usuarionuevo de Linux, corra el comando <code class="command">userdel -r usuarionuevo</code> como usuario root de Linux, junto con su directorio de inicio. También, el mapeo del usuario Linux usuarionuevo y <code class="computeroutput">user_u</code> se elimina:
 				</div><pre class="screen">
 # /usr/sbin/userdel -r newuser
 # /usr/sbin/semanage login -l
@@ -58,4 +58,4 @@ __default__               unconfined_u              s0-s0:c0.c1023
 root                      unconfined_u              s0-s0:c0.c1023
 system_u                  system_u                  s0-s0:c0.c1023
 
-</pre></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Confining_Users-Confining_New_Linux_Users_useradd.html"><strong>Anterior</strong>6.2. Confining New Linux Users: useradd</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Confining_Users-Changing_the_Default_Mapping.html"><strong>Siguiente</strong>6.4. Changing the Default Mapping</a></li></ul></body></html>
+</pre></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Confining_Users-Confining_New_Linux_Users_useradd.html"><strong>Anterior</strong>6.2. Confinando Usuarios Nuevos de Linux: useradd</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Confining_Users-Changing_the_Default_Mapping.html"><strong>Siguiente</strong>6.4. Cambiando el Mapeo Predeterminado</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Confining_Users-Confining_New_Linux_Users_useradd.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Confining_Users-Confining_New_Linux_Users_useradd.html
index 2e8b785..e9d0d98 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Confining_Users-Confining_New_Linux_Users_useradd.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Confining_Users-Confining_New_Linux_Users_useradd.html
@@ -1,19 +1,19 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.2. Confining New Linux Users: useradd</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="chap-Security-Enhanced_Linux-Confining_Users.html" title="Capítulo 6. Confining Users" /><link rel="prev" href="chap-Security-Enhanced_Linux-Confining_Users.html" title="Capítulo 6. Confining Users" /><link rel="next" href="sect-Security-Enhanced_Linux-Confining_Users-Confining_Existing_Linux_Users_semanage_login.html" title="6.3. Confining Existing Linux Users: semanage login" /></head><body class="toc_embeded "><div id="t
 ocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-Confining_Users.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Confining_Users-Confining_Existing_Linux_Users_semanage_login.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="6.2. Confining New Linux Users: useradd" id="sect-Security-Enhanced_Linux-Confining_Users-Confining_New_Linux_Users_useradd"><div class="titlepage"><div><div keep-together.within-column="a
 lways"><h2 class="title">6.2. Confining New Linux Users: useradd</h2></div></div></div><div class="para">
-			Linux users mapped to the SELinux <code class="computeroutput">unconfined_u</code> user run in the <code class="computeroutput">unconfined_t</code> domain. This is seen by running the <code class="command">id -Z</code> command while logged-in as a Linux user mapped to <code class="computeroutput">unconfined_u</code>:
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.2. Confinando Usuarios Nuevos de Linux: useradd</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Confining_Users.html" title="Capítulo 6. Confinando a los Usuarios" /><link rel="prev" href="chap-Security-Enhanced_Linux-Confining_Users.html" title="Capítulo 6. Confinando a los Usuarios" /><link rel="next" href="sect-Security-Enhanced_Linux-Confining_Users-Confining_Existing_Linux_Users_semanage_login.html" title="6.3. Confinando Usuarios Linux Existentes: semanage login" /></h
 ead><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-Confining_Users.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Confining_Users-Confining_Existing_Linux_Users_semanage_login.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="6.2. Confinando Usuarios Nuevos de Linux: useradd" id="sect-Security-Enhanced_Linux-Confining_Users-Confining_New_Linux_Users_useradd"><div class="
 titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.2. Confinando Usuarios Nuevos de Linux: useradd</h2></div></div></div><div class="para">
+			Los usuarios Linux mapeados al usuario SELinux <code class="computeroutput">unconfined_u</code> corren en el dominio <code class="computeroutput">unconfined_t</code>. Esto se ve ejecutando el comando <code class="command">id -Z</code> luego de haber ingresado como el usuario Linux que se mapea a <code class="computeroutput">unconfined_u</code>:
 		</div><pre class="screen">
 $ id -Z
 unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
 
 </pre><div class="para">
-			When Linux users run in the <code class="computeroutput">unconfined_t</code> domain, SELinux policy rules are applied, but policy rules exist that allow Linux users running in the <code class="computeroutput">unconfined_t</code> domain almost all access. If unconfined Linux users execute an application that SELinux policy defines can transition from the <code class="computeroutput">unconfined_t</code> domain to its own confined domain, unconfined Linux users are still subject to the restrictions of that confined domain. The security benefit of this is that, even though a Linux user is running unconfined, the application remains confined, and therefore, the exploitation of a flaw in the application can be limited by policy. Note: this does not protect the system from the user. Instead, the user and the system are being protected from possible damage caused by a flaw in the application.
+			Cuando los usuarios linux ejecuten en el dominio <code class="computeroutput">unconfined_t</code>, se aplican las reglas de la política de SELinux, pero las reglas de políticas que existen para usuarios Linux que corren en el dominio <code class="computeroutput">unconfined_t</code> permiten casi todos los accesos. Si los usuarios Linux no confinados ejecutan una aplicación que la política de SELinux define pueden transicionar desde el dominio <code class="computeroutput">unconfined_t</code> a su propio dominio confinado, los usuarios Linux no confinados todavía pueden ser sujetos a restricciones del dominio confinado. El beneficio de seguridad de esto es que, aunque el usuario Linux corre en un dominio confinado, la aplicación permanece confinada, y por lo tanto, la explotación de una brecha en la aplicación se puede limitar por la política. Nota: esto no protege al sistema del usuario. En su lugar, el usuario y el sistema están siendo protegido de posibles dañ
 os causados en alguna debilidad en la aplicación.
 		</div><div class="para">
-			When creating Linux users with <code class="command">useradd</code>, use the <code class="option">-Z</code> option to specify which SELinux user they are mapped to. The following example creates a new Linux user, useruuser, and maps that user to the SELinux <code class="computeroutput">user_u</code> user. Linux users mapped to the SELinux <code class="computeroutput">user_u</code> user run in the <code class="computeroutput">user_t</code> domain. In this domain, Linux users are unable to run setuid applications unless SELinux policy permits it (such as <code class="command">passwd</code>), and can not run <code class="command">su</code> or <code class="command">sudo</code>, preventing them from becoming the Linux root user with these commands.
+			Cuando se crean usuarios LInux con <code class="command">useradd</code>, use la opción <code class="option">-Z</code> para especificar a qué usuario SELinux se debe mapear. El siguiente ejemplo crea un usuario Linux nuevo, useruuser, y mapea ese usuario al usuario SELinux <code class="computeroutput">user_u</code>. Los usuarios Linux mapeados al usuario SELinux <code class="computeroutput">user_u</code> corren en el dominio <code class="computeroutput">user_t</code>. En este dominio, los usuarios Linux no pueden correr aplicaciones setuid a menos que la política de SELinux lo permita (tal como <code class="command">passwd</code>), y tampoco pueden correr <code class="command">su</code> o <code class="command">sudo</code>, lo que evita que se puedan volver usuarios root de Linux con estos comandos.
 		</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
-					As the Linux root user, run the <code class="command">/usr/sbin/useradd -Z user_u useruuser</code> command to create a new Linux user (useruuser) that is mapped to the SELinux <code class="computeroutput">user_u</code> user.
+					Como usuario root de Linux, corra el comando <code class="command">/usr/sbin/useradd -Z user_u useruuser</code> para crear el usuario Linux nuevo (useruuser) que se mapeará al usuario SELinux <code class="computeroutput">user_u</code>.
 				</div></li><li class="listitem"><div class="para">
-					As the Linux root user, run the <code class="command">semanage login -l</code> command to view the mapping between the Linux <code class="computeroutput">useruuser</code> user and <code class="computeroutput">user_u</code>:
+					Como usuario root de Linux, corra el comando <code class="command">semanage login -l</code> para ver el mapeo entre el usuario Linux <code class="computeroutput">useruuser</code> y <code class="computeroutput">user_u</code>:
 				</div><pre class="screen">
 # /usr/sbin/semanage login -l
 
@@ -25,7 +25,7 @@ system_u                  system_u                  s0-s0:c0.c1023
 useruuser                 user_u                    s0
 
 </pre></li><li class="listitem"><div class="para">
-					As the Linux root user, run the <code class="command">passwd useruuser</code> command to assign a password to the Linux useruuser user:
+					Como usuario root de Linux, corra el comando <code class="command">passwd useruuser</code> para asignar una contraseña para el usuario useruuser de Linux:
 				</div><pre class="screen">
 # passwd useruuser
 Changing password for user useruuser.
@@ -34,11 +34,11 @@ Retype new UNIX password: <em class="replaceable"><code>Enter the same password
 passwd: all authentication tokens updated successfully.
 
 </pre></li><li class="listitem"><div class="para">
-					Log out of your current session, and log in as the Linux useruuser user. When you log in, pam_selinux maps the Linux user to an SELinux user (in this case, <code class="computeroutput">user_u</code>), and sets up the resulting SELinux context. The Linux user's shell is then launched with this context. Run the <code class="command">id -Z</code> command to view the context of a Linux user:
+					Salga de su sesión actual, e ingrese como el usuario useruuser de Linux. Cuando ingrese, pam_selinux mapea el usuario Linux a un usuario SELinux (en este caso, <code class="computeroutput">user_u</code>), y configura el contexto SELinux resultante. El shell del usuario Linux es luego lanzado con este contexto. Corra el comando <code class="command">id -Z</code> para ver el contexto de un usuario Linux:
 				</div><pre class="screen">
 [useruuser at localhost ~]$ id -Z
 user_u:user_r:user_t:s0
 
 </pre></li><li class="listitem"><div class="para">
-					Log out of the Linux useruuser's session, and log back in with your account. If you do not want the Linux useruuser user, run the <code class="command">/usr/sbin/userdel -r useruuser</code> command as the Linux root user to remove it, along with its home directory.
-				</div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-Confining_Users.html"><strong>Anterior</strong>Capítulo 6. Confining Users</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Confining_Users-Confining_Existing_Linux_Users_semanage_login.html"><strong>Siguiente</strong>6.3. Confining Existing Linux Users: semanage log...</a></li></ul></body></html>
+					Salga de la sesión useruuser de Linux, y vuelva a ingresar en su cuenta. Si no quiere el usuario useruuser, ejecute el comando <code class="command">/usr/sbin/userdel -r useruuser</code> como usuario root de Linux para borrarlo junto con su directorio de inicio.
+				</div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-Confining_Users.html"><strong>Anterior</strong>Capítulo 6. Confinando a los Usuarios</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Confining_Users-Confining_Existing_Linux_Users_semanage_login.html"><strong>Siguiente</strong>6.3. Confinando Usuarios Linux Existentes: semana...</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Confining_Users-xguest_Kiosk_Mode.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Confining_Users-xguest_Kiosk_Mode.html
index bc81671..2e008b1 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Confining_Users-xguest_Kiosk_Mode.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Confining_Users-xguest_Kiosk_Mode.html
@@ -1,19 +1,19 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.5. xguest: Kiosk Mode</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="chap-Security-Enhanced_Linux-Confining_Users.html" title="Capítulo 6. Confining Users" /><link rel="prev" href="sect-Security-Enhanced_Linux-Confining_Users-Changing_the_Default_Mapping.html" title="6.4. Changing the Default Mapping" /><link rel="next" href="sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications.html" title="6.6. Booleans for Users Executing Applications" /></head><body class="toc_embeded "><
 div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Confining_Users-Changing_the_Default_Mapping.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="6.5. xguest: Kiosk Mode" id="sect-Security-Enhanced_Linux-Confining_Users-xguest_Kiosk_Mode"><div class="titlepage"><div><div keep-together.within-column=
 "always"><h2 class="title">6.5. xguest: Kiosk Mode</h2></div></div></div><div class="para">
-			The <span class="package">xguest</span> package provides a kiosk user account. This account is used to secure machines that people walk up to and use, such as those at libraries, banks, airports, information kiosks, and coffee shops. The kiosk user account is very locked down: essentially, it only allows users to log in and use <span class="application"><strong>Firefox</strong></span> to browse Internet websites. Any changes made while logged in with his account, such as creating files or changing settings, are lost when you log out.
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.5. xguest: Modo Kiosk</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Confining_Users.html" title="Capítulo 6. Confinando a los Usuarios" /><link rel="prev" href="sect-Security-Enhanced_Linux-Confining_Users-Changing_the_Default_Mapping.html" title="6.4. Cambiando el Mapeo Predeterminado" /><link rel="next" href="sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications.html" title="6.6. Booleanos para que los Usuarios Ejecuten Aplicaciones" /></h
 ead><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Confining_Users-Changing_the_Default_Mapping.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="6.5. xguest: Modo Kiosk" id="sect-Security-Enhanced_Linux-Confining_Users-xguest_Kiosk_Mode"><div class="titlepage"><div><
 div keep-together.within-column="always"><h2 class="title">6.5. xguest: Modo Kiosk</h2></div></div></div><div class="para">
+			El paquete <span class="package">xguest</span> provee una cuenta de usuario kiosk. Esta cuenta se usa para asegurar máquinas a las que ingresan personas y las usan, como las de las bibliotecas, bancos, aeropuertos, quioscos de información y cyber cafés. La cuenta de usuario kiosk está muy bloqueada: escencialmente, s´olo permite a los usuarios ingresar y usar <span class="application"><strong>Firefox</strong></span> para navegar sitios de Internet. Cualquier cambio hecho mientras se ingresó con esa cuenta, tal como la creación y cambio de la configuración, se pierde cuando se sale.
 		</div><div class="para">
-			To set up the kiosk account:
+			Para configurar la cuenta kiosk:
 		</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
-					As the Linux root user, run <code class="command">yum install xguest</code> command to install the <span class="package">xguest</span> package. Install dependencies as required.
+					Como usuario root de Linux, corra el comando <code class="command">yum install xguest</code> para instalar el paquete <span class="package">xguest</span>. Instale las dependencias requeridas.
 				</div></li><li class="listitem"><div class="para">
-					In order to allow the kiosk account to be used by a variety of people, the account is not password-protected, and as such, the account can only be protected if SELinux is running in enforcing mode. Before logging in with this account, use the <code class="command">getenforce</code> command to confirm that SELinux is running in enforcing mode:
+					Para permitir a la cuenta kiosk usarse para una variedad de personas, la cuenta no se protege con contraseña, y como tal, la cuenta sólo se puede proteger si SELinux está funcionando en modo obediente. Antes de ingresar con esta cuenta, use el comando <code class="command">getenforce</code> para confirmar que SELinux está funcionando en modo obediente:
 				</div><pre class="screen">
 $ /usr/sbin/getenforce
 Enforcing
 
 </pre><div class="para">
-					If this is not the case, refer to <a class="xref" href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes.html" title="5.5. SELinux Modes">Sección 5.5, “SELinux Modes”</a> for information about changing to enforcing mode. It is not possible to log in with this account if SELinux is in permissive mode or disabled.
+					If this is not the case, refer to <a class="xref" href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes.html" title="5.5. Modos de SELinux">Sección 5.5, “Modos de SELinux”</a> for information about changing to enforcing mode. It is not possible to log in with this account if SELinux is in permissive mode or disabled.
 				</div></li><li class="listitem"><div class="para">
-					You can only log in to this account via the GNOME Display Manager (GDM). Once the <span class="package">xguest</span> package is installed, a <code class="computeroutput">Guest</code> account is added to GDM. To log in, click on the <code class="computeroutput">Guest</code> account:
-				</div><div class="mediaobject"><img src="./images/xguest.png" /></div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Confining_Users-Changing_the_Default_Mapping.html"><strong>Anterior</strong>6.4. Changing the Default Mapping</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications.html"><strong>Siguiente</strong>6.6. Booleans for Users Executing Applications</a></li></ul></body></html>
+					Solamente puede ingresar a esta cuenta a través del Administración de Pantalla de GNOME (GDM). Una vez que el paquete <span class="package">xguest</span> se instala, se agrega una cuenta <code class="computeroutput">Invitado</code> a GDM. Para ingresar, haga clic en la cuenta <code class="computeroutput">Invitado</code>:
+				</div><div class="mediaobject"><img src="./images/xguest.png" /></div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Confining_Users-Changing_the_Default_Mapping.html"><strong>Anterior</strong>6.4. Cambiando el Mapeo Predeterminado</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications.html"><strong>Siguiente</strong>6.6. Booleanos para que los Usuarios Ejecuten Apl...</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux.html
index 1e3322d..1e767c8 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux.html
@@ -1,7 +1,7 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.4.2. Disabling SELinux</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html" title="5.4. Enabling and Disabling SELinux" /><link rel="prev" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html" title="5.4. Enabling and Disabling SELinux" /><link rel="next" href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes.html" title="5.5. SELinux Modes" /></head><body class="toc_embeded "
 ><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.4.2. Disabling SELinux" id="sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux"><div class="titlepage"><div><div keep-together.within-colum
 n="always"><h3 class="title">5.4.2. Disabling SELinux</h3></div></div></div><div class="para">
-				To disable SELinux, configure <code class="option">SELINUX=disabled</code> in <code class="filename">/etc/selinux/config</code>:
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.4.2. Deshabilitando SELinux</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html" title="5.4. Habilitando y Deshabilitando SELinux" /><link rel="prev" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html" title="5.4. Habilitando y Deshabilitando SELinux" /><link rel="next" href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes.html" title="5.5. Modos de SELinux" /></head><
 body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.4.2. Deshabilitando SELinux" id="sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux"><div class="titlepage"><div><
 div keep-together.within-column="always"><h3 class="title">5.4.2. Deshabilitando SELinux</h3></div></div></div><div class="para">
+				Para deshabilitar SELinux, configure <code class="option">SELINUX=disabled</code> en <code class="filename">/etc/selinux/config</code>:
 			</div><pre class="screen"># This file controls the state of SELinux on the system.
 # SELINUX= can take one of these three values:
 #       enforcing - SELinux security policy is enforced.
@@ -14,8 +14,8 @@ SELINUX=disabled
 SELINUXTYPE=targeted
 
 </pre><div class="para">
-				Reboot your system. After reboot, confirm that the <code class="command">getenforce</code> command returns <code class="computeroutput">Disabled</code>:
+				Reinicie su sistema. Después de reiniciar, confirme que <code class="command">getenforce</code> devuelve <code class="computeroutput">Disabled</code>:
 			</div><pre class="screen">$ /usr/sbin/getenforce
 Disabled
 
-</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html"><strong>Anterior</strong>5.4. Enabling and Disabling SELinux</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes.html"><strong>Siguiente</strong>5.5. SELinux Modes</a></li></ul></body></html>
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html"><strong>Anterior</strong>5.4. Habilitando y Deshabilitando SELinux</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes.html"><strong>Siguiente</strong>5.5. Modos de SELinux</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow.html
index 920ffd6..6f7fc46 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow.html
@@ -1,22 +1,22 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.3.8. Allowing Access: audit2allow</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html" title="7.3. Fixing Problems" /><link rel="prev" href="sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages.html" title="7.3.7. sealert Messages" /><link rel="next" href="chap-Security-Enhanced_Linux-Further_Information.html" title="Capítulo 8. Further Information" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" clas
 s="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-Further_Information.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="7.3.8. Allowing Access: audit2allow" id="sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.3.8. Allowing Access: audit2allow</h3></div></div></d
 iv><div class="para">
-				Do not use the example in this section in production. It is used only to demonstrate the use of <code class="command">audit2allow</code>.
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.3.8. Permitiendo el Acceso: audit2allow</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html" title="7.3. Corrección de Problemas" /><link rel="prev" href="sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages.html" title="7.3.7. Mensajes sealert" /><link rel="next" href="chap-Security-Enhanced_Linux-Further_Information.html" title="Capítulo 8. Información Adicional" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><if
 rame id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-Further_Information.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="7.3.8. Permitiendo el Acceso: audit2allow" id="sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.3.8. Permitiendo el Acce
 so: audit2allow</h3></div></div></div><div class="para">
+				No use el ejemplo en esta sección en producción. Se usa sólo para mostrar el uso de <code class="command">audit2allow</code>.
 			</div><div class="para">
-				From the <span class="citerefentry"><span class="refentrytitle">audit2allow</span>(1)</span> manual page: "<code class="command">audit2allow</code> - generate SELinux policy allow rules from logs of denied operations"<sup>[<a id="id1599053" href="#ftn.id1599053" class="footnote">19</a>]</sup>. After analyzing denials as per <a class="xref" href="sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages.html" title="7.3.7. sealert Messages">Sección 7.3.7, “sealert Messages”</a>, and if no label changes or Booleans allowed access, use <code class="command">audit2allow</code> to create a local policy module. After access is denied by SELinux, running the <code class="command">audit2allow</code> command presents Type Enforcement rules that allow the previously denied access.
+				From the <span class="citerefentry"><span class="refentrytitle">audit2allow</span>(1)</span> manual page: "<code class="command">audit2allow</code> - generate SELinux policy allow rules from logs of denied operations"<sup>[<a id="id810788" href="#ftn.id810788" class="footnote">19</a>]</sup>. After analyzing denials as per <a class="xref" href="sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages.html" title="7.3.7. Mensajes sealert">Sección 7.3.7, “Mensajes sealert”</a>, and if no label changes or Booleans allowed access, use <code class="command">audit2allow</code> to create a local policy module. After access is denied by SELinux, running the <code class="command">audit2allow</code> command presents Type Enforcement rules that allow the previously denied access.
 			</div><div class="para">
-				The following example demonstrates using <code class="command">audit2allow</code> to create a policy module:
+				El siguiente ejemplo muestra el uso de <code class="command">audit2allow</code> para crear un módulo de política:
 			</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
-						A denial and the associated system call are logged to <code class="filename">/var/log/audit/audit.log</code>:
+						Una negación y la llamada al sistema asociado se graban en <code class="filename">/var/log/audit/audit.log</code>:
 					</div><pre class="screen">
 type=AVC msg=audit(1226270358.848:238): avc:  denied  { write } for  pid=13349 comm="certwatch" name="cache" dev=dm-0 ino=218171 scontext=system_u:system_r:certwatch_t:s0 tcontext=system_u:object_r:var_t:s0 tclass=dir
 
 type=SYSCALL msg=audit(1226270358.848:238): arch=40000003 syscall=39 success=no exit=-13 a0=39a2bf a1=3ff a2=3a0354 a3=94703c8 items=0 ppid=13344 pid=13349 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="certwatch" exe="/usr/bin/certwatch" subj=system_u:system_r:certwatch_t:s0 key=(null)
 
 </pre><div class="para">
-						In this example, <span class="application"><strong>certwatch</strong></span> (<code class="computeroutput">comm="certwatch"</code>) was denied write access (<code class="computeroutput">{ write }</code>) to a directory labeled with the <code class="computeroutput">var_t</code> type (<code class="computeroutput">tcontext=system_u:object_r:var_t:s0</code>). Analyze the denial as per <a class="xref" href="sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages.html" title="7.3.7. sealert Messages">Sección 7.3.7, “sealert Messages”</a>. If no label changes or Booleans allowed access, use <code class="command">audit2allow</code> to create a local policy module.
+						In this example, <span class="application"><strong>certwatch</strong></span> (<code class="computeroutput">comm="certwatch"</code>) was denied write access (<code class="computeroutput">{ write }</code>) to a directory labeled with the <code class="computeroutput">var_t</code> type (<code class="computeroutput">tcontext=system_u:object_r:var_t:s0</code>). Analyze the denial as per <a class="xref" href="sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages.html" title="7.3.7. Mensajes sealert">Sección 7.3.7, “Mensajes sealert”</a>. If no label changes or Booleans allowed access, use <code class="command">audit2allow</code> to create a local policy module.
 					</div></li><li class="listitem"><div class="para">
-						With a denial logged, such as the <code class="computeroutput">certwatch</code> denial in step 1, run the <code class="command">audit2allow -w -a</code> command to produce a human-readable description of why access was denied. The <code class="option">-a</code> option causes all audit logs to be read. The <code class="option">-w</code> option produces the human-readable description. The <code class="command">audit2allow</code> tool accesses <code class="filename">/var/log/audit/audit.log</code>, and as such, must be run as the Linux root user:
+						Con una negación grabada, tal como la negación de <code class="computeroutput">certwatch</code> en el paso 1, corra el comando <code class="command">audit2allow -w -a</code> para producir una descripción legible al humano sobre por qué el acceso fue negado. La opción <code class="option">-a</code> hace que se lean todos los registros de autidoría. La opción <code class="option">-w</code> produce una descripción legible al humano. La herramienta <code class="command">audit2allow</code> accede a <code class="filename">/var/log/audit/audit.log</code>, y como tal, debe ser ejecutada como usuario root de Linux:
 					</div><pre class="screen">
 # audit2allow -w -a
 type=AVC msg=audit(1226270358.848:238): avc:  denied  { write } for  pid=13349 comm="certwatch" name="cache" dev=dm-0 ino=218171 scontext=system_u:system_r:certwatch_t:s0 tcontext=system_u:object_r:var_t:s0 tclass=dir
@@ -26,9 +26,9 @@ type=AVC msg=audit(1226270358.848:238): avc:  denied  { write } for  pid=13349 c
 	You can use audit2allow to generate a loadable module to allow this access.
 
 </pre><div class="para">
-						As shown, access was denied due to a missing Type Enforcement rule.
+						Como se muestra, el acceso fue negado debido a que falta una regla de Obligación de Tipo.
 					</div></li><li class="listitem"><div class="para">
-						Run the <code class="command">audit2allow -a</code> command to view the Type Enforcement rule that allows the denied access:
+						Ejecute el comando <code class="command">audit2allow -a</code> para ver la regla de Obligación de Tipo que permite el acceso negado:
 					</div><pre class="screen">
 # audit2allow -a
 
@@ -37,9 +37,9 @@ type=AVC msg=audit(1226270358.848:238): avc:  denied  { write } for  pid=13349 c
 allow certwatch_t var_t:dir write;
 
 </pre><div class="important"><h2>Importante</h2><div class="para">
-							Missing Type Enforcement rules are usually caused by bugs in SELinux policy, and should be reported in <a href="https://bugzilla.redhat.com/">Red Hat Bugzilla</a>. For Fedora, create bugs against the <code class="computeroutput">Fedora</code> product, and select the <code class="computeroutput">selinux-policy</code> component. Include the output of the <code class="command">audit2allow -w -a</code> and <code class="command">audit2allow -a</code> commands in such bug reports.
+							La falta de reglas de Ejecución de Tipos son usualmente causados por errores en la política de SELinux, y deben ser informadas en el <a href="https://bugzilla.redhat.com/">Bugzilla de Red Hat</a>. Para Fedora, crear informes sobre el producto <code class="computeroutput">Fedora</code>, y seleccione el componente <code class="computeroutput">selinux-policy</code>. Incluya la salida de los comandos <code class="command">audit2allow -w -a</code> y <code class="command">audit2allow -a</code> en el informe del error.
 						</div></div></li><li class="listitem"><div class="para">
-						To use the rule displayed by <code class="command">audit2allow -a</code>, run the <code class="command">audit2allow -a -M <em class="replaceable"><code>mycertwatch</code></em></code> command as the Linux root user to create custom module. The <code class="option">-M</code> option creates a Type Enforcement file (<code class="filename">.te</code>) with the name specified with <code class="option">-M</code>, in your current working directory:
+						Para usar la regla mostrada por <code class="command">audit2allow -a</code>, ejecute el comando <code class="command">audit2allow -a -M <em class="replaceable"><code>mycertwatch</code></em></code> como usuario root de Linux. La opción <code class="option">-M</code> crea un archivo de Obligación de Tipo (<code class="filename">.te</code>) con el nombre especificado en <code class="option">-M</code>, en su directorio actual de trabajo:
 					</div><pre class="screen">
 # audit2allow -a -M mycertwatch
 
@@ -52,11 +52,11 @@ semodule -i mycertwatch.pp
 mycertwatch.pp  mycertwatch.te
 
 </pre><div class="para">
-						Also, <code class="command">audit2allow</code> compiles the Type Enforcement rule into a policy package (<code class="filename">.pp</code>). To install the module, run the <code class="command">/usr/sbin/semodule -i <em class="replaceable"><code>mycertwatch.pp</code></em></code> command as the Linux root user.
+						También, <code class="command">audit2allow</code> compila la regla de Obediencia de Tipo en un paquete de política (<code class="filename">.pp</code>). Para instalar el módulo, ejecute el comando <code class="command">/usr/sbin/semodule -i <em class="replaceable"><code>mycertwatch.pp</code></em></code> como usuario root de Linux.
 					</div><div class="important"><h2>Importante</h2><div class="para">
-							Modules created with <code class="command">audit2allow</code> may allow more access than required. It is recommended that policy created with <code class="command">audit2allow</code> be posted to an SELinux list, such as <a href="http://www.redhat.com/mailman/listinfo/fedora-selinux-list">fedora-selinux-list</a>, for review. If you believe their is a bug in policy, create a bug in <a href="https://bugzilla.redhat.com/">Red Hat Bugzilla</a>.
+							Los módulos creados con <code class="command">audit2allow</code> pueden permitir más acceso que el requerido. Se recomienda que la política creada con <code class="command">audit2allow</code> sea enviada a una lista de SELinux, tal como <a href="http://www.redhat.com/mailman/listinfo/fedora-selinux-list">fedora-selinux-list</a>, para su revisión. Si cree que hay un error en la política, informe un error en <a href="https://bugzilla.redhat.com/">Bugzilla de Red Hat</a>.
 						</div></div></li></ol></div><div class="para">
-				If you have multiple denials from multiple processes, but only want to create a custom policy for a single process, use the <code class="command">grep</code> command to narrow down the input for <code class="command">audit2allow</code>. The following example demonstrates using <code class="command">grep</code> to only send denials related to <code class="command">certwatch</code> through <code class="command">audit2allow</code>:
+				Si tiene múltiples negaciones de múltiples procesos, pero solo quiere crear una política personalizada para un proceso único, use el comando <code class="command">grep</code> para una búsqueda más refinada de <code class="command">audit2allow</code>. El siguiente ejemplo muestra el uso de <code class="command">grep</code> para sólo enviar negaciones de <code class="command">certwatch</code> a <code class="command">audit2allow</code>:
 			</div><pre class="screen">
 # grep certwatch /var/log/audit/audit.log | audit2allow -M mycertwatch2
 ******************** IMPORTANT ***********************
@@ -66,6 +66,6 @@ To make this policy package active, execute:
 
 </pre><div class="para">
 				Refer to Dan Walsh's <a href="http://danwalsh.livejournal.com/24750.html">"Using audit2allow to build policy modules. Revisited."</a> blog entry for further information about using <code class="command">audit2allow</code> to build policy modules.
-			</div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id1599053" href="#id1599053" class="para">19</a>] </sup>
+			</div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id810788" href="#id810788" class="para">19</a>] </sup>
 					From the <span class="citerefentry"><span class="refentrytitle">audit2allow</span>(1)</span> manual page, as shipped with the <span class="package">policycoreutils</span> package in Fedora 11.
-				</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages.html"><strong>Anterior</strong>7.3.7. sealert Messages</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-Further_Information.html"><strong>Siguiente</strong>Capítulo 8. Further Information</a></li></ul></body></html>
+				</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages.html"><strong>Anterior</strong>7.3.7. Mensajes sealert</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-Further_Information.html"><strong>Siguiente</strong>Capítulo 8. Información Adicional</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services.html
index 46903b7..a560fd4 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services.html
@@ -1,15 +1,15 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.3.3. Manual Pages for Services</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html" title="7.3. Fixing Problems" /><link rel="prev" href="sect-Security-Enhanced_Linux-Fixing_Problems-Possible_Causes_of_Silent_Denials.html" title="7.3.2. Possible Causes of Silent Denials" /><link rel="next" href="sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains.html" title="7.3.4. Permissive Domains" /></head><body class="toc_embeded "><div id="tocdiv"
  class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Fixing_Problems-Possible_Causes_of_Silent_Denials.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="7.3.3. Manual Pages for Services" id="sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services"><div class="titlepage"><div><div keep-together.within-column="always"><h3 cla
 ss="title">7.3.3. Manual Pages for Services</h3></div></div></div><div class="para">
-				Manual pages for services contain valuable information, such as what file type to use for a given situation, and Booleans to change the access a service has (such as <code class="systemitem">httpd</code> accessing NFS file systems). This information may be in the standard manual page, or a manual page with <code class="computeroutput">selinux</code> prepended or appended.
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.3.3. Páginas de Manual para Servicios</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html" title="7.3. Corrección de Problemas" /><link rel="prev" href="sect-Security-Enhanced_Linux-Fixing_Problems-Possible_Causes_of_Silent_Denials.html" title="7.3.2. Posibles Causas de las Negaciones Silenciosas" /><link rel="next" href="sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains.html" title="7.3.4. Dominios Permisivos" /></head><body cl
 ass="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Fixing_Problems-Possible_Causes_of_Silent_Denials.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="7.3.3. Páginas de Manual para Servicios" id="sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services"><div class="titlepage"><div><div k
 eep-together.within-column="always"><h3 class="title">7.3.3. Páginas de Manual para Servicios</h3></div></div></div><div class="para">
+				Las páginas de manual para los servicios conteniendo información valiosa, tal como qué tipo de archivo usar para una situación dada, y los Booleanos para cambiar el acceso que un servicio tiene (tal como <code class="systemitem">httpd</code> para acceder sistemas de archivos NFS). Esta información puede estar en la página de manual estándar o una página de manual con <code class="computeroutput">selinux</code> como prefijo o sufijo.
 			</div><div class="para">
-				For example, the <span class="citerefentry"><span class="refentrytitle">httpd_selinux</span>(8)</span> manual page has information about what file type to use for a given situation, as well as Booleans to allow scripts, sharing files, accessing directories inside user home directories, and so on. Other manual pages with SELinux information for services include:
+				Por ejemplo, la página de manual <span class="citerefentry"><span class="refentrytitle">httpd_selinux</span>(8)</span> tiene información sobre qué tipo de archivo usar para una situación dada, así como los Booleanos para permitir scripts, compartir archivos, acceder directorios dentro de los directorios home, y así sucesivamente. Otras páginas de manual con información de SELinux para servicios incluyen a:
 			</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-						Samba: the <span class="citerefentry"><span class="refentrytitle">samba_selinux</span>(8)</span> manual page describes that files and directories to be exported via Samba must be labeled with the <code class="computeroutput">samba_share_t</code> type, as well as Booleans to allow files labeled with types other than <code class="computeroutput">samba_share_t</code> to be exported via Samba.
+						Samba: la página de manual <span class="citerefentry"><span class="refentrytitle">samba_selinux</span>(8)</span> describe que los archivos y directorios exportar vía Samba deben ser etiquetados con el tipo <code class="computeroutput">samba_share_t</code>, así como los Booleanos para permitir archivos etiquetados con otros tipos distintos a <code class="computeroutput">samba_share_t</code> para exportarlos vía Samba.
 					</div></li><li class="listitem"><div class="para">
-						NFS: the <span class="citerefentry"><span class="refentrytitle">nfs_selinux</span>(8)</span> manual page describes that, by default, file systems can not be exported via NFS, and that to allow file systems to be exported, Booleans such as <code class="computeroutput">nfs_export_all_ro</code> or <code class="computeroutput">nfs_export_all_rw</code> must be turned on.
+						NFS: la página de manual <span class="citerefentry"><span class="refentrytitle">nfs_selinux</span>(8)</span> describe que, por defecto, los sistemas de archivo no se pueden exportar vía NFS, y que no se permite exportar sistemas de archivos. Los Booleanos como <code class="computeroutput">nfs_export_all_ro</code> o <code class="computeroutput">nfs_export_all_rw</code> deben activarse.
 					</div></li><li class="listitem"><div class="para">
-						Berkeley Internet Name Domain (BIND): the <span class="citerefentry"><span class="refentrytitle">named</span>(8)</span> manual page describes what file type to use for a given situation (see the <code class="computeroutput">Red Hat SELinux BIND Security Profile</code> section). The <span class="citerefentry"><span class="refentrytitle">named_selinux</span>(8)</span> manual page describes that, by default, <code class="systemitem">named</code> can not write to master zone files, and to allow such access, the <code class="computeroutput">named_write_master_zones</code> Boolean must be turned on.
+						Berkeley Internet Name Domain (BIND): la página de manual de <span class="citerefentry"><span class="refentrytitle">named</span>(8)</span> describe qué tipo de archivo usar para una situación dada (vea la sección <code class="computeroutput">Perfil de Seguridad de SELinux para BIND de Red Hat</code> section). La página man de <span class="citerefentry"><span class="refentrytitle">named_selinux</span>(8)</span> describe que, por defecto, <code class="systemitem">named</code> no puede escribir a archivos de zona maestros y que, para permitir ese acceso, el Booleano <code class="computeroutput">named_write_master_zones</code> debe ser puesto en 1.
 					</div></li></ul></div><div class="para">
-				The information in manual pages helps you configure the correct file types and Booleans, helping to prevent SELinux from denying access.
-			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Fixing_Problems-Possible_Causes_of_Silent_Denials.html"><strong>Anterior</strong>7.3.2. Possible Causes of Silent Denials</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains.html"><strong>Siguiente</strong>7.3.4. Permissive Domains</a></li></ul></body></html>
+				La información en las páginas del manual le ayudan a configurar los tipos de archivos correctos y los Booleanos, ayudándolo a prevenir las negaciones de acceso por parte de SELinux.
+			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Fixing_Problems-Possible_Causes_of_Silent_Denials.html"><strong>Anterior</strong>7.3.2. Posibles Causas de las Negaciones Silencio...</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains.html"><strong>Siguiente</strong>7.3.4. Dominios Permisivos</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains.html
index 7eef290..d7c150c 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains.html
@@ -1,35 +1,35 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.3.4. Permissive Domains</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html" title="7.3. Fixing Problems" /><link rel="prev" href="sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services.html" title="7.3.3. Manual Pages for Services" /><link rel="next" href="sect-Security-Enhanced_Linux-Permissive_Domains-Denials_for_Permissive_Domains.html" title="7.3.4.2. Denials for Permissive Domains" /></head><body class="toc_embeded "><div id="t
 ocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Permissive_Domains-Denials_for_Permissive_Domains.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="7.3.4. Permissive Domains" id="sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains"><div class="titlepage"><div><div keep-together.within-column="always"><h3 clas
 s="title">7.3.4. Permissive Domains</h3></div></div></div><div class="para">
-				When SELinux is running in permissive mode, SELinux does not deny access, but denials are logged for actions that would have been denied if running in enforcing mode. Previously, it was not possible to make a single domain permissive (remember: processes run in domains). In certain situations, this led to making the whole system permissive to troubleshoot issues.
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.3.4. Dominios Permisivos</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html" title="7.3. Corrección de Problemas" /><link rel="prev" href="sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services.html" title="7.3.3. Páginas de Manual para Servicios" /><link rel="next" href="sect-Security-Enhanced_Linux-Permissive_Domains-Denials_for_Permissive_Domains.html" title="7.3.4.2. Negaciones para Dominios Permisivos" /></head><body cla
 ss="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Permissive_Domains-Denials_for_Permissive_Domains.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="7.3.4. Dominios Permisivos" id="sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains"><div class="titlepage"><div><div keep-together.wi
 thin-column="always"><h3 class="title">7.3.4. Dominios Permisivos</h3></div></div></div><div class="para">
+				Cuando SELinux se ejecuta en modo permisivo, SELinux no niega el acceso, sino que las negaciones para las acciones se guardan como si fuera que corre en modo obediente. Previamente, no era posible hacer permisivo un único dominio (recuerde: los procesos corren en dominios). En ciertas situaciones, esto llevó a hacer el sistema permisivo para poder corregir los problemas.
 			</div><div class="para">
-				Fedora 11 introduces permissive domains, where an administrator can configure a single process (domain) to run permissive, rather than making the whole system permissive. SELinux checks are still performed for permissive domains; however, the kernel allows access and reports an AVC denial for situations where SELinux would have denied access. Permissive domains are also available in Fedora 9 (with the latest updates applied).
+				Fedora 11 introduce los dominios permisivos, donde un administrador puede configurar un único proceso (dominio) para que corra permisivo, en vez de hacer todo el sistema permisivo. Los chequeos de SELinux se realizan igualmente para dominios permisivos; sin embargo, el kernel permite el acceso e informa la negación AVC para situaciones donde SELinux hubiera negado el acceso. Los dominios permisivos están también disponibles en Fedora 9 (con las últimas actualizaciones aplicadas).
 			</div><div class="para">
-				In Red Hat Enterprise Linux 4 and 5, <code class="computeroutput"><em class="replaceable"><code>domain</code></em>_disable_trans</code> Booleans are available to prevent an application from transitioning to a confined domain, and therefore, the process runs in an unconfined domain, such as <code class="computeroutput">initrc_t</code>. Turning such Booleans on can cause major problems. For example, if the <code class="computeroutput">httpd_disable_trans</code> Boolean is turned on:
+				En el Linux para Empresas de Red Hat 4 y 5, los Booleanos <code class="computeroutput"><em class="replaceable"><code>dominio</code></em>_disable_trans</code> están disponibles para prevenir que una aplicación transicione a un dominio confinado, y por lo tanto, el proceso se ejecute en un dominio no confinado, tal como <code class="computeroutput">initrc_t</code>. Poniendo en 1 tales booleanos pueden causar problemas serios. Por ejemplo, si el Booleano <code class="computeroutput">httpd_disable_trans</code> se pone en 1:
 			</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-						<code class="systemitem">httpd</code> runs in the unconfined <code class="computeroutput">initrc_t</code> domain. Files created by processes running in the <code class="computeroutput">initrc_t</code> domain may not have the same labeling rules applied as files created by a process running in the <code class="computeroutput">httpd_t</code> domain, potentially allowing processes to create mislabeled files. This causes access problems later on.
+						<code class="systemitem">httpd</code> corre en el dominio no confinado <code class="computeroutput">initrc_t</code>. Los archivos creados por los procesos en el dominio <code class="computeroutput">initrc_t</code> puede no tener aplicadas las mismas reglas de etiquetados como los archivos creados por el proceso corriendo en el dominio <code class="computeroutput">httpd_t</code>, permitiendo que los procesos puedan potencialmente crear archivos mal etiquetados. Esto causa problemas más adelante.
 					</div></li><li class="listitem"><div class="para">
-						confined domains that are allowed to communicate with <code class="computeroutput">httpd_t</code> can not communicate with <code class="computeroutput">initrc_t</code>, possibly causing additional failures.
+						dominios confinados que pueden comunicarse con <code class="computeroutput">httpd_t</code> no pueden comunicarse con <code class="computeroutput">initrc_t</code>, posiblemente causan fallas adicionales.
 					</div></li></ul></div><div class="para">
-				The <code class="computeroutput"><em class="replaceable"><code>domain</code></em>_disable_trans</code> Booleans were removed from Fedora 7, even though there was no replacement. Permissive domains solve the above issues: transition rules apply, and files are created with the correct labels.
+				Los Booleanos <code class="computeroutput"><em class="replaceable"><code>domain</code></em>_disable_trans</code> fueron eliminados de Fedora 7, y no se pusieron reemplazos. Los dominios permisivos pueden resolver esos problemas: se aplican las reglas de transición y los archivos se crean con las etiquetas correctas.
 			</div><div class="para">
-				Permissive domains can be used for:
+				Los dominios permisivos se pueden usar para:
 			</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-						making a single process (domain) run permissive to troubleshoot an issue, rather than putting the entire system at risk by making the entire system permissive.
+						hacer que un único proceso (dominio) corra permisivo para solucionar alguna cuestión, en vez de poner todo el sistema en riesgo haciendo permisivo a todo el sistema.
 					</div></li><li class="listitem"><div class="para">
-						creating policies for new applications. Previously, it was recommended that a minimal policy be created, and then the entire machine put into permissive mode, so that the application could run, but SELinux denials still logged. <code class="command">audit2allow</code> could then be used to help write the policy. This put the whole system at risk. With permissive domains, only the domain in the new policy can be marked permissive, without putting the whole system at risk.
-					</div></li></ul></div><div class="section" title="7.3.4.1. Making a Domain Permissive" id="sect-Security-Enhanced_Linux-Permissive_Domains-Making_a_Domain_Permissive"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">7.3.4.1. Making a Domain Permissive</h4></div></div></div><div class="para">
-					To make a domain permissive, run the <code class="command">semanage permissive -a <em class="replaceable"><code>domain</code></em></code> command, where <em class="replaceable"><code>domain</code></em> is the domain you want to make permissive. For example, run the following command as the Linux root user to make the <code class="computeroutput">httpd_t</code> domain (the domain the Apache HTTP Server runs in) permissive:
+						creación de políticas para nuevas aplicaciones. Previamente, era recomendado crear una política mínima, y luego poner la máquina completa en modo permisivo, para que la aplicación pudiera funcionar, pero las negaciones de SELinux eran igualmente grabadas. <code class="command">audit2allow</code> podría usarse luego para ayudar a escribir la política. Esto pone todo el sistema en riesgo. Con dominios permisivos, sólo el dominio en la nueva política puede marcarse como permisivo, sin poner en riesgo todo el sistema.
+					</div></li></ul></div><div class="section" title="7.3.4.1. Creando un Dominio Permisivo" id="sect-Security-Enhanced_Linux-Permissive_Domains-Making_a_Domain_Permissive"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">7.3.4.1. Creando un Dominio Permisivo</h4></div></div></div><div class="para">
+					Para hacer un dominio permisivo, ejecute el comando <code class="command">semanage permissive -a <em class="replaceable"><code>dominio</code></em></code>, donde <em class="replaceable"><code>dominio</code></em> es el dominio que quiere hacer permisivo. Por ejemplo, ejecute el siguiente comando como usuario root de Linux para hacer permisivo el dominio <code class="computeroutput">httpd_t</code> (el dominio en el que corre el Servidor HTTP Apache):
 				</div><div class="para">
 					<code class="command">/usr/sbin/semanage permissive -a httpd_t</code>
 				</div><div class="para">
-					To view a list of domains you have made permissive, run the <code class="command">semodule -l | grep permissive</code> command as the Linux root user. For example:
+					Para ver una lista de los dominios que hizo permisivos, corra el comando <code class="command">semodule -l | grep permissive</code> como usuario root de Linux. Por ejemplo:
 				</div><pre class="screen">
 # /usr/sbin/semodule -l | grep permissive
 permissive_httpd_t      1.0
 
 </pre><div class="para">
-					If you no longer want a domain to be permissive, run the <code class="command">semanage permissive -d <em class="replaceable"><code>domain</code></em></code> command as the Linux root user. For example:
+					Si ya no quiere que un dominio sea permisivo, corra el comando <code class="command">semanage permissive -d <em class="replaceable"><code>dominio</code></em></code> como usuario root de Linux. Por ejemplo:
 				</div><div class="para">
 					<code class="command">/usr/sbin/semanage permissive -d httpd_t</code>
-				</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services.html"><strong>Anterior</strong>7.3.3. Manual Pages for Services</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Permissive_Domains-Denials_for_Permissive_Domains.html"><strong>Siguiente</strong>7.3.4.2. Denials for Permissive Domains</a></li></ul></body></html>
+				</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services.html"><strong>Anterior</strong>7.3.3. Páginas de Manual para Servicios</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Permissive_Domains-Denials_for_Permissive_Domains.html"><strong>Siguiente</strong>7.3.4.2. Negaciones para Dominios Permisivos</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-Possible_Causes_of_Silent_Denials.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-Possible_Causes_of_Silent_Denials.html
index 3ba6515..bd6955c 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-Possible_Causes_of_Silent_Denials.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-Possible_Causes_of_Silent_Denials.html
@@ -1,19 +1,19 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.3.2. Possible Causes of Silent Denials</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html" title="7.3. Fixing Problems" /><link rel="prev" href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html" title="7.3. Fixing Problems" /><link rel="next" href="sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services.html" title="7.3.3. Manual Pages for Services" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><if
 rame id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="7.3.2. Possible Causes of Silent Denials" id="sect-Security-Enhanced_Linux-Fixing_Problems-Possible_Causes_of_Silent_Denials"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">
 7.3.2. Possible Causes of Silent Denials</h3></div></div></div><div class="para">
-				In certain situations, AVC denials may not be logged when SELinux denies access. Applications and system library functions often probe for more access than required to perform their tasks. To maintain least privilege without filling audit logs with AVC denials for harmless application probing, the policy can silence AVC denials without allowing a permission by using <code class="computeroutput">dontaudit</code> rules. These rules are common in standard policy. The downside of <code class="computeroutput">dontaudit</code> is that, although SELinux denies access, denial messages are not logged, making troubleshooting hard.
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.3.2. Posibles Causas de las Negaciones Silenciosas</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html" title="7.3. Corrección de Problemas" /><link rel="prev" href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html" title="7.3. Corrección de Problemas" /><link rel="next" href="sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services.html" title="7.3.3. Páginas de Manual para Servicios" /></head><body class="toc
 _embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="7.3.2. Posibles Causas de las Negaciones Silenciosas" id="sect-Security-Enhanced_Linux-Fixing_Problems-Possible_Causes_of_Silent_Denials"><div class="titlepage"><div><div 
 keep-together.within-column="always"><h3 class="title">7.3.2. Posibles Causas de las Negaciones Silenciosas</h3></div></div></div><div class="para">
+				En ciertas situaciones, las negaciones AVC pueden no ser guardadas cuando SELinux niega el acceso. Las aplicaciones y las funciones de las bibliotecas del sistema a menudo prueban más accesos que los pedidos para realizar sus tareas. Para mantener el menor privilegio sin llenar los informes de auditoría con negaciones AVC para pruebas sin peligro de las aplicaciones, la política puede silenciar las negaciones AVC sin permitir el uso de reglas <code class="computeroutput">dontaudit</code>. Estas reglas son comúnes en la política estándar. La contraparte de <code class="computeroutput">dontaudit</code> es que, aunque SELinux niega el acceso, los mensajes no se guardan, lo que dificulta resolver el problema.
 			</div><div class="para">
-				To temporarily disable <code class="computeroutput">dontaudit</code> rules, allowing all denials to be logged, run the following command as the Linux root user:
+				Deshabilite temporalmente las reglas <code class="computeroutput">dontaudit</code>, permitiendo que se guarden todas las negaciones, ejecute el siguiente comando como usuario root de Linux:
 			</div><div class="para">
 				<code class="command">/usr/sbin/semodule -DB</code>
 			</div><div class="para">
-				The <code class="option">-D</code> option disables <code class="computeroutput">dontaudit</code> rules; the <code class="option">-B</code> option rebuilds policy. After running <code class="command">semodule -DB</code>, try exercising the application that was encountering permission problems, and see if SELinux denials — relevant to the application — are now being logged. Take care in deciding which denials should be allowed, as some should be ignored and handled via <code class="computeroutput">dontaudit</code> rules. If in doubt, or in search of guidance, contact other SELinux users and developers on an SELinux list, such as <a href="http://www.redhat.com/mailman/listinfo/fedora-selinux-list">fedora-selinux-list</a>.
+				La opción <code class="option">-D</code> deshabilita las reglas <code class="computeroutput">dontaudit</code>; la opción <code class="option">-B</code> reconstruye la política. Después de ejcutar <code class="command">semodule -DB</code>, pruebe ejercitar la aplicación que tuvo problemas de permisos, y vea si ahora se guardan negaciones de SELinux relacionadas con la aplicación. Tenga cuidado con la decición de qué negaciones se deben permitir, dado que algunas se deben ignorar y manejarse vía reglas <code class="computeroutput">dontaudit</code>. Si tiene duda, o busca alguna guía, contacte a otros usuarios y desarrolladores de SELinux en una lista de SELinux, tal como <a href="http://www.redhat.com/mailman/listinfo/fedora-selinux-list">fedora-selinux-list</a>.
 			</div><div class="para">
-				To rebuild policy and enable <code class="computeroutput">dontaudit</code> rules, run the following command as the Linux root user:
+				Para reconstruir la política y habilitar las reglas <code class="computeroutput">dontaudit</code>, ejecute el siguiente comando como usuario root de Linux:
 			</div><div class="para">
 				<code class="command">/usr/sbin/semodule -B</code>
 			</div><div class="para">
-				This restores the policy to its original state. For a full list of <code class="computeroutput">dontaudit</code> rules, run the <code class="command">sesearch --dontaudit</code> command. Narrow down searches using the <code class="option">-s <em class="replaceable"><code>domain</code></em></code> option and the <code class="command">grep</code> command. For example:
+				Esto restaura la política a su estado original. Para una lista completa de las reglas <code class="computeroutput">dontaudit</code>, corra el comando <code class="command">sesearch --dontaudit</code>. Búsquedas más refinadas usando la opción <code class="option">-s <em class="replaceable"><code>dominio</code></em></code> y el comando <code class="command">grep</code>. Por ejemplo:
 			</div><pre class="screen">
 $ sesearch --dontaudit -s smbd_t | grep squid
 WARNING: This policy contained disabled aliases; they have been removed.
@@ -21,5 +21,5 @@ dontaudit smbd_t squid_port_t : tcp_socket name_bind ;
 dontaudit smbd_t squid_port_t : udp_socket name_bind ;
 
 </pre><div class="para">
-				Refer to <a class="xref" href="sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages.html" title="7.3.6. Raw Audit Messages">Sección 7.3.6, “Raw Audit Messages”</a> and <a class="xref" href="sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages.html" title="7.3.7. sealert Messages">Sección 7.3.7, “sealert Messages”</a> for information about analyzing denials.
-			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html"><strong>Anterior</strong>7.3. Fixing Problems</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services.html"><strong>Siguiente</strong>7.3.3. Manual Pages for Services</a></li></ul></body></html>
+				Refer to <a class="xref" href="sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages.html" title="7.3.6. Raw Audit Messages">Sección 7.3.6, “Raw Audit Messages”</a> and <a class="xref" href="sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages.html" title="7.3.7. Mensajes sealert">Sección 7.3.7, “Mensajes sealert”</a> for information about analyzing denials.
+			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html"><strong>Anterior</strong>7.3. Corrección de Problemas</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services.html"><strong>Siguiente</strong>7.3.3. Páginas de Manual para Servicios</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages.html
index 0d1a432..dadb22a 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages.html
@@ -1,30 +1,30 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.3.6. Raw Audit Messages</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html" title="7.3. Fixing Problems" /><link rel="prev" href="sect-Security-Enhanced_Linux-Fixing_Problems-Searching_For_and_Viewing_Denials.html" title="7.3.5. Searching For and Viewing Denials" /><link rel="next" href="sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages.html" title="7.3.7. sealert Messages" /></head><body class="toc_embeded "><div id="tocdiv" class="toc
 "><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Fixing_Problems-Searching_For_and_Viewing_Denials.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="7.3.6. Raw Audit Messages" id="sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.3.6. Raw Audit
  Messages</h3></div></div></div><div class="para">
-				Raw audit messages are logged to <code class="filename">/var/log/audit/audit.log</code>. The following is an example AVC denial (and the associated system call) that occurred when the Apache HTTP Server (running in the <code class="computeroutput">httpd_t</code> domain) attempted to access the <code class="filename">/var/www/html/file1</code> file (labeled with the <code class="computeroutput">samba_share_t</code> type):
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.3.6. Raw Audit Messages</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html" title="7.3. Corrección de Problemas" /><link rel="prev" href="sect-Security-Enhanced_Linux-Fixing_Problems-Searching_For_and_Viewing_Denials.html" title="7.3.5. Búsqueda y Revisión de Negaciones" /><link rel="next" href="sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages.html" title="7.3.7. Mensajes sealert" /></head><body class="toc_embeded "><div id="to
 cdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Fixing_Problems-Searching_For_and_Viewing_Denials.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="7.3.6. Raw Audit Messages" id="sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">
 7.3.6. Raw Audit Messages</h3></div></div></div><div class="para">
+				Los mensajes crudos de auditoría se guardan en <code class="filename">/var/log/audit/audit.log</code>. El siguiente es un ejemplo de negación AVC (y su llamada a sistema asociado) que ocurrío cuando el Servidor HTTP Apache (corriendo en el dominio <code class="computeroutput">httpd_t</code>) intentó acceder el <code class="filename">/var/www/html/archivo1</code> (etiquetado con el tipo <code class="computeroutput">samba_share_t</code>):
 			</div><pre class="screen">
 type=AVC msg=audit(1226874073.147:96): avc:  denied  { getattr } for  pid=2465 comm="httpd" path="/var/www/html/file1" dev=dm-0 ino=284133 scontext=unconfined_u:system_r:httpd_t:s0 tcontext=unconfined_u:object_r:samba_share_t:s0 tclass=file
 
 type=SYSCALL msg=audit(1226874073.147:96): arch=40000003 syscall=196 success=no exit=-13 a0=b98df198 a1=bfec85dc a2=54dff4 a3=2008171 items=0 ppid=2463 pid=2465 auid=502 uid=48 gid=48 euid=48 suid=48 fsuid=48 egid=48 sgid=48 fsgid=48 tty=(none) ses=6 comm="httpd" exe="/usr/sbin/httpd" subj=unconfined_u:system_r:httpd_t:s0 key=(null)
 
 </pre><div class="variablelist"><dl><dt><span class="term"><em class="replaceable"><code>{ getattr }</code></em></span></dt><dd><div class="para">
-							The item in braces indicates the permission that was denied. <code class="computeroutput">getattr</code> indicates the source process was trying to read the target file's status information. This occurs before reading files. This action is denied due to the file being accessed having the wrong label. Commonly seen permissions include <code class="computeroutput">getattr</code>, <code class="computeroutput">read</code>, and <code class="computeroutput">write</code>.
+							El item entre llaves indica el permiso que fue negado. <code class="computeroutput">getattr</code> indica el proceso fuente que intentó leer la información de estado del archivo destino. Esto ocurre antes de leer archivos. Esta acción es negada dado que el archivo está siendo accedido con la etiqueta equivocada. Los permisos vistos comúnmente incluyen a <code class="computeroutput">getattr</code>, <code class="computeroutput">read</code> y <code class="computeroutput">write</code>.
 						</div></dd><dt><span class="term">comm="<em class="replaceable"><code>httpd</code></em>"</span></dt><dd><div class="para">
 							The executable that launched the process. The full path of the executable is found in the <code class="computeroutput">exe=</code> section of the system call (<code class="computeroutput">SYSCALL</code>) message, which in this case, is <code class="computeroutput">exe="/usr/sbin/httpd"</code>.
 						</div></dd><dt><span class="term">path="<em class="replaceable"><code>/var/www/html/file1</code></em>"</span></dt><dd><div class="para">
-							The path to the object (target) the process attempted to access.
+							La dirección al objeto (destino) al que quiere acceder el proceso.
 						</div></dd><dt><span class="term">scontext="<em class="replaceable"><code>unconfined_u:system_r:httpd_t:s0</code></em>"</span></dt><dd><div class="para">
-							The SELinux context of the process that attempted the denied action. In this case, it is the SELinux context of the Apache HTTP Server, which is running in the <code class="computeroutput">httpd_t</code> domain.
+							El contexto de SELinux del proceso que intentó la acción denegada. En este caso, es el contexto SELinux del Servidor HTTP Apache, que core en el dominio <code class="computeroutput">httpd_t</code>.
 						</div></dd><dt><span class="term">tcontext="<em class="replaceable"><code>unconfined_u:object_r:samba_share_t:s0</code></em>"</span></dt><dd><div class="para">
-							The SELinux context of the object (target) the process attempted to access. In this case, it is the SELinux context of <code class="filename">file1</code>. Note: the <code class="computeroutput">samba_share_t</code> type is not accessible to processes running in the <code class="computeroutput">httpd_t</code> domain.
+							El contexto de SELinux del objeto (destino) al que intentó acceder el proceso. En este caso, es el contexto SELinux del <code class="filename">archivo1</code>. Nota: el tipo <code class="computeroutput">samba_share_t</code> no es accesible para procesos que corren el dominio <code class="computeroutput">httpd_t</code>.
 						</div><div class="para">
-							In certain situations, the <code class="computeroutput">tcontext</code> may match the <code class="computeroutput">scontext</code>, for example, when a process attempts to execute a system service that will change characteristics of that running process, such as the user ID. Also, the <code class="computeroutput">tcontext</code> may match the <code class="computeroutput">scontext</code> when a process tries to use more resources (such as memory) than normal limits allow, resulting in a security check to see if that process is allowed to break those limits.
+							En ciertas cituaciónes, el <code class="computeroutput">tcontext</code> puede coincidir con <code class="computeroutput">scontext</code>, por ejemplo, cuando un proceso intenta ejecutar un servicio del sistema que cambiará las características de ese proceso en ejecución, tales como el ID del usuario. También el <code class="computeroutput">tcontext</code> puede coincidir con el <code class="computeroutput">scontext</code> cuando un proceso intenta usar más recursos (como la memoria) más allá de los límites normales permitidos, lo que resulta en un chequeo de seguridad para ver si el proceso tiene permitido romper esos límites.
 						</div></dd></dl></div><div class="para">
-				From the system call (<code class="computeroutput">SYSCALL</code>) message, two items are of interest:
+				Desde el mensaje de llamado al sistema (<code class="computeroutput">SYSCALL</code>) nos interesan dos ítems:
 			</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-						<code class="computeroutput">success=<em class="replaceable"><code>no</code></em></code>: indicates whether the denial (AVC) was enforced or not. <code class="computeroutput">success=no</code> indicates the system call was not successful (SELinux denied access). <code class="computeroutput">success=yes</code> indicates the system call was successful - this can be seen for permissive domains or unconfined domains, such as <code class="computeroutput">initrc_t</code> and <code class="computeroutput">kernel_t</code>.
+						<code class="computeroutput">success=<em class="replaceable"><code>no</code></em></code>: indica si la negación (AVC) fue aplicada o no. <code class="computeroutput">success=no</code> indica que la llamada al sistema no fue exitosa(SELinux negó el acceso). <code class="computeroutput">success=yes</code> indica que la llamada al sistema fue exitosa - esto se puede ver en dominios permisivos o en dominios no confinados, tales como <code class="computeroutput">initrc_t</code> y <code class="computeroutput">kernel_t</code>.
 					</div></li><li class="listitem"><div class="para">
 						<code class="computeroutput">exe="<em class="replaceable"><code>/usr/sbin/httpd</code></em>"</code>: the full path to the executable that launched the process, which in this case, is <code class="computeroutput">exe="/usr/sbin/httpd"</code>.
 					</div></li></ul></div><div class="para">
-				An incorrect file type is a common cause for SELinux denying access. To start troubleshooting, compare the source context (<code class="computeroutput">scontext</code>) with the target context (<code class="computeroutput">tcontext</code>). Should the process (<code class="computeroutput">scontext</code>) be accessing such an object (<code class="computeroutput">tcontext</code>)? For example, the Apache HTTP Server (<code class="computeroutput">httpd_t</code>) should only be accessing types specified in the <span class="citerefentry"><span class="refentrytitle">httpd_selinux</span>(8)</span> manual page, such as <code class="computeroutput">httpd_sys_content_t</code>, <code class="computeroutput">public_content_t</code>, and so on, unless configured otherwise.
-			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Fixing_Problems-Searching_For_and_Viewing_Denials.html"><strong>Anterior</strong>7.3.5. Searching For and Viewing Denials</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages.html"><strong>Siguiente</strong>7.3.7. sealert Messages</a></li></ul></body></html>
+				Un tipo de archivo incorrecto es una causa común de que SELinux niegue el acceso. Para comenzar a resolver el problema, compare el contexto fuente (<code class="computeroutput">scontext</code>) con el contexto destino (<code class="computeroutput">tcontext</code>). ¿Debería el proceso (<code class="computeroutput">scontext</code>) acceder a un objeto (<code class="computeroutput">tcontext</code>)? Por ejemplo, el Servidor HTTP Apache (<code class="computeroutput">httpd_t</code>) sólo debería acceder tipos especificados en la página man <span class="citerefentry"><span class="refentrytitle">httpd_selinux</span>(8)</span>, tales como <code class="computeroutput">httpd_sys_content_t</code>, <code class="computeroutput">public_content_t</code>, y así sucesivamente, a menos que se configure de otra forma.
+			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Fixing_Problems-Searching_For_and_Viewing_Denials.html"><strong>Anterior</strong>7.3.5. Búsqueda y Revisión de Negaciones</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages.html"><strong>Siguiente</strong>7.3.7. Mensajes sealert</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-Searching_For_and_Viewing_Denials.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-Searching_For_and_Viewing_Denials.html
index 7af90bc..e285e55 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-Searching_For_and_Viewing_Denials.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-Searching_For_and_Viewing_Denials.html
@@ -1,19 +1,19 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.3.5. Searching For and Viewing Denials</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html" title="7.3. Fixing Problems" /><link rel="prev" href="sect-Security-Enhanced_Linux-Permissive_Domains-Denials_for_Permissive_Domains.html" title="7.3.4.2. Denials for Permissive Domains" /><link rel="next" href="sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages.html" title="7.3.6. Raw Audit Messages" /></head><body class="toc_embeded "><div id="
 tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Permissive_Domains-Denials_for_Permissive_Domains.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="7.3.5. Searching For and Viewing Denials" id="sect-Security-Enhanced_Linux-Fixing_Problems-Searching_For_and_Viewing_Denials"><div class="titlepage"><div><div keep-together.within-
 column="always"><h3 class="title">7.3.5. Searching For and Viewing Denials</h3></div></div></div><div class="para">
-				This section assumes the <span class="package">setroubleshoot</span>, <span class="package">setroubleshoot-server</span>, and <span class="package">audit</span> packages are installed, and that the <code class="systemitem">auditd</code>, <code class="systemitem">rsyslogd</code>, and <code class="systemitem">setroubleshootd</code> daemons are running. Refer to <a class="xref" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used.html" title="5.2. Which Log File is Used">Sección 5.2, “Which Log File is Used”</a> for information about starting these daemons. A number of tools are available for searching for and viewing SELinux denials, such as <code class="command">ausearch</code>, <code class="command">aureport</code>, and <code class="command">sealert</code>.
-			</div><div class="formalpara"><h5 class="formalpara">ausearch</h5>
-					The <span class="package">audit</span> package provides <code class="command">ausearch</code>. From the <span class="citerefentry"><span class="refentrytitle">ausearch</span>(8)</span> manual page: "<code class="command">ausearch</code> is a tool that can query the audit daemon logs based for events based on different search criteria"<sup>[<a id="id709472" href="#ftn.id709472" class="footnote">16</a>]</sup>. The <code class="command">ausearch</code> tool accesses <code class="filename">/var/log/audit/audit.log</code>, and as such, must be run as the Linux root user:
-				</div><div class="segmentedlist"><table border="0"><thead><tr class="segtitle"><th>Searching For</th><th>Command</th></tr></thead><tbody><tr class="seglistitem"><td class="seg">all denials</td><td class="seg"><code class="command">/sbin/ausearch -m avc</code></td></tr><tr class="seglistitem"><td class="seg">denials for that today</td><td class="seg"><code class="command">/sbin/ausearch -m avc -ts today</code></td></tr><tr class="seglistitem"><td class="seg">denials from the last 10 minutes</td><td class="seg"><code class="command">/sbin/ausearch -m avc -ts recent</code></td></tr></tbody></table></div><div class="para">
-				To search for SELinux denials for a particular service, use the <code class="option">-c <em class="replaceable"><code>comm-name</code></em></code> option, where <em class="replaceable"><code>comm-name</code></em> "is the executable’s name"<sup>[<a id="id709569" href="#ftn.id709569" class="footnote">17</a>]</sup>, for example, <code class="systemitem">httpd</code> for the Apache HTTP Server, and <code class="systemitem">smbd</code> for Samba:
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.3.5. Búsqueda y Revisión de Negaciones</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html" title="7.3. Corrección de Problemas" /><link rel="prev" href="sect-Security-Enhanced_Linux-Permissive_Domains-Denials_for_Permissive_Domains.html" title="7.3.4.2. Negaciones para Dominios Permisivos" /><link rel="next" href="sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages.html" title="7.3.6. Raw Audit Messages" /></head><body class="to
 c_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Permissive_Domains-Denials_for_Permissive_Domains.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="7.3.5. Búsqueda y Revisión de Negaciones" id="sect-Security-Enhanced_Linux-Fixing_Problems-Searching_For_and_Viewing_Denials"><div class="titlepage"><div><di
 v keep-together.within-column="always"><h3 class="title">7.3.5. Búsqueda y Revisión de Negaciones</h3></div></div></div><div class="para">
+				This section assumes the <span class="package">setroubleshoot</span>, <span class="package">setroubleshoot-server</span>, and <span class="package">audit</span> packages are installed, and that the <code class="systemitem">auditd</code>, <code class="systemitem">rsyslogd</code>, and <code class="systemitem">setroubleshootd</code> daemons are running. Refer to <a class="xref" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used.html" title="5.2. Qué Archivo Log se usa">Sección 5.2, “Qué Archivo Log se usa”</a> for information about starting these daemons. A number of tools are available for searching for and viewing SELinux denials, such as <code class="command">ausearch</code>, <code class="command">aureport</code>, and <code class="command">sealert</code>.
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Searching_For_and_Viewing_Denials-ausearch"><h5 class="formalpara">ausearch</h5>
+					The <span class="package">audit</span> package provides <code class="command">ausearch</code>. From the <span class="citerefentry"><span class="refentrytitle">ausearch</span>(8)</span> manual page: "<code class="command">ausearch</code> is a tool that can query the audit daemon logs based for events based on different search criteria"<sup>[<a id="id995602" href="#ftn.id995602" class="footnote">16</a>]</sup>. The <code class="command">ausearch</code> tool accesses <code class="filename">/var/log/audit/audit.log</code>, and as such, must be run as the Linux root user:
+				</div><div class="segmentedlist"><table border="0"><thead><tr class="segtitle"><th>Buscando</th><th>Comando</th></tr></thead><tbody><tr class="seglistitem"><td class="seg">todas las negaciones</td><td class="seg"><code class="command">/sbin/ausearch -m avc</code></td></tr><tr class="seglistitem"><td class="seg">negaciones de hoy</td><td class="seg"><code class="command">/sbin/ausearch -m avc -ts today</code></td></tr><tr class="seglistitem"><td class="seg">negaciones desde los últimos 10 minutos</td><td class="seg"><code class="command">/sbin/ausearch -m avc -ts recent</code></td></tr></tbody></table></div><div class="para">
+				To search for SELinux denials for a particular service, use the <code class="option">-c <em class="replaceable"><code>comm-name</code></em></code> option, where <em class="replaceable"><code>comm-name</code></em> "is the executable’s name"<sup>[<a id="id793188" href="#ftn.id793188" class="footnote">17</a>]</sup>, for example, <code class="systemitem">httpd</code> for the Apache HTTP Server, and <code class="systemitem">smbd</code> for Samba:
 			</div><div class="para">
 				<code class="command">/sbin/ausearch -m avc -c httpd</code>
 			</div><div class="para">
 				<code class="command">/sbin/ausearch -m avc -c smbd</code>
 			</div><div class="para">
-				Refer to the <span class="citerefentry"><span class="refentrytitle">ausearch</span>(8)</span> manual page for further <code class="command">ausearch</code> options.
-			</div><div class="formalpara"><h5 class="formalpara">aureport</h5>
-					The <span class="package">audit</span> package provides <code class="command">aureport</code>. From the <span class="citerefentry"><span class="refentrytitle">aureport</span>(8)</span> manual page: "<code class="command">aureport</code> is a tool that produces summary reports of the audit system logs"<sup>[<a id="id1639670" href="#ftn.id1639670" class="footnote">18</a>]</sup>. The <code class="command">aureport</code> tool accesses <code class="filename">/var/log/audit/audit.log</code>, and as such, must be run as the Linux root user. To view a list of SELinux denials and how often each one occurred, run the <code class="command">aureport -a</code> command. The following is example output that includes two denials:
+				Vaya a la página de manual de <span class="citerefentry"><span class="refentrytitle">ausearch</span>(8)</span> para más opciones de <code class="command">ausearch</code>.
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Searching_For_and_Viewing_Denials-aureport"><h5 class="formalpara">aureport</h5>
+					The <span class="package">audit</span> package provides <code class="command">aureport</code>. From the <span class="citerefentry"><span class="refentrytitle">aureport</span>(8)</span> manual page: "<code class="command">aureport</code> is a tool that produces summary reports of the audit system logs"<sup>[<a id="id1128543" href="#ftn.id1128543" class="footnote">18</a>]</sup>. The <code class="command">aureport</code> tool accesses <code class="filename">/var/log/audit/audit.log</code>, and as such, must be run as the Linux root user. To view a list of SELinux denials and how often each one occurred, run the <code class="command">aureport -a</code> command. The following is example output that includes two denials:
 				</div><pre class="screen">
 # /sbin/aureport -a
 
@@ -25,28 +25,28 @@ AVC Report
 2. 05/03/2009 22:00:25 vsftpd unconfined_u:system_r:ftpd_t:s0 5 file read unconfined_u:object_r:cifs_t:s0 denied 4
 
 </pre><div class="para">
-				Refer to the <span class="citerefentry"><span class="refentrytitle">aureport</span>(8)</span> manual page for further <code class="command">aureport</code> options.
-			</div><div class="formalpara"><h5 class="formalpara">sealert</h5>
-					The <span class="package">setroubleshoot-server</span> package provides <code class="command">sealert</code>, which reads denial messages translated by <span class="package">setroubleshoot-server</span>. Denials are assigned IDs, as seen in <code class="filename">/var/log/messages</code>. The following is an example denial from <code class="filename">messages</code>:
+				Vaya a la página de manual de <span class="citerefentry"><span class="refentrytitle">aureport</span>(8)</span> para más opciones de <code class="command">aureport</code>.
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Searching_For_and_Viewing_Denials-sealert"><h5 class="formalpara">sealert</h5>
+					El paquete <span class="package">setroubleshoot-server</span> provee <code class="command">sealert</code>, que lee los mensajes de negación traducidos por <span class="package">setroubleshoot-server</span>. A las negaciones se le asignan IDs, como se ve en <code class="filename">/var/log/messages</code>. El siguiente es un ejemplo de negación en <code class="filename">messages</code>:
 				</div><pre class="screen">
 setroubleshoot: SELinux is preventing httpd (httpd_t) "getattr" to /var/www/html/file1 (samba_share_t). For complete SELinux messages. run sealert -l 84e0b04d-d0ad-4347-8317-22e74f6cd020
 
 </pre><div class="para">
-				In this example, the denial ID is <code class="computeroutput">84e0b04d-d0ad-4347-8317-22e74f6cd020</code>. The <code class="option">-l</code> option takes an ID as an argument. Running the <code class="command">sealert -l 84e0b04d-d0ad-4347-8317-22e74f6cd020</code> command presents a detailed analysis of why SELinux denied access, and a possible solution for allowing access.
+				En este ejemplo, el ID de negación es <code class="computeroutput">84e0b04d-d0ad-4347-8317-22e74f6cd020</code>. La opción <code class="option">-l</code> toma un ID como argumento. Ejecutando el comando <code class="command">sealert -l 84e0b04d-d0ad-4347-8317-22e74f6cd020</code> le presenta un análisis detallado de por qué SELinux negó el acceso, y una posible solución para permitir el acceso.
 			</div><div class="para">
-				If you are running the X Window System, have the <span class="package">setroubleshoot</span> and <span class="package">setroubleshoot-server</span> packages installed, and the <code class="systemitem">setroubleshootd</code> and <code class="systemitem">auditd</code> daemons are running, a yellow star and a warning are displayed when access is denied by SELinux. Clicking on the star launches the <code class="command">sealert</code> GUI, and displays denials in HTML output:
+				Si está corriendo el Sistema de Ventanas X, tenga los paquetes <span class="package">setroubleshoot</span> y <span class="package">setroubleshoot-server</span> instalados, y los demonios <code class="systemitem">setroubleshootd</code> y <code class="systemitem">auditd</code> ejecutándose, una estrella amarilla y una advertencia se muestran cuando un acceso es negado por SELinux. Con clic sobre la estrella se lanza <code class="command">sealert</code> modo gráfico y se muestra la negación como HTML:
 			</div><div class="mediaobject"><img src="./images/sealert_gui.png" /></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-						Run the <code class="command">sealert -b</code> command to launch the <code class="command">sealert</code> GUI.
+						Ejecute el comando <code class="command">sealert -b</code> para lanzar la GUI de <code class="command">sealert</code>.
 					</div></li><li class="listitem"><div class="para">
-						Run the <code class="command">sealert -l \*</code> command to view a detailed analysis of all denials.
+						Ejecute el comando <code class="command">sealert -l \*</code> para ver un análisis detallado de todas las negaciones.
 					</div></li><li class="listitem"><div class="para">
 						As the Linux root user, run the <code class="command">sealert -a /var/log/audit/audit.log -H &gt; audit.html</code> command to create a HTML version of the <code class="command">sealert</code> analysis, as seen with the <code class="command">sealert</code> GUI.
 					</div></li></ul></div><div class="para">
-				Refer to the <span class="citerefentry"><span class="refentrytitle">sealert</span>(8)</span> manual page for further <code class="command">sealert</code> options.
-			</div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id709472" href="#id709472" class="para">16</a>] </sup>
+				Vaya a la página man de <span class="citerefentry"><span class="refentrytitle">sealert</span>(8)</span> para más opciones de <code class="command">sealert</code>.
+			</div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id995602" href="#id995602" class="para">16</a>] </sup>
 						From the <span class="citerefentry"><span class="refentrytitle">ausearch</span>(8)</span> manual page, as shipped with the <span class="package">audit</span> package in Fedora 11.
-					</p></div><div class="footnote"><p><sup>[<a id="ftn.id709569" href="#id709569" class="para">17</a>] </sup>
+					</p></div><div class="footnote"><p><sup>[<a id="ftn.id793188" href="#id793188" class="para">17</a>] </sup>
 					From the <span class="citerefentry"><span class="refentrytitle">ausearch</span>(8)</span> manual page, as shipped with the <span class="package">audit</span> package in Fedora 11.
-				</p></div><div class="footnote"><p><sup>[<a id="ftn.id1639670" href="#id1639670" class="para">18</a>] </sup>
+				</p></div><div class="footnote"><p><sup>[<a id="ftn.id1128543" href="#id1128543" class="para">18</a>] </sup>
 						From the <span class="citerefentry"><span class="refentrytitle">aureport</span>(8)</span> manual page, as shipped with the <span class="package">audit</span> package in Fedora 11.
-					</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Permissive_Domains-Denials_for_Permissive_Domains.html"><strong>Anterior</strong>7.3.4.2. Denials for Permissive Domains</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages.html"><strong>Siguiente</strong>7.3.6. Raw Audit Messages</a></li></ul></body></html>
+					</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Permissive_Domains-Denials_for_Permissive_Domains.html"><strong>Anterior</strong>7.3.4.2. Negaciones para Dominios Permisivos</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages.html"><strong>Siguiente</strong>7.3.6. Raw Audit Messages</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages.html
index 67ca539..a6d478e 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages.html
@@ -1,12 +1,12 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.3.7. sealert Messages</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html" title="7.3. Fixing Problems" /><link rel="prev" href="sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages.html" title="7.3.6. Raw Audit Messages" /><link rel="next" href="sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow.html" title="7.3.8. Allowing Access: audit2allow" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe
  id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="7.3.7. sealert Messages" id="sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.3.7. sealert Messages</h3></div
 ></div></div><div class="para">
-				Denials are assigned IDs, as seen in <code class="filename">/var/log/messages</code>. The following is an example AVC denial (logged to <code class="filename">messages</code>) that occurred when the Apache HTTP Server (running in the <code class="computeroutput">httpd_t</code> domain) attempted to access the <code class="filename">/var/www/html/file1</code> file (labeled with the <code class="computeroutput">samba_share_t</code> type):
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.3.7. Mensajes sealert</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html" title="7.3. Corrección de Problemas" /><link rel="prev" href="sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages.html" title="7.3.6. Raw Audit Messages" /><link rel="next" href="sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow.html" title="7.3.8. Permitiendo el Acceso: audit2allow" /></head><body class="toc_embeded "><div id="tocdiv"
  class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="7.3.7. Mensajes sealert" id="sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.3.7. Mensaj
 es sealert</h3></div></div></div><div class="para">
+				Las negaciones tienen IDs asignados, como se ve en <code class="filename">/var/log/messages</code>. El siguiente es un ejemplo de negación AVC (guardado en <code class="filename">messages</code>) que ocurrió cuando el Servidor HTTP Apache (corriendo en el dominio <code class="computeroutput">httpd_t</code> domain) intentó acceder el <code class="filename">/var/www/html/archivo1</code> (etiquetado con el tipo <code class="computeroutput">samba_share_t</code>):
 			</div><pre class="screen">
 <em class="replaceable"><code>hostname</code></em> setroubleshoot: SELinux is preventing httpd (httpd_t) "getattr" to /var/www/html/file1 (samba_share_t). For complete SELinux messages. run sealert -l 84e0b04d-d0ad-4347-8317-22e74f6cd020
 
 </pre><div class="para">
-				As suggested, run the <code class="command">sealert -l 84e0b04d-d0ad-4347-8317-22e74f6cd020</code> command to view the complete message. This command only works on the local machine, and presents the same information as the <code class="command">sealert</code> GUI:
+				Como se sugirió, ejecute el comando <code class="command">sealert -l 84e0b04d-d0ad-4347-8317-22e74f6cd020</code> para ver el mensaje completo. Este comando sólo funciona en la máquina local, y presenta la misma información que la interfase gráfica de <code class="command">sealert</code>:
 			</div><pre class="screen">
 $ sealert -l 84e0b04d-d0ad-4347-8317-22e74f6cd020
 
@@ -64,16 +64,16 @@ node=<em class="replaceable"><code>hostname</code></em> type=AVC msg=audit(12258
 
 node=<em class="replaceable"><code>hostname</code></em> type=SYSCALL msg=audit(1225812178.788:101): arch=40000003 syscall=196 success=no exit=-13 a0=b8e97188 a1=bf87aaac a2=54dff4 a3=2008171 items=0 ppid=2439 pid=2441 auid=502 uid=48 gid=48 euid=48 suid=48 fsuid=48 egid=48 sgid=48 fsgid=48 tty=(none) ses=3 comm="httpd" exe="/usr/sbin/httpd" subj=unconfined_u:system_r:httpd_t:s0 key=(null)
 
-</pre><div class="variablelist"><dl><dt><span class="term">Summary</span></dt><dd><div class="para">
-							A brief summary of the denied action. This is the same as the denial in <code class="filename">/var/log/messages</code>. In this example, the <code class="systemitem">httpd</code> process was denied access to a file (<code class="filename">file1</code>), which is labeled with the <code class="computeroutput">samba_share_t</code> type.
-						</div></dd><dt><span class="term">Detailed Description</span></dt><dd><div class="para">
-							A more verbose description. In this example, <code class="filename">file1</code> is labeled with the <code class="computeroutput">samba_share_t</code> type. This type is used for files and directories that you want to export via Samba. The description suggests changing the type to a type that can be accessed by the Apache HTTP Server and Samba, if such access is desired.
-						</div></dd><dt><span class="term">Allowing Access</span></dt><dd><div class="para">
-							A suggestion for how to allow access. This may be relabeling files, turning a Boolean on, or making a local policy module. In this case, the suggestion is to label the file with a type accessible to both the Apache HTTP Server and Samba.
-						</div></dd><dt><span class="term">Fix Command</span></dt><dd><div class="para">
-							A suggested command to allow access and resolve the denial. In this example, it gives the command to change the <code class="filename">file1</code> type to <code class="computeroutput">public_content_t</code>, which is accessible to the Apache HTTP Server and Samba.
-						</div></dd><dt><span class="term">Additional Information</span></dt><dd><div class="para">
-							Information that is useful in bug reports, such as the policy package name and version (<code class="computeroutput">selinux-policy-3.5.13-11.fc11</code>), but may not help towards solving why the denial occurred.
+</pre><div class="variablelist"><dl><dt><span class="term">Resumen</span></dt><dd><div class="para">
+							Un breve resumen de la acción negada. Esto es lo mismo que la negación en <code class="filename">/var/log/messages</code>. En este ejemplo, al proceso <code class="systemitem">httpd</code> se le negó el acceso al (<code class="filename">archivo1</code>), que está etiquetado con el tipo <code class="computeroutput">samba_share_t</code>.
+						</div></dd><dt><span class="term">Descripción Detallada</span></dt><dd><div class="para">
+							Una descripción más detallada. En este ejemplo <code class="filename">archivo1</code> está etiquetado con el tipo <code class="computeroutput">samba_share_t</code>. Este tipo se usa para archivos y directorios que quiere exportar vía Samba. La descripción sugiere cambiar el tipo a un tipo que pueda ser accedido por Samba y por el Servidor HTTP Apache, si tal acceso es deseado.
+						</div></dd><dt><span class="term">Permitiendo Acceso</span></dt><dd><div class="para">
+							Una sugerencia sobre cómo permitir el acceso. Esto puede hacerse reetiquetando archivos, poniendo en 1 un Booleano, o creando un módulo de política local. En este caso, la sugerencia es etiquetar el archivo con un tipo accesible por el Servidor HTTP Apache y por Samba.
+						</div></dd><dt><span class="term">Comando para Corregir</span></dt><dd><div class="para">
+							Un comando sugerido para permitir el acceso y resolver la negación. En este ejemplo, se dá el comando para cambiar el tipo del <code class="filename">archivo1</code> a <code class="computeroutput">public_content_t</code>, que es accesible por el Servidor HTTP Apache y por Samba.
+						</div></dd><dt><span class="term">Información Adicional</span></dt><dd><div class="para">
+							Información que es útil en los informes de errores, como el nombre de paquete de política y la versión (<code class="computeroutput">selinux-policy-3.5.13-11.fc11</code>), pero que no puede ser de ayuda para resolver por qué ocurrió la negación.
 						</div></dd><dt><span class="term">Raw Audit Messages</span></dt><dd><div class="para">
 							The raw audit messages from <code class="filename">/var/log/audit/audit.log</code> that are associated with the denial. Refer to <a class="xref" href="sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages.html" title="7.3.6. Raw Audit Messages">Sección 7.3.6, “Raw Audit Messages”</a> for information about each item in the AVC denial.
-						</div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages.html"><strong>Anterior</strong>7.3.6. Raw Audit Messages</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow.html"><strong>Siguiente</strong>7.3.8. Allowing Access: audit2allow</a></li></ul></body></html>
+						</div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages.html"><strong>Anterior</strong>7.3.6. Raw Audit Messages</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow.html"><strong>Siguiente</strong>7.3.8. Permitiendo el Acceso: audit2allow</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Further_Information-Other_Resources.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Further_Information-Other_Resources.html
index 43f08d0..52c38c5 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Further_Information-Other_Resources.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Further_Information-Other_Resources.html
@@ -1,7 +1,7 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.2. Other Resources</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="chap-Security-Enhanced_Linux-Further_Information.html" title="Capítulo 8. Further Information" /><link rel="prev" href="chap-Security-Enhanced_Linux-Further_Information.html" title="Capítulo 8. Further Information" /><link rel="next" href="appe-Security-Enhanced_Linux-Revision_History.html" title="Apéndice A. Revision History" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../
 toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-Further_Information.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="appe-Security-Enhanced_Linux-Revision_History.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="8.2. Other Resources" id="sect-Security-Enhanced_Linux-Further_Information-Other_Resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">8.2. Other Resources</h2></div></div></div><div class="formalpara"><h5 class="formalpara">The National Security Agency 
 (NSA)</h5>
-				From the NSA <a href="http://www.nsa.gov/research/selinux/contrib.shtml">Contributors to SELinux</a> page:
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.2. Other Resources</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Further_Information.html" title="Capítulo 8. Información Adicional" /><link rel="prev" href="chap-Security-Enhanced_Linux-Further_Information.html" title="Capítulo 8. Información Adicional" /><link rel="next" href="appe-Security-Enhanced_Linux-Revision_History.html" title="Apéndice A. Revision History" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src=".
 ./../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-Further_Information.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="appe-Security-Enhanced_Linux-Revision_History.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="8.2. Other Resources" id="sect-Security-Enhanced_Linux-Further_Information-Other_Resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">8.2. Other Resources</h2></div></div></div><div class="formalpara" id="form-Security-Enhanced_Linux-Further_
 Information-The_National_Security_Agency_NSA"><h5 class="formalpara">La Agencia de Seguridad Nacional (NSA)</h5>
+				De la página <a href="http://www.nsa.gov/research/selinux/contrib.shtml">Contribuyentes de SELinux</a>:
 			</div><div class="para">
 			<span class="emphasis"><em>Researchers in NSA's National Information Assurance Research Laboratory (NIARL) designed and implemented flexible mandatory access controls in the major subsystems of the Linux kernel and implemented the new operating system components provided by the Flask architecture, namely the security server and the access vector cache. The NSA researchers reworked the LSM-based SELinux for inclusion in Linux 2.6. NSA has also led the development of similar controls for the X Window System (XACE/XSELinux) and for Xen (XSM/Flask).</em></span>
 		</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
@@ -10,34 +10,34 @@
 					SELinux documentation: <a href="http://www.nsa.gov/research/selinux/docs.shtml">http://www.nsa.gov/research/selinux/docs.shtml</a>.
 				</div></li><li class="listitem"><div class="para">
 					SELinux background: <a href="http://www.nsa.gov/research/selinux/background.shtml">http://www.nsa.gov/research/selinux/background.shtml</a>.
-				</div></li></ul></div><div class="formalpara"><h5 class="formalpara">Tresys Technology</h5>
-				<a href="http://www.tresys.com/">Tresys Technology</a> are the upstream for:
+				</div></li></ul></div><div class="formalpara" id="form-Security-Enhanced_Linux-Further_Information-Tresys_Technology"><h5 class="formalpara">Tecnología de Tresys</h5>
+				<a href="http://www.tresys.com/">Tresys Technology</a> son los desarrolladores de:
 			</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-					<a href="http://userspace.selinuxproject.org/trac/">SELinux userland libraries and tools</a>.
+					<a href="http://userspace.selinuxproject.org/trac/">Herramientas y bibliotecas en el espacio del usuario para SELinux</a>.
 				</div></li><li class="listitem"><div class="para">
-					<a href="http://oss.tresys.com/projects/refpolicy">SELinux Reference Policy</a>.
-				</div></li></ul></div><div class="formalpara"><h5 class="formalpara">SELinux News</h5>
+					<a href="http://oss.tresys.com/projects/refpolicy">Política de Referencia de SELinux</a>.
+				</div></li></ul></div><div class="formalpara" id="form-Security-Enhanced_Linux-Further_Information-SELinux_News"><h5 class="formalpara">Noticias de SELinux</h5>
 				<div class="itemizedlist"><ul><li class="listitem"><div class="para">
 							News: <a href="http://selinuxnews.org/wp/">http://selinuxnews.org/wp/</a>.
 						</div></li><li class="listitem"><div class="para">
 							Planet SELinux (blogs): <a href="http://selinuxnews.org/planet/">http://selinuxnews.org/planet/</a>.
 						</div></li></ul></div>
 
-			</div><div class="formalpara"><h5 class="formalpara">SELinux Project Wiki</h5>
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Further_Information-SELinux_Project_Wiki"><h5 class="formalpara">Wiki del Proyecto SELinux</h5>
 				<div class="itemizedlist"><ul><li class="listitem"><div class="para">
 							Main page: <a href="http://selinuxproject.org/page/Main_Page">http://selinuxproject.org/page/Main_Page</a>.
 						</div></li><li class="listitem"><div class="para">
 							User resources, including links to documentation, mailing lists, websites, and tools: <a href="http://selinuxproject.org/page/User_Resources">http://selinuxproject.org/page/User_Resources</a>.
 						</div></li></ul></div>
 
-			</div><div class="formalpara"><h5 class="formalpara">Red Hat Enterprise Linux</h5>
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Further_Information-Red_Hat_Enterprise_Linux"><h5 class="formalpara">Linux para Empresas de Red Hat</h5>
 				<div class="itemizedlist"><ul><li class="listitem"><div class="para">
-							The <a href="http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.2/html/Deployment_Guide/index.html">Red Hat Enterprise Linux Deployment Guide</a> contains an SELinux <a href="http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.2/html/Deployment_Guide/selg-chapter-0054.html">References</a> section, that has links to SELinux tutorials, general information, and the technology behind SELinux.
+							La <a href="http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.2/html/Deployment_Guide/index.html">Guía de Despliegue del Linux para Empresas de Red Hat</a> contiene una sección de <a href="http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.2/html/Deployment_Guide/selg-chapter-0054.html">Referencias</a> SELinux, que tiene enlaces a tutoriales de SELinux, información general y la tecnología detrás de SELinux.
 						</div></li><li class="listitem"><div class="para">
-							The <a href="http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/selinux-guide/index.html">Red Hat Enterprise Linux 4 SELinux Guide</a>.
+							La <a href="http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/selinux-guide/index.html">Guía de SELinux del Linux para Empresas de Red Hat 4</a>.
 						</div></li></ul></div>
 
-			</div><div class="formalpara"><h5 class="formalpara">Fedora</h5>
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Further_Information-Fedora"><h5 class="formalpara">Fedora</h5>
 				<div class="itemizedlist"><ul><li class="listitem"><div class="para">
 							Main page: <a href="http://fedoraproject.org/wiki/SELinux">http://fedoraproject.org/wiki/SELinux</a>.
 						</div></li><li class="listitem"><div class="para">
@@ -46,12 +46,12 @@
 							Fedora Core 5 SELinux FAQ: <a href="http://docs.fedoraproject.org/selinux-faq-fc5/">http://docs.fedoraproject.org/selinux-faq-fc5/</a>.
 						</div></li></ul></div>
 
-			</div><div class="formalpara"><h5 class="formalpara">The UnOfficial SELinux FAQ</h5>
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Further_Information-The_UnOfficial_SELinux_FAQ"><h5 class="formalpara">Las Preguntas Frecuentes No Oficiales de SELinux</h5>
 				<a href="http://www.crypt.gen.nz/selinux/faq.html">http://www.crypt.gen.nz/selinux/faq.html</a>
-			</div><div class="formalpara"><h5 class="formalpara">IRC</h5>
-				On <a href="http://freenode.net/">Freenode</a>:
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Further_Information-IRC"><h5 class="formalpara">IRC</h5>
+				En <a href="http://freenode.net/">Freenode</a>:
 			</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
 					#selinux
 				</div></li><li class="listitem"><div class="para">
 					#fedora-selinux
-				</div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-Further_Information.html"><strong>Anterior</strong>Capítulo 8. Further Information</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="appe-Security-Enhanced_Linux-Revision_History.html"><strong>Siguiente</strong>Apéndice A. Revision History</a></li></ul></body></html>
+				</div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-Further_Information.html"><strong>Anterior</strong>Capítulo 8. Información Adicional</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="appe-Security-Enhanced_Linux-Revision_History.html"><strong>Siguiente</strong>Apéndice A. Revision History</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Introduction-Examples.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Introduction-Examples.html
index a435948..876cde3 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Introduction-Examples.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Introduction-Examples.html
@@ -1,27 +1,27 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2. Examples</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="chap-Security-Enhanced_Linux-Introduction.html" title="Capítulo 2. Introduction" /><link rel="prev" href="chap-Security-Enhanced_Linux-Introduction.html" title="Capítulo 2. Introduction" /><link rel="next" href="sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture.html" title="2.3. SELinux Architecture" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an i
 frame, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-Introduction.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="2.2. Examples" id="sect-Security-Enhanced_Linux-Introduction-Examples"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.2. Examples</h2></div></div></div><div class="para">
-			The following examples demonstrate how SELinux increases security:
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2. Ejemplos</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Introduction.html" title="Capítulo 2. Introducción" /><link rel="prev" href="chap-Security-Enhanced_Linux-Introduction.html" title="Capítulo 2. Introducción" /><link rel="next" href="sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture.html" title="2.3. Arquitectura de SELinux" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">Th
 is is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-Introduction.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="2.2. Ejemplos" id="sect-Security-Enhanced_Linux-Introduction-Examples"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.2. Ejemplos</h2></div></div></div><div class="para">
+			Los siguientes ejemplos demuestran cómo SELinux aumenta la seguridad:
 		</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-					the default action is deny. If an SELinux policy rule does not exist to allow access, such as for a process opening a file, access is denied.
+					la acción por defecto es denegar. Si una regla de la política de SELinux no existe para permitir el acceso, como para que un proceso pueda abrir un archivo, el acceso es denegado.
 				</div></li><li class="listitem"><div class="para">
-					SELinux can confine Linux users. A number of confined SELinux users exist. Linux users can be mapped to SELinux users to take advantage of confined SELinux users. For example, mapping a Linux user to the SELinux user_u user, results in a Linux user that is not able to run (unless configured otherwise) set user ID (setuid) applications, such as <code class="command">sudo</code> and <code class="command">su</code>, as well as preventing them from executing files and applications in their home directory- if configured, this prevents users from executing malicious files from their home directories.
+					SELinux puede confinar a usuarios Linux. Existe un número de usuarios SELinux confinados. Los usuarios Linux se pueden mapear a usuarios SELinux para sacar ventaja de los usuarios SELinux confinados. Por ejemplo, mapear un usario Linux al usuario SELinux user_u, resulta en un usuario Linux que no puede ejecutar (a menos que se configure de otra forma) aplicaciones con el ID del usuario (setuid), tales como <code class="command">sudo</code> y <code class="command">su</code>, así como previene la ejecución de archivos y aplicaciones en sus directorios de inicio (home)- si se configura, esto evita que los usuarios ejecuten archivos maliciosos desde sus directorios de inicio.
 				</div></li><li class="listitem"><div class="para">
-					process separation. Processes run in their own domains, preventing processes from accessing files used by other processes, as well as processes accessing other processes. For example, when running SELinux, unless otherwise configured, an attacker can not compromise a Samba server, and then use that Samba server to read and write to files used by other processes, such as databases used by <span class="trademark">MySQL</span>®.
+					separación de procesos. Los procesos que corren en sus propios dominios, previenen que estos accedan a archivos usados por otros procesos, así como el acceso a otros procesos. Por ejemplo, cuando se ejecuta SELinux, a menos que se configure de otra forma, un atacante no puede comprometer un servidor Samba, y luego usar ese servidor Samba para leer y escribir archivos usados por otros procesos, tales como las bases de datos usadas por <span class="trademark">MySQL</span>®.
 				</div></li><li class="listitem"><div class="para">
-					help limit the damage done by configuration mistakes. <a href="http://en.wikipedia.org/wiki/Domain_Name_System">Domain Name System (DNS)</a> servers can replicate information between each other. This is known as a zone transfer. Attackers can use zone transfers to update DNS servers with false information. When running the <a href="https://www.isc.org/software/bind">Berkeley Internet Name Domain (BIND)</a> DNS server in Fedora 11, even if an administrator forgets to limit which servers can perform a zone transfer, the default SELinux policy prevents zone files <sup>[<a id="id454134" href="#ftn.id454134" class="footnote">3</a>]</sup> from being updated by zone transfers, the BIND <code class="systemitem">named</code> daemon, and other processes.
+					ayuda a limitar los daños hechos por errores en la configuración. Los servidores <a href="http://en.wikipedia.org/wiki/Domain_Name_System">Sistema de Nombres de Dominio (DNS)</a> pueden replicar información entre si. Esto se conoce como transferencia de zona. Los atacantes pueden usar las transferencias de zonas para actualizar los servidores de DNS con información falsa. Cuando se ejecuta el servidor de DNS <a href="https://www.isc.org/software/bind">Berkeley Internet Name Domain (BIND)</a> en Fedora 11, aún si un administrador se olvida de limitar qué servidores pueden realizar las transferencias de zona, la política predeterminada de SELinux evita que los archivos de zonas <sup>[<a id="id1135822" href="#ftn.id1135822" class="footnote">3</a>]</sup> sean actualizados por transferencias, por el demonio BIND <code class="systemitem">named</code> y por otros procesos.
 				</div></li><li class="listitem"><div class="para">
-					refer to the <a href="http://www.redhatmagazine.com/"><span class="trademark">Red Hat</span>® Magazine</a> article, <a href="http://www.redhatmagazine.com/2008/02/26/risk-report-three-years-of-red-hat-enterprise-linux-4/">Risk report: Three years of Red Hat Enterprise Linux 4</a><sup>[<a id="id454175" href="#ftn.id454175" class="footnote">4</a>]</sup>, for exploits that were restricted due to the default SELinux targeted policy in <span class="trademark">Red Hat</span>® Enterprise <span class="trademark">Linux</span>® 4.
+					refer to the <a href="http://www.redhatmagazine.com/"><span class="trademark">Red Hat</span>® Magazine</a> article, <a href="http://www.redhatmagazine.com/2008/02/26/risk-report-three-years-of-red-hat-enterprise-linux-4/">Risk report: Three years of Red Hat Enterprise Linux 4</a><sup>[<a id="id1135857" href="#ftn.id1135857" class="footnote">4</a>]</sup>, for exploits that were restricted due to the default SELinux targeted policy in <span class="trademark">Red Hat</span>® Enterprise <span class="trademark">Linux</span>® 4.
 				</div></li><li class="listitem"><div class="para">
-					refer to the <a href="http://www.linuxworld.com">LinuxWorld.com</a> article, <a href="http://www.linuxworld.com/news/2008/022408-selinux.html?page=1">A seatbelt for server software: SELinux blocks real-world exploits</a><sup>[<a id="id454223" href="#ftn.id454223" class="footnote">5</a>]</sup>, for background information about SELinux, and information about various exploits that SELinux has prevented.
+					refer to the <a href="http://www.linuxworld.com">LinuxWorld.com</a> article, <a href="http://www.linuxworld.com/news/2008/022408-selinux.html?page=1">A seatbelt for server software: SELinux blocks real-world exploits</a><sup>[<a id="id854101" href="#ftn.id854101" class="footnote">5</a>]</sup>, for background information about SELinux, and information about various exploits that SELinux has prevented.
 				</div></li><li class="listitem"><div class="para">
-					refer to James Morris's <a href="http://james-morris.livejournal.com/25421.html">SELinux mitigates remote root vulnerability in OpenPegasus</a> blog post, for information about an exploit in <a href="http://www.openpegasus.org/">OpenPegasus</a> that was mitigated by SELinux as shipped with Red Hat Enterprise Linux 4 and 5.
+					vaya al blog de James Morris <a href="http://james-morris.livejournal.com/25421.html">SELinux mitiga la vulnerabilidad de root en OpenPegasus</a>, para información acerca de una brecha en <a href="http://www.openpegasus.org/">OpenPegasus</a> que fue mitigada por SELinux tal como fue distribuido con el Linux para Empresas de Red Hat 4 y 5.
 				</div></li></ul></div><div class="para">
-			The <a href="http://www.tresys.com/">Tresys Technology</a> website has an <a href="http://www.tresys.com/innovation.php">SELinux Mitigation News</a> section (on the right-hand side), that lists recent exploits that have been mitigated or prevented by SELinux.
-		</div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id454134" href="#id454134" class="para">3</a>] </sup>
-						Text files that include information, such as hostname to IP address mappings, that are used by DNS servers.
-					</p></div><div class="footnote"><p><sup>[<a id="ftn.id454175" href="#id454175" class="para">4</a>] </sup>
+			El sitio web de <a href="http://www.tresys.com/">Tresys Technology</a> tiene una sección de <a href="http://www.tresys.com/innovation.php">Noticias de Migración a SELinux</a> (en la parte derecha), que lista los ataques recientes que fueron mitigados o prevenidos por SELinux.
+		</div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id1135822" href="#id1135822" class="para">3</a>] </sup>
+						Archivos de texto que incluyen información, tal como el mapeo de nombre de equipo a dirección IP, que usan los servidores de DNS.
+					</p></div><div class="footnote"><p><sup>[<a id="ftn.id1135857" href="#id1135857" class="para">4</a>] </sup>
 						Cox, Mark. "Risk report: Three years of Red Hat Enterprise Linux 4". Published 26 February 2008. Accessed 28 August 2008: <a href="http://www.redhatmagazine.com/2008/02/26/risk-report-three-years-of-red-hat-enterprise-linux-4/">http://www.redhatmagazine.com/2008/02/26/risk-report-three-years-of-red-hat-enterprise-linux-4/</a>.
-					</p></div><div class="footnote"><p><sup>[<a id="ftn.id454223" href="#id454223" class="para">5</a>] </sup>
+					</p></div><div class="footnote"><p><sup>[<a id="ftn.id854101" href="#id854101" class="para">5</a>] </sup>
 						Marti, Don. "A seatbelt for server software: SELinux blocks real-world exploits". Published 24 February 2008. Accessed 28 August 2008: <a href="http://www.linuxworld.com/news/2008/022408-selinux.html?page=1">http://www.linuxworld.com/news/2008/022408-selinux.html?page=1</a>.
-					</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-Introduction.html"><strong>Anterior</strong>Capítulo 2. Introduction</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture.html"><strong>Siguiente</strong>2.3. SELinux Architecture</a></li></ul></body></html>
+					</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-Introduction.html"><strong>Anterior</strong>Capítulo 2. Introducción</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture.html"><strong>Siguiente</strong>2.3. Arquitectura de SELinux</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture.html
index 6666d13..b893a97 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture.html
@@ -1,7 +1,7 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.3. SELinux Architecture</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="chap-Security-Enhanced_Linux-Introduction.html" title="Capítulo 2. Introduction" /><link rel="prev" href="sect-Security-Enhanced_Linux-Introduction-Examples.html" title="2.2. Examples" /><link rel="next" href="sect-Security-Enhanced_Linux-Introduction-SELinux_on_Other_Operating_Systems.html" title="2.4. SELinux on Other Operating Systems" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" sr
 c="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Introduction-Examples.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Introduction-SELinux_on_Other_Operating_Systems.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="2.3. SELinux Architecture" id="sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.3. SELinux Architecture</h2></div></div></div><div class="para">
-			SELinux is a Linux security module that is built into the Linux kernel. SELinux is driven by loadable policy rules. When security-relevant access is taking place, such as when a process attempts to open a file, the operation is intercepted in the kernel by SELinux. If an SELinux policy rule allows the operation, it continues, otherwise, the operation is blocked and the process receives an error.
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.3. Arquitectura de SELinux</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Introduction.html" title="Capítulo 2. Introducción" /><link rel="prev" href="sect-Security-Enhanced_Linux-Introduction-Examples.html" title="2.2. Ejemplos" /><link rel="next" href="sect-Security-Enhanced_Linux-Introduction-SELinux_on_Other_Operating_Systems.html" title="2.4. SELinux en otros Sistemas Operativos" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" cla
 ss="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Introduction-Examples.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Introduction-SELinux_on_Other_Operating_Systems.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="2.3. Arquitectura de SELinux" id="sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.3. Arquitectura de SELinux</h2></div></div></div><di
 v class="para">
+			SELinux es un módulo de seguridad de Linux que se construye dentro del kernel de Linux. SELinux se maneja por reglas de políticas cargables. Cuando un acceso de seguridad relevante se lleva a cabo, tal como un proceso que trata de abrir un archivo, la operación es interceptada por SELinux en el kernel. Si una regla de política de SELinux permite la operación, continúa, sino, la operación se bloquea y el proceso recibe un error.
 		</div><div class="para">
-			SELinux decisions, such as allowing or disallowing access, are cached. This cache is known as the Access Vector Cache (AVC). Caching decisions decreases how often SELinux policy rules need to be checked, which increases performance. SELinux policy rules have no effect if DAC rules deny access first.
-		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Introduction-Examples.html"><strong>Anterior</strong>2.2. Examples</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Introduction-SELinux_on_Other_Operating_Systems.html"><strong>Siguiente</strong>2.4. SELinux on Other Operating Systems</a></li></ul></body></html>
+			Las decisiones de SELinux, tales como permitir o negar accesos, son cacheadas. Este caché se conoce como Caché Vector de Acceso (AVC). Las decisiones de cacheado disminuye la necesidad de que las reglas de políticas de SELinux sean chequeadas muy a menudo, lo que mejora la performance. Las reglas de políticas de SELinux no tienen efecto si las reglas DAC niegan el acceso primero.
+		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Introduction-Examples.html"><strong>Anterior</strong>2.2. Ejemplos</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Introduction-SELinux_on_Other_Operating_Systems.html"><strong>Siguiente</strong>2.4. SELinux en otros Sistemas Operativos</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Introduction-SELinux_on_Other_Operating_Systems.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Introduction-SELinux_on_Other_Operating_Systems.html
index 1e9d4ff..afaf730 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Introduction-SELinux_on_Other_Operating_Systems.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Introduction-SELinux_on_Other_Operating_Systems.html
@@ -1,7 +1,7 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.4. SELinux on Other Operating Systems</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="chap-Security-Enhanced_Linux-Introduction.html" title="Capítulo 2. Introduction" /><link rel="prev" href="sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture.html" title="2.3. SELinux Architecture" /><link rel="next" href="chap-Security-Enhanced_Linux-SELinux_Contexts.html" title="Capítulo 3. SELinux Contexts" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="
 ../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-SELinux_Contexts.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="2.4. SELinux on Other Operating Systems" id="sect-Security-Enhanced_Linux-Introduction-SELinux_on_Other_Operating_Systems"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.4. SELinux on Other Operating Systems</h2></div></div></div>
 <div class="para">
-			Refer to the following for information about running SELinux on operating systems:
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.4. SELinux en otros Sistemas Operativos</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Introduction.html" title="Capítulo 2. Introducción" /><link rel="prev" href="sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture.html" title="2.3. Arquitectura de SELinux" /><link rel="next" href="chap-Security-Enhanced_Linux-SELinux_Contexts.html" title="Capítulo 3. Contextos de SELinux" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" cl
 ass="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-SELinux_Contexts.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="2.4. SELinux en otros Sistemas Operativos" id="sect-Security-Enhanced_Linux-Introduction-SELinux_on_Other_Operating_Systems"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.4. SELinux en otros Sistemas Operativos</h2
 ></div></div></div><div class="para">
+			Vaya a la siguiente información sobre cómo correr SELinux en sistemas operativos:
 		</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
 					Hardened Gentoo: <a href="http://www.gentoo.org/proj/en/hardened/selinux/selinux-handbook.xml">http://www.gentoo.org/proj/en/hardened/selinux/selinux-handbook.xml</a>.
 				</div></li><li class="listitem"><div class="para">
@@ -9,7 +9,7 @@
 				</div></li><li class="listitem"><div class="para">
 					Ubuntu: <a href="https://wiki.ubuntu.com/SELinux">https://wiki.ubuntu.com/SELinux</a> and <a href="https://help.ubuntu.com/community/SELinux">https://help.ubuntu.com/community/SELinux</a>.
 				</div></li><li class="listitem"><div class="para">
-					Red Hat Enterprise Linux: <a href="http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.2/html/Deployment_Guide/selg-overview.html">Red Hat Enterprise Linux Deployment Guide</a> and <a href="http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/selinux-guide/">Red Hat Enterprise Linux 4 SELinux Guide</a>.
+					Linux para Empresas de Red Hat: <a href="http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.2/html/Deployment_Guide/selg-overview.html">Guía de Despliegue del Linux para Empresas de Red Hat</a> y la <a href="http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/selinux-guide/">Guía de SELinux para el Linux para Empresas de Red Hat</a>.
 				</div></li><li class="listitem"><div class="para">
 					Fedora: <a href="http://fedoraproject.org/wiki/SELinux">http://fedoraproject.org/wiki/SELinux</a> and the <a href="http://docs.fedoraproject.org/selinux-faq-fc5/">Fedora Core 5 SELinux FAQ</a>.
-				</div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture.html"><strong>Anterior</strong>2.3. SELinux Architecture</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-SELinux_Contexts.html"><strong>Siguiente</strong>Capítulo 3. SELinux Contexts</a></li></ul></body></html>
+				</div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture.html"><strong>Anterior</strong>2.3. Arquitectura de SELinux</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-SELinux_Contexts.html"><strong>Siguiente</strong>Capítulo 3. Contextos de SELinux</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_star.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_star.html
index 3de6515..685ad67 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_star.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_star.html
@@ -1,11 +1,11 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.10.5. Archiving Files with star</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html" title="5.10. Maintaining SELinux Labels" /><link rel="prev" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_tar.html" title="5.10.4. Archiving Files with tar" /><link rel="next" href="chap-Security-Enhanced_Linux-Confining_Users.html" title="Capítulo 6. Confining Users" /></head><body class="toc_embeded "><div id
 ="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_tar.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-Confining_Users.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.10.5. Archiving Files with star" id="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_star"><div class="titlepage"><div><div keep-together.within-column="always"><
 h3 class="title">5.10.5. Archiving Files with star</h3></div></div></div><div class="para">
-				<code class="command">star</code> does not retain extended attributes by default. Since SELinux contexts are stored in extended attributes, contexts can be lost when archiving files. Use <code class="command">star -xattr -H=exustar</code> to create archives that retain contexts. The <span class="package">star</span> package is not installed by default. To install <code class="command">star</code>, run the <code class="command">yum install star</code> command as the Linux root user.
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.10.5. Archivando archivos con tar</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html" title="5.10. Mantención de las Etiquetas de SELinux" /><link rel="prev" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_tar.html" title="5.10.4. Archivando archivos con tar" /><link rel="next" href="chap-Security-Enhanced_Linux-Confining_Users.html" title="Capítulo 6. Confinando a los Usuarios" /></head><
 body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_tar.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-Confining_Users.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.10.5. Archivando archivos con tar" id="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_star"><div class="titlepage"><div><div kee
 p-together.within-column="always"><h3 class="title">5.10.5. Archivando archivos con tar</h3></div></div></div><div class="para">
+				<code class="command">star</code> no retiene los atributos extendidos por defecto. Dado que los contextos SELinux se almacenan en los atributos extendidos, los contextos se pueden perder cuando se crean esos archivos. Use <code class="command">star -xattr -H=exustar</code> para crear archivos que retengan los contextos. El paquete <span class="package">star</span> no se instala por defecto. Para instalar <code class="command">star</code>, ejecute el comando <code class="command">yum install star</code> como usuario root de Linux.
 			</div><div class="para">
-				The following example demonstrates creating a Star archive that retains SELinux contexts:
+				El siguiente ejemplo muestra la creación de un archivo Star que retiene los contextos SELinux:
 			</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">touch /var/www/html/file{1,2,3}</code> command to create three files (<code class="filename">file1</code>, <code class="filename">file2</code>, and <code class="filename">file3</code>). These files inherit the <code class="computeroutput">httpd_sys_content_t</code> type from the <code class="filename">/var/www/html/</code> directory:
+						Como usuario root de Linux, ejecute el comando <code class="command">touch /var/www/html/archivo{1,2,3}</code> para crear tres archivos (<code class="filename">archivo1</code>, <code class="filename">archivo2</code> y <code class="filename">archivo3</code>). Estos heredan el tipo <code class="computeroutput">httpd_sys_content_t</code> del directorio <code class="filename">/var/www/html/</code>:
 					</div><pre class="screen">
 # touch /var/www/html/file{1,2,3}
 # ls -Z /var/www/html/
@@ -14,23 +14,23 @@
 -rw-r--r--  root root unconfined_u:object_r:httpd_sys_content_t:s0 file3
 
 </pre></li><li class="listitem"><div class="para">
-						Run the <code class="command">cd /var/www/html/</code> command to change into the <code class="filename">/var/www/html/</code> directory. Once in this directory, as the Linux root user, run the <code class="command">star -xattr -H=exustar -c -f=test.star file{1,2,3}</code> command to create a Star archive named <code class="filename">test.star</code>:
+						Ejecute el comando <code class="command">cd /var/www/html/</code> para cambiar al directorio <code class="filename">/var/www/html/</code>. Una vez en este directorio, como usuario root de Linux ejecute el comando <code class="command">star -xattr -H=exustar -c -f=prueba.star archivo{1,2,3}</code> para crear un archivo Star llamado <code class="filename">prueba.star</code>:
 					</div><pre class="screen">
 # star -xattr -H=exustar -c -f=test.star file{1,2,3}
 star: 1 blocks + 0 bytes (total of 10240 bytes = 10.00k).
 
 </pre></li><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">mkdir /test</code> command to create a new directory, and then, run the <code class="command">chmod 777 /test/</code> command to allow all users full-access to the <code class="filename">/test/</code> directory.
+						Como usuario root de Linux, corra el comando <code class="command">mkdir /prueba</code> para crear un directorio nuevo, y luego ejecute el comando <code class="command">chmod 777 /prueba/</code> para permitir a los usuarios acceso total al directorio <code class="filename">/prueba/</code>.
 					</div></li><li class="listitem"><div class="para">
-						Run the <code class="command">cp /var/www/html/test.star /test/</code> command to copy the <code class="filename">test.star</code> file in to the <code class="filename">/test/</code> directory.
+						Ejecute el comando <code class="command">cp /var/www/html/prueba.star /prueba/</code> para copiar el archivo <code class="filename">prueba.star</code> al directorio <code class="filename">/prueba/</code>.
 					</div></li><li class="listitem"><div class="para">
-						Run the <code class="command">cd /test/</code> command to change into the <code class="filename">/test/</code> directory. Once in this directory, run the <code class="command">star -x -f=test.star</code> command to extract the Star archive:
+						Ejecute el comando <code class="command">cd /prueba/</code> para cambiar al directorio <code class="filename">/prueba/</code>. Una vez ahí, ejecute el comando <code class="command">star -x -f=prueba.star</code> para extraer el archivo Star:
 					</div><pre class="screen">
 $ star -x -f=test.star 
 star: 1 blocks + 0 bytes (total of 10240 bytes = 10.00k).
 
 </pre></li><li class="listitem"><div class="para">
-						Run the <code class="command">ls -lZ /test/</code> command to view the SELinux contexts. The <code class="computeroutput">httpd_sys_content_t</code> type has been retained, rather than being changed to <code class="computeroutput">default_t</code>, which would have happened had the <code class="option">--selinux</code> not been used:
+						Ejecute el comando <code class="command">ls -lZ /prueba/</code> para ver los contextos SELinux. El tipo <code class="computeroutput">httpd_sys_content_t</code> fue retenido, en vez de haberse cambiado al <code class="computeroutput">default_t</code>, lo que hubiera pasado si la opción <code class="option">--selinux</code> no se hubiera usado:
 					</div><pre class="screen">
 $ ls -lZ /test/
 -rw-r--r--  user1 group1 unconfined_u:object_r:httpd_sys_content_t:s0 file1
@@ -39,9 +39,9 @@ $ ls -lZ /test/
 -rw-r--r--  user1 group1 unconfined_u:object_r:default_t:s0 test.star
 
 </pre></li><li class="listitem"><div class="para">
-						If the <code class="filename">/test/</code> directory is no longer required, as the Linux root user, run the <code class="command"> rm -ri /test/</code> command to remove it, as well as all files in it.
+						Si el directorio <code class="filename">/prueba/</code> no se necesita más, como usuario root de Linux ejecute el comando <code class="command"> rm -ri /prueba/</code> para eliminarlo, así como todos los archivos en él.
 					</div></li><li class="listitem"><div class="para">
-						If <code class="command">star</code> is no longer required, as the Linux root user, run the <code class="command">yum remove star</code> command to remove the package.
+						Si <code class="command">star</code> ya no se necesita, como usuario root de Linux, ejecute el comando <code class="command">yum remove star</code> para eliminar el paquete.
 					</div></li></ol></div><div class="para">
-				Refer to the <span class="citerefentry"><span class="refentrytitle">star</span>(1)</span> manual page for further information about <code class="command">star</code>.
-			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_tar.html"><strong>Anterior</strong>5.10.4. Archiving Files with tar</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-Confining_Users.html"><strong>Siguiente</strong>Capítulo 6. Confining Users</a></li></ul></body></html>
+				Vaya a la página man de <span class="citerefentry"><span class="refentrytitle">star</span>(1)</span> para más información acerca de <code class="command">star</code>.
+			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_tar.html"><strong>Anterior</strong>5.10.4. Archivando archivos con tar</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-Confining_Users.html"><strong>Siguiente</strong>Capítulo 6. Confinando a los Usuarios</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_tar.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_tar.html
index 59fe256..e38cd9a 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_tar.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_tar.html
@@ -1,16 +1,16 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.10.4. Archiving Files with tar</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html" title="5.10. Maintaining SELinux Labels" /><link rel="prev" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context.html" title="5.10.3. Checking the Default SELinux Context" /><link rel="next" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_star.html" title="5.10.5. Arch
 iving Files with star" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_star.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.10.4. Archiving Files with tar" id="sect-Security-Enhanced_Linux-Maintaining
 _SELinux_Labels_-Archiving_Files_with_tar"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.10.4. Archiving Files with tar</h3></div></div></div><div class="para">
-				<code class="command">tar</code> does not retain extended attributes by default. Since SELinux contexts are stored in extended attributes, contexts can be lost when archiving files. Use <code class="command">tar --selinux</code> to create archives that retain contexts. If a Tar archive contains files without extended attributes, or if you want the extended attributes to match the system defaults, run the archive through <code class="command">/sbin/restorecon</code>:
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.10.4. Archivando archivos con tar</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html" title="5.10. Mantención de las Etiquetas de SELinux" /><link rel="prev" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context.html" title="5.10.3. Chequeando el Contexto SELinux Predeterminado" /><link rel="next" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_
 star.html" title="5.10.5. Archivando archivos con tar" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_star.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.10.4. Archivando archivos con tar" id="sect-
 Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_tar"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.10.4. Archivando archivos con tar</h3></div></div></div><div class="para">
+				<code class="command">tar</code> no retiene los atributos extendidos por defecto. Dado que los contextos SELinux se almacenan en los atributos extendidos, los contextos se pueden perder cuando se compactan archivos. Use <code class="command">tar --selinux</code> para crear archivos que retengan los contextos. Si un archivo Tar contiene archivos sin los atributos extendidos, o si quiere que los atributos extendidos coincidan con los predeterminados del sistema, ejecute el archivado a través de <code class="command">/sbin/restorecon</code>:
 			</div><pre class="screen">
 $ tar -xvf <em class="replaceable"><code>archive.tar</code></em> | /sbin/restorecon -f -
 
 </pre><div class="para">
-				Note: depending on the directory, you may need to be the Linux root user to run the <code class="command">/sbin/restorecon</code> command.
+				Nota: dependiendo del directorio, puede necesitar ser el usuario root de Linux para ejecutar el comando <code class="command">/sbin/restorecon</code>.
 			</div><div class="para">
-				The following example demonstrates creating a Tar archive that retains SELinux contexts:
+				El siguiente ejemplo muestra la creación de un archivo Tar que mantiene sus contextos SELinux:
 			</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">touch /var/www/html/file{1,2,3}</code> command to create three files (<code class="filename">file1</code>, <code class="filename">file2</code>, and <code class="filename">file3</code>). These files inherit the <code class="computeroutput">httpd_sys_content_t</code> type from the <code class="filename">/var/www/html/</code> directory:
+						Como usuario root de Linux, ejecute el comando <code class="command">touch /var/www/html/archivo{1,2,3}</code> para crear tres archivos (<code class="filename">archivo1</code>, <code class="filename">archivo2</code> y <code class="filename">archivo3</code>). Estos heredan el tipo <code class="computeroutput">httpd_sys_content_t</code> del directorio <code class="filename">/var/www/html/</code>:
 					</div><pre class="screen">
 # touch /var/www/html/file{1,2,3}
 # ls -Z /var/www/html/
@@ -19,15 +19,15 @@ $ tar -xvf <em class="replaceable"><code>archive.tar</code></em> | /sbin/restore
 -rw-r--r--  root root unconfined_u:object_r:httpd_sys_content_t:s0 file3
 
 </pre></li><li class="listitem"><div class="para">
-						Run the <code class="command">cd /var/www/html/</code> command to change into the <code class="filename">/var/www/html/</code> directory. Once in this directory, as the Linux root user, run the <code class="command">tar --selinux -cf test.tar file{1,2,3}</code> command to create a Tar archive named <code class="filename">test.tar</code>.
+						Ejecute el comando <code class="command">cd /var/www/html/</code> para cambiar al directorio <code class="filename">/var/www/html/</code>. Una vez en este directorio, como usuario root de Linux ejecute el comando <code class="command">tar --selinux -cf prueba.tar archivo{1,2,3}</code> para crear un archivo Tar con nombre <code class="filename">prueba.tar</code>.
 					</div></li><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">mkdir /test</code> command to create a new directory, and then, run the <code class="command">chmod 777 /test/</code> command to allow all users full-access to the <code class="filename">/test/</code> directory.
+						Como usuario root de Linux, corra el comando <code class="command">mkdir /prueba</code> para crear un directorio nuevo, y luego ejecute el comando <code class="command">chmod 777 /prueba/</code> para permitir a los usuarios acceso total al directorio <code class="filename">/prueba/</code>.
 					</div></li><li class="listitem"><div class="para">
-						Run the <code class="command">cp /var/www/html/test.tar /test/</code> command to copy the <code class="filename">test.tar</code> file in to the <code class="filename">/test/</code> directory.
+						Ejecute el comando <code class="command">cp /var/www/html/prueba.tar /prueba/</code> para copiar el archivo <code class="filename">prueba.tar</code> en el directorio <code class="filename">/prueba/</code>.
 					</div></li><li class="listitem"><div class="para">
-						Run the <code class="command">cd /test/</code> command to change into the <code class="filename">/test/</code> directory. Once in this directory, run the <code class="command">tar -xvf test.tar</code> command to extract the Tar archive.
+						Ejecute el comando <code class="command">cd /prueba/</code> para cambiar al directorio <code class="filename">/test/</code>. Una vez ahí, ejecute el comando <code class="command">tar -xvf prueba.tar</code> para extraer el archivo Tar.
 					</div></li><li class="listitem"><div class="para">
-						Run the <code class="command">ls -lZ /test/</code> command to view the SELinux contexts. The <code class="computeroutput">httpd_sys_content_t</code> type has been retained, rather than being changed to <code class="computeroutput">default_t</code>, which would have happened had the <code class="option">--selinux</code> not been used:
+						Ejecute el comando <code class="command">ls -lZ /prueba/</code> para ver los contextos SELinux. El tipo <code class="computeroutput">httpd_sys_content_t</code> fue retenido, en vez de haberse cambiado al <code class="computeroutput">default_t</code>, lo que hubiera pasado si la opción <code class="option">--selinux</code> no se hubiera usado:
 					</div><pre class="screen">
 $ ls -lZ /test/
 -rw-r--r--  user1 group1 unconfined_u:object_r:httpd_sys_content_t:s0 file1
@@ -36,7 +36,7 @@ $ ls -lZ /test/
 -rw-r--r--  user1 group1 unconfined_u:object_r:default_t:s0 test.tar
 
 </pre></li><li class="listitem"><div class="para">
-						If the <code class="filename">/test/</code> directory is no longer required, as the Linux root user, run the <code class="command"> rm -ri /test/</code> command to remove it, as well as all files in it.
+						Si el directorio <code class="filename">/prueba/</code> no se necesita más, como usuario root de Linux ejecute el comando <code class="command"> rm -ri /prueba/</code> para eliminarlo, así como todos los archivos en él.
 					</div></li></ol></div><div class="para">
-				Refer to the <span class="citerefentry"><span class="refentrytitle">tar</span>(1)</span> manual page for further information about <code class="command">tar</code>, such as the <code class="option">--xattrs</code> option that retains all extended attributes.
-			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context.html"><strong>Anterior</strong>5.10.3. Checking the Default SELinux Context</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_star.html"><strong>Siguiente</strong>5.10.5. Archiving Files with star</a></li></ul></body></html>
+				Vaya a la página man de <span class="citerefentry"><span class="refentrytitle">tar</span>(1)</span> para información adicional de <code class="command">tar</code>, tal como la opción <code class="option">--xattrs</code> para retener todos los atributos extendidos.
+			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context.html"><strong>Anterior</strong>5.10.3. Chequeando el Contexto SELinux Predetermi...</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_star.html"><strong>Siguiente</strong>5.10.5. Archivando archivos con tar</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context.html
index 3814f0a..fce79f7 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context.html
@@ -1,9 +1,9 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.10.3. Checking the Default SELinux Context</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html" title="5.10. Maintaining SELinux Labels" /><link rel="prev" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Moving_Files_and_Directories.html" title="5.10.2. Moving Files and Directories" /><link rel="next" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_tar.html" title="5.10.4. Archiving
  Files with tar" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Moving_Files_and_Directories.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_tar.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.10.3. Checking the Default SELinux Context" id="sect-Security-Enhanced_Linux-Maintaining_SE
 Linux_Labels_-Checking_the_Default_SELinux_Context"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.10.3. Checking the Default SELinux Context</h3></div></div></div><div class="para">
-				Use the <code class="command">/usr/sbin/matchpathcon</code> command to check if files and directories have the correct SELinux context. From the <span class="citerefentry"><span class="refentrytitle">matchpathcon</span>(8)</span> manual page: "<code class="command">matchpathcon</code> queries the system policy and outputs the default security context associated with the file path."<sup>[<a id="id485828" href="#ftn.id485828" class="footnote">13</a>]</sup>. The following example demonstrates using the <code class="command">/usr/sbin/matchpathcon</code> command to verify that files in <code class="filename">/var/www/html/</code> directory are labeled correctly:
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.10.3. Chequeando el Contexto SELinux Predeterminado</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html" title="5.10. Mantención de las Etiquetas de SELinux" /><link rel="prev" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Moving_Files_and_Directories.html" title="5.10.2. Movimiento de Archivos y Directorios" /><link rel="next" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with
 _tar.html" title="5.10.4. Archivando archivos con tar" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Moving_Files_and_Directories.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_tar.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.10.3. Chequeando el Contexto SELinux Predeterminado" 
 id="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.10.3. Chequeando el Contexto SELinux Predeterminado</h3></div></div></div><div class="para">
+				Use the <code class="command">/usr/sbin/matchpathcon</code> command to check if files and directories have the correct SELinux context. From the <span class="citerefentry"><span class="refentrytitle">matchpathcon</span>(8)</span> manual page: "<code class="command">matchpathcon</code> queries the system policy and outputs the default security context associated with the file path."<sup>[<a id="id811224" href="#ftn.id811224" class="footnote">13</a>]</sup>. The following example demonstrates using the <code class="command">/usr/sbin/matchpathcon</code> command to verify that files in <code class="filename">/var/www/html/</code> directory are labeled correctly:
 			</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">touch /var/www/html/file{1,2,3}</code> command to create three files (<code class="filename">file1</code>, <code class="filename">file2</code>, and <code class="filename">file3</code>). These files inherit the <code class="computeroutput">httpd_sys_content_t</code> type from the <code class="filename">/var/www/html/</code> directory:
+						Como usuario root de Linux, ejecute el comando <code class="command">touch /var/www/html/archivo{1,2,3}</code> para crear tres archivos (<code class="filename">archivo1</code>, <code class="filename">archivo2</code> y <code class="filename">archivo3</code>). Estos heredan el tipo <code class="computeroutput">httpd_sys_content_t</code> del directorio <code class="filename">/var/www/html/</code>:
 					</div><pre class="screen"># touch /var/www/html/file{1,2,3}
 # ls -Z /var/www/html/
 -rw-r--r--  root root unconfined_u:object_r:httpd_sys_content_t:s0 file1
@@ -11,23 +11,23 @@
 -rw-r--r--  root root unconfined_u:object_r:httpd_sys_content_t:s0 file3
 
 </pre></li><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">chcon -t samba_share_t /var/www/html/file1</code> command to change the <code class="filename">file1</code> type to <code class="computeroutput">samba_share_t</code>. Note: the Apache HTTP Server can not read files or directories labeled with the <code class="computeroutput">samba_share_t</code> type.
+						Como usuario root de Linux, ejecute el comando <code class="command">chcon -t samba_share_t /var/www/html/archivo1</code> para cambiar el tipo del <code class="filename">archivo1</code> a <code class="computeroutput">samba_share_t</code>. Nota: El Servidor HTTP Apache no puede leer archivos o directorios etiquetados con el tipo <code class="computeroutput">samba_share_t</code>.
 					</div></li><li class="listitem"><div class="para">
-						The <code class="command">/usr/sbin/matchpathcon</code> <code class="option">-V</code> option compares the current SELinux context to the correct, default context in SELinux policy. Run the <code class="command">/usr/sbin/matchpathcon -V /var/www/html/*</code> command to check all files in the <code class="filename">/var/www/html/</code> directory:
+						La opción <code class="command">/usr/sbin/matchpathcon</code> <code class="option">-V</code> compara el contexto SELinux actual con el contexto predeterminado correcto dado por la política de SELinux. Ejecute el comando <code class="command">/usr/sbin/matchpathcon -V /var/www/html/*</code> para chequear todos los archivos del directorio <code class="filename">/var/www/html/</code>:
 					</div><pre class="screen">$ /usr/sbin/matchpathcon -V /var/www/html/*
 /var/www/html/file1 has context unconfined_u:object_r:samba_share_t:s0, should be system_u:object_r:httpd_sys_content_t:s0
 /var/www/html/file2 verified.
 /var/www/html/file3 verified.
 
 </pre></li></ol></div><div class="para">
-				The following output from the <code class="command">/usr/sbin/matchpathcon</code> command explains that <code class="filename">file1</code> is labeled with the <code class="computeroutput">samba_share_t</code> type, but should be labeled with the <code class="computeroutput">httpd_sys_content_t</code> type:
+				La siguiente salida del comando <code class="command">/usr/sbin/matchpathcon</code> explica que el <code class="filename">archivo1</code> está etiquetado con el tipo <code class="computeroutput">samba_share_t</code>, pero debería estar etiquetado con el tipo <code class="computeroutput">httpd_sys_content_t</code>:
 			</div><pre class="screen">/var/www/html/file1 has context unconfined_u:object_r:samba_share_t:s0, should be system_u:object_r:httpd_sys_content_t:s0
 
 </pre><div class="para">
-				To resolve the label problem and allow the Apache HTTP Server access to <code class="filename">file1</code>, as the Linux root user, run the <code class="command">/sbin/restorecon -v /var/www/html/file1</code> command:
+				Para resolver el problema de etiqueta y permitir al Servidor HTTP Apache acceder a <code class="filename">archivo1</code>, como usuario root de Linux corra el comando <code class="command">/sbin/restorecon -v /var/www/html/archivo1</code>:
 			</div><pre class="screen"># /sbin/restorecon -v /var/www/html/file1
 restorecon reset /var/www/html/file1 context unconfined_u:object_r:samba_share_t:s0-&gt;system_u:object_r:httpd_sys_content_t:s0
 
-</pre><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id485828" href="#id485828" class="para">13</a>] </sup>
+</pre><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id811224" href="#id811224" class="para">13</a>] </sup>
 					The <span class="citerefentry"><span class="refentrytitle">matchpathcon</span>(8)</span> manual page, as shipped with the <span class="package">libselinux-utils</span> package in Fedora, is written by Daniel Walsh. Any edits or changes in this version were done by Murray McAllister.
-				</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Moving_Files_and_Directories.html"><strong>Anterior</strong>5.10.2. Moving Files and Directories</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_tar.html"><strong>Siguiente</strong>5.10.4. Archiving Files with tar</a></li></ul></body></html>
+				</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Moving_Files_and_Directories.html"><strong>Anterior</strong>5.10.2. Movimiento de Archivos y Directorios</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_tar.html"><strong>Siguiente</strong>5.10.4. Archivando archivos con tar</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Moving_Files_and_Directories.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Moving_Files_and_Directories.html
index a65c2b1..25bd7a0 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Moving_Files_and_Directories.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Moving_Files_and_Directories.html
@@ -1,27 +1,27 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.10.2. Moving Files and Directories</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html" title="5.10. Maintaining SELinux Labels" /><link rel="prev" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html" title="5.10. Maintaining SELinux Labels" /><link rel="next" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context.html" title="5.10.3. Checking the Defa
 ult SELinux Context" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.10.2. Moving Files and Directories" id="sect-Security-Enhanced_Linux-Maintaining_SE
 Linux_Labels_-Moving_Files_and_Directories"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.10.2. Moving Files and Directories</h3></div></div></div><div class="para">
-				File and directories keep their current SELinux context when they are moved. In many cases, this is incorrect for the location they are being moved to. The following example demonstrates moving a file from a user's home directory to <code class="filename">/var/www/html/</code>, which is used by the Apache HTTP Server. Since the file is moved, it does not inherit the correct SELinux context:
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.10.2. Movimiento de Archivos y Directorios</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html" title="5.10. Mantención de las Etiquetas de SELinux" /><link rel="prev" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html" title="5.10. Mantención de las Etiquetas de SELinux" /><link rel="next" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context
 .html" title="5.10.3. Chequeando el Contexto SELinux Predeterminado" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.10.2. Movimiento de Archivos y Dire
 ctorios" id="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Moving_Files_and_Directories"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.10.2. Movimiento de Archivos y Directorios</h3></div></div></div><div class="para">
+				Los archivos y directorios mantienen su contexto SELinux actual cuando se mueven. En muchos casos, esto es incorrecto para la ubicación nueva a donde se los mueve. El siguiente ejemplo muestra la movida de un archivo desde el directorio de inicio del usuario a <code class="filename">/var/www/html/</code>, que es usado por el Servidor HTTP Apache. Dado que el archivo es movido, no hereda el contexto SELinux correcto:
 			</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
-						Run the <code class="command">cd</code> command without any arguments to change into your home directory. Once in your home directory, run the <code class="command">touch file1</code> command to create a file. This file is labeled with the <code class="computeroutput">user_home_t</code> type:
+						Ejecute el comando <code class="command">cd</code> sin ningún argumento para cambiar a su directorio de inicio. Una vez ahí, ejecute el comando <code class="command">touch archivo1</code> para crear un archivo. Este archivo se etiqueta con el tipo <code class="computeroutput">user_home_t</code>:
 					</div><pre class="screen">$ ls -Z file1
 -rw-rw-r--  user1 group1 unconfined_u:object_r:user_home_t:s0 file1
 
 </pre></li><li class="listitem"><div class="para">
-						Run the <code class="command">ls -dZ /var/www/html/</code> command to view the SELinux context of the <code class="filename">/var/www/html/</code> directory:
+						Ejecute el comando <code class="command">ls -dZ /var/www/html/</code> para ver el contexto de SELinux del directorio <code class="filename">/var/www/html/</code>:
 					</div><pre class="screen">$ ls -dZ /var/www/html/
 drwxr-xr-x  root root system_u:object_r:httpd_sys_content_t:s0 /var/www/html/
 
 </pre><div class="para">
-						By default, the <code class="filename">/var/www/html/</code> directory is labeled with the <code class="computeroutput">httpd_sys_content_t</code> type. Files and directories created under the <code class="filename">/var/www/html/</code> directory inherit this type, and as such, they are labeled with this type.
+						Por defecto, el directorio <code class="filename">/var/www/html/</code> se etiqueta con el tipo <code class="computeroutput">httpd_sys_content_t</code>. Los archivos y directorios creados bajo el directorio <code class="filename">/var/www/html/</code> heredan este tipo, y como tal, son etiquetados con este tipo.
 					</div></li><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">mv file1 /var/www/html/</code> command to move <code class="filename">file1</code> to the <code class="filename">/var/www/html/</code> directory. Since this file is moved, it keeps its current <code class="computeroutput">user_home_t</code> type:
+						Como usuario root de Linux, ejecute el comando <code class="command">mv archivo1 /var/www/html/</code> para mover el <code class="filename">archivo1</code> al directorio <code class="filename">/var/www/html/</code>. Dado que el archivo es movido, mantiene su tipo <code class="computeroutput">user_home_t</code> actual:
 					</div><pre class="screen"># mv file1 /var/www/html/
 # ls -Z /var/www/html/file1
 -rw-rw-r--  user1 group1 unconfined_u:object_r:user_home_t:s0 /var/www/html/file1
 
 </pre></li></ol></div><div class="para">
-				By default, the Apache HTTP Server can not read files that are labeled with the <code class="computeroutput">user_home_t</code> type. If all files comprising a web page are labeled with the <code class="computeroutput">user_home_t</code> type, or another type that the Apache HTTP Server can not read, permission is denied when attempting to access them via Firefox or text-based Web browsers.
+				Por defecto, el Servidor HTTP Apache no puede leer archivos etiquetados con el tipo <code class="computeroutput">user_home_t</code>. Si todos los archivos de una página web se etiquetaron con <code class="computeroutput">user_home_t</code>, u otro tipo al que el Servidor HTTP Apache no puede leer, el permiso es negado cuando intente accederlo vía Firefox o algún otro navegador web basado en texto.
 			</div><div class="important"><h2>Importante</h2><div class="para">
-					Moving files and directories with the <code class="command">mv</code> command may result in the wrong SELinux context, preventing processes, such as the Apache HTTP Server and Samba, from accessing such files and directories.
-				</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html"><strong>Anterior</strong>5.10. Maintaining SELinux Labels </a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context.html"><strong>Siguiente</strong>5.10.3. Checking the Default SELinux Context</a></li></ul></body></html>
+					Mover archivos y directorios con el comando <code class="command">mv</code> puede resultar en el contexto SELinux incorrecto, evitando que los procesos tales como el Servidor HTTP Apache y Samba puedan acceder a tales archivos y directorios.
+				</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html"><strong>Anterior</strong>5.10. Mantención de las Etiquetas de SELinux</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context.html"><strong>Siguiente</strong>5.10.3. Chequeando el Contexto SELinux Predetermi...</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Mounting_File_Systems-Changing_the_Default_Context.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Mounting_File_Systems-Changing_the_Default_Context.html
index 362caaf..dbee068 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Mounting_File_Systems-Changing_the_Default_Context.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Mounting_File_Systems-Changing_the_Default_Context.html
@@ -1,20 +1,20 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.9.2. Changing the Default Context</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html" title="5.9. Mounting File Systems" /><link rel="prev" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html" title="5.9. Mounting File Systems" /><link rel="next" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Mounting_an_NFS_File_System.html" title="5.9.3. Mounting an NFS File System" /></head><body class="toc_emb
 eded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Mounting_an_NFS_File_System.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.9.2. Changing the Default Context" id="sect-Security-Enhanced_Linux-Mounting_File_Systems-Changing_the_Default_Context"><div class="titlepage"><div><div k
 eep-together.within-column="always"><h3 class="title">5.9.2. Changing the Default Context</h3></div></div></div><div class="para">
-				As mentioned in <a class="xref" href="sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types.html" title="5.8. The file_t and default_t Types">Sección 5.8, “The file_t and default_t Types”</a>, on file systems that support extended attributes, when a file that lacks an SELinux context on disk is accessed, it is treated as if it had a default context as defined by SELinux policy. In common policies, this default context uses the <code class="computeroutput">file_t</code> type. If it is desirable to use a different default context, mount the file system with the <code class="option">defcontext</code> option.
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.9.2. Cambio del Contexto Predeterminado</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html" title="5.9. Montaje de Sistemas de Archivos" /><link rel="prev" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html" title="5.9. Montaje de Sistemas de Archivos" /><link rel="next" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Mounting_an_NFS_File_System.html" title="5.9.3. Montando un Sistema de Arch
 ivos NFS" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Mounting_an_NFS_File_System.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.9.2. Cambio del Contexto Predeterminado" id="sect-Security-Enhanced_Linux-Mounting_File_Systems-Changing_the_Defaul
 t_Context"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.9.2. Cambio del Contexto Predeterminado</h3></div></div></div><div class="para">
+				As mentioned in <a class="xref" href="sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types.html" title="5.8. Los tipos file_t y default_t">Sección 5.8, “Los tipos file_t y default_t”</a>, on file systems that support extended attributes, when a file that lacks an SELinux context on disk is accessed, it is treated as if it had a default context as defined by SELinux policy. In common policies, this default context uses the <code class="computeroutput">file_t</code> type. If it is desirable to use a different default context, mount the file system with the <code class="option">defcontext</code> option.
 			</div><div class="para">
-				The following example mounts a newly-created file system (on <code class="filename">/dev/sda2</code>) to the newly-created <code class="filename">/test/</code> directory. It assumes that there are no rules in <code class="filename">/etc/selinux/targeted/contexts/files/</code> that define a context for the <code class="filename">/test/</code> directory:
+				El siguiente ejemplo monta un sistema de archivo recién creado (en <code class="filename">/dev/sda2</code>) en el directorio recién creado <code class="filename">/prueba/</code>. Asume que no hay reglas en <code class="filename">/etc/selinux/targeted/contexts/files/</code> que definan el contexto del directorio <code class="filename">/prueba/</code>:
 			</div><pre class="screen">
 # mount /dev/sda2 /test/ -o defcontext="system_u:object_r:samba_share_t:s0"
 
 </pre><div class="para">
-				In this example:
+				En este ejemplo:
 			</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-						the <code class="option">defcontext</code> option defines that <code class="computeroutput">system_u:object_r:samba_share_t:s0</code> is "the default security context for unlabeled files"<sup>[<a id="id404873" href="#ftn.id404873" class="footnote">12</a>]</sup>.
+						the <code class="option">defcontext</code> option defines that <code class="computeroutput">system_u:object_r:samba_share_t:s0</code> is "the default security context for unlabeled files"<sup>[<a id="id814089" href="#ftn.id814089" class="footnote">12</a>]</sup>.
 					</div></li><li class="listitem"><div class="para">
-						when mounted, the root directory (<code class="filename">/test/</code>) of the file system is treated as if it is labeled with the context specified by <code class="option">defcontext</code> (this label is not stored on disk). This affects the labeling for files created under <code class="filename">/test/</code>: new files inherit the <code class="computeroutput">samba_share_t</code> type, and these labels are stored on disk.
+						cuando sea montado, el directorio raíz (<code class="filename">/prueba/</code>) del sistema de archivo se trata como si estuviera etiquetado con el contexto especificado por <code class="option">defcontext</code> (esta etiqueta no se guarda en el disco). Esto afecta el etiquetado de archvios creados en <code class="filename">/prueba/</code>: los archivos nuevos heredan el tipo <code class="computeroutput">samba_share_t</code>, y estas etiquetas se guardan en el disco.
 					</div></li><li class="listitem"><div class="para">
-						files created under <code class="filename">/test/</code> while the file system was mounted with a <code class="option">defcontext</code> option retain their labels.
-					</div></li></ul></div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id404873" href="#id404873" class="para">12</a>] </sup>
+						los archivos creados bajo <code class="filename">/prueba/</code> mientras el sistema de archivo estaba montado con la opción <code class="option">defcontext</code> retendrán sus etiquetas.
+					</div></li></ul></div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id814089" href="#id814089" class="para">12</a>] </sup>
 							Morris, James. "Filesystem Labeling in SELinux". Published 1 October 2004. Accessed 14 October 2008: <a href="http://www.linuxjournal.com/article/7426">http://www.linuxjournal.com/article/7426</a>.
-						</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html"><strong>Anterior</strong>5.9. Mounting File Systems</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Mounting_an_NFS_File_System.html"><strong>Siguiente</strong>5.9.3. Mounting an NFS File System</a></li></ul></body></html>
+						</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html"><strong>Anterior</strong>5.9. Montaje de Sistemas de Archivos</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Mounting_an_NFS_File_System.html"><strong>Siguiente</strong>5.9.3. Montando un Sistema de Archivos NFS</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Mounting_File_Systems-Making_Context_Mounts_Persistent.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Mounting_File_Systems-Making_Context_Mounts_Persistent.html
index 65a0360..e985ace 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Mounting_File_Systems-Making_Context_Mounts_Persistent.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Mounting_File_Systems-Making_Context_Mounts_Persistent.html
@@ -1,10 +1,10 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.9.5. Making Context Mounts Persistent</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html" title="5.9. Mounting File Systems" /><link rel="prev" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Multiple_NFS_Mounts.html" title="5.9.4. Multiple NFS Mounts" /><link rel="next" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html" title="5.10. Maintaining SELinux Labels" /></head><body class="toc_emb
 eded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Multiple_NFS_Mounts.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.9.5. Making Context Mounts Persistent" id="sect-Security-Enhanced_Linux-Mounting_File_Systems-Making_Context_Mounts_Persistent"><div class="titlepage"><div>
 <div keep-together.within-column="always"><h3 class="title">5.9.5. Making Context Mounts Persistent</h3></div></div></div><div class="para">
-				To make context mounts persistent across remounting and reboots, add entries for the file systems in <code class="filename">/etc/fstab</code> or an automounter map, and use the desired context as a mount option. The following example adds an entry to <code class="filename">/etc/fstab</code> for an NFS context mount:
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.9.5. Haciendo Persistente los Contextos de Montajes</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html" title="5.9. Montaje de Sistemas de Archivos" /><link rel="prev" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Multiple_NFS_Mounts.html" title="5.9.4. Montajes NFS Múltiples" /><link rel="next" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html" title="5.10. Mantención de las Etiqu
 etas de SELinux" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Multiple_NFS_Mounts.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.9.5. Haciendo Persistente los Contextos de Montajes" id="sect-Security-Enhanced_Linux-Mounting_File_Systems-Ma
 king_Context_Mounts_Persistent"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.9.5. Haciendo Persistente los Contextos de Montajes</h3></div></div></div><div class="para">
+				Para hacer que los contextos de montajes persistentes entre remontadas y reiniciadas, agregue las entradas de los sistemas de archivos en <code class="filename">/etc/fstab</code> o un mapa de automontador, y use el contexto deseado como una opción de montaje. El siguiente ejemplo agrega una entrada en <code class="filename">/etc/fstab</code> para un montaje de contexto NFS:
 			</div><pre class="screen">
 server:/export /local/mount/ nfs context="system_u:object_r:httpd_sys_content_t:s0" 0 0
 
 </pre><div class="para">
 				Refer to the <a href="http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.2/html/Deployment_Guide/s1-nfs-client-config.html">Red Hat Enterprise Linux 5 Deployment Guide, Section 19.2. "NFS Client Configuration"</a> for information about mounting NFS file systems.
-			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Multiple_NFS_Mounts.html"><strong>Anterior</strong>5.9.4. Multiple NFS Mounts</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html"><strong>Siguiente</strong>5.10. Maintaining SELinux Labels </a></li></ul></body></html>
+			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Multiple_NFS_Mounts.html"><strong>Anterior</strong>5.9.4. Montajes NFS Múltiples</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html"><strong>Siguiente</strong>5.10. Mantención de las Etiquetas de SELinux</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Mounting_File_Systems-Mounting_an_NFS_File_System.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Mounting_File_Systems-Mounting_an_NFS_File_System.html
index 8f3af42..0733e82 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Mounting_File_Systems-Mounting_an_NFS_File_System.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Mounting_File_Systems-Mounting_an_NFS_File_System.html
@@ -1,14 +1,14 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.9.3. Mounting an NFS File System</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html" title="5.9. Mounting File Systems" /><link rel="prev" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Changing_the_Default_Context.html" title="5.9.2. Changing the Default Context" /><link rel="next" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Multiple_NFS_Mounts.html" title="5.9.4. Multiple NFS Mounts" /></head><body class="toc_emb
 eded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Changing_the_Default_Context.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Multiple_NFS_Mounts.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.9.3. Mounting an NFS File System" id="sect-Security-Enhanced_Linux-Mounting_File_Systems-Mounting_an_NFS_File_System"><div class="titlepage"><div><div kee
 p-together.within-column="always"><h3 class="title">5.9.3. Mounting an NFS File System</h3></div></div></div><div class="para">
-				By default, NFS mounts on the client side are labeled with a default context defined by policy for NFS file systems. In common policies, this default context uses the <code class="computeroutput">nfs_t</code> type. Depending on policy configuration, services, such as Apache HTTP Server and MySQL, may not be able to read files labeled with the <code class="computeroutput">nfs_t</code> type. This may prevent file systems labeled with this type from being mounted and then read or exported by other services.
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.9.3. Montando un Sistema de Archivos NFS</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html" title="5.9. Montaje de Sistemas de Archivos" /><link rel="prev" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Changing_the_Default_Context.html" title="5.9.2. Cambio del Contexto Predeterminado" /><link rel="next" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Multiple_NFS_Mounts.html" title="5.9.4. Montajes NFS Múltipl
 es" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Changing_the_Default_Context.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Multiple_NFS_Mounts.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.9.3. Montando un Sistema de Archivos NFS" id="sect-Security-Enhanced_Linux-Mounting_File_Systems-Mounting_an_NFS_File_Sys
 tem"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.9.3. Montando un Sistema de Archivos NFS</h3></div></div></div><div class="para">
+				Por defecto, los montajes NFS en el lado del cliente son etiquetados con un contexto predeterminado por la política para los sistemas de archivo NFS. En políticas comunes, este contexto predeterminado usa el tipo <code class="computeroutput">nfs_t</code>. Dependiendo de la configuración de la política, los servicios, como el Servidor HTTP Apache y MySQL, pueden no poder leer archivos etiquetados con el tipo <code class="computeroutput">nfs_t</code>. Esto puede prevenir que los sistemas de archivos etiquetados con este tipo se monten y sean leídos o exportados por otros servicios.
 			</div><div class="para">
-				If you would like to mount an NFS file system and read or export that file system with another service, use the <code class="option">context</code> option when mounting to override the <code class="computeroutput">nfs_t</code> type. Use the following context option to mount NFS file systems so that they can be shared via the Apache HTTP Server:
+				Si desea montar un sistema de archivo NFS y leer o exportar ese sistema de archivo con otro servicio, use la opción <code class="option">contexto</code> cuando monte para anular el tipo <code class="computeroutput">nfs_t</code>. Use la siguiente opción de contexto para montar sistemas de archivo NFS para que puedan compartirse vía el Servidor HTTP Apache:
 			</div><pre class="screen">mount server:/export /local/mount/point -o\
 context="system_u:object_r:httpd_sys_content_t:s0"
 
 </pre><div class="para">
-				Since context changes are not written to disk for these situations, the context specified with the <code class="option">context</code> option is only retained if the <code class="option">context</code> option is used on the next mount, and if the same context is specified.
+				Dado que los cambios de contexto no se escriben al disco para estas situaciones, el contexto especificado con la opción <code class="option">context</code> sólo se retiene si la opción <code class="option">context</code> se usa en el siguiente montaje, y si el mismo contexto se especifica.
 			</div><div class="para">
-				As an alternative to mounting file systems with <code class="option">context</code> options, Booleans can be turned on to allow services access to file systems labeled with the <code class="computeroutput">nfs_t</code> type. Refer to <a class="xref" href="sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS.html" title="5.6.3. Booleans for NFS and CIFS">Sección 5.6.3, “Booleans for NFS and CIFS”</a> for instructions on configuring Booleans to allow services access to the <code class="computeroutput">nfs_t</code> type.
-			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Changing_the_Default_Context.html"><strong>Anterior</strong>5.9.2. Changing the Default Context</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Multiple_NFS_Mounts.html"><strong>Siguiente</strong>5.9.4. Multiple NFS Mounts</a></li></ul></body></html>
+				As an alternative to mounting file systems with <code class="option">context</code> options, Booleans can be turned on to allow services access to file systems labeled with the <code class="computeroutput">nfs_t</code> type. Refer to <a class="xref" href="sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS.html" title="5.6.3. Booleanos para NFS y CIFS">Sección 5.6.3, “Booleanos para NFS y CIFS”</a> for instructions on configuring Booleans to allow services access to the <code class="computeroutput">nfs_t</code> type.
+			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Changing_the_Default_Context.html"><strong>Anterior</strong>5.9.2. Cambio del Contexto Predeterminado</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Multiple_NFS_Mounts.html"><strong>Siguiente</strong>5.9.4. Montajes NFS Múltiples</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Mounting_File_Systems-Multiple_NFS_Mounts.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Mounting_File_Systems-Multiple_NFS_Mounts.html
index 4fcca80..05e645b 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Mounting_File_Systems-Multiple_NFS_Mounts.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Mounting_File_Systems-Multiple_NFS_Mounts.html
@@ -1,7 +1,7 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.9.4. Multiple NFS Mounts</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html" title="5.9. Mounting File Systems" /><link rel="prev" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Mounting_an_NFS_File_System.html" title="5.9.3. Mounting an NFS File System" /><link rel="next" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Making_Context_Mounts_Persistent.html" title="5.9.5. Making Context Mounts Persistent" /></head><bod
 y class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Mounting_an_NFS_File_System.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Making_Context_Mounts_Persistent.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.9.4. Multiple NFS Mounts" id="sect-Security-Enhanced_Linux-Mounting_File_Systems-Multiple_NFS_Mounts"><div class="titlepage"><
 div><div keep-together.within-column="always"><h3 class="title">5.9.4. Multiple NFS Mounts</h3></div></div></div><div class="para">
-				When mounting multiple mounts from the same NFS export, attempting to override the SELinux context of each mount with a different context, results in subsequent mount commands failing. In the following example, the NFS server has a single export, <code class="filename">/export</code>, which has two subdirectories, <code class="filename">web/</code> and <code class="filename">database/</code>. The following commands attempt two mounts from a single NFS export, and try to override the context for each one:
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.9.4. Montajes NFS Múltiples</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html" title="5.9. Montaje de Sistemas de Archivos" /><link rel="prev" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Mounting_an_NFS_File_System.html" title="5.9.3. Montando un Sistema de Archivos NFS" /><link rel="next" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Making_Context_Mounts_Persistent.html" title="5.9.5. Haciendo Persistente
  los Contextos de Montajes" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Mounting_an_NFS_File_System.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Making_Context_Mounts_Persistent.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.9.4. Montajes NFS Múltiples" id="sect-Security-Enhanced_Linux-Mounting_File_Systems-
 Multiple_NFS_Mounts"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.9.4. Montajes NFS Múltiples</h3></div></div></div><div class="para">
+				Cuando se monten múltiples montajes desde el mismo NFS exportado, el intento de sobreescribir el contexto de SELinux e cada montaje con un contexto diferente, resulta en fallos de los comandos de montaje subsecuentes. En el siguiente ejemplo, el servidor NFS tiene un exportado único, <code class="filename">/export</code>, que tiene dos subdirectorios, <code class="filename">web/</code> and <code class="filename">database/</code>. El siguiente comando intenta dos montajes desde un único export NFS e intenta sobreescribir el contexto para cada uno:
 			</div><pre class="screen">
 # mount server:/export/web /local/web -o\
 context="system_u:object_r:httpd_sys_content_t:s0"
@@ -10,12 +10,12 @@ context="system_u:object_r:httpd_sys_content_t:s0"
 context="system_u:object_r:mysqld_db_t:s0"
 
 </pre><div class="para">
-				The second mount command fails, and the following is logged to <code class="filename">/var/log/messages</code>:
+				El segundo comando mount falla, y se graba lo siguiente en <code class="filename">/var/log/messages</code>:
 			</div><pre class="screen">
 kernel: SELinux: mount invalid.  Same superblock, different security settings for (dev 0:15, type nfs)
 
 </pre><div class="para">
-				To mount multiple mounts from a single NFS export, with each mount having a different context, use the <code class="option">-o nosharecache,context</code> options. The following example mounts multiple mounts from a single NFS export, with a different context for each mount (allowing a single service access to each one):
+				Para montar montajes múltiples de un exportado NFS único, con cada montaje teniendo un contexto diferente, use las opciones <code class="option">-o nosharecache,context</code>. El siguiente ejemplo monta montajes múltiples de un único export de NSF, con un contexto diferente para cada montaje (permitiendo un único acceso de servicio a cada uno):
 			</div><pre class="screen">
 # mount server:/export/web /local/web -o\
 nosharecache,context="system_u:object_r:httpd_sys_content_t:s0"
@@ -24,7 +24,7 @@ nosharecache,context="system_u:object_r:httpd_sys_content_t:s0"
 nosharecache,context="system_u:object_r:mysqld_db_t:s0"
 
 </pre><div class="para">
-				In this example, <code class="computeroutput">server:/export/web</code> is mounted locally to <code class="filename">/local/web/</code>, with all files being labeled with the <code class="computeroutput">httpd_sys_content_t</code> type, allowing Apache HTTP Server access. <code class="computeroutput">server:/export/database</code> is mounted locally to <code class="filename">/local/database</code>, with all files being labeled with the <code class="computeroutput">mysqld_db_t</code> type, allowing MySQL access. These type changes are not written to disk.
+				En este ejemplo, <code class="computeroutput">server:/export/web</code> se monta localmente en <code class="filename">/local/web/</code>, con todos los archivos etiquetados con el tipo <code class="computeroutput">httpd_sys_content_t</code>, lo que permite el acceso al Servidor HTTP Apache. <code class="computeroutput">server:/export/database</code> está montado localmente en <code class="filename">/local/database</code>, con los archivos etiquetados con el tipo <code class="computeroutput">mysqld_db_t</code>, lo que permite a MySQL el acceso. Estos cambios de tipo no se escriben en el disco.
 			</div><div class="important"><h2>Importante</h2><div class="para">
-					The <code class="option">nosharecache</code> options allows you to mount the same subdirectory of an export multiple times with different contexts (for example, mounting <code class="filename">/export/web</code> multiple times). Do not mount the same subdirectory from an export multiple times with different contexts, as this creates an overlapping mount, where files are accessible under two different contexts.
-				</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Mounting_an_NFS_File_System.html"><strong>Anterior</strong>5.9.3. Mounting an NFS File System</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Making_Context_Mounts_Persistent.html"><strong>Siguiente</strong>5.9.5. Making Context Mounts Persistent</a></li></ul></body></html>
+					Las opciones <code class="option">nosharecache</code> le permiten montar el mismo subdirectorio de un exportado varias veces con distintos contextos (por ejemplo, montar <code class="filename">/export/web</code> varias veces). No monte el mismo directorio de un exportado varias veces con distintos contextos, dado que esto crea un montado solapado, donde los archivos se pueden acceder con dos contextos diferentes.
+				</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Mounting_an_NFS_File_System.html"><strong>Anterior</strong>5.9.3. Montando un Sistema de Archivos NFS</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Making_Context_Mounts_Persistent.html"><strong>Siguiente</strong>5.9.5. Haciendo Persistente los Contextos de Mont...</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Permissive_Domains-Denials_for_Permissive_Domains.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Permissive_Domains-Denials_for_Permissive_Domains.html
index e492b5c..0d0215d 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Permissive_Domains-Denials_for_Permissive_Domains.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Permissive_Domains-Denials_for_Permissive_Domains.html
@@ -1,21 +1,21 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.3.4.2. Denials for Permissive Domains</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains.html" title="7.3.4. Permissive Domains" /><link rel="prev" href="sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains.html" title="7.3.4. Permissive Domains" /><link rel="next" href="sect-Security-Enhanced_Linux-Fixing_Problems-Searching_For_and_Viewing_Denials.html" title="7.3.5. Searching For and Viewing Denials" /></head><body class="toc_embeded "><
 div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Fixing_Problems-Searching_For_and_Viewing_Denials.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="7.3.4.2. Denials for Permissive Domains" id="sect-Security-Enhanced_Linux-Permissive_Domains-Denials_for_Permissive_Domains"><div class="titlepage"><div><div keep-together.
 within-column="always"><h4 class="title">7.3.4.2. Denials for Permissive Domains</h4></div></div></div><div class="para">
-					The <code class="computeroutput">SYSCALL</code> message is different for permissive domains. The following is an example AVC denial (and the associated system call) from the Apache HTTP Server:
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.3.4.2. Negaciones para Dominios Permisivos</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains.html" title="7.3.4. Dominios Permisivos" /><link rel="prev" href="sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains.html" title="7.3.4. Dominios Permisivos" /><link rel="next" href="sect-Security-Enhanced_Linux-Fixing_Problems-Searching_For_and_Viewing_Denials.html" title="7.3.5. Búsqueda y Revisión de Negaciones" /></head><body class="t
 oc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Fixing_Problems-Searching_For_and_Viewing_Denials.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="7.3.4.2. Negaciones para Dominios Permisivos" id="sect-Security-Enhanced_Linux-Permissive_Domains-Denials_for_Permissive_Domains"><div class="titlepage"><div>
 <div keep-together.within-column="always"><h4 class="title">7.3.4.2. Negaciones para Dominios Permisivos</h4></div></div></div><div class="para">
+					El mensaje <code class="computeroutput">SYSCALL</code> es diferente para dominios permisivos. El siguiente es un ejemplo de una negación de AVC (y la llamada a sistema asociada) desde el Servidor HTTP Apache:
 				</div><pre class="screen">
 type=AVC msg=audit(1226882736.442:86): avc:  denied  { getattr } for  pid=2427 comm="httpd" path="/var/www/html/file1" dev=dm-0 ino=284133 scontext=unconfined_u:system_r:httpd_t:s0 tcontext=unconfined_u:object_r:samba_share_t:s0 tclass=file
 	
 type=SYSCALL msg=audit(1226882736.442:86): arch=40000003 syscall=196 success=no exit=-13 a0=b9a1e198 a1=bfc2921c a2=54dff4 a3=2008171 items=0 ppid=2425 pid=2427 auid=502 uid=48 gid=48 euid=48 suid=48 fsuid=48 egid=48 sgid=48 fsgid=48 tty=(none) ses=4 comm="httpd" exe="/usr/sbin/httpd" subj=unconfined_u:system_r:httpd_t:s0 key=(null)
 
 </pre><div class="para">
-					By default, the <code class="computeroutput">httpd_t</code> domain is not permissive, and as such, the action is denied, and the <code class="computeroutput">SYSCALL</code> message contains <code class="computeroutput">success=no</code>. The following is an example AVC denial for the same situation, except the <code class="command">semanage permissive -a httpd_t</code> command has been run to make the <code class="computeroutput">httpd_t</code> domain permissive:
+					Por defecto, el dominio <code class="computeroutput">httpd_t</code> es no permisivo, y como tal, la acción es negada, y el mensaje <code class="computeroutput">SYSCALL</code> contiene <code class="computeroutput">success=no</code>. El siguiente es un ejemplo de negación AVC para la misma situación, excepto que el comando <code class="command">semanage permissive -a httpd_t</code> se ejecutó para hacer el dominio <code class="computeroutput">httpd_t</code> permisivo:
 				</div><pre class="screen">
 type=AVC msg=audit(1226882925.714:136): avc:  denied  { read } for  pid=2512 comm="httpd" name="file1" dev=dm-0 ino=284133 scontext=unconfined_u:system_r:httpd_t:s0 tcontext=unconfined_u:object_r:samba_share_t:s0 tclass=file
 	
 type=SYSCALL msg=audit(1226882925.714:136): arch=40000003 syscall=5 success=yes exit=11 a0=b962a1e8 a1=8000 a2=0 a3=8000 items=0 ppid=2511 pid=2512 auid=502 uid=48 gid=48 euid=48 suid=48 fsuid=48 egid=48 sgid=48 fsgid=48 tty=(none) ses=4 comm="httpd" exe="/usr/sbin/httpd" subj=unconfined_u:system_r:httpd_t:s0 key=(null)
 
 </pre><div class="para">
-					In this case, although an AVC denial was logged, access was not denied, as shown by <code class="computeroutput">success=yes</code> in the <code class="computeroutput">SYSCALL</code> message.
+					En este caso, aunque la negación AVC fue grabada, el acceso no fue negado, como se muestra en el mensaje <code class="computeroutput">SYSCALL</code> <code class="computeroutput">success=yes</code>.
 				</div><div class="para">
 					Refer to Dan Walsh's <a href="http://danwalsh.livejournal.com/24537.html">"Permissive Domains"</a> blog entry for further information about permissive domains.
-				</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains.html"><strong>Anterior</strong>7.3.4. Permissive Domains</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Fixing_Problems-Searching_For_and_Viewing_Denials.html"><strong>Siguiente</strong>7.3.5. Searching For and Viewing Denials</a></li></ul></body></html>
+				</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains.html"><strong>Anterior</strong>7.3.4. Dominios Permisivos</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Fixing_Problems-Searching_For_and_Viewing_Denials.html"><strong>Siguiente</strong>7.3.5. Búsqueda y Revisión de Negaciones</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Processes.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Processes.html
index 5952f22..ce09743 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Processes.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Processes.html
@@ -1,21 +1,21 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.2. SELinux Contexts for Processes</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="chap-Security-Enhanced_Linux-SELinux_Contexts.html" title="Capítulo 3. SELinux Contexts" /><link rel="prev" href="chap-Security-Enhanced_Linux-SELinux_Contexts.html" title="Capítulo 3. SELinux Contexts" /><link rel="next" href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Users.html" title="3.3. SELinux Contexts for Users" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocfram
 e" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-SELinux_Contexts.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Users.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="3.2. SELinux Contexts for Processes" id="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Processes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">3.2. SELinux Contexts for Processes<
 /h2></div></div></div><div class="para">
-			Use the <code class="command">ps -eZ</code> command to view the SELinux context for processes. For example:
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.2. Contextos de SELinux para los Procesos</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-SELinux_Contexts.html" title="Capítulo 3. Contextos de SELinux" /><link rel="prev" href="chap-Security-Enhanced_Linux-SELinux_Contexts.html" title="Capítulo 3. Contextos de SELinux" /><link rel="next" href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Users.html" title="3.3. Contextos de SELinux para los Usuarios" /></head><body class="toc_embeded "><div id="tocdiv
 " class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-SELinux_Contexts.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Users.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="3.2. Contextos de SELinux para los Procesos" id="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Processes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="ti
 tle">3.2. Contextos de SELinux para los Procesos</h2></div></div></div><div class="para">
+			Use el comando <code class="command">ps -eZ</code> para ver los contextos de SELinux para los procesos. Por ejemplo:
 		</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
-					Open a terminal, such as <span class="guimenu"><strong>Applications</strong></span> → <span class="guisubmenu"><strong>System Tools</strong></span> → <span class="guimenuitem"><strong>Terminal</strong></span>.
+					Abra una terminal, como la de <span class="guimenu"><strong>Aplicaciones</strong></span> → <span class="guisubmenu"><strong>Herramientas del Sistema</strong></span> → <span class="guimenuitem"><strong>Terminal</strong></span>.
 				</div></li><li class="listitem"><div class="para">
-					Run the <code class="command">/usr/bin/passwd</code> command. Do not enter a new password.
+					Ejecute el comando <code class="command">/usr/bin/passwd</code>. No ingrese una nueva contraseña.
 				</div></li><li class="listitem"><div class="para">
-					Open a new tab, or another terminal, and run the <code class="command">ps -eZ | grep passwd</code> command. The output is similar to the following:
+					Abra una nueva pestaña, u otra terminal, y ejecute el comando <code class="command">ps -eZ | grep passwd</code>. La salida es similar a la siguiente:
 				</div><pre class="screen">unconfined_u:unconfined_r:passwd_t:s0-s0:c0.c1023 13212 pts/1 00:00:00 passwd
 
 </pre></li><li class="listitem"><div class="para">
-					In the first tab, press <strong class="userinput"><code>Ctrl+C</code></strong> to cancel the <span class="application"><strong>passwd</strong></span> application.
+					En la primer pestaña, presione <strong class="userinput"><code>Ctrl+C</code></strong> para cancelar la aplicación <span class="application"><strong>passwd</strong></span>.
 				</div></li></ol></div><div class="para">
-			In this example, when the <code class="filename">/usr/bin/passwd</code> application (labeled with the <code class="computeroutput">passwd_exec_t</code> type) is executed, the user's shell process transitions to the <code class="computeroutput">passwd_t</code> domain. Remember: the type defines a domain for processes, and a type for files.
+			En este ejemplo, cuando la aplicación <code class="filename">/usr/bin/passwd</code> (etiquetada con el tipo <code class="computeroutput">passwd_exec_t</code>) se ejecuta, el proceso shell del usuario transiciona al dominio <code class="computeroutput">passwd_t</code>. Recuerde: el tipo define un dominio para procesos y un tipo para archivos.
 		</div><div class="para">
-			Use the <code class="command">ps -eZ</code> command to view the SELinux contexts for running processes. The following is a limited example of the output, and may differ on your system:
+			Use el comando <code class="command">ps -eZ</code> para ver los contextos SELinux de los procesos en ejecución. El siguiente es un ejemplo limitado de la salida, y puede cambiar en su sistema:
 		</div><pre class="screen">system_u:system_r:setroubleshootd_t:s0 1866 ?  00:00:08 setroubleshootd
 system_u:system_r:dhcpc_t:s0     1869 ?        00:00:00 dhclient
 system_u:system_r:sshd_t:s0-s0:c0.c1023 1882 ? 00:00:00 sshd
@@ -25,5 +25,5 @@ system_u:system_r:kerneloops_t:s0 1983 ?       00:00:05 kerneloops
 system_u:system_r:crond_t:s0-s0:c0.c1023 1991 ? 00:00:00 atd
 
 </pre><div class="para">
-			The <code class="computeroutput">system_r</code> role is used for system processes, such as daemons. Type Enforcement then separates each domain.
-		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-SELinux_Contexts.html"><strong>Anterior</strong>Capítulo 3. SELinux Contexts</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Users.html"><strong>Siguiente</strong>3.3. SELinux Contexts for Users</a></li></ul></body></html>
+			El rol <code class="computeroutput">system_r</code> se usa para procesos de sistema, como los demonios. El tipo obligatorio los separa luego en dominios.
+		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-SELinux_Contexts.html"><strong>Anterior</strong>Capítulo 3. Contextos de SELinux</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Users.html"><strong>Siguiente</strong>3.3. Contextos de SELinux para los Usuarios</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Users.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Users.html
index ac9caa7..759ac99 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Users.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Users.html
@@ -1,9 +1,9 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.3. SELinux Contexts for Users</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="chap-Security-Enhanced_Linux-SELinux_Contexts.html" title="Capítulo 3. SELinux Contexts" /><link rel="prev" href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Processes.html" title="3.2. SELinux Contexts for Processes" /><link rel="next" href="chap-Security-Enhanced_Linux-Targeted_Policy.html" title="Capítulo 4. Targeted Policy" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocfr
 ame" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Processes.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-Targeted_Policy.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="3.3. SELinux Contexts for Users" id="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Users"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">3.3. SELinux Contexts for Users</h2></d
 iv></div></div><div class="para">
-			Use the <code class="command">id -Z</code> command to view the SELinux context associated with your Linux user:
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.3. Contextos de SELinux para los Usuarios</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-SELinux_Contexts.html" title="Capítulo 3. Contextos de SELinux" /><link rel="prev" href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Processes.html" title="3.2. Contextos de SELinux para los Procesos" /><link rel="next" href="chap-Security-Enhanced_Linux-Targeted_Policy.html" title="Capítulo 4. Política Destinado" /></head><body class="toc_embeded "><div id="tocd
 iv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Processes.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-Targeted_Policy.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="3.3. Contextos de SELinux para los Usuarios" id="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Users"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="t
 itle">3.3. Contextos de SELinux para los Usuarios</h2></div></div></div><div class="para">
+			Use el comando <code class="command">id -Z</code> para ver el contexto SELinux asociado con su usuario Linux:
 		</div><pre class="screen">unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
 
 </pre><div class="para">
-			In Fedora 11, Linux users run unconfined by default. This SELinux context shows that the Linux user is mapped to the SELinux <code class="computeroutput">unconfined_u</code> user, running as the <code class="computeroutput">unconfined_r</code> role, and is running in the <code class="computeroutput">unconfined_t</code> domain. <code class="computeroutput">s0-s0</code> is an MLS range, which in this case, is the same as just <code class="computeroutput">s0</code>. The categories the user has access to is defined by <code class="computeroutput">c0.c1023</code>, which is all categories (<code class="computeroutput">c0</code> through to <code class="computeroutput">c1023</code>).
-		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Processes.html"><strong>Anterior</strong>3.2. SELinux Contexts for Processes</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-Targeted_Policy.html"><strong>Siguiente</strong>Capítulo 4. Targeted Policy</a></li></ul></body></html>
+			En Fedora 11, los usuarios Linux corren no confinados por defecto. Este contexto de SELinux muestra que el usuario Linux se mapea al usuario SELinux <code class="computeroutput">unconfined_u</code>, corriendo con el rol <code class="computeroutput">unconfined_r</code> y en el dominio <code class="computeroutput">unconfined_t</code>. <code class="computeroutput">s0-s0</code> es un rango MLS, que en este caso, es el mismo que <code class="computeroutput">s0</code>. Las categorías a las que el usuario tiene acceso se definen por <code class="computeroutput">c0.c1023</code>, que son todas las categorías (<code class="computeroutput">c0</code> a <code class="computeroutput">c1023</code>).
+		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Processes.html"><strong>Anterior</strong>3.2. Contextos de SELinux para los Procesos</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-Targeted_Policy.html"><strong>Siguiente</strong>Capítulo 4. Política Destinado</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext.html
index c8e9805..b80066d 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext.html
@@ -1,73 +1,73 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.7.2. Persistent Changes: semanage fcontext</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files.html" title="5.7. SELinux Contexts - Labeling Files" /><link rel="prev" href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files.html" title="5.7. SELinux Contexts - Labeling Files" /><link rel="next" href="sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types.html" title="5.8. The f
 ile_t and default_t Types" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.7.2. Persistent Changes: semanage fcontext" id="sect-Security-Enhanced_Linux-SELinux_C
 ontexts_Labeling_Files-Persistent_Changes_semanage_fcontext"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.7.2. Persistent Changes: semanage fcontext</h3></div></div></div><div class="para">
-				The <code class="command">/usr/sbin/semanage fcontext</code> command changes the SELinux context for files. When using targeted policy, changes made with this command are added to the <code class="filename">/etc/selinux/targeted/contexts/files/file_contexts</code> file if the changes are to files that exists in <code class="filename">file_contexts</code>, or are added to <code class="filename">file_contexts.local</code> for new files and directories, such as creating a <code class="filename">/web/</code> directory. <code class="command">setfiles</code>, which is used when a file system is relabeled, and <code class="command">/sbin/restorecon</code>, which restores the default SELinux contexts, read these files. This means that changes made by <code class="command">/usr/sbin/semanage fcontext</code> are persistent, even if the file system is relabeled. SELinux policy controls whether users are able to modify the SELinux context for any given file.
-			</div><div class="formalpara"><h5 class="formalpara">Quick Reference</h5>
-					To make SELinux context changes that survive a file system relabel:
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.7.2. Cambios Persistentes: semanage fcontext</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files.html" title="5.7. Contextos de SELinux - Etiquetado de Archivos" /><link rel="prev" href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files.html" title="5.7. Contextos de SELinux - Etiquetado de Archivos" /><link rel="next" href="sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_
 t_Types.html" title="5.8. Los tipos file_t y default_t" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.7.2. Cambios Persistentes: semanage fcontext" id="sect-Se
 curity-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.7.2. Cambios Persistentes: semanage fcontext</h3></div></div></div><div class="para">
+				El comando <code class="command">/usr/sbin/semanage fcontext</code> cambia el contexto SELinux de los archivos. Cuando se usa la política destinada, los cambios hechos con este comando se agregan al archivo <code class="filename">/etc/selinux/targeted/contexts/files/file_contexts</code> si los cambios so para archivos que están en <code class="filename">file_contexts</code>, se agregan a <code class="filename">file_contexts.local</code> para archivos nuevos y directorios, como sería al crear un directorio <code class="filename">/web/</code> nuevo. <code class="command">setfiles</code>, que se usa cuando el sistema de archivo es reetiquetado, y <code class="command">/sbin/restorecon</code>, que restaura los contextos de SELinux predeterminados, leen estos archivos, Lo que significa que los cambios hechos por <code class="command">/usr/sbin/semanage fcontext</code> son persistentes, aún si el sistema de archivo es reetiquetado. La política de SELinux controla si los u
 suarios pueden modificar el contexto de SELinux para cualquier archivo dado.
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Persistent_Changes_semanage_fcontext-Quick_Reference"><h5 class="formalpara">Referencia Rápida</h5>
+					Para hacer que los cambios de contexto de SELinux sobrevivan un reetiquetado del sistema de archivo:
 				</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
-						Run the <code class="command">/usr/sbin/semanage fcontext -a <em class="replaceable"><code>options</code></em> <em class="replaceable"><code>file-name</code></em>|<em class="replaceable"><code>directory-name</code></em></code> command, remembering to use the full path to the file or directory.
+						Ejecute el comando <code class="command">/usr/sbin/semanage fcontext -a <em class="replaceable"><code>opciones</code></em> <em class="replaceable"><code>nombre-de-archivo</code></em>|<em class="replaceable"><code>nombre-de-directorio</code></em></code>, recuerde usar la dirección completa del archivo o del directorio.
 					</div></li><li class="listitem"><div class="para">
-						Run the <code class="command">/sbin/restorecon -v <em class="replaceable"><code>file-name</code></em>|<em class="replaceable"><code>directory-name</code></em></code> command to apply the context changes.
-					</div></li></ol></div><div class="formalpara"><h5 class="formalpara">Changing a File's Type</h5>
-					The following example demonstrates changing a file's type, and no other attributes of the SELinux context:
+						Ejecute el comando <code class="command">/sbin/restorecon -v <em class="replaceable"><code>nombre-de-archivo</code></em>|<em class="replaceable"><code>nombre-de-directorio</code></em></code> para aplicar los cambios de contexto.
+					</div></li></ol></div><div class="formalpara" id="form-Security-Enhanced_Linux-Persistent_Changes_semanage_fcontext-Changing_a_Files_Type"><h5 class="formalpara">Cambiando un Tipo de archivo</h5>
+					El siguiente ejemplo muestra el cambio de tipo de un archivo, sin tocar otros atributos del contexto de SELinux:
 				</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">touch /etc/file1</code> command to create a new file. By default, newly-created files in the <code class="filename">/etc/</code> directory are labeled with the <code class="computeroutput">etc_t</code> type:
+						Como usuario root de Linux, ejecute el comando <code class="command">touch /etc/archivo1</code> para crear un archivo nuevo. Por defecto, los archivos recién creados en el directorio <code class="filename">/etc/</code> se etiquetan con el tipo <code class="computeroutput">etc_t</code>:
 					</div><pre class="screen"># ls -Z /etc/file1
 -rw-r--r--  root root unconfined_u:object_r:etc_t:s0       /etc/file1
 
 </pre></li><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">/usr/sbin/semanage fcontext -a -t samba_share_t /etc/file1</code> command to change the <code class="filename">file1</code> type to <code class="computeroutput">samba_share_t</code>. The <code class="option">-a</code> option adds a new record, and the <code class="option">-t</code> option defines a type (<code class="computeroutput">samba_share_t</code>). Note: running this command does not directly change the type - <code class="filename">file1</code> is still labeled with the <code class="computeroutput">etc_t</code> type:
+						Como usuario root de Linux, ejecute el comando <code class="command">/usr/sbin/semanage fcontext -a -t samba_share_t /etc/archivo1</code> para cambiar el tipo del <code class="filename">archivo1</code> a <code class="computeroutput">samba_share_t</code>. La opción <code class="option">-a</code> agrega un registro nuevo, y la opción <code class="option">-t</code> define un tipo (<code class="computeroutput">samba_share_t</code>). Nota: al ejecutar este comando no se cambia directamente el tipo - el <code class="filename">archivo1</code> todavía es del tipo <code class="computeroutput">etc_t</code>:
 					</div><pre class="screen"># /usr/sbin/semanage fcontext -a -t samba_share_t /etc/file1
 # ls -Z /etc/file1
 -rw-r--r--  root root unconfined_u:object_r:etc_t:s0       /etc/file1
 
 </pre><div class="para">
-						The <code class="command">/usr/sbin/semanage fcontext -a -t samba_share_t /etc/file1</code> command adds the following entry to <code class="filename">/etc/selinux/targeted/contexts/files/file_contexts.local</code>:
+						El comando <code class="command">/usr/sbin/semanage fcontext -a -t samba_share_t /etc/archivo1</code> agrega la siguiente entrada a <code class="filename">/etc/selinux/targeted/contexts/files/file_contexts.local</code>:
 					</div><pre class="screen">/etc/file1    unconfined_u:object_r:samba_share_t:s0
 
 </pre></li><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">/sbin/restorecon -v /etc/file1</code> command to change the type. Since the <code class="command">semanage</code> command added an entry to <code class="filename">file.contexts.local</code> for <code class="filename">/etc/file1</code>, the <code class="command">/sbin/restorecon</code> command changes the type to <code class="computeroutput">samba_share_t</code>:
+						Como usuario root de Linux, ejecute el comando <code class="command">/sbin/restorecon -v /etc/archivo1</code> para cambiar el tipo. Dado que el comando <code class="command">semanage</code> agregó una entrada a <code class="filename">file.contexts.local</code> para <code class="filename">/etc/archivo1</code>, el comando <code class="command">/sbin/restorecon</code> cambia el tipo a <code class="computeroutput">samba_share_t</code>:
 					</div><pre class="screen"># /sbin/restorecon -v /etc/file1
 restorecon reset /etc/file1 context unconfined_u:object_r:etc_t:s0-&gt;system_u:object_r:samba_share_t:s0
 
 </pre></li><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">rm -i /etc/file1</code> command to remove <code class="filename">file1</code>.
+						Como usuario root de Linux, ejecute el comando <code class="command">rm -i /etc/archivo1</code> para borrar el <code class="filename">archivo1</code>.
 					</div></li><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">/usr/sbin/semanage fcontext -d /etc/file1</code> command to remove the context added for <code class="filename">/etc/file1</code>. When the context is removed, running <code class="command">restorecon</code> changes the type to <code class="computeroutput">etc_t</code>, rather than <code class="computeroutput">samba_share_t</code>.
-					</div></li></ol></div><div class="formalpara"><h5 class="formalpara">Changing a Directory's Type</h5>
-					The following example demonstrates creating a new directory and changing that directory's file type, to a type used by Apache HTTP Server:
+						Como usuario root de Linux, ejecute el comando <code class="command">/usr/sbin/semanage fcontext -d /etc/archivo1</code> para eliminar el contexto agregado para <code class="filename">/etc/archivo1</code>. Cuando el contexto se elimina, ejecutando <code class="command">restorecon</code> cambia el tipo a <code class="computeroutput">etc_t</code>, en vez de <code class="computeroutput">samba_share_t</code>.
+					</div></li></ol></div><div class="formalpara" id="form-Security-Enhanced_Linux-Persistent_Changes_semanage_fcontext-Changing_a_Directorys_Type"><h5 class="formalpara">Cambiando un Tipo de Directorio</h5>
+					El siguiente ejemplo muestra la creación de un directorio nuevo y el cambio del tipo de archivo del directorio a un tipo usado por el Servidor HTTP Apache:
 				</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">mkdir /web</code> command to create a new directory. This directory is labeled with the <code class="computeroutput">default_t</code> type:
+						Como usuario root de LInux, ejecute el comando <code class="command">mkdir /web</code> para crear un directorio nuevo. Este directorio se etiqueta con el tipo <code class="computeroutput">default_t</code>:
 					</div><pre class="screen"># ls -dZ /web
 drwxr-xr-x  root root unconfined_u:object_r:default_t:s0 /web
 
 </pre><div class="para">
-						The <code class="command">ls</code> <code class="option">-d</code> option makes <code class="command">ls</code> list information about a directory, rather than its contents, and the <code class="option">-Z</code> option makes <code class="command">ls</code> display the SELinux context (in this example, <code class="computeroutput">unconfined_u:object_r:default_t:s0</code>).
+						La opción <code class="option">-d</code> de <code class="command">ls</code> hace que <code class="command">ls</code> liste la información de un directorio, en vez de su contenido, y la opción <code class="option">-Z</code> hace que <code class="command">ls</code> muestre el contexto de SELinux (en este ejemplo, <code class="computeroutput">unconfined_u:object_r:default_t:s0</code>).
 					</div></li><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">/usr/sbin/semanage fcontext -a -t httpd_sys_content_t /web</code> command to change the <code class="filename">/web/</code> type to <code class="computeroutput">httpd_sys_content_t</code>. The <code class="option">-a</code> option adds a new record, and the <code class="option">-t</code> option defines a type (<code class="computeroutput">httpd_sys_content_t</code>). Note: running this command does not directly change the type - <code class="filename">/web/</code> is still labeled with the <code class="computeroutput">default_t</code> type:
+						Como usuario root de Linux, ejecute el comando <code class="command">/usr/sbin/semanage fcontext -a -t httpd_sys_content_t /web</code> para cambiar el tipo de <code class="filename">/web/</code> a <code class="computeroutput">httpd_sys_content_t</code>. La opción <code class="option">-a</code> agrega un nuevo registro, y la opción <code class="option">-t</code> define un tipo (<code class="computeroutput">httpd_sys_content_t</code>). Nota: la ejecución de este comando no cambia el tipo directamente - <code class="filename">/web/</code> todavía tiene la etiqueta de tipo <code class="computeroutput">default_t</code>:
 					</div><pre class="screen"># /usr/sbin/semanage fcontext -a -t httpd_sys_content_t /web
 # ls -dZ /web
 drwxr-xr-x  root root unconfined_u:object_r:default_t:s0   /web
 
 </pre><div class="para">
-						The <code class="command">/usr/sbin/semanage fcontext -a -t httpd_sys_content_t /web</code> command adds the following entry to <code class="command">/etc/selinux/targeted/contexts/files/file_contexts.local</code>:
+						El comando <code class="command">/usr/sbin/semanage fcontext -a -t httpd_sys_content_t /web</code> agrega la siguiente entrada a <code class="command">/etc/selinux/targeted/contexts/files/file_contexts.local</code>:
 					</div><pre class="screen">/web    unconfined_u:object_r:httpd_sys_content_t:s0
 
 </pre></li><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">/sbin/restorecon -v /web</code> command to change the type. Since the <code class="command">semanage</code> command added an entry to <code class="filename">file.contexts.local</code> for <code class="filename">/web</code>, the <code class="command">/sbin/restorecon</code> command changes the type to <code class="computeroutput">httpd_sys_content_t</code>:
+						Como usuario root de Linux, ejecute el comando <code class="command">/sbin/restorecon -v /web</code> para cambiar el tipo. Como el comando <code class="command">semanage</code> agregó una entrada a <code class="filename">file.contexts.local</code> para <code class="filename">/web</code>, el comando <code class="command">/sbin/restorecon</code> cambia el tipo a <code class="computeroutput">httpd_sys_content_t</code>:
 					</div><pre class="screen"># /sbin/restorecon -v /web
 restorecon reset /web context unconfined_u:object_r:default_t:s0-&gt;system_u:object_r:httpd_sys_content_t:s0
 
 </pre><div class="para">
-						By default, newly-created files and directories inherit the SELinux type of their parent folders. When using this example, and before removing the SELinux context added for <code class="filename">/web/</code>, files and directories created in the <code class="filename">/web/</code> directory are labeled with the <code class="computeroutput">httpd_sys_content_t</code> type.
+						Por defecto, los archivos y directorios recién creados heredan el tipo SELinux de sus carpetas padres. Cuando se usó este ejemplo, y antes de eliminar el contexto SELinux agregado para <code class="filename">/web/</code>, los archivos y directorios creados en el directorio <code class="filename">/web/</code> fueron etiquetados con el tipo <code class="computeroutput">httpd_sys_content_t</code>.
 					</div></li><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">/usr/sbin/semanage fcontext -d /web</code> command to remove the context added for <code class="filename">/web/</code>.
+						Como usuario root de Linux, ejecute el comando <code class="command">/usr/sbin/semanage fcontext -d /web</code> para borrar el contexto agregado para <code class="filename">/web/</code>.
 					</div></li><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">/sbin/restorecon -v /web</code> command to restore the default SELinux context.
-					</div></li></ol></div><div class="formalpara"><h5 class="formalpara">Changing a Directory and its Contents Types</h5>
-					The following example demonstrates creating a new directory, and changing the directory's file type (along with its contents) to a type used by Apache HTTP Server. The configuration in this example is used if you want Apache HTTP Server to use a different document root (instead of <code class="filename">/var/www/html/</code>):
+						Como usuario root de Linux, ejecute el comando <code class="command">/sbin/restorecon -v /web</code> para restaurar el contexto predeterminado de SELinux.
+					</div></li></ol></div><div class="formalpara" id="form-Security-Enhanced_Linux-Persistent_Changes_semanage_fcontext-Changing_a_Directory_and_its_Contents_Types"><h5 class="formalpara">Cambio de un Directorio y sus Tipos de Contenidos</h5>
+					El siguiente ejemplo muestra la creación de un directorio nuevo y el cambio del tipo de archivo del mismo (junto con su contenido) a un tipo usado por el Servidor HTTP Apache. La configuración en este ejemplo se usa si quiere que el Servidor HTTP Apache use una raíz de documento distinta (en vez de <code class="filename">/var/www/html/</code>):
 				</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">mkdir /web</code> command to create a new directory, and then the <code class="command">touch /web/file{1,2,3}</code> command to create 3 empty files (<code class="filename">file1</code>, <code class="filename">file2</code>, and <code class="filename">file3</code>). The <code class="filename">/web/</code> directory and files in it are labeled with the <code class="computeroutput">default_t</code> type:
+						Como usuario root de Linux, ejecute el comando <code class="command">mkdir /web</code> para crear un directorio nuevo, y luego el comando <code class="command">touch /web/archivo{1,2,3}</code> para crear 3 archivos vacíos (<code class="filename">archivo1</code>, <code class="filename">archivo2</code> y <code class="filename">archivo3</code>). El directorio <code class="filename">/web/</code> y los archivos en él son etiquetados con el tipo <code class="computeroutput">default_t</code>:
 					</div><pre class="screen"># ls -dZ /web
 drwxr-xr-x  root root unconfined_u:object_r:default_t:s0 /web
 # ls -lZ /web
@@ -89,7 +89,7 @@ drwxr-xr-x  root root unconfined_u:object_r:default_t:s0 /web
 					</div><pre class="screen">/web(/.*)?    system_u:object_r:httpd_sys_content_t:s0
 
 </pre></li><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">/sbin/restorecon -R -v /web</code> command to change the type of the <code class="filename">/web/</code> directory, as well as all files in it. The <code class="option">-R</code> is for recursive, which means all files and directories under the <code class="filename">/web/</code> directory are labeled with the <code class="computeroutput">httpd_sys_content_t</code> type. Since the <code class="command">semanage</code> command added an entry to <code class="filename">file.contexts.local</code> for <code class="computeroutput">/web(/.*)?</code>, the <code class="command">/sbin/restorecon</code> command changes the types to <code class="computeroutput">httpd_sys_content_t</code>:
+						Como usuario root de LInux, ejecute el comando <code class="command">/sbin/restorecon -R -v /web</code> para cambiar elt ipo del directorio <code class="filename">/web/</code>, junto con los archivos dentro de él. La opción <code class="option">-R</code> significa recursivo, es decir, todos los archivos y directorios dentro del directorio <code class="filename">/web/</code> se etiquetarán con el tipo <code class="computeroutput">httpd_sys_content_t</code>. Dado que el comando <code class="command">semanage</code> agregó una entrada en <code class="filename">file.contexts.local</code> para <code class="computeroutput">/web(/.*)?</code>, el comando <code class="command">/sbin/restorecon</code> los tipos a <code class="computeroutput">httpd_sys_content_t</code>:
 					</div><pre class="screen"># /sbin/restorecon -R -v /web
 restorecon reset /web context unconfined_u:object_r:default_t:s0-&gt;system_u:object_r:httpd_sys_content_t:s0
 restorecon reset /web/file2 context unconfined_u:object_r:default_t:s0-&gt;system_u:object_r:httpd_sys_content_t:s0
@@ -97,31 +97,31 @@ restorecon reset /web/file3 context unconfined_u:object_r:default_t:s0-&gt;syste
 restorecon reset /web/file1 context unconfined_u:object_r:default_t:s0-&gt;system_u:object_r:httpd_sys_content_t:s0
 
 </pre><div class="para">
-						By default, newly-created files and directories inherit the SELinux type of their parents. In this example, files and directories created in the <code class="filename">/web/</code> directory will be labeled with the <code class="computeroutput">httpd_sys_content_t</code> type.
+						Por defecto, los archivos y directorios recién creados heredan el tipo SELinux de sus padres. En este ejemplo, los archivos y directorios creado en el directorio <code class="filename">/web/</code> se etiquetarán con el tipo <code class="computeroutput">httpd_sys_content_t</code>.
 					</div></li><li class="listitem"><div class="para">
 						As the Linux root user, run the <code class="command">/usr/sbin/semanage fcontext -d "/web(/.*)?"</code> command to remove the context added for <code class="computeroutput">"/web(/.*)?"</code>.
 					</div></li><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">/sbin/restorecon -R -v /web</code> command to restore the default SELinux contexts.
-					</div></li></ol></div><div class="formalpara"><h5 class="formalpara">Deleting an added Context</h5>
-					The following example demonstrates adding and removing an SELinux context:
+						Como usuario root de Linux, ejecute el comando <code class="command">/sbin/restorecon -R -v /web</code> para restaurar el contexto predeterminado de SELinux.
+					</div></li></ol></div><div class="formalpara" id="form-Security-Enhanced_Linux-Persistent_Changes_semanage_fcontext-Deleting_an_added_Context"><h5 class="formalpara">Borrado de un Contexto agregado</h5>
+					El siguiente ejemplo muestra el agregado y su eliminación del contexto de SELinux:
 				</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">/usr/sbin/semanage fcontext -a -t httpd_sys_content_t /test</code> command. The <code class="filename">/test/</code> directory does not have to exist. This command adds the following context to <code class="filename">/etc/selinux/targeted/contexts/files/file_contexts.local</code>:
+						Como usuario root de Linux, ejecute el comando <code class="command">/usr/sbin/semanage fcontext -a -t httpd_sys_content_t /prueba</code>. El directorio <code class="filename">/prueba/</code> no tiene que existir. Este comando agrega el siguiente contexto a <code class="filename">/etc/selinux/targeted/contexts/files/file_contexts.local</code>:
 					</div><pre class="screen">/test    system_u:object_r:httpd_sys_content_t:s0
 
 </pre></li><li class="listitem"><div class="para">
-						To remove the context, as the Linux root user, run the <code class="command">/usr/sbin/semanage fcontext -d <em class="replaceable"><code>file-name</code></em>|<em class="replaceable"><code>directory-name</code></em></code> command, where <em class="replaceable"><code>file-name</code></em>|<em class="replaceable"><code>directory-name</code></em> is the first part in <code class="filename">file_contexts.local</code>. The following is an example of a context in <code class="filename">file_contexts.local</code>:
+						Para eliminar el contexto, como usuario root de Linux, ejecute el comando <code class="command">/usr/sbin/semanage fcontext -d <em class="replaceable"><code>nombre-de-archivo</code></em>|<em class="replaceable"><code>nombre-de-directorio</code></em></code>, donde <em class="replaceable"><code>nombre-de-archivo</code></em>|<em class="replaceable"><code>nombre-de-directorio</code></em> es la primera parte en <code class="filename">file_contexts.local</code>. El siguiente es un ejemplo de un contexto en <code class="filename">file_contexts.local</code>:
 					</div><pre class="screen">/test    system_u:object_r:httpd_sys_content_t:s0
 
 </pre><div class="para">
-						With the first part being <code class="computeroutput">/test</code>. To prevent the <code class="filename">/test/</code> directory from being labeled with the <code class="computeroutput">httpd_sys_content_t</code> after running <code class="command">/sbin/restorecon</code>, or after a file system relabel, run the following command as the Linux root user to delete the context from <code class="filename">file_contexts.local</code>:
+						Siendo la primera parte <code class="computeroutput">/prueba</code>. Para evitar que el directorio <code class="filename">/prueba/</code> se etiquete con <code class="computeroutput">httpd_sys_content_t</code> después de ejecutar <code class="command">/sbin/restorecon</code>, o después de un reetiquetado del sistema, ejecute el siguiente comando como usuario root de Linux para eliminar el contexto de <code class="filename">file_contexts.local</code>:
 					</div><div class="para">
 						<code class="command">/usr/sbin/semanage fcontext -d /test</code>
 					</div></li></ol></div><div class="para">
-				If the context is part of a regular expression, for example, <code class="computeroutput">/web(/.*)?</code>, use quotation marks around the regular expression:
+				Si el contexto es parte de una expresión regular, por ejemplo <code class="computeroutput">/web(/.*)?</code>, use las comillas para encerrar la expresión regular:
 			</div><div class="para">
 				<code class="command">/usr/sbin/semanage fcontext -d "/web(/.*)?"</code>
 			</div><div class="para">
-				Refer to the <span class="citerefentry"><span class="refentrytitle">semanage</span>(8)</span> manual page for further information about <code class="command">/usr/sbin/semanage</code>.
+				Vaya a la página de manual de <span class="citerefentry"><span class="refentrytitle">semanage</span>(8)</span> para información adicional sobre <code class="command">/usr/sbin/semanage</code>.
 			</div><div class="important"><h2>Importante</h2><div class="para">
-					When changing the SELinux context with <code class="command">/usr/sbin/semanage fcontext -a</code>, use the full path to the file or directory to avoid files being mislabeled after a file system relabel, or after the <code class="command">/sbin/restorecon</code> command is run.
-				</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files.html"><strong>Anterior</strong>5.7. SELinux Contexts - Labeling Files</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types.html"><strong>Siguiente</strong>5.8. The file_t and default_t Types</a></li></ul></body></html>
+					Cuando se cambia el contexto de SELinux con <code class="command">/usr/sbin/semanage fcontext -a</code>, use la dirección completa del archivo o directorio para evitar etiquetar mal los archivos después de un reetiquetado del sistema de archivo, o después ejecutar el comando <code class="command">/sbin/restorecon</code>.
+				</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files.html"><strong>Anterior</strong>5.7. Contextos de SELinux - Etiquetado de Archivos</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types.html"><strong>Siguiente</strong>5.8. Los tipos file_t y default_t</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users.html
index c906b3b..b465740 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users.html
@@ -1,7 +1,7 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.3. Confined and Unconfined Users</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="chap-Security-Enhanced_Linux-Targeted_Policy.html" title="Capítulo 4. Targeted Policy" /><link rel="prev" href="sect-Security-Enhanced_Linux-Targeted_Policy-Unconfined_Processes.html" title="4.2. Unconfined Processes" /><link rel="next" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html" title="Capítulo 5. Working with SELinux" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class
 ="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Targeted_Policy-Unconfined_Processes.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="4.3. Confined and Unconfined Users" id="sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.3. Confined and Unconfined Users</h2></div></div
 ></div><div class="para">
-			Each Linux user is mapped to an SELinux user via SELinux policy. This allows Linux users to inherit the restrictions on SELinux users. This Linux user mapping is seen by running the <code class="command">semanage login -l</code> command as the Linux root user:
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.3. Usuarios Confinados y no Confinados</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Targeted_Policy.html" title="Capítulo 4. Política Destinado" /><link rel="prev" href="sect-Security-Enhanced_Linux-Targeted_Policy-Unconfined_Processes.html" title="4.2. Procesos no Confinados" /><link rel="next" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html" title="Capítulo 5. Trabajando con SELinux" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe 
 id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Targeted_Policy-Unconfined_Processes.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="4.3. Usuarios Confinados y no Confinados" id="sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.3. Usuarios Confinados 
 y no Confinados</h2></div></div></div><div class="para">
+			Cada usuario Linux se mapea a un usuario SELinux vía la política de SELinux. Esto permite a los usuarios Linux heredar las restricciones sobre los usuarios SELinux. Este mapeo de usuarios Linux se ve ejecutando el comando <code class="command">semanage login -l</code> como usuario root de Linux:
 		</div><pre class="screen"># /usr/sbin/semanage login -l
 
 Login Name                SELinux User              MLS/MCS Range
@@ -11,13 +11,13 @@ root                      unconfined_u              s0-s0:c0.c1023
 system_u                  system_u                  s0-s0:c0.c1023
 
 </pre><div class="para">
-			In Fedora 11, Linux users are mapped to the SELinux <code class="computeroutput">__default__</code> login by default (which is mapped to the SELinux <code class="computeroutput">unconfined_u</code> user). The following defines the default-mapping:
+			En Fedora 11, los usuarios de Linux se mapean por defecto al ingreso <code class="computeroutput">__default__</code> de SELinux (el cual se mapea al usuario SELinux <code class="computeroutput">unconfined_u</code>). Lo siguiente define el mapeo por defecto:
 		</div><pre class="screen">__default__               unconfined_u              s0-s0:c0.c1023
 
 </pre><div class="para">
-			The following example demonstrates adding a new Linux user, and that Linux user being mapped to the SELinux <code class="computeroutput">unconfined_u</code> user. It assumes that the Linux root user is running unconfined, as it does by default in Fedora 11:
+			El siguiente ejemplo muestra el agregado de un usuario de Linux nuevo y el mapeo de ese usuario al usuario SELinux <code class="computeroutput">unconfined_u</code>. Asume que el usuario root corre no confinado, como es por defecto en Fedora 11:
 		</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
-					As the Linux root user, run the <code class="command">/usr/sbin/useradd newuser</code> command to create a new Linux user named newuser.
+					Como usuario root de Linux, ejecute el comando <code class="command">/usr/sbin/useradd usuarionuevo</code> para crear un nuevo usuario Linux con nombre usuarionuevo.
 				</div></li><li class="listitem"><div class="para">
 					As the Linux root user, run the <code class="command">passwd newuser</code> command to assign a password to the Linux newuser user:
 				</div><pre class="screen"># passwd newuser
@@ -27,28 +27,28 @@ Retype new UNIX password: <em class="replaceable"><code>Enter the same password
 passwd: all authentication tokens updated successfully.
 
 </pre></li><li class="listitem"><div class="para">
-					Log out of your current session, and log in as the Linux newuser user. When you log in, pam_selinux maps the Linux user to an SELinux user (in this case, unconfined_u), and sets up the resulting SELinux context. The Linux user's shell is then launched with this context. Run the <code class="command">id -Z</code> command to view the context of a Linux user:
+					Salga de su sesión actual e ingrese como el usuario Linux usuarionuevo. Cuando ingrese, pam_selinux mapea el usuario Linux a un usuario SELinux (en este caso, unconfined_u), y configura el contexto SELinux resultante. El shell del usuario Linux es entonces lanzado en este contexto. Corra el comando <code class="command">id -Z</code> para ver el contexto de un usuario Linux:
 				</div><pre class="screen">[newuser at localhost ~]$ id -Z
 unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
 
 </pre></li><li class="listitem"><div class="para">
-					Log out of the Linux newuser's session, and log in with your account. If you do not want the Linux newuser user, run the <code class="command">/usr/sbin/userdel -r newuser</code> command as the Linux root user to remove it, along with the Linux newuser's home directory.
+					Salga de la sesión del usuarionuevo de Linux e ingrese con su cuenta. Si no quiere el usuario usuarionuevo, ejecute el comando <code class="command">/usr/sbin/userdel -r usuarionuevo</code> como usuario root de Linux para eliminarlo, junto con su directorio de inicio.
 				</div></li></ol></div><div class="para">
-			Confined and unconfined Linux users are subject to executable and writeable memory checks, and are also restricted by MCS (and MLS, if the MLS policy is used). If unconfined Linux users execute an application that SELinux policy defines can transition from the <code class="computeroutput">unconfined_t</code> domain to its own confined domain, unconfined Linux users are still subject to the restrictions of that confined domain. The security benefit of this is that, even though a Linux user is running unconfined, the application remains confined, and therefore, the exploitation of a flaw in the application can be limited by policy. Note: this does not protect the system from the user. Instead, the user and the system are being protected from possible damage caused by a flaw in the application.
+			Los usuarios Linux confinados y no confinados son sujeto a chequeso de memoria escribible y ejecutable, y también son restringidos por MCS (y MLS, si la política MLS está siendo usada). Si los usuarios Linux no confinados ejecutan una aplicación que la política de SELinux define que puede transicionar del dominio <code class="computeroutput">unconfined_t</code> a su propio dominio confinado, los usuarios Linux no confinados están sujetos a restricciones de ese dominio confinado. El beneficio de seguridad de esto es que, aunque un usuario Linux corra no confinado, la aplicación permanece confinada, y por lo tanto, la explotación de una brecha en la aplicación está limitada por la política. Nota: esto no protege al sistema del usuario. En su defecto, el usuario y el sistema están siendo protegidos de posibles daños causados por una brecha en la aplicación.
 		</div><div class="para">
-			The following confined SELinux users are available in Fedora 11:
-		</div><div class="table"><div class="table-contents"><table summary="SELinux User Capabilities" border="1"><colgroup><col width="17%" /><col width="17%" /><col width="17%" /><col width="17%" /><col width="17%" /><col width="17%" /></colgroup><thead><tr><th>
-							User
+			Los siguientes usuarios SELinux confinados están disponibles en Fedora 11:
+		</div><div class="table" title="Tabla 4.1. Capacidades del Usuario SELinux" id="tabl-Security-Enhanced_Linux-Confined_and_Unconfined_Users-SELinux_User_Capabilities"><div class="table-contents"><table summary="Capacidades del Usuario SELinux" border="1"><colgroup><col width="17%" /><col width="17%" /><col width="17%" /><col width="17%" /><col width="17%" /><col width="17%" /></colgroup><thead><tr><th>
+							Usuario
 						</th><th>
-							Domain
+							Dominio
 						</th><th>
-							X Window System
+							Sistema de Ventanas X
 						</th><th>
-							su and sudo
+							su y sudo
 						</th><th>
-							Execute in home directory and /tmp/
+							Ejecute en el directorio de inicio y /tmp/
 						</th><th>
-							Networking
+							Red
 						</th></tr></thead><tbody><tr><td>
 							guest_u
 						</td><td>
@@ -97,18 +97,18 @@ unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
 							optional
 						</td><td align="center">
 							yes
-						</td></tr></tbody></table></div><h6>Tabla 4.1. SELinux User Capabilities</h6></div><br class="table-break" /><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-					Linux users in the <code class="computeroutput">guest_t</code>, <code class="computeroutput">xguest_t</code>, and <code class="computeroutput">user_t</code> domains can only run set user ID (setuid) applications if SELinux policy permits it (such as <code class="command">passwd</code>). They can not run the <code class="command">su</code> and <code class="command">/usr/bin/sudo</code> setuid applications, and therefore, can not use these applications to become the Linux root user.
+						</td></tr></tbody></table></div><h6>Tabla 4.1. Capacidades del Usuario SELinux</h6></div><br class="table-break" /><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+					Los usuarios Linux en los dominios <code class="computeroutput">guest_t</code>, <code class="computeroutput">xguest_t</code> y <code class="computeroutput">user_t</code> sólo pueden ejecutar aplicaciones con ID de usuario (setuid) si la política de SELinux lo permite (tal como <code class="command">passwd</code>). No podrán ejecutar <code class="command">su</code> y <code class="command">/usr/bin/sudo</code>
 				</div></li><li class="listitem"><div class="para">
-					Linux users in the <code class="computeroutput">guest_t</code> domain have no network access, and can only log in via a terminal (including <code class="systemitem">ssh</code>; they can log in via <code class="systemitem">ssh</code>, but can not use <code class="systemitem">ssh</code> to connect to another system).
+					Los usuarios Linux en el dominio <code class="computeroutput">guest_t</code> no tienen acceso a la red, y sólo pueden ingresar vía una terminal (incluyendo <code class="systemitem">ssh</code>; pueden ingresaro por <code class="systemitem">ssh</code>, pero no se pueden <code class="systemitem">ssh</code> conectar a otro sistema).
 				</div></li><li class="listitem"><div class="para">
-					The only network access Linux users in the <code class="computeroutput">xguest_t</code> domain have is <span class="application"><strong>Firefox</strong></span> connecting to web pages.
+					El único acceso de red que tienen los usuarios en el dominoi <code class="computeroutput">xguest_t</code> es con <span class="application"><strong>Firefox</strong></span> conectándose a páginas web.
 				</div></li><li class="listitem"><div class="para">
-					Linux users in the <code class="computeroutput">xguest_t</code>, <code class="computeroutput">user_t</code> and <code class="computeroutput">staff_t</code> domains can log in via the X Window System and a terminal.
+					Los usuarios Linux en los dominios <code class="computeroutput">xguest_t</code>, <code class="computeroutput">user_t</code> y <code class="computeroutput">staff_t</code> pueden ingresar vía el Sistema de Ventanas X o por una terminal.
 				</div></li><li class="listitem"><div class="para">
-					By default, Linux users in the <code class="computeroutput">staff_t</code> domain do not have permissions to execute applications with <code class="command">/usr/bin/sudo</code>. These permissions must be configured by an administrator.
+					Por defecto, los usuarios Linux en el dominio <code class="computeroutput">staff_t</code> no tienen permisos para ejecutar aplicaciones con <code class="command">/usr/bin/sudo</code>. Estos permisos deben ser configurados por un administrador.
 				</div></li></ul></div><div class="para">
-			By default, Linux users in the <code class="computeroutput">guest_t</code> and <code class="computeroutput">xguest_t</code> domains can not execute applications in their home directories or <code class="filename">/tmp/</code>, preventing them from executing applications (which inherit users' permissions) in directories they have write access to. This helps prevent flawed or malicious applications from modifying files users' own.
+			Por defecto, los usuarios de Linux en los dominios <code class="computeroutput">guest_t</code> y <code class="computeroutput">xguest_t</code> no pueden ejecutar aplicaciones en sus directorios de inicio o en <code class="filename">/tmp/</code>, previniéndolos de ejecutar aplicaciones (que hereden los permisos de los usuarios) en directorios a los que tienen acceso de escritura. Esto ayuda a prevenir que aplicaciones maliciosas modifiquen archivos de los usuarios.
 		</div><div class="para">
-			By default, Linux users in the <code class="computeroutput">user_t</code> and <code class="computeroutput">staff_t</code> domains can execute applications in their home directories and <code class="filename">/tmp/</code>. Refer to <a class="xref" href="sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications.html" title="6.6. Booleans for Users Executing Applications">Sección 6.6, “Booleans for Users Executing Applications”</a> for information about allowing and preventing users from executing applications in their home directories and <code class="filename">/tmp/</code>.
-		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Targeted_Policy-Unconfined_Processes.html"><strong>Anterior</strong>4.2. Unconfined Processes</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html"><strong>Siguiente</strong>Capítulo 5. Working with SELinux</a></li></ul></body></html>
+			By default, Linux users in the <code class="computeroutput">user_t</code> and <code class="computeroutput">staff_t</code> domains can execute applications in their home directories and <code class="filename">/tmp/</code>. Refer to <a class="xref" href="sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications.html" title="6.6. Booleanos para que los Usuarios Ejecuten Aplicaciones">Sección 6.6, “Booleanos para que los Usuarios Ejecuten Aplicaciones”</a> for information about allowing and preventing users from executing applications in their home directories and <code class="filename">/tmp/</code>.
+		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Targeted_Policy-Unconfined_Processes.html"><strong>Anterior</strong>4.2. Procesos no Confinados</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html"><strong>Siguiente</strong>Capítulo 5. Trabajando con SELinux</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Targeted_Policy-Unconfined_Processes.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Targeted_Policy-Unconfined_Processes.html
index fba069b..212a9f9 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Targeted_Policy-Unconfined_Processes.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Targeted_Policy-Unconfined_Processes.html
@@ -1,11 +1,11 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.2. Unconfined Processes</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="chap-Security-Enhanced_Linux-Targeted_Policy.html" title="Capítulo 4. Targeted Policy" /><link rel="prev" href="chap-Security-Enhanced_Linux-Targeted_Policy.html" title="Capítulo 4. Targeted Policy" /><link rel="next" href="sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users.html" title="4.3. Confined and Unconfined Users" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class=
 "toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-Targeted_Policy.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="4.2. Unconfined Processes" id="sect-Security-Enhanced_Linux-Targeted_Policy-Unconfined_Processes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.2. Unconfined Processes</h2></div></div></div><div class="para"
 >
-			Unconfined processes run in unconfined domains, for example, init programs run in the unconfined <code class="computeroutput">initrc_t</code> domain, unconfined kernel processes run in the <code class="computeroutput">kernel_t</code> domain, and unconfined Linux users run in the <code class="computeroutput">unconfined_t</code> domain. For unconfined processes, SELinux policy rules are applied, but policy rules exist that allow processes running in unconfined domains almost all access. Processes running in unconfined domains fall back to using DAC rules exclusively. If an unconfined process is compromised, SELinux does not prevent an attacker from gaining access to system resources and data, but of course, DAC rules are still used. SELinux is a security enhancement on top of DAC rules - it does not replace them.
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.2. Procesos no Confinados</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Targeted_Policy.html" title="Capítulo 4. Política Destinado" /><link rel="prev" href="chap-Security-Enhanced_Linux-Targeted_Policy.html" title="Capítulo 4. Política Destinado" /><link rel="next" href="sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users.html" title="4.3. Usuarios Confinados y no Confinados" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe
  id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-Targeted_Policy.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="4.2. Procesos no Confinados" id="sect-Security-Enhanced_Linux-Targeted_Policy-Unconfined_Processes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.2. Procesos no Confinados</h2></div></di
 v></div><div class="para">
+			Los procesos no confinados corren en dominios no confinados, por ejemplo, los programas init (del arranque) corren en el dominio no confinado <code class="computeroutput">initrc_t</code>, los procesos no confinados del kernel corren en el dominio <code class="computeroutput">kernel_t</code> y los usuarios no confinados deLInux corren en el dominio <code class="computeroutput">unconfined_t</code>. Para procesos no confinados, las reglas de la política de SELinux son aplicadas, pero hay reglas de la política que permiten que los procesos se ejecuten en dominios no confinados tengan casi todos los accesos. Los procesos que corren en dominios no confinados terminan usando exclusivamente las reglas DAC. Si un proceso no confinado es comprometido, SELinux no impide que un atacante gane acceso a los recursos del sistema y a los datos, pero, por supuesto, las reglas DAC todavía se usan. SELinux es una mejora de seguridad sobre las reglas DAC - no las reemplaza.
 		</div><div class="para">
-			The following example demonstrates how the Apache HTTP Server (<code class="systemitem">httpd</code>) can access data intended for use by Samba, when running unconfined. Note: in Fedora 11, the <code class="systemitem">httpd</code> process runs in the confined <code class="computeroutput">httpd_t</code> domain by default. This is an example, and should not be used in production. It assumes that the <span class="package">httpd</span>, <span class="package">wget</span>, <span class="package">setroubleshoot-server</span>, and <span class="package">audit</span> packages are installed, that the SELinux targeted policy is used, and that SELinux is running in enforcing mode:
+			El siguiente ejemplo muestra cómo el Servidor HTTP Apache (<code class="systemitem">httpd</code>) puede acceder datos que se suponen son para ser usados por Samba, cuando se corre no confinado. Nota: en Fedora 11, el proceso <code class="systemitem">httpd</code> corre en el dominio confinado <code class="computeroutput">httpd_t</code> por defecto. Este es un ejemplo, y no debe usarse en producción. Se asume que los paquetes <span class="package">httpd</span>, <span class="package">wget</span>, <span class="package">setroubleshoot-server</span>, y <span class="package">audit</span> están instalados, que se usa la política destinada de SELinux y que SELinux corre en modo obligatorio:
 		</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
-					Run the <code class="command">sestatus</code> command to confirm that SELinux is enabled, is running in enforcing mode, and that targeted policy is being used:
+					Ejecute el comando <code class="command">sestatus</code> para confirmar que SELinux está activado, se ejecuta en modo obligatorio y que la política destinada se está usando:
 				</div><pre class="screen">
 $ /usr/sbin/sestatus
 SELinux status:                 enabled
@@ -18,46 +18,46 @@ Policy from config file:        targeted
 </pre><div class="para">
 					<code class="computeroutput">SELinux status: enabled</code> is returned when SELinux is enabled. <code class="computeroutput">Current mode: enforcing</code> is returned when SELinux is running in enforcing mode. <code class="computeroutput">Policy from config file: targeted</code> is returned when the SELinux targeted policy is used.
 				</div></li><li class="listitem"><div class="para">
-					As the Linux root user, run the <code class="command">touch /var/www/html/test2file</code> command to create a file.
+					Como usuario root de Linux, corra el comando <code class="command">touch /var/www/html/prueba2</code> para crear un archivo.
 				</div></li><li class="listitem"><div class="para">
-					Run the <code class="command">ls -Z /var/www/html/test2file</code> command to view the SELinux context:
+					Ejecute el comando <code class="command">ls -Z /var/www/html/prueba2</code> para ver el contexto SELinux:
 				</div><pre class="screen">-rw-r--r--  root root unconfined_u:object_r:httpd_sys_content_t:s0 /var/www/html/test2file
 
 </pre><div class="para">
-					By default, Linux users run unconfined in Fedora 11, which is why the <code class="filename">test2file</code> file is labeled with the SELinux <code class="computeroutput">unconfined_u</code> user. RBAC is used for processes, not files. Roles do not have a meaning for files - the <code class="computeroutput">object_r</code> role is a generic role used for files (on persistent storage and network file systems). Under the <code class="filename">/proc/</code> directory, files related to processes may use the <code class="computeroutput">system_r</code> role.<sup>[<a id="id1612571" href="#ftn.id1612571" class="footnote">7</a>]</sup> The <code class="computeroutput">httpd_sys_content_t</code> type allows the <code class="systemitem">httpd</code> process to access this file.
+					Por defecto, los usuarios Linux corren no confinados en Fedora 11, razón por la cual el archivo <code class="filename">prueba2</code> está etiquetado con el usuario SELinux <code class="computeroutput">unconfined_u</code>. RBAC se usa para procesos, no para archivos. Los roles no tienen un significado para archivos - el rol <code class="computeroutput">object_r</code> es el rol genérico que se usa para archivos (en almacenamiento persistente y sistemas de archivos de red). Bajo el directorio <code class="filename">/proc/</code>, los archivos relacionados con procesos pueden usar el rol <code class="computeroutput">system_r</code>.<sup>[<a id="id858849" href="#ftn.id858849" class="footnote">7</a>]</sup> El tipo <code class="computeroutput">httpd_sys_content_t</code> permite al proceso <code class="systemitem">httpd</code> acceder a este archivo.
 				</div></li><li class="listitem"><div class="para">
-					The <code class="command">chcon</code> command relabels files; however, such label changes do not survive when the file system is relabeled. For permanent changes that survive a file system relabel, use the <code class="command">semanage</code> command, which is discussed later. As the Linux root user, run the following command to change the type to a type used by Samba:
+					El comando <code class="command">chcon</code> reetiqueta archivos; sin embargo, tales cambios de etiquetas no sobreviven cuando el sistema se reetiqueta. Para que los cambios sobrevivan un reetiquetado del sistema, use el comando <code class="command">semanage</code>, que se discute más adelante. Como usuario root de Linux, corra el siguiente comando para cambiar el tipo a un tipo usado por Samba:
 				</div><div class="para">
 					<code class="command">chcon -t samba_share_t /var/www/html/test2file</code>
 				</div><div class="para">
-					Run the <code class="command">ls -Z /var/www/html/test2file</code> command to view the changes:
+					Ejecute el comando <code class="command">ls -Z /var/www/html/prueba2</code> para ver los cambios:
 				</div><pre class="screen">-rw-r--r--  root root unconfined_u:object_r:samba_share_t:s0 /var/www/html/test2file
 
 </pre></li><li class="listitem"><div class="para">
-					Run the <code class="command">service httpd status</code> command to confirm that the <code class="systemitem">httpd</code> process is not running:
+					Corra el comando <code class="command">service httpd status</code> para confirmar que el proceso <code class="systemitem">httpd</code> no se está ejecutando:
 				</div><pre class="screen">$ /sbin/service httpd status
 httpd is stopped
 
 </pre><div class="para">
-					If the output differs, run the <code class="command">service httpd stop</code> command as the Linux root user to stop the <code class="systemitem">httpd</code> process:
+					Si la salida difiere, ejecute <code class="command">service httpd stop</code> como usuario root de Linux para detener el proceso <code class="systemitem">httpd</code>:
 				</div><pre class="screen"># /sbin/service httpd stop
 Stopping httpd:                                            [  OK  ]
 
 </pre></li><li class="listitem"><div class="para">
-					To make the <code class="systemitem">httpd</code> process run unconfined, run the following command as the Linux root user to change the type of <code class="filename">/usr/sbin/httpd</code>, to a type that does not transition to a confined domain:
+					Para hacer que el proceso <code class="systemitem">httpd</code> corra no confinado, ejecute el siguiente comando como usuario root de Linux para cambiar el tipo de <code class="filename">/usr/sbin/httpd</code>, a un tipo que no transicione a un dominio confinado:
 				</div><div class="para">
 					<code class="command">chcon -t unconfined_exec_t /usr/sbin/httpd</code>
 				</div></li><li class="listitem"><div class="para">
-					Run the <code class="command">ls -Z /usr/sbin/httpd</code> command to confirm that <code class="filename">/usr/sbin/httpd</code> is labeled with the <code class="computeroutput">unconfined_exec_t</code> type:
+					Ejecute el comando <code class="command">ls -Z /usr/sbin/httpd</code> para confirmar que <code class="filename">/usr/sbin/httpd</code> está etiquetado con el tipo <code class="computeroutput">unconfined_exec_t</code>:
 				</div><pre class="screen">-rwxr-xr-x  root root system_u:object_r:unconfined_exec_t /usr/sbin/httpd
 
 </pre></li><li class="listitem"><div class="para">
-					As the Linux root user, run the <code class="command">service httpd start</code> command to start the <code class="systemitem">httpd</code> process. The output is as follows if <code class="systemitem">httpd</code> starts successfully:
+					Como usuario root de Linux, ejecute el comando <code class="command">service httpd start</code> para iniciar el proceso <code class="systemitem">httpd</code>. La salida escomo sigue si <code class="systemitem">httpd</code> inicia con éxito:
 				</div><pre class="screen"># /sbin/service httpd start
 Starting httpd:                                            [  OK  ]
 
 </pre></li><li class="listitem"><div class="para">
-					Run the <code class="command">ps -eZ | grep httpd</code> command to view the <code class="systemitem">httpd</code> running in the <code class="computeroutput">unconfined_t</code> domain:
+					Ejecute el comando <code class="command">ps -eZ | grep httpd</code> para ver si <code class="systemitem">httpd</code> está corriendo en el dominio <code class="computeroutput">unconfined_t</code>:
 				</div><pre class="screen">$ ps -eZ | grep httpd
 unconfined_u:system_r:unconfined_t <em class="replaceable"><code>7721</code></em> ?      00:00:00 httpd
 unconfined_u:system_r:unconfined_t <em class="replaceable"><code>7723</code></em> ?      00:00:00 httpd
@@ -70,7 +70,7 @@ unconfined_u:system_r:unconfined_t <em class="replaceable"><code>7729</code></em
 unconfined_u:system_r:unconfined_t <em class="replaceable"><code>7730</code></em> ?      00:00:00 httpd
 
 </pre></li><li class="listitem"><div class="para">
-					Change into a directory where your Linux user has write access to, and run the <code class="command">wget http://localhost/test2file</code> command. Unless there are changes to the default configuration, this command succeeds:
+					Cambie al directorio donde su usuario Linux tenga permiso de escritura y ejecute el comando <code class="command">wget http://localhost/prueba2</code>. A menos que hayan cambios en la configuración predeterminada, este comando debería tener éxito:
 				</div><pre class="screen">--2009-05-07 01:41:10--  http://localhost/test2file
 Resolving localhost... 127.0.0.1
 Connecting to localhost|127.0.0.1|:80... connected.
@@ -83,19 +83,19 @@ Saving to: `test2file.1'
 2009-05-07 01:41:10 (0.00 B/s) - `test2file.1' saved [0/0]
 
 </pre><div class="para">
-					Although the <code class="systemitem">httpd</code> process does not have access to files labeled with the <code class="computeroutput">samba_share_t</code> type, <code class="systemitem">httpd</code> is running in the unconfined <code class="computeroutput">unconfined_t</code> domain, and falls back to using DAC rules, and as such, the <code class="command">wget</code> command succeeds. Had <code class="systemitem">httpd</code> been running in the confined <code class="computeroutput">httpd_t</code> domain, the <code class="command">wget</code> command would have failed.
+					Aunque el proceso <code class="systemitem">httpd</code> no tiene acceso a archivos etiquetados con el tipo <code class="computeroutput">samba_share_t</code>, <code class="systemitem">httpd</code> se ejecuta en el dominio <code class="computeroutput">unconfined_t</code>, y termina usando las reglas DAC, como tal, el comando <code class="command">wget</code> tiene éxito. Teniendo a <code class="systemitem">httpd</code> ejecutándose en el dominio <code class="computeroutput">httpd_t</code>, el comando <code class="command">wget</code> habría fallado.
 				</div></li><li class="listitem"><div class="para">
-					The <code class="command">restorecon</code> command restores the default SELinux context for files. As the Linux root user, run the <code class="command">restorecon -v /usr/sbin/httpd</code> command to restore the default SELinux context for <code class="filename">/usr/sbin/httpd</code>:
+					El comando <code class="command">restorecon</code> restaura el contexto SELinux predeterminado de los archivos. Como usuario root de Linux, ejecute el comando <code class="command">restorecon -v /usr/sbin/httpd</code> para restaurar el contexto SELinux de <code class="filename">/usr/sbin/httpd</code>:
 				</div><pre class="screen"># /sbin/restorecon -v /usr/sbin/httpd
 restorecon reset /usr/sbin/httpd context system_u:object_r:unconfined_notrans_exec_t:s0-&gt;system_u:object_r:httpd_exec_t:s0
 
 </pre><div class="para">
-					Run the <code class="command">ls -Z /usr/sbin/httpd</code> command to confirm that <code class="filename">/usr/sbin/httpd</code> is labeled with the <code class="computeroutput">httpd_exec_t</code> type:
+					Ejecute el comando <code class="command">ls -Z /usr/sbin/httpd</code> para confirmar que <code class="filename">/usr/sbin/httpd</code> está etiquetado con el tipo <code class="computeroutput">httpd_exec_t</code>:
 				</div><pre class="screen">$ ls -Z /usr/sbin/httpd
 -rwxr-xr-x  root root system_u:object_r:httpd_exec_t   /usr/sbin/httpd
 
 </pre></li><li class="listitem"><div class="para">
-					As the Linux root user, run the <code class="command">/sbin/service httpd restart</code> command to restart <code class="systemitem">httpd</code>. After restarting, run the <code class="command">ps -eZ | grep httpd</code> to confirm that <code class="systemitem">httpd</code> is running in the confined <code class="computeroutput">httpd_t</code> domain:
+					Como usuario root de Linux, corra el comando <code class="command">/sbin/service httpd restart</code> para reiniciar <code class="systemitem">httpd</code>. Después de reiniciar, ejecute <code class="command">ps -eZ | grep httpd</code> para confirmar que <code class="systemitem">httpd</code> se está ejecutando en el dominio confinado <code class="computeroutput">httpd_t</code>:
 				</div><pre class="screen"># /sbin/service httpd restart
 Stopping httpd:                                            [  OK  ]
 Starting httpd:                                            [  OK  ]
@@ -111,14 +111,14 @@ unconfined_u:system_r:httpd_t    8888 ?        00:00:00 httpd
 unconfined_u:system_r:httpd_t    8889 ?        00:00:00 httpd
 
 </pre></li><li class="listitem"><div class="para">
-					As the Linux root user, run the <code class="command">rm -i /var/www/html/test2file</code> command to remove <code class="filename">test2file</code>.
+					Como usuario root de Linux, corra el comando <code class="command">rm -i /var/www/html/prueba2</code> para eliminar <code class="filename">prueba2</code>.
 				</div></li><li class="listitem"><div class="para">
-					If you do not require <code class="systemitem">httpd</code> to be running, as the Linux root user, run the <code class="command">service httpd stop</code> command to stop <code class="systemitem">httpd</code>:
+					Si no necesita que corra <code class="systemitem">httpd</code>, como usuario root de Linux corra el comando <code class="command">service httpd stop</code> para detener a <code class="systemitem">httpd</code>:
 				</div><pre class="screen"># /sbin/service httpd stop
 Stopping httpd:                                            [  OK  ]
 
 </pre></li></ol></div><div class="para">
-			The examples in these sections demonstrate how data can be protected from a compromised confined-process (protected by SELinux), as well as how data is more accessible to an attacker from a compromised unconfined-process (not protected by SELinux).
-		</div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id1612571" href="#id1612571" class="para">7</a>] </sup>
-						When using other policies, such as MLS, other roles may also be used, for example, <code class="computeroutput">secadm_r</code>.
-					</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-Targeted_Policy.html"><strong>Anterior</strong>Capítulo 4. Targeted Policy</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users.html"><strong>Siguiente</strong>4.3. Confined and Unconfined Users</a></li></ul></body></html>
+			Los ejemplos en estas secciones muestran cómo proteger los datos desde un proceso confinado comprometido (protegido por SELinux), así como cuánto más accesible son los datos para un atacante si el proceso comprometido estaba no confinado (no protegido por SELinux).
+		</div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id858849" href="#id858849" class="para">7</a>] </sup>
+						Cuando se usan otras políticas, tal como la MLS, se pueden usar también otros roles, por ejemplo el <code class="computeroutput">secadm_r</code>.
+					</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-Targeted_Policy.html"><strong>Anterior</strong>Capítulo 4. Política Destinado</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users.html"><strong>Siguiente</strong>4.3. Usuarios Confinados y no Confinados</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Evolving_Rules_and_Broken_Applications.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Evolving_Rules_and_Broken_Applications.html
index d5b0a27..a279675 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Evolving_Rules_and_Broken_Applications.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Evolving_Rules_and_Broken_Applications.html
@@ -1,7 +1,7 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.2.3. Evolving Rules and Broken Applications</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html" title="7.2. Top Three Causes of Problems" /><link rel="prev" href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running.html" title="7.2.2. How are Confined Services Running?" /><link rel="next" href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html" title="7.3. Fixing Problems" /></hea
 d><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="7.2.3. Evolving Rules and Broken Applications" id="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Evolving_Rules_and_Brok
 en_Applications"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.2.3. Evolving Rules and Broken Applications</h3></div></div></div><div class="para">
-				Applications may be broken, causing SELinux to deny access. Also, SELinux rules are evolving - SELinux may not have seen an application running in a certain way, possibly causing it to deny access, even though the application is working as expected. For example, if a new version of PostgreSQL is released, it may perform actions the current policy has not seen before, causing access to be denied, even though access should be allowed.
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.2.3. Evolucionando las Reglas y las Aplicaciones Rotas</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html" title="7.2. Tres Principales Causas de Problemas" /><link rel="prev" href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running.html" title="7.2.2. ¿Cómo se Ejecutan los Servicios Confinados?" /><link rel="next" href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html" t
 itle="7.3. Corrección de Problemas" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="7.2.3. Evolucionando las Reglas y las Aplicaciones Rotas" id="sect-Security-Enhanced_Lin
 ux-Top_Three_Causes_of_Problems-Evolving_Rules_and_Broken_Applications"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.2.3. Evolucionando las Reglas y las Aplicaciones Rotas</h3></div></div></div><div class="para">
+				Las aplicaciones se pueden romper, provocando que SELinux niegue el acceso. También, las reglas de SELinux evolucionan - SELinux no se debe ver como una aplicación que se ejecuta en una cierta forma, haciendo que deniegue el acceso, aún cuando la aplicación está funcionado como se espera que lo haga. Por ejemplo, si una nueva versión de PostgreSQL se lanza, puede realizar acciones sobre la política actual que no han sido vistas antes, haciendo que el acceso sea denegado, aún cuando el acceso debería ser permitido.
 			</div><div class="para">
-				For these situations, after access is denied, use <code class="command">audit2allow</code> to create a custom policy module to allow access. Refer to <a class="xref" href="sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow.html" title="7.3.8. Allowing Access: audit2allow">Sección 7.3.8, “Allowing Access: audit2allow”</a> for information about using <code class="command">audit2allow</code>.
-			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running.html"><strong>Anterior</strong>7.2.2. How are Confined Services Running?</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html"><strong>Siguiente</strong>7.3. Fixing Problems</a></li></ul></body></html>
+				For these situations, after access is denied, use <code class="command">audit2allow</code> to create a custom policy module to allow access. Refer to <a class="xref" href="sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow.html" title="7.3.8. Permitiendo el Acceso: audit2allow">Sección 7.3.8, “Permitiendo el Acceso: audit2allow”</a> for information about using <code class="command">audit2allow</code>.
+			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running.html"><strong>Anterior</strong>7.2.2. ¿Cómo se Ejecutan los Servicios Confinados?</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html"><strong>Siguiente</strong>7.3. Corrección de Problemas</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running.html
index f186a67..6077609 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running.html
@@ -1,14 +1,14 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.2.2. How are Confined Services Running?</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html" title="7.2. Top Three Causes of Problems" /><link rel="prev" href="sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html" title="7.2. Top Three Causes of Problems" /><link rel="next" href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Evolving_Rules_and_Broken_Applications.html" title="7.2.3. Evolving Rules a
 nd Broken Applications" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Evolving_Rules_and_Broken_Applications.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="7.2.2. How are Confined Services Running?" id="sect-Security-Enhanced_Linux-Top_Thr
 ee_Causes_of_Problems-How_are_Confined_Services_Running"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.2.2. How are Confined Services Running?</h3></div></div></div><div class="para">
-				Services can be run in a variety of ways. To cater for this, you must tell SELinux how you are running services. This can be achieved via Booleans that allow parts of SELinux policy to be changed at runtime, without any knowledge of SELinux policy writing. This allows changes, such as allowing services access to NFS file systems, without reloading or recompiling SELinux policy. Also, running services on non-default port numbers requires policy configuration to be updated via the <code class="command">semanage</code> command.
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.2.2. ¿Cómo se Ejecutan los Servicios Confinados?</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html" title="7.2. Tres Principales Causas de Problemas" /><link rel="prev" href="sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html" title="7.2. Tres Principales Causas de Problemas" /><link rel="next" href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Evolving_Rules_and_Broken_Applications.html
 " title="7.2.3. Evolucionando las Reglas y las Aplicaciones Rotas" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Evolving_Rules_and_Broken_Applications.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="7.2.2. ¿Cómo se Ejecutan los Servicios
  Confinados?" id="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.2.2. ¿Cómo se Ejecutan los Servicios Confinados?</h3></div></div></div><div class="para">
+				Los servicios se pueden ejecutar en una variedad de formas. Para cambiar esto, debe decirle a SELinux cómo correrá los servicios. Esto se puede conseguir vía los Booleanos que permiten que parte de las políticas de SELinux se cambien en tiempo de ejecución, sin ningún conocimiento sobre la escritura de políticas de SELinux. Esto permite cambios, tales como permitir a servicios que accedan a sistemas de archivo NFS, sin recargar o recompilar una política SELinux. También, correr servicios en números de puerto no predeterminados requiere que la configuración de la política se actualice vía el comando <code class="command">semanage</code>.
 			</div><div class="para">
-				For example, to allow the Apache HTTP Server to communicate with MySQL, turn the <code class="computeroutput">httpd_can_network_connect_db</code> Boolean on:
+				Por ejemplo, para permitir al Servidor HTTP Apache comunicarse con MySQL, active el Booleano <code class="computeroutput">httpd_can_network_connect_db</code>:
 			</div><pre class="screen">
 # /usr/sbin/setsebool -P httpd_can_network_connect_db on
 
 </pre><div class="para">
-				If access is denied for a particular service, use the <code class="command">getsebool</code> and <code class="command">grep</code> commands to see if any Booleans are available to allow access. For example, use the <code class="command">getsebool -a | grep ftp</code> command to search for FTP related Booleans:
+				Si el acceso es denegado para un servicio particular, use los comandos <code class="command">getsebool</code> y <code class="command">grep</code> para ver si algún Booleano está disponible para permitir el acceso. Por ejemplo, use el comando <code class="command">getsebool -a | grep ftp</code> para buscar un Booleano relacionado con FTP:
 			</div><pre class="screen">
 $ /usr/sbin/getsebool -a | grep ftp
 allow_ftpd_anon_write --&gt; off
@@ -20,9 +20,9 @@ httpd_enable_ftp_server --&gt; off
 tftp_anon_write --&gt; off
 
 </pre><div class="para">
-				For a list of Booleans and whether they are on or off, run the <code class="command">/usr/sbin/getsebool -a</code> command. For a list of Booleans, an explanation of what each one is, and whether they are on or off, run the <code class="command">/usr/sbin/semanage boolean -l</code> command as the Linux root user. Refer to <a class="xref" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html" title="5.6. Booleans">Sección 5.6, “Booleans”</a> for information about listing and configuring Booleans.
-			</div><div class="formalpara"><h5 class="formalpara">Port Numbers</h5>
-					Depending on policy configuration, services may only be allowed to run on certain port numbers. Attempting to change the port a service runs on without changing policy may result in the service failing to start. For example, run the <code class="command">semanage port -l | grep http</code> command as the Linux root user to list <code class="systemitem">http</code> related ports:
+				For a list of Booleans and whether they are on or off, run the <code class="command">/usr/sbin/getsebool -a</code> command. For a list of Booleans, an explanation of what each one is, and whether they are on or off, run the <code class="command">/usr/sbin/semanage boolean -l</code> command as the Linux root user. Refer to <a class="xref" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html" title="5.6. Booleanos">Sección 5.6, “Booleanos”</a> for information about listing and configuring Booleans.
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-How_are_Confined_Services_Running-Port_Numbers"><h5 class="formalpara">Números de Puertos</h5>
+					Dependiendo de la configuración de la política, los servicios pueden tener permitido correr sobre ciertos números de puerto. Intentar cambiar el puerto en el que corre un servicio sin cambiar la política puede resultar en un fallo al iniciar el servicio. Por ejemplo, ejecute el comando <code class="command">semanage port -l | grep http</code> como usuario root de Linux para listar los puertos relacionados con <code class="systemitem">http</code>:
 				</div><pre class="screen">
 # /usr/sbin/semanage port -l | grep http
 http_cache_port_t              tcp      3128, 8080, 8118
@@ -32,7 +32,7 @@ pegasus_http_port_t            tcp      5988
 pegasus_https_port_t           tcp      5989
 
 </pre><div class="para">
-				The <code class="computeroutput">http_port_t</code> port type defines the ports Apache HTTP Server can listen on, which in this case, are TCP ports 80, 443, 488, 8008, 8009, and 8443. If an administrator configures <code class="filename">httpd.conf</code> so that <code class="systemitem">httpd</code> listens on port 9876 (<code class="option">Listen 9876</code>), but policy is not updated to reflect this, the <code class="command">service httpd start</code> command fails:
+				El tipo de puerto <code class="computeroutput">http_port_t</code> define los puertos en los que el Servidor HTTP Apache puede escuchar, que en este caso son los puertos TCP 80, 443, 488, 8008, 8009, y 8443. Si un administrador configura <code class="filename">httpd.conf</code> para que <code class="systemitem">httpd</code> escuche en el puerto 9876 (<code class="option">Listen 9876</code>), pero la política no fue actualizada para reflejar esto, el comando <code class="command">service httpd start</code> falla:
 			</div><pre class="screen">
 # /sbin/service httpd start
 Starting httpd: (13)Permission denied: make_sock: could not bind to address [::]:9876
@@ -42,17 +42,17 @@ Unable to open logs
 						            [FAILED]
 
 </pre><div class="para">
-				An SELinux denial similar to the following is logged to <code class="filename">/var/log/audit/audit.log</code>:
+				Una negación de SELinux es similar a la siguiente y se guarda en <code class="filename">/var/log/audit/audit.log</code>:
 			</div><pre class="screen">
 type=AVC msg=audit(1225948455.061:294): avc:  denied  { name_bind } for  pid=4997 comm="httpd" src=9876 scontext=unconfined_u:system_r:httpd_t:s0 tcontext=system_u:object_r:port_t:s0 tclass=tcp_socket
 
 </pre><div class="para">
-				To allow <code class="systemitem">httpd</code> to listen on a port that is not listed for the <code class="computeroutput">http_port_t</code> port type, run the <code class="command">semanage port</code> command to add a port to policy configuration<sup>[<a id="id558383" href="#ftn.id558383" class="footnote">15</a>]</sup>:
+				Para permitir a <code class="systemitem">httpd</code> escuchar en un puerto que no está listado en el tipo de puerto <code class="computeroutput">http_port_t</code>, ejecute el comando <code class="command">semanage port</code> para agregar un puerto a la configuración de la política <sup>[<a id="id1181658" href="#ftn.id1181658" class="footnote">15</a>]</sup>:
 			</div><pre class="screen">
 # /usr/sbin/semanage port -a -t http_port_t -p tcp 9876
 
 </pre><div class="para">
-				The <code class="option">-a</code> option adds a new record; the <code class="option">-t</code> option defines a type; and the <code class="option">-p</code> option defines a protocol. The last argument is the port number to add.
-			</div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id558383" href="#id558383" class="para">15</a>] </sup>
-					The <code class="command">semanage port -a</code> command adds an entry to the <code class="filename">/etc/selinux/targeted/modules/active/ports.local</code> file. Note: by default, this file can only be viewed by the Linux root user.
-				</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html"><strong>Anterior</strong>7.2. Top Three Causes of Problems</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Evolving_Rules_and_Broken_Applications.html"><strong>Siguiente</strong>7.2.3. Evolving Rules and Broken Applications</a></li></ul></body></html>
+				La opción <code class="option">-a</code> agrega un nuevo registro; la opción <code class="option">-t</code> define un tipo; y la opción <code class="option">-p</code> define un protocolo. El último argumento es el número de puerto a agregar.
+			</div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id1181658" href="#id1181658" class="para">15</a>] </sup>
+					El comando <code class="command">semanage port -a</code> agrega una entrada al archivo <code class="filename">/etc/selinux/targeted/modules/active/ports.local</code>. Nota: por defecto, este archivo sólo puede ser visto por el usuario root de Linux.
+				</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html"><strong>Anterior</strong>7.2. Tres Principales Causas de Problemas</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Evolving_Rules_and_Broken_Applications.html"><strong>Siguiente</strong>7.2.3. Evolucionando las Reglas y las Aplicacione...</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html
index fb393c8..4e0dabb 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html
@@ -1,22 +1,22 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.3. Fixing Problems</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="chap-Security-Enhanced_Linux-Troubleshooting.html" title="Capítulo 7. Troubleshooting" /><link rel="prev" href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Evolving_Rules_and_Broken_Applications.html" title="7.2.3. Evolving Rules and Broken Applications" /><link rel="next" href="sect-Security-Enhanced_Linux-Fixing_Problems-Possible_Causes_of_Silent_Denials.html" title="7.3.2. Possible Causes of Silent Denials" /></head><body clas
 s="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Evolving_Rules_and_Broken_Applications.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Fixing_Problems-Possible_Causes_of_Silent_Denials.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="7.3. Fixing Problems" id="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems"><div class="titlepage"><div><div 
 keep-together.within-column="always"><h2 class="title">7.3. Fixing Problems</h2></div></div></div><div class="para">
-			The following sections help troubleshoot issues. They go over: checking Linux permissions, which are checked before SELinux rules; possible causes of SELinux denying access, but no denials being logged; manual pages for services, which contain information about labeling and Booleans; permissive domains, for allowing one process to run permissive, rather than the whole system; how to search for and view denial messages; analyzing denials; and creating custom policy modules with <code class="command">audit2allow</code>.
-		</div><div class="section" title="7.3.1. Linux Permissions" id="sect-Security-Enhanced_Linux-Fixing_Problems-Linux_Permissions"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.3.1. Linux Permissions</h3></div></div></div><div class="para">
-				When access is denied, check standard Linux permissions. As mentioned in <a class="xref" href="chap-Security-Enhanced_Linux-Introduction.html" title="Capítulo 2. Introduction">Capítulo 2, <i>Introduction</i></a>, most operating systems use a Discretionary Access Control (DAC) system to control access, allowing users to control the permissions of files that they own. SELinux policy rules are checked after DAC rules. SELinux policy rules are not used if DAC rules deny access first.
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.3. Corrección de Problemas</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Troubleshooting.html" title="Capítulo 7. Solución a Problemas" /><link rel="prev" href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Evolving_Rules_and_Broken_Applications.html" title="7.2.3. Evolucionando las Reglas y las Aplicaciones Rotas" /><link rel="next" href="sect-Security-Enhanced_Linux-Fixing_Problems-Possible_Causes_of_Silent_Denials.html" title="7.3.2. Posibles Causas de las 
 Negaciones Silenciosas" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Evolving_Rules_and_Broken_Applications.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Fixing_Problems-Possible_Causes_of_Silent_Denials.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="7.3. Corrección de Problemas" id="sect-Security-Enhanced_Linux-Troubleshootin
 g-Fixing_Problems"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">7.3. Corrección de Problemas</h2></div></div></div><div class="para">
+			Las siguientes secciones ayudan a resolver problemas. Cubren los temas: chequeo de los permisos de Linux, que se chequean antes que las reglas de SELinux; posibles causas de negaciones de acceso de SELinux, pero no negaciones que se estén guardando; páginas man de los servicios, que contienen información sobre etiquetado y Booleanos; dominios permisivos, para permitir a un proceso correr en modo permisivo, en vez de todo el sistema; cómo buscar y encontrar mensajes; análisis de negaciones; y creación de módulos de políticas personalizados con <code class="command">audit2allow</code>.
+		</div><div class="section" title="7.3.1. Permisos de Linux" id="sect-Security-Enhanced_Linux-Fixing_Problems-Linux_Permissions"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.3.1. Permisos de Linux</h3></div></div></div><div class="para">
+				When access is denied, check standard Linux permissions. As mentioned in <a class="xref" href="chap-Security-Enhanced_Linux-Introduction.html" title="Capítulo 2. Introducción">Capítulo 2, <i>Introducción</i></a>, most operating systems use a Discretionary Access Control (DAC) system to control access, allowing users to control the permissions of files that they own. SELinux policy rules are checked after DAC rules. SELinux policy rules are not used if DAC rules deny access first.
 			</div><div class="para">
-				If access is denied and no SELinux denials are logged, use the <code class="command">ls -l</code> command to view the standard Linux permissions:
+				Si el acceso es denegado y no hay negaciones SELinux guardadas, use el comando <code class="command">ls -l</code> para ver los permisos estándares de Linux:
 			</div><pre class="screen">
 $ ls -l /var/www/html/index.html
 -rw-r----- 1 root root 0 2009-05-07 11:06 index.html
 
 </pre><div class="para">
-				In this example, <code class="filename">index.html</code> is owned by the root user and group. The root user has read and write permissions (<code class="computeroutput">-rw</code>), and members of the root group have read permissions (<code class="computeroutput">-r-</code>). Everyone else has no access (<code class="computeroutput">---</code>). By default, such permissions do not allow <code class="systemitem">httpd</code> to read this file. To resolve this issue, use the <code class="command">chown</code> command to change the owner and group. This command must be run as the Linux root user:
+				En este ejemplo, <code class="filename">index.html</code> pertenece al usuario y al grupo root. El usuario root tiene permisos de lectura y escritura (<code class="computeroutput">-rw</code>), y los miembros del grupo root tienen permisos de lectura (<code class="computeroutput">-r-</code>). Cualquier otro no tiene acceso (<code class="computeroutput">---</code>). Por defecto, tales permisos no permiten a <code class="systemitem">httpd</code> leer este archivo. Para resolver esto, use el comando <code class="command">chown</code> el dueño y el grupo. Este comando se debe ejecutar como usuario root de Linux:
 			</div><pre class="screen">
 # chown apache:apache /var/www/html/index.html
 
 </pre><div class="para">
-				This assumes the default configuration, in which <code class="systemitem">httpd</code> runs as the Linux apache user. If you run <code class="systemitem">httpd</code> with a different user, replace <code class="computeroutput">apache:apache</code> with that user.
+				Esto asume la configuración predeterminada, en la que <code class="systemitem">httpd</code> corre como usuario apache de Linux. Si corre <code class="systemitem">httpd</code> con un usuario diferente, reemplace <code class="computeroutput">apache:apache</code> con ese usuario.
 			</div><div class="para">
 				Refer to the <a href="http://fedoraproject.org/wiki/Docs/Drafts/AdministrationGuide/Permissions">Fedora Documentation Project "Permissions"</a> draft for information about managing Linux permissions.
-			</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Evolving_Rules_and_Broken_Applications.html"><strong>Anterior</strong>7.2.3. Evolving Rules and Broken Applications</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Fixing_Problems-Possible_Causes_of_Silent_Denials.html"><strong>Siguiente</strong>7.3.2. Possible Causes of Silent Denials</a></li></ul></body></html>
+			</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Evolving_Rules_and_Broken_Applications.html"><strong>Anterior</strong>7.2.3. Evolucionando las Reglas y las Aplicacione...</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Fixing_Problems-Possible_Causes_of_Silent_Denials.html"><strong>Siguiente</strong>7.3.2. Posibles Causas de las Negaciones Silencio...</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html
index 6660cec..82d9fd4 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html
@@ -1,44 +1,44 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.2. Top Three Causes of Problems</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="chap-Security-Enhanced_Linux-Troubleshooting.html" title="Capítulo 7. Troubleshooting" /><link rel="prev" href="chap-Security-Enhanced_Linux-Troubleshooting.html" title="Capítulo 7. Troubleshooting" /><link rel="next" href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running.html" title="7.2.2. How are Confined Services Running?" /></head><body class="toc_embeded "><div id="tocdiv" class="t
 oc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-Troubleshooting.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="7.2. Top Three Causes of Problems" id="sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">
 7.2. Top Three Causes of Problems</h2></div></div></div><div class="para">
-			The following sections describe the top three causes of problems: labeling problems, configuring Booleans and ports for services, and evolving SELinux rules.
-		</div><div class="section" title="7.2.1. Labeling Problems" id="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Labeling_Problems"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.2.1. Labeling Problems</h3></div></div></div><div class="para">
-				On systems running SELinux, all processes and files are labeled with a label that contains security-relevant information. This information is called the SELinux context. If these labels are wrong, access may be denied. If an application is labeled incorrectly, the process it transitions to may not have the correct label, possibly causing SELinux to deny access, and the process being able to create mislabeled files.
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.2. Tres Principales Causas de Problemas</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Troubleshooting.html" title="Capítulo 7. Solución a Problemas" /><link rel="prev" href="chap-Security-Enhanced_Linux-Troubleshooting.html" title="Capítulo 7. Solución a Problemas" /><link rel="next" href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running.html" title="7.2.2. ¿Cómo se Ejecutan los Servicios Confinados?" /></head><body class="toc
 _embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-Troubleshooting.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="7.2. Tres Principales Causas de Problemas" id="sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems"><div class="titlepage"><div><div keep-togeth
 er.within-column="always"><h2 class="title">7.2. Tres Principales Causas de Problemas</h2></div></div></div><div class="para">
+			Las siguientes secciones describen las tres principales causas de problemas: problemas de etiquetados, configuración de Booleanos y puertos para servicios, y la evolución de las reglas SELinux.
+		</div><div class="section" title="7.2.1. Problemas de Etiquetados" id="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Labeling_Problems"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.2.1. Problemas de Etiquetados</h3></div></div></div><div class="para">
+				En sistemas que corren SELinux, todos los procesosy archivos se etiquetan con una etiqueta que contiene información de seguridad relevante. Esta información se llama contexto de SELinux. Si estas etiquetas están mal, el acceso puede ser negado. Si una aplicación se etiqueta incorrectamente, el proceso al que transiciona puede no tener la etiqueta correcta, causando negaciones de acceso de SELinux, y los procesos pueden crear archivo con las etiquetas incorrectas.
 			</div><div class="para">
-				A common cause of labeling problems is when a non-standard directory is used for a service. For example, instead of using <code class="filename">/var/www/html/</code> for a website, an administrator wants to use <code class="filename">/srv/myweb/</code>. On Fedora 11, the <code class="filename">/srv/</code> directory is labeled with the <code class="computeroutput">var_t</code> type. Files and directories created and <code class="filename">/srv/</code> inherit this type. Also, newly-created top-level directories (such as <code class="filename">/myserver/</code>) may be labeled with the <code class="computeroutput">default_t</code> type. SELinux prevents the Apache HTTP Server (<code class="systemitem">httpd</code>) from accessing both of these types. To allow access, SELinux must know that the files in <code class="filename">/srv/myweb/</code> are to be accessible to <code class="systemitem">httpd</code>:
+				Una causa común de problemas de etiquetados es cuando un directorio no estandar se usa para un servicio. Por ejemplo, en vez de usar <code class="filename">/var/www/html/</code> para un sitio web, un administrador prefiere usar <code class="filename">/srv/miweb/</code>. En Fedora 11, el directorio <code class="filename">/srv/</code> se etiqueta con el tipo <code class="computeroutput">var_t</code>. Los archivos y directorios creados en <code class="filename">/srv/</code> heredan este tipo. También, los directorios de alto nivel recién creados (como <code class="filename">/miservidor/</code>) puede ser etiquetado con el tipo <code class="computeroutput">default_t</code>. SELinux impide al Servidor HTTP Apache (<code class="systemitem">httpd</code>) el acceso a estos dos tipos. Para permitirle el acceso, SELinux debe saber qué archivos en <code class="filename">/srv/miweb/</code> son accesibles a <code class="systemitem">httpd</code>:
 			</div><pre class="screen">
 # /usr/sbin/semanage fcontext -a -t httpd_sys_content_t \
 "/srv/myweb(/.*)?"
 
 </pre><div class="para">
-				This <code class="command">semanage</code> command adds the context for the <code class="filename">/srv/myweb/</code> directory (and all files and directories under it) to the SELinux file-context configuration<sup>[<a id="id440313" href="#ftn.id440313" class="footnote">14</a>]</sup>. The <code class="command">semanage</code> command does not change the context. As the Linux root user, run the <code class="command">restorecon</code> command to apply the changes:
+				Este comando <code class="command">semanage</code> agrega el contexto para el directorio <code class="filename">/srv/miweb/</code> (y todos los archivos dentro de él) a la configuración de contexto de archivos de SELinux <sup>[<a id="id862115" href="#ftn.id862115" class="footnote">14</a>]</sup>. El comando <code class="command">semanage</code> no cambia el contexto. Como usuario root de Linux, ejecute el comando <code class="command">restorecon</code> para aplicar los cambios:
 			</div><pre class="screen">
 # /sbin/restorecon -R -v /srv/myweb
 
 </pre><div class="para">
-				Refer to <a class="xref" href="sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext.html" title="5.7.2. Persistent Changes: semanage fcontext">Sección 5.7.2, “Persistent Changes: semanage fcontext”</a> for further information about adding contexts to the file-context configuration.
-			</div><div class="section" title="7.2.1.1. What is the Correct Context?" id="sect-Security-Enhanced_Linux-Labeling_Problems-What_is_the_Correct_Context"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">7.2.1.1. What is the Correct Context?</h4></div></div></div><div class="para">
-					The <code class="command">matchpathcon</code> command checks the context of a file path and compares it to the default label for that path. The following example demonstrates using <code class="command">matchpathcon</code> on a directory that contains incorrectly labeled files:
+				Refer to <a class="xref" href="sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext.html" title="5.7.2. Cambios Persistentes: semanage fcontext">Sección 5.7.2, “Cambios Persistentes: semanage fcontext”</a> for further information about adding contexts to the file-context configuration.
+			</div><div class="section" title="7.2.1.1. ¿Cuál es el contexto correcto?" id="sect-Security-Enhanced_Linux-Labeling_Problems-What_is_the_Correct_Context"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">7.2.1.1. ¿Cuál es el contexto correcto?</h4></div></div></div><div class="para">
+					El comando <code class="command">matchpathcon</code> chequea el contexto de un nombre completo de archivo y lo compara con la etiqueta por defecto para esa dirección. El siguiente ejemplo muestra el uso de <code class="command">matchpathcon</code> en un directorio con archivos etiquetados incorrectamente:
 				</div><pre class="screen">
 $ /usr/sbin/matchpathcon -V /var/www/html/*
 /var/www/html/index.html has context unconfined_u:object_r:user_home_t:s0, should be system_u:object_r:httpd_sys_content_t:s0
 /var/www/html/page1.html has context unconfined_u:object_r:user_home_t:s0, should be system_u:object_r:httpd_sys_content_t:s0
 
 </pre><div class="para">
-					In this example, the <code class="filename">index.html</code> and <code class="filename">page1.html</code> files are labeled with the <code class="computeroutput">user_home_t</code> type. This type is used for files in user home directories. Using the <code class="command">mv</code> command to move files from your home directory may result in files being labeled with the <code class="computeroutput">user_home_t</code> type. This type should not exist outside of home directories. Use the <code class="command">restorecon</code> command to restore such files to their correct type:
+					En este ejemplo, los archivos <code class="filename">index.html</code> and <code class="filename">pagina1.html</code> se etiquetan con el tipo <code class="computeroutput">user_home_t</code>. Este tipo se usa para archivos en los directorios de inicio de los usuarios. Usando el comando <code class="command">mv</code> para mover archivos puede resultar en archivos etiquetados con el tipo <code class="computeroutput">user_home_t</code>. Este tipo no debería existir fuera de los directorios home. Use el comando <code class="command">restorecon</code> para restaurar tales archivos a su tipo correcto:
 				</div><pre class="screen">
 # /sbin/restorecon -v /var/www/html/index.html 
 restorecon reset /var/www/html/index.html context unconfined_u:object_r:user_home_t:s0-&gt;system_u:object_r:httpd_sys_content_t:s0
 
 </pre><div class="para">
-					To restore the context for all files under a directory, use the <code class="option">-R</code> option:
+					Para restaurar el contexto de todos los archivos bajo un directorio, use la opción <code class="option">-R</code>:
 				</div><pre class="screen">
 # /sbin/restorecon -R -v /var/www/html/
 restorecon reset /var/www/html/page1.html context unconfined_u:object_r:samba_share_t:s0-&gt;system_u:object_r:httpd_sys_content_t:s0
 restorecon reset /var/www/html/index.html context unconfined_u:object_r:samba_share_t:s0-&gt;system_u:object_r:httpd_sys_content_t:s0
 
 </pre><div class="para">
-					Refer to <a class="xref" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context.html" title="5.10.3. Checking the Default SELinux Context">Sección 5.10.3, “Checking the Default SELinux Context”</a> for a more detailed example of <code class="command">matchpathcon</code>.
-				</div></div></div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id440313" href="#id440313" class="para">14</a>] </sup>
-					Files in <code class="filename">/etc/selinux/targeted/contexts/files/</code> define contexts for files and directories. Files in this directory are read by <code class="command">restorecon</code> and <code class="command">setfiles</code> to restore files and directories to their default contexts.
-				</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-Troubleshooting.html"><strong>Anterior</strong>Capítulo 7. Troubleshooting</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running.html"><strong>Siguiente</strong>7.2.2. How are Confined Services Running?</a></li></ul></body></html>
+					Refer to <a class="xref" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context.html" title="5.10.3. Chequeando el Contexto SELinux Predeterminado">Sección 5.10.3, “Chequeando el Contexto SELinux Predeterminado”</a> for a more detailed example of <code class="command">matchpathcon</code>.
+				</div></div></div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id862115" href="#id862115" class="para">14</a>] </sup>
+					Los archivos en <code class="filename">/etc/selinux/targeted/contexts/files/</code> definen los contextos de archivos y directorios. Los archivos en este directorio son leídos por <code class="command">restorecon</code> y <code class="command">setfiles</code> para restaurar archivos y directorios a sus contextos predeterminados.
+				</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-Troubleshooting.html"><strong>Anterior</strong>Capítulo 7. Solución a Problemas</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running.html"><strong>Siguiente</strong>7.2.2. ¿Cómo se Ejecutan los Servicios Confinados?</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html
index 8ac475c..c461586 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html
@@ -1,9 +1,9 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.6. Booleans</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html" title="Capítulo 5. Working with SELinux" /><link rel="prev" href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes.html" title="5.5. SELinux Modes" /><link rel="next" href="sect-Security-Enhanced_Linux-Booleans-Configuring_Booleans.html" title="5.6.2. Configuring Booleans" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../..
 /../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Booleans-Configuring_Booleans.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.6. Booleans" id="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.6. Booleans</h2></div></div></div><div class="para">
-			Booleans allow parts of SELinux policy to be changed at runtime, without any knowledge of SELinux policy writing. This allows changes, such as allowing services access to NFS file systems, without reloading or recompiling SELinux policy.
-		</div><div class="section" title="5.6.1. Listing Booleans" id="sect-Security-Enhanced_Linux-Booleans-Listing_Booleans"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.6.1. Listing Booleans</h3></div></div></div><div class="para">
-				For a list of Booleans, an explanation of what each one is, and whether they are on or off, run the <code class="command">semanage boolean -l</code> command as the Linux root user. The following example does not list all Booleans:
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.6. Booleanos</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html" title="Capítulo 5. Trabajando con SELinux" /><link rel="prev" href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes.html" title="5.5. Modos de SELinux" /><link rel="next" href="sect-Security-Enhanced_Linux-Booleans-Configuring_Booleans.html" title="5.6.2. Configurando los Booleanos" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class
 ="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Booleans-Configuring_Booleans.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.6. Booleanos" id="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.6. Booleanos</h2></div></div></div><div class="para">
+			Los booleanos permiten cambiar partes de la política de SELinux en tiempo de ejecución, sin ningún conocimiento sobre la escritura de políticas de SELinux. Esto permite cambios, como permitir el acceso de servicios a sistemas de archivo NFS, sin recargar o recompilar la política de SELinux.
+		</div><div class="section" title="5.6.1. Listando los Booleanos" id="sect-Security-Enhanced_Linux-Booleans-Listing_Booleans"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.6.1. Listando los Booleanos</h3></div></div></div><div class="para">
+				Para una lista de los Booleanos, una explicación de lo que son y de si están activos o inactivos, ejecute el comando <code class="command">semanage boolean -l</code> como usuario root de Linux. El siguiente ejemplo no lista todos los Booleanos:
 			</div><pre class="screen"># /usr/sbin/semanage boolean -l
 SELinux boolean                          Description
 
@@ -12,28 +12,28 @@ xen_use_nfs                    -&gt; off   Allow xen to manage nfs files
 xguest_connect_network         -&gt; on    Allow xguest to configure Network Manager
 
 </pre><div class="para">
-				The <code class="computeroutput">SELinux boolean</code> column lists Boolean names. The <code class="computeroutput">Description</code> column lists whether the Booleans are on or off, and what they do.
+				La columna <code class="computeroutput">SELinux boolean</code> lista los nombres de Booleanos. La columna <code class="computeroutput">Description</code> lista si el booleano está activo (on) o inactivo (off) y lo que hacen.
 			</div><div class="para">
-				In the following example, the <code class="computeroutput">ftp_home_dir</code> Boolean is off, preventing the FTP daemon (<code class="systemitem">vsftpd</code>) from reading and writing to files in user home directories:
+				En el siguiente ejemplo, el Booleano <code class="computeroutput">ftp_home_dir</code> está apagado, impidiendo al demonio FTP (<code class="systemitem">vsftpd</code>) la lectura y escritura de archivos en los directorios de inicio de los usuarios:
 			</div><pre class="screen">ftp_home_dir                   -&gt; off   Allow ftp to read and write files in the user home directories
 
 </pre><div class="para">
-				The <code class="command">getsebool -a</code> command lists Booleans, whether they are on or off, but does not give a description of each one. The following example does not list all Booleans:
+				El comando <code class="command">getsebool -a</code> lista los Booleanos, ya sea que estén activos o inactivos, pero no da una descripción de cada uno. El siguiente ejemplo no lista todos los booleanos:
 			</div><pre class="screen">$ /usr/sbin/getsebool -a
 allow_console_login --&gt; off
 allow_cvs_read_shadow --&gt; off
 allow_daemons_dump_core --&gt; on
 
 </pre><div class="para">
-				Run the <code class="command">getsebool <em class="replaceable"><code>boolean-name</code></em></code> command to only list the status of the <em class="replaceable"><code>boolean-name</code></em> Boolean:
+				Ejecute el comando <code class="command">getsebool <em class="replaceable"><code>nombre-de-booleano</code></em></code> para listar solamente el estado del booleano <em class="replaceable"><code>nombre-de-booleano</code></em>:
 			</div><pre class="screen">$ /usr/sbin/getsebool allow_console_login
 allow_console_login --&gt; off
 
 </pre><div class="para">
-				Use a space-separated list to list multiple Booleans:
+				Una lista separada por espacio para listar los Booleanos múltiples:
 			</div><pre class="screen">$ getsebool allow_console_login allow_cvs_read_shadow allow_daemons_dump_core
 allow_console_login --&gt; off
 allow_cvs_read_shadow --&gt; off
 allow_daemons_dump_core --&gt; on
 
-</pre></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes.html"><strong>Anterior</strong>5.5. SELinux Modes</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Booleans-Configuring_Booleans.html"><strong>Siguiente</strong>5.6.2. Configuring Booleans</a></li></ul></body></html>
+</pre></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes.html"><strong>Anterior</strong>5.5. Modos de SELinux</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Booleans-Configuring_Booleans.html"><strong>Siguiente</strong>5.6.2. Configurando los Booleanos</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html
index 87f6add..5d63c66 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html
@@ -1,14 +1,14 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.4. Enabling and Disabling SELinux</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html" title="Capítulo 5. Working with SELinux" /><link rel="prev" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Main_Configuration_File.html" title="5.3. Main Configuration File" /><link rel="next" href="sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux.html" title="5.4.2. Disabling SELinux" /></head><body class="toc_embeded "><div id="tocdiv
 " class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Main_Configuration_File.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.4. Enabling and Disabling SELinux" id="sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux"><div class="titlepage"><div><div keep-together.within-
 column="always"><h2 class="title">5.4. Enabling and Disabling SELinux</h2></div></div></div><div class="para">
-			Use the <code class="command">/usr/sbin/getenforce</code> or <code class="command">/usr/sbin/sestatus</code> commands to check the status of SELinux. The <code class="command">getenforce</code> command returns <code class="computeroutput">Enforcing</code>, <code class="computeroutput">Permissive</code>, or <code class="computeroutput">Disabled</code>. The <code class="command">getenforce</code> command returns <code class="computeroutput">Enforcing</code> when SELinux is enabled (SELinux policy rules are enforced):
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.4. Habilitando y Deshabilitando SELinux</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html" title="Capítulo 5. Trabajando con SELinux" /><link rel="prev" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Main_Configuration_File.html" title="5.3. Archivo de Configuración Principal" /><link rel="next" href="sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux.html" title="5.4.2. Deshabilitando SELinux" /></head><body class=
 "toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Main_Configuration_File.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.4. Habilitando y Deshabilitando SELinux" id="sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux"><div class="titlep
 age"><div><div keep-together.within-column="always"><h2 class="title">5.4. Habilitando y Deshabilitando SELinux</h2></div></div></div><div class="para">
+			Use los comandos <code class="command">/usr/sbin/getenforce</code> o <code class="command">/usr/sbin/sestatus</code> para chequear el estado de SELinux. El comando <code class="command">getenforce</code> devuelve <code class="computeroutput">Obediente</code>, <code class="computeroutput">Permisivo</code>, o <code class="computeroutput">Deshabilitado</code>. El comando <code class="command">getenforce</code> devuelve <code class="computeroutput">Obediente</code> cuando SELinux está habilitado (las reglas de la política de SELinux son aplicadas):
 		</div><pre class="screen">$ /usr/sbin/getenforce
 Enforcing
 
 </pre><div class="para">
-			The <code class="command">getenforce</code> command returns <code class="computeroutput">Permissive</code> when SELinux is enabled, but SELinux policy rules are not enforced, and only DAC rules are used. The <code class="command">getenforce</code> command returns <code class="computeroutput">Disabled</code> if SELinux is disabled.
+			El comando <code class="command">getenforce</code> devuelve <code class="computeroutput">Permissive</code> cuando SELinux está activado, pero las reglas de políticas de SELinux no están en obligatorio, y sólo se usan las reglas DAC. El comando <code class="command">getenforce</code> devuelve <code class="computeroutput">Disabled</code> si SELinux está deshabilitado.
 		</div><div class="para">
-			The <code class="command">sestatus</code> command returns the SELinux status and the SELinux policy being used:
+			El comando <code class="command">sestatus</code> devuelve el estado de SELinux y la política de SELinux que se está usando:
 		</div><pre class="screen">$ /usr/sbin/sestatus
 SELinux status:                 enabled
 SELinuxfs mount:                /selinux
@@ -19,8 +19,8 @@ Policy from config file:        targeted
 
 </pre><div class="para">
 			<code class="computeroutput">SELinux status: enabled</code> is returned when SELinux is enabled. <code class="computeroutput">Current mode: enforcing</code> is returned when SELinux is running in enforcing mode. <code class="computeroutput">Policy from config file: targeted</code> is returned when the SELinux targeted policy is used.
-		</div><div class="section" title="5.4.1. Enabling SELinux" id="sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Enabling_SELinux"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.4.1. Enabling SELinux</h3></div></div></div><div class="para">
-				On systems with SELinux disabled, the <code class="computeroutput">SELINUX=disabled</code> option is configured in <code class="filename">/etc/selinux/config</code>:
+		</div><div class="section" title="5.4.1. Habilitando SELinux" id="sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Enabling_SELinux"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.4.1. Habilitando SELinux</h3></div></div></div><div class="para">
+				En sistemas con SELinux deshabilitado, la opción <code class="computeroutput">SELINUX=disabled</code> se configura en <code class="filename">/etc/selinux/config</code>:
 			</div><pre class="screen"># This file controls the state of SELinux on the system.
 # SELINUX= can take one of these three values:
 #       enforcing - SELinux security policy is enforced.
@@ -33,23 +33,23 @@ SELINUX=disabled
 SELINUXTYPE=targeted
 
 </pre><div class="para">
-				Also, the <code class="command">getenforce</code> command returns <code class="computeroutput">Disabled</code>:
+				También, el comando <code class="command">getenforce</code> devuelve <code class="computeroutput">Disabled</code>:
 			</div><pre class="screen">$ /usr/sbin/getenforce
 Disabled
 
 </pre><div class="para">
-				To enable SELinux:
+				Para habilitar SELinux:
 			</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
-						Use the <code class="command">rpm -qa | grep selinux</code>, <code class="command">rpm -q policycoreutils</code>, and <code class="command">rpm -qa | grep setroubleshoot</code> commands to confirm that the SELinux packages are installed. This guide assumes the following packages are installed: <span class="package">selinux-policy-targeted</span>, <span class="package">selinux-policy</span>, <span class="package">libselinux</span>, <span class="package">libselinux-python</span>, <span class="package">libselinux-utils</span>, <span class="package">policycoreutils</span>, <span class="package">setroubleshoot</span>, <span class="package">setroubleshoot-server</span>, <span class="package">setroubleshoot-plugins</span>. If these packages are not installed, as the Linux root user, install them via the <code class="command">yum install <em class="replaceable"><code>package-name</code></em></code> command. The following packages are optional: <span class="package">policycoreu
 tils-gui</span>, <span class="package">setroubleshoot</span>, <span class="package">selinux-policy-devel</span>, and <span class="package">mcstrans</span>.
+						Use los comandos <code class="command">rpm -qa | grep selinux</code>, <code class="command">rpm -q policycoreutils</code> y <code class="command">rpm -qa | grep setroubleshoot</code> para confirmar que los paquetes de SELinux están instalados. esta guía asume que los siguientes paquetes están instalados: <span class="package">selinux-policy-targeted</span>, <span class="package">selinux-policy</span>, <span class="package">libselinux</span>, <span class="package">libselinux-python</span>, <span class="package">libselinux-utils</span>, <span class="package">policycoreutils</span>, <span class="package">setroubleshoot</span>, <span class="package">setroubleshoot-server</span>, <span class="package">setroubleshoot-plugins</span>. Si estos paquetes no están instalados, como usuario root de Linux, debe instalarlos con el comando <code class="command">yum install <em class="replaceable"><code>nombre-de-paquete</code></em></code>. Los siguientes paquetes son opcionales: <
 span class="package">policycoreutils-gui</span>, <span class="package">setroubleshoot</span>, <span class="package">selinux-policy-devel</span> y <span class="package">mcstrans</span>.
 					</div><div class="para">
-						After installing the <span class="package">setroubleshoot-server</span> package, use the <code class="command">/sbin/chkconfig --list setroubleshoot</code> command to confirm that <code class="systemitem">setroubleshootd</code> starts when the system is running in runlevel<sup>[<a id="id459426" href="#ftn.id459426" class="footnote">10</a>]</sup> 3, 4, and 5:
+						After installing the <span class="package">setroubleshoot-server</span> package, use the <code class="command">/sbin/chkconfig --list setroubleshoot</code> command to confirm that <code class="systemitem">setroubleshootd</code> starts when the system is running in runlevel<sup>[<a id="id1193464" href="#ftn.id1193464" class="footnote">10</a>]</sup> 3, 4, and 5:
 					</div><pre class="screen">$ /sbin/chkconfig --list setroubleshoot
 setroubleshoot  0:off   1:off   2:off   3:on    4:on    5:on    6:off
 
 </pre><div class="para">
-						If the output differs, as the Linux root user, run the <code class="command">/sbin/chkconfig --levels 345 setroubleshoot on</code> command. This makes <code class="systemitem">setroubleshootd</code> automatically start when the system is in runlevel 3, 4, and 5.
+						Si la salida difiere, como usuario root de Linux ejecute el comando <code class="command">/sbin/chkconfig --levels 345 setroubleshoot on</code>. Esto hace que <code class="systemitem">setroubleshootd</code> se inicie automáticamente cuando el sistema esté en los niveles de ejecución 3, 4 y 5.
 					</div></li><li class="listitem"><div class="para">
-						Before SELinux is enabled, each file on the file system must be labeled with an SELinux context. Before this happens, confined domains may be denied access, preventing your system from booting correctly. To prevent this, configure <code class="computeroutput">SELINUX=permissive</code> in <code class="filename">/etc/selinux/config</code>:
+						Antes de activar SELinux, cada archivo en el sistema de archivo debe ser etiquetado con un contexto de SELinux. Antes que esto ocurra, los dominios confinados pueden tener el acceso denegado, impidiendo de que su sistema se inicie correctamente. Para prevenir esto, configure <code class="computeroutput">SELINUX=permissive</code> en <code class="filename">/etc/selinux/config</code>:
 					</div><pre class="screen"># This file controls the state of SELinux on the system.
 # SELINUX= can take one of these three values:
 #       enforcing - SELinux security policy is enforced.
@@ -62,18 +62,18 @@ SELINUX=permissive
 SELINUXTYPE=targeted
 
 </pre></li><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">reboot</code> command to restart the system. During the next boot, file systems are labeled. The label process labels all files with an SELinux context:
+						Como usuario root de Linux, corra el comando <code class="command">reboot</code> para reiniciar el sistema. Durante el siguiente arranque, los sistemas de archivo son etiquetados. El proceso etiqueta todos los archivos con un contexto de SELinux:
 					</div><pre class="screen">*** Warning -- SELinux targeted policy relabel is required.
 *** Relabeling could take a very long time, depending on file
 *** system size and speed of hard drives.
 ****
 
 </pre><div class="para">
-						Each <code class="computeroutput">*</code> character on the bottom line represents 1000 files that have been labeled. In the above example, four <code class="computeroutput">*</code> characters represent 4000 files have been labeled. The time it takes to label all files depends upon the number of files on the system, and the speed of the hard disk drives. On modern systems, this process can take as little as 10 minutes.
+						Cada carácter <code class="computeroutput">*</code> en la línea de abajo representa 1000 archivos que han sido etiquetados. En el ejemplo de arriba, cuatro caracteres <code class="computeroutput">*</code> representan 4000 archivos etiquetados. El tiempo que toma reetiquetar todos los archivos depende del número de archivos del sistema, y la velocidad de los discos rígidos. En sistemas modernos, este proceso puede tomar 10 minutos.
 					</div></li><li class="listitem"><div class="para">
-						In permissive mode, SELinux policy is not enforced, but denials are still logged for actions that would have been denied if running in enforcing mode. Before changing to enforcing mode, as the Linux root user, run the <code class="command">grep "SELinux is preventing" /var/log/messages</code> command as the Linux root user to confirm that SELinux did not deny actions during the last boot. If SELinux did not deny actions during the last boot, this command does not return any output. Refer to <a class="xref" href="chap-Security-Enhanced_Linux-Troubleshooting.html" title="Capítulo 7. Troubleshooting">Capítulo 7, <i>Troubleshooting</i></a> for troubleshooting information if SELinux denied access during boot.
+						In permissive mode, SELinux policy is not enforced, but denials are still logged for actions that would have been denied if running in enforcing mode. Before changing to enforcing mode, as the Linux root user, run the <code class="command">grep "SELinux is preventing" /var/log/messages</code> command as the Linux root user to confirm that SELinux did not deny actions during the last boot. If SELinux did not deny actions during the last boot, this command does not return any output. Refer to <a class="xref" href="chap-Security-Enhanced_Linux-Troubleshooting.html" title="Capítulo 7. Solución a Problemas">Capítulo 7, <i>Solución a Problemas</i></a> for troubleshooting information if SELinux denied access during boot.
 					</div></li><li class="listitem"><div class="para">
-						If there were no denial messages in <code class="filename">/var/log/messages</code>, configure <code class="computeroutput">SELINUX=enforcing</code> in <code class="filename">/etc/selinux/config</code>:
+						Si no hay mensajes de negación en <code class="filename">/var/log/messages</code>, configure <code class="computeroutput">SELINUX=enforcing</code> en <code class="filename">/etc/selinux/config</code>:
 					</div><pre class="screen"># This file controls the state of SELinux on the system.
 # SELINUX= can take one of these three values:
 #       enforcing - SELinux security policy is enforced.
@@ -86,12 +86,12 @@ SELINUX=enforcing
 SELINUXTYPE=targeted
 
 </pre></li><li class="listitem"><div class="para">
-						Reboot your system. After reboot, confirm that the <code class="command">getenforce</code> command returns <code class="computeroutput">Enforcing</code>:
+						Reinicie su sistema. Después de reiniciar, confirme que <code class="command">getenforce</code> devuelve <code class="computeroutput">Enforcing</code>:
 					</div><pre class="screen">$ /usr/sbin/getenforce
 Enforcing
 
 </pre></li><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">/usr/sbin/semanage login -l</code> command to view the mapping between SELinux and Linux users. The output should be as follows:
+						Como usuario root de Linux, corra el comando <code class="command">/usr/sbin/semanage login -l</code> para ver el mapeo entre usuarios de SELinux y de Linux. La salida debe ser como la siguiente:
 					</div><pre class="screen">Login Name                SELinux User              MLS/MCS Range
 
 __default__               unconfined_u              s0-s0:c0.c1023
@@ -99,7 +99,7 @@ root                      unconfined_u              s0-s0:c0.c1023
 system_u                  system_u                  s0-s0:c0.c1023
 
 </pre></li></ol></div><div class="para">
-				If this is not the case, run the following commands as the Linux root user to fix the user mappings. It is safe to ignore the <code class="computeroutput">SELinux-user<em class="replaceable"><code> username</code></em> is already defined</code> warnings if they occur, where <em class="replaceable"><code>username</code></em> can be <code class="computeroutput">unconfined_u</code>, <code class="computeroutput">guest_u</code>, or <code class="computeroutput">xguest_u</code>:
+				Si éste no es el caso, ejecute los siguientes comandos como usuario root de Linux para corregir los mapeos de usuario. Es seguro ignorar los mensajes <code class="computeroutput">El usuario SELinux <em class="replaceable"><code>nombre-de-usuario</code></em> ya está definido</code> si es que aparecen, donde <em class="replaceable"><code>nombre-de-usuario</code></em> puede ser <code class="computeroutput">unconfined_u</code>, <code class="computeroutput">guest_u</code>, o <code class="computeroutput">xguest_u</code>:
 			</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
 						
 <pre class="screen">/usr/sbin/semanage user -a -S targeted -P user -R "unconfined_r system_r" -r s0-s0:c0.c1023 unconfined_u
@@ -131,7 +131,7 @@ system_u                  system_u                  s0-s0:c0.c1023
 </pre>
 
 					</div></li></ol></div><div class="important"><h2>Importante</h2><div class="para">
-					When systems run with SELinux in permissive or disabled mode, users have permission to label files incorrectly. Also, files created while SELinux is disabled are not labeled. This causes problems when changing to enforcing mode. To prevent incorrectly labeled and unlabeled files from causing problems, file systems are automatically relabeled when changing from disabled mode to permissive or enforcing mode.
-				</div></div></div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id459426" href="#id459426" class="para">10</a>] </sup>
+					Cuando los sistemas corren con SELinux en modo permisivo o deshabilitado, los usuarios tiene permiso para etiquetar los archivos incorrectamente. También, los archivos creados con SELinux deshabilitado no son etiquetados. Esto causa problemas cuando se cambia a modo obediente. Para prevenir el etiquetado incorrecto o la falta de etiquetado, los sistemas de archivos son automáticamente reetiquetados cuando se cambie desde el modo deshabilitado al modo permisivo u obediente.
+				</div></div></div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id1193464" href="#id1193464" class="para">10</a>] </sup>
 							Refer to <a href="http://en.wikipedia.org/wiki/Runlevel">http://en.wikipedia.org/wiki/Runlevel</a> for information about runlevels.
-						</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Main_Configuration_File.html"><strong>Anterior</strong>5.3. Main Configuration File</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux.html"><strong>Siguiente</strong>5.4.2. Disabling SELinux</a></li></ul></body></html>
+						</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Main_Configuration_File.html"><strong>Anterior</strong>5.3. Archivo de Configuración Principal</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux.html"><strong>Siguiente</strong>5.4.2. Deshabilitando SELinux</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-Main_Configuration_File.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-Main_Configuration_File.html
index 8905c5b..887c72e 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-Main_Configuration_File.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-Main_Configuration_File.html
@@ -1,7 +1,7 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.3. Main Configuration File</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html" title="Capítulo 5. Working with SELinux" /><link rel="prev" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used.html" title="5.2. Which Log File is Used" /><link rel="next" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html" title="5.4. Enabling and Disabling SELinux" /></head><body class="toc_embeded "><div id="t
 ocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.3. Main Configuration File" id="sect-Security-Enhanced_Linux-Working_with_SELinux-Main_Configuration_File"><div class="titlepage"><div><div keep-together.within-column=
 "always"><h2 class="title">5.3. Main Configuration File</h2></div></div></div><div class="para">
-			The <code class="filename">/etc/selinux/config</code> file is the main SELinux configuration file. It controls the SELinux mode and the SELinux policy to use:
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.3. Archivo de Configuración Principal</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html" title="Capítulo 5. Trabajando con SELinux" /><link rel="prev" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used.html" title="5.2. Qué Archivo Log se usa" /><link rel="next" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html" title="5.4. Habilitando y Deshabilitando SELinux" /></head><body class
 ="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.3. Archivo de Configuración Principal" id="sect-Security-Enhanced_Linux-Working_with_SELinux-Main_Configuration_File"><div class="titlepage">
 <div><div keep-together.within-column="always"><h2 class="title">5.3. Archivo de Configuración Principal</h2></div></div></div><div class="para">
+			El archivo <code class="filename">/etc/selinux/config</code> es el archivo de configuración principal de SELinux. Controla el modo de SELinux y la política de SELinux a usar:
 		</div><pre class="screen"># This file controls the state of SELinux on the system.
 # SELINUX= can take one of these three values:
 #       enforcing - SELinux security policy is enforced.
@@ -14,9 +14,9 @@ SELINUX=enforcing
 SELINUXTYPE=targeted
 
 </pre><div class="variablelist"><dl><dt><span class="term"><code class="computeroutput">SELINUX=enforcing</code></span></dt><dd><div class="para">
-						The <code class="option">SELINUX</code> option sets the mode SELinux runs in. SELinux has three modes: enforcing, permissive, and disabled. When using enforcing mode, SELinux policy is enforced, and SELinux denies access based on SELinux policy rules. Denial messages are logged. When using permissive mode, SELinux policy is not enforced. SELinux does not deny access, but denials are logged for actions that would have been denied if running SELinux in enforcing mode. When using disabled mode, SELinux is disabled (the SELinux module is not registered with the Linux kernel), and only DAC rules are used.
+						La opción <code class="option">SELINUX</code> pone el modo en el que corre SELinux. SELinux tiene tres modos: obediente, permisivo y deshabilitado. Cuando se usa modo obediente, la política de SELinux es aplicada y SELinux niega el acceso basándose en las reglas de políticas de SELinux. Los mensajes de negación se guardan. Cuando se usa modo permisivo, la política de SELinux no es obediente. Los mensajes son guardados. SELinux no niega el acceso, pero se guardan las negaciones de acciones que hubieran sido negadas si SELinux estaba en modo obediente. Cuando se usa el modo deshabilitado, SELinux está deshabilitado (el módulo de SELinux no se registra con el kernel de Linux), y sólo se usan las reglas DAC.
 					</div></dd><dt><span class="term"><code class="computeroutput">SELINUXTYPE=targeted</code></span></dt><dd><div class="para">
-						The <code class="option">SELINUXTYPE</code> option sets the SELinux policy to use. Targeted policy is the default policy. Only change this option if you want to use the MLS policy. To use the MLS policy, install the <span class="package">selinux-policy-mls</span> package; configure <code class="option">SELINUXTYPE=mls</code> in <code class="filename">/etc/selinux/config</code>; and reboot your system.
+						La opción <code class="option">SELINUXTYPE</code> pone la política SELinux a usar. La política Destinada es la predeterminada. Sólo cambie esta opción si quiere usar la política MLS. Para usar la política MLS, instale el paquete <span class="package">selinux-policy-mls</span>; configure <code class="option">SELINUXTYPE=mls</code> en <code class="filename">/etc/selinux/config</code>; y reinicie su sistema.
 					</div></dd></dl></div><div class="important"><h2>Importante</h2><div class="para">
-				When systems run with SELinux in permissive or disabled mode, users have permission to label files incorrectly. Also, files created while SELinux is disabled are not labeled. This causes problems when changing to enforcing mode. To prevent incorrectly labeled and unlabeled files from causing problems, file systems are automatically relabeled when changing from disabled mode to permissive or enforcing mode.
-			</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used.html"><strong>Anterior</strong>5.2. Which Log File is Used</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html"><strong>Siguiente</strong>5.4. Enabling and Disabling SELinux</a></li></ul></body></html>
+				Cuando los sistemas corren con SELinux en modo permisivo o deshabilitado, los usuarios tiene permiso para etiquetar los archivos incorrectamente. También, los archivos creados con SELinux deshabilitado no son etiquetados. Esto causa problemas cuando se cambia a modo obediente. Para prevenir el etiquetado incorrecto o la falta de etiquetado, los sistemas de archivos son automáticamente reetiquetados cuando se cambie desde el modo deshabilitado al modo permisivo u obediente.
+			</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used.html"><strong>Anterior</strong>5.2. Qué Archivo Log se usa</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html"><strong>Siguiente</strong>5.4. Habilitando y Deshabilitando SELinux</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html
index acf174e..1319c80 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html
@@ -1,16 +1,16 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.10. Maintaining SELinux Labels</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html" title="Capítulo 5. Working with SELinux" /><link rel="prev" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Making_Context_Mounts_Persistent.html" title="5.9.5. Making Context Mounts Persistent" /><link rel="next" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Moving_Files_and_Directories.html" title="5.10.2. Moving Files and Directories" /></head><bod
 y class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Making_Context_Mounts_Persistent.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Moving_Files_and_Directories.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.10. Maintaining SELinux Labels" id="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_"><div
  class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.10. Maintaining SELinux Labels </h2></div></div></div><div class="para">
-			These sections describe what happens to SELinux contexts when copying, moving, and archiving files and directories. Also, it explains how to preserve contexts when copying and archiving.
-		</div><div class="section" title="5.10.1. Copying Files and Directories" id="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Copying_Files_and_Directories"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.10.1. Copying Files and Directories</h3></div></div></div><div class="para">
-				When a file or directory is copied, a new file or directory is created if it does not exist. That new file or directory's context is based on default-labeling rules, not the original file or directory's context (unless options were used to preserve the original context). For example, files created in user home directories are labeled with the <code class="computeroutput">user_home_t</code> type:
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.10. Mantención de las Etiquetas de SELinux</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html" title="Capítulo 5. Trabajando con SELinux" /><link rel="prev" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Making_Context_Mounts_Persistent.html" title="5.9.5. Haciendo Persistente los Contextos de Montajes" /><link rel="next" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Moving_Files_and_Directories.html" title="5.10.2. Movimient
 o de Archivos y Directorios" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Making_Context_Mounts_Persistent.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Moving_Files_and_Directories.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.10. Mantención de las Etiquetas de SELinux" id="sect-Security-Enhanced_Linux
 -Working_with_SELinux-Maintaining_SELinux_Labels_"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.10. Mantención de las Etiquetas de SELinux</h2></div></div></div><div class="para">
+			Estas secciones describen qué les pasa a los contextos SELinux cuando se copia, mueve y compacta archivos y directorios. También explica cómo preservar los contextos cuando se copia o se compacta.
+		</div><div class="section" title="5.10.1. Copia de Directorios y Archivos" id="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Copying_Files_and_Directories"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.10.1. Copia de Directorios y Archivos</h3></div></div></div><div class="para">
+				Cuando se copia un archivo o directorio, se crea uno si no existía. El contexto de ese archivo o directorio nuevo está basado en las reglas de etiquetados predeterminada, y no el contexto original del archivo o directorio (a menos que se usen opciones para preservar el contexto original). Por ejemplo, los archivos creados en los directorios home de los usuarios se etiquetan con el tipo <code class="computeroutput">user_home_t</code>:
 			</div><pre class="screen">
 $ touch file1
 $ ls -Z file1 
 -rw-rw-r--  user1 group1 unconfined_u:object_r:user_home_t:s0 file1
 
 </pre><div class="para">
-				If such a file is copied to another directory, such as <code class="filename">/etc/</code>, the new file is created in accordance to default-labeling rules for the <code class="filename">/etc/</code> directory. Copying a file (without additional options) may not preserve the original context:
+				Si un archivo se copia a otro directorio, tal como <code class="filename">/etc/</code>, el archivo nuevo se crea de acuerdo a las reglas de etiquetado predeterminado del directorio <code class="filename">/etc/</code>. El copiado de un archivo (sin opciones adicionales) puede no preservar el contexto original:
 			</div><pre class="screen">
 $ ls -Z file1 
 -rw-rw-r--  user1 group1 unconfined_u:object_r:user_home_t:s0 file1
@@ -19,11 +19,11 @@ $ ls -Z /etc/file1
 -rw-r--r--  root root unconfined_u:object_r:etc_t:s0   /etc/file1
 
 </pre><div class="para">
-				When <code class="filename">file1</code> is copied to <code class="filename">/etc/</code>, if <code class="filename">/etc/file1</code> does not exist, <code class="filename">/etc/file1</code> is created as a new file. As shown in the example above, <code class="filename">/etc/file1</code> is labeled with the <code class="computeroutput">etc_t</code> type, in accordance to default-labeling rules.
+				Cuando el <code class="filename">archivo1</code> se copia a <code class="filename">/etc/</code>, si <code class="filename">/etc/archivo1</code> no existe, <code class="filename">/etc/archivo1</code> se crea como un archivo nuevo. Como se muestra en el ejemplo de arriba, <code class="filename">/etc/archivo1</code> se etiqueta con el tipo <code class="computeroutput">etc_t</code>, de acuerdo con las reglas de etiquetado predeterminadas.
 			</div><div class="para">
-				When a file is copied over an existing file, the existing file's context is preserved, unless the user specified <code class="command">cp</code> options to preserve the context of the original file, such as <code class="option">--preserve=context</code>. SELinux policy may prevent contexts from being preserved during copies.
-			</div><div class="formalpara"><h5 class="formalpara">Copying Without Preserving SELinux Contexts</h5>
-					When copying a file with the <code class="command">cp</code> command, if no options are given, the type is inherited from the targeted, parent directory:
+				Cuando un archivo se copia sobre otro existente, el contexto del archivo existente se preserva, a menos que el usuario especifique opciones de <code class="command">cp</code> para preservar el contexto del archivo original, tal como <code class="option">--preserve=context</code>. La política de SELinux puede prevenir que se preserver los contextos al copiar.
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Copying_Files_and_Directories-Copying_Without_Preserving_SELinux_Contexts"><h5 class="formalpara">Copia sin Preservar los Contextos de SELinux</h5>
+					Cuando se copia un archivo con el comando <code class="command">cp</code>, si no se dan opciones, el tipo se hereda desde el directorio padre destino:
 				</div><pre class="screen">
 $ touch file1
 $ ls -Z file1
@@ -35,9 +35,9 @@ $ ls -Z /var/www/html/file1
 -rw-r--r--  root root unconfined_u:object_r:httpd_sys_content_t:s0 /var/www/html/file1
 
 </pre><div class="para">
-				In this example, <code class="filename">file1</code> is created in a user's home directory, and is labeled with the <code class="computeroutput">user_home_t</code> type. The <code class="filename">/var/www/html/</code> directory is labeled with the <code class="computeroutput">httpd_sys_content_t</code> type, as shown with the <code class="command">ls -dZ /var/www/html/</code> command. When <code class="filename">file1</code> is copied to <code class="filename">/var/www/html/</code>, it inherits the <code class="computeroutput">httpd_sys_content_t</code> type, as shown with the <code class="command">ls -Z /var/www/html/file1</code> command.
-			</div><div class="formalpara"><h5 class="formalpara">Preserving SELinux Contexts When Copying</h5>
-					Use the <code class="command">cp --preserve=context</code> command to preserve contexts when copying:
+				En este ejemplo, <code class="filename">archivo1</code> se crea en el directorio de inicio del usuario, y se etiqueta con el tipo <code class="computeroutput">user_home_t</code>. El directorio <code class="filename">/var/www/html/</code> está etiquetado con el tipo <code class="computeroutput">httpd_sys_content_t</code>, como se muestra con el comando <code class="command">ls -dZ /var/www/html/</code>. Cuando el <code class="filename">archivo1</code> se copia a <code class="filename">/var/www/html/</code>, hereda el tipo <code class="computeroutput">httpd_sys_content_t</code>, como se muestra con el comando<code class="command">ls -Z /var/www/html/archivo1</code>.
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Copying_Files_and_Directories-Preserving_SELinux_Contexts_When_Copying"><h5 class="formalpara">Preservación de los Contextos de SELinux cuando se copia</h5>
+					Use el comando <code class="command">cp --preserve=context</code> para preservar los contextos cuando se copia:
 				</div><pre class="screen">
 $ touch file1
 $ ls -Z file1
@@ -49,9 +49,9 @@ $ ls -Z /var/www/html/file1
 -rw-r--r--  root root unconfined_u:object_r:user_home_t:s0 /var/www/html/file1
 
 </pre><div class="para">
-				In this example, <code class="filename">file1</code> is created in a user's home directory, and is labeled with the <code class="computeroutput">user_home_t</code> type. The <code class="filename">/var/www/html/</code> directory is labeled with the <code class="computeroutput">httpd_sys_content_t</code> type, as shown with the <code class="command">ls -dZ /var/www/html/</code> command. Using the <code class="option">--preserve=context</code> option preserves SELinux contexts during copy operations. As shown with the <code class="command">ls -Z /var/www/html/file1</code> command, the <code class="filename">file1</code> <code class="computeroutput">user_home_t</code> type was preserved when the file was copied to <code class="filename">/var/www/html/</code>.
-			</div><div class="formalpara"><h5 class="formalpara">Copying and Changing the Context</h5>
-					Use the <code class="command">cp -Z</code> command to change the destination copy's context. The following example was performed in the user's home directory:
+				En este ejemplo, el <code class="filename">archivo1</code> se crea en el directorio de inicio del usuario, y se etiqueta con el tipo <code class="computeroutput">user_home_t</code>. El directorio <code class="filename">/var/www/html/</code> está etiquetado con el tipo <code class="computeroutput">httpd_sys_content_t</code>, como se muestra con el comando <code class="command">ls -dZ /var/www/html/</code>. Usando la opción <code class="option">--preserve=context</code> se mantienen los contextos de SELinux durante operaciones de copia. Como se muestra con el comando <code class="command">ls -Z /var/www/html/archivo1</code>, el tipo <code class="computeroutput">user_home_t</code> del <code class="filename">archivo1</code> fue preservado cuando el archivo se copió a <code class="filename">/var/www/html/</code>.
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Copying_Files_and_Directories-Copying_and_Changing_the_Context"><h5 class="formalpara">Copiado y Cambio del Contexto</h5>
+					Use el comando <code class="command">cp -Z</code> para cambiar el contexto destino de copia. El siguiente ejemplo se realizó en el directorio de inicio del usuario:
 				</div><pre class="screen">
 $ touch file1
 $ cp -Z system_u:object_r:samba_share_t:s0 file1 file2
@@ -61,9 +61,9 @@ $ ls -Z file1 file2
 $ rm file1 file2
 
 </pre><div class="para">
-				In this example, the context is defined with the <code class="option">-Z</code> option. Without the <code class="option">-Z</code> option, <code class="filename">file2</code> would be labeled with the <code class="computeroutput">unconfined_u:object_r:user_home_t</code> context.
-			</div><div class="formalpara"><h5 class="formalpara">Copying a File Over an Existing File</h5>
-					When a file is copied over an existing file, the existing file's context is preserved (unless an option is used to preserve contexts). For example:
+				En este ejemplo, el contexto se define en la opción <code class="option">-Z</code>. Sin la opción <code class="option">-Z</code>, <code class="filename">archivo2</code> se etiquetaría con el contexto <code class="computeroutput">unconfined_u:object_r:user_home_t</code>.
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Copying_Files_and_Directories-Copying_a_File_Over_an_Existing_File"><h5 class="formalpara">Copia de un Archivos sobre un otro existente</h5>
+					Cuando un archivo se copia sobre otro existente, el contexto del archivo existente se preserva (a menos que se use una opción para preservar los contextos). Por ejemplo:
 				</div><pre class="screen">
 # touch /etc/file1
 # ls -Z /etc/file1
@@ -76,7 +76,7 @@ $ rm file1 file2
 -rw-r--r--  root root unconfined_u:object_r:etc_t:s0   /etc/file1
 
 </pre><div class="para">
-				In this example, two files are created: <code class="filename">/etc/file1</code>, labeled with the <code class="computeroutput">etc_t</code> type, and <code class="filename">/tmp/file2</code>, labeled with the <code class="computeroutput">user_tmp_t</code> type. The <code class="command">cp /tmp/file2 /etc/file1</code> command overwrites <code class="filename">file1</code> with <code class="filename">file2</code>. After copying, the <code class="command">ls -Z /etc/file1</code> command shows <code class="filename">file1</code> labeled with the <code class="computeroutput">etc_t</code> type, not the <code class="computeroutput">user_tmp_t</code> type from <code class="filename">/tmp/file2</code> that replaced <code class="filename">/etc/file1</code>.
+				En este ejemplo, se crean dos archivos: <code class="filename">/etc/archivo1</code>, etiquetado con el tipo <code class="computeroutput">etc_t</code>, y <code class="filename">/tmp/archivo2</code>, etiquetado con el tipo <code class="computeroutput">user_tmp_t</code>. Ell comando <code class="command">cp /tmp/archivo2 /etc/archivo1</code> sobreescribe <code class="filename">archivo1</code> con <code class="filename">archivo2</code>. Después de copiar, el comando <code class="command">ls -Z /etc/archivo1</code> muestra a <code class="filename">archivo1</code> etiquetado con el tipo <code class="computeroutput">etc_t</code>, en vez del <code class="computeroutput">user_tmp_t</code> de <code class="filename">/tmp/archivo2</code> que reemplazó a <code class="filename">/etc/archivo1</code>.
 			</div><div class="important"><h2>Importante</h2><div class="para">
-					Copy files and directories, rather than moving them. This helps ensure they are labeled with the correct SELinux contexts. Incorrect SELinux contexts can prevent processes from accessing such files and directories.
-				</div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Making_Context_Mounts_Persistent.html"><strong>Anterior</strong>5.9.5. Making Context Mounts Persistent</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Moving_Files_and_Directories.html"><strong>Siguiente</strong>5.10.2. Moving Files and Directories</a></li></ul></body></html>
+					Copie archivos y directorios, en vez de moverlos. Esto ayuda a asegurar que se etiquetan con los contextos de SELinux correctos. Los contextos SELinux incorrectos pueden hacer que los procesos no puedan acceder a esos archivos y directorios.
+				</div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Making_Context_Mounts_Persistent.html"><strong>Anterior</strong>5.9.5. Haciendo Persistente los Contextos de Mont...</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Moving_Files_and_Directories.html"><strong>Siguiente</strong>5.10.2. Movimiento de Archivos y Directorios</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html
index 88e44ef..d68f7cb 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html
@@ -1,13 +1,13 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.9. Mounting File Systems</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html" title="Capítulo 5. Working with SELinux" /><link rel="prev" href="sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types.html" title="5.8. The file_t and default_t Types" /><link rel="next" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Changing_the_Default_Context.html" title="5.9.2. Changing the Default Context" /></head><body class="toc_embeded
  "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Changing_the_Default_Context.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.9. Mounting File Systems" id="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems"><div class="titlepage"><div><div keep-togethe
 r.within-column="always"><h2 class="title">5.9. Mounting File Systems</h2></div></div></div><div class="para">
-			By default, when a file system that supports extended attributes is mounted, the security context for each file is obtained from the <span class="emphasis"><em>security.selinux</em></span> extended attribute of the file. Files in file systems that do not support extended attributes are assigned a single, default security context from the policy configuration, based on file system type.
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.9. Montaje de Sistemas de Archivos</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html" title="Capítulo 5. Trabajando con SELinux" /><link rel="prev" href="sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types.html" title="5.8. Los tipos file_t y default_t" /><link rel="next" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Changing_the_Default_Context.html" title="5.9.2. Cambio del Contexto Predeterminado" /></head><bo
 dy class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Changing_the_Default_Context.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.9. Montaje de Sistemas de Archivos" id="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems"><div class="ti
 tlepage"><div><div keep-together.within-column="always"><h2 class="title">5.9. Montaje de Sistemas de Archivos</h2></div></div></div><div class="para">
+			Por defecto, cuando un sistema de archivo que soporta atributos extendidos se monta, el contexto de seguridad para cada archivo se obtiene de atributo extendido <span class="emphasis"><em>security.selinux</em></span> del archivo. A los archivos en sistemas de archivo que no dan soporte a atributos extendidos se les asigna un único contexto de seguridad predeterminado desde la configuración de la política, basada en el tipo de sistema de archivo.
 		</div><div class="para">
-			Use the <code class="command">mount -o context</code> command to override existing extended attributes, or to specify a different, default context for file systems that do not support extended attributes. This is useful if you do not trust a file system to supply the correct attributes, for example, removable media used in multiple systems. The <code class="command">mount -o context</code> command can also be used to support labeling for file systems that do not support extended attributes, such as File Allocation Table (FAT) or NFS file systems. The context specified with the <code class="option">context</code> is not written to disk: the original contexts are preserved, and are seen when mounting without a <code class="option">context</code> option (if the file system had extended attributes in the first place).
+			Use el comando <code class="command">mount -o context</code> para superponer los atributos extendidos actuales, o para especificar uno distinto y por defecto para sistemas de archivo que no dan soporte a atributos extendidos. Esto es útil si no confía en que un sistema de archivo provea los atributos correctos, por ejemplo, medios removibles en sistemas múltiples. El comando <code class="command">mount -o context</code> también se puede ussar para dar soporte al etiquetado de sistemas de archivos que no soportan atributos extendidos, tales como la Tabla de Ubicación de Archivos (FAT) o los sistemas de archivo NFS. El contexto especificado con la opción <code class="option">context</code> no se escribe al disco: los contextos originales son preservados, y se ven cuando se lo monta sin la opción <code class="option">context</code> (si el sistema de archivo ya tenía sopoorte para atributos extendidos).
 		</div><div class="para">
 			For further information about file system labeling, refer to James Morris's "Filesystem Labeling in SELinux" article: <a href="http://www.linuxjournal.com/article/7426">http://www.linuxjournal.com/article/7426</a>.
-		</div><div class="section" title="5.9.1. Context Mounts" id="sect-Security-Enhanced_Linux-Mounting_File_Systems-Context_Mounts"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.9.1. Context Mounts</h3></div></div></div><div class="para">
-				To mount a file system with the specified context, overriding existing contexts if they exist, or to specify a different, default context for a file system that does not support extended attributes, as the Linux root user, use the <code class="command">mount -o context=<em class="replaceable"><code>SELinux_user:role:type:level</code></em></code> command when mounting the desired file system. Context changes are not written to disk. By default, NFS mounts on the client side are labeled with a default context defined by policy for NFS file systems. In common policies, this default context uses the <code class="computeroutput">nfs_t</code> type. Without additional mount options, this may prevent sharing NFS file systems via other services, such as the Apache HTTP Server. The following example mounts an NFS file system so that it can be shared via the Apache HTTP Server:
+		</div><div class="section" title="5.9.1. Montajes de Contexto" id="sect-Security-Enhanced_Linux-Mounting_File_Systems-Context_Mounts"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.9.1. Montajes de Contexto</h3></div></div></div><div class="para">
+				Para montar un sistema de archivo con el contexto especificado, superponiendo los contextos existentes si existieran, o para especificar uno predeterminado distinto para un sistema de archivo que no da soporte para atributos extendidos, como usuario root de Linux, use el comando <code class="command">mount -o context=<em class="replaceable"><code>SELinux_user:role:type:level</code></em></code> cuando monte el sistema de archivo deseado. Los cambios de contexto no se graban en el disco. Por defecto, los montajes NFS en el lado del cliente se etiquetan con un contexto distinto definido por una política para sistemas de archivo NFS. En políticas comunes, este contexto predeterminado usa el tipo <code class="computeroutput">nfs_t</code>. Sin las opciones de montaje adicionales, esto podría evitar el que sistemas de archivo NFS sean compartidos vía otros servicios, como el Servidor HTTP Apache. El siguiente ejemplo monta un sistema de archivo NFS para que se pueda acceder
  a través del Servidor HTTP Apache:
 			</div><div class="para">
 				
 <pre class="screen"># mount server:/export /local/mount/point -o\
@@ -16,9 +16,9 @@ context="system_u:object_r:httpd_sys_content_t:s0"
 </pre>
 
 			</div><div class="para">
-				Newly-created files and directories on this file system appear to have the SELinux context specified with <code class="option">-o context</code>; however, since context changes are not written to disk for these situations, the context specified with the <code class="option">context</code> option is only retained if the <code class="option">context</code> option is used on the next mount, and if the same context is specified.
+				Los archivos y directorios recién creados en este sistema de archivo parecen tener un contexto SELinux especificado con <code class="option">-o contexto</code>; sin embargo, dado que los cambios del contexto no se escriben en el disco en estas situaciones, el contexto especificado por la opción <code class="option">-o contexto</code> sólo se mantiene si se usa la misma opción en la siguiente montada, y si además se especifica el mismo contexto.
 			</div><div class="para">
-				Type Enforcement is the main permission control used in SELinux targeted policy. For the most part, SELinux users and roles can be ignored, so, when overriding the SELinux context with <code class="option">-o context</code>, use the SELinux <code class="computeroutput">system_u</code> user and <code class="computeroutput">object_r</code> role, and concentrate on the type. If you are not using the MLS policy or multi-category security, use the <code class="computeroutput">s0</code> level.
+				La Obligación de Tipo es el control de permiso principal en la política destinada de SELinux. Para la mayor parte, los usuarios y roles de SELinux se pueden ignorar, por lo que, cuando se superponga el contexto de SELinux con <code class="option">-o context</code>, use el usuario SELinux <code class="computeroutput">system_u</code> y el rol <code class="computeroutput">object_r</code>, y concéntrese en el tipo. Si no está usando la política MLS o seguridad multi-categoría, use el nivel <code class="computeroutput">s0</code>.
 			</div><div class="note"><h2>Nota</h2><div class="para">
-					When a file system is mounted with a <code class="option">context</code> option, context changes (by users and processes) are prohibited. For example, running <code class="command">chcon</code> on a file system mounted with a <code class="option">context</code> option results in a <code class="computeroutput">Operation not supported</code> error.
-				</div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types.html"><strong>Anterior</strong>5.8. The file_t and default_t Types</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Changing_the_Default_Context.html"><strong>Siguiente</strong>5.9.2. Changing the Default Context</a></li></ul></body></html>
+					Cuando se monta un sistema de archivo con la opción <code class="option">context</code>, los cambios de contexto (por usuarios y procesos) son prohibidos. Por ejemplo, ejecutando <code class="command">chcon</code> en un sistema de archivo montado con la opción <code class="option">context</code> resulta en un error de <code class="computeroutput">Operación no soportada</code>.
+				</div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types.html"><strong>Anterior</strong>5.8. Los tipos file_t y default_t</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Changing_the_Default_Context.html"><strong>Siguiente</strong>5.9.2. Cambio del Contexto Predeterminado</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files.html
index c75be93..7e39118 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files.html
@@ -1,52 +1,52 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.7. SELinux Contexts - Labeling Files</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html" title="Capítulo 5. Working with SELinux" /><link rel="prev" href="sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS.html" title="5.6.3. Booleans for NFS and CIFS" /><link rel="next" href="sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext.html" title="5.7.2. Persistent Changes: semanage fcontext" /></head><body
  class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.7. SELinux Contexts - Labeling Files" id="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files"><di
 v class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.7. SELinux Contexts - Labeling Files</h2></div></div></div><div class="para">
-			On systems running SELinux, all processes and files are labeled with a label that contains security-relevant information. This information is called the SELinux context. For files, this is viewed using the <code class="command">ls -Z</code> command:
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.7. Contextos de SELinux - Etiquetado de Archivos</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html" title="Capítulo 5. Trabajando con SELinux" /><link rel="prev" href="sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS.html" title="5.6.3. Booleanos para NFS y CIFS" /><link rel="next" href="sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext.html" title="5.7.2. Cambios Persistentes: semanage fco
 ntext" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.7. Contextos de SELinux - Etiquetado de Archivos" id="sect-Security-Enhanced_Linux-Working_with_SELinux-SEL
 inux_Contexts_Labeling_Files"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.7. Contextos de SELinux - Etiquetado de Archivos</h2></div></div></div><div class="para">
+			En sistemas que corren SELinux, todos los procesos y archivos son etiquetados con una etiqueta que contiene información de seguridad relevante. Esta información se llama contexto de SELinux. Para archivos, esto se ve usando el comando <code class="command">ls -Z</code>:
 		</div><pre class="screen">$ ls -Z file1
 -rw-rw-r--  user1 group1 unconfined_u:object_r:user_home_t:s0 file1
 
 </pre><div class="para">
-			In this example, SELinux provides a user (<code class="computeroutput">unconfined_u</code>), a role (<code class="computeroutput">object_r</code>), a type (<code class="computeroutput">user_home_t</code>), and a level (<code class="computeroutput">s0</code>). This information is used to make access control decisions. On DAC systems, access is controlled based on Linux user and group IDs. SELinux policy rules are checked after DAC rules. SELinux policy rules are not used if DAC rules deny access first.
+			En este ejemplo, SELinux provee un usuario (<code class="computeroutput">unconfined_u</code>), un rol (<code class="computeroutput">object_r</code>), un tipo (<code class="computeroutput">user_home_t</code>) y un nivel (<code class="computeroutput">s0</code>). Esta información se usa para tomar decisiones sobre el control de acceso. En sistemas DAC, el control de acceso se basa en los IDs de usuario y grupo de Linux. Las reglas de la política de SELinux se chequean después de las reglas DAC. Las reglas de la política de SELinux no se usan si las reglas DAC niegan el acceso antes.
 		</div><div class="para">
-			There are multiple commands for managing the SELinux context for files, such as <code class="command">chcon</code>, <code class="command">semanage fcontext</code>, and <code class="command">restorecon</code>.
-		</div><div class="section" title="5.7.1. Temporary Changes: chcon" id="sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Temporary_Changes_chcon"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.7.1. Temporary Changes: chcon</h3></div></div></div><div class="para">
-				The <code class="command">chcon</code> command changes the SELinux context for files. These changes do not survive a file system relabel, or the <code class="command">/sbin/restorecon</code> command. SELinux policy controls whether users are able to modify the SELinux context for any given file. When using <code class="command">chcon</code>, users provide all or part of the SELinux context to change. An incorrect file type is a common cause of SELinux denying access.
-			</div><div class="formalpara"><h5 class="formalpara">Quick Reference</h5>
+			Hay muchos comandos para la administración del contexto de archivos de SELinux, como por ejemplo <code class="command">chcon</code>, <code class="command">semanage fcontext</code>, y <code class="command">restorecon</code>.
+		</div><div class="section" title="5.7.1. Cambios Temporales: chcon" id="sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Temporary_Changes_chcon"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.7.1. Cambios Temporales: chcon</h3></div></div></div><div class="para">
+				El comando <code class="command">chcon</code> cambia el contexto SELinux de los archivos. Estos cambios no sobreviven un reetiquetado del sistema de archivo, o el comando <code class="command">/sbin/restorecon</code>. La política de SELinux controla si los usuarios pueden modificar el contexto SELinux de algún archivo. Cuando se usa <code class="command">chcon</code>, los usuarios proveen toda o parte del contexto SELinux a cambiar. Un tipo de archivo incorrecto es una causa común de negación de acceso de SELinux.
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Temporary_Changes_chcon-Quick_Reference"><h5 class="formalpara">Referencia Rápida</h5>
 					<div class="itemizedlist"><ul><li class="listitem"><div class="para">
-								Run the <code class="command">chcon -t <em class="replaceable"><code>type</code></em> <em class="replaceable"><code>file-name</code></em></code> command to change the file type, where <em class="replaceable"><code>type</code></em> is a type, such as <code class="computeroutput">httpd_sys_content_t</code>, and <em class="replaceable"><code>file-name</code></em> is a file or directory name.
+								Ejecute el comando <code class="command">chcon -t <em class="replaceable"><code>tipo</code></em> <em class="replaceable"><code>nombre-de-archivo</code></em></code> para cambiar el tipo de archivo, donde <em class="replaceable"><code>tipo</code></em> es el tipo, por ejemplo <code class="computeroutput">httpd_sys_content_t</code>, y <em class="replaceable"><code>nombre-de-archivo</code></em> es un nombre de archivo o de directorio.
 							</div></li><li class="listitem"><div class="para">
-								Run the <code class="command">chcon -R -t <em class="replaceable"><code>type</code></em> <em class="replaceable"><code>directory-name</code></em></code> command to change the type of the directory and its contents, where <em class="replaceable"><code>type</code></em> is a type, such as <code class="computeroutput">httpd_sys_content_t</code>, and <em class="replaceable"><code>directory-name</code></em> is a directory name.
+								Ejecute el comando <code class="command">chcon -R -t <em class="replaceable"><code>tipo</code></em> <em class="replaceable"><code>nombre-de-directorio</code></em></code> para cambiar el tipo de un directorio y su contenido, donde <em class="replaceable"><code>tipo</code></em> es el tipo, por ejemplo <code class="computeroutput">httpd_sys_content_t</code>, y <em class="replaceable"><code>nombre-de-directorio</code></em> es un nombre de directorio.
 							</div></li></ul></div>
 
-				</div><div class="formalpara"><h5 class="formalpara">Changing a File's or Directory's Type</h5>
-					The following example demonstrates changing the type, and no other attributes of the SELinux context:
+				</div><div class="formalpara" id="form-Security-Enhanced_Linux-Temporary_Changes_chcon-Changing_a_Files_or_Directorys_Type"><h5 class="formalpara">Cambiando el Tipo de un Archivo o de un Directorio</h5>
+					El siguiente ejemplo muestra el cambio de tipo solamente en el contexto de SELinux:
 				</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
-						Run the <code class="command">cd</code> command without arguments to change into your home directory.
+						Ejecute el comando <code class="command">cd</code> sin argumentos para cambiar a su directorio de inicio.
 					</div></li><li class="listitem"><div class="para">
-						Run the <code class="command">touch file1</code> command to create a new file. Use the <code class="command">ls -Z file1</code> command to view the SELinux context for <code class="filename">file1</code>:
+						Ejecute el comando <code class="command">touch archivo1</code> para crear un archivo nuevo. Use el comando <code class="command">ls -Z archivo1</code> para ver el contexto de SELinux del <code class="filename">archivo1</code>:
 					</div><pre class="screen">$ ls -Z file1
 -rw-rw-r--  user1 group1 unconfined_u:object_r:user_home_t:s0 file1
 
 </pre><div class="para">
-						In this example, the SELinux context for <code class="filename">file1</code> includes the SELinux <code class="computeroutput">unconfined_u</code> user, <code class="computeroutput">object_r</code> role, <code class="computeroutput">user_home_t</code> type, and the <code class="computeroutput">s0</code> level. For a description of each part of the SELinux context, refer to <a class="xref" href="chap-Security-Enhanced_Linux-SELinux_Contexts.html" title="Capítulo 3. SELinux Contexts">Capítulo 3, <i>SELinux Contexts</i></a>.
+						In this example, the SELinux context for <code class="filename">file1</code> includes the SELinux <code class="computeroutput">unconfined_u</code> user, <code class="computeroutput">object_r</code> role, <code class="computeroutput">user_home_t</code> type, and the <code class="computeroutput">s0</code> level. For a description of each part of the SELinux context, refer to <a class="xref" href="chap-Security-Enhanced_Linux-SELinux_Contexts.html" title="Capítulo 3. Contextos de SELinux">Capítulo 3, <i>Contextos de SELinux</i></a>.
 					</div></li><li class="listitem"><div class="para">
-						Run the <code class="command">chcon -t samba_share_t file1</code> command to change the type to <code class="computeroutput">samba_share_t</code>. The <code class="option">-t</code> option only changes the type. View the change with <code class="command">ls -Z file1</code>:
+						EJecute el comando <code class="command">chcon -t samba_share_t archivo1</code> para cambiar el tipo a <code class="computeroutput">samba_share_t</code>. La opción <code class="option">-t</code> sólo cambia el tipo. Vea el cambio con <code class="command">ls -Z archivo1</code>:
 					</div><pre class="screen">$ ls -Z file1 
 -rw-rw-r--  user1 group1 unconfined_u:object_r:samba_share_t:s0 file1
 
 </pre></li><li class="listitem"><div class="para">
-						Use the <code class="command">/sbin/restorecon -v file1</code> command to restore the SELinux context for the <code class="filename">file1</code> file. Use the <code class="option">-v</code> option to view what changes:
+						Use el comando <code class="command">/sbin/restorecon -v archivo1</code> para restaurar el contexto de SELinux del <code class="filename">archivo1</code>. Use la opción <code class="option">-v</code> para ver qué cambia:
 					</div><pre class="screen">$ /sbin/restorecon -v file1
 restorecon reset file1 context unconfined_u:object_r:samba_share_t:s0-&gt;system_u:object_r:user_home_t:s0
 
 </pre><div class="para">
-						In this example, the previous type, <code class="computeroutput">samba_share_t</code>, is restored to the correct, <code class="computeroutput">user_home_t</code> type. When using targeted policy (the default SELinux policy in Fedora 11), the <code class="command">/sbin/restorecon</code> command reads the files in the <code class="filename">/etc/selinux/targeted/contexts/files/</code> directory, to see which SELinux context files should have.
+						En este ejemplo, el tipo previo <code class="computeroutput">samba_share_t</code>, se restaura al tipo correcto <code class="computeroutput">user_home_t</code>. Cuando se usa la política destinada (la política SELinux predeterminada en Fedora 11), el comando <code class="command">/sbin/restorecon</code> lee los archivos en el directorio <code class="filename">/etc/selinux/targeted/contexts/files/</code> para ver qué contexto de SELinux deben tener los archivos.
 					</div></li></ol></div><div class="para">
-				The example in this section works the same for directories, for example, if <code class="filename">file1</code> was a directory.
-			</div><div class="formalpara"><h5 class="formalpara">Changing a Directory and its Contents Types</h5>
-					The following example demonstrates creating a new directory, and changing the directory's file type (along with its contents) to a type used by the Apache HTTP Server. The configuration in this example is used if you want Apache HTTP Server to use a different document root (instead of <code class="filename">/var/www/html/</code>):
+				El ejemplo en esta sección funciona igual para directorios, por ejemplo, si <code class="filename">archivo1</code> fuera un directorio.
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Temporary_Changes_chcon-Changing_a_Directory_and_its_Contents_Types"><h5 class="formalpara">Cambio de un Directorio y sus Tipos de Contenidos</h5>
+					El siguiente ejemplo muestra la creación de un directorio nuevo y el cambio del tipo de archivo del mismo (junto con su contenido) a un tipo usado por el Servidor HTTP Apache. La configuración en este ejemplo se usa si quiere que el Servidor HTTP Apache use una raíz de documento distinta (en vez de <code class="filename">/var/www/html/</code>):
 				</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">mkdir /web</code> command to create a new directory, and then the <code class="command">touch /web/file{1,2,3}</code> command to create 3 empty files (<code class="filename">file1</code>, <code class="filename">file2</code>, and <code class="filename">file3</code>). The <code class="filename">/web/</code> directory and files in it are labeled with the <code class="computeroutput">default_t</code> type:
+						Como usuario root de Linux, ejecute el comando <code class="command">mkdir /web</code> para crear un directorio nuevo, y luego el comando <code class="command">touch /web/archivo{1,2,3}</code> para crear 3 archivos vacíos (<code class="filename">archivo1</code>, <code class="filename">archivo2</code> y <code class="filename">archivo3</code>). El directorio <code class="filename">/web/</code> y los archivos en él son etiquetados con el tipo <code class="computeroutput">default_t</code>:
 					</div><pre class="screen"># ls -dZ /web
 drwxr-xr-x  root root unconfined_u:object_r:default_t:s0 /web
 # ls -lZ /web
@@ -55,7 +55,7 @@ drwxr-xr-x  root root unconfined_u:object_r:default_t:s0 /web
 -rw-r--r--  root root unconfined_u:object_r:default_t:s0 file3
 
 </pre></li><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">chcon -R -t httpd_sys_content_t /web/</code> command to change the type of the <code class="filename">/web/</code> directory (and its contents) to <code class="computeroutput">httpd_sys_content_t</code>:
+						Como usuario root de Linux, corra el comando <code class="command">chcon -R -t httpd_sys_content_t /web/</code> para cambiar el tipo del directorio <code class="filename">/web/</code> (y su contenido) a <code class="computeroutput">httpd_sys_content_t</code>:
 					</div><pre class="screen"># chcon -R -t httpd_sys_content_t /web/
 # ls -dZ /web/
 drwxr-xr-x  root root unconfined_u:object_r:httpd_sys_content_t:s0 /web/
@@ -65,7 +65,7 @@ drwxr-xr-x  root root unconfined_u:object_r:httpd_sys_content_t:s0 /web/
 -rw-r--r--  root root unconfined_u:object_r:httpd_sys_content_t:s0 file3
 
 </pre></li><li class="listitem"><div class="para">
-						As the Linux root user, run the <code class="command">/sbin/restorecon -R -v /web/</code> command to restore the default SELinux contexts:
+						Como usuario root de Linux, corra el comando <code class="command">/sbin/restorecon -R -v /web/</code> para restaurar los contextos de SELinux predeterminados:
 					</div><pre class="screen"># /sbin/restorecon -R -v /web/
 restorecon reset /web context unconfined_u:object_r:httpd_sys_content_t:s0-&gt;system_u:object_r:default_t:s0
 restorecon reset /web/file2 context unconfined_u:object_r:httpd_sys_content_t:s0-&gt;system_u:object_r:default_t:s0
@@ -73,7 +73,7 @@ restorecon reset /web/file3 context unconfined_u:object_r:httpd_sys_content_t:s0
 restorecon reset /web/file1 context unconfined_u:object_r:httpd_sys_content_t:s0-&gt;system_u:object_r:default_t:s0
 
 </pre></li></ol></div><div class="para">
-				Refer to the <span class="citerefentry"><span class="refentrytitle">chcon</span>(1)</span> manual page for further information about <code class="command">chcon</code>.
+				Vaya a la página del manual de <span class="citerefentry"><span class="refentrytitle">chcon</span>(1)</span> para más información sobre <code class="command">chcon</code>.
 			</div><div class="note"><h2>Nota</h2><div class="para">
-					Type Enforcement is the main permission control used in SELinux targeted policy. For the most part, SELinux users and roles can be ignored.
-				</div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS.html"><strong>Anterior</strong>5.6.3. Booleans for NFS and CIFS</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext.html"><strong>Siguiente</strong>5.7.2. Persistent Changes: semanage fcontext</a></li></ul></body></html>
+					La Obligación de Tipo es el control de permisos principal usado en la política destinada de SELinux. Para la mayor parte, los usuarios y roles de SELinux se pueden ignorar.
+				</div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS.html"><strong>Anterior</strong>5.6.3. Booleanos para NFS y CIFS</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext.html"><strong>Siguiente</strong>5.7.2. Cambios Persistentes: semanage fcontext</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes.html
index 2a8fee3..6ae0fb3 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes.html
@@ -1,15 +1,15 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.5. SELinux Modes</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html" title="Capítulo 5. Working with SELinux" /><link rel="prev" href="sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux.html" title="5.4.2. Disabling SELinux" /><link rel="next" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html" title="5.6. Booleans" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc"
  src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.5. SELinux Modes" id="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.5. SELinux Modes</h2></div></div></div><div class="para">
-			SELinux has three modes:
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.5. Modos de SELinux</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html" title="Capítulo 5. Trabajando con SELinux" /><link rel="prev" href="sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux.html" title="5.4.2. Deshabilitando SELinux" /><link rel="next" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html" title="5.6. Booleanos" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocfr
 ame" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.5. Modos de SELinux" id="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.5. Modos de SELinux</h2></div></div></div
 ><div class="para">
+			SELinux tiene tres modos:
 		</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-					Enforcing: SELinux policy is enforced. SELinux denies access based on SELinux policy rules.
+					Obligatorio: la política de SELinux es obligatoria. SELinux niega el acceso basado en las reglas de políticas de SELinux.
 				</div></li><li class="listitem"><div class="para">
-					Permissive: SELinux policy is not enforced. SELinux does not deny access, but denials are logged for actions that would have been denied if running in enforcing mode.
+					Permisivo: la política de SELinux no es obligatoria. SELinux no niega el acceso, pero se guardan las negaciones para acciones que hubieran sido negadas si el modo obligatorio estaba activado.
 				</div></li><li class="listitem"><div class="para">
-					Disabled: SELinux is disabled. Only DAC rules are used.
+					Deshabilitado: SELinux está deshabilitado. Sólo se usan las reglas DAC.
 				</div></li></ul></div><div class="para">
-			Use the <code class="command">/usr/sbin/setenforce</code> command to change between enforcing and permissive mode. Changes made with <code class="command">/usr/sbin/setenforce</code> do not persist across reboots. To change to enforcing mode, as the Linux root user, run the <code class="command">/usr/sbin/setenforce 1</code> command. To change to permissive mode, run the <code class="command">/usr/sbin/setenforce 0</code> command. Use the <code class="command">/usr/sbin/getenforce</code> command to view the current SELinux mode.
+			Use el comando <code class="command">/usr/sbin/setenforce</code> para cambiar entre los modos obediente y permisivo. Los cambios hechos con <code class="command">/usr/sbin/setenforce</code> no sobreviven a una reiniciada. Para cambiar a modo obediente, como usuario root de Linux, ejecute el comando <code class="command">/usr/sbin/setenforce 1</code>. Para cambiar a modo permisivo, ejecute el comando <code class="command">/usr/sbin/setenforce 0</code>. Use el comando <code class="command">/usr/sbin/getenforce</code> para ver el modo de SELinux actual.
 		</div><div class="para">
-			Persistent mode changes are covered in <a class="xref" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html" title="5.4. Enabling and Disabling SELinux">Sección 5.4, “Enabling and Disabling SELinux”</a>.
-		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux.html"><strong>Anterior</strong>5.4.2. Disabling SELinux</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html"><strong>Siguiente</strong>5.6. Booleans</a></li></ul></body></html>
+			Persistent mode changes are covered in <a class="xref" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html" title="5.4. Habilitando y Deshabilitando SELinux">Sección 5.4, “Habilitando y Deshabilitando SELinux”</a>.
+		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux.html"><strong>Anterior</strong>5.4.2. Deshabilitando SELinux</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html"><strong>Siguiente</strong>5.6. Booleanos</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types.html
index 7d532fb..d2eda0c 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types.html
@@ -1,9 +1,9 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.8. The file_t and default_t Types</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html" title="Capítulo 5. Working with SELinux" /><link rel="prev" href="sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext.html" title="5.7.2. Persistent Changes: semanage fcontext" /><link rel="next" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html" title="5.9. Mounting File Systems" /></head><body 
 class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.8. The file_t and default_t Types" id="sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types">
 <div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.8. The file_t and default_t Types</h2></div></div></div><div class="para">
-			On file systems that support extended attributes, when a file that lacks an SELinux context on disk is accessed, it is treated as if it had a default context as defined by SELinux policy. In common policies, this default context uses the <code class="computeroutput">file_t</code> type. This should be the only use of this type, so that files without a context on disk can be distinguished in policy, and generally kept inaccessible to confined domains. The <code class="computeroutput">file_t</code> type should not exist on correctly-labeled file systems, because all files on a system running SELinux should have an SELinux context, and the <code class="computeroutput">file_t</code> type is never used in file-context configuration<sup>[<a id="id1652523" href="#ftn.id1652523" class="footnote">11</a>]</sup>.
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.8. Los tipos file_t y default_t</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html" title="Capítulo 5. Trabajando con SELinux" /><link rel="prev" href="sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext.html" title="5.7.2. Cambios Persistentes: semanage fcontext" /><link rel="next" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html" title="5.9. Montaje de Sistemas de Archivos
 " /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.8. Los tipos file_t y default_t" id="sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_de
 fault_t_Types"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.8. Los tipos file_t y default_t</h2></div></div></div><div class="para">
+			En sistemas de archivo que soportan atributos extendidos, cuando se accede a un archivo en disco al que le falta el contexto de SELinux, se trata como si tuviera un contexto predeterminado tal como fue definido en la política de SELinux. En políticas comunes, este conexto por defecto usa el tipo <code class="computeroutput">file_t</code>. Este debería ser el único uso de este tipo, por lo que los archivos sin un contexto en el disco se podrían distinguir en la política, y generalmente mantenerse inaccesibles a dominios confinados. El tipo <code class="computeroutput">file_t</code> no debería existir en sistemas de archivo correctamente etiquetados, porque todos los archivos dado que todos los archivos en un sistema corriendo SELinux deberían tener un contexto de SELinux, y el tipo <code class="computeroutput">file_t</code> no sebería usarse en la configuración de contexto de archivos <sup>[<a id="id1116773" href="#ftn.id1116773" class="footnote">11</a>]</sup>.
 		</div><div class="para">
-			The <code class="computeroutput">default_t</code> type is used on files that do not match any other pattern in file-context configuration, so that such files can be distinguished from files that do not have a context on disk, and generally kept inaccessible to confined domains. If you create a new top-level directory, such as <code class="filename">/mydirectory/</code>, this directory may be labeled with the <code class="computeroutput">default_t</code> type. If services need access to such a directory, update the file-contexts configuration for this location. Refer to <a class="xref" href="sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext.html" title="5.7.2. Persistent Changes: semanage fcontext">Sección 5.7.2, “Persistent Changes: semanage fcontext”</a> for details on adding a context to the file-context configuration.
-		</div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id1652523" href="#id1652523" class="para">11</a>] </sup>
-				Files in <code class="filename">/etc/selinux/targeted/contexts/files/</code> define contexts for files and directories. Files in this directory are read by <code class="command">restorecon</code> and <code class="command">setfiles</code> to restore files and directories to their default contexts.
-			</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext.html"><strong>Anterior</strong>5.7.2. Persistent Changes: semanage fcontext</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html"><strong>Siguiente</strong>5.9. Mounting File Systems</a></li></ul></body></html>
+			The <code class="computeroutput">default_t</code> type is used on files that do not match any other pattern in file-context configuration, so that such files can be distinguished from files that do not have a context on disk, and generally kept inaccessible to confined domains. If you create a new top-level directory, such as <code class="filename">/mydirectory/</code>, this directory may be labeled with the <code class="computeroutput">default_t</code> type. If services need access to such a directory, update the file-contexts configuration for this location. Refer to <a class="xref" href="sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext.html" title="5.7.2. Cambios Persistentes: semanage fcontext">Sección 5.7.2, “Cambios Persistentes: semanage fcontext”</a> for details on adding a context to the file-context configuration.
+		</div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id1116773" href="#id1116773" class="para">11</a>] </sup>
+				Los archivos en <code class="filename">/etc/selinux/targeted/contexts/files/</code> definen los contextos de los archivos y directorios. Los archivos en este directorio son accedidos por <code class="command">restorecon</code> y por <code class="command">setfiles</code> para restaurar al valor predeterminado los contextos de los archivos y directorios.
+			</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext.html"><strong>Anterior</strong>5.7.2. Cambios Persistentes: semanage fcontext</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html"><strong>Siguiente</strong>5.9. Montaje de Sistemas de Archivos</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used.html b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used.html
index a87210e..51fcbb3 100644
--- a/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used.html
+++ b/public_html/es-ES/Fedora/11/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used.html
@@ -1,19 +1,19 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.2. Which Log File is Used</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Security-Enhanced Linux" /><link rel="up" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html" title="Capítulo 5. Working with SELinux" /><link rel="prev" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html" title="Capítulo 5. Working with SELinux" /><link rel="next" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Main_Configuration_File.html" title="5.3. Main Configuration File" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="t
 ocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Main_Configuration_File.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.2. Which Log File is Used" id="sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.2. Which Log File is Used</h2></div
 ></div></div><div class="para">
-			In Fedora 11, the <span class="package">setroubleshoot-server</span> and <span class="package">audit</span> packages are installed if packages are not removed from the default package selection. These packages include the <code class="systemitem">setroubleshootd</code> and <code class="systemitem">auditd</code> daemons respectively. These daemons run by default.
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.2. Qué Archivo Log se usa</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-11-es-ES-1.3-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html" title="Capítulo 5. Trabajando con SELinux" /><link rel="prev" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html" title="Capítulo 5. Trabajando con SELinux" /><link rel="next" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Main_Configuration_File.html" title="5.3. Archivo de Configuración Principal" /></head><body class="toc_embeded "><div id="tocdiv" cla
 ss="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Main_Configuration_File.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.2. Qué Archivo Log se usa" id="sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.2. Qué Arch
 ivo Log se usa</h2></div></div></div><div class="para">
+			En Fedora 11, los paquetes <span class="package">setroubleshoot-server</span> y <span class="package">audit</span> se instalan si los paquetes no se eliminan de la selección de paquetes predeterminada. Estos paquetes incluyen a los demonios <code class="systemitem">setroubleshootd</code> y <code class="systemitem">auditd</code> respectivamente. Estos demonios se ejecutan por defecto.
 		</div><div class="para">
-			SELinux denial messages, such as the following, are written to <code class="filename">/var/log/audit/audit.log</code> by default:
+			Los mensajes de negación de SELinux, tales como el siguiente, se escriben por defecto en <code class="filename">/var/log/audit/audit.log</code>:
 		</div><pre class="screen">type=AVC msg=audit(1223024155.684:49): avc:  denied  { getattr } for  pid=2000 comm="httpd" path="/var/www/html/file1" dev=dm-0 ino=399185 scontext=unconfined_u:system_r:httpd_t:s0 tcontext=system_u:object_r:samba_share_t:s0 tclass=file
 
 </pre><div class="para">
-			Also, if <code class="systemitem">setroubleshootd</code> is running, which it is by default, denial messages from <code class="filename">/var/log/audit/audit.log</code> are translated to an easier-to-read form and sent to <code class="filename">/var/log/messages</code>:
+			También, si <code class="systemitem">setroubleshootd</code> está ejecutándose, lo que es por defecto, los mensajes de negación desde <code class="filename">/var/log/audit/audit.log</code> se traducen a una forma más fácil de leer en <code class="filename">/var/log/messages</code>:
 		</div><pre class="screen">May  7 18:55:56 localhost setroubleshoot: SELinux is preventing httpd (httpd_t) "getattr" to /var/www/html/file1 (samba_share_t). For complete SELinux messages. run sealert -l de7e30d6-5488-466d-a606-92c9f40d316d
 
 </pre><div class="para">
-			Denial messages are sent to a different location, depending on which daemons are running:
-		</div><div class="segmentedlist"><table border="0"><thead><tr class="segtitle"><th>Daemon</th><th>Log Location</th></tr></thead><tbody><tr class="seglistitem"><td class="seg">auditd on</td><td class="seg"><code class="filename">/var/log/audit/audit.log</code></td></tr><tr class="seglistitem"><td class="seg">auditd off; rsyslogd on</td><td class="seg"><code class="filename">/var/log/messages</code></td></tr><tr class="seglistitem"><td class="seg">setroubleshootd, rsyslogd, and auditd on</td><td class="seg"><code class="filename">/var/log/audit/audit.log</code>. Easier-to-read denial messages also sent to <code class="filename">/var/log/messages</code></td></tr></tbody></table></div><div class="formalpara"><h5 class="formalpara">Starting Daemons Automatically</h5>
-				To configure the <code class="systemitem">auditd</code>, <code class="systemitem">rsyslogd</code>, and <code class="systemitem">setroubleshootd</code> daemons to automatically start at boot, run the following commands as the Linux root user:
+			Los mensajes de negación se envían a una ubicación distinta, dependiendo de cuáles demonios se están ejecutando:
+		</div><div class="segmentedlist"><table border="0"><thead><tr class="segtitle"><th>Daemon</th><th>Log Location</th></tr></thead><tbody><tr class="seglistitem"><td class="seg">auditd on</td><td class="seg"><code class="filename">/var/log/audit/audit.log</code></td></tr><tr class="seglistitem"><td class="seg">auditd off; rsyslogd on</td><td class="seg"><code class="filename">/var/log/messages</code></td></tr><tr class="seglistitem"><td class="seg">setroubleshootd, rsyslogd, and auditd on</td><td class="seg"><code class="filename">/var/log/audit/audit.log</code>. Easier-to-read denial messages also sent to <code class="filename">/var/log/messages</code></td></tr></tbody></table></div><div class="formalpara" id="form-Security-Enhanced_Linux-Which_Log_File_is_Used-Starting_Daemons_Automatically"><h5 class="formalpara">Iniciando Demonios Automáticamente</h5>
+				Para configurar los demonios <code class="systemitem">auditd</code>, <code class="systemitem">rsyslogd</code>, y <code class="systemitem">setroubleshootd</code> para que inicien automáticamente al arrancar, corra los siguientes comandos como usuario root de Linux:
 			</div><pre class="screen">/sbin/chkconfig --levels 2345 auditd on
 
 </pre><pre class="screen">/sbin/chkconfig --levels 2345 rsyslog on
@@ -21,15 +21,15 @@
 </pre><pre class="screen">/sbin/chkconfig --levels 345 setroubleshoot on
 
 </pre><div class="para">
-			Use the <code class="command">service <em class="replaceable"><code>service-name</code></em> status</code> command to check if these services are running, for example:
+			Use el comando <code class="command">service <em class="replaceable"><code>nombre-de-servicio</code></em> status</code> para chequear si estos servicios se están ejecutando, por ejemplo:
 		</div><pre class="screen">
 $ /sbin/service auditd status
 auditd (pid  <em class="replaceable"><code>1318</code></em>) is running...
 
 </pre><div class="para">
-			If the above services are not running (<code class="computeroutput"><em class="replaceable"><code>service-name</code></em> is stopped</code>), use the <code class="command">service <em class="replaceable"><code>service-name</code></em> start</code> command as the Linux root user to start them. For example:
+			Si los servicos de arriba no se están ejecutando (<code class="computeroutput"><em class="replaceable"><code>nombre-de-servicio</code></em> está detenido</code>), use el comando <code class="command">service <em class="replaceable"><code>nombre-de-servicio</code></em> start</code> como usuario root de Linux para iniciarlos. Por ejemplo:
 		</div><pre class="screen">
 # /sbin/service setroubleshoot start
 Starting setroubleshootd:                                  [  OK  ]
 
-</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html"><strong>Anterior</strong>Capítulo 5. Working with SELinux</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Main_Configuration_File.html"><strong>Siguiente</strong>5.3. Main Configuration File</a></li></ul></body></html>
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html"><strong>Anterior</strong>Capítulo 5. Trabajando con SELinux</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Main_Configuration_File.html"><strong>Siguiente</strong>5.3. Archivo de Configuración Principal</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/11/pdf/Security-Enhanced_Linux/Fedora-11-Security-Enhanced_Linux-es-ES.pdf b/public_html/es-ES/Fedora/11/pdf/Security-Enhanced_Linux/Fedora-11-Security-Enhanced_Linux-es-ES.pdf
index 6dc36b5..ad22f66 100644
Binary files a/public_html/es-ES/Fedora/11/pdf/Security-Enhanced_Linux/Fedora-11-Security-Enhanced_Linux-es-ES.pdf and b/public_html/es-ES/Fedora/11/pdf/Security-Enhanced_Linux/Fedora-11-Security-Enhanced_Linux-es-ES.pdf differ
diff --git a/public_html/es-ES/Fedora/13/epub/Security-Enhanced_Linux/Fedora-13-Security-Enhanced_Linux-es-ES.epub b/public_html/es-ES/Fedora/13/epub/Security-Enhanced_Linux/Fedora-13-Security-Enhanced_Linux-es-ES.epub
index 8aabeaf..cd05ca7 100644
Binary files a/public_html/es-ES/Fedora/13/epub/Security-Enhanced_Linux/Fedora-13-Security-Enhanced_Linux-es-ES.epub and b/public_html/es-ES/Fedora/13/epub/Security-Enhanced_Linux/Fedora-13-Security-Enhanced_Linux-es-ES.epub differ
diff --git a/public_html/es-ES/Fedora/13/html-single/Security-Enhanced_Linux/Common_Content/css/common.css b/public_html/es-ES/Fedora/13/html-single/Security-Enhanced_Linux/Common_Content/css/common.css
index e1f4d9f..d8a380f 100644
--- a/public_html/es-ES/Fedora/13/html-single/Security-Enhanced_Linux/Common_Content/css/common.css
+++ b/public_html/es-ES/Fedora/13/html-single/Security-Enhanced_Linux/Common_Content/css/common.css
@@ -50,7 +50,8 @@ body.desktop .book > .toc {
 	line-height:1.35em;
 }
 
-.toc .chapter, .toc .appendix, .toc .glossary {
+ .toc .glossary,
+.toc .chapter, .toc .appendix {
 	margin-top:1em;
 }
 
@@ -59,7 +60,8 @@ body.desktop .book > .toc {
 	display:block;
 }
 
-span.appendix, span.glossary {
+span.glossary,
+span.appendix {
 	display:block;
 	margin-top:0.5em;
 }
@@ -346,7 +348,6 @@ a.version:focus, a.version:hover {
 	clear:both;
 }
 
-
 /*revision history*/
 .revhistory {
 	display:block;
@@ -362,34 +363,24 @@ a.version:focus, a.version:hover {
 }
 
 .revhistory td {
-	text-align:right;
+	text-align :left;
 	padding:0em;
 	border: none;
 	border-top: 1px solid #fff;
+	font-weight: bold;
 }
 
-
-.revhistory tr td:first-child {
-	text-align:left;
+.revhistory .simplelist td {
+	font-weight: normal;
 }
 
-.revhistory tr td p, .revhistory tr td div.para {
-	text-align:left;
-	font-weight:bold;
-	display:block;
-	margin:0em;
-	padding:0em;
-	padding-bottom:0.7em;
-	border-bottom:1px solid #eee;
+.revhistory .simplelist {
+	margin-bottom: 1.5em;
+	margin-left: 1em;
 }
 
 .revhistory table th {
-	background-color:transparent;
-	color:#336699;
-	font-size:2em;
-	padding: 1em 0em;
-	border: none;
-	border-bottom:1px solid #eee;
+	display: none;
 }
 
 
@@ -901,6 +892,10 @@ th, td {
 	border: 1px solid #000;
 }
 
+.simplelist th, .simplelist td {
+	border: none;
+}
+
 table table td {
 	border-bottom:1px dotted #aaa;
 	background-color:white;
@@ -1007,7 +1002,8 @@ span.chapter {
 	margin-bottom:1em;
 }
 
-.glossary dt, .index dt {
+.glossary dt,
+.index dt {
 	color:#444;
 	padding-top:.5em;
 }
@@ -1375,10 +1371,6 @@ pre {
 	border-radius: 15px;
 }
 
-.term{
-	color:#336699;
-}
-
 .package, .citetitle {
 	font-style: italic;
 }
diff --git a/public_html/es-ES/Fedora/13/html-single/Security-Enhanced_Linux/Common_Content/css/lang.css b/public_html/es-ES/Fedora/13/html-single/Security-Enhanced_Linux/Common_Content/css/lang.css
index e69de29..81c3115 100644
--- a/public_html/es-ES/Fedora/13/html-single/Security-Enhanced_Linux/Common_Content/css/lang.css
+++ b/public_html/es-ES/Fedora/13/html-single/Security-Enhanced_Linux/Common_Content/css/lang.css
@@ -0,0 +1,2 @@
+/* place holder */
+
diff --git a/public_html/es-ES/Fedora/13/html-single/Security-Enhanced_Linux/index.html b/public_html/es-ES/Fedora/13/html-single/Security-Enhanced_Linux/index.html
index 38f33a3..bd6412c 100644
--- a/public_html/es-ES/Fedora/13/html-single/Security-Enhanced_Linux/index.html
+++ b/public_html/es-ES/Fedora/13/html-single/Security-Enhanced_Linux/index.html
@@ -1,9 +1,9 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Linux con Seguridad Mejorada</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><meta name="description" content="La Guía del Usuario de SELinux asiste a los usuarios y administradores en la administración y uso del Linux con Seguridad Mejorada." /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a cl
 ass="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><div xml:lang="es-ES" class="book" title="Linux con Seguridad Mejorada" lang="es-ES"><div class="titlepage"><div><div class="producttitle" font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><span class="productname">Fedora</span> <span class="productnumber">13</span></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h1 id="id2542228" class="title">Linux con Seguridad Mejorada</h1></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h2 class="subtitle">Guía del Usuario</h2></div><p class="edition">Edición 1.5</p><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h3 class="corpauthor">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Linux con Seguridad Mejorada</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><meta name="description" content="The SELinux User Guide assists users and administrators in managing and using Security-Enhanced Linux." /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://
 docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><div xml:lang="es-ES" class="book" title="Linux con Seguridad Mejorada" lang="es-ES"><div class="titlepage"><div><div class="producttitle" font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><span class="productname">Fedora</span> <span class="productnumber">13</span></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h1 id="id637981" class="title">Linux con Seguridad Mejorada</h1></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h2 class="subtitle">Guía del Usuario</h2></div><p class="edition">Edición 1.4</p><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h3 class="corpauthor">
 		<span class="inlinemediaobject"><object data="Common_Content/images/title_logo.svg" type="image/svg+xml"> Logo</object></span>
 
-	</h3></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div xml:lang="es-ES" class="authorgroup" lang="es-ES"><div class="author"><h3 class="author"><span class="firstname">Murray</span> <span class="surname">McAllister</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Ingeniería de Servicios de Contenido</span></div><code class="email"><a class="email" href="mailto:mmcallis at redhat.com">mmcallis at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Scott</span> <span class="surname">Radvan</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Ingeniería de Servicios de Contenido</span></div><code class="email"><a class="email" href="mailto:sradvan at redhat.com">sradvan at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Daniel</span> <span class="surname">Wa
 lsh</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Ingeniería de la Seguridad</span></div><code class="email"><a class="email" href="mailto:dwalsh at redhat.com">dwalsh at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Dominick</span> <span class="surname">Grift</span></h3><span class="contrib">Editor técnico para los capítulos Introducción, Contextos de SELinux, Política Destinada, Trabajando con SELinux, Confinando Usuarios y Solución de Problemas.</span> <div class="affiliation"><span class="orgname"></span> <span class="orgdiv"></span></div><code class="email"><a class="email" href="mailto:domg472 at gmail.com">domg472 at gmail.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Eric</span> <span class="surname">Paris</span></h3><span class="contrib">Editor técnico para las secciones Montaje de Sistemas de Archivos y Mensajes Crudos de Auditoría.</span> 
 <div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Ingeniería de la Seguridad</span></div><code class="email"><a class="email" href="mailto:eparis at parisplace.org">eparis at parisplace.org</a></code></div><div class="author"><h3 class="author"><span class="firstname">James</span> <span class="surname">Morris</span></h3><span class="contrib">Editor técnico para los capítulos Introducción y Política Destinada.</span> <div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Ingeniería de la Seguridad</span></div><code class="email"><a class="email" href="mailto:jmorris at redhat.com">jmorris at redhat.com</a></code></div></div></div><hr /><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div id="id893807" class="legalnotice"><h1 class="legalnotice">Aviso Legal</h1><div class="para">
+	</h3></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div xml:lang="es-ES" class="authorgroup" lang="es-ES"><div class="author"><h3 class="author"><span class="firstname">Murray</span> <span class="surname">McAllister</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:mmcallis at redhat.com">mmcallis at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Scott</span> <span class="surname">Radvan</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:sradvan at redhat.com">sradvan at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Daniel</span> <span class="surname">Walsh</span></h3><di
 v class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Security Engineering</span></div><code class="email"><a class="email" href="mailto:dwalsh at redhat.com">dwalsh at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Dominick</span> <span class="surname">Grift</span></h3><span class="contrib">Technical editor for the Introduction, SELinux Contexts, Targeted Policy, Working with SELinux, Confining Users, and Troubleshooting chapters.</span> <div class="affiliation"><span class="orgname"></span> <span class="orgdiv"></span></div><code class="email"><a class="email" href="mailto:domg472 at gmail.com">domg472 at gmail.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Eric</span> <span class="surname">Paris</span></h3><span class="contrib">Technical editor for the Mounting File Systems and Raw Audit Messages sections.</span> <div class="affiliation"><span class="orgname">Red Hat</span> <spa
 n class="orgdiv">Security Engineering</span></div><code class="email"><a class="email" href="mailto:eparis at parisplace.org">eparis at parisplace.org</a></code></div><div class="author"><h3 class="author"><span class="firstname">James</span> <span class="surname">Morris</span></h3><span class="contrib">Technical editor for the Introduction and Targeted Policy chapters.</span> <div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Security Engineering</span></div><code class="email"><a class="email" href="mailto:jmorris at redhat.com">jmorris at redhat.com</a></code></div></div></div><hr /><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div id="id782264" class="legalnotice"><h1 class="legalnotice">Aviso Legal</h1><div class="para">
 		Copyright <span class="trademark"></span>© 2010 Red Hat, Inc.
 	</div><div class="para">
 		The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at <a href="http://creativecommons.org/licenses/by-sa/3.0/">http://creativecommons.org/licenses/by-sa/3.0/</a>. The original authors of this document, and Red Hat, designate the Fedora Project as the "Attribution Party" for purposes of CC-BY-SA. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
@@ -22,24 +22,24 @@
 	</div><div class="para">
 		All other trademarks are the property of their respective owners.
 	</div></div></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div class="abstract" title="Resumen"><h6>Resumen</h6><div class="para">
-			La Guía del Usuario de SELinux asiste a los usuarios y administradores en la administración y uso del <span class="trademark">Linux</span>® con Seguridad Mejorada.
-		</div></div></div></div><hr /></div><div class="toc"><dl><dt><span class="preface"><a href="#pref-Security-Enhanced_Linux-Preface">Prefacio</a></span></dt><dd><dl><dt><span class="section"><a href="#id1113856">1. Convenciones del Documento</a></span></dt><dd><dl><dt><span class="section"><a href="#id2062524">1.1. Convenciones Tipográficas</a></span></dt><dt><span class="section"><a href="#id2082376">1.2. Convenciones del documento</a></span></dt><dt><span class="section"><a href="#id1073400">1.3. Notas y Advertencias</a></span></dt></dl></dd><dt><span class="section"><a href="#id867204">2. ¡Necesitamos sus comentarios!</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Security-Enhanced_Linux-Trademark_Information">1. Información de Marca Comercial</a></span></dt><dd><dl><dt><span class="section"><a href="#chap-Security-Enhanced_Linux-Trademark_Information-Source_Code">1.1. Código Fuente</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-S
 ecurity-Enhanced_Linux-Introduction">2. Introducción</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Introduction-Benefits_of_running_SELinux">2.1. Beneficios de usar SELinux</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Introduction-Examples">2.2. Ejemplos</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture">2.3. Arquitectura de SELinux</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Introduction-SELinux_on_Other_Operating_Systems">2.4. SELinux en otros Sistemas Operativos</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Security-Enhanced_Linux-SELinux_Contexts">3. Contextos de SELinux</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-SELinux_Contexts-Domain_Transitions">3.1. Transiciones de Dominios</a></span></dt><dt><span class="section"><a href="#sec
 t-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Processes">3.2. Contextos de SELinux para los Procesos</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Users">3.3. Contextos de SELinux para los Usuarios</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Security-Enhanced_Linux-Targeted_Policy">4. Política Destinado</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Targeted_Policy-Confined_Processes">4.1. Procesos Confinados</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Targeted_Policy-Unconfined_Processes">4.2. Procesos no Confinados</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users">4.3. Usuarios Confinados y no Confinados</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Security-Enhanced_Linux-Working_with_SELin
 ux">5. Trabajando con SELinux</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Packages">5.1. Paquetes de SELinux</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used">5.2. Qué Archivo Log se usa</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Main_Configuration_File">5.3. Archivo de Configuración Principal</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux">5.4. Habilitando y Deshabilitando SELinux</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Enabling_SELinux">5.4.1. Habilitando SELinux</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux">5.4.2. Deshabilit
 ando SELinux</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes">5.5. Modos de SELinux</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans">5.6. Booleanos</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Booleans-Listing_Booleans">5.6.1. Listando los Booleanos</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Booleans-Configuring_Booleans">5.6.2. Configurando los Booleanos</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS">5.6.3. Booleanos para NFS y CIFS</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files">5.7. Contextos de SELinux - Etiquetado de Archivos</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Secu
 rity-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Temporary_Changes_chcon">5.7.1. Cambios Temporales: chcon</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext">5.7.2. Cambios Persistentes: semanage fcontext</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types">5.8. Los tipos file_t y default_t</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems">5.9. Montaje de Sistemas de Archivos</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Mounting_File_Systems-Context_Mounts">5.9.1. Montajes de Contexto</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Mounting_File_Systems-Changing_the_Default_Context">5.9.2. Cambio del Contexto Predeterminado</a></span></dt><
 dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Mounting_File_Systems-Mounting_an_NFS_File_System">5.9.3. Montando un Sistema de Archivos NFS</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Mounting_File_Systems-Multiple_NFS_Mounts">5.9.4. Montajes NFS Múltiples</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Mounting_File_Systems-Making_Context_Mounts_Persistent">5.9.5. Haciendo Persistente los Contextos de Montajes</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_">5.10. Mantención de las Etiquetas de SELinux</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Copying_Files_and_Directories">5.10.1. Copia de Directorios y Archivos</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Moving
 _Files_and_Directories">5.10.2. Movimiento de Archivos y Directorios</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context">5.10.3. Chequeando el Contexto SELinux Predeterminado</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_tar">5.10.4. Archivando archivos con tar</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_star">5.10.5. Archivando archivos con tar</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#chap-Security-Enhanced_Linux-Confining_Users">6. Confinando a los Usuarios</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Confining_Users-Linux_and_SELinux_User_Mappings">6.1. Linux y los Mapeos de Usuarios de SELinux</a></span></dt><dt><span class="section"><a href=
 "#sect-Security-Enhanced_Linux-Confining_Users-Confining_New_Linux_Users_useradd">6.2. Confinando Usuarios Nuevos de Linux: useradd</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Confining_Users-Confining_Existing_Linux_Users_semanage_login">6.3. Confinando Usuarios Linux Existentes: semanage login</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Confining_Users-Changing_the_Default_Mapping">6.4. Cambiando el Mapeo Predeterminado</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Confining_Users-xguest_Kiosk_Mode">6.5. xguest: Modo Kiosk</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications">6.6. Booleanos para que los Usuarios Ejecuten Aplicaciones</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Security-Enhanced_Linux-Troubleshooting">7. Solución a Problemas</a></span></dt><dd><dl
 ><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Troubleshooting-What_Happens_when_Access_is_Denied">7.1. Qué pasa cuando el Acceso es Denegado</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems">7.2. Tres Principales Causas de Problemas</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Labeling_Problems">7.2.1. Problemas de Etiquetados</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running">7.2.2. ¿Cómo se Ejecutan los Servicios Confinados?</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Evolving_Rules_and_Broken_Applications">7.2.3. Evolucionando las Reglas y las Aplicaciones Rotas</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security-Enhanced_Linu
 x-Troubleshooting-Fixing_Problems">7.3. Corrección de Problemas</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Linux_Permissions">7.3.1. Permisos de Linux</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Possible_Causes_of_Silent_Denials">7.3.2. Posibles Causas de las Negaciones Silenciosas</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services">7.3.3. Páginas de Manual para Servicios</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains">7.3.4. Dominios Permisivos</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Searching_For_and_Viewing_Denials">7.3.5. Búsqueda y Revisión de Negaciones</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messa
 ges">7.3.6. Mensajes Crudos de Auditoría</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages">7.3.7. Mensajes sealert</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow">7.3.8. Permitiendo el Acceso: audit2allow</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#chap-Security-Enhanced_Linux-Further_Information">8. Información Adicional</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Further_Information-Contributors">8.1. Contribuyentes</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Further_Information-Other_Resources">8.2. Otros Recursos</a></span></dt></dl></dd><dt><span class="appendix"><a href="#appe-Security-Enhanced_Linux-Revision_History">A. Historia de Revisiones</a></span></dt></dl></div><div xml:lang="es-ES" class="preface" title="Prefacio" 
 id="pref-Security-Enhanced_Linux-Preface" lang="es-ES"><div class="titlepage"><div><div><h1 class="title">Prefacio</h1></div></div></div><div class="para">
-		La Guía del Usuario de SELinux de Fedora 13 es para gente sin o con mínima experiencia con SELinux. Aunque la experiencia de administración de sistema no es necesario, el contenido de esta guía se escribe para tareas de administración del sistema. Esta guía provee una introducción a los conceptos fundamentales y aplicaciones prácticas de SELinux. Después de leer esta guía debe tener un entendimiento intermedio de SELinux.
+			The SELinux User Guide assists users and administrators in managing and using Security-Enhanced <span class="trademark">Linux</span>®.
+		</div></div></div></div><hr /></div><div class="toc"><dl><dt><span class="preface"><a href="#pref-Security-Enhanced_Linux-Preface">Prefacio</a></span></dt><dd><dl><dt><span class="section"><a href="#id812153">1. Convenciones del Documento</a></span></dt><dd><dl><dt><span class="section"><a href="#id793802">1.1. Convenciones Tipográficas</a></span></dt><dt><span class="section"><a href="#id861219">1.2. Convenciones del documento</a></span></dt><dt><span class="section"><a href="#id811740">1.3. Notas y Advertencias</a></span></dt></dl></dd><dt><span class="section"><a href="#id842097">2. ¡Necesitamos sus comentarios!</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Security-Enhanced_Linux-Trademark_Information">1. Información de Marca Comercial</a></span></dt><dd><dl><dt><span class="section"><a href="#chap-Security-Enhanced_Linux-Trademark_Information-Source_Code">1.1. Source Code</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Security
 -Enhanced_Linux-Introduction">2. Introducción</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Introduction-Benefits_of_running_SELinux">2.1. Beneficios de usar SELinux</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Introduction-Examples">2.2. Ejemplos</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture">2.3. Arquitectura de SELinux</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Introduction-SELinux_on_Other_Operating_Systems">2.4. SELinux en otros Sistemas Operativos</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Security-Enhanced_Linux-SELinux_Contexts">3. Contextos de SELinux</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-SELinux_Contexts-Domain_Transitions">3.1. Transiciones de Dominios</a></span></dt><dt><span class="section"><a href="#sect-Secur
 ity-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Processes">3.2. Contextos de SELinux para los Procesos</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Users">3.3. Contextos de SELinux para los Usuarios</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Security-Enhanced_Linux-Targeted_Policy">4. Política Destinado</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Targeted_Policy-Confined_Processes">4.1. Procesos Confinados</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Targeted_Policy-Unconfined_Processes">4.2. Procesos no Confinados</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users">4.3. Usuarios Confinados y no Confinados</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Security-Enhanced_Linux-Working_with_SELinux">5. 
 Trabajando con SELinux</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Packages">5.1. Paquetes de SELinux</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used">5.2. Qué Archivo Log se usa</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Main_Configuration_File">5.3. Archivo de Configuración Principal</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux">5.4. Habilitando y Deshabilitando SELinux</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Enabling_SELinux">5.4.1. Habilitando SELinux</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux">5.4.2. Deshabilitando SE
 Linux</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes">5.5. Modos de SELinux</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans">5.6. Booleanos</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Booleans-Listing_Booleans">5.6.1. Listando los Booleanos</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Booleans-Configuring_Booleans">5.6.2. Configurando los Booleanos</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS">5.6.3. Booleanos para NFS y CIFS</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files">5.7. Contextos de SELinux - Etiquetado de Archivos</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-En
 hanced_Linux-SELinux_Contexts_Labeling_Files-Temporary_Changes_chcon">5.7.1. Cambios Temporales: chcon</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext">5.7.2. Cambios Persistentes: semanage fcontext</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types">5.8. Los tipos file_t y default_t</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems">5.9. Montaje de Sistemas de Archivos</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Mounting_File_Systems-Context_Mounts">5.9.1. Montajes de Contexto</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Mounting_File_Systems-Changing_the_Default_Context">5.9.2. Cambio del Contexto Predeterminado</a></span></dt><dt><spa
 n class="section"><a href="#sect-Security-Enhanced_Linux-Mounting_File_Systems-Mounting_an_NFS_File_System">5.9.3. Montando un Sistema de Archivos NFS</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Mounting_File_Systems-Multiple_NFS_Mounts">5.9.4. Montajes NFS Múltiples</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Mounting_File_Systems-Making_Context_Mounts_Persistent">5.9.5. Haciendo Persistente los Contextos de Montajes</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_">5.10. Mantención de las Etiquetas de SELinux</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Copying_Files_and_Directories">5.10.1. Copia de Directorios y Archivos</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Moving_Files_
 and_Directories">5.10.2. Movimiento de Archivos y Directorios</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context">5.10.3. Chequeando el Contexto SELinux Predeterminado</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_tar">5.10.4. Archivando archivos con tar</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_star">5.10.5. Archivando archivos con tar</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#chap-Security-Enhanced_Linux-Confining_Users">6. Confinando a los Usuarios</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Confining_Users-Linux_and_SELinux_User_Mappings">6.1. Linux y los Mapeos de Usuarios de SELinux</a></span></dt><dt><span class="section"><a href="#sect-
 Security-Enhanced_Linux-Confining_Users-Confining_New_Linux_Users_useradd">6.2. Confinando Usuarios Nuevos de Linux: useradd</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Confining_Users-Confining_Existing_Linux_Users_semanage_login">6.3. Confinando Usuarios Linux Existentes: semanage login</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Confining_Users-Changing_the_Default_Mapping">6.4. Cambiando el Mapeo Predeterminado</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Confining_Users-xguest_Kiosk_Mode">6.5. xguest: Modo Kiosk</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications">6.6. Booleanos para que los Usuarios Ejecuten Aplicaciones</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Security-Enhanced_Linux-Troubleshooting">7. Solución a Problemas</a></span></dt><dd><dl><dt><s
 pan class="section"><a href="#sect-Security-Enhanced_Linux-Troubleshooting-What_Happens_when_Access_is_Denied">7.1. Qué pasa cuando el Acceso es Denegado</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems">7.2. Tres Principales Causas de Problemas</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Labeling_Problems">7.2.1. Problemas de Etiquetados</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running">7.2.2. ¿Cómo se Ejecutan los Servicios Confinados?</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Evolving_Rules_and_Broken_Applications">7.2.3. Evolucionando las Reglas y las Aplicaciones Rotas</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Troub
 leshooting-Fixing_Problems">7.3. Corrección de Problemas</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Linux_Permissions">7.3.1. Permisos de Linux</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Possible_Causes_of_Silent_Denials">7.3.2. Posibles Causas de las Negaciones Silenciosas</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services">7.3.3. Páginas de Manual para Servicios</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains">7.3.4. Dominios Permisivos</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Searching_For_and_Viewing_Denials">7.3.5. Búsqueda y Revisión de Negaciones</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages">7.
 3.6. Raw Audit Messages</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages">7.3.7. Mensajes sealert</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow">7.3.8. Permitiendo el Acceso: audit2allow</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#chap-Security-Enhanced_Linux-Further_Information">8. Información Adicional</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Further_Information-Contributors">8.1. Contributors</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Further_Information-Other_Resources">8.2. Other Resources</a></span></dt></dl></dd><dt><span class="appendix"><a href="#appe-Security-Enhanced_Linux-Revision_History">A. Revision History</a></span></dt></dl></div><div xml:lang="es-ES" class="preface" title="Prefacio" id="pref-Security-Enhance
 d_Linux-Preface" lang="es-ES"><div class="titlepage"><div><div><h1 class="title">Prefacio</h1></div></div></div><div class="para">
+		The Fedora 13 SELinux User Guide is for people with minimal or no experience with SELinux. Although system administration experience is not necessary, content in this guide is written for system administration tasks. This guide provides an introduction to fundamental concepts and practical applications of SELinux. After reading this guide you should have an intermediate understanding of SELinux.
 	</div><div class="para">
 		Gracias a todos los que nos alentaron, ofrecieron ayuda y lo probaron - la ayuda es muy apreciada. Agradecimientos muy especiales a:
 	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
 				Dominick Grift, Stephen Smalley y Russell Coker por sus contribuciones, ayuda y paciencia.
 			</div></li><li class="listitem"><div class="para">
-				Karsten Wade por su ayuda, al agregar un componente para esta guía en el <a href="https://bugzilla.redhat.com/">Bugzilla de Red Hat</a> y resolver el alojamiento web en <a href="http://docs.fedoraproject.org/">http://docs.fedoraproject.org/</a>.
+				Karsten Wade for his help, adding a component for this guide to <a href="https://bugzilla.redhat.com/"> Red Hat Bugzilla</a>, and sorting out web hosting on <a href="http://docs.fedoraproject.org/">http://docs.fedoraproject.org/</a>.
 			</div></li><li class="listitem"><div class="para">
 				Al <a href="http://fedoraproject.org/wiki/Infrastructure">Equipo de Infraestructura de Fedora</a> por proveer el alojamiento.
 			</div></li><li class="listitem"><div class="para">
 				Jens-Ulrik Petersen por asegurar que la oficina de Brisbane de Red Hat tenga espejos de Fedora actualizados.
-			</div></li></ul></div><div xml:lang="es-ES" class="section" title="1. Convenciones del Documento" lang="es-ES"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id1113856">1. Convenciones del Documento</h2></div></div></div><div class="para">
+			</div></li></ul></div><div xml:lang="es-ES" class="section" title="1. Convenciones del Documento" lang="es-ES"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id812153">1. Convenciones del Documento</h2></div></div></div><div class="para">
 		Este manual utiliza varias convenciones para resaltar algunas palabras y frases y llamar la atención sobre ciertas partes específicas de información.
 	</div><div class="para">
 		En ediciones PDF y de papel, este manual utiliza tipos de letra procedentes de <a href="https://fedorahosted.org/liberation-fonts/">Liberation Fonts</a>. Liberation Fonts también se utilizan en ediciones de HTML si están instalados en su sistema. Si no, se muestran tipografías alternativas pero equivalentes. Nota: Red Hat Enterprise Linux 5 y siguientes incluyen Liberation Fonts predeterminadas.
-	</div><div class="section" title="1.1. Convenciones Tipográficas"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id2062524">1.1. Convenciones Tipográficas</h3></div></div></div><div class="para">
+	</div><div class="section" title="1.1. Convenciones Tipográficas"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id793802">1.1. Convenciones Tipográficas</h3></div></div></div><div class="para">
 			Se utilizan cuatro convenciones tipográficas para llamar la atención sobre palabras o frases específicas. Dichas convenciones y las circunstancias en que se aplican son las siguientes:
 		</div><div class="para">
 			<code class="literal">Negrita monoespaciado</code>
@@ -87,7 +87,7 @@
 			Aparte del uso estándar para presentar el título de un trabajo, las itálicas denotan el primer uso de un término nuevo e importante. Por ejemplo:
 		</div><div class="blockquote"><blockquote class="blockquote"><div class="para">
 				Publican es un sistema de publicación de <em class="firstterm">DocBook</em>.
-			</div></blockquote></div></div><div class="section" title="1.2. Convenciones del documento"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id2082376">1.2. Convenciones del documento</h3></div></div></div><div class="para">
+			</div></blockquote></div></div><div class="section" title="1.2. Convenciones del documento"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id861219">1.2. Convenciones del documento</h3></div></div></div><div class="para">
 			Los mensajes de salida de la terminal o fragmentos de código fuente se distinguen visualmente del texto circundante.
 		</div><div class="para">
 			Los mensajes de salida enviados a una terminal se muestran en <code class="computeroutput">romano monoespaciado</code> y se presentan así:
@@ -116,7 +116,7 @@ books_tests  Desktop1  downloads      images  notes  scripts  svgs
    }
 }
 
-</pre></div><div class="section" title="1.3. Notas y Advertencias"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id1073400">1.3. Notas y Advertencias</h3></div></div></div><div class="para">
+</pre></div><div class="section" title="1.3. Notas y Advertencias"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id811740">1.3. Notas y Advertencias</h3></div></div></div><div class="para">
 			Finalmente, utilizamos tres estilos visuales para llamar la atención sobre la información que de otro modo se podría pasar por alto.
 		</div><div class="note"><h2>Nota</h2><div class="para">
 				Una nota es una sugerencia, atajo o enfoque alternativo para una tarea determinada. Ignorar una nota no debería tener consecuencias negativas, pero podría perderse de algunos trucos que pueden facilitarle las cosas.
@@ -124,13 +124,13 @@ books_tests  Desktop1  downloads      images  notes  scripts  svgs
 				Important boxes detail things that are easily missed: configuration changes that only apply to the current session, or services that need restarting before an update will apply. Ignoring a box labeled 'Important' won't cause data loss but may cause irritation and frustration.
 			</div></div><div class="warning"><h2>Advertencia</h2><div class="para">
 				Las advertencias no deben ignorarse. Ignorarlas muy probablemente ocasionará pérdida de datos.
-			</div></div></div></div><div xml:lang="es-ES" class="section" title="2. ¡Necesitamos sus comentarios!" lang="es-ES"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id867204">2. ¡Necesitamos sus comentarios!</h2></div></div></div><a id="id867216" class="indexterm"></a><div class="para">
+			</div></div></div></div><div xml:lang="es-ES" class="section" title="2. ¡Necesitamos sus comentarios!" lang="es-ES"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id842097">2. ¡Necesitamos sus comentarios!</h2></div></div></div><a id="id861022" class="indexterm"></a><div class="para">
 		Si encuentra un error tipográfico en este manual o si sabe de alguna manera de mejorarlo, nos gustaría escuchar sus sugerencias. Por favor complete un reporte en Bugzilla: <a href="http://bugzilla.redhat.com/bugzilla/">http://bugzilla.redhat.com/bugzilla/</a> usando el producto <span class="application"><strong>Fedora Documentation</strong></span>.
 	</div><div class="para">
 		Cuando envíe un reporte de error no olvide mencionar el identificador del manual: <em class="citetitle">selinux-user-guide</em>
 	</div><div class="para">
 		Si tiene una sugerencia para mejorar la documentación, intente ser tan específico como sea posible cuando describa su sugerencia. Si ha encontrado un error, por favor incluya el número de sección y parte del texto que rodea el error para que podamos encontrarlo más fácilmente.
-	</div></div></div><div xml:lang="es-ES" class="chapter" title="Capítulo 1. Información de Marca Comercial" id="chap-Security-Enhanced_Linux-Trademark_Information" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 1. Información de Marca Comercial</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#chap-Security-Enhanced_Linux-Trademark_Information-Source_Code">1.1. Código Fuente</a></span></dt></dl></div><div class="para">
+	</div></div></div><div xml:lang="es-ES" class="chapter" title="Capítulo 1. Información de Marca Comercial" id="chap-Security-Enhanced_Linux-Trademark_Information" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 1. Información de Marca Comercial</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#chap-Security-Enhanced_Linux-Trademark_Information-Source_Code">1.1. Source Code</a></span></dt></dl></div><div class="para">
 		<span class="trademark">Linux</span>® es una marca comercial registrada de Linus Torvalds en los EEUU y en otros países.
 	</div><div class="para">
 		UNIX es una marca comercial registrada de El Grupo Abierto.
@@ -141,32 +141,32 @@ books_tests  Desktop1  downloads      images  notes  scripts  svgs
 	</div><div class="para">
 		MySQL es una marca comercial o marca comercial registrada de MySQL AB en los EEUU y en otros países.
 	</div><div class="para">
-		Otros productos mencionados pueden ser marcas comerciales de sus respectivas corporaciones.
-	</div><div class="section" title="1.1. Código Fuente" id="chap-Security-Enhanced_Linux-Trademark_Information-Source_Code"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">1.1. Código Fuente</h2></div></div></div><div class="para">
-			El código fuente XML de está guía está disponible en <a href="http://svn.fedorahosted.org/svn/selinuxguide/">http://svn.fedorahosted.org/svn/selinuxguide/</a>
+		Other products mentioned may be trademarks of their respective corporations.
+	</div><div class="section" title="1.1. Source Code" id="chap-Security-Enhanced_Linux-Trademark_Information-Source_Code"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">1.1. Source Code</h2></div></div></div><div class="para">
+			The XML source for this guide is available at <a href="http://svn.fedorahosted.org/svn/selinuxguide/">http://svn.fedorahosted.org/svn/selinuxguide/</a>
 		</div></div></div><div xml:lang="es-ES" class="chapter" title="Capítulo 2. Introducción" id="chap-Security-Enhanced_Linux-Introduction" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 2. Introducción</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Introduction-Benefits_of_running_SELinux">2.1. Beneficios de usar SELinux</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Introduction-Examples">2.2. Ejemplos</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture">2.3. Arquitectura de SELinux</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Introduction-SELinux_on_Other_Operating_Systems">2.4. SELinux en otros Sistemas Operativos</a></span></dt></dl></div><div class="para">
-		Linux con Seguridad Mejorada (SELinux) es una implementación de un mecanismo de <em class="firstterm">control de acceso obligatorio</em> en el kernel de Linux, para chequear si las operaciones son permitidas después de los <em class="firstterm">controles de acceso discrecionales</em> estándares.
+		Security-Enhanced Linux (SELinux) is an implementation of a <em class="firstterm">mandatory access control</em> mechanism in the Linux kernel, checking for allowed operations after standard <em class="firstterm">discretionary access controls</em> are checked. It was created by the National Security Agency and can enforce rules on files and processes in a Linux system, and on their actions, based on defined policy.
 	</div><div class="para">
-		Los Archivos, tales como directorios y dispositivos, se llaman objetos. Los procesos, tal como un comando que ejecuta el usuario o la aplicación <span class="trademark">Mozilla</span>®<span class="trademark"> Firefox</span>®, se llaman sujetos. La mayoría de los sistemas oeprativos usan un sistema de Control de Acceso Discrecional (DAC), que controla cómo interactúan los sujetos con los objetos, y cómo los sujetos interactuan entre sí. En sistemas operativos que usan DAC, los usuarios controlan los permisos de archivos (objetos) de los que son dueños. Por ejemplo, en sistemas operativos <span class="trademark">Linux</span>®, los usuarios pueden hacer sus directorios legibles para el resto del mundo, dando a los usuarios y procesos (sujetos) acceso a información potencialmente sensible, sin protección adicional sobre esta acción indeseada.
+		When using SELinux, files, including directories and devices, are referred to as objects. Processes, such as a user running a command or the <span class="trademark">Mozilla</span>®<span class="trademark"> Firefox</span>® application, are referred to as subjects. Most operating systems use a Discretionary Access Control (DAC) system that controls how subjects interact with objects, and how subjects interact with each other. On operating systems using DAC, users control the permissions of files (objects) that they own. For example, on <span class="trademark">Linux</span>® operating systems, users could make their home directories world-readable, giving users and processes (subjects) access to potentially sensitive information, with no further protection over this unwanted action.
 	</div><div class="para">
-		Relying on DAC mechanisms alone is fundamentally inadequate for strong system security. DAC access decisions are only based on user identity and ownership, ignoring other security-relevant information such as the role of the user, the function and trustworthiness of the program, and the sensitivity and integrity of the data. Each user has complete discretion over their files, making it impossible to enforce a system-wide security policy. Furthermore, every program run by a user inherits all of the permissions granted to the user and is free to change access to the user's files, so no protection is provided against malicious software. Many system services and privileged programs must run with coarse-grained privileges that far exceed their requirements, so that a flaw in any one of these programs could be exploited to obtain further system access.<sup>[<a id="id2090071" href="#ftn.id2090071" class="footnote">1</a>]</sup>
+		Relying on DAC mechanisms alone is fundamentally inadequate for strong system security. DAC access decisions are only based on user identity and ownership, ignoring other security-relevant information such as the role of the user, the function and trustworthiness of the program, and the sensitivity and integrity of the data. Each user has complete discretion over their files, making it impossible to enforce a system-wide security policy. Furthermore, every program run by a user inherits all of the permissions granted to the user and is free to change access to the user's files, so no protection is provided against malicious software. Many system services and privileged programs must run with coarse-grained privileges that far exceed their requirements, so that a flaw in any one of these programs could be exploited to obtain further system access.<sup>[<a id="id636508" href="#ftn.id636508" class="footnote">1</a>]</sup>
 	</div><div class="para">
-		El siguiente es un ejemplo de permisos usados en sistemas operativos Linux que no corren el Linux con Seguridad Mejorada (SELinux). Los permisos en estos ejemplos pueden diferir de su sistema. Use el comando <code class="command">ls -l</code> para ver los permisos de archivos:
+		The following is an example of permissions used on Linux operating systems that do not run Security-Enhanced Linux (SELinux). The permissions and output in these examples may differ from your system. Use the <code class="command">ls -l</code> command to view file permissions:
 	</div><pre class="screen">$ ls -l file1
--rw-rw-r--. 1 user1 group1 0 May 11 10:46 file1
+-rwxrw-r-- 1 user1 group1 0 2009-08-30 11:03 file1
 
 </pre><div class="para">
-		The first three permission bits, <code class="computeroutput">rw</code>, control the access the Linux <code class="computeroutput">user1</code> user (in this case, the owner) has to <code class="filename">file1</code>. The next three permission bits, <code class="computeroutput">rw-</code>, control the access the Linux <code class="computeroutput">group1</code> group has to <code class="filename">file1</code>. The last three permission bits, <code class="computeroutput">r--</code>, control the access everyone else has to <code class="filename">file1</code>, which includes all users and processes.
+		Los primeros tres bits de permisos, <code class="computeroutput">rwx</code>, controlan el acceso que el usuario Linux <code class="computeroutput">usuario1</code> (en este caso, el dueño) tiene para el <code class="filename">archivo1</code>. Los siguientes tres bits de permisos, <code class="computeroutput">rw-</code>, controlan el acceso que el grupo Linux <code class="computeroutput">grupo1</code> tiene para el <code class="filename">archivo1</code>. Los últimos tres bits de permisos, <code class="computeroutput">r--</code>, controlan el acceso que todo el mundo tiene para el <code class="filename">archivo1</code>, que incluyen a todos los usuarios y procesos.
 	</div><div class="para">
-		Security-Enhanced Linux (SELinux) adds Mandatory Access Control (MAC) to the Linux kernel, and is enabled by default in Fedora. A general purpose MAC architecture needs the ability to enforce an administratively-set security policy over all processes and files in the system, basing decisions on labels containing a variety of security-relevant information. When properly implemented, it enables a system to adequately defend itself and offers critical support for application security by protecting against the tampering with, and bypassing of, secured applications. MAC provides strong separation of applications that permits the safe execution of untrustworthy applications. Its ability to limit the privileges associated with executing processes limits the scope of potential damage that can result from the exploitation of vulnerabilities in applications and system services. MAC enables information to be protected from legitimate users with limited authorization as well as from a
 uthorized users who have unwittingly executed malicious applications.<sup>[<a id="id973716" href="#ftn.id973716" class="footnote">2</a>]</sup>
+		Security-Enhanced Linux (SELinux) adds Mandatory Access Control (MAC) to the Linux kernel, and is enabled by default in Fedora. A general purpose MAC architecture needs the ability to enforce an administratively-set security policy over all processes and files in the system, basing decisions on labels containing a variety of security-relevant information. When properly implemented, it enables a system to adequately defend itself and offers critical support for application security by protecting against the tampering with, and bypassing of, secured applications. MAC provides strong separation of applications that permits the safe execution of untrustworthy applications. Its ability to limit the privileges associated with executing processes limits the scope of potential damage that can result from the exploitation of vulnerabilities in applications and system services. MAC enables information to be protected from legitimate users with limited authorization as well as from a
 uthorized users who have unwittingly executed malicious applications.<sup>[<a id="id705006" href="#ftn.id705006" class="footnote">2</a>]</sup>
 	</div><div class="para">
-		El siguiente es un ejemplo de las etiquetas que contienen información de seguridad relevante que se usa en los procesos, usuarios Linux y archivos, en sistemas operativos Linux que corren SELinux. Esta información se llama contexto de SELinux y se visualiza usando el comando <code class="command">ls -Z</code>:
+		The following is an example of the labels containing security-relevant information that are used on processes, Linux users, and files, on Linux operating systems that run SELinux. This information is called the SELinux <span class="emphasis"><em>context</em></span>, and is viewed using the <code class="command">ls -Z</code> command:
 	</div><pre class="screen">$ ls -Z file1
--rw-rw-r--. user1 group1 unconfined_u:object_r:user_home_t:s0 file1
+-rwxrw-r--  user1 group1 unconfined_u:object_r:user_home_t:s0      file1
 
 </pre><div class="para">
-		En este ejemplo, SELinux provee un usuario (<code class="computeroutput">unconfined_u</code>), un rol (<code class="computeroutput">object_r</code>), un tipo (<code class="computeroutput">user_home_t</code>), y un nivel (<code class="computeroutput">s0</code>). Esta información se usa para tomar decisiones sobre el control de acceso. Con DAC, el acceso se controla basado sólo en los IDs de usuarios y grupos de Linux. Las reglas de políticas de SELinux se chequean <span class="emphasis"><em>después</em></span> de las reglas DAC. Las reglas de políticas de SELInux no se usan si las reglas DAC niegan el acceso al principio.
-	</div><div class="formalpara"><h5 class="formalpara">Linux y los Usuarios SELinux</h5>
+		In this example, SELinux provides a user (<code class="computeroutput">unconfined_u</code>), a role (<code class="computeroutput">object_r</code>), a type (<code class="computeroutput">user_home_t</code>), and a level (<code class="computeroutput">s0</code>). This information is used to make access control decisions. With DAC, access is controlled based only on Linux user and group IDs. It is important to remember that SELinux policy rules are checked <span class="emphasis"><em>after</em></span> DAC rules. SELinux policy rules are not used if DAC rules deny access first.
+	</div><div class="formalpara" id="form-Security-Enhanced_Linux-Introduction-Linux_and_SELinux_Users"><h5 class="formalpara">Linux y los Usuarios SELinux</h5>
 			On Linux operating systems that run SELinux, there are Linux users as well as SELinux users. SELinux users are part of SELinux policy. Linux users are mapped to SELinux users. To avoid confusion, this guide uses "Linux user" and "SELinux user" to differentiate between the two.
 		</div><div class="section" title="2.1. Beneficios de usar SELinux" id="sect-Security-Enhanced_Linux-Introduction-Benefits_of_running_SELinux"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.1. Beneficios de usar SELinux</h2></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
 					Todos los procesos y archivos se etiquetan con un tipo. Un tipo define un dominio para los procesos y un tipo para los archivos. Los procesos se separan entre sí corriéndolos en sus propios dominios, y las reglas de políticas de SELinux define cómo interactúan los procesos con los archivos, así como la forma en que interactúan entre sí. El acceso sólo se permite si existe una regla de política de SELinux que específicamente lo permita.
@@ -175,9 +175,7 @@ books_tests  Desktop1  downloads      images  notes  scripts  svgs
 				</div></li><li class="listitem"><div class="para">
 					La política de SELinux se define administrativamente, obligando a todo el sistema, y no se pone a discreción del usuario.
 				</div></li><li class="listitem"><div class="para">
-					Vulnerabilidad reducida para ataques de escalamiento de privilegios. Un ejemplo: dado que los procesos corren en dominios, y son por lo tanto separados entre si, y las reglas de la política de SELinux definen cómo los procesos acceden a los archivos y a otros procesos, si un proceso queda comprometido, el atacante sólo tiene acceso a las funciones normales de ese proceso, y a archivos a los que el proceso tiene configurado que puede acceder. Por ejemplo, si el Servidor HTTP Apache es comprometido, un atacante no puede usar el proceso para leer archivos en los directorios home de los usuarios, a menos que una regla específica de la política de SELinux haya sido agregada o configurada para permitir tal acceso.
-				</div></li><li class="listitem"><div class="para">
-					Confined services. SELinux ships with the ability to confine services and daemons so that they are more predictable and are only allowed access that is required for their normal operation.
+					Reduced vulnerability to privilege escalation attacks. One example: since processes run in domains, and are therefore separated from each other, and because SELinux policy rules define how processes access files and other processes, if a process is compromised, the attacker only has access to the normal functions of that process, and to files the process has been configured to have access to. For example, if the Apache HTTP Server is compromised, an attacker can not use that process to read files in user home directories, unless a specific SELinux policy rule was added or configured to allow such access.
 				</div></li><li class="listitem"><div class="para">
 					Se linux se puede usar para asegurar la confidencialidad e integridad de los datos, así como proteger los procesos de entradas no confiables.
 				</div></li></ul></div><div class="para">
@@ -189,21 +187,21 @@ books_tests  Desktop1  downloads      images  notes  scripts  svgs
 				</div></li><li class="listitem"><div class="para">
 					una solución todo en uno.
 				</div></li></ul></div><div class="para">
-			SELinux is designed to enhance existing security solutions, not replace them. Even when running SELinux, it is important to continue to follow good security practices, such as keeping software up-to-date, using hard-to-guess passwords, firewalls, and so on.
+			SELinux está diseñado para mejorar las soluciones de seguridad existentes, no reemplazarlas. Aún cuando corra SELinux, siga las buenas prácticas de seguridad, tales como mantener el software actualizado, usar contraseñas difíciles de adivinar, cortafuegos y demás.
 		</div></div><div class="section" title="2.2. Ejemplos" id="sect-Security-Enhanced_Linux-Introduction-Examples"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.2. Ejemplos</h2></div></div></div><div class="para">
 			Los siguientes ejemplos demuestran cómo SELinux aumenta la seguridad:
 		</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-					The default action is deny. If a specific SELinux policy rule does not exist to allow access, such as for a process opening a file, access is denied.
+					The default action is deny. If an SELinux policy rule does not exist to allow access, such as for a process opening a file, access is denied.
 				</div></li><li class="listitem"><div class="para">
-					SELinux puede confinar a usuarios Linux. Existe un número de usuarios SELinux confinados. Los usuarios Linux se pueden mapear a usuarios SELinux para sacar ventaja de los usuarios SELinux confinados. Por ejemplo, mapear un usario Linux al usuario SELinux user_u, resulta en un usuario Linux que no puede ejecutar (a menos que se configure de otra forma) aplicaciones con el ID del usuario (setuid), tales como <code class="command">sudo</code> y <code class="command">su</code>, así como previene la ejecución de archivos y aplicaciones en sus directorios de inicio (home)- si se configura, esto evita que los usuarios ejecuten archivos maliciosos desde sus directorios de inicio.
+					SELinux can confine Linux users. A number of confined SELinux users exist in SELinux policy. Linux users can be mapped to confined SELinux users to take advantage of the security rules and mechanisms applied to them. For example, mapping a Linux user to the SELinux user_u user, results in a Linux user that is not able to run (unless configured otherwise) set user ID (setuid) applications, such as <code class="command">sudo</code> and <code class="command">su</code>, as well as preventing them from executing files and applications in their home directory - if configured, this prevents users from executing malicious files from their home directories.
 				</div></li><li class="listitem"><div class="para">
-					Se usa separación de procesos. Los procesos que corren en sus propios dominios, previenen que estos accedan a archivos usados por otros procesos, así como el acceso a otros procesos. Por ejemplo, cuando se ejecuta SELinux, a menos que se configure de otra forma, un atacante no puede comprometer un servidor Samba, y luego usar ese servidor Samba para leer y escribir archivos usados por otros procesos, tales como las bases de datos usadas por <span class="trademark">MySQL</span>®.
+					Process separation is used. Processes run in their own domains, preventing processes from accessing files used by other processes, as well as preventing processes from accessing other processes. For example, when running SELinux, unless otherwise configured, an attacker can not compromise a Samba server, and then use that Samba server as an attack vector to read and write to files used by other processes, such as databases used by <span class="trademark">MySQL</span>®.
 				</div></li><li class="listitem"><div class="para">
-					SELinux helps limit the damage made by configuration mistakes. <a href="http://en.wikipedia.org/wiki/Domain_Name_System">Domain Name System (DNS)</a> servers often replicate information between each other in what is known as a zone transfer. Attackers can use zone transfers to update DNS servers with false information. When running the <a href="https://www.isc.org/software/bind">Berkeley Internet Name Daemon (BIND)</a> as a DNS server in Fedora, even if an administrator forgets to limit which servers can perform a zone transfer, the default SELinux policy prevents zone files <sup>[<a id="id884662" href="#ftn.id884662" class="footnote">3</a>]</sup> from being updated via zone transfers, by the BIND <code class="systemitem">named</code> daemon itself, and by other processes.
+					SELinux helps limit the damage made by configuration mistakes. <a href="http://en.wikipedia.org/wiki/Domain_Name_System">Domain Name System (DNS)</a> servers often replicate information between each other in what is known as a zone transfer. Attackers can use zone transfers to update DNS servers with false information. When running the <a href="https://www.isc.org/software/bind">Berkeley Internet Name Domain (BIND)</a> as a DNS server in Fedora, even if an administrator forgets to limit which servers can perform a zone transfer, the default SELinux policy prevents zone files <sup>[<a id="id715600" href="#ftn.id715600" class="footnote">3</a>]</sup> from being updated via zone transfers, by the BIND <code class="systemitem">named</code> daemon itself, and by other processes.
 				</div></li><li class="listitem"><div class="para">
-					Refer to the <a href="http://www.redhatmagazine.com/"><span class="trademark">Red Hat</span>® Magazine</a> article, <a href="http://www.redhatmagazine.com/2008/02/26/risk-report-three-years-of-red-hat-enterprise-linux-4/">Risk report: Three years of Red Hat Enterprise Linux 4</a><sup>[<a id="id884702" href="#ftn.id884702" class="footnote">4</a>]</sup>, for exploits that were restricted due to the default SELinux targeted policy in <span class="trademark">Red Hat</span>® Enterprise <span class="trademark">Linux</span>® 4.
+					Refer to the <a href="http://www.redhatmagazine.com/"><span class="trademark">Red Hat</span>® Magazine</a> article, <a href="http://www.redhatmagazine.com/2008/02/26/risk-report-three-years-of-red-hat-enterprise-linux-4/">Risk report: Three years of Red Hat Enterprise Linux 4</a><sup>[<a id="id715635" href="#ftn.id715635" class="footnote">4</a>]</sup>, for exploits that were restricted due to the default SELinux targeted policy in <span class="trademark">Red Hat</span>® Enterprise <span class="trademark">Linux</span>® 4.
 				</div></li><li class="listitem"><div class="para">
-					Refer to the <a href="http://www.linuxworld.com">LinuxWorld.com</a> article, <a href="http://www.linuxworld.com/news/2008/022408-selinux.html?page=1">A seatbelt for server software: SELinux blocks real-world exploits</a><sup>[<a id="id2075446" href="#ftn.id2075446" class="footnote">5</a>]</sup>, for background information about SELinux, and information about various exploits that SELinux has prevented.
+					Refer to the <a href="http://www.linuxworld.com">LinuxWorld.com</a> article, <a href="http://www.linuxworld.com/news/2008/022408-selinux.html?page=1">A seatbelt for server software: SELinux blocks real-world exploits</a><sup>[<a id="id715678" href="#ftn.id715678" class="footnote">5</a>]</sup>, for background information about SELinux, and information about various exploits that SELinux has prevented.
 				</div></li><li class="listitem"><div class="para">
 					Refer to James Morris's <a href="http://james-morris.livejournal.com/25421.html">SELinux mitigates remote root vulnerability in OpenPegasus</a> blog post for information about an exploit in <a href="http://www.openpegasus.org/">OpenPegasus</a> that was mitigated by SELinux as shipped with Red Hat Enterprise Linux 4 and 5.
 				</div></li></ul></div><div class="para">
@@ -211,11 +209,11 @@ books_tests  Desktop1  downloads      images  notes  scripts  svgs
 		</div></div><div class="section" title="2.3. Arquitectura de SELinux" id="sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.3. Arquitectura de SELinux</h2></div></div></div><div class="para">
 			SELinux es un módulo de seguridad de Linux que se construye dentro del kernel de Linux. SELinux se maneja por reglas de políticas cargables. Cuando un acceso de seguridad relevante se lleva a cabo, tal como un proceso que trata de abrir un archivo, la operación es interceptada por SELinux en el kernel. Si una regla de política de SELinux permite la operación, continúa, sino, la operación se bloquea y el proceso recibe un error.
 		</div><div class="para">
-			Las decisiones de SELinux, tales como permitir o negar accesos, son cacheadas. Este caché se conoce como Caché Vector de Acceso (AVC). Las decisiones de cacheado disminuye la necesidad de que las reglas de políticas de SELinux sean chequeadas muy a menudo, lo que mejora la performance. Las reglas de políticas de SELinux no tienen efecto si las reglas DAC niegan el acceso primero.
+			SELinux decisions, such as allowing or disallowing access, are cached. This cache is known as the Access Vector Cache (AVC). Caching decisions decreases how often SELinux policy rules need to be checked, which increases performance. Remember that SELinux policy rules have no effect if DAC rules deny access first.
 		</div></div><div class="section" title="2.4. SELinux en otros Sistemas Operativos" id="sect-Security-Enhanced_Linux-Introduction-SELinux_on_Other_Operating_Systems"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.4. SELinux en otros Sistemas Operativos</h2></div></div></div><div class="para">
 			Vaya a la siguiente información sobre cómo correr SELinux en sistemas operativos:
 		</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-					Gentoo endurecido: <a href="http://www.gentoo.org/proj/en/hardened/selinux/selinux-handbook.xml">http://www.gentoo.org/proj/en/hardened/selinux/selinux-handbook.xml</a>.
+					Hardened Gentoo: <a href="http://www.gentoo.org/proj/en/hardened/selinux/selinux-handbook.xml">http://www.gentoo.org/proj/en/hardened/selinux/selinux-handbook.xml</a>.
 				</div></li><li class="listitem"><div class="para">
 					Debian: <a href="http://wiki.debian.org/SELinux">http://wiki.debian.org/SELinux</a>.
 				</div></li><li class="listitem"><div class="para">
@@ -223,28 +221,28 @@ books_tests  Desktop1  downloads      images  notes  scripts  svgs
 				</div></li><li class="listitem"><div class="para">
 					Linux para Empresas de Red Hat: <a href="http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.2/html/Deployment_Guide/selg-overview.html">Guía de Despliegue del Linux para Empresas de Red Hat</a> y la <a href="http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/selinux-guide/">Guía de SELinux para el Linux para Empresas de Red Hat</a>.
 				</div></li><li class="listitem"><div class="para">
-					Fedora: <a href="http://fedoraproject.org/wiki/SELinux">http://fedoraproject.org/wiki/SELinux</a> y el <a href="http://docs.fedoraproject.org/selinux-faq-fc5/">FAQ de SELinux de Fedora Core 5</a>.
-				</div></li></ul></div></div><div class="footnotes"><br /><hr width="100" align="left" /><div class="footnote"><p><sup>[<a id="ftn.id2090071" href="#id2090071" class="para">1</a>] </sup>
+					Fedora: <a href="http://fedoraproject.org/wiki/SELinux">http://fedoraproject.org/wiki/SELinux</a> and the <a href="http://docs.fedoraproject.org/selinux-faq-fc5/">Fedora Core 5 SELinux FAQ</a>.
+				</div></li></ul></div></div><div class="footnotes"><br /><hr width="100" align="left" /><div class="footnote"><p><sup>[<a id="ftn.id636508" href="#id636508" class="para">1</a>] </sup>
 			"Integrating Flexible Support for Security Policies into the Linux Operating System", by Peter Loscocco and Stephen Smalley. This paper was originally prepared for the National Security Agency and is, consequently, in the public domain. Refer to the <a href="http://www.nsa.gov/research/_files/selinux/papers/freenix01/index.shtml">original paper</a> for details and the document as it was first released. Any edits and changes were done by Murray McAllister.
-		</p></div><div class="footnote"><p><sup>[<a id="ftn.id973716" href="#id973716" class="para">2</a>] </sup>
+		</p></div><div class="footnote"><p><sup>[<a id="ftn.id705006" href="#id705006" class="para">2</a>] </sup>
 			"Meeting Critical Security Objectives with Security-Enhanced Linux", by Peter Loscocco and Stephen Smalley. This paper was originally prepared for the National Security Agency and is, consequently, in the public domain. Refer to the <a href="http://www.nsa.gov/research/_files/selinux/papers/ottawa01/index.shtml">original paper</a> for details and the document as it was first released. Any edits and changes were done by Murray McAllister.
-		</p></div><div class="footnote"><p><sup>[<a id="ftn.id884662" href="#id884662" class="para">3</a>] </sup>
+		</p></div><div class="footnote"><p><sup>[<a id="ftn.id715600" href="#id715600" class="para">3</a>] </sup>
 						Text files that include information, such as hostname to IP address mappings, that are used by DNS servers.
-					</p></div><div class="footnote"><p><sup>[<a id="ftn.id884702" href="#id884702" class="para">4</a>] </sup>
+					</p></div><div class="footnote"><p><sup>[<a id="ftn.id715635" href="#id715635" class="para">4</a>] </sup>
 						Cox, Mark. "Risk report: Three years of Red Hat Enterprise Linux 4". Published 26 February 2008. Accessed 27 August 2009: <a href="http://www.redhatmagazine.com/2008/02/26/risk-report-three-years-of-red-hat-enterprise-linux-4/">http://www.redhatmagazine.com/2008/02/26/risk-report-three-years-of-red-hat-enterprise-linux-4/</a>.
-					</p></div><div class="footnote"><p><sup>[<a id="ftn.id2075446" href="#id2075446" class="para">5</a>] </sup>
+					</p></div><div class="footnote"><p><sup>[<a id="ftn.id715678" href="#id715678" class="para">5</a>] </sup>
 						Marti, Don. "A seatbelt for server software: SELinux blocks real-world exploits". Published 24 February 2008. Accessed 27 August 2009: <a href="http://www.linuxworld.com/news/2008/022408-selinux.html?page=1">http://www.linuxworld.com/news/2008/022408-selinux.html?page=1</a>.
 					</p></div></div></div><div xml:lang="es-ES" class="chapter" title="Capítulo 3. Contextos de SELinux" id="chap-Security-Enhanced_Linux-SELinux_Contexts" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 3. Contextos de SELinux</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-SELinux_Contexts-Domain_Transitions">3.1. Transiciones de Dominios</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Processes">3.2. Contextos de SELinux para los Procesos</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Users">3.3. Contextos de SELinux para los Usuarios</a></span></dt></dl></div><div class="para">
-		Los procesos y archivos se etiquetan con un contexto SELinux que contiene información adicional, tal como un usuario SELinux, rol, tipo y, opcionalmente, un nivel. Cuando se ejecuta SELinux, toda esta información se usa para tomar decisiones de control de acceso. En Fedora, SELinux provee una combinación de Control de Acceso Basado en Roles (RBAC en inglés), <span class="trademark">Obediencia de Tipos</span>® (TE en inglés), y, opcionalmente, Seguridad Multi-nivel (MLS en inglés).
+		Processes and files are labeled with an SELinux context that contains additional information, such as an SELinux user, role, type, and, optionally, a level. When running SELinux, all of this information is used to make access control decisions. In Fedora, SELinux provides a combination of Role-Based Access Control (RBAC), <span class="trademark">Type Enforcement</span>® (TE), and, optionally, Multi-Level Security (MLS).
 	</div><div class="para">
-		El siguiente es un ejemplo de contexto de SELinux. Los contextos de SELinux se usan en procesos, usuarios de Linux y archivos, en sistemas operativos Linux que corren SELinux. Use el comando <code class="command">ls -Z</code> para ver el contexto SELinux de archivos y directorios:
+		The following is an example showing SELinux context. SELinux contexts are used on processes, Linux users, and files, on Linux operating systems that run SELinux. Use the <code class="command">ls -Z</code> command to view the SELinux context of files and directories:
 	</div><pre class="screen">$ ls -Z file1
--rw-rw-r--. user1 group1 unconfined_u:object_r:user_home_t:s0 file1
+-rwxrw-r--  user1 group1 unconfined_u:object_r:user_home_t:s0      file1
 
 </pre><div class="para">
 		Los contextos de SELinux siguen la <span class="emphasis"><em>SELinux nombre-de-usuario:role:type:level</em></span> sintaxis:
-	</div><div class="variablelist"><dl><dt><span class="term"><span class="emphasis"><em>Usuario SELinux</em></span></span></dt><dd><div class="para">
-					La identidad de usuario SELinux es una identidad conocida para la política a la que se le autoriza un conjunto específico de roles, y un rango específico de MLS. Cada usuario Linux se mapea a un usuario SELinux vía la política de SELinux. Esto permite a los usuarios de Linux heredar las restricciones de los usuarios SELinux. La identidad del usuario SELinux mapeado se usa en el contexto de SELinux para procesos en esa sesión, para definir a qué roles y niveles pueden ingresar. Ejecute el comando <code class="command">semanage login -l</code> como usuario root de Linux para ver una lista de mapeos entre cuentas de usuarios Linux y SELinux:
+	</div><div class="variablelist"><dl><dt><span class="term"><span class="emphasis"><em>SELinux user</em></span></span></dt><dd><div class="para">
+					The SELinux user identity is an identity known to the policy that is authorized for a specific set of roles, and for a specific MLS range. Each Linux user is mapped to an SELinux user via SELinux policy. This allows Linux users to inherit the restrictions placed on SELinux users. The mapped SELinux user identity is used in the SELinux context for processes in that session, in order to define what roles and levels they can enter. Run the <code class="command">semanage login -l</code> command as the Linux root user to view a list of mappings between SELinux and Linux user accounts:
 				</div><pre class="screen">
 # /usr/sbin/semanage login -l
 
@@ -255,28 +253,28 @@ root                      unconfined_u              s0-s0:c0.c1023
 system_u                  system_u                  s0-s0:c0.c1023
 
 </pre><div class="para">
-					La salida puede ser distinta de sistema a sistema. La columna <code class="computeroutput">Nombre de Ingreso</code> lista los usuarios Linux, y la columna <code class="computeroutput">Usuario SELinux</code> lista qué a usuario SELinux es mapeado un usuario Linux. Para procesos, el usuario SELinux limita qué roles y niveles son accesibles. La última columna, <code class="computeroutput">Rango MLS/MCS</code>, es el nivel usado por la Seguridad Multi Nivel (MLS) y por la Seguridad Multi Categoría (MCS). Los niveles se describen brevemente más adelante.
-				</div></dd><dt><span class="term"><span class="emphasis"><em>rol</em></span></span></dt><dd><div class="para">
+					Output may differ slightly from system to system. The <code class="computeroutput">Login Name</code> column lists Linux users, and the <code class="computeroutput">SELinux User</code> column lists which SELinux user the Linux user is mapped to. For processes, the SELinux user limits which roles and levels are accessible. The last column, <code class="computeroutput">MLS/MCS Range</code>, is the level used by Multi-Level Security (MLS) and Multi-Category Security (MCS). Levels are briefly discussed later.
+				</div></dd><dt><span class="term"><span class="emphasis"><em>role</em></span></span></dt><dd><div class="para">
 					Parte de SELinux es el modelo de seguridad de Control de Acceso Basado en Roles (RBAC). El rol es un atributo de RBAC. Los usuarios de SELinux son autorizados para ciertos roles y los roles son autorizados para ciertos dominios. Los roles sirven como un intermediario entre dominios y usarios SELinux. Los roles en los que se puede ingresar determinan los dominios a los que se ingresan - al final, esto controla los tipos de objetos que se pueden acceder. Esto ayuda a reducir la vulnerabilidad de ataques de escalada de privilegios.
-				</div></dd><dt><span class="term"><span class="emphasis"><em>tipo</em></span></span></dt><dd><div class="para">
-					El tipo es un atributo de la Obediencia de Tipos. El tipo define un dominio para procesos y un tipo para los archivos. Las reglas de políticas de SELinux define cómo se acceden los tipos entre si, ya sea un dominio que accede a un tipo o un dominio que accede a otro dominio. Los acceso sólo se permiten si existe una regla de política de SELinux que lo permita.
-				</div></dd><dt><span class="term"><span class="emphasis"><em>nivel</em></span></span></dt><dd><div class="para">
+				</div></dd><dt><span class="term"><span class="emphasis"><em>type</em></span></span></dt><dd><div class="para">
+					The type is an attribute of Type Enforcement. The type defines a domain for processes, and a type for files. SELinux policy rules define how types can access each other, whether it be a domain accessing a type, or a domain accessing another domain. Access is only allowed if a specific SELinux policy rule exists that allows it.
+				</div></dd><dt><span class="term"><span class="emphasis"><em>level</em></span></span></dt><dd><div class="para">
 					El nivel es un atributo de MLS y la Seguridad Multi Categoría (MCS). Un rango MLS es un par de niveles, escrito como <span class="emphasis"><em>bajonivel-altonivel</em></span> si los niveles sin distintos, o <span class="emphasis"><em>bajonivel</em></span> si los niveles son idénticos (<code class="computeroutput">s0-s0</code> es lo mismo que <code class="computeroutput">s0</code>). Cada nivel es un par sensible a categorías, donde las categorías son opcionales. Si no hay categorías, el nivel se escribe como <span class="emphasis"><em>sensibilidad:conjunto-de-categoría</em></span>. Si no hay categorías, se escribe como <span class="emphasis"><em>sensibilidad</em></span>.
 				</div><div class="para">
 					If the category set is a contiguous series, it can be abbreviated. For example, <code class="computeroutput">c0.c3</code> is the same as <code class="computeroutput">c0,c1,c2,c3</code>. The <code class="filename">/etc/selinux/targeted/setrans.conf</code> file maps levels (<code class="computeroutput">s0:c0</code>) to human-readable form (ie. <code class="computeroutput">CompanyConfidential</code>). Do not edit <code class="filename">setrans.conf</code> with a text editor: use <code class="command">semanage</code> to make changes. Refer to the <span class="citerefentry"><span class="refentrytitle">semanage</span>(8)</span> manual page for further information. In Fedora, targeted policy enforces MCS, and in MCS, there is just one sensitivity, <code class="computeroutput">s0</code>. MCS in Fedora supports 1024 different categories: <code class="computeroutput">c0</code> through to <code class="computeroutput">c1023</code>. <code class="computeroutput">s0-s0:c0.c1023</code>
  is sensitivity <code class="computeroutput">s0</code> and authorized for all categories.
 				</div><div class="para">
-					MLS enforces the <a href="http://en.wikipedia.org/wiki/Bell-LaPadula_model">Bell-La Padula Mandatory Access Model</a>, and is used in Labeled Security Protection Profile (LSPP) environments. To use MLS restrictions, install the <span class="package">selinux-policy-mls</span> package, and configure MLS to be the default SELinux policy via the <code class="filename">/etc/selinux/config</code> file. The MLS policy shipped with Fedora omits many program domains that were not part of the evaluated configuration, and therefore, MLS on a desktop workstation is unusable (no support for the X Window System); however, an MLS policy from the <a href="http://oss.tresys.com/projects/refpolicy">upstream SELinux Reference Policy</a> can be built that includes all program domains.
+					MLS enforces the <a href="http://en.wikipedia.org/wiki/Bell-LaPadula_model">Bell-La Padula Mandatory Access Model</a>, and is used in Labeled Security Protection Profile (LSPP) environments. To use MLS restrictions, install the <span class="package">selinux-policy-mls</span> package, and configure MLS to be the default SELinux policy. The MLS policy shipped with Fedora omits many program domains that were not part of the evaluated configuration, and therefore, MLS on a desktop workstation is unusable (no support for the X Window System); however, an MLS policy from the <a href="http://oss.tresys.com/projects/refpolicy">upstream SELinux Reference Policy</a> can be built that includes all program domains.
 				</div></dd></dl></div><div class="section" title="3.1. Transiciones de Dominios" id="sect-Security-Enhanced_Linux-SELinux_Contexts-Domain_Transitions"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">3.1. Transiciones de Dominios</h2></div></div></div><div class="para">
 			Un proceso transiciona de un dominio a otro ejecutando una aplicación que tiene el tipo <code class="computeroutput">entrypoint</code> en el nuevo dominio. Los permisos <code class="computeroutput">entrypoint</code> se usan en las políticas de SELinux, y controlan qué aplicaciones pueden usarse para ingresar a un dominio. El siguiente ejemplo muestra una transición de dominio.
 		</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
-					Un usuario desea cambiar su contraseña. Para cambiar sus contraseñas, corren la aplicación <code class="command">passwd</code>. El ejecutable <code class="filename">/usr/bin/passwd</code> está etiquetado con el tipo <code class="computeroutput">passwd_exec_t</code>:
+					A user wants to change their password. To do this, they run the <code class="command">passwd</code> application. The <code class="filename">/usr/bin/passwd</code> executable is labeled with the <code class="computeroutput">passwd_exec_t</code> type:
 				</div><pre class="screen">$ ls -Z /usr/bin/passwd
 -rwsr-xr-x  root root system_u:object_r:passwd_exec_t:s0 /usr/bin/passwd
 
 </pre><div class="para">
 					La aplicación <span class="application"><strong>passwd</strong></span> accede <code class="filename">/etc/shadow</code>, que está etiquetado con el tipo <code class="computeroutput">shadow_t</code>:
 				</div><pre class="screen">$ ls -Z /etc/shadow
-----------. root root system_u:object_r:shadow_t:s0    /etc/shadow
+-r--------. root root system_u:object_r:shadow_t:s0    /etc/shadow
 
 </pre></li><li class="listitem"><div class="para">
 					Una regla de política de SELinux dice que los procesos que se ejecutan en el dominio <code class="computeroutput">passwd_t</code> no pueden leer y escribir archivos etiquetados con el tipo <code class="computeroutput">shadow_t</code>. El tipo <code class="computeroutput">shadow_t</code> sólo se aplica a archivos que necesitan un cambio de contraseñas. Esto incluye a <code class="filename">/etc/gshadow</code>, <code class="filename">/etc/shadow</code>, y sus archivos de respaldo.
@@ -305,7 +303,7 @@ system_u                  system_u                  s0-s0:c0.c1023
 				</div><pre class="screen">unconfined_u:unconfined_r:passwd_t:s0-s0:c0.c1023 13212 pts/1 00:00:00 passwd
 
 </pre></li><li class="listitem"><div class="para">
-					En la primer pestaña, presione <strong class="userinput"><code>Ctrl+C</code></strong> para cancelar la aplicación <span class="application"><strong>passwd</strong></span>.
+					In the first tab/terminal, press <strong class="userinput"><code>Ctrl+C</code></strong> to cancel the <span class="application"><strong>passwd</strong></span> application.
 				</div></li></ol></div><div class="para">
 			In this example, when the <code class="filename">/usr/bin/passwd</code> application (labeled with the <code class="computeroutput">passwd_exec_t</code> type) is executed, the user's shell process transitions to the <code class="computeroutput">passwd_t</code> domain. Remember: the type defines a domain for processes, and a type for files.
 		</div><div class="para">
@@ -325,15 +323,15 @@ system_u:system_r:crond_t:s0-s0:c0.c1023 1991 ? 00:00:00 atd
 		</div><pre class="screen">unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
 
 </pre><div class="para">
-			En Fedora, los usuarios Linux corren no confinados por defecto. Este contexto de SELinux muestra que el usuario Linux se mapea al usuario SELinux <code class="computeroutput">unconfined_u</code>, corriendo con el rol <code class="computeroutput">unconfined_r</code> y en el dominio <code class="computeroutput">unconfined_t</code>. <code class="computeroutput">s0-s0</code> es un rango MLS, que en este caso, es el mismo que <code class="computeroutput">s0</code>. Las categorías a las que el usuario tiene acceso se definen por <code class="computeroutput">c0.c1023</code>, que son todas las categorías (<code class="computeroutput">c0</code> a <code class="computeroutput">c1023</code>).
+			In Fedora, Linux users run unconfined by default. This SELinux context shows that the Linux user is mapped to the SELinux <code class="computeroutput">unconfined_u</code> user, running as the <code class="computeroutput">unconfined_r</code> role, and is running in the <code class="computeroutput">unconfined_t</code> domain. <code class="computeroutput">s0-s0</code> is an MLS range, which in this case, is the same as just <code class="computeroutput">s0</code>. The categories the user has access to is defined by <code class="computeroutput">c0.c1023</code>, which is all categories (<code class="computeroutput">c0</code> through to <code class="computeroutput">c1023</code>).
 		</div></div></div><div xml:lang="es-ES" class="chapter" title="Capítulo 4. Política Destinado" id="chap-Security-Enhanced_Linux-Targeted_Policy" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 4. Política Destinado</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Targeted_Policy-Confined_Processes">4.1. Procesos Confinados</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Targeted_Policy-Unconfined_Processes">4.2. Procesos no Confinados</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users">4.3. Usuarios Confinados y no Confinados</a></span></dt></dl></div><div class="para">
-		La política destinada es la política predeterminada de SELinux usada en Fedora. Cuando la política destinada está en uso, los procesos son destinados a correr en dominios confinados, y los procesos que no son destinados a correr en un dominio corren en un dominio no confinado. Por ejemplo, por defecto, los usuarios que ingresaron corren en el dominio <code class="computeroutput">unconfined_t</code>, y los procesos del sistema iniciado por init corren en el dominio <code class="computeroutput">initrc_t</code> - ambos dominios están no confinados.
+		Targeted policy is the default SELinux policy used in Fedora. When using targeted policy, processes that are targeted run in a confined domain, and processes that are not targeted run in an unconfined domain. For example, by default, logged in users run in the <code class="computeroutput">unconfined_t</code> domain, and system processes started by init run in the <code class="computeroutput">initrc_t</code> domain - both of these domains are unconfined.
 	</div><div class="para">
-		Los dominios no confinados (así como los dominios confinados) son sujetos a chequeos de memoria escribible y ejecutable. Por defecto, los que se ejecutan en un dominio no confinado no pueden asignar memoria escribible y ejecutarla. Esto reduce la vulnerabilidad de <a href="http://en.wikipedia.org/wiki/Buffer_overflow">ataque de sobreflujo de buffer</a>. Estos chequeos de memoria se deshabilitan poniendo Booleanos, que permiten modificar la política de SELinux en tiempo de ejecución. La configuración de Booleano se discute más adelante.
+		Unconfined domains (as well as confined domains) are subject to executable and writeable memory checks. By default, subjects running in an unconfined domain can not allocate writeable memory and execute it. This reduces vulnerability to <a href="http://en.wikipedia.org/wiki/Buffer_overflow">buffer overflow attacks</a>. These memory checks are disabled by setting Booleans, which allow the SELinux policy to be modified at runtime. Boolean configuration is discussed later.
 	</div><div class="section" title="4.1. Procesos Confinados" id="sect-Security-Enhanced_Linux-Targeted_Policy-Confined_Processes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.1. Procesos Confinados</h2></div></div></div><div class="para">
 			Almost every service that listens on a network is confined in Fedora. Also, most processes that run as the Linux root user and perform tasks for users, such as the <span class="application"><strong>passwd</strong></span> application, are confined. When a process is confined, it runs in its own domain, such as the <code class="systemitem">httpd</code> process running in the <code class="computeroutput">httpd_t</code> domain. If a confined process is compromised by an attacker, depending on SELinux policy configuration, an attacker's access to resources and the possible damage they can do is limited.
 		</div><div class="para">
-			El siguiente ejemplo muestra cómo previene SELinux la lectura por parte del Servidor HTTP Apache (<code class="systemitem">httpd</code>) de archivos que no se etiquetaron correctamente, tales como archivos a usar con Samba. Este es un ejemplo, y no se debe usar en producción. Asume que los paquetes <span class="package">httpd</span>, <span class="package">wget</span>, <span class="package">setroubleshoot-server</span>, <span class="package">dbus</span> y <span class="package">audit</span> están instalados, que se usa la política destinada de SELinux y que SELinux está corriendo en modo obediente:
+			The following example demonstrates how SELinux prevents the Apache HTTP Server (<code class="systemitem">httpd</code>) from reading files that are not correctly labeled, such as files intended for use by Samba. This is an example, and should not be used in production. It assumes that the <span class="package">httpd</span>, <span class="package">wget</span>, <span class="package">setroubleshoot-server</span>, <span class="package">dbus</span> and <span class="package">audit</span> packages are installed, that the SELinux targeted policy is used, and that SELinux is running in enforcing mode:
 		</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
 					Ejecute el comando <code class="command">sestatus</code> para confirmar que SELinux está activado, se ejecuta en modo obligatorio y que la política destinada se está usando:
 				</div><pre class="screen">
@@ -346,7 +344,7 @@ Policy version:                 24
 Policy from config file:        targeted
 
 </pre><div class="para">
-					<code class="computeroutput">Estado de SELinux: activado</code> se devuelve cuando SELinux está activado. <code class="computeroutput">Modo actual: obediente</code> se devuelve cuando SELinux está ejecutándose en modo obediente. <code class="computeroutput">Política desde el archivo de configuración: destinada</code> se devuelve cuando se usa la política destinada de SELinux.
+					<code class="computeroutput">SELinux status: enabled</code> is returned when SELinux is enabled. <code class="computeroutput">Current mode: enforcing</code> is returned when SELinux is running in enforcing mode. <code class="computeroutput">Policy from config file: targeted</code> is returned when the SELinux targeted policy is used.
 				</div></li><li class="listitem"><div class="para">
 					Como usuario root de Linux, ejecute el comando <code class="command">touch /var/www/html/prueba</code> para crear un archivo.
 				</div></li><li class="listitem"><div class="para">
@@ -354,7 +352,7 @@ Policy from config file:        targeted
 				</div><pre class="screen">-rw-r--r--  root root unconfined_u:object_r:httpd_sys_content_t:s0 /var/www/html/testfile
 
 </pre><div class="para">
-					Por defecto, los usuarios Linux corren no confinados en Fedora, razón por la cual el archivo <code class="filename">prueba</code> se etiqueta con el usuario SELinux <code class="computeroutput">unconfined_u</code>. RBAC se usa para procesos, y no para archivos. Los roles no tienen significado para archivos - el rol <code class="computeroutput">object_r</code> es un rol genérico usado para archivos (en sistemas de archivos persistentes y de red). Bajo el directorio <code class="filename">/proc/</code>, los archivos relacionados con procesos pueden usar el rol <code class="computeroutput">system_r</code>.<sup>[<a id="id2087633" href="#ftn.id2087633" class="footnote">6</a>]</sup> El tipo <code class="computeroutput">httpd_sys_content_t</code> permite al proceso <code class="systemitem">httpd</code> acceder a este archivo.
+					By default, Linux users run unconfined in Fedora, which is why the <code class="filename">testfile</code> file is labeled with the SELinux <code class="computeroutput">unconfined_u</code> user. RBAC is used for processes, not files. Roles do not have a meaning for files - the <code class="computeroutput">object_r</code> role is a generic role used for files (on persistent storage and network file systems). Under the <code class="filename">/proc/</code> directory, files related to processes may use the <code class="computeroutput">system_r</code> role.<sup>[<a id="id730926" href="#ftn.id730926" class="footnote">6</a>]</sup> The <code class="computeroutput">httpd_sys_content_t</code> type allows the <code class="systemitem">httpd</code> process to access this file.
 				</div></li><li class="listitem"><div class="para">
 					Como usuario root de Linux, ejecute el comando <code class="command">service httpd start</code> para iniciar el proceso <code class="systemitem">httpd</code>. La salida escomo sigue si <code class="systemitem">httpd</code> inicia con éxito:
 				</div><pre class="screen"># /sbin/service httpd start
@@ -362,38 +360,32 @@ Starting httpd:                                            [  OK  ]
 
 </pre></li><li class="listitem"><div class="para">
 					Cambie al directorio donde su usuario Linux tenga acceso de escritura y ejecute el comando <code class="command">wget http://localhost/prueba</code>. A menos que hubieran cambios en la configuración predeterminada, este comando tiene éxito:
-				</div><pre class="screen">
-$ wget http://localhost/testfile
-
---2010-05-11 13:19:07--  http://localhost/testfile
-Resolving localhost... ::1, 127.0.0.1
-Connecting to localhost|::1|:80... connected.
+				</div><pre class="screen">--2009-11-06 17:43:01--  http://localhost/testfile
+Resolving localhost... 127.0.0.1
+Connecting to localhost|127.0.0.1|:80... connected.
 HTTP request sent, awaiting response... 200 OK
 Length: 0 [text/plain]
-Saving to: “testfile”
-
-    [ &lt;=&gt;            ] 0           --.-K/s   in 0s      
+Saving to: `testfile'
 
-2010-05-11 13:19:07 (0.00 B/s) - “testfile” saved [0/0]
+[ &lt;=&gt;                              ] 0     --.-K/s   in 0s
+		
+2009-11-06 17:43:01 (0.00 B/s) - `testfile' saved [0/0]
 
 </pre></li><li class="listitem"><div class="para">
 					El comando <code class="command">chcon</code> reetiqueta archivos; sin embargo, tales cambios de etiquetas no sobreviven cuando el sistema se reetiqueta. Para que los cambios sobrevivan un reetiquetado del sistema, use el comando <code class="command">semanage</code>, que se discute más adelante. Como usuario root de Linux, corra el siguiente comando para cambiar el tipo a un tipo usado por Samba:
 				</div><div class="para">
-					<code class="command">chcon -t samba_share_t /var/www/html/prueba</code>
+					<code class="command">chcon -t samba_share_t /var/www/html/testfile</code>
 				</div><div class="para">
 					Ejecute el comando <code class="command">ls -Z /var/www/html/prueba</code> para ver los cambios:
 				</div><pre class="screen">-rw-r--r--  root root unconfined_u:object_r:samba_share_t:s0 /var/www/html/testfile
 
 </pre></li><li class="listitem"><div class="para">
 					Nota: los permisos de DAC actuales permiten al proceso <code class="systemitem">httpd</code> acceder al <code class="filename">prueba</code>. Cambie al directorio donde el usuario Linux tenga permiso de escritura y ejecute el comando <code class="command">wget http://localhost/prueba</code>. A menos que hayan cambios en la configuración predeterminada, este comando fallará:
-				</div><pre class="screen">
-$ wget http://localhost/testfile
-
---2010-05-11 13:23:49--  http://localhost/testfile
-Resolving localhost... ::1, 127.0.0.1
-Connecting to localhost|::1|:80... connected.
+				</div><pre class="screen">--2009-11-06 14:11:23--  http://localhost/testfile
+Resolving localhost... 127.0.0.1
+Connecting to localhost|127.0.0.1|:80... connected.
 HTTP request sent, awaiting response... 403 Forbidden
-2010-05-11 13:23:49 ERROR 403: Forbidden.
+2009-11-06 14:11:23 ERROR 403: Forbidden.
 
 </pre></li><li class="listitem"><div class="para">
 					Como usuario root de Linux, corra el comando <code class="command">rm -i /var/www/html/prueba</code> para borrar <code class="filename">prueba</code>.
@@ -404,8 +396,9 @@ Stopping httpd:                                            [  OK  ]
 
 </pre></li></ol></div><div class="para">
 			Este ejemplo muestra la seguridad adicional agregada por SELinux. Aunque las reglas de DAC permitieron al proceso <code class="systemitem">httpd</code> acceder a <code class="filename">prueba</code> en el paso 7, dado que estaba etiquetado con un tipo al que el proceso <code class="systemitem">httpd</code> no tenía acceso, SELinux negó el acceso. Después del paso 7, un error similar al siguiente se guarda en <code class="filename">/var/log/messages</code>:
-		</div><pre class="screen">
-May 11 13:23:51 localhost setroubleshoot: SELinux is preventing /usr/sbin/httpd "getattr" access to /var/www/html/testfile. For complete SELinux messages. run sealert -l ca2ab0df-fcb9-46d1-8283-037450d1efcc
+		</div><pre class="screen">May 6 23:00:54 localhost setroubleshoot: SELinux is preventing httpd (httpd_t) "getattr"
+to /var/www/html/testfile (samba_share_t). For complete SELinux messages.
+run sealert -l c05911d3-e680-4e42-8e36-fe2ab9f8e654
 
 </pre><div class="para">
 			Archivos log previos pueden usar el formato <code class="filename">/var/log/messages.<em class="replaceable"><code>YYYYMMDD</code></em></code>. Cuando se ejecuta <span class="application"><strong>syslog-ng</strong></span>, los archivos log previos pueden usar el formato <code class="filename">/var/log/messages.<em class="replaceable"><code>X</code></em></code>. Si los procesos <code class="systemitem">setroubleshootd</code> y <code class="systemitem">auditd</code> están ejecutándose, errores similares a los siguientes se registran en <code class="filename">/var/log/audit/audit.log</code>:
@@ -415,12 +408,12 @@ type=SYSCALL msg=audit(1220706212.937:70): arch=40000003 syscall=196 success=no
 
 </pre><div class="para">
 			También, un error similar al siguiente se registra en <code class="filename">/var/log/httpd/error_log</code>:
-		</div><pre class="screen">[Tue May 11 13:23:49 2010] [error] [client <em class="replaceable"><code>::1</code></em>] (13)Permission denied: access to /testfile denied
+		</div><pre class="screen">[Wed May 06 23:00:54 2009] [error] [client <em class="replaceable"><code>127.0.0.1</code></em>] (13)Permission denied: access to /testfile denied
 
 </pre></div><div class="section" title="4.2. Procesos no Confinados" id="sect-Security-Enhanced_Linux-Targeted_Policy-Unconfined_Processes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.2. Procesos no Confinados</h2></div></div></div><div class="para">
 			Los procesos no confinados corren en dominios no confinados, por ejemplo, los programas init (del arranque) corren en el dominio no confinado <code class="computeroutput">initrc_t</code>, los procesos no confinados del kernel corren en el dominio <code class="computeroutput">kernel_t</code> y los usuarios no confinados deLInux corren en el dominio <code class="computeroutput">unconfined_t</code>. Para procesos no confinados, las reglas de la política de SELinux son aplicadas, pero hay reglas de la política que permiten que los procesos se ejecuten en dominios no confinados tengan casi todos los accesos. Los procesos que corren en dominios no confinados terminan usando exclusivamente las reglas DAC. Si un proceso no confinado es comprometido, SELinux no impide que un atacante gane acceso a los recursos del sistema y a los datos, pero, por supuesto, las reglas DAC todavía se usan. SELinux es una mejora de seguridad sobre las reglas DAC - no las reemplaza.
 		</div><div class="para">
-			El siguiente ejemplo muestra cómo el Servidor HTTP Apache (<code class="systemitem">httpd</code>) puede acceder datos que se suponen son para ser usados por Samba, cuando se corre no confinado. Nota: en Fedora, el proceso <code class="systemitem">httpd</code> corre en el dominio confinado <code class="computeroutput">httpd_t</code> por defecto. Este es un ejemplo, y no debe usarse en producción. Se asume que los paquetes <span class="package">httpd</span>, <span class="package">wget</span>, <span class="package">setroubleshoot-server</span>, <span class="package">dbus</span> y <span class="package">audit</span> están instalados, que se usa la política destinada de SELinux y que SELinux corre en modo obediente:
+			The following example demonstrates how the Apache HTTP Server (<code class="systemitem">httpd</code>) can access data intended for use by Samba, when running unconfined. Note: in Fedora, the <code class="systemitem">httpd</code> process runs in the confined <code class="computeroutput">httpd_t</code> domain by default. This is an example, and should not be used in production. It assumes that the <span class="package">httpd</span>, <span class="package">wget</span>, <span class="package">setroubleshoot-server</span>, <span class="package">dbus</span> and <span class="package">audit</span> packages are installed, that the SELinux targeted policy is used, and that SELinux is running in enforcing mode:
 		</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
 					Ejecute el comando <code class="command">sestatus</code> para confirmar que SELinux está activado, se ejecuta en modo obligatorio y que la política destinada se está usando:
 				</div><pre class="screen">
@@ -429,11 +422,11 @@ SELinux status:                 enabled
 SELinuxfs mount:                /selinux
 Current mode:                   enforcing
 Mode from config file:          enforcing
-Policy version:                 24
+Policy version:                 23
 Policy from config file:        targeted
 
 </pre><div class="para">
-					<code class="computeroutput">Estado de SELinux: activado</code> se devuelve cuando SELinux está activado. <code class="computeroutput">Modo actual: obediente</code> se devuelve cuando SELinux está ejecutándose en modo obediente. <code class="computeroutput">Política desde el archivo de configuración: destinada</code> se devuelve cuando se usa la política destinada de SELinux.
+					<code class="computeroutput">SELinux status: enabled</code> is returned when SELinux is enabled. <code class="computeroutput">Current mode: enforcing</code> is returned when SELinux is running in enforcing mode. <code class="computeroutput">Policy from config file: targeted</code> is returned when the SELinux targeted policy is used.
 				</div></li><li class="listitem"><div class="para">
 					Como usuario root de Linux, corra el comando <code class="command">touch /var/www/html/prueba2</code> para crear un archivo.
 				</div></li><li class="listitem"><div class="para">
@@ -441,11 +434,11 @@ Policy from config file:        targeted
 				</div><pre class="screen">-rw-r--r--  root root unconfined_u:object_r:httpd_sys_content_t:s0 /var/www/html/test2file
 
 </pre><div class="para">
-					Por defecto, los usuarios Linux corren no confinados en Fedora, razón por la cual el archivo <code class="filename">prueba2</code> está etiquetado con el usuario SELinux <code class="computeroutput">unconfined_u</code>. RBAC se usa para procesos, no para archivos. Los roles no tienen un significado para archivos - el rol <code class="computeroutput">object_r</code> es el rol genérico que se usa para archivos (en almacenamiento persistente y sistemas de archivos de red). Bajo el directorio <code class="filename">/proc/</code>, los archivos relacionados con procesos pueden usar el rol <code class="computeroutput">system_r</code>.<sup>[<a id="id972672" href="#ftn.id972672" class="footnote">7</a>]</sup> El tipo <code class="computeroutput">httpd_sys_content_t</code> permite al proceso <code class="systemitem">httpd</code> acceder a este archivo.
+					By default, Linux users run unconfined in Fedora, which is why the <code class="filename">test2file</code> file is labeled with the SELinux <code class="computeroutput">unconfined_u</code> user. RBAC is used for processes, not files. Roles do not have a meaning for files - the <code class="computeroutput">object_r</code> role is a generic role used for files (on persistent storage and network file systems). Under the <code class="filename">/proc/</code> directory, files related to processes may use the <code class="computeroutput">system_r</code> role.<sup>[<a id="id792174" href="#ftn.id792174" class="footnote">7</a>]</sup> The <code class="computeroutput">httpd_sys_content_t</code> type allows the <code class="systemitem">httpd</code> process to access this file.
 				</div></li><li class="listitem"><div class="para">
 					El comando <code class="command">chcon</code> reetiqueta archivos; sin embargo, tales cambios de etiquetas no sobreviven cuando el sistema se reetiqueta. Para que los cambios sobrevivan un reetiquetado del sistema, use el comando <code class="command">semanage</code>, que se discute más adelante. Como usuario root de Linux, corra el siguiente comando para cambiar el tipo a un tipo usado por Samba:
 				</div><div class="para">
-					<code class="command">chcon -t samba_share_t /var/www/html/prueba2</code>
+					<code class="command">chcon -t samba_share_t /var/www/html/test2file</code>
 				</div><div class="para">
 					Ejecute el comando <code class="command">ls -Z /var/www/html/prueba2</code> para ver los cambios:
 				</div><pre class="screen">-rw-r--r--  root root unconfined_u:object_r:samba_share_t:s0 /var/www/html/test2file
@@ -547,15 +540,15 @@ root                      unconfined_u              s0-s0:c0.c1023
 system_u                  system_u                  s0-s0:c0.c1023
 
 </pre><div class="para">
-			En Fedora 13, los usuarios de Linux se mapean por defecto al ingreso <code class="computeroutput">__default__</code> de SELinux (el cual se mapea al usuario SELinux <code class="computeroutput">unconfined_u</code>). Lo siguiente define el mapeo por defecto:
+			In Fedora 13, Linux users are mapped to the SELinux <code class="computeroutput">__default__</code> login by default (which is mapped to the SELinux <code class="computeroutput">unconfined_u</code> user). The following defines the default-mapping:
 		</div><pre class="screen">__default__               unconfined_u              s0-s0:c0.c1023
 
 </pre><div class="para">
-			El siguiente ejemplo muestra el agregado de un usuario de Linux nuevo y el mapeo de ese usuario al usuario SELinux <code class="computeroutput">unconfined_u</code>. Asume que el usuario root corre no confinado, como es por defecto en Fedora 13:
+			The following example demonstrates adding a new Linux user, and that Linux user being mapped to the SELinux <code class="computeroutput">unconfined_u</code> user. It assumes that the Linux root user is running unconfined, as it does by default in Fedora 13:
 		</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
 					Como usuario root de Linux, ejecute el comando <code class="command">/usr/sbin/useradd usuarionuevo</code> para crear un nuevo usuario Linux con nombre usuarionuevo.
 				</div></li><li class="listitem"><div class="para">
-					Como usuario root de Linux, corra el comando <code class="command">passwd usuarionuevo</code> para asignar una contraseña para el usuario usuarionuevo de Linux:
+					As the Linux root user, run the <code class="command">passwd newuser</code> command to assign a password to the Linux newuser user:
 				</div><pre class="screen"># passwd newuser
 Changing password for user newuser.
 New UNIX password: <em class="replaceable"><code>Enter a password</code></em> 
@@ -572,8 +565,8 @@ unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
 				</div></li></ol></div><div class="para">
 			Los usuarios Linux confinados y no confinados son sujeto a chequeso de memoria escribible y ejecutable, y también son restringidos por MCS (y MLS, si la política MLS está siendo usada). Si los usuarios Linux no confinados ejecutan una aplicación que la política de SELinux define que puede transicionar del dominio <code class="computeroutput">unconfined_t</code> a su propio dominio confinado, los usuarios Linux no confinados están sujetos a restricciones de ese dominio confinado. El beneficio de seguridad de esto es que, aunque un usuario Linux corra no confinado, la aplicación permanece confinada, y por lo tanto, la explotación de una brecha en la aplicación está limitada por la política. Nota: esto no protege al sistema del usuario. En su defecto, el usuario y el sistema están siendo protegidos de posibles daños causados por una brecha en la aplicación.
 		</div><div class="para">
-			Los siguientes usuarios SELinux confinados están disponibles en Fedora 13:
-		</div><div class="table"><div class="table-contents"><table summary="Capacidades del Usuario SELinux" border="1"><colgroup><col width="17%" /><col width="17%" /><col width="17%" /><col width="17%" /><col width="17%" /><col width="17%" /></colgroup><thead><tr><th>
+			The following confined SELinux users are available in Fedora 13:
+		</div><div class="table" title="Tabla 4.1. Capacidades del Usuario SELinux" id="tabl-Security-Enhanced_Linux-Confined_and_Unconfined_Users-SELinux_User_Capabilities"><div class="table-contents"><table summary="Capacidades del Usuario SELinux" border="1"><colgroup><col width="17%" /><col width="17%" /><col width="17%" /><col width="17%" /><col width="17%" /><col width="17%" /></colgroup><thead><tr><th>
 							Usuario
 						</th><th>
 							Dominio
@@ -646,19 +639,17 @@ unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
 				</div></li></ul></div><div class="para">
 			By default, Linux users in the <code class="computeroutput">guest_t</code> and <code class="computeroutput">xguest_t</code> domains can not execute applications in their home directories or <code class="filename">/tmp/</code>, preventing them from executing applications (which inherit users' permissions) in directories they have write access to. This helps prevent flawed or malicious applications from modifying files users' own.
 		</div><div class="para">
-			Por defecto, los usuarios Linux en los dominios <code class="computeroutput">user_t</code> y <code class="computeroutput">staff_t</code> pueden ejecutar aplicaciones en sus directorios de inicio y en <code class="filename">/tmp/</code>. Vaya a <a class="xref" href="#sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications" title="6.6. Booleanos para que los Usuarios Ejecuten Aplicaciones">Sección 6.6, “Booleanos para que los Usuarios Ejecuten Aplicaciones”</a> para información sobre permitir y evitar que los usuarios ejecuten aplicaciones en sus directorios de inicio y en <code class="filename">/tmp/</code>.
-		</div></div><div class="footnotes"><br /><hr width="100" align="left" /><div class="footnote"><p><sup>[<a id="ftn.id2087633" href="#id2087633" class="para">6</a>] </sup>
-						cuando se usan otras políticas, tal como MLS, se pueden usar otros roles, por ejemplo <code class="computeroutput">secadm_r</code>.
-					</p></div><div class="footnote"><p><sup>[<a id="ftn.id972672" href="#id972672" class="para">7</a>] </sup>
-						Cuando se usan otras políticas, tal como la MLS, se pueden usar también otros roles, por ejemplo el <code class="computeroutput">secadm_r</code>.
+			By default, Linux users in the <code class="computeroutput">user_t</code> and <code class="computeroutput">staff_t</code> domains can execute applications in their home directories and <code class="filename">/tmp/</code>. Refer to <a class="xref" href="#sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications" title="6.6. Booleanos para que los Usuarios Ejecuten Aplicaciones">Sección 6.6, “Booleanos para que los Usuarios Ejecuten Aplicaciones”</a> for information about allowing and preventing users from executing applications in their home directories and <code class="filename">/tmp/</code>.
+		</div></div><div class="footnotes"><br /><hr width="100" align="left" /><div class="footnote"><p><sup>[<a id="ftn.id730926" href="#id730926" class="para">6</a>] </sup>
+						When using other policies, such as MLS, other roles may be used, for example, <code class="computeroutput">secadm_r</code>.
+					</p></div><div class="footnote"><p><sup>[<a id="ftn.id792174" href="#id792174" class="para">7</a>] </sup>
+						When using other policies, such as MLS, other roles may also be used, for example, <code class="computeroutput">secadm_r</code>.
 					</p></div></div></div><div xml:lang="es-ES" class="chapter" title="Capítulo 5. Trabajando con SELinux" id="chap-Security-Enhanced_Linux-Working_with_SELinux" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 5. Trabajando con SELinux</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Packages">5.1. Paquetes de SELinux</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used">5.2. Qué Archivo Log se usa</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Main_Configuration_File">5.3. Archivo de Configuración Principal</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux">5.4. Habilitando y Deshabilitando SELinux</a></span></dt><dd><dl><dt><span class="section"><a href=
 "#sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Enabling_SELinux">5.4.1. Habilitando SELinux</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux">5.4.2. Deshabilitando SELinux</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes">5.5. Modos de SELinux</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans">5.6. Booleanos</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Booleans-Listing_Booleans">5.6.1. Listando los Booleanos</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Booleans-Configuring_Booleans">5.6.2. Configurando los Booleanos</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS">5.6.3. Booleanos para NFS y CIFS</a></span
 ></dt></dl></dd><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files">5.7. Contextos de SELinux - Etiquetado de Archivos</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Temporary_Changes_chcon">5.7.1. Cambios Temporales: chcon</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext">5.7.2. Cambios Persistentes: semanage fcontext</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types">5.8. Los tipos file_t y default_t</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems">5.9. Montaje de Sistemas de Archivos</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Mo
 unting_File_Systems-Context_Mounts">5.9.1. Montajes de Contexto</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Mounting_File_Systems-Changing_the_Default_Context">5.9.2. Cambio del Contexto Predeterminado</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Mounting_File_Systems-Mounting_an_NFS_File_System">5.9.3. Montando un Sistema de Archivos NFS</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Mounting_File_Systems-Multiple_NFS_Mounts">5.9.4. Montajes NFS Múltiples</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Mounting_File_Systems-Making_Context_Mounts_Persistent">5.9.5. Haciendo Persistente los Contextos de Montajes</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_">5.10. Mantención de las Etiquetas de SELinux</a></span></dt><dd><dl><dt><span class="section
 "><a href="#sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Copying_Files_and_Directories">5.10.1. Copia de Directorios y Archivos</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Moving_Files_and_Directories">5.10.2. Movimiento de Archivos y Directorios</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context">5.10.3. Chequeando el Contexto SELinux Predeterminado</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_tar">5.10.4. Archivando archivos con tar</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_star">5.10.5. Archivando archivos con tar</a></span></dt></dl></dd></dl></div><div class="para">
-		Las siguientes secciones dan un breve repaso de los paquetes de SELinux principales en Fedora; instalación y actualización de paquetes; qué archivos de registro se usan; el archivo de configuración principal de SELinux; habilitación y deshabilitación de SELinux; modos de SELinux; configuración de Booleanos; cambios temporales y permanentes de etiquetas de archivos y directorios; superposición de las etiquetas de sistemas de archivos con el comando <code class="command">mount</code>; montaje de sistemas de archivos NFS; y cómo preservar contextos de SELinux cuando se copia y compacta archivos y directorios.
+		The following sections give a brief overview of the main SELinux packages in Fedora; installing and updating packages; which log files are used; the main SELinux configuration file; enabling and disabling SELinux; SELinux modes; configuring Booleans; temporarily and persistently changing file and directory labels; overriding file system labels with the <code class="command">mount</code> command; mounting NFS file systems; and how to preserve SELinux contexts when copying and archiving files and directories.
 	</div><div class="section" title="5.1. Paquetes de SELinux" id="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Packages"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.1. Paquetes de SELinux</h2></div></div></div><div class="para">
-			In Fedora, the SELinux packages are installed by default in a full installation, unless they are manually excluded during installation. If performing a minimal installation in text mode, the <span class="package">policycoreutils-python</span> package will not be installed by default. Also, by default, SELinux targeted policy is used, and SELinux runs in enforcing mode. The following is a brief description of the main SELinux packages:
-		</div><div class="para">
-			<span class="package">policycoreutils-python</span>: provides utilities such as <code class="command">semanage</code>, <code class="command">audit2allow</code>, <code class="command">audit2why</code> and <code class="command">chcat</code>, for operating and managing SELinux.
+			In Fedora, the SELinux packages are installed by default, unless they are manually excluded during installation. By default, SELinux targeted policy is used, and SELinux runs in enforcing mode. The following is a brief description of the main SELinux packages:
 		</div><div class="para">
-			<span class="package">policycoreutils</span>: provides utilities such as <code class="command">restorecon</code>, <code class="command">secon</code>, <code class="command">setfiles</code>, <code class="command">semodule</code>, <code class="command">load_policy</code>, and <code class="command">setsebool</code>, for operating and managing SELinux.
+			<span class="package">policycoreutils</span>: provee utilitarios, tales como <code class="command">semanage</code>, <code class="command">restorecon</code>, <code class="command">audit2allow</code>, <code class="command">semodule</code>, <code class="command">load_policy</code> y <code class="command">setsebool</code>, para la operación y administración de SELinux.
 		</div><div class="para">
 			<span class="package">policycoreutils-gui</span>: provee <code class="command">system-config-selinux</code>, una herramienta gráfica para la administración de SELinux.
 		</div><div class="para">
@@ -668,32 +659,32 @@ unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
 		</div><div class="para">
 			<span class="package">setroubleshoot-server</span>: traduce mensajes de negaciones, producidos cuando el acceso es denegado por SELinux, en descripciones detalladas que se ven con <code class="command">sealert</code> (que se provee en este paquete).
 		</div><div class="para">
-			<span class="package">setools</span>, <span class="package">setools-gui</span>, and <span class="package">setools-console</span>: these packages provide the <a href="http://oss.tresys.com/projects/setools">Tresys Technology SETools distribution</a>, a number of tools and libraries for analyzing and querying policy, audit log monitoring and reporting, and file context management<sup>[<a id="id867449" href="#ftn.id867449" class="footnote">8</a>]</sup>. The <span class="package">setools</span> package is a meta-package for SETools. The <span class="package">setools-gui</span> package provides the <code class="command">apol</code>, <code class="command">seaudit</code>, and <code class="command">sediffx</code> tools. The <span class="package">setools-console</span> package provides the <code class="command">seaudit-report</code>, <code class="command">sechecker</code>, <code class="command">sediff</code>, <code class="command">seinfo</code>, <code class="command">sesearch</cod
 e>, <code class="command">findcon</code>, <code class="command">replcon</code>, and <code class="command">indexcon</code> command line tools. Refer to the <a href="http://oss.tresys.com/projects/setools">Tresys Technology SETools</a> page for information about these tools.
+			<span class="package">setools</span>, <span class="package">setools-gui</span>, and <span class="package">setools-console</span>: these packages provide the <a href="http://oss.tresys.com/projects/setools">Tresys Technology SETools distribution</a>, a number of tools and libraries for analyzing and querying policy, audit log monitoring and reporting, and file context management<sup>[<a id="id703826" href="#ftn.id703826" class="footnote">8</a>]</sup>. The <span class="package">setools</span> package is a meta-package for SETools. The <span class="package">setools-gui</span> package provides the <code class="command">apol</code>, <code class="command">seaudit</code>, and <code class="command">sediffx</code> tools. The <span class="package">setools-console</span> package provides the <code class="command">seaudit-report</code>, <code class="command">sechecker</code>, <code class="command">sediff</code>, <code class="command">seinfo</code>, <code class="command">sesearch</cod
 e>, <code class="command">findcon</code>, <code class="command">replcon</code>, and <code class="command">indexcon</code> command line tools. Refer to the <a href="http://oss.tresys.com/projects/setools">Tresys Technology SETools</a> page for information about these tools.
 		</div><div class="para">
 			<span class="package">libselinux-utils</span>: provee las herramientas <code class="command">avcstat</code>, <code class="command">getenforce</code>, <code class="command">getsebool</code>, <code class="command">matchpathcon</code>, <code class="command">selinuxconlist</code>, <code class="command">selinuxdefcon</code>, <code class="command">selinuxenabled</code>, <code class="command">setenforce</code>, <code class="command">togglesebool</code>.
 		</div><div class="para">
 			<span class="package">mcstrans</span>: traduce niveles, tales como <code class="computeroutput">s0-s0:c0.c1023</code>, a una forma legible como <code class="computeroutput">SystemLow-SystemHigh</code>. Este paquete no se instala por defecto.
 		</div><div class="para">
-			Para instalar paquetes en Fedora, como usuario root de Linux ejecute el comando <code class="command">yum install <em class="replaceable"><code>nombre-de-paquete</code></em></code>. Por ejemplo, para instalar el paquete <span class="package">mcstrans</span>, ejecute el comando <code class="command">yum install mcstrans</code>. Para actualizar todos los paquetes instalados en Fedora, ejecute el comando <code class="command">yum update</code>.
+			To install packages in Fedora, as the Linux root user, run the <code class="command">yum install <em class="replaceable"><code>package-name</code></em></code> command. For example, to install the <span class="package">mcstrans</span> package, run the <code class="command">yum install mcstrans</code> command. To upgrade all installed packages in Fedora, run the <code class="command">yum update</code> command.
 		</div><div class="para">
-			Vaya a <a href="http://docs.fedoraproject.org/yum/en/">Administración de Software con yum</a><sup>[<a id="id2496212" href="#ftn.id2496212" class="footnote">9</a>]</sup> para más información sobre el uso de <code class="command">yum</code> para administrar paquetes.
+			Vaya a <a href="http://docs.fedoraproject.org/yum/en/">Administración de Software con yum</a><sup>[<a id="id800959" href="#ftn.id800959" class="footnote">9</a>]</sup> para más información sobre el uso de <code class="command">yum</code> para administrar paquetes.
 		</div><div class="note"><h2>Nota</h2><div class="para">
 				En versiones anteriores de Fedora, el paquete <span class="package">selinux-policy-devel</span> es necesario cuando se crea un módulo de política local con <code class="command">audit2allow -M</code>.
 			</div></div></div><div class="section" title="5.2. Qué Archivo Log se usa" id="sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.2. Qué Archivo Log se usa</h2></div></div></div><div class="para">
-			En Fedora 13, los paquetes <span class="package">dbus</span>, <span class="package">setroubleshoot-server</span> y <span class="package">audit</span> se instalan si no son eliminados de la selección de paquetes predeterminada.
+			In Fedora 13, the <span class="package">dbus</span>, <span class="package">setroubleshoot-server</span> and <span class="package">audit</span> packages are installed if packages are not removed from the default package selection.
 		</div><div class="para">
 			Los mensajes de negación de SELinux, tales como el siguiente, se escriben por defecto en <code class="filename">/var/log/audit/audit.log</code>:
 		</div><pre class="screen">type=AVC msg=audit(1223024155.684:49): avc:  denied  { getattr } for  pid=2000 comm="httpd" path="/var/www/html/file1" dev=dm-0 ino=399185 scontext=unconfined_u:system_r:httpd_t:s0 tcontext=system_u:object_r:samba_share_t:s0 tclass=file
 
 </pre><div class="para">
-			También, si <code class="systemitem">setroubleshootd</code> está ejecutándose, los mensajes de negación desde <code class="filename">/var/log/audit/audit.log</code> se traducen a una forma más fácil de leer en <code class="filename">/var/log/messages</code>:
+			Also, if <code class="systemitem">setroubleshootd</code> is running, denial messages from <code class="filename">/var/log/audit/audit.log</code> are translated to an easier-to-read form and sent to <code class="filename">/var/log/messages</code>:
 		</div><pre class="screen">May  7 18:55:56 localhost setroubleshoot: SELinux is preventing httpd (httpd_t) "getattr" to /var/www/html/file1 (samba_share_t). For complete SELinux messages. run sealert -l de7e30d6-5488-466d-a606-92c9f40d316d
 
 </pre><div class="para">
 			In Fedora 13, <code class="systemitem">setroubleshootd</code> no longer constantly runs as a service, however it is still used to analyze the AVC messages. Two new programs act as a method to start setroubleshoot when needed: <code class="systemitem">sedispatch</code> and <code class="systemitem">seapplet</code>. <code class="systemitem">sedispatch</code> runs as part of the audit subsystem, and via <code class="systemitem">dbus</code>, sends a message when an AVC denial occurs, which will go straight to <code class="systemitem">setroubleshootd</code> if it is already running, or it will start <code class="systemitem">setroubleshootd</code> if it is not running. <code class="systemitem">seapplet</code> is a tool which runs in the system's toolbar, waiting for dbus messages in <code class="systemitem">setroubleshootd</code>, and will launch the notification bubble, allowing the user to review the denial.
 		</div><div class="para">
 			Los mensajes de negación se envían a una ubicación distinta, dependiendo de cuáles demonios se están ejecutando:
-		</div><div class="segmentedlist"><table border="0"><thead><tr class="segtitle"><th>Demonio</th><th>Ubicación del Log</th></tr></thead><tbody><tr class="seglistitem"><td class="seg">auditd activado</td><td class="seg"><code class="filename">/var/log/audit/audit.log</code></td></tr><tr class="seglistitem"><td class="seg">auditd desactivado; rsyslogd activado</td><td class="seg"><code class="filename">/var/log/messages</code></td></tr><tr class="seglistitem"><td class="seg">rsyslogd y auditd activado</td><td class="seg"><code class="filename">/var/log/audit/audit.log</code>. Mensajes de negación legibles que también se envían a <code class="filename">/var/log/messages</code></td></tr></tbody></table></div><div class="formalpara"><h5 class="formalpara">Iniciando Demonios Automáticamente</h5>
+		</div><div class="segmentedlist"><table border="0"><thead><tr class="segtitle"><th>Daemon</th><th>Log Location</th></tr></thead><tbody><tr class="seglistitem"><td class="seg">auditd on</td><td class="seg"><code class="filename">/var/log/audit/audit.log</code></td></tr><tr class="seglistitem"><td class="seg">auditd off; rsyslogd on</td><td class="seg"><code class="filename">/var/log/messages</code></td></tr><tr class="seglistitem"><td class="seg">rsyslogd and auditd on</td><td class="seg"><code class="filename">/var/log/audit/audit.log</code>. Easier-to-read denial messages also sent to <code class="filename">/var/log/messages</code></td></tr></tbody></table></div><div class="formalpara" id="form-Security-Enhanced_Linux-Which_Log_File_is_Used-Starting_Daemons_Automatically"><h5 class="formalpara">Iniciando Demonios Automáticamente</h5>
 				Para configurar los demonios <code class="systemitem">auditd</code>, <code class="systemitem">rsyslogd</code>, y <code class="systemitem">setroubleshootd</code> para que inicien automáticamente al arrancar, corra los siguientes comandos como usuario root de Linux:
 			</div><pre class="screen">/sbin/chkconfig --levels 2345 auditd on
 
@@ -724,9 +715,9 @@ SELINUX=enforcing
 #       mls - Multi Level Security protection.
 SELINUXTYPE=targeted
 
-</pre><div class="variablelist"><dl><dt><span class="term"><code class="computeroutput">SELINUX=obediente</code></span></dt><dd><div class="para">
+</pre><div class="variablelist"><dl><dt><span class="term"><code class="computeroutput">SELINUX=enforcing</code></span></dt><dd><div class="para">
 						La opción <code class="option">SELINUX</code> pone el modo en el que corre SELinux. SELinux tiene tres modos: obediente, permisivo y deshabilitado. Cuando se usa modo obediente, la política de SELinux es aplicada y SELinux niega el acceso basándose en las reglas de políticas de SELinux. Los mensajes de negación se guardan. Cuando se usa modo permisivo, la política de SELinux no es obediente. Los mensajes son guardados. SELinux no niega el acceso, pero se guardan las negaciones de acciones que hubieran sido negadas si SELinux estaba en modo obediente. Cuando se usa el modo deshabilitado, SELinux está deshabilitado (el módulo de SELinux no se registra con el kernel de Linux), y sólo se usan las reglas DAC.
-					</div></dd><dt><span class="term"><code class="computeroutput">SELINUXTYPE=destinado</code></span></dt><dd><div class="para">
+					</div></dd><dt><span class="term"><code class="computeroutput">SELINUXTYPE=targeted</code></span></dt><dd><div class="para">
 						La opción <code class="option">SELINUXTYPE</code> pone la política SELinux a usar. La política Destinada es la predeterminada. Sólo cambie esta opción si quiere usar la política MLS. Para usar la política MLS, instale el paquete <span class="package">selinux-policy-mls</span>; configure <code class="option">SELINUXTYPE=mls</code> en <code class="filename">/etc/selinux/config</code>; y reinicie su sistema.
 					</div></dd></dl></div><div class="important"><h2>Importante</h2><div class="para">
 				Cuando los sistemas corren con SELinux en modo permisivo o deshabilitado, los usuarios tiene permiso para etiquetar los archivos incorrectamente. También, los archivos creados con SELinux deshabilitado no son etiquetados. Esto causa problemas cuando se cambia a modo obediente. Para prevenir el etiquetado incorrecto o la falta de etiquetado, los sistemas de archivos son automáticamente reetiquetados cuando se cambie desde el modo deshabilitado al modo permisivo u obediente.
@@ -748,7 +739,7 @@ Policy version:                 23
 Policy from config file:        targeted
 
 </pre><div class="para">
-			<code class="computeroutput">Estado de SELinux: activado</code> se devuelve cuando SELinux está activado. <code class="computeroutput">Modo actual: obediente</code> se devuelve cuando SELinux corre en modo obediente. <code class="computeroutput">Política desde el archivo de configuración: destinado</code> se devuelve cuando la política destinada de SELinux está en uso.
+			<code class="computeroutput">SELinux status: enabled</code> is returned when SELinux is enabled. <code class="computeroutput">Current mode: enforcing</code> is returned when SELinux is running in enforcing mode. <code class="computeroutput">Policy from config file: targeted</code> is returned when the SELinux targeted policy is used.
 		</div><div class="section" title="5.4.1. Habilitando SELinux" id="sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Enabling_SELinux"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.4.1. Habilitando SELinux</h3></div></div></div><div class="para">
 				En sistemas con SELinux deshabilitado, la opción <code class="computeroutput">SELINUX=disabled</code> se configura en <code class="filename">/etc/selinux/config</code>:
 			</div><pre class="screen"># This file controls the state of SELinux on the system.
@@ -864,7 +855,7 @@ Disabled
 				</div></li></ul></div><div class="para">
 			Use el comando <code class="command">/usr/sbin/setenforce</code> para cambiar entre los modos obediente y permisivo. Los cambios hechos con <code class="command">/usr/sbin/setenforce</code> no sobreviven a una reiniciada. Para cambiar a modo obediente, como usuario root de Linux, ejecute el comando <code class="command">/usr/sbin/setenforce 1</code>. Para cambiar a modo permisivo, ejecute el comando <code class="command">/usr/sbin/setenforce 0</code>. Use el comando <code class="command">/usr/sbin/getenforce</code> para ver el modo de SELinux actual.
 		</div><div class="para">
-			Los cambios de modo persistentes se cubren en <a class="xref" href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux" title="5.4. Habilitando y Deshabilitando SELinux">Sección 5.4, “Habilitando y Deshabilitando SELinux”</a>.
+			Persistent mode changes are covered in <a class="xref" href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux" title="5.4. Habilitando y Deshabilitando SELinux">Sección 5.4, “Habilitando y Deshabilitando SELinux”</a>.
 		</div></div><div class="section" title="5.6. Booleanos" id="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.6. Booleanos</h2></div></div></div><div class="para">
 			Los booleanos permiten cambiar partes de la política de SELinux en tiempo de ejecución, sin ningún conocimiento sobre la escritura de políticas de SELinux. Esto permite cambios, como permitir el acceso de servicios a sistemas de archivo NFS, sin recargar o recompilar la política de SELinux.
 		</div><div class="section" title="5.6.1. Listando los Booleanos" id="sect-Security-Enhanced_Linux-Booleans-Listing_Booleans"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.6.1. Listando los Booleanos</h3></div></div></div><div class="para">
@@ -931,7 +922,7 @@ httpd_can_network_connect_db --&gt; on
 				Dependiendo en la configuración de la política, los servicios pueden tener bloqueado la lectura a archivos con la etiqueta de los tipos <code class="computeroutput">nfs_t</code> o <code class="computeroutput">cifs_t</code>. Esto puede prevenir que los sistemas de archivo etiquetados con estas etiquetas se monten y sean leídos o exportados por otros servicios. Hay Booleanos que se pueden poner en 1 o 0 para controlar qué servicios pueden acceder los tipos <code class="computeroutput">nfs_t</code> y <code class="computeroutput">cifs_t</code>.
 			</div><div class="para">
 				Los comandos <code class="command">setsebool</code> y <code class="command">semanage</code> se deben ejecutar como usuario root de Linux. El comando <code class="command">setsebool -P</code> hace persistentes a los cambios. No use la opción <code class="option">-P</code> si no quiere que los cambios persistan entre reiniciadas:
-			</div><div class="formalpara"><h5 class="formalpara">Servidor HTTP Apache</h5>
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Booleans_for_NFS_and_CIFS-Apache_HTTP_Server"><h5 class="formalpara">Servidor HTTP Apache</h5>
 					Para permitir el acceso a sistemas de archivo NFS (archivos etiquetados con el tipo <code class="computeroutput">nfs_t</code>):
 				</div><div class="para">
 				<code class="command">/usr/sbin/setsebool -P httpd_use_nfs on</code>
@@ -939,11 +930,11 @@ httpd_can_network_connect_db --&gt; on
 				Para permitir el acceso a sistemas de archivos SAMBA (archivos etiquetados con el tipo <code class="computeroutput">cifs_t</code>):
 			</div><div class="para">
 				<code class="command">/usr/sbin/setsebool -P httpd_use_cifs on</code>
-			</div><div class="formalpara"><h5 class="formalpara">Samba</h5>
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Booleans_for_NFS_and_CIFS-Samba"><h5 class="formalpara">Samba</h5>
 					Para exportar sistemas de archivo NFS:
 				</div><div class="para">
 				<code class="command">/usr/sbin/setsebool -P samba_share_nfs on</code>
-			</div><div class="formalpara"><h5 class="formalpara">FTP (<code class="systemitem">vsftpd</code>)</h5>
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Booleans_for_NFS_and_CIFS-FTP_vsftpd"><h5 class="formalpara">FTP (<code class="systemitem">vsftpd</code>)</h5>
 					Para permitir el acceso a sistemas de archivo NFS:
 				</div><div class="para">
 				<code class="command">/usr/sbin/setsebool -P allow_ftpd_use_nfs on</code>
@@ -951,7 +942,7 @@ httpd_can_network_connect_db --&gt; on
 				Para permitir el acceso a sistemas de archivo Samba:
 			</div><div class="para">
 				<code class="command">/usr/sbin/setsebool -P allow_ftpd_use_cifs on</code>
-			</div><div class="formalpara"><h5 class="formalpara">Otros Servicios</h5>
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Booleans_for_NFS_and_CIFS-Other_Services"><h5 class="formalpara">Otros Servicios</h5>
 					Para una lista de los Booleanos relacionados con NFS para otros servicios:
 				</div><div class="para">
 				<code class="command">/usr/sbin/semanage boolean -l | grep nfs</code>
@@ -960,11 +951,11 @@ httpd_can_network_connect_db --&gt; on
 			</div><div class="para">
 				<code class="command">/usr/sbin/semanage boolean -l | grep cifs</code>
 			</div><div class="note"><h2>Nota</h2><div class="para">
-					Estos Booleanos existen en la política de SELinux tal cual fueron puestos en Fedora 13. Pueden no existir en la política puesta en otras versiones de Fedora o de otros sistemas operativos.
+					These Booleans exist in SELinux policy as shipped with Fedora 13. They may not exist in policy shipped with other versions of Fedora or other operating systems.
 				</div></div><div class="para">
-				Refer to the SELinux Managing Confined Services Guide at <a href="http://docs.fedoraproject.org">http://docs.fedoraproject.org</a> for more information regarding SELinux Booleans.
+				Refer to the SELinux Managing Confined Services Guide:<a href="http://docs.fedoraproject.org/selinux-managing-confined-services-guide">http://docs.fedoraproject.org/selinux-managing-confined-services-guide</a> for more information relating to SELinux Booleans.
 			</div></div></div><div class="section" title="5.7. Contextos de SELinux - Etiquetado de Archivos" id="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.7. Contextos de SELinux - Etiquetado de Archivos</h2></div></div></div><div class="para">
-			En sistemas que corren SELinux, todos los procesos y archivos son etiquetados con una etiqueta que contiene información de seguridad relevante. Esta información se llama contexto de SELinux. Para archivos, esto se ve usando el comando <code class="command">ls -Z</code>:
+			On systems running SELinux, all processes and files are labeled in a way that represents security-relevant information. This information is called the SELinux context. For files, this is viewed using the <code class="command">ls -Z</code> command:
 		</div><pre class="screen">$ ls -Z file1
 -rw-rw-r--  user1 group1 unconfined_u:object_r:user_home_t:s0 file1
 
@@ -973,15 +964,15 @@ httpd_can_network_connect_db --&gt; on
 		</div><div class="para">
 			Hay muchos comandos para la administración del contexto de archivos de SELinux, como por ejemplo <code class="command">chcon</code>, <code class="command">semanage fcontext</code>, y <code class="command">restorecon</code>.
 		</div><div class="section" title="5.7.1. Cambios Temporales: chcon" id="sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Temporary_Changes_chcon"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.7.1. Cambios Temporales: chcon</h3></div></div></div><div class="para">
-				El comando <code class="command">chcon</code> cambia el contexto SELinux de los archivos. Estos cambios no sobreviven un reetiquetado del sistema de archivo, o la ejecución del comando <code class="command">/sbin/restorecon</code>. La política de SELinux controla si los usuarios pueden modificar el contexto SELinux de algún archivo. Cuando se usa <code class="command">chcon</code>, los usuarios proveen toda o parte del contexto SELinux a cambiar. Un tipo de archivo incorrecto es una causa común de negación de acceso de SELinux.
-			</div><div class="formalpara"><h5 class="formalpara">Referencia Rápida</h5>
+				The <code class="command">chcon</code> command changes the SELinux context for files. However, changes made with the <code class="command">chcon</code> command do not survive a file system relabel, or the execution of the <code class="command">/sbin/restorecon</code> command. SELinux policy controls whether users are able to modify the SELinux context for any given file. When using <code class="command">chcon</code>, users provide all or part of the SELinux context to change. An incorrect file type is a common cause of SELinux denying access.
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Temporary_Changes_chcon-Quick_Reference"><h5 class="formalpara">Referencia Rápida</h5>
 					<div class="itemizedlist"><ul><li class="listitem"><div class="para">
 								Ejecute el comando <code class="command">chcon -t <em class="replaceable"><code>tipo</code></em> <em class="replaceable"><code>nombre-de-archivo</code></em></code> para cambiar el tipo de archivo, donde <em class="replaceable"><code>tipo</code></em> es el tipo, por ejemplo <code class="computeroutput">httpd_sys_content_t</code>, y <em class="replaceable"><code>nombre-de-archivo</code></em> es un nombre de archivo o de directorio.
 							</div></li><li class="listitem"><div class="para">
 								Ejecute el comando <code class="command">chcon -R -t <em class="replaceable"><code>tipo</code></em> <em class="replaceable"><code>nombre-de-directorio</code></em></code> para cambiar el tipo de un directorio y su contenido, donde <em class="replaceable"><code>tipo</code></em> es el tipo, por ejemplo <code class="computeroutput">httpd_sys_content_t</code>, y <em class="replaceable"><code>nombre-de-directorio</code></em> es un nombre de directorio.
 							</div></li></ul></div>
 
-				</div><div class="formalpara"><h5 class="formalpara">Changing a File's or Directory's Type</h5>
+				</div><div class="formalpara" id="form-Security-Enhanced_Linux-Temporary_Changes_chcon-Changing_a_Files_or_Directorys_Type"><h5 class="formalpara">Changing a File's or Directory's Type</h5>
 					El siguiente ejemplo muestra el cambio de tipo solamente en el contexto de SELinux:
 				</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
 						Ejecute el comando <code class="command">cd</code> sin argumentos para cambiar a su directorio de inicio.
@@ -991,7 +982,7 @@ httpd_can_network_connect_db --&gt; on
 -rw-rw-r--  user1 group1 unconfined_u:object_r:user_home_t:s0 file1
 
 </pre><div class="para">
-						En este ejemplo, el contexto SELinux del <code class="filename">archivo1</code> incluye el usuario <code class="computeroutput">unconfined_u</code>, el rol <code class="computeroutput">object_r</code>, el tipo <code class="computeroutput">user_home_t</code>, y el nivel <code class="computeroutput">s0</code>. Para una descripción de cada parte del contexto SELinux, vaya a <a class="xref" href="#chap-Security-Enhanced_Linux-SELinux_Contexts" title="Capítulo 3. Contextos de SELinux">Capítulo 3, <i>Contextos de SELinux</i></a>.
+						In this example, the SELinux context for <code class="filename">file1</code> includes the SELinux <code class="computeroutput">unconfined_u</code> user, <code class="computeroutput">object_r</code> role, <code class="computeroutput">user_home_t</code> type, and the <code class="computeroutput">s0</code> level. For a description of each part of the SELinux context, refer to <a class="xref" href="#chap-Security-Enhanced_Linux-SELinux_Contexts" title="Capítulo 3. Contextos de SELinux">Capítulo 3, <i>Contextos de SELinux</i></a>.
 					</div></li><li class="listitem"><div class="para">
 						EJecute el comando <code class="command">chcon -t samba_share_t archivo1</code> para cambiar el tipo a <code class="computeroutput">samba_share_t</code>. La opción <code class="option">-t</code> sólo cambia el tipo. Vea el cambio con <code class="command">ls -Z archivo1</code>:
 					</div><pre class="screen">$ ls -Z file1 
@@ -1006,7 +997,7 @@ restorecon reset file1 context unconfined_u:object_r:samba_share_t:s0-&gt;system
 						En este ejemplo, el tipo previo <code class="computeroutput">samba_share_t</code>, se restaura al tipo correcto <code class="computeroutput">user_home_t</code>. Cuando se usa la política destinada (la política SELinux predeterminada en Fedora 11), el comando <code class="command">/sbin/restorecon</code> lee los archivos en el directorio <code class="filename">/etc/selinux/targeted/contexts/files/</code> para ver qué contexto de SELinux deben tener los archivos.
 					</div></li></ol></div><div class="para">
 				El ejemplo en esta sección funciona igual para directorios, por ejemplo, si <code class="filename">archivo1</code> fuera un directorio.
-			</div><div class="formalpara"><h5 class="formalpara">Cambio de un Directorio y sus Tipos de Contenidos</h5>
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Temporary_Changes_chcon-Changing_a_Directory_and_its_Contents_Types"><h5 class="formalpara">Cambio de un Directorio y sus Tipos de Contenidos</h5>
 					The following example demonstrates creating a new directory, and changing the directory's file type (along with its contents) to a type used by the Apache HTTP Server. The configuration in this example is used if you want Apache HTTP Server to use a different document root (instead of <code class="filename">/var/www/html/</code>):
 				</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
 						Como usuario root de Linux, ejecute el comando <code class="command">mkdir /web</code> para crear un directorio nuevo, y luego el comando <code class="command">touch /web/archivo{1,2,3}</code> para crear 3 archivos vacíos (<code class="filename">archivo1</code>, <code class="filename">archivo2</code> y <code class="filename">archivo3</code>). El directorio <code class="filename">/web/</code> y los archivos en él son etiquetados con el tipo <code class="computeroutput">default_t</code>:
@@ -1041,13 +1032,13 @@ restorecon reset /web/file1 context unconfined_u:object_r:httpd_sys_content_t:s0
 					La Obligación de Tipo es el control de permisos principal usado en la política destinada de SELinux. Para la mayor parte, los usuarios y roles de SELinux se pueden ignorar.
 				</div></div></div><div class="section" title="5.7.2. Cambios Persistentes: semanage fcontext" id="sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.7.2. Cambios Persistentes: semanage fcontext</h3></div></div></div><div class="para">
 				El comando <code class="command">/usr/sbin/semanage fcontext</code> cambia el contexto SELinux de los archivos. Cuando se usa la política destinada, los cambios hechos con este comando se agregan al archivo <code class="filename">/etc/selinux/targeted/contexts/files/file_contexts</code> si los cambios so para archivos que están en <code class="filename">file_contexts</code>, se agregan a <code class="filename">file_contexts.local</code> para archivos nuevos y directorios, como sería al crear un directorio <code class="filename">/web/</code> nuevo. <code class="command">setfiles</code>, que se usa cuando el sistema de archivo es reetiquetado, y <code class="command">/sbin/restorecon</code>, que restaura los contextos de SELinux predeterminados, leen estos archivos, Lo que significa que los cambios hechos por <code class="command">/usr/sbin/semanage fcontext</code> son persistentes, aún si el sistema de archivo es reetiquetado. La política de SELinux controla si los u
 suarios pueden modificar el contexto de SELinux para cualquier archivo dado.
-			</div><div class="formalpara"><h5 class="formalpara">Referencia Rápida</h5>
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Persistent_Changes_semanage_fcontext-Quick_Reference"><h5 class="formalpara">Referencia Rápida</h5>
 					Para hacer que los cambios de contexto de SELinux sobrevivan un reetiquetado del sistema de archivo:
 				</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
 						Ejecute el comando <code class="command">/usr/sbin/semanage fcontext -a <em class="replaceable"><code>opciones</code></em> <em class="replaceable"><code>nombre-de-archivo</code></em>|<em class="replaceable"><code>nombre-de-directorio</code></em></code>, recuerde usar la dirección completa del archivo o del directorio.
 					</div></li><li class="listitem"><div class="para">
 						Ejecute el comando <code class="command">/sbin/restorecon -v <em class="replaceable"><code>nombre-de-archivo</code></em>|<em class="replaceable"><code>nombre-de-directorio</code></em></code> para aplicar los cambios de contexto.
-					</div></li></ol></div><div class="formalpara"><h5 class="formalpara">Changing a File's Type</h5>
+					</div></li></ol></div><div class="formalpara" id="form-Security-Enhanced_Linux-Persistent_Changes_semanage_fcontext-Changing_a_Files_Type"><h5 class="formalpara">Changing a File's Type</h5>
 					The following example demonstrates changing a file's type, and no other attributes of the SELinux context:
 				</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
 						Como usuario root de Linux, ejecute el comando <code class="command">touch /etc/archivo1</code> para crear un archivo nuevo. Por defecto, los archivos recién creados en el directorio <code class="filename">/etc/</code> se etiquetan con el tipo <code class="computeroutput">etc_t</code>:
@@ -1073,7 +1064,7 @@ restorecon reset /etc/file1 context unconfined_u:object_r:etc_t:s0-&gt;system_u:
 						Como usuario root de Linux, ejecute el comando <code class="command">rm -i /etc/archivo1</code> para borrar el <code class="filename">archivo1</code>.
 					</div></li><li class="listitem"><div class="para">
 						Como usuario root de Linux, ejecute el comando <code class="command">/usr/sbin/semanage fcontext -d /etc/archivo1</code> para eliminar el contexto agregado para <code class="filename">/etc/archivo1</code>. Cuando el contexto se elimina, ejecutando <code class="command">restorecon</code> cambia el tipo a <code class="computeroutput">etc_t</code>, en vez de <code class="computeroutput">samba_share_t</code>.
-					</div></li></ol></div><div class="formalpara"><h5 class="formalpara">Changing a Directory's Type</h5>
+					</div></li></ol></div><div class="formalpara" id="form-Security-Enhanced_Linux-Persistent_Changes_semanage_fcontext-Changing_a_Directorys_Type"><h5 class="formalpara">Changing a Directory's Type</h5>
 					The following example demonstrates creating a new directory and changing that directory's file type, to a type used by Apache HTTP Server:
 				</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
 						Como usuario root de LInux, ejecute el comando <code class="command">mkdir /web</code> para crear un directorio nuevo. Este directorio se etiqueta con el tipo <code class="computeroutput">default_t</code>:
@@ -1103,7 +1094,7 @@ restorecon reset /web context unconfined_u:object_r:default_t:s0-&gt;system_u:ob
 						Como usuario root de Linux, ejecute el comando <code class="command">/usr/sbin/semanage fcontext -d /web</code> para borrar el contexto agregado para <code class="filename">/web/</code>.
 					</div></li><li class="listitem"><div class="para">
 						Como usuario root de Linux, ejecute el comando <code class="command">/sbin/restorecon -v /web</code> para restaurar el contexto predeterminado de SELinux.
-					</div></li></ol></div><div class="formalpara"><h5 class="formalpara">Cambio de un Directorio y sus Tipos de Contenidos</h5>
+					</div></li></ol></div><div class="formalpara" id="form-Security-Enhanced_Linux-Persistent_Changes_semanage_fcontext-Changing_a_Directory_and_its_Contents_Types"><h5 class="formalpara">Cambio de un Directorio y sus Tipos de Contenidos</h5>
 					The following example demonstrates creating a new directory, and changing the directory's file type (along with its contents) to a type used by Apache HTTP Server. The configuration in this example is used if you want Apache HTTP Server to use a different document root (instead of <code class="filename">/var/www/html/</code>):
 				</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
 						Como usuario root de Linux, ejecute el comando <code class="command">mkdir /web</code> para crear un directorio nuevo, y luego el comando <code class="command">touch /web/archivo{1,2,3}</code> para crear 3 archivos vacíos (<code class="filename">archivo1</code>, <code class="filename">archivo2</code> y <code class="filename">archivo3</code>). El directorio <code class="filename">/web/</code> y los archivos en él son etiquetados con el tipo <code class="computeroutput">default_t</code>:
@@ -1141,7 +1132,7 @@ restorecon reset /web/file1 context unconfined_u:object_r:default_t:s0-&gt;syste
 						As the Linux root user, run the <code class="command">/usr/sbin/semanage fcontext -d "/web(/.*)?"</code> command to remove the context added for <code class="computeroutput">"/web(/.*)?"</code>.
 					</div></li><li class="listitem"><div class="para">
 						Como usuario root de Linux, ejecute el comando <code class="command">/sbin/restorecon -R -v /web</code> para restaurar el contexto predeterminado de SELinux.
-					</div></li></ol></div><div class="formalpara"><h5 class="formalpara">Borrado de un Contexto agregado</h5>
+					</div></li></ol></div><div class="formalpara" id="form-Security-Enhanced_Linux-Persistent_Changes_semanage_fcontext-Deleting_an_added_Context"><h5 class="formalpara">Borrado de un Contexto agregado</h5>
 					El siguiente ejemplo muestra el agregado y su eliminación del contexto de SELinux:
 				</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
 						Como usuario root de Linux, ejecute el comando <code class="command">/usr/sbin/semanage fcontext -a -t httpd_sys_content_t /prueba</code>. El directorio <code class="filename">/prueba/</code> no tiene que existir. Este comando agrega el siguiente contexto a <code class="filename">/etc/selinux/targeted/contexts/files/file_contexts.local</code>:
@@ -1154,7 +1145,7 @@ restorecon reset /web/file1 context unconfined_u:object_r:default_t:s0-&gt;syste
 </pre><div class="para">
 						Siendo la primera parte <code class="computeroutput">/prueba</code>. Para evitar que el directorio <code class="filename">/prueba/</code> se etiquete con <code class="computeroutput">httpd_sys_content_t</code> después de ejecutar <code class="command">/sbin/restorecon</code>, o después de un reetiquetado del sistema, ejecute el siguiente comando como usuario root de Linux para eliminar el contexto de <code class="filename">file_contexts.local</code>:
 					</div><div class="para">
-						<code class="command">/usr/sbin/semanage fcontext -d /prueba</code>
+						<code class="command">/usr/sbin/semanage fcontext -d /test</code>
 					</div></li></ol></div><div class="para">
 				Si el contexto es parte de una expresión regular, por ejemplo <code class="computeroutput">/web(/.*)?</code>, use las comillas para encerrar la expresión regular:
 			</div><div class="para">
@@ -1164,9 +1155,9 @@ restorecon reset /web/file1 context unconfined_u:object_r:default_t:s0-&gt;syste
 			</div><div class="important"><h2>Importante</h2><div class="para">
 					Cuando se cambia el contexto de SELinux con <code class="command">/usr/sbin/semanage fcontext -a</code>, use la dirección completa del archivo o directorio para evitar etiquetar mal los archivos después de un reetiquetado del sistema de archivo, o después ejecutar el comando <code class="command">/sbin/restorecon</code>.
 				</div></div></div></div><div class="section" title="5.8. Los tipos file_t y default_t" id="sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.8. Los tipos file_t y default_t</h2></div></div></div><div class="para">
-			En sistemas de archivo que soportan atributos extendidos, cuando se accede a un archivo en disco al que le falta el contexto de SELinux, se trata como si tuviera un contexto predeterminado tal como fue definido en la política de SELinux. En políticas comunes, este conexto por defecto usa el tipo <code class="computeroutput">file_t</code>. Este debería ser el único uso de este tipo, por lo que los archivos sin un contexto en el disco se podrían distinguir en la política, y generalmente mantenerse inaccesibles a dominios confinados. El tipo <code class="computeroutput">file_t</code> no debería existir en sistemas de archivo correctamente etiquetados, porque todos los archivos en un sistema corriendo SELinux deberían tener un contexto de SELinux, y el tipo <code class="computeroutput">file_t</code> no sebería usarse en la configuración de contexto de archivos <sup>[<a id="id958694" href="#ftn.id958694" class="footnote">10</a>]</sup>.
+			For file systems that support extended attributes, when a file that lacks an SELinux context on disk is accessed, it is treated as if it had a default context as defined by SELinux policy. In common policies, this default context uses the <code class="computeroutput">file_t</code> type. This should be the only use of this type, so that files without a context on disk can be distinguished in policy, and generally kept inaccessible to confined domains. The <code class="computeroutput">file_t</code> type should not exist on correctly-labeled file systems, because all files on a system running SELinux should have an SELinux context, and the <code class="computeroutput">file_t</code> type is never used in file-context configuration<sup>[<a id="id806263" href="#ftn.id806263" class="footnote">10</a>]</sup>.
 		</div><div class="para">
-			El tipo <code class="computeroutput">default_t</code> se usa en archivos que no coinciden con ningún otro patrón en la configuración de contexto de archivo, por lo que tales archivos se pueden distinguir de aquellos que no tienen un contexto en el disco, y generalmente mantenerse inaccesibles a los dominios confinados. Si crea un directorio de alto nivel, tal como <code class="filename">/midir/</code>, este directorio puede ser etiquetado con el tipo <code class="computeroutput">default_t</code>. Si los servicios necesitan acceder a tal directorio, actualice la configuración de contextos de archivo para esta ubicación. Vaya a <a class="xref" href="#sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext" title="5.7.2. Cambios Persistentes: semanage fcontext">Sección 5.7.2, “Cambios Persistentes: semanage fcontext”</a> para más detalles sobre el agregado de un contexto para la configuración de contexto de archivos.
+			The <code class="computeroutput">default_t</code> type is used on files that do not match any other pattern in file-context configuration, so that such files can be distinguished from files that do not have a context on disk, and generally kept inaccessible to confined domains. If you create a new top-level directory, such as <code class="filename">/mydirectory/</code>, this directory may be labeled with the <code class="computeroutput">default_t</code> type. If services need access to such a directory, update the file-contexts configuration for this location. Refer to <a class="xref" href="#sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext" title="5.7.2. Cambios Persistentes: semanage fcontext">Sección 5.7.2, “Cambios Persistentes: semanage fcontext”</a> for details on adding a context to the file-context configuration.
 		</div></div><div class="section" title="5.9. Montaje de Sistemas de Archivos" id="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.9. Montaje de Sistemas de Archivos</h2></div></div></div><div class="para">
 			Por defecto, cuando un sistema de archivo que soporta atributos extendidos se monta, el contexto de seguridad para cada archivo se obtiene de atributo extendido <span class="emphasis"><em>security.selinux</em></span> del archivo. A los archivos en sistemas de archivo que no dan soporte a atributos extendidos se les asigna un único contexto de seguridad predeterminado desde la configuración de la política, basada en el tipo de sistema de archivo.
 		</div><div class="para">
@@ -1185,7 +1176,7 @@ context="system_u:object_r:httpd_sys_content_t:s0"
 			</div><div class="note"><h2>Nota</h2><div class="para">
 					Cuando se monta un sistema de archivo con la opción <code class="option">context</code>, los cambios de contexto (por usuarios y procesos) son prohibidos. Por ejemplo, ejecutando <code class="command">chcon</code> en un sistema de archivo montado con la opción <code class="option">context</code> resulta en un error de <code class="computeroutput">Operación no soportada</code>.
 				</div></div></div><div class="section" title="5.9.2. Cambio del Contexto Predeterminado" id="sect-Security-Enhanced_Linux-Mounting_File_Systems-Changing_the_Default_Context"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.9.2. Cambio del Contexto Predeterminado</h3></div></div></div><div class="para">
-				Como se mencionó en <a class="xref" href="#sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types" title="5.8. Los tipos file_t y default_t">Sección 5.8, “Los tipos file_t y default_t”</a>, en sistemas de archivo que soportan atributos extendidos, cuando se accede a un archivo en disco que le falta el contexto SELinux, se trata como si hubiera tenido el contexto predeterminado tal como se define en la política SELinux. En políticas comúnes, este contexto predeterminados usa el tipo <code class="computeroutput">file_t</code>. Si se desea usar un contexto predeterminado diferente, monte el sistema de archivo con la opción<code class="option">defcontext</code>.
+				As mentioned in <a class="xref" href="#sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types" title="5.8. Los tipos file_t y default_t">Sección 5.8, “Los tipos file_t y default_t”</a>, on file systems that support extended attributes, when a file that lacks an SELinux context on disk is accessed, it is treated as if it had a default context as defined by SELinux policy. In common policies, this default context uses the <code class="computeroutput">file_t</code> type. If it is desirable to use a different default context, mount the file system with the <code class="option">defcontext</code> option.
 			</div><div class="para">
 				El siguiente ejemplo monta un sistema de archivo recién creado (en <code class="filename">/dev/sda2</code>) en el directorio recién creado <code class="filename">/prueba/</code>. Asume que no hay reglas en <code class="filename">/etc/selinux/targeted/contexts/files/</code> que definan el contexto del directorio <code class="filename">/prueba/</code>:
 			</div><pre class="screen">
@@ -1194,7 +1185,7 @@ context="system_u:object_r:httpd_sys_content_t:s0"
 </pre><div class="para">
 				En este ejemplo:
 			</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-						the <code class="option">defcontext</code> option defines that <code class="computeroutput">system_u:object_r:samba_share_t:s0</code> is "the default security context for unlabeled files"<sup>[<a id="id2265564" href="#ftn.id2265564" class="footnote">11</a>]</sup>.
+						the <code class="option">defcontext</code> option defines that <code class="computeroutput">system_u:object_r:samba_share_t:s0</code> is "the default security context for unlabeled files"<sup>[<a id="id806542" href="#ftn.id806542" class="footnote">11</a>]</sup>.
 					</div></li><li class="listitem"><div class="para">
 						cuando sea montado, el directorio raíz (<code class="filename">/prueba/</code>) del sistema de archivo se trata como si estuviera etiquetado con el contexto especificado por <code class="option">defcontext</code> (esta etiqueta no se guarda en el disco). Esto afecta el etiquetado de archvios creados en <code class="filename">/prueba/</code>: los archivos nuevos heredan el tipo <code class="computeroutput">samba_share_t</code>, y estas etiquetas se guardan en el disco.
 					</div></li><li class="listitem"><div class="para">
@@ -1209,7 +1200,7 @@ context="system_u:object_r:httpd_sys_content_t:s0"
 </pre><div class="para">
 				Dado que los cambios de contexto no se escriben al disco para estas situaciones, el contexto especificado con la opción <code class="option">context</code> sólo se retiene si la opción <code class="option">context</code> se usa en el siguiente montaje, y si el mismo contexto se especifica.
 			</div><div class="para">
-				Como una alternativa a montar sistemas de archivo con la opción <code class="option">contexto</code>, los Booleanos se pueden activar para permitir a los servicios acceder sistemas de archivos etiquetados con el tipo <code class="computeroutput">nfs_t</code>. Vaya a <a class="xref" href="#sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS" title="5.6.3. Booleanos para NFS y CIFS">Sección 5.6.3, “Booleanos para NFS y CIFS”</a> para instrucciones sobre configuración de Booleanos para permitir a servicios acceder al tipo <code class="computeroutput">nfs_t</code>.
+				As an alternative to mounting file systems with <code class="option">context</code> options, Booleans can be turned on to allow services access to file systems labeled with the <code class="computeroutput">nfs_t</code> type. Refer to <a class="xref" href="#sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS" title="5.6.3. Booleanos para NFS y CIFS">Sección 5.6.3, “Booleanos para NFS y CIFS”</a> for instructions on configuring Booleans to allow services access to the <code class="computeroutput">nfs_t</code> type.
 			</div></div><div class="section" title="5.9.4. Montajes NFS Múltiples" id="sect-Security-Enhanced_Linux-Mounting_File_Systems-Multiple_NFS_Mounts"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.9.4. Montajes NFS Múltiples</h3></div></div></div><div class="para">
 				Cuando se monten múltiples montajes desde el mismo NFS exportado, el intento de sobreescribir el contexto de SELinux e cada montaje con un contexto diferente, resulta en fallos de los comandos de montaje subsecuentes. En el siguiente ejemplo, el servidor NFS tiene un exportado único, <code class="filename">/export</code>, que tiene dos subdirectorios, <code class="filename">web/</code> and <code class="filename">database/</code>. El siguiente comando intenta dos montajes desde un único export NFS e intenta sobreescribir el contexto para cada uno:
 			</div><pre class="screen">
@@ -1266,7 +1257,7 @@ $ ls -Z /etc/file1
 				Cuando el <code class="filename">archivo1</code> se copia a <code class="filename">/etc/</code>, si <code class="filename">/etc/archivo1</code> no existe, <code class="filename">/etc/archivo1</code> se crea como un archivo nuevo. Como se muestra en el ejemplo de arriba, <code class="filename">/etc/archivo1</code> se etiqueta con el tipo <code class="computeroutput">etc_t</code>, de acuerdo con las reglas de etiquetado predeterminadas.
 			</div><div class="para">
 				When a file is copied over an existing file, the existing file's context is preserved, unless the user specified <code class="command">cp</code> options to preserve the context of the original file, such as <code class="option">--preserve=context</code>. SELinux policy may prevent contexts from being preserved during copies.
-			</div><div class="formalpara"><h5 class="formalpara">Copia sin Preservar los Contextos de SELinux</h5>
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Copying_Files_and_Directories-Copying_Without_Preserving_SELinux_Contexts"><h5 class="formalpara">Copia sin Preservar los Contextos de SELinux</h5>
 					Cuando se copia un archivo con el comando <code class="command">cp</code>, si no se dan opciones, el tipo se hereda desde el directorio padre destino:
 				</div><pre class="screen">
 $ touch file1
@@ -1280,7 +1271,7 @@ $ ls -Z /var/www/html/file1
 
 </pre><div class="para">
 				In this example, <code class="filename">file1</code> is created in a user's home directory, and is labeled with the <code class="computeroutput">user_home_t</code> type. The <code class="filename">/var/www/html/</code> directory is labeled with the <code class="computeroutput">httpd_sys_content_t</code> type, as shown with the <code class="command">ls -dZ /var/www/html/</code> command. When <code class="filename">file1</code> is copied to <code class="filename">/var/www/html/</code>, it inherits the <code class="computeroutput">httpd_sys_content_t</code> type, as shown with the <code class="command">ls -Z /var/www/html/file1</code> command.
-			</div><div class="formalpara"><h5 class="formalpara">Preservación de los Contextos de SELinux cuando se copia</h5>
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Copying_Files_and_Directories-Preserving_SELinux_Contexts_When_Copying"><h5 class="formalpara">Preservación de los Contextos de SELinux cuando se copia</h5>
 					Use el comando <code class="command">cp --preserve=context</code> para preservar los contextos cuando se copia:
 				</div><pre class="screen">
 $ touch file1
@@ -1294,7 +1285,7 @@ $ ls -Z /var/www/html/file1
 
 </pre><div class="para">
 				In this example, <code class="filename">file1</code> is created in a user's home directory, and is labeled with the <code class="computeroutput">user_home_t</code> type. The <code class="filename">/var/www/html/</code> directory is labeled with the <code class="computeroutput">httpd_sys_content_t</code> type, as shown with the <code class="command">ls -dZ /var/www/html/</code> command. Using the <code class="option">--preserve=context</code> option preserves SELinux contexts during copy operations. As shown with the <code class="command">ls -Z /var/www/html/file1</code> command, the <code class="filename">file1</code> <code class="computeroutput">user_home_t</code> type was preserved when the file was copied to <code class="filename">/var/www/html/</code>.
-			</div><div class="formalpara"><h5 class="formalpara">Copiado y Cambio del Contexto</h5>
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Copying_Files_and_Directories-Copying_and_Changing_the_Context"><h5 class="formalpara">Copiado y Cambio del Contexto</h5>
 					Use the <code class="command">cp -Z</code> command to change the destination copy's context. The following example was performed in the user's home directory:
 				</div><pre class="screen">
 $ touch file1
@@ -1306,7 +1297,7 @@ $ rm file1 file2
 
 </pre><div class="para">
 				En este ejemplo, el contexto se define en la opción <code class="option">-Z</code>. Sin la opción <code class="option">-Z</code>, <code class="filename">archivo2</code> se etiquetaría con el contexto <code class="computeroutput">unconfined_u:object_r:user_home_t</code>.
-			</div><div class="formalpara"><h5 class="formalpara">Copia de un Archivos sobre un otro existente</h5>
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Copying_Files_and_Directories-Copying_a_File_Over_an_Existing_File"><h5 class="formalpara">Copia de un Archivos sobre un otro existente</h5>
 					When a file is copied over an existing file, the existing file's context is preserved (unless an option is used to preserve contexts). For example:
 				</div><pre class="screen">
 # touch /etc/file1
@@ -1348,7 +1339,7 @@ drwxr-xr-x  root root system_u:object_r:httpd_sys_content_t:s0 /var/www/html/
 			</div><div class="important"><h2>Importante</h2><div class="para">
 					Mover archivos y directorios con el comando <code class="command">mv</code> puede resultar en el contexto SELinux incorrecto, evitando que los procesos tales como el Servidor HTTP Apache y Samba puedan acceder a tales archivos y directorios.
 				</div></div></div><div class="section" title="5.10.3. Chequeando el Contexto SELinux Predeterminado" id="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.10.3. Chequeando el Contexto SELinux Predeterminado</h3></div></div></div><div class="para">
-				Use the <code class="command">/usr/sbin/matchpathcon</code> command to check if files and directories have the correct SELinux context. From the <span class="citerefentry"><span class="refentrytitle">matchpathcon</span>(8)</span> manual page: "<code class="command">matchpathcon</code> queries the system policy and outputs the default security context associated with the file path."<sup>[<a id="id2554139" href="#ftn.id2554139" class="footnote">12</a>]</sup>. The following example demonstrates using the <code class="command">/usr/sbin/matchpathcon</code> command to verify that files in <code class="filename">/var/www/html/</code> directory are labeled correctly:
+				Use the <code class="command">/usr/sbin/matchpathcon</code> command to check if files and directories have the correct SELinux context. From the <span class="citerefentry"><span class="refentrytitle">matchpathcon</span>(8)</span> manual page: "<code class="command">matchpathcon</code> queries the system policy and outputs the default security context associated with the file path."<sup>[<a id="id807398" href="#ftn.id807398" class="footnote">12</a>]</sup>. The following example demonstrates using the <code class="command">/usr/sbin/matchpathcon</code> command to verify that files in <code class="filename">/var/www/html/</code> directory are labeled correctly:
 			</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
 						Como usuario root de Linux, ejecute el comando <code class="command">touch /var/www/html/archivo{1,2,3}</code> para crear tres archivos (<code class="filename">archivo1</code>, <code class="filename">archivo2</code> y <code class="filename">archivo3</code>). Estos heredan el tipo <code class="computeroutput">httpd_sys_content_t</code> del directorio <code class="filename">/var/www/html/</code>:
 					</div><pre class="screen"># touch /var/www/html/file{1,2,3}
@@ -1458,18 +1449,18 @@ $ ls -lZ /test/
 						Si <code class="command">star</code> ya no se necesita, como usuario root de Linux, ejecute el comando <code class="command">yum remove star</code> para eliminar el paquete.
 					</div></li></ol></div><div class="para">
 				Refer to the <span class="citerefentry"><span class="refentrytitle">star</span>(1)</span> manual page for further information about <code class="command">star</code>.
-			</div></div></div><div class="footnotes"><br /><hr width="100" align="left" /><div class="footnote"><p><sup>[<a id="ftn.id867449" href="#id867449" class="para">8</a>] </sup>
+			</div></div></div><div class="footnotes"><br /><hr width="100" align="left" /><div class="footnote"><p><sup>[<a id="ftn.id703826" href="#id703826" class="para">8</a>] </sup>
 				Brindle, Joshua. "Re: blurb for fedora setools packages" Email to Murray McAllister. 1 November 2008. Any edits or changes in this version were done by Murray McAllister.
-			</p></div><div class="footnote"><p><sup>[<a id="ftn.id2496212" href="#id2496212" class="para">9</a>] </sup>
+			</p></div><div class="footnote"><p><sup>[<a id="ftn.id800959" href="#id800959" class="para">9</a>] </sup>
 				Administración de Software con yum, escrito por Stuart Ellis, editado por Paul W. Frields, Rodrigo Menezes y Hugo Cisneiros.
-			</p></div><div class="footnote"><p><sup>[<a id="ftn.id958694" href="#id958694" class="para">10</a>] </sup>
-				Los archivos en <code class="filename">/etc/selinux/targeted/contexts/files/</code> definen los contextos de los archivos y directorios. Los archivos en este directorio son accedidos por <code class="command">restorecon</code> y por <code class="command">setfiles</code> para restaurar al valor predeterminado los contextos de los archivos y directorios.
-			</p></div><div class="footnote"><p><sup>[<a id="ftn.id2265564" href="#id2265564" class="para">11</a>] </sup>
+			</p></div><div class="footnote"><p><sup>[<a id="ftn.id806263" href="#id806263" class="para">10</a>] </sup>
+				Files in <code class="filename">/etc/selinux/targeted/contexts/files/</code> define contexts for files and directories. Files in this directory are read by <code class="command">restorecon</code> and <code class="command">setfiles</code> to restore files and directories to their default contexts.
+			</p></div><div class="footnote"><p><sup>[<a id="ftn.id806542" href="#id806542" class="para">11</a>] </sup>
 							Morris, James. "Filesystem Labeling in SELinux". Published 1 October 2004. Accessed 14 October 2008: <a href="http://www.linuxjournal.com/article/7426">http://www.linuxjournal.com/article/7426</a>.
-						</p></div><div class="footnote"><p><sup>[<a id="ftn.id2554139" href="#id2554139" class="para">12</a>] </sup>
+						</p></div><div class="footnote"><p><sup>[<a id="ftn.id807398" href="#id807398" class="para">12</a>] </sup>
 					The <span class="citerefentry"><span class="refentrytitle">matchpathcon</span>(8)</span> manual page, as shipped with the <span class="package">libselinux-utils</span> package in Fedora, is written by Daniel Walsh. Any edits or changes in this version were done by Murray McAllister.
 				</p></div></div></div><div xml:lang="es-ES" class="chapter" title="Capítulo 6. Confinando a los Usuarios" id="chap-Security-Enhanced_Linux-Confining_Users" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 6. Confinando a los Usuarios</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Confining_Users-Linux_and_SELinux_User_Mappings">6.1. Linux y los Mapeos de Usuarios de SELinux</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Confining_Users-Confining_New_Linux_Users_useradd">6.2. Confinando Usuarios Nuevos de Linux: useradd</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Confining_Users-Confining_Existing_Linux_Users_semanage_login">6.3. Confinando Usuarios Linux Existentes: semanage login</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Confining_Users-Changing_the_Default_Mapping">6.4. Cambiand
 o el Mapeo Predeterminado</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Confining_Users-xguest_Kiosk_Mode">6.5. xguest: Modo Kiosk</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications">6.6. Booleanos para que los Usuarios Ejecuten Aplicaciones</a></span></dt></dl></div><div class="para">
-		Un número de usuarios confinados SELinux están disponibles en Fedora 13. Cada usuario Linux se mapea aun usuario SELinux vía la política de SELinux, permitiendo a los usuarios Linux heredar las restricciones sobre los usuarios SELinux, por ejemplo (dependiendo del usuairo), no poder: ejecutar el sistema de ventanas X; usar la red; ejecutar aplicaciones setuid (a menos que la política de SELinux lo permita); o ejecutar comandos <code class="command">su</code> y <code class="command">sudo</code> para volverse el usuario root de Linux. Esto ayuda a proteger el sistema del usuario. Vaya a <a class="xref" href="#sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users" title="4.3. Usuarios Confinados y no Confinados">Sección 4.3, “Usuarios Confinados y no Confinados”</a> para información adicional sobre usuarios confinados.
+		A number of confined SELinux users are available in Fedora 13. Each Linux user is mapped to an SELinux user via SELinux policy, allowing Linux users to inherit the restrictions placed on SELinux users, for example (depending on the user), not being able to: run the X Window System; use networking; run setuid applications (unless SELinux policy permits it); or run the <code class="command">su</code> and <code class="command">sudo</code> commands. This helps protect the system from the user. Refer to <a class="xref" href="#sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users" title="4.3. Usuarios Confinados y no Confinados">Sección 4.3, “Usuarios Confinados y no Confinados”</a> for further information about confined users.
 	</div><div class="section" title="6.1. Linux y los Mapeos de Usuarios de SELinux" id="sect-Security-Enhanced_Linux-Confining_Users-Linux_and_SELinux_User_Mappings"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.1. Linux y los Mapeos de Usuarios de SELinux</h2></div></div></div><div class="para">
 			Como usuario root de Linux, corra el comando <code class="command">semanage login -l</code> para ver el mapeo entre los usuarios de Linux y los usuarios de SELinux:
 		</div><pre class="screen"># /usr/sbin/semanage login -l
@@ -1481,7 +1472,7 @@ root                      unconfined_u              s0-s0:c0.c1023
 system_u                  system_u                  s0-s0:c0.c1023
 
 </pre><div class="para">
-			En Fedora 13, los usuarios Linux se mapean al ingreso SELinux <code class="computeroutput">__default__</code> por defecto (que se mapea al usuario SELinux <code class="computeroutput">unconfined_u</code>). Cuando se crea un usuario Linux con el comando <code class="command">useradd</code>, si no se especifica ninguna opcion, son mapeados al usuario SELinux <code class="computeroutput">unconfined_u</code>. Lo siguiente define el mapeo por defecto:
+			In Fedora 13, Linux users are mapped to the SELinux <code class="computeroutput">__default__</code> login by default (which is in turn mapped to the SELinux <code class="computeroutput">unconfined_u</code> user). When a Linux user is created with the <code class="command">useradd</code> command, if no options are specified, they are mapped to the SELinux <code class="computeroutput">unconfined_u</code> user. The following defines the default-mapping:
 		</div><pre class="screen">
 __default__               unconfined_u              s0-s0:c0.c1023
 
@@ -1542,7 +1533,7 @@ system_u                  system_u                  s0-s0:c0.c1023
 </pre></li><li class="listitem"><div class="para">
 					Para mapear un usuario usuarionuevo de Linux al usuario <code class="computeroutput">user_u</code> de SELinux, corra el siguiente comando como usuario root de Linux:
 				</div><div class="para">
-					<code class="command">/usr/sbin/semanage login -a -s user_u usuarionuevo</code>
+					<code class="command">/usr/sbin/semanage login -a -s user_u newuser</code>
 				</div><div class="para">
 					La opción <code class="option">-a</code> agrega un registro nuevo y la opción <code class="option">-s</code> especifica el usuario SELinux al que mapea el usuario Linux. El último argumento <code class="computeroutput">usuarionuevo</code>, es el usuario Linux al que quiere que se mapee el usuario SELinux especificado.
 				</div></li><li class="listitem"><div class="para">
@@ -1558,7 +1549,7 @@ root                      unconfined_u              s0-s0:c0.c1023
 system_u                  system_u                  s0-s0:c0.c1023
 
 </pre></li><li class="listitem"><div class="para">
-					Como usuario root de Linux, corra el comando <code class="command">passwd usuarionuevo</code> para asignar una contraseña para el usuario usuarionuevo de Linux:
+					As the Linux root user, run the <code class="command">passwd newuser</code> command to assign a password to the Linux newuser user:
 				</div><pre class="screen">
 # passwd newuser
 Changing password for user newuser.
@@ -1585,7 +1576,7 @@ root                      unconfined_u              s0-s0:c0.c1023
 system_u                  system_u                  s0-s0:c0.c1023
 
 </pre></li></ol></div></div><div class="section" title="6.4. Cambiando el Mapeo Predeterminado" id="sect-Security-Enhanced_Linux-Confining_Users-Changing_the_Default_Mapping"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.4. Cambiando el Mapeo Predeterminado</h2></div></div></div><div class="para">
-			En Fedora 13, los usuarios Linux se mapean al ingreso SELinux <code class="computeroutput">__default__</code> por defecto (que se mapea al usuario SELinux <code class="computeroutput">unconfined_u</code>). Si quiere que los usuarios nuevos de Linux y los usuarios Linux no mapeados específicamente a un usuario SELinux sean confinados por defecto, cambie el mapeo predeterminado con el comando <code class="command">semanage login</code>.
+			In Fedora 13, Linux users are mapped to the SELinux <code class="computeroutput">__default__</code> login by default (which is in turn mapped to the SELinux <code class="computeroutput">unconfined_u</code> user). If you would like new Linux users, and Linux users not specifically mapped to an SELinux user to be confined by default, change the default mapping with the <code class="command">semanage login</code> command.
 		</div><div class="para">
 			Por ejemplo, corra el siguiente comando como usuario root de Linux para cambiar el mapeo predeterminado de <code class="computeroutput">unconfined_u</code> a <code class="computeroutput">user_u</code>:
 		</div><div class="para">
@@ -1609,7 +1600,7 @@ system_u                  system_u                  s0-s0:c0.c1023
 s0-s0:c0.c1023 __default__
 
 </pre></div><div class="section" title="6.5. xguest: Modo Kiosk" id="sect-Security-Enhanced_Linux-Confining_Users-xguest_Kiosk_Mode"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.5. xguest: Modo Kiosk</h2></div></div></div><div class="para">
-			El paquete <span class="package">xguest</span> provee una cuenta de usuario kiosk. Esta cuenta se usa para asegurar máquinas a las que ingresan personas y las usan, como las de las bibliotecas, bancos, aeropuertos, quioscos de información y cyber cafés. La cuenta de usuario kiosk está muy bloqueada: escencialmente, sólo permite a los usuarios ingresar y usar <span class="application"><strong>Firefox</strong></span> para navegar sitios de Internet. Cualquier cambio hecho mientras se ingresó con esa cuenta, tal como la creación y cambio de la configuración, se pierde cuando se sale.
+			The <span class="package">xguest</span> package provides a kiosk user account. This account is used to secure machines that people walk up to and use, such as those at libraries, banks, airports, information kiosks, and coffee shops. The kiosk user account is very limited: essentially, it only allows users to log in and use <span class="application"><strong>Firefox</strong></span> to browse Internet websites. Any changes made while logged in with his account, such as creating files or changing settings, are lost when you log out.
 		</div><div class="para">
 			Para configurar la cuenta kiosk:
 		</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
@@ -1621,35 +1612,35 @@ $ /usr/sbin/getenforce
 Enforcing
 
 </pre><div class="para">
-					Si no es éste el caso, vaya a <a class="xref" href="#sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes" title="5.5. Modos de SELinux">Sección 5.5, “Modos de SELinux”</a> para información acerca del cambio de modo a obediente. No es posible ingresar con esta cuenta si SELinux está en modo permisivo o deshabilitado.
+					If this is not the case, refer to <a class="xref" href="#sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes" title="5.5. Modos de SELinux">Sección 5.5, “Modos de SELinux”</a> for information about changing to enforcing mode. It is not possible to log in with this account if SELinux is in permissive mode or disabled.
 				</div></li><li class="listitem"><div class="para">
 					Solamente puede ingresar a esta cuenta a través del Administración de Pantalla de GNOME (GDM). Una vez que el paquete <span class="package">xguest</span> se instala, se agrega una cuenta <code class="computeroutput">Invitado</code> a GDM. Para ingresar, haga clic en la cuenta <code class="computeroutput">Invitado</code>:
 				</div><div class="mediaobject"><img src="./images/xguest.png" /></div></li></ol></div></div><div class="section" title="6.6. Booleanos para que los Usuarios Ejecuten Aplicaciones" id="sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.6. Booleanos para que los Usuarios Ejecuten Aplicaciones</h2></div></div></div><div class="para">
 			Not allowing Linux users to execute applications (which inherit users' permissions) in their home directories and <code class="filename">/tmp/</code>, which they have write access to, helps prevent flawed or malicious applications from modifying files that users own. In Fedora 13, by default, Linux users in the <code class="computeroutput">guest_t</code> and <code class="computeroutput">xguest_t</code> domains can not execute applications in their home directories or <code class="filename">/tmp/</code>; however, by default, Linux users in the <code class="computeroutput">user_t</code> and <code class="computeroutput">staff_t</code> domains can.
 		</div><div class="para">
 			Hay booleanos disponibles para cambiar este comportamiento, y se configuran con el comando <code class="command">setsebool</code>. El comando <code class="command">setsebool</code> se debe usar con el usuario root de Linux. El comando <code class="command">setsebool -P</code> hace los cambios persistentes. No use la opción <code class="option">-P</code> si no quiere que los cambios persistan entre reiniciadas:
-		</div><div class="formalpara"><h5 class="formalpara">guest_t</h5>
+		</div><div class="formalpara" id="form-Security-Enhanced_Linux-Booleans_for_Users_Executing_Applications-guest_t"><h5 class="formalpara">guest_t</h5>
 				Para <span class="emphasis"><em>permitir</em></span> a los usuarios Linux en el dominio <code class="computeroutput">guest_t</code> que ejecuten aplicaciones en sus directorios de inicio y en <code class="filename">/tmp/</code>:
 			</div><div class="para">
 			<code class="command">/usr/sbin/setsebool -P allow_guest_exec_content on</code>
-		</div><div class="formalpara"><h5 class="formalpara">xguest_t</h5>
+		</div><div class="formalpara" id="form-Security-Enhanced_Linux-Booleans_for_Users_Executing_Applications-xguest_t"><h5 class="formalpara">xguest_t</h5>
 				Para <span class="emphasis"><em>permitir</em></span> a los usuarios Linux en el dominio <code class="computeroutput">xguest_t</code> ejecutar aplicaciones en sus directorios inicios y <code class="filename">/tmp/</code>:
 			</div><div class="para">
 			<code class="command">/usr/sbin/setsebool -P allow_xguest_exec_content on</code>
-		</div><div class="formalpara"><h5 class="formalpara">user_t</h5>
+		</div><div class="formalpara" id="form-Security-Enhanced_Linux-Booleans_for_Users_Executing_Applications-user_t"><h5 class="formalpara">user_t</h5>
 				Para <span class="emphasis"><em>impedir</em></span> que los usuarios Linux en el dominio <code class="computeroutput">user_t</code> ejecuten aplicaciones en sus directorios de inicio y <code class="filename">/tmp/</code>:
 			</div><div class="para">
 			<code class="command">/usr/sbin/setsebool -P allow_user_exec_content off</code>
-		</div><div class="formalpara"><h5 class="formalpara">staff_t</h5>
+		</div><div class="formalpara" id="form-Security-Enhanced_Linux-Booleans_for_Users_Executing_Applications-staff_t"><h5 class="formalpara">staff_t</h5>
 				Para <span class="emphasis"><em>impedir</em></span> que los usuarios Linux en el dominio <code class="computeroutput">staff_t</code> ejecuten aplicaciones en sus directorios de inicio y en <code class="filename">/tmp/</code>:
 			</div><div class="para">
 			<code class="command">/usr/sbin/setsebool -P allow_staff_exec_content off</code>
-		</div></div></div><div xml:lang="es-ES" class="chapter" title="Capítulo 7. Solución a Problemas" id="chap-Security-Enhanced_Linux-Troubleshooting" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 7. Solución a Problemas</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Troubleshooting-What_Happens_when_Access_is_Denied">7.1. Qué pasa cuando el Acceso es Denegado</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems">7.2. Tres Principales Causas de Problemas</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Labeling_Problems">7.2.1. Problemas de Etiquetados</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running">7.2.2. ¿Cómo se Ejecutan los Servicios Confinados?</a
 ></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Evolving_Rules_and_Broken_Applications">7.2.3. Evolucionando las Reglas y las Aplicaciones Rotas</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems">7.3. Corrección de Problemas</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Linux_Permissions">7.3.1. Permisos de Linux</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Possible_Causes_of_Silent_Denials">7.3.2. Posibles Causas de las Negaciones Silenciosas</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services">7.3.3. Páginas de Manual para Servicios</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains">7.3.4. Dominios Perm
 isivos</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Searching_For_and_Viewing_Denials">7.3.5. Búsqueda y Revisión de Negaciones</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages">7.3.6. Mensajes Crudos de Auditoría</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages">7.3.7. Mensajes sealert</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow">7.3.8. Permitiendo el Acceso: audit2allow</a></span></dt></dl></dd></dl></div><div class="para">
+		</div></div></div><div xml:lang="es-ES" class="chapter" title="Capítulo 7. Solución a Problemas" id="chap-Security-Enhanced_Linux-Troubleshooting" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 7. Solución a Problemas</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Troubleshooting-What_Happens_when_Access_is_Denied">7.1. Qué pasa cuando el Acceso es Denegado</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems">7.2. Tres Principales Causas de Problemas</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Labeling_Problems">7.2.1. Problemas de Etiquetados</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running">7.2.2. ¿Cómo se Ejecutan los Servicios Confinados?</a
 ></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Evolving_Rules_and_Broken_Applications">7.2.3. Evolucionando las Reglas y las Aplicaciones Rotas</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems">7.3. Corrección de Problemas</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Linux_Permissions">7.3.1. Permisos de Linux</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Possible_Causes_of_Silent_Denials">7.3.2. Posibles Causas de las Negaciones Silenciosas</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services">7.3.3. Páginas de Manual para Servicios</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains">7.3.4. Dominios Perm
 isivos</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Searching_For_and_Viewing_Denials">7.3.5. Búsqueda y Revisión de Negaciones</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages">7.3.6. Raw Audit Messages</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages">7.3.7. Mensajes sealert</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow">7.3.8. Permitiendo el Acceso: audit2allow</a></span></dt></dl></dd></dl></div><div class="para">
 		El siguiente capítulo describe qué pasa cuando SELinux niega el acceso; las principales tres causas de problemas; dónde encontrar información acerca del correcto etiquetado; análisis de las negaciones de SELinux; y creación de módulos de políticas personalizados con <code class="command">audit2allow</code>.
 	</div><div class="section" title="7.1. Qué pasa cuando el Acceso es Denegado" id="sect-Security-Enhanced_Linux-Troubleshooting-What_Happens_when_Access_is_Denied"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">7.1. Qué pasa cuando el Acceso es Denegado</h2></div></div></div><div class="para">
 			SELinux decisions, such as allowing or disallowing access, are cached. This cache is known as the Access Vector Cache (AVC). Denial messages are logged when SELinux denies access. These denials are also known as "AVC denials", and are logged to a different location, depending on which daemons are running:
-		</div><div class="segmentedlist"><table border="0"><thead><tr class="segtitle"><th>Demonio</th><th>Ubicación del Log</th></tr></thead><tbody><tr class="seglistitem"><td class="seg">auditd activado</td><td class="seg"><code class="filename">/var/log/audit/audit.log</code></td></tr><tr class="seglistitem"><td class="seg">auditd desactivado; rsyslogd activado</td><td class="seg"><code class="filename">/var/log/messages</code></td></tr><tr class="seglistitem"><td class="seg">setroubleshootd, rsyslogd y auditd activados</td><td class="seg"><code class="filename">/var/log/audit/audit.log</code>. Mensages de negaciones legibles que también se envían a <code class="filename">/var/log/messages</code></td></tr></tbody></table></div><div class="para">
-			Si está corriendo el Sistema de Ventanas X, ya tienen los paquetes <span class="package">setroubleshoot</span> y <span class="package">setroubleshoot-server</span> instalados, y los demonios <code class="systemitem">setroubleshootd</code> y <code class="systemitem">auditd</code> están ejecutándose, se muestra una estrella amarilla y una advertencia cuando SELinux deniega el acceso:
+		</div><div class="segmentedlist"><table border="0"><thead><tr class="segtitle"><th>Daemon</th><th>Log Location</th></tr></thead><tbody><tr class="seglistitem"><td class="seg">auditd on</td><td class="seg"><code class="filename">/var/log/audit/audit.log</code></td></tr><tr class="seglistitem"><td class="seg">auditd off; rsyslogd on</td><td class="seg"><code class="filename">/var/log/messages</code></td></tr><tr class="seglistitem"><td class="seg">setroubleshootd, rsyslogd, and auditd on</td><td class="seg"><code class="filename">/var/log/audit/audit.log</code>. Easier-to-read denial messages also sent to <code class="filename">/var/log/messages</code></td></tr></tbody></table></div><div class="para">
+			If you are running the X Window System, have the <span class="package">setroubleshoot</span> and <span class="package">setroubleshoot-server</span> packages installed, and the <code class="systemitem">setroubleshootd</code> and <code class="systemitem">auditd</code> daemons are running, a warning is displayed when access is denied by SELinux:
 		</div><div class="mediaobject"><img src="./images/denial.png" width="444" /></div><div class="para">
 			Clicking on 'Show' presents a detailed analysis of why SELinux denied access, and a possible solution for allowing access. If you are not running the X Window System, it is less obvious when access is denied by SELinux. For example, users browsing your website may receive an error similar to the following:
 		</div><pre class="screen">
@@ -1668,18 +1659,18 @@ You don't have permission to access <em class="replaceable"><code>file name</cod
 		</div><div class="section" title="7.2.1. Problemas de Etiquetados" id="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Labeling_Problems"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.2.1. Problemas de Etiquetados</h3></div></div></div><div class="para">
 				En sistemas que corren SELinux, todos los procesosy archivos se etiquetan con una etiqueta que contiene información de seguridad relevante. Esta información se llama contexto de SELinux. Si estas etiquetas están mal, el acceso puede ser negado. Si una aplicación se etiqueta incorrectamente, el proceso al que transiciona puede no tener la etiqueta correcta, causando negaciones de acceso de SELinux, y los procesos pueden crear archivo con las etiquetas incorrectas.
 			</div><div class="para">
-				Una causa común de problemas de etiquetados es cuando un directorio no estandar se usa para un servicio. Por ejemplo, en vez de usar <code class="filename">/var/www/html/</code> para un sitio web, un administrador prefiere usar <code class="filename">/srv/miweb/</code>. En Fedora 13, el directorio <code class="filename">/srv/</code> se etiqueta con el tipo <code class="computeroutput">var_t</code>. Los archivos y directorios creados en <code class="filename">/srv/</code> heredan este tipo. También, los directorios de alto nivel recién creados (como <code class="filename">/miservidor/</code>) puede ser etiquetado con el tipo <code class="computeroutput">default_t</code>. SELinux impide al Servidor HTTP Apache (<code class="systemitem">httpd</code>) el acceso a estos dos tipos. Para permitirle el acceso, SELinux debe saber qué archivos en <code class="filename">/srv/miweb/</code> son accesibles a <code class="systemitem">httpd</code>:
+				A common cause of labeling problems is when a non-standard directory is used for a service. For example, instead of using <code class="filename">/var/www/html/</code> for a website, an administrator wants to use <code class="filename">/srv/myweb/</code>. On Fedora 13, the <code class="filename">/srv/</code> directory is labeled with the <code class="computeroutput">var_t</code> type. Files and directories created and <code class="filename">/srv/</code> inherit this type. Also, newly-created top-level directories (such as <code class="filename">/myserver/</code>) may be labeled with the <code class="computeroutput">default_t</code> type. SELinux prevents the Apache HTTP Server (<code class="systemitem">httpd</code>) from accessing both of these types. To allow access, SELinux must know that the files in <code class="filename">/srv/myweb/</code> are to be accessible to <code class="systemitem">httpd</code>:
 			</div><pre class="screen">
 # /usr/sbin/semanage fcontext -a -t httpd_sys_content_t \
 "/srv/myweb(/.*)?"
 
 </pre><div class="para">
-				Este comando <code class="command">semanage</code> agrega el contexto para el directorio <code class="filename">/srv/miweb/</code> (y todos los archivos dentro de él) a la configuración de contexto de archivos de SELinux <sup>[<a id="id1563492" href="#ftn.id1563492" class="footnote">13</a>]</sup>. El comando <code class="command">semanage</code> no cambia el contexto. Como usuario root de Linux, ejecute el comando <code class="command">restorecon</code> para aplicar los cambios:
+				Este comando <code class="command">semanage</code> agrega el contexto para el directorio <code class="filename">/srv/miweb/</code> (y todos los archivos dentro de él) a la configuración de contexto de archivos de SELinux <sup>[<a id="id794556" href="#ftn.id794556" class="footnote">13</a>]</sup>. El comando <code class="command">semanage</code> no cambia el contexto. Como usuario root de Linux, ejecute el comando <code class="command">restorecon</code> para aplicar los cambios:
 			</div><pre class="screen">
 # /sbin/restorecon -R -v /srv/myweb
 
 </pre><div class="para">
-				Vaya a <a class="xref" href="#sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext" title="5.7.2. Cambios Persistentes: semanage fcontext">Sección 5.7.2, “Cambios Persistentes: semanage fcontext”</a> para más información sobre agregado de contextos a la configuración de contexto de archivo.
+				Refer to <a class="xref" href="#sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext" title="5.7.2. Cambios Persistentes: semanage fcontext">Sección 5.7.2, “Cambios Persistentes: semanage fcontext”</a> for further information about adding contexts to the file-context configuration.
 			</div><div class="section" title="7.2.1.1. ¿Cuál es el contexto correcto?" id="sect-Security-Enhanced_Linux-Labeling_Problems-What_is_the_Correct_Context"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">7.2.1.1. ¿Cuál es el contexto correcto?</h4></div></div></div><div class="para">
 					El comando <code class="command">matchpathcon</code> chequea el contexto de un nombre completo de archivo y lo compara con la etiqueta por defecto para esa dirección. El siguiente ejemplo muestra el uso de <code class="command">matchpathcon</code> en un directorio con archivos etiquetados incorrectamente:
 				</div><pre class="screen">
@@ -1701,7 +1692,7 @@ restorecon reset /var/www/html/page1.html context unconfined_u:object_r:samba_sh
 restorecon reset /var/www/html/index.html context unconfined_u:object_r:samba_share_t:s0-&gt;system_u:object_r:httpd_sys_content_t:s0
 
 </pre><div class="para">
-					Vaya a <a class="xref" href="#sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context" title="5.10.3. Chequeando el Contexto SELinux Predeterminado">Sección 5.10.3, “Chequeando el Contexto SELinux Predeterminado”</a> para un ejemplo más detallado de <code class="command">matchpathcon</code>.
+					Refer to <a class="xref" href="#sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context" title="5.10.3. Chequeando el Contexto SELinux Predeterminado">Sección 5.10.3, “Chequeando el Contexto SELinux Predeterminado”</a> for a more detailed example of <code class="command">matchpathcon</code>.
 				</div></div></div><div class="section" title="7.2.2. ¿Cómo se Ejecutan los Servicios Confinados?" id="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.2.2. ¿Cómo se Ejecutan los Servicios Confinados?</h3></div></div></div><div class="para">
 				Los servicios se pueden ejecutar en una variedad de formas. Para cambiar esto, debe decirle a SELinux cómo correrá los servicios. Esto se puede conseguir vía los Booleanos que permiten que parte de las políticas de SELinux se cambien en tiempo de ejecución, sin ningún conocimiento sobre la escritura de políticas de SELinux. Esto permite cambios, tales como permitir a servicios que accedan a sistemas de archivo NFS, sin recargar o recompilar una política SELinux. También, correr servicios en números de puerto no predeterminados requiere que la configuración de la política se actualice vía el comando <code class="command">semanage</code>.
 			</div><div class="para">
@@ -1722,8 +1713,8 @@ httpd_enable_ftp_server --&gt; off
 tftp_anon_write --&gt; off
 
 </pre><div class="para">
-				Para una lista de los Booleanos y de si están activos o inactivos, corra el comando <code class="command">/usr/sbin/getsebool -a</code>. Para una lista de los Booleanos y una explicación de lo que son, y de si están activos o no, ejecute el comando <code class="command">/usr/sbin/semanage boolean -l</code> como usuario root de Linux. vaya a <a class="xref" href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans" title="5.6. Booleanos">Sección 5.6, “Booleanos”</a> para información sobre listado y configuración de Booleanos.
-			</div><div class="formalpara"><h5 class="formalpara">Números de Puertos</h5>
+				For a list of Booleans and whether they are on or off, run the <code class="command">/usr/sbin/getsebool -a</code> command. For a list of Booleans, an explanation of what each one is, and whether they are on or off, run the <code class="command">/usr/sbin/semanage boolean -l</code> command as the Linux root user. Refer to <a class="xref" href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans" title="5.6. Booleanos">Sección 5.6, “Booleanos”</a> for information about listing and configuring Booleans.
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-How_are_Confined_Services_Running-Port_Numbers"><h5 class="formalpara">Números de Puertos</h5>
 					Dependiendo de la configuración de la política, los servicios pueden tener permitido correr sobre ciertos números de puerto. Intentar cambiar el puerto en el que corre un servicio sin cambiar la política puede resultar en un fallo al iniciar el servicio. Por ejemplo, ejecute el comando <code class="command">semanage port -l | grep http</code> como usuario root de Linux para listar los puertos relacionados con <code class="systemitem">http</code>:
 				</div><pre class="screen">
 # /usr/sbin/semanage port -l | grep http
@@ -1749,7 +1740,7 @@ Unable to open logs
 type=AVC msg=audit(1225948455.061:294): avc:  denied  { name_bind } for  pid=4997 comm="httpd" src=9876 scontext=unconfined_u:system_r:httpd_t:s0 tcontext=system_u:object_r:port_t:s0 tclass=tcp_socket
 
 </pre><div class="para">
-				Para permitir a <code class="systemitem">httpd</code> escuchar en un puerto que no está listado en el tipo de puerto <code class="computeroutput">http_port_t</code>, ejecute el comando <code class="command">semanage port</code> para agregar un puerto a la configuración de la política <sup>[<a id="id978454" href="#ftn.id978454" class="footnote">14</a>]</sup>:
+				Para permitir a <code class="systemitem">httpd</code> escuchar en un puerto que no está listado en el tipo de puerto <code class="computeroutput">http_port_t</code>, ejecute el comando <code class="command">semanage port</code> para agregar un puerto a la configuración de la política <sup>[<a id="id721089" href="#ftn.id721089" class="footnote">14</a>]</sup>:
 			</div><pre class="screen">
 # /usr/sbin/semanage port -a -t http_port_t -p tcp 9876
 
@@ -1758,11 +1749,11 @@ type=AVC msg=audit(1225948455.061:294): avc:  denied  { name_bind } for  pid=499
 			</div></div><div class="section" title="7.2.3. Evolucionando las Reglas y las Aplicaciones Rotas" id="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Evolving_Rules_and_Broken_Applications"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.2.3. Evolucionando las Reglas y las Aplicaciones Rotas</h3></div></div></div><div class="para">
 				Las aplicaciones se pueden romper, provocando que SELinux niegue el acceso. También, las reglas de SELinux evolucionan - SELinux no se debe ver como una aplicación que se ejecuta en una cierta forma, haciendo que deniegue el acceso, aún cuando la aplicación está funcionado como se espera que lo haga. Por ejemplo, si una nueva versión de PostgreSQL se lanza, puede realizar acciones sobre la política actual que no han sido vistas antes, haciendo que el acceso sea denegado, aún cuando el acceso debería ser permitido.
 			</div><div class="para">
-				Para estas situaciones, después de que se niegue el acceso, use <code class="command">audit2allow</code> para crear un módulo de política personalizado para permitir el acceso. Vaya a <a class="xref" href="#sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow" title="7.3.8. Permitiendo el Acceso: audit2allow">Sección 7.3.8, “Permitiendo el Acceso: audit2allow”</a> para más información sobre el uso de <code class="command">audit2allow</code>.
+				For these situations, after access is denied, use <code class="command">audit2allow</code> to create a custom policy module to allow access. Refer to <a class="xref" href="#sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow" title="7.3.8. Permitiendo el Acceso: audit2allow">Sección 7.3.8, “Permitiendo el Acceso: audit2allow”</a> for information about using <code class="command">audit2allow</code>.
 			</div></div></div><div class="section" title="7.3. Corrección de Problemas" id="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">7.3. Corrección de Problemas</h2></div></div></div><div class="para">
 			Las siguientes secciones ayudan a resolver problemas. Cubren los temas: chequeo de los permisos de Linux, que se chequean antes que las reglas de SELinux; posibles causas de negaciones de acceso de SELinux, pero no negaciones que se estén guardando; páginas man de los servicios, que contienen información sobre etiquetado y Booleanos; dominios permisivos, para permitir a un proceso correr en modo permisivo, en vez de todo el sistema; cómo buscar y encontrar mensajes; análisis de negaciones; y creación de módulos de políticas personalizados con <code class="command">audit2allow</code>.
 		</div><div class="section" title="7.3.1. Permisos de Linux" id="sect-Security-Enhanced_Linux-Fixing_Problems-Linux_Permissions"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.3.1. Permisos de Linux</h3></div></div></div><div class="para">
-				Cuando el acceso se niega, verifique los permisos estándares de LInux. Como se mencionó en <a class="xref" href="#chap-Security-Enhanced_Linux-Introduction" title="Capítulo 2. Introducción">Capítulo 2, <i>Introducción</i></a>, la mayoría de los sistemas operativos usan un sistema de Control de Acceso Discrecional (DAC) para controlar el acceso, permitiendo a los usuarios controlar los permisos de sus propios archivos. Las reglas de políticas de SELinux se verifican después de estas reglas DAC. Las reglas de políticas de SELinux no se usan si las reglas DAC niegan el acceso al principio.
+				When access is denied, check standard Linux permissions. As mentioned in <a class="xref" href="#chap-Security-Enhanced_Linux-Introduction" title="Capítulo 2. Introducción">Capítulo 2, <i>Introducción</i></a>, most operating systems use a Discretionary Access Control (DAC) system to control access, allowing users to control the permissions of files that they own. SELinux policy rules are checked after DAC rules. SELinux policy rules are not used if DAC rules deny access first.
 			</div><div class="para">
 				Si el acceso es denegado y no hay negaciones SELinux guardadas, use el comando <code class="command">ls -l</code> para ver los permisos estándares de Linux:
 			</div><pre class="screen">
@@ -1799,7 +1790,7 @@ dontaudit smbd_t squid_port_t : tcp_socket name_bind ;
 dontaudit smbd_t squid_port_t : udp_socket name_bind ;
 
 </pre><div class="para">
-				Vaya a <a class="xref" href="#sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages" title="7.3.6. Mensajes Crudos de Auditoría">Sección 7.3.6, “Mensajes Crudos de Auditoría”</a> y a <a class="xref" href="#sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages" title="7.3.7. Mensajes sealert">Sección 7.3.7, “Mensajes sealert”</a> para información acerca del análisis de las negaciones.
+				Refer to <a class="xref" href="#sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages" title="7.3.6. Raw Audit Messages">Sección 7.3.6, “Raw Audit Messages”</a> and <a class="xref" href="#sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages" title="7.3.7. Mensajes sealert">Sección 7.3.7, “Mensajes sealert”</a> for information about analyzing denials.
 			</div></div><div class="section" title="7.3.3. Páginas de Manual para Servicios" id="sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.3.3. Páginas de Manual para Servicios</h3></div></div></div><div class="para">
 				Las páginas de manual para los servicios conteniendo información valiosa, tal como qué tipo de archivo usar para una situación dada, y los Booleanos para cambiar el acceso que un servicio tiene (tal como <code class="systemitem">httpd</code> para acceder sistemas de archivos NFS). Esta información puede estar en la página de manual estándar o una página de manual con <code class="computeroutput">selinux</code> como prefijo o sufijo.
 			</div><div class="para">
@@ -1815,7 +1806,7 @@ dontaudit smbd_t squid_port_t : udp_socket name_bind ;
 			</div></div><div class="section" title="7.3.4. Dominios Permisivos" id="sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.3.4. Dominios Permisivos</h3></div></div></div><div class="para">
 				Cuando SELinux se ejecuta en modo permisivo, SELinux no niega el acceso, sino que las negaciones para las acciones se guardan como si fuera que corre en modo obediente. Previamente, no era posible hacer permisivo un único dominio (recuerde: los procesos corren en dominios). En ciertas situaciones, esto llevó a hacer el sistema permisivo para poder corregir los problemas.
 			</div><div class="para">
-				Fedora 13 introduce los dominios permisivos, donde un administrador puede configurar un único proceso (dominio) para que corra permisivo, en vez de hacer todo el sistema permisivo. Los chequeos de SELinux se realizan igualmente para dominios permisivos; sin embargo, el kernel permite el acceso e informa la negación AVC para situaciones donde SELinux hubiera negado el acceso. Los dominios permisivos están también disponibles en Fedora 9 (con las últimas actualizaciones aplicadas).
+				Fedora 13 includes permissive domains, where an administrator can configure a single process (domain) to run permissive, rather than making the whole system permissive. SELinux checks are still performed for permissive domains; however, the kernel allows access and reports an AVC denial for situations where SELinux would have denied access. Permissive domains are also available in Fedora 9 (with the latest updates applied).
 			</div><div class="para">
 				En el Linux para Empresas de Red Hat 4 y 5, los Booleanos <code class="computeroutput"><em class="replaceable"><code>dominio</code></em>_disable_trans</code> están disponibles para prevenir que una aplicación transicione a un dominio confinado, y por lo tanto, el proceso se ejecute en un dominio no confinado, tal como <code class="computeroutput">initrc_t</code>. Poniendo en 1 tales booleanos pueden causar problemas serios. Por ejemplo, si el Booleano <code class="computeroutput">httpd_disable_trans</code> se pone en 1:
 			</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
@@ -1863,19 +1854,19 @@ type=SYSCALL msg=audit(1226882925.714:136): arch=40000003 syscall=5 success=yes
 				</div><div class="para">
 					Refer to Dan Walsh's <a href="http://danwalsh.livejournal.com/24537.html">"Permissive Domains"</a> blog entry for further information about permissive domains.
 				</div></div></div><div class="section" title="7.3.5. Búsqueda y Revisión de Negaciones" id="sect-Security-Enhanced_Linux-Fixing_Problems-Searching_For_and_Viewing_Denials"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.3.5. Búsqueda y Revisión de Negaciones</h3></div></div></div><div class="para">
-				Esta sección asume que los paquetes <span class="package">setroubleshoot</span>, <span class="package">setroubleshoot-server</span>, <span class="package">dbus</span> y <span class="package">audit</span> están instalados, y que los demonios <code class="systemitem">auditd</code>, <code class="systemitem">rsyslogd</code> y <code class="systemitem">setroubleshootd</code> están ejecutándose. Vaya a <a class="xref" href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used" title="5.2. Qué Archivo Log se usa">Sección 5.2, “Qué Archivo Log se usa”</a> para información sobre cómo iniciar estos demonios. Hay disponibles un número de herramientas para ver las negaciones de SELinux, tales como <code class="command">ausearch</code>, <code class="command">aureport</code> y <code class="command">sealert</code>.
-			</div><div class="formalpara"><h5 class="formalpara">ausearch</h5>
-					The <span class="package">audit</span> package provides <code class="command">ausearch</code>. From the <span class="citerefentry"><span class="refentrytitle">ausearch</span>(8)</span> manual page: "<code class="command">ausearch</code> is a tool that can query the audit daemon logs based for events based on different search criteria"<sup>[<a id="id960392" href="#ftn.id960392" class="footnote">15</a>]</sup>. The <code class="command">ausearch</code> tool accesses <code class="filename">/var/log/audit/audit.log</code>, and as such, must be run as the Linux root user:
+				This section assumes the <span class="package">setroubleshoot</span>, <span class="package">setroubleshoot-server</span>, <span class="package">dbus</span> and <span class="package">audit</span> packages are installed, and that the <code class="systemitem">auditd</code>, <code class="systemitem">rsyslogd</code>, and <code class="systemitem">setroubleshootd</code> daemons are running. Refer to <a class="xref" href="#sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used" title="5.2. Qué Archivo Log se usa">Sección 5.2, “Qué Archivo Log se usa”</a> for information about starting these daemons. A number of tools are available for searching for and viewing SELinux denials, such as <code class="command">ausearch</code>, <code class="command">aureport</code>, and <code class="command">sealert</code>.
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Searching_For_and_Viewing_Denials-ausearch"><h5 class="formalpara">ausearch</h5>
+					The <span class="package">audit</span> package provides <code class="command">ausearch</code>. From the <span class="citerefentry"><span class="refentrytitle">ausearch</span>(8)</span> manual page: "<code class="command">ausearch</code> is a tool that can query the audit daemon logs based for events based on different search criteria"<sup>[<a id="id792321" href="#ftn.id792321" class="footnote">15</a>]</sup>. The <code class="command">ausearch</code> tool accesses <code class="filename">/var/log/audit/audit.log</code>, and as such, must be run as the Linux root user:
 				</div><div class="segmentedlist"><table border="0"><thead><tr class="segtitle"><th>Buscando</th><th>Comando</th></tr></thead><tbody><tr class="seglistitem"><td class="seg">todas las negaciones</td><td class="seg"><code class="command">/sbin/ausearch -m avc</code></td></tr><tr class="seglistitem"><td class="seg">negaciones de hoy</td><td class="seg"><code class="command">/sbin/ausearch -m avc -ts today</code></td></tr><tr class="seglistitem"><td class="seg">negaciones desde los últimos 10 minutos</td><td class="seg"><code class="command">/sbin/ausearch -m avc -ts recent</code></td></tr></tbody></table></div><div class="para">
-				To search for SELinux denials for a particular service, use the <code class="option">-c <em class="replaceable"><code>comm-name</code></em></code> option, where <em class="replaceable"><code>comm-name</code></em> "is the executable’s name"<sup>[<a id="id960490" href="#ftn.id960490" class="footnote">16</a>]</sup>, for example, <code class="systemitem">httpd</code> for the Apache HTTP Server, and <code class="systemitem">smbd</code> for Samba:
+				To search for SELinux denials for a particular service, use the <code class="option">-c <em class="replaceable"><code>comm-name</code></em></code> option, where <em class="replaceable"><code>comm-name</code></em> "is the executable’s name"<sup>[<a id="id792416" href="#ftn.id792416" class="footnote">16</a>]</sup>, for example, <code class="systemitem">httpd</code> for the Apache HTTP Server, and <code class="systemitem">smbd</code> for Samba:
 			</div><div class="para">
 				<code class="command">/sbin/ausearch -m avc -c httpd</code>
 			</div><div class="para">
 				<code class="command">/sbin/ausearch -m avc -c smbd</code>
 			</div><div class="para">
 				Refer to the <span class="citerefentry"><span class="refentrytitle">ausearch</span>(8)</span> manual page for further <code class="command">ausearch</code> options.
-			</div><div class="formalpara"><h5 class="formalpara">aureport</h5>
-					The <span class="package">audit</span> package provides <code class="command">aureport</code>. From the <span class="citerefentry"><span class="refentrytitle">aureport</span>(8)</span> manual page: "<code class="command">aureport</code> is a tool that produces summary reports of the audit system logs"<sup>[<a id="id960595" href="#ftn.id960595" class="footnote">17</a>]</sup>. The <code class="command">aureport</code> tool accesses <code class="filename">/var/log/audit/audit.log</code>, and as such, must be run as the Linux root user. To view a list of SELinux denials and how often each one occurred, run the <code class="command">aureport -a</code> command. The following is example output that includes two denials:
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Searching_For_and_Viewing_Denials-aureport"><h5 class="formalpara">aureport</h5>
+					The <span class="package">audit</span> package provides <code class="command">aureport</code>. From the <span class="citerefentry"><span class="refentrytitle">aureport</span>(8)</span> manual page: "<code class="command">aureport</code> is a tool that produces summary reports of the audit system logs"<sup>[<a id="id792516" href="#ftn.id792516" class="footnote">17</a>]</sup>. The <code class="command">aureport</code> tool accesses <code class="filename">/var/log/audit/audit.log</code>, and as such, must be run as the Linux root user. To view a list of SELinux denials and how often each one occurred, run the <code class="command">aureport -a</code> command. The following is example output that includes two denials:
 				</div><pre class="screen">
 # /sbin/aureport -a
 
@@ -1888,7 +1879,7 @@ AVC Report
 
 </pre><div class="para">
 				Refer to the <span class="citerefentry"><span class="refentrytitle">aureport</span>(8)</span> manual page for further <code class="command">aureport</code> options.
-			</div><div class="formalpara"><h5 class="formalpara">sealert</h5>
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Searching_For_and_Viewing_Denials-sealert"><h5 class="formalpara">sealert</h5>
 					El paquete <span class="package">setroubleshoot-server</span> provee <code class="command">sealert</code>, que lee los mensajes de negación traducidos por <span class="package">setroubleshoot-server</span>. A las negaciones se le asignan IDs, como se ve en <code class="filename">/var/log/messages</code>. El siguiente es un ejemplo de negación en <code class="filename">messages</code>:
 				</div><pre class="screen">
 setroubleshoot: SELinux is preventing httpd (httpd_t) "getattr" to /var/www/html/file1 (samba_share_t). For complete SELinux messages. run sealert -l 84e0b04d-d0ad-4347-8317-22e74f6cd020
@@ -1905,7 +1896,7 @@ setroubleshoot: SELinux is preventing httpd (httpd_t) "getattr" to /var/www/html
 						As the Linux root user, run the <code class="command">sealert -a /var/log/audit/audit.log -H &gt; audit.html</code> command to create a HTML version of the <code class="command">sealert</code> analysis, as seen with the <code class="command">sealert</code> GUI.
 					</div></li></ul></div><div class="para">
 				Refer to the <span class="citerefentry"><span class="refentrytitle">sealert</span>(8)</span> manual page for further <code class="command">sealert</code> options.
-			</div></div><div class="section" title="7.3.6. Mensajes Crudos de Auditoría" id="sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.3.6. Mensajes Crudos de Auditoría</h3></div></div></div><div class="para">
+			</div></div><div class="section" title="7.3.6. Raw Audit Messages" id="sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.3.6. Raw Audit Messages</h3></div></div></div><div class="para">
 				Los mensajes crudos de auditoría se guardan en <code class="filename">/var/log/audit/audit.log</code>. El siguiente es un ejemplo de negación AVC (y su llamada a sistema asociado) que ocurrío cuando el Servidor HTTP Apache (corriendo en el dominio <code class="computeroutput">httpd_t</code>) intentó acceder el <code class="filename">/var/www/html/archivo1</code> (etiquetado con el tipo <code class="computeroutput">samba_share_t</code>):
 			</div><pre class="screen">
 type=AVC msg=audit(1226874073.147:96): avc:  denied  { getattr } for  pid=2465 comm="httpd" path="/var/www/html/file1" dev=dm-0 ino=284133 scontext=unconfined_u:system_r:httpd_t:s0 tcontext=unconfined_u:object_r:samba_share_t:s0 tclass=file
@@ -2005,13 +1996,13 @@ node=<em class="replaceable"><code>hostname</code></em> type=SYSCALL msg=audit(1
 						</div></dd><dt><span class="term">Comando para Corregir</span></dt><dd><div class="para">
 							Un comando sugerido para permitir el acceso y resolver la negación. En este ejemplo, se dá el comando para cambiar el tipo del <code class="filename">archivo1</code> a <code class="computeroutput">public_content_t</code>, que es accesible por el Servidor HTTP Apache y por Samba.
 						</div></dd><dt><span class="term">Información Adicional</span></dt><dd><div class="para">
-							Información que es útil en los informes de errores, como el nombre de paquete de política y la versión (<code class="computeroutput">selinux-policy-3.5.13-11.fc12</code>), pero que no puede ser de ayuda para resolver por qué ocurrió la negación.
-						</div></dd><dt><span class="term">Mensajes Crudos de Auditoría</span></dt><dd><div class="para">
-							Los mensajes crudos de auditoría de <code class="filename">/var/log/audit/audit.log</code> que son asociados con la negación. Vaya a <a class="xref" href="#sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages" title="7.3.6. Mensajes Crudos de Auditoría">Sección 7.3.6, “Mensajes Crudos de Auditoría”</a> para información acerca de cada ítem en la negación AVC.
+							Information that is useful in bug reports, such as the policy package name and version (<code class="computeroutput">selinux-policy-3.5.13-11.fc12</code>), but may not help towards solving why the denial occurred.
+						</div></dd><dt><span class="term">Raw Audit Messages</span></dt><dd><div class="para">
+							The raw audit messages from <code class="filename">/var/log/audit/audit.log</code> that are associated with the denial. Refer to <a class="xref" href="#sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages" title="7.3.6. Raw Audit Messages">Sección 7.3.6, “Raw Audit Messages”</a> for information about each item in the AVC denial.
 						</div></dd></dl></div></div><div class="section" title="7.3.8. Permitiendo el Acceso: audit2allow" id="sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.3.8. Permitiendo el Acceso: audit2allow</h3></div></div></div><div class="para">
 				No use el ejemplo en esta sección en producción. Se usa sólo para mostrar el uso de <code class="command">audit2allow</code>.
 			</div><div class="para">
-				From the <span class="citerefentry"><span class="refentrytitle">audit2allow</span>(1)</span> manual page: "<code class="command">audit2allow</code> - generate SELinux policy allow rules from logs of denied operations"<sup>[<a id="id2084832" href="#ftn.id2084832" class="footnote">18</a>]</sup>. After analyzing denials as per <a class="xref" href="#sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages" title="7.3.7. Mensajes sealert">Sección 7.3.7, “Mensajes sealert”</a>, and if no label changes or Booleans allowed access, use <code class="command">audit2allow</code> to create a local policy module. After access is denied by SELinux, running the <code class="command">audit2allow</code> command presents Type Enforcement rules that allow the previously denied access.
+				From the <span class="citerefentry"><span class="refentrytitle">audit2allow</span>(1)</span> manual page: "<code class="command">audit2allow</code> - generate SELinux policy allow rules from logs of denied operations"<sup>[<a id="id793358" href="#ftn.id793358" class="footnote">18</a>]</sup>. After analyzing denials as per <a class="xref" href="#sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages" title="7.3.7. Mensajes sealert">Sección 7.3.7, “Mensajes sealert”</a>, and if no label changes or Booleans allowed access, use <code class="command">audit2allow</code> to create a local policy module. After access is denied by SELinux, running the <code class="command">audit2allow</code> command presents Type Enforcement rules that allow the previously denied access.
 			</div><div class="para">
 				El siguiente ejemplo muestra el uso de <code class="command">audit2allow</code> para crear un módulo de política:
 			</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
@@ -2074,75 +2065,75 @@ To make this policy package active, execute:
 
 </pre><div class="para">
 				Refer to Dan Walsh's <a href="http://danwalsh.livejournal.com/24750.html">"Using audit2allow to build policy modules. Revisited."</a> blog entry for further information about using <code class="command">audit2allow</code> to build policy modules.
-			</div></div></div><div class="footnotes"><br /><hr width="100" align="left" /><div class="footnote"><p><sup>[<a id="ftn.id1563492" href="#id1563492" class="para">13</a>] </sup>
+			</div></div></div><div class="footnotes"><br /><hr width="100" align="left" /><div class="footnote"><p><sup>[<a id="ftn.id794556" href="#id794556" class="para">13</a>] </sup>
 					Los archivos en <code class="filename">/etc/selinux/targeted/contexts/files/</code> definen los contextos de archivos y directorios. Los archivos en este directorio son leídos por <code class="command">restorecon</code> y <code class="command">setfiles</code> para restaurar archivos y directorios a sus contextos predeterminados.
-				</p></div><div class="footnote"><p><sup>[<a id="ftn.id978454" href="#id978454" class="para">14</a>] </sup>
+				</p></div><div class="footnote"><p><sup>[<a id="ftn.id721089" href="#id721089" class="para">14</a>] </sup>
 					El comando <code class="command">semanage port -a</code> agrega una entrada al archivo <code class="filename">/etc/selinux/targeted/modules/active/ports.local</code>. Nota: por defecto, este archivo sólo puede ser visto por el usuario root de Linux.
-				</p></div><div class="footnote"><p><sup>[<a id="ftn.id960392" href="#id960392" class="para">15</a>] </sup>
+				</p></div><div class="footnote"><p><sup>[<a id="ftn.id792321" href="#id792321" class="para">15</a>] </sup>
 						From the <span class="citerefentry"><span class="refentrytitle">ausearch</span>(8)</span> manual page, as shipped with the <span class="package">audit</span> package in Fedora 13.
-					</p></div><div class="footnote"><p><sup>[<a id="ftn.id960490" href="#id960490" class="para">16</a>] </sup>
+					</p></div><div class="footnote"><p><sup>[<a id="ftn.id792416" href="#id792416" class="para">16</a>] </sup>
 					From the <span class="citerefentry"><span class="refentrytitle">ausearch</span>(8)</span> manual page, as shipped with the <span class="package">audit</span> package in Fedora 13.
-				</p></div><div class="footnote"><p><sup>[<a id="ftn.id960595" href="#id960595" class="para">17</a>] </sup>
+				</p></div><div class="footnote"><p><sup>[<a id="ftn.id792516" href="#id792516" class="para">17</a>] </sup>
 						From the <span class="citerefentry"><span class="refentrytitle">aureport</span>(8)</span> manual page, as shipped with the <span class="package">audit</span> package in Fedora 13.
-					</p></div><div class="footnote"><p><sup>[<a id="ftn.id2084832" href="#id2084832" class="para">18</a>] </sup>
+					</p></div><div class="footnote"><p><sup>[<a id="ftn.id793358" href="#id793358" class="para">18</a>] </sup>
 					From the <span class="citerefentry"><span class="refentrytitle">audit2allow</span>(1)</span> manual page, as shipped with the <span class="package">policycoreutils</span> package in Fedora 13.
-				</p></div></div></div><div xml:lang="es-ES" class="chapter" title="Capítulo 8. Información Adicional" id="chap-Security-Enhanced_Linux-Further_Information" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 8. Información Adicional</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Further_Information-Contributors">8.1. Contribuyentes</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Further_Information-Other_Resources">8.2. Otros Recursos</a></span></dt></dl></div><div class="section" title="8.1. Contribuyentes" id="sect-Security-Enhanced_Linux-Further_Information-Contributors"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">8.1. Contribuyentes</h2></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-					<a href="http://fedoraproject.org/wiki/GeertWarrink">Geert Warrink</a> (traducción - Danés)
+				</p></div></div></div><div xml:lang="es-ES" class="chapter" title="Capítulo 8. Información Adicional" id="chap-Security-Enhanced_Linux-Further_Information" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 8. Información Adicional</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Further_Information-Contributors">8.1. Contributors</a></span></dt><dt><span class="section"><a href="#sect-Security-Enhanced_Linux-Further_Information-Other_Resources">8.2. Other Resources</a></span></dt></dl></div><div class="section" title="8.1. Contributors" id="sect-Security-Enhanced_Linux-Further_Information-Contributors"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">8.1. Contributors</h2></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+					<a href="http://fedoraproject.org/wiki/GeertWarrink">Geert Warrink</a> (translation - Dutch)
 				</div></li><li class="listitem"><div class="para">
-					<a href="http://fedoraproject.org/wiki/User:Beckerde">Domingo Becker</a> (traducción - Español)
+					<a href="http://fedoraproject.org/wiki/User:Beckerde">Domingo Becker</a> (translation - Spanish)
 				</div></li><li class="listitem"><div class="para">
-					<a href="http://fedoraproject.org/wiki/User:Logan">Daniel Cabrera</a> (traducción - Español)
-				</div></li></ul></div></div><div class="section" title="8.2. Otros Recursos" id="sect-Security-Enhanced_Linux-Further_Information-Other_Resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">8.2. Otros Recursos</h2></div></div></div><div class="formalpara"><h5 class="formalpara">La Agencia de Seguridad Nacional (NSA)</h5>
+					<a href="http://fedoraproject.org/wiki/User:Logan">Daniel Cabrera</a> (translation - Spanish)
+				</div></li></ul></div></div><div class="section" title="8.2. Other Resources" id="sect-Security-Enhanced_Linux-Further_Information-Other_Resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">8.2. Other Resources</h2></div></div></div><div class="formalpara" id="form-Security-Enhanced_Linux-Further_Information-The_National_Security_Agency_NSA"><h5 class="formalpara">La Agencia de Seguridad Nacional (NSA)</h5>
 				De la página <a href="http://www.nsa.gov/research/selinux/contrib.shtml">Contribuyentes de SELinux</a>:
 			</div><div class="para">
 			<span class="emphasis"><em>Researchers in NSA's National Information Assurance Research Laboratory (NIARL) designed and implemented flexible mandatory access controls in the major subsystems of the Linux kernel and implemented the new operating system components provided by the Flask architecture, namely the security server and the access vector cache. The NSA researchers reworked the LSM-based SELinux for inclusion in Linux 2.6. NSA has also led the development of similar controls for the X Window System (XACE/XSELinux) and for Xen (XSM/Flask).</em></span>
 		</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-					El sitio web principal de SELinux: <a href="http://www.nsa.gov/research/selinux/index.shtml">http://www.nsa.gov/research/selinux/index.shtml</a>.
+					Main SELinux website: <a href="http://www.nsa.gov/research/selinux/index.shtml">http://www.nsa.gov/research/selinux/index.shtml</a>.
 				</div></li><li class="listitem"><div class="para">
-					Documentación de SELinux: <a href="http://www.nsa.gov/research/selinux/docs.shtml">http://www.nsa.gov/research/selinux/docs.shtml</a>.
+					SELinux documentation: <a href="http://www.nsa.gov/research/selinux/docs.shtml">http://www.nsa.gov/research/selinux/docs.shtml</a>.
 				</div></li><li class="listitem"><div class="para">
-					Trasfondo de SELinux: <a href="http://www.nsa.gov/research/selinux/background.shtml">http://www.nsa.gov/research/selinux/background.shtml</a>.
-				</div></li></ul></div><div class="formalpara"><h5 class="formalpara">Tecnología de Tresys</h5>
+					SELinux background: <a href="http://www.nsa.gov/research/selinux/background.shtml">http://www.nsa.gov/research/selinux/background.shtml</a>.
+				</div></li></ul></div><div class="formalpara" id="form-Security-Enhanced_Linux-Further_Information-Tresys_Technology"><h5 class="formalpara">Tecnología de Tresys</h5>
 				<a href="http://www.tresys.com/">Tresys Technology</a> son los desarrolladores de:
 			</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
 					<a href="http://userspace.selinuxproject.org/trac/">Herramientas y bibliotecas en el espacio del usuario para SELinux</a>.
 				</div></li><li class="listitem"><div class="para">
 					<a href="http://oss.tresys.com/projects/refpolicy">Política de Referencia de SELinux</a>.
-				</div></li></ul></div><div class="formalpara"><h5 class="formalpara">Noticias de SELinux</h5>
+				</div></li></ul></div><div class="formalpara" id="form-Security-Enhanced_Linux-Further_Information-SELinux_News"><h5 class="formalpara">Noticias de SELinux</h5>
 				<div class="itemizedlist"><ul><li class="listitem"><div class="para">
-							Noticias: <a href="http://selinuxnews.org/wp/">http://selinuxnews.org/wp/</a>.
+							News: <a href="http://selinuxnews.org/wp/">http://selinuxnews.org/wp/</a>.
 						</div></li><li class="listitem"><div class="para">
-							Planeta SELinux (blogs): <a href="http://selinuxnews.org/planet/">http://selinuxnews.org/planet/</a>.
+							Planet SELinux (blogs): <a href="http://selinuxnews.org/planet/">http://selinuxnews.org/planet/</a>.
 						</div></li></ul></div>
 
-			</div><div class="formalpara"><h5 class="formalpara">Wiki del Proyecto SELinux</h5>
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Further_Information-SELinux_Project_Wiki"><h5 class="formalpara">Wiki del Proyecto SELinux</h5>
 				<div class="itemizedlist"><ul><li class="listitem"><div class="para">
-							Página principal: <a href="http://selinuxproject.org/page/Main_Page">http://selinuxproject.org/page/Main_Page</a>.
+							Main page: <a href="http://selinuxproject.org/page/Main_Page">http://selinuxproject.org/page/Main_Page</a>.
 						</div></li><li class="listitem"><div class="para">
-							Recursos del usuario, incluyendo enlaces a documentación, listas de correo, sitios web y herramientas: <a href="http://selinuxproject.org/page/User_Resources">http://selinuxproject.org/page/User_Resources</a>.
+							User resources, including links to documentation, mailing lists, websites, and tools: <a href="http://selinuxproject.org/page/User_Resources">http://selinuxproject.org/page/User_Resources</a>.
 						</div></li></ul></div>
 
-			</div><div class="formalpara"><h5 class="formalpara">Linux para Empresas de Red Hat</h5>
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Further_Information-Red_Hat_Enterprise_Linux"><h5 class="formalpara">Linux para Empresas de Red Hat</h5>
 				<div class="itemizedlist"><ul><li class="listitem"><div class="para">
 							La <a href="http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.2/html/Deployment_Guide/index.html">Guía de Despliegue del Linux para Empresas de Red Hat</a> contiene una sección de <a href="http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.2/html/Deployment_Guide/selg-chapter-0054.html">Referencias</a> SELinux, que tiene enlaces a tutoriales de SELinux, información general y la tecnología detrás de SELinux.
 						</div></li><li class="listitem"><div class="para">
 							La <a href="http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/selinux-guide/index.html">Guía de SELinux del Linux para Empresas de Red Hat 4</a>.
 						</div></li></ul></div>
 
-			</div><div class="formalpara"><h5 class="formalpara">Fedora</h5>
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Further_Information-Fedora"><h5 class="formalpara">Fedora</h5>
 				<div class="itemizedlist"><ul><li class="listitem"><div class="para">
-							Página principal: <a href="http://fedoraproject.org/wiki/SELinux">http://fedoraproject.org/wiki/SELinux</a>.
+							Main page: <a href="http://fedoraproject.org/wiki/SELinux">http://fedoraproject.org/wiki/SELinux</a>.
 						</div></li><li class="listitem"><div class="para">
-							Resolución de problemas: <a href="http://fedoraproject.org/wiki/SELinux/Troubleshooting">http://fedoraproject.org/wiki/SELinux/Troubleshooting</a>.
+							Troubleshooting: <a href="http://fedoraproject.org/wiki/SELinux/Troubleshooting">http://fedoraproject.org/wiki/SELinux/Troubleshooting</a>.
 						</div></li><li class="listitem"><div class="para">
-							Fedora SELinux FAQ: <a href="http://docs.fedoraproject.org/selinux-faq/">http://docs.fedoraproject.org/selinux-faq/</a>.
+							Fedora Core 5 SELinux FAQ: <a href="http://docs.fedoraproject.org/selinux-faq-fc5/">http://docs.fedoraproject.org/selinux-faq-fc5/</a>.
 						</div></li><li class="listitem"><div class="para">
-							Guía de Administración de Servicios Confinados de SELinux: <a href="http://docs.fedoraproject.org/selinux-managing-confined-services-guide/">http://docs.fedoraproject.org/selinux-managing-confined-services-guide/</a>
+							SELinux Managing Confined Services Guide: <a href="http://docs.fedoraproject.org/selinux-managing-confined-services-guide/">http://docs.fedoraproject.org/selinux-managing-confined-services-guide/</a>
 						</div></li></ul></div>
 
-			</div><div class="formalpara"><h5 class="formalpara">Las Preguntas Frecuentes No Oficiales de SELinux</h5>
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Further_Information-The_UnOfficial_SELinux_FAQ"><h5 class="formalpara">Las Preguntas Frecuentes No Oficiales de SELinux</h5>
 				<a href="http://www.crypt.gen.nz/selinux/faq.html">http://www.crypt.gen.nz/selinux/faq.html</a>
-			</div><div class="formalpara"><h5 class="formalpara">IRC</h5>
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Further_Information-IRC"><h5 class="formalpara">IRC</h5>
 				En <a href="http://freenode.net/">Freenode</a>:
 			</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
 					#selinux
@@ -2150,15 +2141,12 @@ To make this policy package active, execute:
 					#fedora-selinux
 				</div></li><li class="listitem"><div class="para">
 					#security
-				</div></li></ul></div></div></div><div xml:lang="es-ES" class="appendix" title="Apéndice A. Historia de Revisiones" id="appe-Security-Enhanced_Linux-Revision_History" lang="es-ES"><div class="titlepage"><div><div><h1 class="title">Historia de Revisiones</h1></div></div></div><div class="para">
-		<div class="revhistory"><table border="0" width="100%" summary="Revision history"><tr><th align="left" valign="top" colspan="3"><b>Historial de revisiones</b></th></tr><tr><td align="left">Revisión 1.5</td><td align="left">Mon May 10 2010</td><td align="left"><span class="author"><span class="firstname">Scott</span> <span class="surname">Radvan</span></span></td></tr><tr><td align="left" colspan="3">
-					<table border="0" summary="Simple list" class="simplelist"><tr><td>Update and verification for Fedora 13</td></tr></table>
-
-				</td></tr><tr><td align="left">Revisión 1.4</td><td align="left">Mon Aug 31 2009</td><td align="left"><span class="author"><span class="firstname">Scott</span> <span class="surname">Radvan</span></span></td></tr><tr><td align="left" colspan="3">
-					<table border="0" summary="Simple list" class="simplelist"><tr><td>Actualización y verificación para Fedora 12</td></tr></table>
+				</div></li></ul></div></div></div><div xml:lang="es-ES" class="appendix" title="Apéndice A. Revision History" id="appe-Security-Enhanced_Linux-Revision_History" lang="es-ES"><div class="titlepage"><div><div><h1 class="title">Revision History</h1></div></div></div><div class="para">
+		<div class="revhistory"><table border="0" width="100%" summary="Revision history"><tr><th align="left" valign="top" colspan="3"><b>Historial de revisiones</b></th></tr><tr><td align="left">Revisión 1.4</td><td align="left">Mon Aug 31 2009</td><td align="left"><span class="author"><span class="firstname">Scott</span> <span class="surname">Radvan</span></span></td></tr><tr><td align="left" colspan="3">
+					<table border="0" summary="Simple list" class="simplelist"><tr><td>Update and verification for Fedora 12</td></tr></table>
 
 				</td></tr><tr><td align="left">Revisión 1.3</td><td align="left">Tue May 12 2009</td><td align="left"><span class="author"><span class="firstname">Scott</span> <span class="surname">Radvan</span></span></td></tr><tr><td align="left" colspan="3">
-					<table border="0" summary="Simple list" class="simplelist"><tr><td>Actualización y verificación para Fedora 11</td></tr></table>
+					<table border="0" summary="Simple list" class="simplelist"><tr><td>Update and verification for Fedora 11</td></tr></table>
 
 				</td></tr><tr><td align="left">Revisión 1.2</td><td align="left">Mon Jan 19 2009</td><td align="left"><span class="author"><span class="firstname">Murray</span> <span class="surname">McAllister</span></span></td></tr><tr><td align="left" colspan="3">
 					<table border="0" summary="Simple list" class="simplelist"><tr><td>Actualización de los enlaces a sitios web de la NSA</td></tr></table>
@@ -2167,7 +2155,7 @@ To make this policy package active, execute:
 					<table border="0" summary="Simple list" class="simplelist"><tr><td>Resolving <a href="https://bugzilla.redhat.com/show_bug.cgi?id=472986">Red Hat Bugzilla #472986, "httpd does not write to /etc/httpd/logs/"</a></td></tr><tr><td>Added new section, "6.6. Booleans for Users Executing Applications"</td></tr><tr><td>Revisiones menores del texto</td></tr></table>
 
 				</td></tr><tr><td align="left">Revisión 1.0</td><td align="left">Tue Nov 25 2008</td><td align="left"><span class="author"><span class="firstname">Murray</span> <span class="surname">McAllister</span></span></td></tr><tr><td align="left" colspan="3">
-					<table border="0" summary="Simple list" class="simplelist"><tr><td>El contenido inicial se guarda en <a href="http://docs.fedoraproject.org/">http://docs.fedoraproject.org/</a></td></tr></table>
+					<table border="0" summary="Simple list" class="simplelist"><tr><td>Initial content release on <a href="http://docs.fedoraproject.org/">http://docs.fedoraproject.org/</a></td></tr></table>
 
 				</td></tr></table></div>
 
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/Common_Content/css/common.css b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/Common_Content/css/common.css
index e1f4d9f..d8a380f 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/Common_Content/css/common.css
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/Common_Content/css/common.css
@@ -50,7 +50,8 @@ body.desktop .book > .toc {
 	line-height:1.35em;
 }
 
-.toc .chapter, .toc .appendix, .toc .glossary {
+ .toc .glossary,
+.toc .chapter, .toc .appendix {
 	margin-top:1em;
 }
 
@@ -59,7 +60,8 @@ body.desktop .book > .toc {
 	display:block;
 }
 
-span.appendix, span.glossary {
+span.glossary,
+span.appendix {
 	display:block;
 	margin-top:0.5em;
 }
@@ -346,7 +348,6 @@ a.version:focus, a.version:hover {
 	clear:both;
 }
 
-
 /*revision history*/
 .revhistory {
 	display:block;
@@ -362,34 +363,24 @@ a.version:focus, a.version:hover {
 }
 
 .revhistory td {
-	text-align:right;
+	text-align :left;
 	padding:0em;
 	border: none;
 	border-top: 1px solid #fff;
+	font-weight: bold;
 }
 
-
-.revhistory tr td:first-child {
-	text-align:left;
+.revhistory .simplelist td {
+	font-weight: normal;
 }
 
-.revhistory tr td p, .revhistory tr td div.para {
-	text-align:left;
-	font-weight:bold;
-	display:block;
-	margin:0em;
-	padding:0em;
-	padding-bottom:0.7em;
-	border-bottom:1px solid #eee;
+.revhistory .simplelist {
+	margin-bottom: 1.5em;
+	margin-left: 1em;
 }
 
 .revhistory table th {
-	background-color:transparent;
-	color:#336699;
-	font-size:2em;
-	padding: 1em 0em;
-	border: none;
-	border-bottom:1px solid #eee;
+	display: none;
 }
 
 
@@ -901,6 +892,10 @@ th, td {
 	border: 1px solid #000;
 }
 
+.simplelist th, .simplelist td {
+	border: none;
+}
+
 table table td {
 	border-bottom:1px dotted #aaa;
 	background-color:white;
@@ -1007,7 +1002,8 @@ span.chapter {
 	margin-bottom:1em;
 }
 
-.glossary dt, .index dt {
+.glossary dt,
+.index dt {
 	color:#444;
 	padding-top:.5em;
 }
@@ -1375,10 +1371,6 @@ pre {
 	border-radius: 15px;
 }
 
-.term{
-	color:#336699;
-}
-
 .package, .citetitle {
 	font-style: italic;
 }
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/Common_Content/css/lang.css b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/Common_Content/css/lang.css
index e69de29..81c3115 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/Common_Content/css/lang.css
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/Common_Content/css/lang.css
@@ -0,0 +1,2 @@
+/* place holder */
+
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/appe-Security-Enhanced_Linux-Revision_History.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/appe-Security-Enhanced_Linux-Revision_History.html
index d84359c..86c65b3 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/appe-Security-Enhanced_Linux-Revision_History.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/appe-Security-Enhanced_Linux-Revision_History.html
@@ -1,14 +1,11 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Apéndice A. Historia de Revisiones</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="prev" href="sect-Security-Enhanced_Linux-Further_Information-Other_Resources.html" title="8.2. Otros Recursos" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="ht
 tp://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Further_Information-Other_Resources.html"><strong>Anterior</strong></a></li><li class="next"></li></ul><div xml:lang="es-ES" class="appendix" title="Apéndice A. Historia de Revisiones" id="appe-Security-Enhanced_Linux-Revision_History" lang="es-ES"><div class="titlepage"><div><div><h1 class="title">Historia de Revisiones</h1></div></div></div><div class="para">
-		<div class="revhistory"><table border="0" width="100%" summary="Revision history"><tr><th align="left" valign="top" colspan="3"><b>Historial de revisiones</b></th></tr><tr><td align="left">Revisión 1.5</td><td align="left">Mon May 10 2010</td><td align="left"><span class="author"><span class="firstname">Scott</span> <span class="surname">Radvan</span></span></td></tr><tr><td align="left" colspan="3">
-					<table border="0" summary="Simple list" class="simplelist"><tr><td>Update and verification for Fedora 13</td></tr></table>
-
-				</td></tr><tr><td align="left">Revisión 1.4</td><td align="left">Mon Aug 31 2009</td><td align="left"><span class="author"><span class="firstname">Scott</span> <span class="surname">Radvan</span></span></td></tr><tr><td align="left" colspan="3">
-					<table border="0" summary="Simple list" class="simplelist"><tr><td>Actualización y verificación para Fedora 12</td></tr></table>
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Apéndice A. Revision History</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="prev" href="sect-Security-Enhanced_Linux-Further_Information-Other_Resources.html" title="8.2. Other Resources" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="h
 ttp://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Further_Information-Other_Resources.html"><strong>Anterior</strong></a></li><li class="next"></li></ul><div xml:lang="es-ES" class="appendix" title="Apéndice A. Revision History" id="appe-Security-Enhanced_Linux-Revision_History" lang="es-ES"><div class="titlepage"><div><div><h1 class="title">Revision History</h1></div></div></div><div class="para">
+		<div class="revhistory"><table border="0" width="100%" summary="Revision history"><tr><th align="left" valign="top" colspan="3"><b>Historial de revisiones</b></th></tr><tr><td align="left">Revisión 1.4</td><td align="left">Mon Aug 31 2009</td><td align="left"><span class="author"><span class="firstname">Scott</span> <span class="surname">Radvan</span></span></td></tr><tr><td align="left" colspan="3">
+					<table border="0" summary="Simple list" class="simplelist"><tr><td>Update and verification for Fedora 12</td></tr></table>
 
 				</td></tr><tr><td align="left">Revisión 1.3</td><td align="left">Tue May 12 2009</td><td align="left"><span class="author"><span class="firstname">Scott</span> <span class="surname">Radvan</span></span></td></tr><tr><td align="left" colspan="3">
-					<table border="0" summary="Simple list" class="simplelist"><tr><td>Actualización y verificación para Fedora 11</td></tr></table>
+					<table border="0" summary="Simple list" class="simplelist"><tr><td>Update and verification for Fedora 11</td></tr></table>
 
 				</td></tr><tr><td align="left">Revisión 1.2</td><td align="left">Mon Jan 19 2009</td><td align="left"><span class="author"><span class="firstname">Murray</span> <span class="surname">McAllister</span></span></td></tr><tr><td align="left" colspan="3">
 					<table border="0" summary="Simple list" class="simplelist"><tr><td>Actualización de los enlaces a sitios web de la NSA</td></tr></table>
@@ -17,8 +14,8 @@
 					<table border="0" summary="Simple list" class="simplelist"><tr><td>Resolving <a href="https://bugzilla.redhat.com/show_bug.cgi?id=472986">Red Hat Bugzilla #472986, "httpd does not write to /etc/httpd/logs/"</a></td></tr><tr><td>Added new section, "6.6. Booleans for Users Executing Applications"</td></tr><tr><td>Revisiones menores del texto</td></tr></table>
 
 				</td></tr><tr><td align="left">Revisión 1.0</td><td align="left">Tue Nov 25 2008</td><td align="left"><span class="author"><span class="firstname">Murray</span> <span class="surname">McAllister</span></span></td></tr><tr><td align="left" colspan="3">
-					<table border="0" summary="Simple list" class="simplelist"><tr><td>El contenido inicial se guarda en <a href="http://docs.fedoraproject.org/">http://docs.fedoraproject.org/</a></td></tr></table>
+					<table border="0" summary="Simple list" class="simplelist"><tr><td>Initial content release on <a href="http://docs.fedoraproject.org/">http://docs.fedoraproject.org/</a></td></tr></table>
 
 				</td></tr></table></div>
 
-	</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Further_Information-Other_Resources.html"><strong>Anterior</strong>8.2. Otros Recursos</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li></ul></body></html>
+	</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Further_Information-Other_Resources.html"><strong>Anterior</strong>8.2. Other Resources</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Confining_Users.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Confining_Users.html
index 234cb98..38fcef4 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Confining_Users.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Confining_Users.html
@@ -1,7 +1,7 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Capítulo 6. Confinando a los Usuarios</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="prev" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_star.html" title="5.10.5. Archivando archivos con tar" /><link rel="next" href="sect-Security-Enhanced_Linux-Confining_Users-Confining_New_Linux_Users_useradd.html" title="6.2. Confinando Usuarios Nuevos de Linux: useradd" /></head><body class="toc_embeded "><div id="tocdi
 v" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_star.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Confining_Users-Confining_New_Linux_Users_useradd.html"><strong>Siguiente</strong></a></li></ul><div xml:lang="es-ES" class="chapter" title="Capítulo 6. Confinando a los Usuarios" id="chap-Security-Enhanced_Linux-Confining_Users" lang="es-ES"><div class="titlepage"><div><div><h2 class="ti
 tle">Capítulo 6. Confinando a los Usuarios</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-Confining_Users.html#sect-Security-Enhanced_Linux-Confining_Users-Linux_and_SELinux_User_Mappings">6.1. Linux y los Mapeos de Usuarios de SELinux</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Confining_Users-Confining_New_Linux_Users_useradd.html">6.2. Confinando Usuarios Nuevos de Linux: useradd</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Confining_Users-Confining_Existing_Linux_Users_semanage_login.html">6.3. Confinando Usuarios Linux Existentes: semanage login</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Confining_Users-Changing_the_Default_Mapping.html">6.4. Cambiando el Mapeo Predeterminado</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Confining_Users-xguest_Kiosk_Mode.html">6.5. xguest: M
 odo Kiosk</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications.html">6.6. Booleanos para que los Usuarios Ejecuten Aplicaciones</a></span></dt></dl></div><div class="para">
-		Un número de usuarios confinados SELinux están disponibles en Fedora 13. Cada usuario Linux se mapea aun usuario SELinux vía la política de SELinux, permitiendo a los usuarios Linux heredar las restricciones sobre los usuarios SELinux, por ejemplo (dependiendo del usuairo), no poder: ejecutar el sistema de ventanas X; usar la red; ejecutar aplicaciones setuid (a menos que la política de SELinux lo permita); o ejecutar comandos <code class="command">su</code> y <code class="command">sudo</code> para volverse el usuario root de Linux. Esto ayuda a proteger el sistema del usuario. Vaya a <a class="xref" href="sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users.html" title="4.3. Usuarios Confinados y no Confinados">Sección 4.3, “Usuarios Confinados y no Confinados”</a> para información adicional sobre usuarios confinados.
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Capítulo 6. Confinando a los Usuarios</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="prev" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_star.html" title="5.10.5. Archivando archivos con tar" /><link rel="next" href="sect-Security-Enhanced_Linux-Confining_Users-Confining_New_Linux_Users_useradd.html" title="6.2. Confinando Usuarios Nuevos de Linux: useradd" /></head><body class="draft toc_embeded "><div id=
 "tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_star.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Confining_Users-Confining_New_Linux_Users_useradd.html"><strong>Siguiente</strong></a></li></ul><div xml:lang="es-ES" class="chapter" title="Capítulo 6. Confinando a los Usuarios" id="chap-Security-Enhanced_Linux-Confining_Users" lang="es-ES"><div class="titlepage"><div><div><h2 cla
 ss="title">Capítulo 6. Confinando a los Usuarios</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-Confining_Users.html#sect-Security-Enhanced_Linux-Confining_Users-Linux_and_SELinux_User_Mappings">6.1. Linux y los Mapeos de Usuarios de SELinux</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Confining_Users-Confining_New_Linux_Users_useradd.html">6.2. Confinando Usuarios Nuevos de Linux: useradd</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Confining_Users-Confining_Existing_Linux_Users_semanage_login.html">6.3. Confinando Usuarios Linux Existentes: semanage login</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Confining_Users-Changing_the_Default_Mapping.html">6.4. Cambiando el Mapeo Predeterminado</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Confining_Users-xguest_Kiosk_Mode.html">6.5. xgu
 est: Modo Kiosk</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications.html">6.6. Booleanos para que los Usuarios Ejecuten Aplicaciones</a></span></dt></dl></div><div class="para">
+		A number of confined SELinux users are available in Fedora 13. Each Linux user is mapped to an SELinux user via SELinux policy, allowing Linux users to inherit the restrictions placed on SELinux users, for example (depending on the user), not being able to: run the X Window System; use networking; run setuid applications (unless SELinux policy permits it); or run the <code class="command">su</code> and <code class="command">sudo</code> commands. This helps protect the system from the user. Refer to <a class="xref" href="sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users.html" title="4.3. Usuarios Confinados y no Confinados">Sección 4.3, “Usuarios Confinados y no Confinados”</a> for further information about confined users.
 	</div><div class="section" title="6.1. Linux y los Mapeos de Usuarios de SELinux" id="sect-Security-Enhanced_Linux-Confining_Users-Linux_and_SELinux_User_Mappings"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.1. Linux y los Mapeos de Usuarios de SELinux</h2></div></div></div><div class="para">
 			Como usuario root de Linux, corra el comando <code class="command">semanage login -l</code> para ver el mapeo entre los usuarios de Linux y los usuarios de SELinux:
 		</div><pre class="screen"># /usr/sbin/semanage login -l
@@ -13,7 +13,7 @@ root                      unconfined_u              s0-s0:c0.c1023
 system_u                  system_u                  s0-s0:c0.c1023
 
 </pre><div class="para">
-			En Fedora 13, los usuarios Linux se mapean al ingreso SELinux <code class="computeroutput">__default__</code> por defecto (que se mapea al usuario SELinux <code class="computeroutput">unconfined_u</code>). Cuando se crea un usuario Linux con el comando <code class="command">useradd</code>, si no se especifica ninguna opcion, son mapeados al usuario SELinux <code class="computeroutput">unconfined_u</code>. Lo siguiente define el mapeo por defecto:
+			In Fedora 13, Linux users are mapped to the SELinux <code class="computeroutput">__default__</code> login by default (which is in turn mapped to the SELinux <code class="computeroutput">unconfined_u</code> user). When a Linux user is created with the <code class="command">useradd</code> command, if no options are specified, they are mapped to the SELinux <code class="computeroutput">unconfined_u</code> user. The following defines the default-mapping:
 		</div><pre class="screen">
 __default__               unconfined_u              s0-s0:c0.c1023
 
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Further_Information.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Further_Information.html
index 1eaa013..d1f5cfa 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Further_Information.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Further_Information.html
@@ -1,9 +1,9 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Capítulo 8. Información Adicional</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="prev" href="sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow.html" title="7.3.8. Permitiendo el Acceso: audit2allow" /><link rel="next" href="sect-Security-Enhanced_Linux-Further_Information-Other_Resources.html" title="8.2. Otros Recursos" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" sr
 c="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Further_Information-Other_Resources.html"><strong>Siguiente</strong></a></li></ul><div xml:lang="es-ES" class="chapter" title="Capítulo 8. Información Adicional" id="chap-Security-Enhanced_Linux-Further_Information" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 8. Información Adicional</h2></div></div></div><div class=
 "toc"><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-Further_Information.html#sect-Security-Enhanced_Linux-Further_Information-Contributors">8.1. Contribuyentes</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Further_Information-Other_Resources.html">8.2. Otros Recursos</a></span></dt></dl></div><div class="section" title="8.1. Contribuyentes" id="sect-Security-Enhanced_Linux-Further_Information-Contributors"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">8.1. Contribuyentes</h2></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-					<a href="http://fedoraproject.org/wiki/GeertWarrink">Geert Warrink</a> (traducción - Danés)
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Capítulo 8. Información Adicional</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="prev" href="sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow.html" title="7.3.8. Permitiendo el Acceso: audit2allow" /><link rel="next" href="sect-Security-Enhanced_Linux-Further_Information-Other_Resources.html" title="8.2. Other Resources" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="
 toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Further_Information-Other_Resources.html"><strong>Siguiente</strong></a></li></ul><div xml:lang="es-ES" class="chapter" title="Capítulo 8. Información Adicional" id="chap-Security-Enhanced_Linux-Further_Information" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 8. Información Adicional</h2></div></div></div><div
  class="toc"><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-Further_Information.html#sect-Security-Enhanced_Linux-Further_Information-Contributors">8.1. Contributors</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Further_Information-Other_Resources.html">8.2. Other Resources</a></span></dt></dl></div><div class="section" title="8.1. Contributors" id="sect-Security-Enhanced_Linux-Further_Information-Contributors"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">8.1. Contributors</h2></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+					<a href="http://fedoraproject.org/wiki/GeertWarrink">Geert Warrink</a> (translation - Dutch)
 				</div></li><li class="listitem"><div class="para">
-					<a href="http://fedoraproject.org/wiki/User:Beckerde">Domingo Becker</a> (traducción - Español)
+					<a href="http://fedoraproject.org/wiki/User:Beckerde">Domingo Becker</a> (translation - Spanish)
 				</div></li><li class="listitem"><div class="para">
-					<a href="http://fedoraproject.org/wiki/User:Logan">Daniel Cabrera</a> (traducción - Español)
-				</div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow.html"><strong>Anterior</strong>7.3.8. Permitiendo el Acceso: audit2allow</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Further_Information-Other_Resources.html"><strong>Siguiente</strong>8.2. Otros Recursos</a></li></ul></body></html>
+					<a href="http://fedoraproject.org/wiki/User:Logan">Daniel Cabrera</a> (translation - Spanish)
+				</div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow.html"><strong>Anterior</strong>7.3.8. Permitiendo el Acceso: audit2allow</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Further_Information-Other_Resources.html"><strong>Siguiente</strong>8.2. Other Resources</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Introduction.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Introduction.html
index d297278..4725b49 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Introduction.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Introduction.html
@@ -1,28 +1,28 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Capítulo 2. Introducción</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="prev" href="chap-Security-Enhanced_Linux-Trademark_Information.html" title="Capítulo 1. Información de Marca Comercial" /><link rel="next" href="sect-Security-Enhanced_Linux-Introduction-Examples.html" title="2.2. Ejemplos" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to v
 iew it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-Trademark_Information.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Introduction-Examples.html"><strong>Siguiente</strong></a></li></ul><div xml:lang="es-ES" class="chapter" title="Capítulo 2. Introducción" id="chap-Security-Enhanced_Linux-Introduction" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 2. Introducción</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-Introduction.html#sect-Security-Enh
 anced_Linux-Introduction-Benefits_of_running_SELinux">2.1. Beneficios de usar SELinux</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Introduction-Examples.html">2.2. Ejemplos</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture.html">2.3. Arquitectura de SELinux</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Introduction-SELinux_on_Other_Operating_Systems.html">2.4. SELinux en otros Sistemas Operativos</a></span></dt></dl></div><div class="para">
-		Linux con Seguridad Mejorada (SELinux) es una implementación de un mecanismo de <em class="firstterm">control de acceso obligatorio</em> en el kernel de Linux, para chequear si las operaciones son permitidas después de los <em class="firstterm">controles de acceso discrecionales</em> estándares.
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Capítulo 2. Introducción</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="prev" href="chap-Security-Enhanced_Linux-Trademark_Information.html" title="Capítulo 1. Información de Marca Comercial" /><link rel="next" href="sect-Security-Enhanced_Linux-Introduction-Examples.html" title="2.2. Ejemplos" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe
 , to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-Trademark_Information.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Introduction-Examples.html"><strong>Siguiente</strong></a></li></ul><div xml:lang="es-ES" class="chapter" title="Capítulo 2. Introducción" id="chap-Security-Enhanced_Linux-Introduction" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 2. Introducción</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-Introduction.html#sect-Securi
 ty-Enhanced_Linux-Introduction-Benefits_of_running_SELinux">2.1. Beneficios de usar SELinux</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Introduction-Examples.html">2.2. Ejemplos</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture.html">2.3. Arquitectura de SELinux</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Introduction-SELinux_on_Other_Operating_Systems.html">2.4. SELinux en otros Sistemas Operativos</a></span></dt></dl></div><div class="para">
+		Security-Enhanced Linux (SELinux) is an implementation of a <em class="firstterm">mandatory access control</em> mechanism in the Linux kernel, checking for allowed operations after standard <em class="firstterm">discretionary access controls</em> are checked. It was created by the National Security Agency and can enforce rules on files and processes in a Linux system, and on their actions, based on defined policy.
 	</div><div class="para">
-		Los Archivos, tales como directorios y dispositivos, se llaman objetos. Los procesos, tal como un comando que ejecuta el usuario o la aplicación <span class="trademark">Mozilla</span>®<span class="trademark"> Firefox</span>®, se llaman sujetos. La mayoría de los sistemas oeprativos usan un sistema de Control de Acceso Discrecional (DAC), que controla cómo interactúan los sujetos con los objetos, y cómo los sujetos interactuan entre sí. En sistemas operativos que usan DAC, los usuarios controlan los permisos de archivos (objetos) de los que son dueños. Por ejemplo, en sistemas operativos <span class="trademark">Linux</span>®, los usuarios pueden hacer sus directorios legibles para el resto del mundo, dando a los usuarios y procesos (sujetos) acceso a información potencialmente sensible, sin protección adicional sobre esta acción indeseada.
+		When using SELinux, files, including directories and devices, are referred to as objects. Processes, such as a user running a command or the <span class="trademark">Mozilla</span>®<span class="trademark"> Firefox</span>® application, are referred to as subjects. Most operating systems use a Discretionary Access Control (DAC) system that controls how subjects interact with objects, and how subjects interact with each other. On operating systems using DAC, users control the permissions of files (objects) that they own. For example, on <span class="trademark">Linux</span>® operating systems, users could make their home directories world-readable, giving users and processes (subjects) access to potentially sensitive information, with no further protection over this unwanted action.
 	</div><div class="para">
-		Relying on DAC mechanisms alone is fundamentally inadequate for strong system security. DAC access decisions are only based on user identity and ownership, ignoring other security-relevant information such as the role of the user, the function and trustworthiness of the program, and the sensitivity and integrity of the data. Each user has complete discretion over their files, making it impossible to enforce a system-wide security policy. Furthermore, every program run by a user inherits all of the permissions granted to the user and is free to change access to the user's files, so no protection is provided against malicious software. Many system services and privileged programs must run with coarse-grained privileges that far exceed their requirements, so that a flaw in any one of these programs could be exploited to obtain further system access.<sup>[<a id="id2083135" href="#ftn.id2083135" class="footnote">1</a>]</sup>
+		Relying on DAC mechanisms alone is fundamentally inadequate for strong system security. DAC access decisions are only based on user identity and ownership, ignoring other security-relevant information such as the role of the user, the function and trustworthiness of the program, and the sensitivity and integrity of the data. Each user has complete discretion over their files, making it impossible to enforce a system-wide security policy. Furthermore, every program run by a user inherits all of the permissions granted to the user and is free to change access to the user's files, so no protection is provided against malicious software. Many system services and privileged programs must run with coarse-grained privileges that far exceed their requirements, so that a flaw in any one of these programs could be exploited to obtain further system access.<sup>[<a id="id1060393" href="#ftn.id1060393" class="footnote">1</a>]</sup>
 	</div><div class="para">
-		El siguiente es un ejemplo de permisos usados en sistemas operativos Linux que no corren el Linux con Seguridad Mejorada (SELinux). Los permisos en estos ejemplos pueden diferir de su sistema. Use el comando <code class="command">ls -l</code> para ver los permisos de archivos:
+		The following is an example of permissions used on Linux operating systems that do not run Security-Enhanced Linux (SELinux). The permissions and output in these examples may differ from your system. Use the <code class="command">ls -l</code> command to view file permissions:
 	</div><pre class="screen">$ ls -l file1
--rw-rw-r--. 1 user1 group1 0 May 11 10:46 file1
+-rwxrw-r-- 1 user1 group1 0 2009-08-30 11:03 file1
 
 </pre><div class="para">
-		The first three permission bits, <code class="computeroutput">rw</code>, control the access the Linux <code class="computeroutput">user1</code> user (in this case, the owner) has to <code class="filename">file1</code>. The next three permission bits, <code class="computeroutput">rw-</code>, control the access the Linux <code class="computeroutput">group1</code> group has to <code class="filename">file1</code>. The last three permission bits, <code class="computeroutput">r--</code>, control the access everyone else has to <code class="filename">file1</code>, which includes all users and processes.
+		Los primeros tres bits de permisos, <code class="computeroutput">rwx</code>, controlan el acceso que el usuario Linux <code class="computeroutput">usuario1</code> (en este caso, el dueño) tiene para el <code class="filename">archivo1</code>. Los siguientes tres bits de permisos, <code class="computeroutput">rw-</code>, controlan el acceso que el grupo Linux <code class="computeroutput">grupo1</code> tiene para el <code class="filename">archivo1</code>. Los últimos tres bits de permisos, <code class="computeroutput">r--</code>, controlan el acceso que todo el mundo tiene para el <code class="filename">archivo1</code>, que incluyen a todos los usuarios y procesos.
 	</div><div class="para">
-		Security-Enhanced Linux (SELinux) adds Mandatory Access Control (MAC) to the Linux kernel, and is enabled by default in Fedora. A general purpose MAC architecture needs the ability to enforce an administratively-set security policy over all processes and files in the system, basing decisions on labels containing a variety of security-relevant information. When properly implemented, it enables a system to adequately defend itself and offers critical support for application security by protecting against the tampering with, and bypassing of, secured applications. MAC provides strong separation of applications that permits the safe execution of untrustworthy applications. Its ability to limit the privileges associated with executing processes limits the scope of potential damage that can result from the exploitation of vulnerabilities in applications and system services. MAC enables information to be protected from legitimate users with limited authorization as well as from a
 uthorized users who have unwittingly executed malicious applications.<sup>[<a id="id2063648" href="#ftn.id2063648" class="footnote">2</a>]</sup>
+		Security-Enhanced Linux (SELinux) adds Mandatory Access Control (MAC) to the Linux kernel, and is enabled by default in Fedora. A general purpose MAC architecture needs the ability to enforce an administratively-set security policy over all processes and files in the system, basing decisions on labels containing a variety of security-relevant information. When properly implemented, it enables a system to adequately defend itself and offers critical support for application security by protecting against the tampering with, and bypassing of, secured applications. MAC provides strong separation of applications that permits the safe execution of untrustworthy applications. Its ability to limit the privileges associated with executing processes limits the scope of potential damage that can result from the exploitation of vulnerabilities in applications and system services. MAC enables information to be protected from legitimate users with limited authorization as well as from a
 uthorized users who have unwittingly executed malicious applications.<sup>[<a id="id843044" href="#ftn.id843044" class="footnote">2</a>]</sup>
 	</div><div class="para">
-		El siguiente es un ejemplo de las etiquetas que contienen información de seguridad relevante que se usa en los procesos, usuarios Linux y archivos, en sistemas operativos Linux que corren SELinux. Esta información se llama contexto de SELinux y se visualiza usando el comando <code class="command">ls -Z</code>:
+		The following is an example of the labels containing security-relevant information that are used on processes, Linux users, and files, on Linux operating systems that run SELinux. This information is called the SELinux <span class="emphasis"><em>context</em></span>, and is viewed using the <code class="command">ls -Z</code> command:
 	</div><pre class="screen">$ ls -Z file1
--rw-rw-r--. user1 group1 unconfined_u:object_r:user_home_t:s0 file1
+-rwxrw-r--  user1 group1 unconfined_u:object_r:user_home_t:s0      file1
 
 </pre><div class="para">
-		En este ejemplo, SELinux provee un usuario (<code class="computeroutput">unconfined_u</code>), un rol (<code class="computeroutput">object_r</code>), un tipo (<code class="computeroutput">user_home_t</code>), y un nivel (<code class="computeroutput">s0</code>). Esta información se usa para tomar decisiones sobre el control de acceso. Con DAC, el acceso se controla basado sólo en los IDs de usuarios y grupos de Linux. Las reglas de políticas de SELinux se chequean <span class="emphasis"><em>después</em></span> de las reglas DAC. Las reglas de políticas de SELInux no se usan si las reglas DAC niegan el acceso al principio.
-	</div><div class="formalpara"><h5 class="formalpara">Linux y los Usuarios SELinux</h5>
+		In this example, SELinux provides a user (<code class="computeroutput">unconfined_u</code>), a role (<code class="computeroutput">object_r</code>), a type (<code class="computeroutput">user_home_t</code>), and a level (<code class="computeroutput">s0</code>). This information is used to make access control decisions. With DAC, access is controlled based only on Linux user and group IDs. It is important to remember that SELinux policy rules are checked <span class="emphasis"><em>after</em></span> DAC rules. SELinux policy rules are not used if DAC rules deny access first.
+	</div><div class="formalpara" id="form-Security-Enhanced_Linux-Introduction-Linux_and_SELinux_Users"><h5 class="formalpara">Linux y los Usuarios SELinux</h5>
 			On Linux operating systems that run SELinux, there are Linux users as well as SELinux users. SELinux users are part of SELinux policy. Linux users are mapped to SELinux users. To avoid confusion, this guide uses "Linux user" and "SELinux user" to differentiate between the two.
 		</div><div class="section" title="2.1. Beneficios de usar SELinux" id="sect-Security-Enhanced_Linux-Introduction-Benefits_of_running_SELinux"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.1. Beneficios de usar SELinux</h2></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
 					Todos los procesos y archivos se etiquetan con un tipo. Un tipo define un dominio para los procesos y un tipo para los archivos. Los procesos se separan entre sí corriéndolos en sus propios dominios, y las reglas de políticas de SELinux define cómo interactúan los procesos con los archivos, así como la forma en que interactúan entre sí. El acceso sólo se permite si existe una regla de política de SELinux que específicamente lo permita.
@@ -31,9 +31,7 @@
 				</div></li><li class="listitem"><div class="para">
 					La política de SELinux se define administrativamente, obligando a todo el sistema, y no se pone a discreción del usuario.
 				</div></li><li class="listitem"><div class="para">
-					Vulnerabilidad reducida para ataques de escalamiento de privilegios. Un ejemplo: dado que los procesos corren en dominios, y son por lo tanto separados entre si, y las reglas de la política de SELinux definen cómo los procesos acceden a los archivos y a otros procesos, si un proceso queda comprometido, el atacante sólo tiene acceso a las funciones normales de ese proceso, y a archivos a los que el proceso tiene configurado que puede acceder. Por ejemplo, si el Servidor HTTP Apache es comprometido, un atacante no puede usar el proceso para leer archivos en los directorios home de los usuarios, a menos que una regla específica de la política de SELinux haya sido agregada o configurada para permitir tal acceso.
-				</div></li><li class="listitem"><div class="para">
-					Confined services. SELinux ships with the ability to confine services and daemons so that they are more predictable and are only allowed access that is required for their normal operation.
+					Reduced vulnerability to privilege escalation attacks. One example: since processes run in domains, and are therefore separated from each other, and because SELinux policy rules define how processes access files and other processes, if a process is compromised, the attacker only has access to the normal functions of that process, and to files the process has been configured to have access to. For example, if the Apache HTTP Server is compromised, an attacker can not use that process to read files in user home directories, unless a specific SELinux policy rule was added or configured to allow such access.
 				</div></li><li class="listitem"><div class="para">
 					Se linux se puede usar para asegurar la confidencialidad e integridad de los datos, así como proteger los procesos de entradas no confiables.
 				</div></li></ul></div><div class="para">
@@ -45,9 +43,9 @@
 				</div></li><li class="listitem"><div class="para">
 					una solución todo en uno.
 				</div></li></ul></div><div class="para">
-			SELinux is designed to enhance existing security solutions, not replace them. Even when running SELinux, it is important to continue to follow good security practices, such as keeping software up-to-date, using hard-to-guess passwords, firewalls, and so on.
-		</div></div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id2083135" href="#id2083135" class="para">1</a>] </sup>
+			SELinux está diseñado para mejorar las soluciones de seguridad existentes, no reemplazarlas. Aún cuando corra SELinux, siga las buenas prácticas de seguridad, tales como mantener el software actualizado, usar contraseñas difíciles de adivinar, cortafuegos y demás.
+		</div></div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id1060393" href="#id1060393" class="para">1</a>] </sup>
 			"Integrating Flexible Support for Security Policies into the Linux Operating System", by Peter Loscocco and Stephen Smalley. This paper was originally prepared for the National Security Agency and is, consequently, in the public domain. Refer to the <a href="http://www.nsa.gov/research/_files/selinux/papers/freenix01/index.shtml">original paper</a> for details and the document as it was first released. Any edits and changes were done by Murray McAllister.
-		</p></div><div class="footnote"><p><sup>[<a id="ftn.id2063648" href="#id2063648" class="para">2</a>] </sup>
+		</p></div><div class="footnote"><p><sup>[<a id="ftn.id843044" href="#id843044" class="para">2</a>] </sup>
 			"Meeting Critical Security Objectives with Security-Enhanced Linux", by Peter Loscocco and Stephen Smalley. This paper was originally prepared for the National Security Agency and is, consequently, in the public domain. Refer to the <a href="http://www.nsa.gov/research/_files/selinux/papers/ottawa01/index.shtml">original paper</a> for details and the document as it was first released. Any edits and changes were done by Murray McAllister.
 		</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-Trademark_Information.html"><strong>Anterior</strong>Capítulo 1. Información de Marca Comercial</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Introduction-Examples.html"><strong>Siguiente</strong>2.2. Ejemplos</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-SELinux_Contexts.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-SELinux_Contexts.html
index f60171a..3abc6e1 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-SELinux_Contexts.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-SELinux_Contexts.html
@@ -1,16 +1,16 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Capítulo 3. Contextos de SELinux</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="prev" href="sect-Security-Enhanced_Linux-Introduction-SELinux_on_Other_Operating_Systems.html" title="2.4. SELinux en otros Sistemas Operativos" /><link rel="next" href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Processes.html" title="3.2. Contextos de SELinux para los Procesos" /></head><body class="toc_embeded "><div id="tocdiv" class="toc
 "><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Introduction-SELinux_on_Other_Operating_Systems.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Processes.html"><strong>Siguiente</strong></a></li></ul><div xml:lang="es-ES" class="chapter" title="Capítulo 3. Contextos de SELinux" id="chap-Security-Enhanced_Linux-SELinux_Contexts" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 3. Context
 os de SELinux</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-SELinux_Contexts.html#sect-Security-Enhanced_Linux-SELinux_Contexts-Domain_Transitions">3.1. Transiciones de Dominios</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Processes.html">3.2. Contextos de SELinux para los Procesos</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Users.html">3.3. Contextos de SELinux para los Usuarios</a></span></dt></dl></div><div class="para">
-		Los procesos y archivos se etiquetan con un contexto SELinux que contiene información adicional, tal como un usuario SELinux, rol, tipo y, opcionalmente, un nivel. Cuando se ejecuta SELinux, toda esta información se usa para tomar decisiones de control de acceso. En Fedora, SELinux provee una combinación de Control de Acceso Basado en Roles (RBAC en inglés), <span class="trademark">Obediencia de Tipos</span>® (TE en inglés), y, opcionalmente, Seguridad Multi-nivel (MLS en inglés).
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Capítulo 3. Contextos de SELinux</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="prev" href="sect-Security-Enhanced_Linux-Introduction-SELinux_on_Other_Operating_Systems.html" title="2.4. SELinux en otros Sistemas Operativos" /><link rel="next" href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Processes.html" title="3.2. Contextos de SELinux para los Procesos" /></head><body class="draft toc_embeded "><div id="tocdiv" clas
 s="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Introduction-SELinux_on_Other_Operating_Systems.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Processes.html"><strong>Siguiente</strong></a></li></ul><div xml:lang="es-ES" class="chapter" title="Capítulo 3. Contextos de SELinux" id="chap-Security-Enhanced_Linux-SELinux_Contexts" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 3. C
 ontextos de SELinux</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-SELinux_Contexts.html#sect-Security-Enhanced_Linux-SELinux_Contexts-Domain_Transitions">3.1. Transiciones de Dominios</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Processes.html">3.2. Contextos de SELinux para los Procesos</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Users.html">3.3. Contextos de SELinux para los Usuarios</a></span></dt></dl></div><div class="para">
+		Processes and files are labeled with an SELinux context that contains additional information, such as an SELinux user, role, type, and, optionally, a level. When running SELinux, all of this information is used to make access control decisions. In Fedora, SELinux provides a combination of Role-Based Access Control (RBAC), <span class="trademark">Type Enforcement</span>® (TE), and, optionally, Multi-Level Security (MLS).
 	</div><div class="para">
-		El siguiente es un ejemplo de contexto de SELinux. Los contextos de SELinux se usan en procesos, usuarios de Linux y archivos, en sistemas operativos Linux que corren SELinux. Use el comando <code class="command">ls -Z</code> para ver el contexto SELinux de archivos y directorios:
+		The following is an example showing SELinux context. SELinux contexts are used on processes, Linux users, and files, on Linux operating systems that run SELinux. Use the <code class="command">ls -Z</code> command to view the SELinux context of files and directories:
 	</div><pre class="screen">$ ls -Z file1
--rw-rw-r--. user1 group1 unconfined_u:object_r:user_home_t:s0 file1
+-rwxrw-r--  user1 group1 unconfined_u:object_r:user_home_t:s0      file1
 
 </pre><div class="para">
 		Los contextos de SELinux siguen la <span class="emphasis"><em>SELinux nombre-de-usuario:role:type:level</em></span> sintaxis:
-	</div><div class="variablelist"><dl><dt><span class="term"><span class="emphasis"><em>Usuario SELinux</em></span></span></dt><dd><div class="para">
-					La identidad de usuario SELinux es una identidad conocida para la política a la que se le autoriza un conjunto específico de roles, y un rango específico de MLS. Cada usuario Linux se mapea a un usuario SELinux vía la política de SELinux. Esto permite a los usuarios de Linux heredar las restricciones de los usuarios SELinux. La identidad del usuario SELinux mapeado se usa en el contexto de SELinux para procesos en esa sesión, para definir a qué roles y niveles pueden ingresar. Ejecute el comando <code class="command">semanage login -l</code> como usuario root de Linux para ver una lista de mapeos entre cuentas de usuarios Linux y SELinux:
+	</div><div class="variablelist"><dl><dt><span class="term"><span class="emphasis"><em>SELinux user</em></span></span></dt><dd><div class="para">
+					The SELinux user identity is an identity known to the policy that is authorized for a specific set of roles, and for a specific MLS range. Each Linux user is mapped to an SELinux user via SELinux policy. This allows Linux users to inherit the restrictions placed on SELinux users. The mapped SELinux user identity is used in the SELinux context for processes in that session, in order to define what roles and levels they can enter. Run the <code class="command">semanage login -l</code> command as the Linux root user to view a list of mappings between SELinux and Linux user accounts:
 				</div><pre class="screen">
 # /usr/sbin/semanage login -l
 
@@ -21,28 +21,28 @@ root                      unconfined_u              s0-s0:c0.c1023
 system_u                  system_u                  s0-s0:c0.c1023
 
 </pre><div class="para">
-					La salida puede ser distinta de sistema a sistema. La columna <code class="computeroutput">Nombre de Ingreso</code> lista los usuarios Linux, y la columna <code class="computeroutput">Usuario SELinux</code> lista qué a usuario SELinux es mapeado un usuario Linux. Para procesos, el usuario SELinux limita qué roles y niveles son accesibles. La última columna, <code class="computeroutput">Rango MLS/MCS</code>, es el nivel usado por la Seguridad Multi Nivel (MLS) y por la Seguridad Multi Categoría (MCS). Los niveles se describen brevemente más adelante.
-				</div></dd><dt><span class="term"><span class="emphasis"><em>rol</em></span></span></dt><dd><div class="para">
+					Output may differ slightly from system to system. The <code class="computeroutput">Login Name</code> column lists Linux users, and the <code class="computeroutput">SELinux User</code> column lists which SELinux user the Linux user is mapped to. For processes, the SELinux user limits which roles and levels are accessible. The last column, <code class="computeroutput">MLS/MCS Range</code>, is the level used by Multi-Level Security (MLS) and Multi-Category Security (MCS). Levels are briefly discussed later.
+				</div></dd><dt><span class="term"><span class="emphasis"><em>role</em></span></span></dt><dd><div class="para">
 					Parte de SELinux es el modelo de seguridad de Control de Acceso Basado en Roles (RBAC). El rol es un atributo de RBAC. Los usuarios de SELinux son autorizados para ciertos roles y los roles son autorizados para ciertos dominios. Los roles sirven como un intermediario entre dominios y usarios SELinux. Los roles en los que se puede ingresar determinan los dominios a los que se ingresan - al final, esto controla los tipos de objetos que se pueden acceder. Esto ayuda a reducir la vulnerabilidad de ataques de escalada de privilegios.
-				</div></dd><dt><span class="term"><span class="emphasis"><em>tipo</em></span></span></dt><dd><div class="para">
-					El tipo es un atributo de la Obediencia de Tipos. El tipo define un dominio para procesos y un tipo para los archivos. Las reglas de políticas de SELinux define cómo se acceden los tipos entre si, ya sea un dominio que accede a un tipo o un dominio que accede a otro dominio. Los acceso sólo se permiten si existe una regla de política de SELinux que lo permita.
-				</div></dd><dt><span class="term"><span class="emphasis"><em>nivel</em></span></span></dt><dd><div class="para">
+				</div></dd><dt><span class="term"><span class="emphasis"><em>type</em></span></span></dt><dd><div class="para">
+					The type is an attribute of Type Enforcement. The type defines a domain for processes, and a type for files. SELinux policy rules define how types can access each other, whether it be a domain accessing a type, or a domain accessing another domain. Access is only allowed if a specific SELinux policy rule exists that allows it.
+				</div></dd><dt><span class="term"><span class="emphasis"><em>level</em></span></span></dt><dd><div class="para">
 					El nivel es un atributo de MLS y la Seguridad Multi Categoría (MCS). Un rango MLS es un par de niveles, escrito como <span class="emphasis"><em>bajonivel-altonivel</em></span> si los niveles sin distintos, o <span class="emphasis"><em>bajonivel</em></span> si los niveles son idénticos (<code class="computeroutput">s0-s0</code> es lo mismo que <code class="computeroutput">s0</code>). Cada nivel es un par sensible a categorías, donde las categorías son opcionales. Si no hay categorías, el nivel se escribe como <span class="emphasis"><em>sensibilidad:conjunto-de-categoría</em></span>. Si no hay categorías, se escribe como <span class="emphasis"><em>sensibilidad</em></span>.
 				</div><div class="para">
 					If the category set is a contiguous series, it can be abbreviated. For example, <code class="computeroutput">c0.c3</code> is the same as <code class="computeroutput">c0,c1,c2,c3</code>. The <code class="filename">/etc/selinux/targeted/setrans.conf</code> file maps levels (<code class="computeroutput">s0:c0</code>) to human-readable form (ie. <code class="computeroutput">CompanyConfidential</code>). Do not edit <code class="filename">setrans.conf</code> with a text editor: use <code class="command">semanage</code> to make changes. Refer to the <span class="citerefentry"><span class="refentrytitle">semanage</span>(8)</span> manual page for further information. In Fedora, targeted policy enforces MCS, and in MCS, there is just one sensitivity, <code class="computeroutput">s0</code>. MCS in Fedora supports 1024 different categories: <code class="computeroutput">c0</code> through to <code class="computeroutput">c1023</code>. <code class="computeroutput">s0-s0:c0.c1023</code>
  is sensitivity <code class="computeroutput">s0</code> and authorized for all categories.
 				</div><div class="para">
-					MLS enforces the <a href="http://en.wikipedia.org/wiki/Bell-LaPadula_model">Bell-La Padula Mandatory Access Model</a>, and is used in Labeled Security Protection Profile (LSPP) environments. To use MLS restrictions, install the <span class="package">selinux-policy-mls</span> package, and configure MLS to be the default SELinux policy via the <code class="filename">/etc/selinux/config</code> file. The MLS policy shipped with Fedora omits many program domains that were not part of the evaluated configuration, and therefore, MLS on a desktop workstation is unusable (no support for the X Window System); however, an MLS policy from the <a href="http://oss.tresys.com/projects/refpolicy">upstream SELinux Reference Policy</a> can be built that includes all program domains.
+					MLS enforces the <a href="http://en.wikipedia.org/wiki/Bell-LaPadula_model">Bell-La Padula Mandatory Access Model</a>, and is used in Labeled Security Protection Profile (LSPP) environments. To use MLS restrictions, install the <span class="package">selinux-policy-mls</span> package, and configure MLS to be the default SELinux policy. The MLS policy shipped with Fedora omits many program domains that were not part of the evaluated configuration, and therefore, MLS on a desktop workstation is unusable (no support for the X Window System); however, an MLS policy from the <a href="http://oss.tresys.com/projects/refpolicy">upstream SELinux Reference Policy</a> can be built that includes all program domains.
 				</div></dd></dl></div><div class="section" title="3.1. Transiciones de Dominios" id="sect-Security-Enhanced_Linux-SELinux_Contexts-Domain_Transitions"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">3.1. Transiciones de Dominios</h2></div></div></div><div class="para">
 			Un proceso transiciona de un dominio a otro ejecutando una aplicación que tiene el tipo <code class="computeroutput">entrypoint</code> en el nuevo dominio. Los permisos <code class="computeroutput">entrypoint</code> se usan en las políticas de SELinux, y controlan qué aplicaciones pueden usarse para ingresar a un dominio. El siguiente ejemplo muestra una transición de dominio.
 		</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
-					Un usuario desea cambiar su contraseña. Para cambiar sus contraseñas, corren la aplicación <code class="command">passwd</code>. El ejecutable <code class="filename">/usr/bin/passwd</code> está etiquetado con el tipo <code class="computeroutput">passwd_exec_t</code>:
+					A user wants to change their password. To do this, they run the <code class="command">passwd</code> application. The <code class="filename">/usr/bin/passwd</code> executable is labeled with the <code class="computeroutput">passwd_exec_t</code> type:
 				</div><pre class="screen">$ ls -Z /usr/bin/passwd
 -rwsr-xr-x  root root system_u:object_r:passwd_exec_t:s0 /usr/bin/passwd
 
 </pre><div class="para">
 					La aplicación <span class="application"><strong>passwd</strong></span> accede <code class="filename">/etc/shadow</code>, que está etiquetado con el tipo <code class="computeroutput">shadow_t</code>:
 				</div><pre class="screen">$ ls -Z /etc/shadow
-----------. root root system_u:object_r:shadow_t:s0    /etc/shadow
+-r--------. root root system_u:object_r:shadow_t:s0    /etc/shadow
 
 </pre></li><li class="listitem"><div class="para">
 					Una regla de política de SELinux dice que los procesos que se ejecutan en el dominio <code class="computeroutput">passwd_t</code> no pueden leer y escribir archivos etiquetados con el tipo <code class="computeroutput">shadow_t</code>. El tipo <code class="computeroutput">shadow_t</code> sólo se aplica a archivos que necesitan un cambio de contraseñas. Esto incluye a <code class="filename">/etc/gshadow</code>, <code class="filename">/etc/shadow</code>, y sus archivos de respaldo.
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Targeted_Policy.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Targeted_Policy.html
index e31d458..e9729bc 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Targeted_Policy.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Targeted_Policy.html
@@ -1,13 +1,13 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Capítulo 4. Política Destinado</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="prev" href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Users.html" title="3.3. Contextos de SELinux para los Usuarios" /><link rel="next" href="sect-Security-Enhanced_Linux-Targeted_Policy-Unconfined_Processes.html" title="4.2. Procesos no Confinados" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class=
 "toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Users.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Targeted_Policy-Unconfined_Processes.html"><strong>Siguiente</strong></a></li></ul><div xml:lang="es-ES" class="chapter" title="Capítulo 4. Política Destinado" id="chap-Security-Enhanced_Linux-Targeted_Policy" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 4. Política Destinado</h2></div></div></div><div class="
 toc"><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-Targeted_Policy.html#sect-Security-Enhanced_Linux-Targeted_Policy-Confined_Processes">4.1. Procesos Confinados</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Targeted_Policy-Unconfined_Processes.html">4.2. Procesos no Confinados</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users.html">4.3. Usuarios Confinados y no Confinados</a></span></dt></dl></div><div class="para">
-		La política destinada es la política predeterminada de SELinux usada en Fedora. Cuando la política destinada está en uso, los procesos son destinados a correr en dominios confinados, y los procesos que no son destinados a correr en un dominio corren en un dominio no confinado. Por ejemplo, por defecto, los usuarios que ingresaron corren en el dominio <code class="computeroutput">unconfined_t</code>, y los procesos del sistema iniciado por init corren en el dominio <code class="computeroutput">initrc_t</code> - ambos dominios están no confinados.
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Capítulo 4. Política Destinado</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="prev" href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Users.html" title="3.3. Contextos de SELinux para los Usuarios" /><link rel="next" href="sect-Security-Enhanced_Linux-Targeted_Policy-Unconfined_Processes.html" title="4.2. Procesos no Confinados" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" 
 class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Users.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Targeted_Policy-Unconfined_Processes.html"><strong>Siguiente</strong></a></li></ul><div xml:lang="es-ES" class="chapter" title="Capítulo 4. Política Destinado" id="chap-Security-Enhanced_Linux-Targeted_Policy" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 4. Política Destinado</h2></div></div></div><div c
 lass="toc"><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-Targeted_Policy.html#sect-Security-Enhanced_Linux-Targeted_Policy-Confined_Processes">4.1. Procesos Confinados</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Targeted_Policy-Unconfined_Processes.html">4.2. Procesos no Confinados</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users.html">4.3. Usuarios Confinados y no Confinados</a></span></dt></dl></div><div class="para">
+		Targeted policy is the default SELinux policy used in Fedora. When using targeted policy, processes that are targeted run in a confined domain, and processes that are not targeted run in an unconfined domain. For example, by default, logged in users run in the <code class="computeroutput">unconfined_t</code> domain, and system processes started by init run in the <code class="computeroutput">initrc_t</code> domain - both of these domains are unconfined.
 	</div><div class="para">
-		Los dominios no confinados (así como los dominios confinados) son sujetos a chequeos de memoria escribible y ejecutable. Por defecto, los que se ejecutan en un dominio no confinado no pueden asignar memoria escribible y ejecutarla. Esto reduce la vulnerabilidad de <a href="http://en.wikipedia.org/wiki/Buffer_overflow">ataque de sobreflujo de buffer</a>. Estos chequeos de memoria se deshabilitan poniendo Booleanos, que permiten modificar la política de SELinux en tiempo de ejecución. La configuración de Booleano se discute más adelante.
+		Unconfined domains (as well as confined domains) are subject to executable and writeable memory checks. By default, subjects running in an unconfined domain can not allocate writeable memory and execute it. This reduces vulnerability to <a href="http://en.wikipedia.org/wiki/Buffer_overflow">buffer overflow attacks</a>. These memory checks are disabled by setting Booleans, which allow the SELinux policy to be modified at runtime. Boolean configuration is discussed later.
 	</div><div class="section" title="4.1. Procesos Confinados" id="sect-Security-Enhanced_Linux-Targeted_Policy-Confined_Processes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.1. Procesos Confinados</h2></div></div></div><div class="para">
 			Almost every service that listens on a network is confined in Fedora. Also, most processes that run as the Linux root user and perform tasks for users, such as the <span class="application"><strong>passwd</strong></span> application, are confined. When a process is confined, it runs in its own domain, such as the <code class="systemitem">httpd</code> process running in the <code class="computeroutput">httpd_t</code> domain. If a confined process is compromised by an attacker, depending on SELinux policy configuration, an attacker's access to resources and the possible damage they can do is limited.
 		</div><div class="para">
-			El siguiente ejemplo muestra cómo previene SELinux la lectura por parte del Servidor HTTP Apache (<code class="systemitem">httpd</code>) de archivos que no se etiquetaron correctamente, tales como archivos a usar con Samba. Este es un ejemplo, y no se debe usar en producción. Asume que los paquetes <span class="package">httpd</span>, <span class="package">wget</span>, <span class="package">setroubleshoot-server</span>, <span class="package">dbus</span> y <span class="package">audit</span> están instalados, que se usa la política destinada de SELinux y que SELinux está corriendo en modo obediente:
+			The following example demonstrates how SELinux prevents the Apache HTTP Server (<code class="systemitem">httpd</code>) from reading files that are not correctly labeled, such as files intended for use by Samba. This is an example, and should not be used in production. It assumes that the <span class="package">httpd</span>, <span class="package">wget</span>, <span class="package">setroubleshoot-server</span>, <span class="package">dbus</span> and <span class="package">audit</span> packages are installed, that the SELinux targeted policy is used, and that SELinux is running in enforcing mode:
 		</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
 					Ejecute el comando <code class="command">sestatus</code> para confirmar que SELinux está activado, se ejecuta en modo obligatorio y que la política destinada se está usando:
 				</div><pre class="screen">
@@ -20,7 +20,7 @@ Policy version:                 24
 Policy from config file:        targeted
 
 </pre><div class="para">
-					<code class="computeroutput">Estado de SELinux: activado</code> se devuelve cuando SELinux está activado. <code class="computeroutput">Modo actual: obediente</code> se devuelve cuando SELinux está ejecutándose en modo obediente. <code class="computeroutput">Política desde el archivo de configuración: destinada</code> se devuelve cuando se usa la política destinada de SELinux.
+					<code class="computeroutput">SELinux status: enabled</code> is returned when SELinux is enabled. <code class="computeroutput">Current mode: enforcing</code> is returned when SELinux is running in enforcing mode. <code class="computeroutput">Policy from config file: targeted</code> is returned when the SELinux targeted policy is used.
 				</div></li><li class="listitem"><div class="para">
 					Como usuario root de Linux, ejecute el comando <code class="command">touch /var/www/html/prueba</code> para crear un archivo.
 				</div></li><li class="listitem"><div class="para">
@@ -28,7 +28,7 @@ Policy from config file:        targeted
 				</div><pre class="screen">-rw-r--r--  root root unconfined_u:object_r:httpd_sys_content_t:s0 /var/www/html/testfile
 
 </pre><div class="para">
-					Por defecto, los usuarios Linux corren no confinados en Fedora, razón por la cual el archivo <code class="filename">prueba</code> se etiqueta con el usuario SELinux <code class="computeroutput">unconfined_u</code>. RBAC se usa para procesos, y no para archivos. Los roles no tienen significado para archivos - el rol <code class="computeroutput">object_r</code> es un rol genérico usado para archivos (en sistemas de archivos persistentes y de red). Bajo el directorio <code class="filename">/proc/</code>, los archivos relacionados con procesos pueden usar el rol <code class="computeroutput">system_r</code>.<sup>[<a id="id2068576" href="#ftn.id2068576" class="footnote">6</a>]</sup> El tipo <code class="computeroutput">httpd_sys_content_t</code> permite al proceso <code class="systemitem">httpd</code> acceder a este archivo.
+					By default, Linux users run unconfined in Fedora, which is why the <code class="filename">testfile</code> file is labeled with the SELinux <code class="computeroutput">unconfined_u</code> user. RBAC is used for processes, not files. Roles do not have a meaning for files - the <code class="computeroutput">object_r</code> role is a generic role used for files (on persistent storage and network file systems). Under the <code class="filename">/proc/</code> directory, files related to processes may use the <code class="computeroutput">system_r</code> role.<sup>[<a id="id730805" href="#ftn.id730805" class="footnote">6</a>]</sup> The <code class="computeroutput">httpd_sys_content_t</code> type allows the <code class="systemitem">httpd</code> process to access this file.
 				</div></li><li class="listitem"><div class="para">
 					Como usuario root de Linux, ejecute el comando <code class="command">service httpd start</code> para iniciar el proceso <code class="systemitem">httpd</code>. La salida escomo sigue si <code class="systemitem">httpd</code> inicia con éxito:
 				</div><pre class="screen"># /sbin/service httpd start
@@ -36,38 +36,32 @@ Starting httpd:                                            [  OK  ]
 
 </pre></li><li class="listitem"><div class="para">
 					Cambie al directorio donde su usuario Linux tenga acceso de escritura y ejecute el comando <code class="command">wget http://localhost/prueba</code>. A menos que hubieran cambios en la configuración predeterminada, este comando tiene éxito:
-				</div><pre class="screen">
-$ wget http://localhost/testfile
-
---2010-05-11 13:19:07--  http://localhost/testfile
-Resolving localhost... ::1, 127.0.0.1
-Connecting to localhost|::1|:80... connected.
+				</div><pre class="screen">--2009-11-06 17:43:01--  http://localhost/testfile
+Resolving localhost... 127.0.0.1
+Connecting to localhost|127.0.0.1|:80... connected.
 HTTP request sent, awaiting response... 200 OK
 Length: 0 [text/plain]
-Saving to: “testfile”
-
-    [ &lt;=&gt;            ] 0           --.-K/s   in 0s      
+Saving to: `testfile'
 
-2010-05-11 13:19:07 (0.00 B/s) - “testfile” saved [0/0]
+[ &lt;=&gt;                              ] 0     --.-K/s   in 0s
+		
+2009-11-06 17:43:01 (0.00 B/s) - `testfile' saved [0/0]
 
 </pre></li><li class="listitem"><div class="para">
 					El comando <code class="command">chcon</code> reetiqueta archivos; sin embargo, tales cambios de etiquetas no sobreviven cuando el sistema se reetiqueta. Para que los cambios sobrevivan un reetiquetado del sistema, use el comando <code class="command">semanage</code>, que se discute más adelante. Como usuario root de Linux, corra el siguiente comando para cambiar el tipo a un tipo usado por Samba:
 				</div><div class="para">
-					<code class="command">chcon -t samba_share_t /var/www/html/prueba</code>
+					<code class="command">chcon -t samba_share_t /var/www/html/testfile</code>
 				</div><div class="para">
 					Ejecute el comando <code class="command">ls -Z /var/www/html/prueba</code> para ver los cambios:
 				</div><pre class="screen">-rw-r--r--  root root unconfined_u:object_r:samba_share_t:s0 /var/www/html/testfile
 
 </pre></li><li class="listitem"><div class="para">
 					Nota: los permisos de DAC actuales permiten al proceso <code class="systemitem">httpd</code> acceder al <code class="filename">prueba</code>. Cambie al directorio donde el usuario Linux tenga permiso de escritura y ejecute el comando <code class="command">wget http://localhost/prueba</code>. A menos que hayan cambios en la configuración predeterminada, este comando fallará:
-				</div><pre class="screen">
-$ wget http://localhost/testfile
-
---2010-05-11 13:23:49--  http://localhost/testfile
-Resolving localhost... ::1, 127.0.0.1
-Connecting to localhost|::1|:80... connected.
+				</div><pre class="screen">--2009-11-06 14:11:23--  http://localhost/testfile
+Resolving localhost... 127.0.0.1
+Connecting to localhost|127.0.0.1|:80... connected.
 HTTP request sent, awaiting response... 403 Forbidden
-2010-05-11 13:23:49 ERROR 403: Forbidden.
+2009-11-06 14:11:23 ERROR 403: Forbidden.
 
 </pre></li><li class="listitem"><div class="para">
 					Como usuario root de Linux, corra el comando <code class="command">rm -i /var/www/html/prueba</code> para borrar <code class="filename">prueba</code>.
@@ -78,8 +72,9 @@ Stopping httpd:                                            [  OK  ]
 
 </pre></li></ol></div><div class="para">
 			Este ejemplo muestra la seguridad adicional agregada por SELinux. Aunque las reglas de DAC permitieron al proceso <code class="systemitem">httpd</code> acceder a <code class="filename">prueba</code> en el paso 7, dado que estaba etiquetado con un tipo al que el proceso <code class="systemitem">httpd</code> no tenía acceso, SELinux negó el acceso. Después del paso 7, un error similar al siguiente se guarda en <code class="filename">/var/log/messages</code>:
-		</div><pre class="screen">
-May 11 13:23:51 localhost setroubleshoot: SELinux is preventing /usr/sbin/httpd "getattr" access to /var/www/html/testfile. For complete SELinux messages. run sealert -l ca2ab0df-fcb9-46d1-8283-037450d1efcc
+		</div><pre class="screen">May 6 23:00:54 localhost setroubleshoot: SELinux is preventing httpd (httpd_t) "getattr"
+to /var/www/html/testfile (samba_share_t). For complete SELinux messages.
+run sealert -l c05911d3-e680-4e42-8e36-fe2ab9f8e654
 
 </pre><div class="para">
 			Archivos log previos pueden usar el formato <code class="filename">/var/log/messages.<em class="replaceable"><code>YYYYMMDD</code></em></code>. Cuando se ejecuta <span class="application"><strong>syslog-ng</strong></span>, los archivos log previos pueden usar el formato <code class="filename">/var/log/messages.<em class="replaceable"><code>X</code></em></code>. Si los procesos <code class="systemitem">setroubleshootd</code> y <code class="systemitem">auditd</code> están ejecutándose, errores similares a los siguientes se registran en <code class="filename">/var/log/audit/audit.log</code>:
@@ -89,8 +84,8 @@ type=SYSCALL msg=audit(1220706212.937:70): arch=40000003 syscall=196 success=no
 
 </pre><div class="para">
 			También, un error similar al siguiente se registra en <code class="filename">/var/log/httpd/error_log</code>:
-		</div><pre class="screen">[Tue May 11 13:23:49 2010] [error] [client <em class="replaceable"><code>::1</code></em>] (13)Permission denied: access to /testfile denied
+		</div><pre class="screen">[Wed May 06 23:00:54 2009] [error] [client <em class="replaceable"><code>127.0.0.1</code></em>] (13)Permission denied: access to /testfile denied
 
-</pre></div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id2068576" href="#id2068576" class="para">6</a>] </sup>
-						cuando se usan otras políticas, tal como MLS, se pueden usar otros roles, por ejemplo <code class="computeroutput">secadm_r</code>.
+</pre></div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id730805" href="#id730805" class="para">6</a>] </sup>
+						When using other policies, such as MLS, other roles may be used, for example, <code class="computeroutput">secadm_r</code>.
 					</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Users.html"><strong>Anterior</strong>3.3. Contextos de SELinux para los Usuarios</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Targeted_Policy-Unconfined_Processes.html"><strong>Siguiente</strong>4.2. Procesos no Confinados</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Trademark_Information.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Trademark_Information.html
index 8ff84fe..0cf5c6d 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Trademark_Information.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Trademark_Information.html
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Capítulo 1. Información de Marca Comercial</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="prev" href="pr01s02.html" title="2. ¡Necesitamos sus comentarios!" /><link rel="next" href="chap-Security-Enhanced_Linux-Introduction.html" title="Capítulo 2. Introducción" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or e
 nable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="pr01s02.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-Introduction.html"><strong>Siguiente</strong></a></li></ul><div xml:lang="es-ES" class="chapter" title="Capítulo 1. Información de Marca Comercial" id="chap-Security-Enhanced_Linux-Trademark_Information" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 1. Información de Marca Comercial</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-Trademark_Information.html#chap-Security-Enhanced_Linux-Trademark_Informat
 ion-Source_Code">1.1. Código Fuente</a></span></dt></dl></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Capítulo 1. Información de Marca Comercial</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="prev" href="pr01s02.html" title="2. ¡Necesitamos sus comentarios!" /><link rel="next" href="chap-Security-Enhanced_Linux-Introduction.html" title="Capítulo 2. Introducción" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browse
 r or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="pr01s02.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-Introduction.html"><strong>Siguiente</strong></a></li></ul><div xml:lang="es-ES" class="chapter" title="Capítulo 1. Información de Marca Comercial" id="chap-Security-Enhanced_Linux-Trademark_Information" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 1. Información de Marca Comercial</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-Trademark_Information.html#chap-Security-Enhanced_Linux-Trademark_In
 formation-Source_Code">1.1. Source Code</a></span></dt></dl></div><div class="para">
 		<span class="trademark">Linux</span>® es una marca comercial registrada de Linus Torvalds en los EEUU y en otros países.
 	</div><div class="para">
 		UNIX es una marca comercial registrada de El Grupo Abierto.
@@ -11,7 +11,7 @@
 	</div><div class="para">
 		MySQL es una marca comercial o marca comercial registrada de MySQL AB en los EEUU y en otros países.
 	</div><div class="para">
-		Otros productos mencionados pueden ser marcas comerciales de sus respectivas corporaciones.
-	</div><div class="section" title="1.1. Código Fuente" id="chap-Security-Enhanced_Linux-Trademark_Information-Source_Code"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">1.1. Código Fuente</h2></div></div></div><div class="para">
-			El código fuente XML de está guía está disponible en <a href="http://svn.fedorahosted.org/svn/selinuxguide/">http://svn.fedorahosted.org/svn/selinuxguide/</a>
+		Other products mentioned may be trademarks of their respective corporations.
+	</div><div class="section" title="1.1. Source Code" id="chap-Security-Enhanced_Linux-Trademark_Information-Source_Code"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">1.1. Source Code</h2></div></div></div><div class="para">
+			The XML source for this guide is available at <a href="http://svn.fedorahosted.org/svn/selinuxguide/">http://svn.fedorahosted.org/svn/selinuxguide/</a>
 		</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="pr01s02.html"><strong>Anterior</strong>2. ¡Necesitamos sus comentarios!</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-Introduction.html"><strong>Siguiente</strong>Capítulo 2. Introducción</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Troubleshooting.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Troubleshooting.html
index 4be02ff..9647c25 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Troubleshooting.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Troubleshooting.html
@@ -1,11 +1,11 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Capítulo 7. Solución a Problemas</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="prev" href="sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications.html" title="6.6. Booleanos para que los Usuarios Ejecuten Aplicaciones" /><link rel="next" href="sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html" title="7.2. Tres Principales Causas de Problemas" /></head><body class="toc_embeded "><div
  id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html"><strong>Siguiente</strong></a></li></ul><div xml:lang="es-ES" class="chapter" title="Capítulo 7. Solución a Problemas" id="chap-Security-Enhanced_Linux-Troubleshooting" lang="es-ES"><div class="titlepage"><div><div><h2 clas
 s="title">Capítulo 7. Solución a Problemas</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-Troubleshooting.html#sect-Security-Enhanced_Linux-Troubleshooting-What_Happens_when_Access_is_Denied">7.1. Qué pasa cuando el Acceso es Denegado</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html">7.2. Tres Principales Causas de Problemas</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html#sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Labeling_Problems">7.2.1. Problemas de Etiquetados</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running.html">7.2.2. ¿Cómo se Ejecutan los Servicios Confinados?</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced
 _Linux-Top_Three_Causes_of_Problems-Evolving_Rules_and_Broken_Applications.html">7.2.3. Evolucionando las Reglas y las Aplicaciones Rotas</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html">7.3. Corrección de Problemas</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html#sect-Security-Enhanced_Linux-Fixing_Problems-Linux_Permissions">7.3.1. Permisos de Linux</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-Possible_Causes_of_Silent_Denials.html">7.3.2. Posibles Causas de las Negaciones Silenciosas</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services.html">7.3.3. Páginas de Manual para Servicios</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains.html">7.3.4
 . Dominios Permisivos</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-Searching_For_and_Viewing_Denials.html">7.3.5. Búsqueda y Revisión de Negaciones</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages.html">7.3.6. Mensajes Crudos de Auditoría</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages.html">7.3.7. Mensajes sealert</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow.html">7.3.8. Permitiendo el Acceso: audit2allow</a></span></dt></dl></dd></dl></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Capítulo 7. Solución a Problemas</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="prev" href="sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications.html" title="6.6. Booleanos para que los Usuarios Ejecuten Aplicaciones" /><link rel="next" href="sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html" title="7.2. Tres Principales Causas de Problemas" /></head><body class="draft toc_embeded 
 "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html"><strong>Siguiente</strong></a></li></ul><div xml:lang="es-ES" class="chapter" title="Capítulo 7. Solución a Problemas" id="chap-Security-Enhanced_Linux-Troubleshooting" lang="es-ES"><div class="titlepage"><div><div><h
 2 class="title">Capítulo 7. Solución a Problemas</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-Troubleshooting.html#sect-Security-Enhanced_Linux-Troubleshooting-What_Happens_when_Access_is_Denied">7.1. Qué pasa cuando el Acceso es Denegado</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html">7.2. Tres Principales Causas de Problemas</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html#sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Labeling_Problems">7.2.1. Problemas de Etiquetados</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running.html">7.2.2. ¿Cómo se Ejecutan los Servicios Confinados?</a></span></dt><dt><span class="section"><a href="sect-Security-En
 hanced_Linux-Top_Three_Causes_of_Problems-Evolving_Rules_and_Broken_Applications.html">7.2.3. Evolucionando las Reglas y las Aplicaciones Rotas</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html">7.3. Corrección de Problemas</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html#sect-Security-Enhanced_Linux-Fixing_Problems-Linux_Permissions">7.3.1. Permisos de Linux</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-Possible_Causes_of_Silent_Denials.html">7.3.2. Posibles Causas de las Negaciones Silenciosas</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services.html">7.3.3. Páginas de Manual para Servicios</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains.html"
 >7.3.4. Dominios Permisivos</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-Searching_For_and_Viewing_Denials.html">7.3.5. Búsqueda y Revisión de Negaciones</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages.html">7.3.6. Raw Audit Messages</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages.html">7.3.7. Mensajes sealert</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow.html">7.3.8. Permitiendo el Acceso: audit2allow</a></span></dt></dl></dd></dl></div><div class="para">
 		El siguiente capítulo describe qué pasa cuando SELinux niega el acceso; las principales tres causas de problemas; dónde encontrar información acerca del correcto etiquetado; análisis de las negaciones de SELinux; y creación de módulos de políticas personalizados con <code class="command">audit2allow</code>.
 	</div><div class="section" title="7.1. Qué pasa cuando el Acceso es Denegado" id="sect-Security-Enhanced_Linux-Troubleshooting-What_Happens_when_Access_is_Denied"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">7.1. Qué pasa cuando el Acceso es Denegado</h2></div></div></div><div class="para">
 			SELinux decisions, such as allowing or disallowing access, are cached. This cache is known as the Access Vector Cache (AVC). Denial messages are logged when SELinux denies access. These denials are also known as "AVC denials", and are logged to a different location, depending on which daemons are running:
-		</div><div class="segmentedlist"><table border="0"><thead><tr class="segtitle"><th>Demonio</th><th>Ubicación del Log</th></tr></thead><tbody><tr class="seglistitem"><td class="seg">auditd activado</td><td class="seg"><code class="filename">/var/log/audit/audit.log</code></td></tr><tr class="seglistitem"><td class="seg">auditd desactivado; rsyslogd activado</td><td class="seg"><code class="filename">/var/log/messages</code></td></tr><tr class="seglistitem"><td class="seg">setroubleshootd, rsyslogd y auditd activados</td><td class="seg"><code class="filename">/var/log/audit/audit.log</code>. Mensages de negaciones legibles que también se envían a <code class="filename">/var/log/messages</code></td></tr></tbody></table></div><div class="para">
-			Si está corriendo el Sistema de Ventanas X, ya tienen los paquetes <span class="package">setroubleshoot</span> y <span class="package">setroubleshoot-server</span> instalados, y los demonios <code class="systemitem">setroubleshootd</code> y <code class="systemitem">auditd</code> están ejecutándose, se muestra una estrella amarilla y una advertencia cuando SELinux deniega el acceso:
+		</div><div class="segmentedlist"><table border="0"><thead><tr class="segtitle"><th>Daemon</th><th>Log Location</th></tr></thead><tbody><tr class="seglistitem"><td class="seg">auditd on</td><td class="seg"><code class="filename">/var/log/audit/audit.log</code></td></tr><tr class="seglistitem"><td class="seg">auditd off; rsyslogd on</td><td class="seg"><code class="filename">/var/log/messages</code></td></tr><tr class="seglistitem"><td class="seg">setroubleshootd, rsyslogd, and auditd on</td><td class="seg"><code class="filename">/var/log/audit/audit.log</code>. Easier-to-read denial messages also sent to <code class="filename">/var/log/messages</code></td></tr></tbody></table></div><div class="para">
+			If you are running the X Window System, have the <span class="package">setroubleshoot</span> and <span class="package">setroubleshoot-server</span> packages installed, and the <code class="systemitem">setroubleshootd</code> and <code class="systemitem">auditd</code> daemons are running, a warning is displayed when access is denied by SELinux:
 		</div><div class="mediaobject"><img src="./images/denial.png" width="444" /></div><div class="para">
 			Clicking on 'Show' presents a detailed analysis of why SELinux denied access, and a possible solution for allowing access. If you are not running the X Window System, it is less obvious when access is denied by SELinux. For example, users browsing your website may receive an error similar to the following:
 		</div><pre class="screen">
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Working_with_SELinux.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Working_with_SELinux.html
index bc4eb6d..850bac4 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Working_with_SELinux.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/chap-Security-Enhanced_Linux-Working_with_SELinux.html
@@ -1,13 +1,11 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Capítulo 5. Trabajando con SELinux</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="prev" href="sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users.html" title="4.3. Usuarios Confinados y no Confinados" /><link rel="next" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used.html" title="5.2. Qué Archivo Log se usa" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocfra
 me" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used.html"><strong>Siguiente</strong></a></li></ul><div xml:lang="es-ES" class="chapter" title="Capítulo 5. Trabajando con SELinux" id="chap-Security-Enhanced_Linux-Working_with_SELinux" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 5. Trabajando con SELinux</h2>
 </div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-Working_with_SELinux.html#sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Packages">5.1. Paquetes de SELinux</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used.html">5.2. Qué Archivo Log se usa</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Main_Configuration_File.html">5.3. Archivo de Configuración Principal</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html">5.4. Habilitando y Deshabilitando SELinux</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html#sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Enabling_SELinux">5.4.1. Habilitando SELinux</a></span>
 </dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux.html">5.4.2. Deshabilitando SELinux</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes.html">5.5. Modos de SELinux</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html">5.6. Booleanos</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html#sect-Security-Enhanced_Linux-Booleans-Listing_Booleans">5.6.1. Listando los Booleanos</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Booleans-Configuring_Booleans.html">5.6.2. Configurando los Booleanos</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS.html">5.6.3. Booleanos para NFS y CIFS</a></span></dt></dl></dd><dt><span class="s
 ection"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files.html">5.7. Contextos de SELinux - Etiquetado de Archivos</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files.html#sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Temporary_Changes_chcon">5.7.1. Cambios Temporales: chcon</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext.html">5.7.2. Cambios Persistentes: semanage fcontext</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types.html">5.8. Los tipos file_t y default_t</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html">5.9. Montaje de Sistemas de Archivos</a></span></dt><dd><dl
 ><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html#sect-Security-Enhanced_Linux-Mounting_File_Systems-Context_Mounts">5.9.1. Montajes de Contexto</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Changing_the_Default_Context.html">5.9.2. Cambio del Contexto Predeterminado</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Mounting_an_NFS_File_System.html">5.9.3. Montando un Sistema de Archivos NFS</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Multiple_NFS_Mounts.html">5.9.4. Montajes NFS Múltiples</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Making_Context_Mounts_Persistent.html">5.9.5. Haciendo Persistente los Contextos de Montajes</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Security
 -Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html">5.10. Mantención de las Etiquetas de SELinux</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html#sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Copying_Files_and_Directories">5.10.1. Copia de Directorios y Archivos</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Moving_Files_and_Directories.html">5.10.2. Movimiento de Archivos y Directorios</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context.html">5.10.3. Chequeando el Contexto SELinux Predeterminado</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_tar.html">5.10.4. Archivando archivos con tar</a></span></dt><dt><span class="sectio
 n"><a href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_star.html">5.10.5. Archivando archivos con tar</a></span></dt></dl></dd></dl></div><div class="para">
-		Las siguientes secciones dan un breve repaso de los paquetes de SELinux principales en Fedora; instalación y actualización de paquetes; qué archivos de registro se usan; el archivo de configuración principal de SELinux; habilitación y deshabilitación de SELinux; modos de SELinux; configuración de Booleanos; cambios temporales y permanentes de etiquetas de archivos y directorios; superposición de las etiquetas de sistemas de archivos con el comando <code class="command">mount</code>; montaje de sistemas de archivos NFS; y cómo preservar contextos de SELinux cuando se copia y compacta archivos y directorios.
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Capítulo 5. Trabajando con SELinux</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="prev" href="sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users.html" title="4.3. Usuarios Confinados y no Confinados" /><link rel="next" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used.html" title="5.2. Qué Archivo Log se usa" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="
 tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used.html"><strong>Siguiente</strong></a></li></ul><div xml:lang="es-ES" class="chapter" title="Capítulo 5. Trabajando con SELinux" id="chap-Security-Enhanced_Linux-Working_with_SELinux" lang="es-ES"><div class="titlepage"><div><div><h2 class="title">Capítulo 5. Trabajando con SELinu
 x</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-Working_with_SELinux.html#sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Packages">5.1. Paquetes de SELinux</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used.html">5.2. Qué Archivo Log se usa</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Main_Configuration_File.html">5.3. Archivo de Configuración Principal</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html">5.4. Habilitando y Deshabilitando SELinux</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html#sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Enabling_SELinux">5.4.1. Habilitando SELinux</a><
 /span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux.html">5.4.2. Deshabilitando SELinux</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes.html">5.5. Modos de SELinux</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html">5.6. Booleanos</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html#sect-Security-Enhanced_Linux-Booleans-Listing_Booleans">5.6.1. Listando los Booleanos</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Booleans-Configuring_Booleans.html">5.6.2. Configurando los Booleanos</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS.html">5.6.3. Booleanos para NFS y CIFS</a></span></dt></dl></dd><dt><span cl
 ass="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files.html">5.7. Contextos de SELinux - Etiquetado de Archivos</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files.html#sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Temporary_Changes_chcon">5.7.1. Cambios Temporales: chcon</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext.html">5.7.2. Cambios Persistentes: semanage fcontext</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types.html">5.8. Los tipos file_t y default_t</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html">5.9. Montaje de Sistemas de Archivos</a></span></dt><
 dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html#sect-Security-Enhanced_Linux-Mounting_File_Systems-Context_Mounts">5.9.1. Montajes de Contexto</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Changing_the_Default_Context.html">5.9.2. Cambio del Contexto Predeterminado</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Mounting_an_NFS_File_System.html">5.9.3. Montando un Sistema de Archivos NFS</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Multiple_NFS_Mounts.html">5.9.4. Montajes NFS Múltiples</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Making_Context_Mounts_Persistent.html">5.9.5. Haciendo Persistente los Contextos de Montajes</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Se
 curity-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html">5.10. Mantención de las Etiquetas de SELinux</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html#sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Copying_Files_and_Directories">5.10.1. Copia de Directorios y Archivos</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Moving_Files_and_Directories.html">5.10.2. Movimiento de Archivos y Directorios</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context.html">5.10.3. Chequeando el Contexto SELinux Predeterminado</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_tar.html">5.10.4. Archivando archivos con tar</a></span></dt><dt><span class="
 section"><a href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_star.html">5.10.5. Archivando archivos con tar</a></span></dt></dl></dd></dl></div><div class="para">
+		The following sections give a brief overview of the main SELinux packages in Fedora; installing and updating packages; which log files are used; the main SELinux configuration file; enabling and disabling SELinux; SELinux modes; configuring Booleans; temporarily and persistently changing file and directory labels; overriding file system labels with the <code class="command">mount</code> command; mounting NFS file systems; and how to preserve SELinux contexts when copying and archiving files and directories.
 	</div><div class="section" title="5.1. Paquetes de SELinux" id="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Packages"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.1. Paquetes de SELinux</h2></div></div></div><div class="para">
-			In Fedora, the SELinux packages are installed by default in a full installation, unless they are manually excluded during installation. If performing a minimal installation in text mode, the <span class="package">policycoreutils-python</span> package will not be installed by default. Also, by default, SELinux targeted policy is used, and SELinux runs in enforcing mode. The following is a brief description of the main SELinux packages:
+			In Fedora, the SELinux packages are installed by default, unless they are manually excluded during installation. By default, SELinux targeted policy is used, and SELinux runs in enforcing mode. The following is a brief description of the main SELinux packages:
 		</div><div class="para">
-			<span class="package">policycoreutils-python</span>: provides utilities such as <code class="command">semanage</code>, <code class="command">audit2allow</code>, <code class="command">audit2why</code> and <code class="command">chcat</code>, for operating and managing SELinux.
-		</div><div class="para">
-			<span class="package">policycoreutils</span>: provides utilities such as <code class="command">restorecon</code>, <code class="command">secon</code>, <code class="command">setfiles</code>, <code class="command">semodule</code>, <code class="command">load_policy</code>, and <code class="command">setsebool</code>, for operating and managing SELinux.
+			<span class="package">policycoreutils</span>: provee utilitarios, tales como <code class="command">semanage</code>, <code class="command">restorecon</code>, <code class="command">audit2allow</code>, <code class="command">semodule</code>, <code class="command">load_policy</code> y <code class="command">setsebool</code>, para la operación y administración de SELinux.
 		</div><div class="para">
 			<span class="package">policycoreutils-gui</span>: provee <code class="command">system-config-selinux</code>, una herramienta gráfica para la administración de SELinux.
 		</div><div class="para">
@@ -17,19 +15,19 @@
 		</div><div class="para">
 			<span class="package">setroubleshoot-server</span>: traduce mensajes de negaciones, producidos cuando el acceso es denegado por SELinux, en descripciones detalladas que se ven con <code class="command">sealert</code> (que se provee en este paquete).
 		</div><div class="para">
-			<span class="package">setools</span>, <span class="package">setools-gui</span>, and <span class="package">setools-console</span>: these packages provide the <a href="http://oss.tresys.com/projects/setools">Tresys Technology SETools distribution</a>, a number of tools and libraries for analyzing and querying policy, audit log monitoring and reporting, and file context management<sup>[<a id="id944612" href="#ftn.id944612" class="footnote">8</a>]</sup>. The <span class="package">setools</span> package is a meta-package for SETools. The <span class="package">setools-gui</span> package provides the <code class="command">apol</code>, <code class="command">seaudit</code>, and <code class="command">sediffx</code> tools. The <span class="package">setools-console</span> package provides the <code class="command">seaudit-report</code>, <code class="command">sechecker</code>, <code class="command">sediff</code>, <code class="command">seinfo</code>, <code class="command">sesearch</cod
 e>, <code class="command">findcon</code>, <code class="command">replcon</code>, and <code class="command">indexcon</code> command line tools. Refer to the <a href="http://oss.tresys.com/projects/setools">Tresys Technology SETools</a> page for information about these tools.
+			<span class="package">setools</span>, <span class="package">setools-gui</span>, and <span class="package">setools-console</span>: these packages provide the <a href="http://oss.tresys.com/projects/setools">Tresys Technology SETools distribution</a>, a number of tools and libraries for analyzing and querying policy, audit log monitoring and reporting, and file context management<sup>[<a id="id1057926" href="#ftn.id1057926" class="footnote">8</a>]</sup>. The <span class="package">setools</span> package is a meta-package for SETools. The <span class="package">setools-gui</span> package provides the <code class="command">apol</code>, <code class="command">seaudit</code>, and <code class="command">sediffx</code> tools. The <span class="package">setools-console</span> package provides the <code class="command">seaudit-report</code>, <code class="command">sechecker</code>, <code class="command">sediff</code>, <code class="command">seinfo</code>, <code class="command">sesearch</c
 ode>, <code class="command">findcon</code>, <code class="command">replcon</code>, and <code class="command">indexcon</code> command line tools. Refer to the <a href="http://oss.tresys.com/projects/setools">Tresys Technology SETools</a> page for information about these tools.
 		</div><div class="para">
 			<span class="package">libselinux-utils</span>: provee las herramientas <code class="command">avcstat</code>, <code class="command">getenforce</code>, <code class="command">getsebool</code>, <code class="command">matchpathcon</code>, <code class="command">selinuxconlist</code>, <code class="command">selinuxdefcon</code>, <code class="command">selinuxenabled</code>, <code class="command">setenforce</code>, <code class="command">togglesebool</code>.
 		</div><div class="para">
 			<span class="package">mcstrans</span>: traduce niveles, tales como <code class="computeroutput">s0-s0:c0.c1023</code>, a una forma legible como <code class="computeroutput">SystemLow-SystemHigh</code>. Este paquete no se instala por defecto.
 		</div><div class="para">
-			Para instalar paquetes en Fedora, como usuario root de Linux ejecute el comando <code class="command">yum install <em class="replaceable"><code>nombre-de-paquete</code></em></code>. Por ejemplo, para instalar el paquete <span class="package">mcstrans</span>, ejecute el comando <code class="command">yum install mcstrans</code>. Para actualizar todos los paquetes instalados en Fedora, ejecute el comando <code class="command">yum update</code>.
+			To install packages in Fedora, as the Linux root user, run the <code class="command">yum install <em class="replaceable"><code>package-name</code></em></code> command. For example, to install the <span class="package">mcstrans</span> package, run the <code class="command">yum install mcstrans</code> command. To upgrade all installed packages in Fedora, run the <code class="command">yum update</code> command.
 		</div><div class="para">
-			Vaya a <a href="http://docs.fedoraproject.org/yum/en/">Administración de Software con yum</a><sup>[<a id="id926273" href="#ftn.id926273" class="footnote">9</a>]</sup> para más información sobre el uso de <code class="command">yum</code> para administrar paquetes.
+			Vaya a <a href="http://docs.fedoraproject.org/yum/en/">Administración de Software con yum</a><sup>[<a id="id689965" href="#ftn.id689965" class="footnote">9</a>]</sup> para más información sobre el uso de <code class="command">yum</code> para administrar paquetes.
 		</div><div class="note"><h2>Nota</h2><div class="para">
 				En versiones anteriores de Fedora, el paquete <span class="package">selinux-policy-devel</span> es necesario cuando se crea un módulo de política local con <code class="command">audit2allow -M</code>.
-			</div></div></div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id944612" href="#id944612" class="para">8</a>] </sup>
+			</div></div></div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id1057926" href="#id1057926" class="para">8</a>] </sup>
 				Brindle, Joshua. "Re: blurb for fedora setools packages" Email to Murray McAllister. 1 November 2008. Any edits or changes in this version were done by Murray McAllister.
-			</p></div><div class="footnote"><p><sup>[<a id="ftn.id926273" href="#id926273" class="para">9</a>] </sup>
+			</p></div><div class="footnote"><p><sup>[<a id="ftn.id689965" href="#id689965" class="para">9</a>] </sup>
 				Administración de Software con yum, escrito por Stuart Ellis, editado por Paul W. Frields, Rodrigo Menezes y Hugo Cisneiros.
 			</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users.html"><strong>Anterior</strong>4.3. Usuarios Confinados y no Confinados</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used.html"><strong>Siguiente</strong>5.2. Qué Archivo Log se usa</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/index.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/index.html
index 510133f..ac4786a 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/index.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/index.html
@@ -1,9 +1,9 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Linux con Seguridad Mejorada</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><meta name="description" content="La Guía del Usuario de SELinux asiste a los usuarios y administradores en la administración y uso del Linux con Seguridad Mejorada." /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="next" href="pref-Security-Enhanced_Linux-Preface.html" title="Prefacio" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.
 </iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"></li><li class="next"><a accesskey="n" href="pref-Security-Enhanced_Linux-Preface.html"><strong>Siguiente</strong></a></li></ul><div xml:lang="es-ES" class="book" title="Linux con Seguridad Mejorada" lang="es-ES"><div class="titlepage"><div><div class="producttitle" font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><span class="productname">Fedora</span> <span class="productnumber">13</span></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h1 id="id1266497" class="title">Linux con Seguridad Mejorada</h1></div><div font-family="sans-serif
 ,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h2 class="subtitle">Guía del Usuario</h2></div><p class="edition">Edición 1.5</p><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h3 class="corpauthor">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Linux con Seguridad Mejorada</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><meta name="description" content="The SELinux User Guide assists users and administrators in managing and using Security-Enhanced Linux." /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="next" href="pref-Security-Enhanced_Linux-Preface.html" title="Prefacio" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="tit
 le"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"></li><li class="next"><a accesskey="n" href="pref-Security-Enhanced_Linux-Preface.html"><strong>Siguiente</strong></a></li></ul><div xml:lang="es-ES" class="book" title="Linux con Seguridad Mejorada" lang="es-ES"><div class="titlepage"><div><div class="producttitle" font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><span class="productname">Fedora</span> <span class="productnumber">13</span></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h1 id="id788166" class="title">Linux con Seguridad Mejorada</h1></div><div font-family="sans-serif,Symbol,ZapfDingbats" font
 -weight="bold" font-size="12pt" text-align="center"><h2 class="subtitle">Guía del Usuario</h2></div><p class="edition">Edición 1.4</p><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h3 class="corpauthor">
 		<span class="inlinemediaobject"><object data="Common_Content/images/title_logo.svg" type="image/svg+xml"> Logo</object></span>
 
-	</h3></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div xml:lang="es-ES" class="authorgroup" lang="es-ES"><div class="author"><h3 class="author"><span class="firstname">Murray</span> <span class="surname">McAllister</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Ingeniería de Servicios de Contenido</span></div><code class="email"><a class="email" href="mailto:mmcallis at redhat.com">mmcallis at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Scott</span> <span class="surname">Radvan</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Ingeniería de Servicios de Contenido</span></div><code class="email"><a class="email" href="mailto:sradvan at redhat.com">sradvan at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Daniel</span> <span class="surname">Wa
 lsh</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Ingeniería de la Seguridad</span></div><code class="email"><a class="email" href="mailto:dwalsh at redhat.com">dwalsh at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Dominick</span> <span class="surname">Grift</span></h3><span class="contrib">Editor técnico para los capítulos Introducción, Contextos de SELinux, Política Destinada, Trabajando con SELinux, Confinando Usuarios y Solución de Problemas.</span> <div class="affiliation"><span class="orgname"></span> <span class="orgdiv"></span></div><code class="email"><a class="email" href="mailto:domg472 at gmail.com">domg472 at gmail.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Eric</span> <span class="surname">Paris</span></h3><span class="contrib">Editor técnico para las secciones Montaje de Sistemas de Archivos y Mensajes Crudos de Auditoría.</span> 
 <div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Ingeniería de la Seguridad</span></div><code class="email"><a class="email" href="mailto:eparis at parisplace.org">eparis at parisplace.org</a></code></div><div class="author"><h3 class="author"><span class="firstname">James</span> <span class="surname">Morris</span></h3><span class="contrib">Editor técnico para los capítulos Introducción y Política Destinada.</span> <div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Ingeniería de la Seguridad</span></div><code class="email"><a class="email" href="mailto:jmorris at redhat.com">jmorris at redhat.com</a></code></div></div></div><hr /><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div id="id2078627" class="legalnotice"><h1 class="legalnotice">Aviso Legal</h1><div class="para">
+	</h3></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div xml:lang="es-ES" class="authorgroup" lang="es-ES"><div class="author"><h3 class="author"><span class="firstname">Murray</span> <span class="surname">McAllister</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:mmcallis at redhat.com">mmcallis at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Scott</span> <span class="surname">Radvan</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:sradvan at redhat.com">sradvan at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Daniel</span> <span class="surname">Walsh</span></h3><di
 v class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Security Engineering</span></div><code class="email"><a class="email" href="mailto:dwalsh at redhat.com">dwalsh at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Dominick</span> <span class="surname">Grift</span></h3><span class="contrib">Technical editor for the Introduction, SELinux Contexts, Targeted Policy, Working with SELinux, Confining Users, and Troubleshooting chapters.</span> <div class="affiliation"><span class="orgname"></span> <span class="orgdiv"></span></div><code class="email"><a class="email" href="mailto:domg472 at gmail.com">domg472 at gmail.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Eric</span> <span class="surname">Paris</span></h3><span class="contrib">Technical editor for the Mounting File Systems and Raw Audit Messages sections.</span> <div class="affiliation"><span class="orgname">Red Hat</span> <spa
 n class="orgdiv">Security Engineering</span></div><code class="email"><a class="email" href="mailto:eparis at parisplace.org">eparis at parisplace.org</a></code></div><div class="author"><h3 class="author"><span class="firstname">James</span> <span class="surname">Morris</span></h3><span class="contrib">Technical editor for the Introduction and Targeted Policy chapters.</span> <div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Security Engineering</span></div><code class="email"><a class="email" href="mailto:jmorris at redhat.com">jmorris at redhat.com</a></code></div></div></div><hr /><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div id="id667733" class="legalnotice"><h1 class="legalnotice">Aviso Legal</h1><div class="para">
 		Copyright <span class="trademark"></span>© 2010 Red Hat, Inc.
 	</div><div class="para">
 		The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at <a href="http://creativecommons.org/licenses/by-sa/3.0/">http://creativecommons.org/licenses/by-sa/3.0/</a>. The original authors of this document, and Red Hat, designate the Fedora Project as the "Attribution Party" for purposes of CC-BY-SA. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
@@ -22,5 +22,5 @@
 	</div><div class="para">
 		All other trademarks are the property of their respective owners.
 	</div></div></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div class="abstract" title="Resumen"><h6>Resumen</h6><div class="para">
-			La Guía del Usuario de SELinux asiste a los usuarios y administradores en la administración y uso del <span class="trademark">Linux</span>® con Seguridad Mejorada.
-		</div></div></div></div><hr /></div><div class="toc"><dl><dt><span class="preface"><a href="pref-Security-Enhanced_Linux-Preface.html">Prefacio</a></span></dt><dd><dl><dt><span class="section"><a href="pref-Security-Enhanced_Linux-Preface.html#id1073417">1. Convenciones del Documento</a></span></dt><dd><dl><dt><span class="section"><a href="pref-Security-Enhanced_Linux-Preface.html#id978564">1.1. Convenciones Tipográficas</a></span></dt><dt><span class="section"><a href="pref-Security-Enhanced_Linux-Preface.html#id2046495">1.2. Convenciones del documento</a></span></dt><dt><span class="section"><a href="pref-Security-Enhanced_Linux-Preface.html#id974259">1.3. Notas y Advertencias</a></span></dt></dl></dd><dt><span class="section"><a href="pr01s02.html">2. ¡Necesitamos sus comentarios!</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Security-Enhanced_Linux-Trademark_Information.html">1. Información de Marca Comercial</a></span></dt><dd><dl><dt><span clas
 s="section"><a href="chap-Security-Enhanced_Linux-Trademark_Information.html#chap-Security-Enhanced_Linux-Trademark_Information-Source_Code">1.1. Código Fuente</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Security-Enhanced_Linux-Introduction.html">2. Introducción</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-Introduction.html#sect-Security-Enhanced_Linux-Introduction-Benefits_of_running_SELinux">2.1. Beneficios de usar SELinux</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Introduction-Examples.html">2.2. Ejemplos</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture.html">2.3. Arquitectura de SELinux</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Introduction-SELinux_on_Other_Operating_Systems.html">2.4. SELinux en otros Sistemas Operativos</a></span></dt></dl></dd><dt><span class="chapter">
 <a href="chap-Security-Enhanced_Linux-SELinux_Contexts.html">3. Contextos de SELinux</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-SELinux_Contexts.html#sect-Security-Enhanced_Linux-SELinux_Contexts-Domain_Transitions">3.1. Transiciones de Dominios</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Processes.html">3.2. Contextos de SELinux para los Procesos</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Users.html">3.3. Contextos de SELinux para los Usuarios</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Security-Enhanced_Linux-Targeted_Policy.html">4. Política Destinado</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-Targeted_Policy.html#sect-Security-Enhanced_Linux-Targeted_Policy-Confined_Processes">4.1. Procesos Confinados</a></span></dt><d
 t><span class="section"><a href="sect-Security-Enhanced_Linux-Targeted_Policy-Unconfined_Processes.html">4.2. Procesos no Confinados</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users.html">4.3. Usuarios Confinados y no Confinados</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Security-Enhanced_Linux-Working_with_SELinux.html">5. Trabajando con SELinux</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-Working_with_SELinux.html#sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Packages">5.1. Paquetes de SELinux</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used.html">5.2. Qué Archivo Log se usa</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Main_Configuration_File.html">5.3. Archivo de Configuración Principal</a></sp
 an></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html">5.4. Habilitando y Deshabilitando SELinux</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html#sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Enabling_SELinux">5.4.1. Habilitando SELinux</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux.html">5.4.2. Deshabilitando SELinux</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes.html">5.5. Modos de SELinux</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html">5.6. Booleanos</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html#
 sect-Security-Enhanced_Linux-Booleans-Listing_Booleans">5.6.1. Listando los Booleanos</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Booleans-Configuring_Booleans.html">5.6.2. Configurando los Booleanos</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS.html">5.6.3. Booleanos para NFS y CIFS</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files.html">5.7. Contextos de SELinux - Etiquetado de Archivos</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files.html#sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Temporary_Changes_chcon">5.7.1. Cambios Temporales: chcon</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage
 _fcontext.html">5.7.2. Cambios Persistentes: semanage fcontext</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types.html">5.8. Los tipos file_t y default_t</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html">5.9. Montaje de Sistemas de Archivos</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html#sect-Security-Enhanced_Linux-Mounting_File_Systems-Context_Mounts">5.9.1. Montajes de Contexto</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Changing_the_Default_Context.html">5.9.2. Cambio del Contexto Predeterminado</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Mounting_an_NFS_File_System.html">5.9.3. Montando un Sistema de Archivo
 s NFS</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Multiple_NFS_Mounts.html">5.9.4. Montajes NFS Múltiples</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Making_Context_Mounts_Persistent.html">5.9.5. Haciendo Persistente los Contextos de Montajes</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html">5.10. Mantención de las Etiquetas de SELinux</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html#sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Copying_Files_and_Directories">5.10.1. Copia de Directorios y Archivos</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Moving_Files_and_Directories.html">5.10.2. Movimiento de Archivos
  y Directorios</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context.html">5.10.3. Chequeando el Contexto SELinux Predeterminado</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_tar.html">5.10.4. Archivando archivos con tar</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_star.html">5.10.5. Archivando archivos con tar</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="chap-Security-Enhanced_Linux-Confining_Users.html">6. Confinando a los Usuarios</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-Confining_Users.html#sect-Security-Enhanced_Linux-Confining_Users-Linux_and_SELinux_User_Mappings">6.1. Linux y los Mapeos de Usuarios de SELinux</a></span></dt><dt><span class="sectio
 n"><a href="sect-Security-Enhanced_Linux-Confining_Users-Confining_New_Linux_Users_useradd.html">6.2. Confinando Usuarios Nuevos de Linux: useradd</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Confining_Users-Confining_Existing_Linux_Users_semanage_login.html">6.3. Confinando Usuarios Linux Existentes: semanage login</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Confining_Users-Changing_the_Default_Mapping.html">6.4. Cambiando el Mapeo Predeterminado</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Confining_Users-xguest_Kiosk_Mode.html">6.5. xguest: Modo Kiosk</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications.html">6.6. Booleanos para que los Usuarios Ejecuten Aplicaciones</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Security-Enhanced_Linux-Troubleshooting.html">7. Solución
  a Problemas</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-Troubleshooting.html#sect-Security-Enhanced_Linux-Troubleshooting-What_Happens_when_Access_is_Denied">7.1. Qué pasa cuando el Acceso es Denegado</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html">7.2. Tres Principales Causas de Problemas</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html#sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Labeling_Problems">7.2.1. Problemas de Etiquetados</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running.html">7.2.2. ¿Cómo se Ejecutan los Servicios Confinados?</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Evolving_Rules_a
 nd_Broken_Applications.html">7.2.3. Evolucionando las Reglas y las Aplicaciones Rotas</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html">7.3. Corrección de Problemas</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html#sect-Security-Enhanced_Linux-Fixing_Problems-Linux_Permissions">7.3.1. Permisos de Linux</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-Possible_Causes_of_Silent_Denials.html">7.3.2. Posibles Causas de las Negaciones Silenciosas</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services.html">7.3.3. Páginas de Manual para Servicios</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains.html">7.3.4. Dominios Permisivos</a></span></dt><dt><span class
 ="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-Searching_For_and_Viewing_Denials.html">7.3.5. Búsqueda y Revisión de Negaciones</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages.html">7.3.6. Mensajes Crudos de Auditoría</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages.html">7.3.7. Mensajes sealert</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow.html">7.3.8. Permitiendo el Acceso: audit2allow</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="chap-Security-Enhanced_Linux-Further_Information.html">8. Información Adicional</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-Further_Information.html#sect-Security-Enhanced_Linux-Further_Information-Contributors">8.1. Contribuyentes</a></span></dt><dt><span 
 class="section"><a href="sect-Security-Enhanced_Linux-Further_Information-Other_Resources.html">8.2. Otros Recursos</a></span></dt></dl></dd><dt><span class="appendix"><a href="appe-Security-Enhanced_Linux-Revision_History.html">A. Historia de Revisiones</a></span></dt></dl></div></div><ul class="docnav"><li class="previous"></li><li class="next"><a accesskey="n" href="pref-Security-Enhanced_Linux-Preface.html"><strong>Siguiente</strong>Prefacio</a></li></ul></body></html>
+			The SELinux User Guide assists users and administrators in managing and using Security-Enhanced <span class="trademark">Linux</span>®.
+		</div></div></div></div><hr /></div><div class="toc"><dl><dt><span class="preface"><a href="pref-Security-Enhanced_Linux-Preface.html">Prefacio</a></span></dt><dd><dl><dt><span class="section"><a href="pref-Security-Enhanced_Linux-Preface.html#id695028">1. Convenciones del Documento</a></span></dt><dd><dl><dt><span class="section"><a href="pref-Security-Enhanced_Linux-Preface.html#id837400">1.1. Convenciones Tipográficas</a></span></dt><dt><span class="section"><a href="pref-Security-Enhanced_Linux-Preface.html#id1143917">1.2. Convenciones del documento</a></span></dt><dt><span class="section"><a href="pref-Security-Enhanced_Linux-Preface.html#id791864">1.3. Notas y Advertencias</a></span></dt></dl></dd><dt><span class="section"><a href="pr01s02.html">2. ¡Necesitamos sus comentarios!</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Security-Enhanced_Linux-Trademark_Information.html">1. Información de Marca Comercial</a></span></dt><dd><dl><dt><span class
 ="section"><a href="chap-Security-Enhanced_Linux-Trademark_Information.html#chap-Security-Enhanced_Linux-Trademark_Information-Source_Code">1.1. Source Code</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Security-Enhanced_Linux-Introduction.html">2. Introducción</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-Introduction.html#sect-Security-Enhanced_Linux-Introduction-Benefits_of_running_SELinux">2.1. Beneficios de usar SELinux</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Introduction-Examples.html">2.2. Ejemplos</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture.html">2.3. Arquitectura de SELinux</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Introduction-SELinux_on_Other_Operating_Systems.html">2.4. SELinux en otros Sistemas Operativos</a></span></dt></dl></dd><dt><span class="chapter"><a h
 ref="chap-Security-Enhanced_Linux-SELinux_Contexts.html">3. Contextos de SELinux</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-SELinux_Contexts.html#sect-Security-Enhanced_Linux-SELinux_Contexts-Domain_Transitions">3.1. Transiciones de Dominios</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Processes.html">3.2. Contextos de SELinux para los Procesos</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Users.html">3.3. Contextos de SELinux para los Usuarios</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Security-Enhanced_Linux-Targeted_Policy.html">4. Política Destinado</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-Targeted_Policy.html#sect-Security-Enhanced_Linux-Targeted_Policy-Confined_Processes">4.1. Procesos Confinados</a></span></dt><dt><s
 pan class="section"><a href="sect-Security-Enhanced_Linux-Targeted_Policy-Unconfined_Processes.html">4.2. Procesos no Confinados</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users.html">4.3. Usuarios Confinados y no Confinados</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Security-Enhanced_Linux-Working_with_SELinux.html">5. Trabajando con SELinux</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-Working_with_SELinux.html#sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Packages">5.1. Paquetes de SELinux</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used.html">5.2. Qué Archivo Log se usa</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Main_Configuration_File.html">5.3. Archivo de Configuración Principal</a></span><
 /dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html">5.4. Habilitando y Deshabilitando SELinux</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html#sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Enabling_SELinux">5.4.1. Habilitando SELinux</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux.html">5.4.2. Deshabilitando SELinux</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes.html">5.5. Modos de SELinux</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html">5.6. Booleanos</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html#sect
 -Security-Enhanced_Linux-Booleans-Listing_Booleans">5.6.1. Listando los Booleanos</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Booleans-Configuring_Booleans.html">5.6.2. Configurando los Booleanos</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS.html">5.6.3. Booleanos para NFS y CIFS</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files.html">5.7. Contextos de SELinux - Etiquetado de Archivos</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files.html#sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Temporary_Changes_chcon">5.7.1. Cambios Temporales: chcon</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fco
 ntext.html">5.7.2. Cambios Persistentes: semanage fcontext</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types.html">5.8. Los tipos file_t y default_t</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html">5.9. Montaje de Sistemas de Archivos</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html#sect-Security-Enhanced_Linux-Mounting_File_Systems-Context_Mounts">5.9.1. Montajes de Contexto</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Changing_the_Default_Context.html">5.9.2. Cambio del Contexto Predeterminado</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Mounting_an_NFS_File_System.html">5.9.3. Montando un Sistema de Archivos NF
 S</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Multiple_NFS_Mounts.html">5.9.4. Montajes NFS Múltiples</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Making_Context_Mounts_Persistent.html">5.9.5. Haciendo Persistente los Contextos de Montajes</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html">5.10. Mantención de las Etiquetas de SELinux</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html#sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Copying_Files_and_Directories">5.10.1. Copia de Directorios y Archivos</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Moving_Files_and_Directories.html">5.10.2. Movimiento de Archivos y D
 irectorios</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context.html">5.10.3. Chequeando el Contexto SELinux Predeterminado</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_tar.html">5.10.4. Archivando archivos con tar</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_star.html">5.10.5. Archivando archivos con tar</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="chap-Security-Enhanced_Linux-Confining_Users.html">6. Confinando a los Usuarios</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-Confining_Users.html#sect-Security-Enhanced_Linux-Confining_Users-Linux_and_SELinux_User_Mappings">6.1. Linux y los Mapeos de Usuarios de SELinux</a></span></dt><dt><span class="section"><
 a href="sect-Security-Enhanced_Linux-Confining_Users-Confining_New_Linux_Users_useradd.html">6.2. Confinando Usuarios Nuevos de Linux: useradd</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Confining_Users-Confining_Existing_Linux_Users_semanage_login.html">6.3. Confinando Usuarios Linux Existentes: semanage login</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Confining_Users-Changing_the_Default_Mapping.html">6.4. Cambiando el Mapeo Predeterminado</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Confining_Users-xguest_Kiosk_Mode.html">6.5. xguest: Modo Kiosk</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications.html">6.6. Booleanos para que los Usuarios Ejecuten Aplicaciones</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Security-Enhanced_Linux-Troubleshooting.html">7. Solución a P
 roblemas</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-Troubleshooting.html#sect-Security-Enhanced_Linux-Troubleshooting-What_Happens_when_Access_is_Denied">7.1. Qué pasa cuando el Acceso es Denegado</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html">7.2. Tres Principales Causas de Problemas</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html#sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Labeling_Problems">7.2.1. Problemas de Etiquetados</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running.html">7.2.2. ¿Cómo se Ejecutan los Servicios Confinados?</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Evolving_Rules_and_B
 roken_Applications.html">7.2.3. Evolucionando las Reglas y las Aplicaciones Rotas</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html">7.3. Corrección de Problemas</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html#sect-Security-Enhanced_Linux-Fixing_Problems-Linux_Permissions">7.3.1. Permisos de Linux</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-Possible_Causes_of_Silent_Denials.html">7.3.2. Posibles Causas de las Negaciones Silenciosas</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services.html">7.3.3. Páginas de Manual para Servicios</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains.html">7.3.4. Dominios Permisivos</a></span></dt><dt><span class="se
 ction"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-Searching_For_and_Viewing_Denials.html">7.3.5. Búsqueda y Revisión de Negaciones</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages.html">7.3.6. Raw Audit Messages</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages.html">7.3.7. Mensajes sealert</a></span></dt><dt><span class="section"><a href="sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow.html">7.3.8. Permitiendo el Acceso: audit2allow</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="chap-Security-Enhanced_Linux-Further_Information.html">8. Información Adicional</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Security-Enhanced_Linux-Further_Information.html#sect-Security-Enhanced_Linux-Further_Information-Contributors">8.1. Contributors</a></span></dt><dt><span class="section"><
 a href="sect-Security-Enhanced_Linux-Further_Information-Other_Resources.html">8.2. Other Resources</a></span></dt></dl></dd><dt><span class="appendix"><a href="appe-Security-Enhanced_Linux-Revision_History.html">A. Revision History</a></span></dt></dl></div></div><ul class="docnav"><li class="previous"></li><li class="next"><a accesskey="n" href="pref-Security-Enhanced_Linux-Preface.html"><strong>Siguiente</strong>Prefacio</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/pr01s02.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/pr01s02.html
index 9576c63..98942cf 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/pr01s02.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/pr01s02.html
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2. ¡Necesitamos sus comentarios!</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="pref-Security-Enhanced_Linux-Preface.html" title="Prefacio" /><link rel="prev" href="pref-Security-Enhanced_Linux-Preface.html" title="Prefacio" /><link rel="next" href="chap-Security-Enhanced_Linux-Trademark_Information.html" title="Capítulo 1. Información de Marca Comercial" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to vi
 ew it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="pref-Security-Enhanced_Linux-Preface.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-Trademark_Information.html"><strong>Siguiente</strong></a></li></ul><div xml:lang="es-ES" class="section" title="2. ¡Necesitamos sus comentarios!" lang="es-ES"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id2010625">2. ¡Necesitamos sus comentarios!</h2></div></div></div><a id="id2010637" class="indexterm"></a><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2. ¡Necesitamos sus comentarios!</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="pref-Security-Enhanced_Linux-Preface.html" title="Prefacio" /><link rel="prev" href="pref-Security-Enhanced_Linux-Preface.html" title="Prefacio" /><link rel="next" href="chap-Security-Enhanced_Linux-Trademark_Information.html" title="Capítulo 1. Información de Marca Comercial" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe,
  to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="pref-Security-Enhanced_Linux-Preface.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-Trademark_Information.html"><strong>Siguiente</strong></a></li></ul><div xml:lang="es-ES" class="section" title="2. ¡Necesitamos sus comentarios!" lang="es-ES"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id718011">2. ¡Necesitamos sus comentarios!</h2></div></div></div><a id="id893928" class="indexterm"></a><div class="para">
 		Si encuentra un error tipográfico en este manual o si sabe de alguna manera de mejorarlo, nos gustaría escuchar sus sugerencias. Por favor complete un reporte en Bugzilla: <a href="http://bugzilla.redhat.com/bugzilla/">http://bugzilla.redhat.com/bugzilla/</a> usando el producto <span class="application"><strong>Fedora Documentation</strong></span>.
 	</div><div class="para">
 		Cuando envíe un reporte de error no olvide mencionar el identificador del manual: <em class="citetitle">selinux-user-guide</em>
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/pref-Security-Enhanced_Linux-Preface.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/pref-Security-Enhanced_Linux-Preface.html
index ef7e58c..6194425 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/pref-Security-Enhanced_Linux-Preface.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/pref-Security-Enhanced_Linux-Preface.html
@@ -1,22 +1,22 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Prefacio</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="prev" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="next" href="pr01s02.html" title="2. ¡Necesitamos sus comentarios!" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href
 ="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="index.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="pr01s02.html"><strong>Siguiente</strong></a></li></ul><div xml:lang="es-ES" class="preface" title="Prefacio" id="pref-Security-Enhanced_Linux-Preface" lang="es-ES"><div class="titlepage"><div><div><h1 class="title">Prefacio</h1></div></div></div><div class="para">
-		La Guía del Usuario de SELinux de Fedora 13 es para gente sin o con mínima experiencia con SELinux. Aunque la experiencia de administración de sistema no es necesario, el contenido de esta guía se escribe para tareas de administración del sistema. Esta guía provee una introducción a los conceptos fundamentales y aplicaciones prácticas de SELinux. Después de leer esta guía debe tener un entendimiento intermedio de SELinux.
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Prefacio</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="prev" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="next" href="pr01s02.html" title="2. ¡Necesitamos sus comentarios!" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left
 " href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="index.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="pr01s02.html"><strong>Siguiente</strong></a></li></ul><div xml:lang="es-ES" class="preface" title="Prefacio" id="pref-Security-Enhanced_Linux-Preface" lang="es-ES"><div class="titlepage"><div><div><h1 class="title">Prefacio</h1></div></div></div><div class="para">
+		The Fedora 13 SELinux User Guide is for people with minimal or no experience with SELinux. Although system administration experience is not necessary, content in this guide is written for system administration tasks. This guide provides an introduction to fundamental concepts and practical applications of SELinux. After reading this guide you should have an intermediate understanding of SELinux.
 	</div><div class="para">
 		Gracias a todos los que nos alentaron, ofrecieron ayuda y lo probaron - la ayuda es muy apreciada. Agradecimientos muy especiales a:
 	</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
 				Dominick Grift, Stephen Smalley y Russell Coker por sus contribuciones, ayuda y paciencia.
 			</div></li><li class="listitem"><div class="para">
-				Karsten Wade por su ayuda, al agregar un componente para esta guía en el <a href="https://bugzilla.redhat.com/">Bugzilla de Red Hat</a> y resolver el alojamiento web en <a href="http://docs.fedoraproject.org/">http://docs.fedoraproject.org/</a>.
+				Karsten Wade for his help, adding a component for this guide to <a href="https://bugzilla.redhat.com/"> Red Hat Bugzilla</a>, and sorting out web hosting on <a href="http://docs.fedoraproject.org/">http://docs.fedoraproject.org/</a>.
 			</div></li><li class="listitem"><div class="para">
 				Al <a href="http://fedoraproject.org/wiki/Infrastructure">Equipo de Infraestructura de Fedora</a> por proveer el alojamiento.
 			</div></li><li class="listitem"><div class="para">
 				Jens-Ulrik Petersen por asegurar que la oficina de Brisbane de Red Hat tenga espejos de Fedora actualizados.
-			</div></li></ul></div><div xml:lang="es-ES" class="section" title="1. Convenciones del Documento" lang="es-ES"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id1073417">1. Convenciones del Documento</h2></div></div></div><div class="para">
+			</div></li></ul></div><div xml:lang="es-ES" class="section" title="1. Convenciones del Documento" lang="es-ES"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id695028">1. Convenciones del Documento</h2></div></div></div><div class="para">
 		Este manual utiliza varias convenciones para resaltar algunas palabras y frases y llamar la atención sobre ciertas partes específicas de información.
 	</div><div class="para">
 		En ediciones PDF y de papel, este manual utiliza tipos de letra procedentes de <a href="https://fedorahosted.org/liberation-fonts/">Liberation Fonts</a>. Liberation Fonts también se utilizan en ediciones de HTML si están instalados en su sistema. Si no, se muestran tipografías alternativas pero equivalentes. Nota: Red Hat Enterprise Linux 5 y siguientes incluyen Liberation Fonts predeterminadas.
-	</div><div class="section" title="1.1. Convenciones Tipográficas"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id978564">1.1. Convenciones Tipográficas</h3></div></div></div><div class="para">
+	</div><div class="section" title="1.1. Convenciones Tipográficas"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id837400">1.1. Convenciones Tipográficas</h3></div></div></div><div class="para">
 			Se utilizan cuatro convenciones tipográficas para llamar la atención sobre palabras o frases específicas. Dichas convenciones y las circunstancias en que se aplican son las siguientes:
 		</div><div class="para">
 			<code class="literal">Negrita monoespaciado</code>
@@ -64,7 +64,7 @@
 			Aparte del uso estándar para presentar el título de un trabajo, las itálicas denotan el primer uso de un término nuevo e importante. Por ejemplo:
 		</div><div class="blockquote"><blockquote class="blockquote"><div class="para">
 				Publican es un sistema de publicación de <em class="firstterm">DocBook</em>.
-			</div></blockquote></div></div><div class="section" title="1.2. Convenciones del documento"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id2046495">1.2. Convenciones del documento</h3></div></div></div><div class="para">
+			</div></blockquote></div></div><div class="section" title="1.2. Convenciones del documento"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id1143917">1.2. Convenciones del documento</h3></div></div></div><div class="para">
 			Los mensajes de salida de la terminal o fragmentos de código fuente se distinguen visualmente del texto circundante.
 		</div><div class="para">
 			Los mensajes de salida enviados a una terminal se muestran en <code class="computeroutput">romano monoespaciado</code> y se presentan así:
@@ -93,7 +93,7 @@ books_tests  Desktop1  downloads      images  notes  scripts  svgs
    }
 }
 
-</pre></div><div class="section" title="1.3. Notas y Advertencias"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id974259">1.3. Notas y Advertencias</h3></div></div></div><div class="para">
+</pre></div><div class="section" title="1.3. Notas y Advertencias"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id791864">1.3. Notas y Advertencias</h3></div></div></div><div class="para">
 			Finalmente, utilizamos tres estilos visuales para llamar la atención sobre la información que de otro modo se podría pasar por alto.
 		</div><div class="note"><h2>Nota</h2><div class="para">
 				Una nota es una sugerencia, atajo o enfoque alternativo para una tarea determinada. Ignorar una nota no debería tener consecuencias negativas, pero podría perderse de algunos trucos que pueden facilitarle las cosas.
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS.html
index af11e08..5cc6742 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS.html
@@ -1,12 +1,12 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.6.3. Booleanos para NFS y CIFS</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html" title="5.6. Booleanos" /><link rel="prev" href="sect-Security-Enhanced_Linux-Booleans-Configuring_Booleans.html" title="5.6.2. Configurando los Booleanos" /><link rel="next" href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files.html" title="5.7. Contextos de SELinux - Etiquetado de Archivos" /></head><body class="toc_embeded "><di
 v id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Booleans-Configuring_Booleans.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.6.3. Booleanos para NFS y CIFS" id="sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS"><div class="titlepage"><div><div keep-together.within-column="always"><h3
  class="title">5.6.3. Booleanos para NFS y CIFS</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.6.3. Booleanos para NFS y CIFS</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html" title="5.6. Booleanos" /><link rel="prev" href="sect-Security-Enhanced_Linux-Booleans-Configuring_Booleans.html" title="5.6.2. Configurando los Booleanos" /><link rel="next" href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files.html" title="5.7. Contextos de SELinux - Etiquetado de Archivos" /></head><body class="draft toc_embeded
  "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Booleans-Configuring_Booleans.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.6.3. Booleanos para NFS y CIFS" id="sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS"><div class="titlepage"><div><div keep-together.within-column="alway
 s"><h3 class="title">5.6.3. Booleanos para NFS y CIFS</h3></div></div></div><div class="para">
 				Por defecto, los montajes NFS en el lado del cliente se etiquetan con el contexto predeterminado definido por la política para sistemas de archivos NFS. En políticas comúnes, este contexto predeterminado usa el tipo <code class="computeroutput">nfs_t</code>. También, por defecto, los compartidos de Samba en el lado del cliente se etiquetan con el contexto predeterminado definido por la política. En políticas comúnes, este contexto predeterminado usa el tipo <code class="computeroutput">cifs_t</code>.
 			</div><div class="para">
 				Dependiendo en la configuración de la política, los servicios pueden tener bloqueado la lectura a archivos con la etiqueta de los tipos <code class="computeroutput">nfs_t</code> o <code class="computeroutput">cifs_t</code>. Esto puede prevenir que los sistemas de archivo etiquetados con estas etiquetas se monten y sean leídos o exportados por otros servicios. Hay Booleanos que se pueden poner en 1 o 0 para controlar qué servicios pueden acceder los tipos <code class="computeroutput">nfs_t</code> y <code class="computeroutput">cifs_t</code>.
 			</div><div class="para">
 				Los comandos <code class="command">setsebool</code> y <code class="command">semanage</code> se deben ejecutar como usuario root de Linux. El comando <code class="command">setsebool -P</code> hace persistentes a los cambios. No use la opción <code class="option">-P</code> si no quiere que los cambios persistan entre reiniciadas:
-			</div><div class="formalpara"><h5 class="formalpara">Servidor HTTP Apache</h5>
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Booleans_for_NFS_and_CIFS-Apache_HTTP_Server"><h5 class="formalpara">Servidor HTTP Apache</h5>
 					Para permitir el acceso a sistemas de archivo NFS (archivos etiquetados con el tipo <code class="computeroutput">nfs_t</code>):
 				</div><div class="para">
 				<code class="command">/usr/sbin/setsebool -P httpd_use_nfs on</code>
@@ -14,11 +14,11 @@
 				Para permitir el acceso a sistemas de archivos SAMBA (archivos etiquetados con el tipo <code class="computeroutput">cifs_t</code>):
 			</div><div class="para">
 				<code class="command">/usr/sbin/setsebool -P httpd_use_cifs on</code>
-			</div><div class="formalpara"><h5 class="formalpara">Samba</h5>
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Booleans_for_NFS_and_CIFS-Samba"><h5 class="formalpara">Samba</h5>
 					Para exportar sistemas de archivo NFS:
 				</div><div class="para">
 				<code class="command">/usr/sbin/setsebool -P samba_share_nfs on</code>
-			</div><div class="formalpara"><h5 class="formalpara">FTP (<code class="systemitem">vsftpd</code>)</h5>
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Booleans_for_NFS_and_CIFS-FTP_vsftpd"><h5 class="formalpara">FTP (<code class="systemitem">vsftpd</code>)</h5>
 					Para permitir el acceso a sistemas de archivo NFS:
 				</div><div class="para">
 				<code class="command">/usr/sbin/setsebool -P allow_ftpd_use_nfs on</code>
@@ -26,7 +26,7 @@
 				Para permitir el acceso a sistemas de archivo Samba:
 			</div><div class="para">
 				<code class="command">/usr/sbin/setsebool -P allow_ftpd_use_cifs on</code>
-			</div><div class="formalpara"><h5 class="formalpara">Otros Servicios</h5>
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Booleans_for_NFS_and_CIFS-Other_Services"><h5 class="formalpara">Otros Servicios</h5>
 					Para una lista de los Booleanos relacionados con NFS para otros servicios:
 				</div><div class="para">
 				<code class="command">/usr/sbin/semanage boolean -l | grep nfs</code>
@@ -35,7 +35,7 @@
 			</div><div class="para">
 				<code class="command">/usr/sbin/semanage boolean -l | grep cifs</code>
 			</div><div class="note"><h2>Nota</h2><div class="para">
-					Estos Booleanos existen en la política de SELinux tal cual fueron puestos en Fedora 13. Pueden no existir en la política puesta en otras versiones de Fedora o de otros sistemas operativos.
+					These Booleans exist in SELinux policy as shipped with Fedora 13. They may not exist in policy shipped with other versions of Fedora or other operating systems.
 				</div></div><div class="para">
-				Refer to the SELinux Managing Confined Services Guide at <a href="http://docs.fedoraproject.org">http://docs.fedoraproject.org</a> for more information regarding SELinux Booleans.
+				Refer to the SELinux Managing Confined Services Guide:<a href="http://docs.fedoraproject.org/selinux-managing-confined-services-guide">http://docs.fedoraproject.org/selinux-managing-confined-services-guide</a> for more information relating to SELinux Booleans.
 			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Booleans-Configuring_Booleans.html"><strong>Anterior</strong>5.6.2. Configurando los Booleanos</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files.html"><strong>Siguiente</strong>5.7. Contextos de SELinux - Etiquetado de Archivos</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Booleans-Configuring_Booleans.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Booleans-Configuring_Booleans.html
index 6dee18f..d11fd47 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Booleans-Configuring_Booleans.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Booleans-Configuring_Booleans.html
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.6.2. Configurando los Booleanos</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html" title="5.6. Booleanos" /><link rel="prev" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html" title="5.6. Booleanos" /><link rel="next" href="sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS.html" title="5.6.3. Booleanos para NFS y CIFS" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class=
 "toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.6.2. Configurando los Booleanos" id="sect-Security-Enhanced_Linux-Booleans-Configuring_Booleans"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.6.2. Configurando los Booleanos</h3></div></div></div><div 
 class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.6.2. Configurando los Booleanos</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html" title="5.6. Booleanos" /><link rel="prev" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html" title="5.6. Booleanos" /><link rel="next" href="sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS.html" title="5.6.3. Booleanos para NFS y CIFS" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" 
 class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.6.2. Configurando los Booleanos" id="sect-Security-Enhanced_Linux-Booleans-Configuring_Booleans"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.6.2. Configurando los Booleanos</h3></div></div></div
 ><div class="para">
 				El comando <code class="command">setsebool <em class="replaceable"><code>nombre-de-booleano</code></em> <em class="replaceable"><code>x</code></em></code> activa o desactiva Booleanos, donde <em class="replaceable"><code>nombre-de-booleano</code></em> es un nombre de Booleano, y <em class="replaceable"><code>x</code></em> es <code class="option">on</code> para activar, u <code class="option">off</code> para desactivar.
 			</div><div class="para">
 				El siguiente ejemplo muestra la configuración de Booleano <code class="computeroutput">httpd_can_network_connect_db</code>:
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications.html
index 9ab3fd2..047bc97 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications.html
@@ -1,22 +1,22 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.6. Booleanos para que los Usuarios Ejecuten Aplicaciones</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Confining_Users.html" title="Capítulo 6. Confinando a los Usuarios" /><link rel="prev" href="sect-Security-Enhanced_Linux-Confining_Users-xguest_Kiosk_Mode.html" title="6.5. xguest: Modo Kiosk" /><link rel="next" href="chap-Security-Enhanced_Linux-Troubleshooting.html" title="Capítulo 7. Solución a Problemas" /></head><body class="toc_embeded "><div id="tocdiv" class="to
 c"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Confining_Users-xguest_Kiosk_Mode.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-Troubleshooting.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="6.6. Booleanos para que los Usuarios Ejecuten Aplicaciones" id="sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class=
 "title">6.6. Booleanos para que los Usuarios Ejecuten Aplicaciones</h2></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.6. Booleanos para que los Usuarios Ejecuten Aplicaciones</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Confining_Users.html" title="Capítulo 6. Confinando a los Usuarios" /><link rel="prev" href="sect-Security-Enhanced_Linux-Confining_Users-xguest_Kiosk_Mode.html" title="6.5. xguest: Modo Kiosk" /><link rel="next" href="chap-Security-Enhanced_Linux-Troubleshooting.html" title="Capítulo 7. Solución a Problemas" /></head><body class="draft toc_embeded "><div id="tocdiv" cla
 ss="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Confining_Users-xguest_Kiosk_Mode.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-Troubleshooting.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="6.6. Booleanos para que los Usuarios Ejecuten Aplicaciones" id="sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications"><div class="titlepage"><div><div keep-together.within-column="always"><h2 
 class="title">6.6. Booleanos para que los Usuarios Ejecuten Aplicaciones</h2></div></div></div><div class="para">
 			Not allowing Linux users to execute applications (which inherit users' permissions) in their home directories and <code class="filename">/tmp/</code>, which they have write access to, helps prevent flawed or malicious applications from modifying files that users own. In Fedora 13, by default, Linux users in the <code class="computeroutput">guest_t</code> and <code class="computeroutput">xguest_t</code> domains can not execute applications in their home directories or <code class="filename">/tmp/</code>; however, by default, Linux users in the <code class="computeroutput">user_t</code> and <code class="computeroutput">staff_t</code> domains can.
 		</div><div class="para">
 			Hay booleanos disponibles para cambiar este comportamiento, y se configuran con el comando <code class="command">setsebool</code>. El comando <code class="command">setsebool</code> se debe usar con el usuario root de Linux. El comando <code class="command">setsebool -P</code> hace los cambios persistentes. No use la opción <code class="option">-P</code> si no quiere que los cambios persistan entre reiniciadas:
-		</div><div class="formalpara"><h5 class="formalpara">guest_t</h5>
+		</div><div class="formalpara" id="form-Security-Enhanced_Linux-Booleans_for_Users_Executing_Applications-guest_t"><h5 class="formalpara">guest_t</h5>
 				Para <span class="emphasis"><em>permitir</em></span> a los usuarios Linux en el dominio <code class="computeroutput">guest_t</code> que ejecuten aplicaciones en sus directorios de inicio y en <code class="filename">/tmp/</code>:
 			</div><div class="para">
 			<code class="command">/usr/sbin/setsebool -P allow_guest_exec_content on</code>
-		</div><div class="formalpara"><h5 class="formalpara">xguest_t</h5>
+		</div><div class="formalpara" id="form-Security-Enhanced_Linux-Booleans_for_Users_Executing_Applications-xguest_t"><h5 class="formalpara">xguest_t</h5>
 				Para <span class="emphasis"><em>permitir</em></span> a los usuarios Linux en el dominio <code class="computeroutput">xguest_t</code> ejecutar aplicaciones en sus directorios inicios y <code class="filename">/tmp/</code>:
 			</div><div class="para">
 			<code class="command">/usr/sbin/setsebool -P allow_xguest_exec_content on</code>
-		</div><div class="formalpara"><h5 class="formalpara">user_t</h5>
+		</div><div class="formalpara" id="form-Security-Enhanced_Linux-Booleans_for_Users_Executing_Applications-user_t"><h5 class="formalpara">user_t</h5>
 				Para <span class="emphasis"><em>impedir</em></span> que los usuarios Linux en el dominio <code class="computeroutput">user_t</code> ejecuten aplicaciones en sus directorios de inicio y <code class="filename">/tmp/</code>:
 			</div><div class="para">
 			<code class="command">/usr/sbin/setsebool -P allow_user_exec_content off</code>
-		</div><div class="formalpara"><h5 class="formalpara">staff_t</h5>
+		</div><div class="formalpara" id="form-Security-Enhanced_Linux-Booleans_for_Users_Executing_Applications-staff_t"><h5 class="formalpara">staff_t</h5>
 				Para <span class="emphasis"><em>impedir</em></span> que los usuarios Linux en el dominio <code class="computeroutput">staff_t</code> ejecuten aplicaciones en sus directorios de inicio y en <code class="filename">/tmp/</code>:
 			</div><div class="para">
 			<code class="command">/usr/sbin/setsebool -P allow_staff_exec_content off</code>
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Confining_Users-Changing_the_Default_Mapping.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Confining_Users-Changing_the_Default_Mapping.html
index 70f709c..67b99ad 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Confining_Users-Changing_the_Default_Mapping.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Confining_Users-Changing_the_Default_Mapping.html
@@ -1,7 +1,7 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.4. Cambiando el Mapeo Predeterminado</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Confining_Users.html" title="Capítulo 6. Confinando a los Usuarios" /><link rel="prev" href="sect-Security-Enhanced_Linux-Confining_Users-Confining_Existing_Linux_Users_semanage_login.html" title="6.3. Confinando Usuarios Linux Existentes: semanage login" /><link rel="next" href="sect-Security-Enhanced_Linux-Confining_Users-xguest_Kiosk_Mode.html" title="6.5. xguest: Modo Kiosk" /></head><bod
 y class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Confining_Users-Confining_Existing_Linux_Users_semanage_login.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Confining_Users-xguest_Kiosk_Mode.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="6.4. Cambiando el Mapeo Predeterminado" id="sect-Security-Enhanced_Linux-Confining_Users-Changing_the_Default_Mapping"><div class="titlep
 age"><div><div keep-together.within-column="always"><h2 class="title">6.4. Cambiando el Mapeo Predeterminado</h2></div></div></div><div class="para">
-			En Fedora 13, los usuarios Linux se mapean al ingreso SELinux <code class="computeroutput">__default__</code> por defecto (que se mapea al usuario SELinux <code class="computeroutput">unconfined_u</code>). Si quiere que los usuarios nuevos de Linux y los usuarios Linux no mapeados específicamente a un usuario SELinux sean confinados por defecto, cambie el mapeo predeterminado con el comando <code class="command">semanage login</code>.
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.4. Cambiando el Mapeo Predeterminado</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Confining_Users.html" title="Capítulo 6. Confinando a los Usuarios" /><link rel="prev" href="sect-Security-Enhanced_Linux-Confining_Users-Confining_Existing_Linux_Users_semanage_login.html" title="6.3. Confinando Usuarios Linux Existentes: semanage login" /><link rel="next" href="sect-Security-Enhanced_Linux-Confining_Users-xguest_Kiosk_Mode.html" title="6.5. xguest: Modo Kiosk" /></head><bod
 y class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Confining_Users-Confining_Existing_Linux_Users_semanage_login.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Confining_Users-xguest_Kiosk_Mode.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="6.4. Cambiando el Mapeo Predeterminado" id="sect-Security-Enhanced_Linux-Confining_Users-Changing_the_Default_Mapping"><div class="
 titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.4. Cambiando el Mapeo Predeterminado</h2></div></div></div><div class="para">
+			In Fedora 13, Linux users are mapped to the SELinux <code class="computeroutput">__default__</code> login by default (which is in turn mapped to the SELinux <code class="computeroutput">unconfined_u</code> user). If you would like new Linux users, and Linux users not specifically mapped to an SELinux user to be confined by default, change the default mapping with the <code class="command">semanage login</code> command.
 		</div><div class="para">
 			Por ejemplo, corra el siguiente comando como usuario root de Linux para cambiar el mapeo predeterminado de <code class="computeroutput">unconfined_u</code> a <code class="computeroutput">user_u</code>:
 		</div><div class="para">
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Confining_Users-Confining_Existing_Linux_Users_semanage_login.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Confining_Users-Confining_Existing_Linux_Users_semanage_login.html
index a0e9f7f..a1419b6 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Confining_Users-Confining_Existing_Linux_Users_semanage_login.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Confining_Users-Confining_Existing_Linux_Users_semanage_login.html
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.3. Confinando Usuarios Linux Existentes: semanage login</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Confining_Users.html" title="Capítulo 6. Confinando a los Usuarios" /><link rel="prev" href="sect-Security-Enhanced_Linux-Confining_Users-Confining_New_Linux_Users_useradd.html" title="6.2. Confinando Usuarios Nuevos de Linux: useradd" /><link rel="next" href="sect-Security-Enhanced_Linux-Confining_Users-Changing_the_Default_Mapping.html" title="6.4. Cambiando el Mapeo Pred
 eterminado" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Confining_Users-Confining_New_Linux_Users_useradd.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Confining_Users-Changing_the_Default_Mapping.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="6.3. Confinando Usuarios Linux Existentes: semanage login" id="sect-Security-Enhanced_Linux-Confining_Users-Confi
 ning_Existing_Linux_Users_semanage_login"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.3. Confinando Usuarios Linux Existentes: semanage login</h2></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.3. Confinando Usuarios Linux Existentes: semanage login</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Confining_Users.html" title="Capítulo 6. Confinando a los Usuarios" /><link rel="prev" href="sect-Security-Enhanced_Linux-Confining_Users-Confining_New_Linux_Users_useradd.html" title="6.2. Confinando Usuarios Nuevos de Linux: useradd" /><link rel="next" href="sect-Security-Enhanced_Linux-Confining_Users-Changing_the_Default_Mapping.html" title="6.4. Cambiando el Mapeo Pred
 eterminado" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Confining_Users-Confining_New_Linux_Users_useradd.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Confining_Users-Changing_the_Default_Mapping.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="6.3. Confinando Usuarios Linux Existentes: semanage login" id="sect-Security-Enhanced_Linux-Confining_Users
 -Confining_Existing_Linux_Users_semanage_login"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.3. Confinando Usuarios Linux Existentes: semanage login</h2></div></div></div><div class="para">
 			Si un usuario Linux se mapea al usuario <code class="computeroutput">unconfined_u</code> (el comportamiento predeterminado), y desea cambiar le usuario SELinux al que se mapea, use el comando <code class="command">semanage login</code>. El siguiente ejemplo crea un usuario de Linux nuevo llamado usuarionuevo, luego lo mapea al usuario SELinux <code class="computeroutput">user_u</code>:
 		</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
 					Como usuario root de Linux, ejecute el comando <code class="command">/usr/sbin/useradd usuarionuevo</code> para crear un nuevo usuario (usuarionuevo). Dado que este usuario usa el mapeo por defecto, no aparece en la salida de <code class="command">/usr/sbin/semanage login -l</code>:
@@ -16,7 +16,7 @@ system_u                  system_u                  s0-s0:c0.c1023
 </pre></li><li class="listitem"><div class="para">
 					Para mapear un usuario usuarionuevo de Linux al usuario <code class="computeroutput">user_u</code> de SELinux, corra el siguiente comando como usuario root de Linux:
 				</div><div class="para">
-					<code class="command">/usr/sbin/semanage login -a -s user_u usuarionuevo</code>
+					<code class="command">/usr/sbin/semanage login -a -s user_u newuser</code>
 				</div><div class="para">
 					La opción <code class="option">-a</code> agrega un registro nuevo y la opción <code class="option">-s</code> especifica el usuario SELinux al que mapea el usuario Linux. El último argumento <code class="computeroutput">usuarionuevo</code>, es el usuario Linux al que quiere que se mapee el usuario SELinux especificado.
 				</div></li><li class="listitem"><div class="para">
@@ -32,7 +32,7 @@ root                      unconfined_u              s0-s0:c0.c1023
 system_u                  system_u                  s0-s0:c0.c1023
 
 </pre></li><li class="listitem"><div class="para">
-					Como usuario root de Linux, corra el comando <code class="command">passwd usuarionuevo</code> para asignar una contraseña para el usuario usuarionuevo de Linux:
+					As the Linux root user, run the <code class="command">passwd newuser</code> command to assign a password to the Linux newuser user:
 				</div><pre class="screen">
 # passwd newuser
 Changing password for user newuser.
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Confining_Users-Confining_New_Linux_Users_useradd.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Confining_Users-Confining_New_Linux_Users_useradd.html
index ebfa2f0..03f8576 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Confining_Users-Confining_New_Linux_Users_useradd.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Confining_Users-Confining_New_Linux_Users_useradd.html
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.2. Confinando Usuarios Nuevos de Linux: useradd</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Confining_Users.html" title="Capítulo 6. Confinando a los Usuarios" /><link rel="prev" href="chap-Security-Enhanced_Linux-Confining_Users.html" title="Capítulo 6. Confinando a los Usuarios" /><link rel="next" href="sect-Security-Enhanced_Linux-Confining_Users-Confining_Existing_Linux_Users_semanage_login.html" title="6.3. Confinando Usuarios Linux Existentes: semanage login" /></h
 ead><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-Confining_Users.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Confining_Users-Confining_Existing_Linux_Users_semanage_login.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="6.2. Confinando Usuarios Nuevos de Linux: useradd" id="sect-Security-Enhanced_Linux-Confining_Users-Confining_New_Linux_Users_useradd"><div class="
 titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.2. Confinando Usuarios Nuevos de Linux: useradd</h2></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.2. Confinando Usuarios Nuevos de Linux: useradd</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Confining_Users.html" title="Capítulo 6. Confinando a los Usuarios" /><link rel="prev" href="chap-Security-Enhanced_Linux-Confining_Users.html" title="Capítulo 6. Confinando a los Usuarios" /><link rel="next" href="sect-Security-Enhanced_Linux-Confining_Users-Confining_Existing_Linux_Users_semanage_login.html" title="6.3. Confinando Usuarios Linux Existentes: semanage login" /></h
 ead><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-Confining_Users.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Confining_Users-Confining_Existing_Linux_Users_semanage_login.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="6.2. Confinando Usuarios Nuevos de Linux: useradd" id="sect-Security-Enhanced_Linux-Confining_Users-Confining_New_Linux_Users_useradd"><div c
 lass="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.2. Confinando Usuarios Nuevos de Linux: useradd</h2></div></div></div><div class="para">
 			Los usuarios Linux mapeados al usuario SELinux <code class="computeroutput">unconfined_u</code> corren en el dominio <code class="computeroutput">unconfined_t</code>. Esto se ve ejecutando el comando <code class="command">id -Z</code> luego de haber ingresado como el usuario Linux que se mapea a <code class="computeroutput">unconfined_u</code>:
 		</div><pre class="screen">
 $ id -Z
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Confining_Users-xguest_Kiosk_Mode.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Confining_Users-xguest_Kiosk_Mode.html
index 9995f1f..978f19d 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Confining_Users-xguest_Kiosk_Mode.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Confining_Users-xguest_Kiosk_Mode.html
@@ -1,7 +1,7 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.5. xguest: Modo Kiosk</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Confining_Users.html" title="Capítulo 6. Confinando a los Usuarios" /><link rel="prev" href="sect-Security-Enhanced_Linux-Confining_Users-Changing_the_Default_Mapping.html" title="6.4. Cambiando el Mapeo Predeterminado" /><link rel="next" href="sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications.html" title="6.6. Booleanos para que los Usuarios Ejecuten Aplicaciones" /></h
 ead><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Confining_Users-Changing_the_Default_Mapping.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="6.5. xguest: Modo Kiosk" id="sect-Security-Enhanced_Linux-Confining_Users-xguest_Kiosk_Mode"><div class="titlepage"><div><
 div keep-together.within-column="always"><h2 class="title">6.5. xguest: Modo Kiosk</h2></div></div></div><div class="para">
-			El paquete <span class="package">xguest</span> provee una cuenta de usuario kiosk. Esta cuenta se usa para asegurar máquinas a las que ingresan personas y las usan, como las de las bibliotecas, bancos, aeropuertos, quioscos de información y cyber cafés. La cuenta de usuario kiosk está muy bloqueada: escencialmente, sólo permite a los usuarios ingresar y usar <span class="application"><strong>Firefox</strong></span> para navegar sitios de Internet. Cualquier cambio hecho mientras se ingresó con esa cuenta, tal como la creación y cambio de la configuración, se pierde cuando se sale.
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.5. xguest: Modo Kiosk</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Confining_Users.html" title="Capítulo 6. Confinando a los Usuarios" /><link rel="prev" href="sect-Security-Enhanced_Linux-Confining_Users-Changing_the_Default_Mapping.html" title="6.4. Cambiando el Mapeo Predeterminado" /><link rel="next" href="sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications.html" title="6.6. Booleanos para que los Usuarios Ejecuten Aplicaciones" /></h
 ead><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Confining_Users-Changing_the_Default_Mapping.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="6.5. xguest: Modo Kiosk" id="sect-Security-Enhanced_Linux-Confining_Users-xguest_Kiosk_Mode"><div class="titlepage">
 <div><div keep-together.within-column="always"><h2 class="title">6.5. xguest: Modo Kiosk</h2></div></div></div><div class="para">
+			The <span class="package">xguest</span> package provides a kiosk user account. This account is used to secure machines that people walk up to and use, such as those at libraries, banks, airports, information kiosks, and coffee shops. The kiosk user account is very limited: essentially, it only allows users to log in and use <span class="application"><strong>Firefox</strong></span> to browse Internet websites. Any changes made while logged in with his account, such as creating files or changing settings, are lost when you log out.
 		</div><div class="para">
 			Para configurar la cuenta kiosk:
 		</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
@@ -13,7 +13,7 @@ $ /usr/sbin/getenforce
 Enforcing
 
 </pre><div class="para">
-					Si no es éste el caso, vaya a <a class="xref" href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes.html" title="5.5. Modos de SELinux">Sección 5.5, “Modos de SELinux”</a> para información acerca del cambio de modo a obediente. No es posible ingresar con esta cuenta si SELinux está en modo permisivo o deshabilitado.
+					If this is not the case, refer to <a class="xref" href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes.html" title="5.5. Modos de SELinux">Sección 5.5, “Modos de SELinux”</a> for information about changing to enforcing mode. It is not possible to log in with this account if SELinux is in permissive mode or disabled.
 				</div></li><li class="listitem"><div class="para">
 					Solamente puede ingresar a esta cuenta a través del Administración de Pantalla de GNOME (GDM). Una vez que el paquete <span class="package">xguest</span> se instala, se agrega una cuenta <code class="computeroutput">Invitado</code> a GDM. Para ingresar, haga clic en la cuenta <code class="computeroutput">Invitado</code>:
 				</div><div class="mediaobject"><img src="./images/xguest.png" /></div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Confining_Users-Changing_the_Default_Mapping.html"><strong>Anterior</strong>6.4. Cambiando el Mapeo Predeterminado</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications.html"><strong>Siguiente</strong>6.6. Booleanos para que los Usuarios Ejecuten Apl...</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux.html
index 3a9f510..f0ea73b 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux.html
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.4.2. Deshabilitando SELinux</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html" title="5.4. Habilitando y Deshabilitando SELinux" /><link rel="prev" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html" title="5.4. Habilitando y Deshabilitando SELinux" /><link rel="next" href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes.html" title="5.5. Modos de SELinux" /></head><
 body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.4.2. Deshabilitando SELinux" id="sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux"><div class="titlepage"><div><
 div keep-together.within-column="always"><h3 class="title">5.4.2. Deshabilitando SELinux</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.4.2. Deshabilitando SELinux</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html" title="5.4. Habilitando y Deshabilitando SELinux" /><link rel="prev" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html" title="5.4. Habilitando y Deshabilitando SELinux" /><link rel="next" href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes.html" title="5.5. Modos de SELinux" /></head><
 body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.4.2. Deshabilitando SELinux" id="sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux"><div class="titlepage">
 <div><div keep-together.within-column="always"><h3 class="title">5.4.2. Deshabilitando SELinux</h3></div></div></div><div class="para">
 				Para deshabilitar SELinux, configure <code class="option">SELINUX=disabled</code> en <code class="filename">/etc/selinux/config</code>:
 			</div><pre class="screen"># This file controls the state of SELinux on the system.
 # SELINUX= can take one of these three values:
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow.html
index f7921c3..d930db8 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow.html
@@ -1,9 +1,9 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.3.8. Permitiendo el Acceso: audit2allow</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html" title="7.3. Corrección de Problemas" /><link rel="prev" href="sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages.html" title="7.3.7. Mensajes sealert" /><link rel="next" href="chap-Security-Enhanced_Linux-Further_Information.html" title="Capítulo 8. Información Adicional" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><if
 rame id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-Further_Information.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="7.3.8. Permitiendo el Acceso: audit2allow" id="sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.3.8. Permitiendo el Acce
 so: audit2allow</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.3.8. Permitiendo el Acceso: audit2allow</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html" title="7.3. Corrección de Problemas" /><link rel="prev" href="sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages.html" title="7.3.7. Mensajes sealert" /><link rel="next" href="chap-Security-Enhanced_Linux-Further_Information.html" title="Capítulo 8. Información Adicional" /></head><body class="draft toc_embeded "><div id="tocdiv" class="to
 c"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-Further_Information.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="7.3.8. Permitiendo el Acceso: audit2allow" id="sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.3.8. Permitiendo e
 l Acceso: audit2allow</h3></div></div></div><div class="para">
 				No use el ejemplo en esta sección en producción. Se usa sólo para mostrar el uso de <code class="command">audit2allow</code>.
 			</div><div class="para">
-				From the <span class="citerefentry"><span class="refentrytitle">audit2allow</span>(1)</span> manual page: "<code class="command">audit2allow</code> - generate SELinux policy allow rules from logs of denied operations"<sup>[<a id="id2496130" href="#ftn.id2496130" class="footnote">18</a>]</sup>. After analyzing denials as per <a class="xref" href="sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages.html" title="7.3.7. Mensajes sealert">Sección 7.3.7, “Mensajes sealert”</a>, and if no label changes or Booleans allowed access, use <code class="command">audit2allow</code> to create a local policy module. After access is denied by SELinux, running the <code class="command">audit2allow</code> command presents Type Enforcement rules that allow the previously denied access.
+				From the <span class="citerefentry"><span class="refentrytitle">audit2allow</span>(1)</span> manual page: "<code class="command">audit2allow</code> - generate SELinux policy allow rules from logs of denied operations"<sup>[<a id="id723904" href="#ftn.id723904" class="footnote">18</a>]</sup>. After analyzing denials as per <a class="xref" href="sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages.html" title="7.3.7. Mensajes sealert">Sección 7.3.7, “Mensajes sealert”</a>, and if no label changes or Booleans allowed access, use <code class="command">audit2allow</code> to create a local policy module. After access is denied by SELinux, running the <code class="command">audit2allow</code> command presents Type Enforcement rules that allow the previously denied access.
 			</div><div class="para">
 				El siguiente ejemplo muestra el uso de <code class="command">audit2allow</code> para crear un módulo de política:
 			</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
@@ -66,6 +66,6 @@ To make this policy package active, execute:
 
 </pre><div class="para">
 				Refer to Dan Walsh's <a href="http://danwalsh.livejournal.com/24750.html">"Using audit2allow to build policy modules. Revisited."</a> blog entry for further information about using <code class="command">audit2allow</code> to build policy modules.
-			</div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id2496130" href="#id2496130" class="para">18</a>] </sup>
+			</div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id723904" href="#id723904" class="para">18</a>] </sup>
 					From the <span class="citerefentry"><span class="refentrytitle">audit2allow</span>(1)</span> manual page, as shipped with the <span class="package">policycoreutils</span> package in Fedora 13.
 				</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages.html"><strong>Anterior</strong>7.3.7. Mensajes sealert</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-Further_Information.html"><strong>Siguiente</strong>Capítulo 8. Información Adicional</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services.html
index 7709d30..b9fc1b0 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services.html
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.3.3. Páginas de Manual para Servicios</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html" title="7.3. Corrección de Problemas" /><link rel="prev" href="sect-Security-Enhanced_Linux-Fixing_Problems-Possible_Causes_of_Silent_Denials.html" title="7.3.2. Posibles Causas de las Negaciones Silenciosas" /><link rel="next" href="sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains.html" title="7.3.4. Dominios Permisivos" /></head><body cl
 ass="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Fixing_Problems-Possible_Causes_of_Silent_Denials.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="7.3.3. Páginas de Manual para Servicios" id="sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services"><div class="titlepage"><div><div k
 eep-together.within-column="always"><h3 class="title">7.3.3. Páginas de Manual para Servicios</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.3.3. Páginas de Manual para Servicios</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html" title="7.3. Corrección de Problemas" /><link rel="prev" href="sect-Security-Enhanced_Linux-Fixing_Problems-Possible_Causes_of_Silent_Denials.html" title="7.3.2. Posibles Causas de las Negaciones Silenciosas" /><link rel="next" href="sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains.html" title="7.3.4. Dominios Permisivos" /></head><body cl
 ass="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Fixing_Problems-Possible_Causes_of_Silent_Denials.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="7.3.3. Páginas de Manual para Servicios" id="sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services"><div class="titlepage"><div>
 <div keep-together.within-column="always"><h3 class="title">7.3.3. Páginas de Manual para Servicios</h3></div></div></div><div class="para">
 				Las páginas de manual para los servicios conteniendo información valiosa, tal como qué tipo de archivo usar para una situación dada, y los Booleanos para cambiar el acceso que un servicio tiene (tal como <code class="systemitem">httpd</code> para acceder sistemas de archivos NFS). Esta información puede estar en la página de manual estándar o una página de manual con <code class="computeroutput">selinux</code> como prefijo o sufijo.
 			</div><div class="para">
 				For example, the <span class="citerefentry"><span class="refentrytitle">httpd_selinux</span>(8)</span> manual page has information about what file type to use for a given situation, as well as Booleans to allow scripts, sharing files, accessing directories inside user home directories, and so on. Other manual pages with SELinux information for services include:
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains.html
index c39c371..f9ed9bc 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains.html
@@ -1,9 +1,9 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.3.4. Dominios Permisivos</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html" title="7.3. Corrección de Problemas" /><link rel="prev" href="sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services.html" title="7.3.3. Páginas de Manual para Servicios" /><link rel="next" href="sect-Security-Enhanced_Linux-Permissive_Domains-Denials_for_Permissive_Domains.html" title="7.3.4.2. Negaciones para Dominios Permisivos" /></head><body cla
 ss="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Permissive_Domains-Denials_for_Permissive_Domains.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="7.3.4. Dominios Permisivos" id="sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains"><div class="titlepage"><div><div keep-together.wi
 thin-column="always"><h3 class="title">7.3.4. Dominios Permisivos</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.3.4. Dominios Permisivos</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html" title="7.3. Corrección de Problemas" /><link rel="prev" href="sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services.html" title="7.3.3. Páginas de Manual para Servicios" /><link rel="next" href="sect-Security-Enhanced_Linux-Permissive_Domains-Denials_for_Permissive_Domains.html" title="7.3.4.2. Negaciones para Dominios Permisivos" /></head><body cla
 ss="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Permissive_Domains-Denials_for_Permissive_Domains.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="7.3.4. Dominios Permisivos" id="sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains"><div class="titlepage"><div><div keep-toget
 her.within-column="always"><h3 class="title">7.3.4. Dominios Permisivos</h3></div></div></div><div class="para">
 				Cuando SELinux se ejecuta en modo permisivo, SELinux no niega el acceso, sino que las negaciones para las acciones se guardan como si fuera que corre en modo obediente. Previamente, no era posible hacer permisivo un único dominio (recuerde: los procesos corren en dominios). En ciertas situaciones, esto llevó a hacer el sistema permisivo para poder corregir los problemas.
 			</div><div class="para">
-				Fedora 13 introduce los dominios permisivos, donde un administrador puede configurar un único proceso (dominio) para que corra permisivo, en vez de hacer todo el sistema permisivo. Los chequeos de SELinux se realizan igualmente para dominios permisivos; sin embargo, el kernel permite el acceso e informa la negación AVC para situaciones donde SELinux hubiera negado el acceso. Los dominios permisivos están también disponibles en Fedora 9 (con las últimas actualizaciones aplicadas).
+				Fedora 13 includes permissive domains, where an administrator can configure a single process (domain) to run permissive, rather than making the whole system permissive. SELinux checks are still performed for permissive domains; however, the kernel allows access and reports an AVC denial for situations where SELinux would have denied access. Permissive domains are also available in Fedora 9 (with the latest updates applied).
 			</div><div class="para">
 				En el Linux para Empresas de Red Hat 4 y 5, los Booleanos <code class="computeroutput"><em class="replaceable"><code>dominio</code></em>_disable_trans</code> están disponibles para prevenir que una aplicación transicione a un dominio confinado, y por lo tanto, el proceso se ejecute en un dominio no confinado, tal como <code class="computeroutput">initrc_t</code>. Poniendo en 1 tales booleanos pueden causar problemas serios. Por ejemplo, si el Booleano <code class="computeroutput">httpd_disable_trans</code> se pone en 1:
 			</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-Possible_Causes_of_Silent_Denials.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-Possible_Causes_of_Silent_Denials.html
index b1fc608..2c33f53 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-Possible_Causes_of_Silent_Denials.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-Possible_Causes_of_Silent_Denials.html
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.3.2. Posibles Causas de las Negaciones Silenciosas</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html" title="7.3. Corrección de Problemas" /><link rel="prev" href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html" title="7.3. Corrección de Problemas" /><link rel="next" href="sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services.html" title="7.3.3. Páginas de Manual para Servicios" /></head><body class="toc
 _embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="7.3.2. Posibles Causas de las Negaciones Silenciosas" id="sect-Security-Enhanced_Linux-Fixing_Problems-Possible_Causes_of_Silent_Denials"><div class="titlepage"><div><div 
 keep-together.within-column="always"><h3 class="title">7.3.2. Posibles Causas de las Negaciones Silenciosas</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.3.2. Posibles Causas de las Negaciones Silenciosas</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html" title="7.3. Corrección de Problemas" /><link rel="prev" href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html" title="7.3. Corrección de Problemas" /><link rel="next" href="sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services.html" title="7.3.3. Páginas de Manual para Servicios" /></head><body class="dra
 ft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="7.3.2. Posibles Causas de las Negaciones Silenciosas" id="sect-Security-Enhanced_Linux-Fixing_Problems-Possible_Causes_of_Silent_Denials"><div class="titlepage"><div
 ><div keep-together.within-column="always"><h3 class="title">7.3.2. Posibles Causas de las Negaciones Silenciosas</h3></div></div></div><div class="para">
 				En ciertas situaciones, las negaciones AVC pueden no ser guardadas cuando SELinux niega el acceso. Las aplicaciones y las funciones de las bibliotecas del sistema a menudo prueban más accesos que los pedidos para realizar sus tareas. Para mantener el menor privilegio sin llenar los informes de auditoría con negaciones AVC para pruebas sin peligro de las aplicaciones, la política puede silenciar las negaciones AVC sin permitir el uso de reglas <code class="computeroutput">dontaudit</code>. Estas reglas son comúnes en la política estándar. La contraparte de <code class="computeroutput">dontaudit</code> es que, aunque SELinux niega el acceso, los mensajes no se guardan, lo que dificulta resolver el problema.
 			</div><div class="para">
 				Deshabilite temporalmente las reglas <code class="computeroutput">dontaudit</code>, permitiendo que se guarden todas las negaciones, ejecute el siguiente comando como usuario root de Linux:
@@ -21,5 +21,5 @@ dontaudit smbd_t squid_port_t : tcp_socket name_bind ;
 dontaudit smbd_t squid_port_t : udp_socket name_bind ;
 
 </pre><div class="para">
-				Vaya a <a class="xref" href="sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages.html" title="7.3.6. Mensajes Crudos de Auditoría">Sección 7.3.6, “Mensajes Crudos de Auditoría”</a> y a <a class="xref" href="sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages.html" title="7.3.7. Mensajes sealert">Sección 7.3.7, “Mensajes sealert”</a> para información acerca del análisis de las negaciones.
+				Refer to <a class="xref" href="sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages.html" title="7.3.6. Raw Audit Messages">Sección 7.3.6, “Raw Audit Messages”</a> and <a class="xref" href="sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages.html" title="7.3.7. Mensajes sealert">Sección 7.3.7, “Mensajes sealert”</a> for information about analyzing denials.
 			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html"><strong>Anterior</strong>7.3. Corrección de Problemas</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Fixing_Problems-Manual_Pages_for_Services.html"><strong>Siguiente</strong>7.3.3. Páginas de Manual para Servicios</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages.html
index c65930c..ec00e94 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages.html
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.3.6. Mensajes Crudos de Auditoría</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html" title="7.3. Corrección de Problemas" /><link rel="prev" href="sect-Security-Enhanced_Linux-Fixing_Problems-Searching_For_and_Viewing_Denials.html" title="7.3.5. Búsqueda y Revisión de Negaciones" /><link rel="next" href="sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages.html" title="7.3.7. Mensajes sealert" /></head><body class="toc_embeded ">
 <div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Fixing_Problems-Searching_For_and_Viewing_Denials.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="7.3.6. Mensajes Crudos de Auditoría" id="sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages"><div class="titlepage"><div><div keep-together.within-column="alwa
 ys"><h3 class="title">7.3.6. Mensajes Crudos de Auditoría</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.3.6. Raw Audit Messages</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html" title="7.3. Corrección de Problemas" /><link rel="prev" href="sect-Security-Enhanced_Linux-Fixing_Problems-Searching_For_and_Viewing_Denials.html" title="7.3.5. Búsqueda y Revisión de Negaciones" /><link rel="next" href="sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages.html" title="7.3.7. Mensajes sealert" /></head><body class="draft toc_embeded "><div 
 id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Fixing_Problems-Searching_For_and_Viewing_Denials.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="7.3.6. Raw Audit Messages" id="sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="t
 itle">7.3.6. Raw Audit Messages</h3></div></div></div><div class="para">
 				Los mensajes crudos de auditoría se guardan en <code class="filename">/var/log/audit/audit.log</code>. El siguiente es un ejemplo de negación AVC (y su llamada a sistema asociado) que ocurrío cuando el Servidor HTTP Apache (corriendo en el dominio <code class="computeroutput">httpd_t</code>) intentó acceder el <code class="filename">/var/www/html/archivo1</code> (etiquetado con el tipo <code class="computeroutput">samba_share_t</code>):
 			</div><pre class="screen">
 type=AVC msg=audit(1226874073.147:96): avc:  denied  { getattr } for  pid=2465 comm="httpd" path="/var/www/html/file1" dev=dm-0 ino=284133 scontext=unconfined_u:system_r:httpd_t:s0 tcontext=unconfined_u:object_r:samba_share_t:s0 tclass=file
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-Searching_For_and_Viewing_Denials.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-Searching_For_and_Viewing_Denials.html
index 98aab80..999cece 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-Searching_For_and_Viewing_Denials.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-Searching_For_and_Viewing_Denials.html
@@ -1,19 +1,19 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.3.5. Búsqueda y Revisión de Negaciones</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html" title="7.3. Corrección de Problemas" /><link rel="prev" href="sect-Security-Enhanced_Linux-Permissive_Domains-Denials_for_Permissive_Domains.html" title="7.3.4.2. Negaciones para Dominios Permisivos" /><link rel="next" href="sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages.html" title="7.3.6. Mensajes Crudos de Auditoría" /></head><bod
 y class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Permissive_Domains-Denials_for_Permissive_Domains.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="7.3.5. Búsqueda y Revisión de Negaciones" id="sect-Security-Enhanced_Linux-Fixing_Problems-Searching_For_and_Viewing_Denials"><div class="titlepag
 e"><div><div keep-together.within-column="always"><h3 class="title">7.3.5. Búsqueda y Revisión de Negaciones</h3></div></div></div><div class="para">
-				Esta sección asume que los paquetes <span class="package">setroubleshoot</span>, <span class="package">setroubleshoot-server</span>, <span class="package">dbus</span> y <span class="package">audit</span> están instalados, y que los demonios <code class="systemitem">auditd</code>, <code class="systemitem">rsyslogd</code> y <code class="systemitem">setroubleshootd</code> están ejecutándose. Vaya a <a class="xref" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used.html" title="5.2. Qué Archivo Log se usa">Sección 5.2, “Qué Archivo Log se usa”</a> para información sobre cómo iniciar estos demonios. Hay disponibles un número de herramientas para ver las negaciones de SELinux, tales como <code class="command">ausearch</code>, <code class="command">aureport</code> y <code class="command">sealert</code>.
-			</div><div class="formalpara"><h5 class="formalpara">ausearch</h5>
-					The <span class="package">audit</span> package provides <code class="command">ausearch</code>. From the <span class="citerefentry"><span class="refentrytitle">ausearch</span>(8)</span> manual page: "<code class="command">ausearch</code> is a tool that can query the audit daemon logs based for events based on different search criteria"<sup>[<a id="id2269754" href="#ftn.id2269754" class="footnote">15</a>]</sup>. The <code class="command">ausearch</code> tool accesses <code class="filename">/var/log/audit/audit.log</code>, and as such, must be run as the Linux root user:
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.3.5. Búsqueda y Revisión de Negaciones</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html" title="7.3. Corrección de Problemas" /><link rel="prev" href="sect-Security-Enhanced_Linux-Permissive_Domains-Denials_for_Permissive_Domains.html" title="7.3.4.2. Negaciones para Dominios Permisivos" /><link rel="next" href="sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages.html" title="7.3.6. Raw Audit Messages" /></head><body class="dr
 aft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Permissive_Domains-Denials_for_Permissive_Domains.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="7.3.5. Búsqueda y Revisión de Negaciones" id="sect-Security-Enhanced_Linux-Fixing_Problems-Searching_For_and_Viewing_Denials"><div class="titlepage"><d
 iv><div keep-together.within-column="always"><h3 class="title">7.3.5. Búsqueda y Revisión de Negaciones</h3></div></div></div><div class="para">
+				This section assumes the <span class="package">setroubleshoot</span>, <span class="package">setroubleshoot-server</span>, <span class="package">dbus</span> and <span class="package">audit</span> packages are installed, and that the <code class="systemitem">auditd</code>, <code class="systemitem">rsyslogd</code>, and <code class="systemitem">setroubleshootd</code> daemons are running. Refer to <a class="xref" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used.html" title="5.2. Qué Archivo Log se usa">Sección 5.2, “Qué Archivo Log se usa”</a> for information about starting these daemons. A number of tools are available for searching for and viewing SELinux denials, such as <code class="command">ausearch</code>, <code class="command">aureport</code>, and <code class="command">sealert</code>.
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Searching_For_and_Viewing_Denials-ausearch"><h5 class="formalpara">ausearch</h5>
+					The <span class="package">audit</span> package provides <code class="command">ausearch</code>. From the <span class="citerefentry"><span class="refentrytitle">ausearch</span>(8)</span> manual page: "<code class="command">ausearch</code> is a tool that can query the audit daemon logs based for events based on different search criteria"<sup>[<a id="id714518" href="#ftn.id714518" class="footnote">15</a>]</sup>. The <code class="command">ausearch</code> tool accesses <code class="filename">/var/log/audit/audit.log</code>, and as such, must be run as the Linux root user:
 				</div><div class="segmentedlist"><table border="0"><thead><tr class="segtitle"><th>Buscando</th><th>Comando</th></tr></thead><tbody><tr class="seglistitem"><td class="seg">todas las negaciones</td><td class="seg"><code class="command">/sbin/ausearch -m avc</code></td></tr><tr class="seglistitem"><td class="seg">negaciones de hoy</td><td class="seg"><code class="command">/sbin/ausearch -m avc -ts today</code></td></tr><tr class="seglistitem"><td class="seg">negaciones desde los últimos 10 minutos</td><td class="seg"><code class="command">/sbin/ausearch -m avc -ts recent</code></td></tr></tbody></table></div><div class="para">
-				To search for SELinux denials for a particular service, use the <code class="option">-c <em class="replaceable"><code>comm-name</code></em></code> option, where <em class="replaceable"><code>comm-name</code></em> "is the executable’s name"<sup>[<a id="id2269851" href="#ftn.id2269851" class="footnote">16</a>]</sup>, for example, <code class="systemitem">httpd</code> for the Apache HTTP Server, and <code class="systemitem">smbd</code> for Samba:
+				To search for SELinux denials for a particular service, use the <code class="option">-c <em class="replaceable"><code>comm-name</code></em></code> option, where <em class="replaceable"><code>comm-name</code></em> "is the executable’s name"<sup>[<a id="id781704" href="#ftn.id781704" class="footnote">16</a>]</sup>, for example, <code class="systemitem">httpd</code> for the Apache HTTP Server, and <code class="systemitem">smbd</code> for Samba:
 			</div><div class="para">
 				<code class="command">/sbin/ausearch -m avc -c httpd</code>
 			</div><div class="para">
 				<code class="command">/sbin/ausearch -m avc -c smbd</code>
 			</div><div class="para">
 				Refer to the <span class="citerefentry"><span class="refentrytitle">ausearch</span>(8)</span> manual page for further <code class="command">ausearch</code> options.
-			</div><div class="formalpara"><h5 class="formalpara">aureport</h5>
-					The <span class="package">audit</span> package provides <code class="command">aureport</code>. From the <span class="citerefentry"><span class="refentrytitle">aureport</span>(8)</span> manual page: "<code class="command">aureport</code> is a tool that produces summary reports of the audit system logs"<sup>[<a id="id2269956" href="#ftn.id2269956" class="footnote">17</a>]</sup>. The <code class="command">aureport</code> tool accesses <code class="filename">/var/log/audit/audit.log</code>, and as such, must be run as the Linux root user. To view a list of SELinux denials and how often each one occurred, run the <code class="command">aureport -a</code> command. The following is example output that includes two denials:
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Searching_For_and_Viewing_Denials-aureport"><h5 class="formalpara">aureport</h5>
+					The <span class="package">audit</span> package provides <code class="command">aureport</code>. From the <span class="citerefentry"><span class="refentrytitle">aureport</span>(8)</span> manual page: "<code class="command">aureport</code> is a tool that produces summary reports of the audit system logs"<sup>[<a id="id706929" href="#ftn.id706929" class="footnote">17</a>]</sup>. The <code class="command">aureport</code> tool accesses <code class="filename">/var/log/audit/audit.log</code>, and as such, must be run as the Linux root user. To view a list of SELinux denials and how often each one occurred, run the <code class="command">aureport -a</code> command. The following is example output that includes two denials:
 				</div><pre class="screen">
 # /sbin/aureport -a
 
@@ -26,7 +26,7 @@ AVC Report
 
 </pre><div class="para">
 				Refer to the <span class="citerefentry"><span class="refentrytitle">aureport</span>(8)</span> manual page for further <code class="command">aureport</code> options.
-			</div><div class="formalpara"><h5 class="formalpara">sealert</h5>
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Searching_For_and_Viewing_Denials-sealert"><h5 class="formalpara">sealert</h5>
 					El paquete <span class="package">setroubleshoot-server</span> provee <code class="command">sealert</code>, que lee los mensajes de negación traducidos por <span class="package">setroubleshoot-server</span>. A las negaciones se le asignan IDs, como se ve en <code class="filename">/var/log/messages</code>. El siguiente es un ejemplo de negación en <code class="filename">messages</code>:
 				</div><pre class="screen">
 setroubleshoot: SELinux is preventing httpd (httpd_t) "getattr" to /var/www/html/file1 (samba_share_t). For complete SELinux messages. run sealert -l 84e0b04d-d0ad-4347-8317-22e74f6cd020
@@ -43,10 +43,10 @@ setroubleshoot: SELinux is preventing httpd (httpd_t) "getattr" to /var/www/html
 						As the Linux root user, run the <code class="command">sealert -a /var/log/audit/audit.log -H &gt; audit.html</code> command to create a HTML version of the <code class="command">sealert</code> analysis, as seen with the <code class="command">sealert</code> GUI.
 					</div></li></ul></div><div class="para">
 				Refer to the <span class="citerefentry"><span class="refentrytitle">sealert</span>(8)</span> manual page for further <code class="command">sealert</code> options.
-			</div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id2269754" href="#id2269754" class="para">15</a>] </sup>
+			</div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id714518" href="#id714518" class="para">15</a>] </sup>
 						From the <span class="citerefentry"><span class="refentrytitle">ausearch</span>(8)</span> manual page, as shipped with the <span class="package">audit</span> package in Fedora 13.
-					</p></div><div class="footnote"><p><sup>[<a id="ftn.id2269851" href="#id2269851" class="para">16</a>] </sup>
+					</p></div><div class="footnote"><p><sup>[<a id="ftn.id781704" href="#id781704" class="para">16</a>] </sup>
 					From the <span class="citerefentry"><span class="refentrytitle">ausearch</span>(8)</span> manual page, as shipped with the <span class="package">audit</span> package in Fedora 13.
-				</p></div><div class="footnote"><p><sup>[<a id="ftn.id2269956" href="#id2269956" class="para">17</a>] </sup>
+				</p></div><div class="footnote"><p><sup>[<a id="ftn.id706929" href="#id706929" class="para">17</a>] </sup>
 						From the <span class="citerefentry"><span class="refentrytitle">aureport</span>(8)</span> manual page, as shipped with the <span class="package">audit</span> package in Fedora 13.
-					</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Permissive_Domains-Denials_for_Permissive_Domains.html"><strong>Anterior</strong>7.3.4.2. Negaciones para Dominios Permisivos</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages.html"><strong>Siguiente</strong>7.3.6. Mensajes Crudos de Auditoría</a></li></ul></body></html>
+					</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Permissive_Domains-Denials_for_Permissive_Domains.html"><strong>Anterior</strong>7.3.4.2. Negaciones para Dominios Permisivos</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages.html"><strong>Siguiente</strong>7.3.6. Raw Audit Messages</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages.html
index 63aa301..f82d3ce 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages.html
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.3.7. Mensajes sealert</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html" title="7.3. Corrección de Problemas" /><link rel="prev" href="sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages.html" title="7.3.6. Mensajes Crudos de Auditoría" /><link rel="next" href="sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow.html" title="7.3.8. Permitiendo el Acceso: audit2allow" /></head><body class="toc_embeded "><div 
 id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="7.3.7. Mensajes sealert" id="sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.
 3.7. Mensajes sealert</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.3.7. Mensajes sealert</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html" title="7.3. Corrección de Problemas" /><link rel="prev" href="sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages.html" title="7.3.6. Raw Audit Messages" /><link rel="next" href="sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow.html" title="7.3.8. Permitiendo el Acceso: audit2allow" /></head><body class="draft toc_embeded "><div id="t
 ocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="7.3.7. Mensajes sealert" id="sect-Security-Enhanced_Linux-Fixing_Problems-sealert_Messages"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.3.7. 
 Mensajes sealert</h3></div></div></div><div class="para">
 				Las negaciones tienen IDs asignados, como se ve en <code class="filename">/var/log/messages</code>. El siguiente es un ejemplo de negación AVC (guardado en <code class="filename">messages</code>) que ocurrió cuando el Servidor HTTP Apache (corriendo en el dominio <code class="computeroutput">httpd_t</code> domain) intentó acceder el <code class="filename">/var/www/html/archivo1</code> (etiquetado con el tipo <code class="computeroutput">samba_share_t</code>):
 			</div><pre class="screen">
 <em class="replaceable"><code>hostname</code></em> setroubleshoot: SELinux is preventing httpd (httpd_t) "getattr" to /var/www/html/file1 (samba_share_t). For complete SELinux messages. run sealert -l 84e0b04d-d0ad-4347-8317-22e74f6cd020
@@ -73,7 +73,7 @@ node=<em class="replaceable"><code>hostname</code></em> type=SYSCALL msg=audit(1
 						</div></dd><dt><span class="term">Comando para Corregir</span></dt><dd><div class="para">
 							Un comando sugerido para permitir el acceso y resolver la negación. En este ejemplo, se dá el comando para cambiar el tipo del <code class="filename">archivo1</code> a <code class="computeroutput">public_content_t</code>, que es accesible por el Servidor HTTP Apache y por Samba.
 						</div></dd><dt><span class="term">Información Adicional</span></dt><dd><div class="para">
-							Información que es útil en los informes de errores, como el nombre de paquete de política y la versión (<code class="computeroutput">selinux-policy-3.5.13-11.fc12</code>), pero que no puede ser de ayuda para resolver por qué ocurrió la negación.
-						</div></dd><dt><span class="term">Mensajes Crudos de Auditoría</span></dt><dd><div class="para">
-							Los mensajes crudos de auditoría de <code class="filename">/var/log/audit/audit.log</code> que son asociados con la negación. Vaya a <a class="xref" href="sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages.html" title="7.3.6. Mensajes Crudos de Auditoría">Sección 7.3.6, “Mensajes Crudos de Auditoría”</a> para información acerca de cada ítem en la negación AVC.
-						</div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages.html"><strong>Anterior</strong>7.3.6. Mensajes Crudos de Auditoría</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow.html"><strong>Siguiente</strong>7.3.8. Permitiendo el Acceso: audit2allow</a></li></ul></body></html>
+							Information that is useful in bug reports, such as the policy package name and version (<code class="computeroutput">selinux-policy-3.5.13-11.fc12</code>), but may not help towards solving why the denial occurred.
+						</div></dd><dt><span class="term">Raw Audit Messages</span></dt><dd><div class="para">
+							The raw audit messages from <code class="filename">/var/log/audit/audit.log</code> that are associated with the denial. Refer to <a class="xref" href="sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages.html" title="7.3.6. Raw Audit Messages">Sección 7.3.6, “Raw Audit Messages”</a> for information about each item in the AVC denial.
+						</div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Fixing_Problems-Raw_Audit_Messages.html"><strong>Anterior</strong>7.3.6. Raw Audit Messages</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow.html"><strong>Siguiente</strong>7.3.8. Permitiendo el Acceso: audit2allow</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Further_Information-Other_Resources.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Further_Information-Other_Resources.html
index 60adcd0..a5c0403 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Further_Information-Other_Resources.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Further_Information-Other_Resources.html
@@ -1,56 +1,56 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.2. Otros Recursos</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Further_Information.html" title="Capítulo 8. Información Adicional" /><link rel="prev" href="chap-Security-Enhanced_Linux-Further_Information.html" title="Capítulo 8. Información Adicional" /><link rel="next" href="appe-Security-Enhanced_Linux-Revision_History.html" title="Apéndice A. Historia de Revisiones" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" s
 rc="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-Further_Information.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="appe-Security-Enhanced_Linux-Revision_History.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="8.2. Otros Recursos" id="sect-Security-Enhanced_Linux-Further_Information-Other_Resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">8.2. Otros Recursos</h2></div></div></div><div class="formalpara"><h5 class="formalpara">La Agencia de S
 eguridad Nacional (NSA)</h5>
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.2. Other Resources</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Further_Information.html" title="Capítulo 8. Información Adicional" /><link rel="prev" href="chap-Security-Enhanced_Linux-Further_Information.html" title="Capítulo 8. Información Adicional" /><link rel="next" href="appe-Security-Enhanced_Linux-Revision_History.html" title="Apéndice A. Revision History" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" 
 src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-Further_Information.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="appe-Security-Enhanced_Linux-Revision_History.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="8.2. Other Resources" id="sect-Security-Enhanced_Linux-Further_Information-Other_Resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">8.2. Other Resources</h2></div></div></div><div class="formalpara" id="form-Security-Enhanced_Linux-Fu
 rther_Information-The_National_Security_Agency_NSA"><h5 class="formalpara">La Agencia de Seguridad Nacional (NSA)</h5>
 				De la página <a href="http://www.nsa.gov/research/selinux/contrib.shtml">Contribuyentes de SELinux</a>:
 			</div><div class="para">
 			<span class="emphasis"><em>Researchers in NSA's National Information Assurance Research Laboratory (NIARL) designed and implemented flexible mandatory access controls in the major subsystems of the Linux kernel and implemented the new operating system components provided by the Flask architecture, namely the security server and the access vector cache. The NSA researchers reworked the LSM-based SELinux for inclusion in Linux 2.6. NSA has also led the development of similar controls for the X Window System (XACE/XSELinux) and for Xen (XSM/Flask).</em></span>
 		</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-					El sitio web principal de SELinux: <a href="http://www.nsa.gov/research/selinux/index.shtml">http://www.nsa.gov/research/selinux/index.shtml</a>.
+					Main SELinux website: <a href="http://www.nsa.gov/research/selinux/index.shtml">http://www.nsa.gov/research/selinux/index.shtml</a>.
 				</div></li><li class="listitem"><div class="para">
-					Documentación de SELinux: <a href="http://www.nsa.gov/research/selinux/docs.shtml">http://www.nsa.gov/research/selinux/docs.shtml</a>.
+					SELinux documentation: <a href="http://www.nsa.gov/research/selinux/docs.shtml">http://www.nsa.gov/research/selinux/docs.shtml</a>.
 				</div></li><li class="listitem"><div class="para">
-					Trasfondo de SELinux: <a href="http://www.nsa.gov/research/selinux/background.shtml">http://www.nsa.gov/research/selinux/background.shtml</a>.
-				</div></li></ul></div><div class="formalpara"><h5 class="formalpara">Tecnología de Tresys</h5>
+					SELinux background: <a href="http://www.nsa.gov/research/selinux/background.shtml">http://www.nsa.gov/research/selinux/background.shtml</a>.
+				</div></li></ul></div><div class="formalpara" id="form-Security-Enhanced_Linux-Further_Information-Tresys_Technology"><h5 class="formalpara">Tecnología de Tresys</h5>
 				<a href="http://www.tresys.com/">Tresys Technology</a> son los desarrolladores de:
 			</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
 					<a href="http://userspace.selinuxproject.org/trac/">Herramientas y bibliotecas en el espacio del usuario para SELinux</a>.
 				</div></li><li class="listitem"><div class="para">
 					<a href="http://oss.tresys.com/projects/refpolicy">Política de Referencia de SELinux</a>.
-				</div></li></ul></div><div class="formalpara"><h5 class="formalpara">Noticias de SELinux</h5>
+				</div></li></ul></div><div class="formalpara" id="form-Security-Enhanced_Linux-Further_Information-SELinux_News"><h5 class="formalpara">Noticias de SELinux</h5>
 				<div class="itemizedlist"><ul><li class="listitem"><div class="para">
-							Noticias: <a href="http://selinuxnews.org/wp/">http://selinuxnews.org/wp/</a>.
+							News: <a href="http://selinuxnews.org/wp/">http://selinuxnews.org/wp/</a>.
 						</div></li><li class="listitem"><div class="para">
-							Planeta SELinux (blogs): <a href="http://selinuxnews.org/planet/">http://selinuxnews.org/planet/</a>.
+							Planet SELinux (blogs): <a href="http://selinuxnews.org/planet/">http://selinuxnews.org/planet/</a>.
 						</div></li></ul></div>
 
-			</div><div class="formalpara"><h5 class="formalpara">Wiki del Proyecto SELinux</h5>
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Further_Information-SELinux_Project_Wiki"><h5 class="formalpara">Wiki del Proyecto SELinux</h5>
 				<div class="itemizedlist"><ul><li class="listitem"><div class="para">
-							Página principal: <a href="http://selinuxproject.org/page/Main_Page">http://selinuxproject.org/page/Main_Page</a>.
+							Main page: <a href="http://selinuxproject.org/page/Main_Page">http://selinuxproject.org/page/Main_Page</a>.
 						</div></li><li class="listitem"><div class="para">
-							Recursos del usuario, incluyendo enlaces a documentación, listas de correo, sitios web y herramientas: <a href="http://selinuxproject.org/page/User_Resources">http://selinuxproject.org/page/User_Resources</a>.
+							User resources, including links to documentation, mailing lists, websites, and tools: <a href="http://selinuxproject.org/page/User_Resources">http://selinuxproject.org/page/User_Resources</a>.
 						</div></li></ul></div>
 
-			</div><div class="formalpara"><h5 class="formalpara">Linux para Empresas de Red Hat</h5>
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Further_Information-Red_Hat_Enterprise_Linux"><h5 class="formalpara">Linux para Empresas de Red Hat</h5>
 				<div class="itemizedlist"><ul><li class="listitem"><div class="para">
 							La <a href="http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.2/html/Deployment_Guide/index.html">Guía de Despliegue del Linux para Empresas de Red Hat</a> contiene una sección de <a href="http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.2/html/Deployment_Guide/selg-chapter-0054.html">Referencias</a> SELinux, que tiene enlaces a tutoriales de SELinux, información general y la tecnología detrás de SELinux.
 						</div></li><li class="listitem"><div class="para">
 							La <a href="http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/selinux-guide/index.html">Guía de SELinux del Linux para Empresas de Red Hat 4</a>.
 						</div></li></ul></div>
 
-			</div><div class="formalpara"><h5 class="formalpara">Fedora</h5>
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Further_Information-Fedora"><h5 class="formalpara">Fedora</h5>
 				<div class="itemizedlist"><ul><li class="listitem"><div class="para">
-							Página principal: <a href="http://fedoraproject.org/wiki/SELinux">http://fedoraproject.org/wiki/SELinux</a>.
+							Main page: <a href="http://fedoraproject.org/wiki/SELinux">http://fedoraproject.org/wiki/SELinux</a>.
 						</div></li><li class="listitem"><div class="para">
-							Resolución de problemas: <a href="http://fedoraproject.org/wiki/SELinux/Troubleshooting">http://fedoraproject.org/wiki/SELinux/Troubleshooting</a>.
+							Troubleshooting: <a href="http://fedoraproject.org/wiki/SELinux/Troubleshooting">http://fedoraproject.org/wiki/SELinux/Troubleshooting</a>.
 						</div></li><li class="listitem"><div class="para">
-							Fedora SELinux FAQ: <a href="http://docs.fedoraproject.org/selinux-faq/">http://docs.fedoraproject.org/selinux-faq/</a>.
+							Fedora Core 5 SELinux FAQ: <a href="http://docs.fedoraproject.org/selinux-faq-fc5/">http://docs.fedoraproject.org/selinux-faq-fc5/</a>.
 						</div></li><li class="listitem"><div class="para">
-							Guía de Administración de Servicios Confinados de SELinux: <a href="http://docs.fedoraproject.org/selinux-managing-confined-services-guide/">http://docs.fedoraproject.org/selinux-managing-confined-services-guide/</a>
+							SELinux Managing Confined Services Guide: <a href="http://docs.fedoraproject.org/selinux-managing-confined-services-guide/">http://docs.fedoraproject.org/selinux-managing-confined-services-guide/</a>
 						</div></li></ul></div>
 
-			</div><div class="formalpara"><h5 class="formalpara">Las Preguntas Frecuentes No Oficiales de SELinux</h5>
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Further_Information-The_UnOfficial_SELinux_FAQ"><h5 class="formalpara">Las Preguntas Frecuentes No Oficiales de SELinux</h5>
 				<a href="http://www.crypt.gen.nz/selinux/faq.html">http://www.crypt.gen.nz/selinux/faq.html</a>
-			</div><div class="formalpara"><h5 class="formalpara">IRC</h5>
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Further_Information-IRC"><h5 class="formalpara">IRC</h5>
 				En <a href="http://freenode.net/">Freenode</a>:
 			</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
 					#selinux
@@ -58,4 +58,4 @@
 					#fedora-selinux
 				</div></li><li class="listitem"><div class="para">
 					#security
-				</div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-Further_Information.html"><strong>Anterior</strong>Capítulo 8. Información Adicional</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="appe-Security-Enhanced_Linux-Revision_History.html"><strong>Siguiente</strong>Apéndice A. Historia de Revisiones</a></li></ul></body></html>
+				</div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-Further_Information.html"><strong>Anterior</strong>Capítulo 8. Información Adicional</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="appe-Security-Enhanced_Linux-Revision_History.html"><strong>Siguiente</strong>Apéndice A. Revision History</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Introduction-Examples.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Introduction-Examples.html
index 0f5821d..053eca5 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Introduction-Examples.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Introduction-Examples.html
@@ -1,27 +1,27 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2. Ejemplos</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Introduction.html" title="Capítulo 2. Introducción" /><link rel="prev" href="chap-Security-Enhanced_Linux-Introduction.html" title="Capítulo 2. Introducción" /><link rel="next" href="sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture.html" title="2.3. Arquitectura de SELinux" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">Th
 is is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-Introduction.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="2.2. Ejemplos" id="sect-Security-Enhanced_Linux-Introduction-Examples"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.2. Ejemplos</h2></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2. Ejemplos</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Introduction.html" title="Capítulo 2. Introducción" /><link rel="prev" href="chap-Security-Enhanced_Linux-Introduction.html" title="Capítulo 2. Introducción" /><link rel="next" href="sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture.html" title="2.3. Arquitectura de SELinux" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.ht
 ml">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-Introduction.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="2.2. Ejemplos" id="sect-Security-Enhanced_Linux-Introduction-Examples"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.2. Ejemplos</h2></div></div></div><div class="para">
 			Los siguientes ejemplos demuestran cómo SELinux aumenta la seguridad:
 		</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-					The default action is deny. If a specific SELinux policy rule does not exist to allow access, such as for a process opening a file, access is denied.
+					The default action is deny. If an SELinux policy rule does not exist to allow access, such as for a process opening a file, access is denied.
 				</div></li><li class="listitem"><div class="para">
-					SELinux puede confinar a usuarios Linux. Existe un número de usuarios SELinux confinados. Los usuarios Linux se pueden mapear a usuarios SELinux para sacar ventaja de los usuarios SELinux confinados. Por ejemplo, mapear un usario Linux al usuario SELinux user_u, resulta en un usuario Linux que no puede ejecutar (a menos que se configure de otra forma) aplicaciones con el ID del usuario (setuid), tales como <code class="command">sudo</code> y <code class="command">su</code>, así como previene la ejecución de archivos y aplicaciones en sus directorios de inicio (home)- si se configura, esto evita que los usuarios ejecuten archivos maliciosos desde sus directorios de inicio.
+					SELinux can confine Linux users. A number of confined SELinux users exist in SELinux policy. Linux users can be mapped to confined SELinux users to take advantage of the security rules and mechanisms applied to them. For example, mapping a Linux user to the SELinux user_u user, results in a Linux user that is not able to run (unless configured otherwise) set user ID (setuid) applications, such as <code class="command">sudo</code> and <code class="command">su</code>, as well as preventing them from executing files and applications in their home directory - if configured, this prevents users from executing malicious files from their home directories.
 				</div></li><li class="listitem"><div class="para">
-					Se usa separación de procesos. Los procesos que corren en sus propios dominios, previenen que estos accedan a archivos usados por otros procesos, así como el acceso a otros procesos. Por ejemplo, cuando se ejecuta SELinux, a menos que se configure de otra forma, un atacante no puede comprometer un servidor Samba, y luego usar ese servidor Samba para leer y escribir archivos usados por otros procesos, tales como las bases de datos usadas por <span class="trademark">MySQL</span>®.
+					Process separation is used. Processes run in their own domains, preventing processes from accessing files used by other processes, as well as preventing processes from accessing other processes. For example, when running SELinux, unless otherwise configured, an attacker can not compromise a Samba server, and then use that Samba server as an attack vector to read and write to files used by other processes, such as databases used by <span class="trademark">MySQL</span>®.
 				</div></li><li class="listitem"><div class="para">
-					SELinux helps limit the damage made by configuration mistakes. <a href="http://en.wikipedia.org/wiki/Domain_Name_System">Domain Name System (DNS)</a> servers often replicate information between each other in what is known as a zone transfer. Attackers can use zone transfers to update DNS servers with false information. When running the <a href="https://www.isc.org/software/bind">Berkeley Internet Name Daemon (BIND)</a> as a DNS server in Fedora, even if an administrator forgets to limit which servers can perform a zone transfer, the default SELinux policy prevents zone files <sup>[<a id="id2075427" href="#ftn.id2075427" class="footnote">3</a>]</sup> from being updated via zone transfers, by the BIND <code class="systemitem">named</code> daemon itself, and by other processes.
+					SELinux helps limit the damage made by configuration mistakes. <a href="http://en.wikipedia.org/wiki/Domain_Name_System">Domain Name System (DNS)</a> servers often replicate information between each other in what is known as a zone transfer. Attackers can use zone transfers to update DNS servers with false information. When running the <a href="https://www.isc.org/software/bind">Berkeley Internet Name Domain (BIND)</a> as a DNS server in Fedora, even if an administrator forgets to limit which servers can perform a zone transfer, the default SELinux policy prevents zone files <sup>[<a id="id756772" href="#ftn.id756772" class="footnote">3</a>]</sup> from being updated via zone transfers, by the BIND <code class="systemitem">named</code> daemon itself, and by other processes.
 				</div></li><li class="listitem"><div class="para">
-					Refer to the <a href="http://www.redhatmagazine.com/"><span class="trademark">Red Hat</span>® Magazine</a> article, <a href="http://www.redhatmagazine.com/2008/02/26/risk-report-three-years-of-red-hat-enterprise-linux-4/">Risk report: Three years of Red Hat Enterprise Linux 4</a><sup>[<a id="id2075467" href="#ftn.id2075467" class="footnote">4</a>]</sup>, for exploits that were restricted due to the default SELinux targeted policy in <span class="trademark">Red Hat</span>® Enterprise <span class="trademark">Linux</span>® 4.
+					Refer to the <a href="http://www.redhatmagazine.com/"><span class="trademark">Red Hat</span>® Magazine</a> article, <a href="http://www.redhatmagazine.com/2008/02/26/risk-report-three-years-of-red-hat-enterprise-linux-4/">Risk report: Three years of Red Hat Enterprise Linux 4</a><sup>[<a id="id756807" href="#ftn.id756807" class="footnote">4</a>]</sup>, for exploits that were restricted due to the default SELinux targeted policy in <span class="trademark">Red Hat</span>® Enterprise <span class="trademark">Linux</span>® 4.
 				</div></li><li class="listitem"><div class="para">
-					Refer to the <a href="http://www.linuxworld.com">LinuxWorld.com</a> article, <a href="http://www.linuxworld.com/news/2008/022408-selinux.html?page=1">A seatbelt for server software: SELinux blocks real-world exploits</a><sup>[<a id="id2075515" href="#ftn.id2075515" class="footnote">5</a>]</sup>, for background information about SELinux, and information about various exploits that SELinux has prevented.
+					Refer to the <a href="http://www.linuxworld.com">LinuxWorld.com</a> article, <a href="http://www.linuxworld.com/news/2008/022408-selinux.html?page=1">A seatbelt for server software: SELinux blocks real-world exploits</a><sup>[<a id="id1220418" href="#ftn.id1220418" class="footnote">5</a>]</sup>, for background information about SELinux, and information about various exploits that SELinux has prevented.
 				</div></li><li class="listitem"><div class="para">
 					Refer to James Morris's <a href="http://james-morris.livejournal.com/25421.html">SELinux mitigates remote root vulnerability in OpenPegasus</a> blog post for information about an exploit in <a href="http://www.openpegasus.org/">OpenPegasus</a> that was mitigated by SELinux as shipped with Red Hat Enterprise Linux 4 and 5.
 				</div></li></ul></div><div class="para">
 			El sitio web de <a href="http://www.tresys.com/">Tresys Technology</a> tiene una sección de <a href="http://www.tresys.com/innovation.php">Noticias de Migración a SELinux</a> (en la parte derecha), que lista los ataques recientes que fueron mitigados o prevenidos por SELinux.
-		</div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id2075427" href="#id2075427" class="para">3</a>] </sup>
+		</div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id756772" href="#id756772" class="para">3</a>] </sup>
 						Text files that include information, such as hostname to IP address mappings, that are used by DNS servers.
-					</p></div><div class="footnote"><p><sup>[<a id="ftn.id2075467" href="#id2075467" class="para">4</a>] </sup>
+					</p></div><div class="footnote"><p><sup>[<a id="ftn.id756807" href="#id756807" class="para">4</a>] </sup>
 						Cox, Mark. "Risk report: Three years of Red Hat Enterprise Linux 4". Published 26 February 2008. Accessed 27 August 2009: <a href="http://www.redhatmagazine.com/2008/02/26/risk-report-three-years-of-red-hat-enterprise-linux-4/">http://www.redhatmagazine.com/2008/02/26/risk-report-three-years-of-red-hat-enterprise-linux-4/</a>.
-					</p></div><div class="footnote"><p><sup>[<a id="ftn.id2075515" href="#id2075515" class="para">5</a>] </sup>
+					</p></div><div class="footnote"><p><sup>[<a id="ftn.id1220418" href="#id1220418" class="para">5</a>] </sup>
 						Marti, Don. "A seatbelt for server software: SELinux blocks real-world exploits". Published 24 February 2008. Accessed 27 August 2009: <a href="http://www.linuxworld.com/news/2008/022408-selinux.html?page=1">http://www.linuxworld.com/news/2008/022408-selinux.html?page=1</a>.
 					</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-Introduction.html"><strong>Anterior</strong>Capítulo 2. Introducción</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture.html"><strong>Siguiente</strong>2.3. Arquitectura de SELinux</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture.html
index b7b6f7c..c53a8c1 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture.html
@@ -1,7 +1,7 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.3. Arquitectura de SELinux</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Introduction.html" title="Capítulo 2. Introducción" /><link rel="prev" href="sect-Security-Enhanced_Linux-Introduction-Examples.html" title="2.2. Ejemplos" /><link rel="next" href="sect-Security-Enhanced_Linux-Introduction-SELinux_on_Other_Operating_Systems.html" title="2.4. SELinux en otros Sistemas Operativos" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" cla
 ss="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Introduction-Examples.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Introduction-SELinux_on_Other_Operating_Systems.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="2.3. Arquitectura de SELinux" id="sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.3. Arquitectura de SELinux</h2></div></div></div><di
 v class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.3. Arquitectura de SELinux</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Introduction.html" title="Capítulo 2. Introducción" /><link rel="prev" href="sect-Security-Enhanced_Linux-Introduction-Examples.html" title="2.2. Ejemplos" /><link rel="next" href="sect-Security-Enhanced_Linux-Introduction-SELinux_on_Other_Operating_Systems.html" title="2.4. SELinux en otros Sistemas Operativos" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocfram
 e" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Introduction-Examples.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Introduction-SELinux_on_Other_Operating_Systems.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="2.3. Arquitectura de SELinux" id="sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.3. Arquitectura de SELinux</h2></div></div></d
 iv><div class="para">
 			SELinux es un módulo de seguridad de Linux que se construye dentro del kernel de Linux. SELinux se maneja por reglas de políticas cargables. Cuando un acceso de seguridad relevante se lleva a cabo, tal como un proceso que trata de abrir un archivo, la operación es interceptada por SELinux en el kernel. Si una regla de política de SELinux permite la operación, continúa, sino, la operación se bloquea y el proceso recibe un error.
 		</div><div class="para">
-			Las decisiones de SELinux, tales como permitir o negar accesos, son cacheadas. Este caché se conoce como Caché Vector de Acceso (AVC). Las decisiones de cacheado disminuye la necesidad de que las reglas de políticas de SELinux sean chequeadas muy a menudo, lo que mejora la performance. Las reglas de políticas de SELinux no tienen efecto si las reglas DAC niegan el acceso primero.
+			SELinux decisions, such as allowing or disallowing access, are cached. This cache is known as the Access Vector Cache (AVC). Caching decisions decreases how often SELinux policy rules need to be checked, which increases performance. Remember that SELinux policy rules have no effect if DAC rules deny access first.
 		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Introduction-Examples.html"><strong>Anterior</strong>2.2. Ejemplos</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Introduction-SELinux_on_Other_Operating_Systems.html"><strong>Siguiente</strong>2.4. SELinux en otros Sistemas Operativos</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Introduction-SELinux_on_Other_Operating_Systems.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Introduction-SELinux_on_Other_Operating_Systems.html
index a78a9bd..f4ebb5a 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Introduction-SELinux_on_Other_Operating_Systems.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Introduction-SELinux_on_Other_Operating_Systems.html
@@ -1,9 +1,9 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.4. SELinux en otros Sistemas Operativos</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Introduction.html" title="Capítulo 2. Introducción" /><link rel="prev" href="sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture.html" title="2.3. Arquitectura de SELinux" /><link rel="next" href="chap-Security-Enhanced_Linux-SELinux_Contexts.html" title="Capítulo 3. Contextos de SELinux" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" cl
 ass="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-SELinux_Contexts.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="2.4. SELinux en otros Sistemas Operativos" id="sect-Security-Enhanced_Linux-Introduction-SELinux_on_Other_Operating_Systems"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.4. SELinux en otros Sistemas Operativos</h2
 ></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.4. SELinux en otros Sistemas Operativos</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Introduction.html" title="Capítulo 2. Introducción" /><link rel="prev" href="sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture.html" title="2.3. Arquitectura de SELinux" /><link rel="next" href="chap-Security-Enhanced_Linux-SELinux_Contexts.html" title="Capítulo 3. Contextos de SELinux" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocfra
 me" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-SELinux_Contexts.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="2.4. SELinux en otros Sistemas Operativos" id="sect-Security-Enhanced_Linux-Introduction-SELinux_on_Other_Operating_Systems"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.4. SELinux en otros Sistemas Operativ
 os</h2></div></div></div><div class="para">
 			Vaya a la siguiente información sobre cómo correr SELinux en sistemas operativos:
 		</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-					Gentoo endurecido: <a href="http://www.gentoo.org/proj/en/hardened/selinux/selinux-handbook.xml">http://www.gentoo.org/proj/en/hardened/selinux/selinux-handbook.xml</a>.
+					Hardened Gentoo: <a href="http://www.gentoo.org/proj/en/hardened/selinux/selinux-handbook.xml">http://www.gentoo.org/proj/en/hardened/selinux/selinux-handbook.xml</a>.
 				</div></li><li class="listitem"><div class="para">
 					Debian: <a href="http://wiki.debian.org/SELinux">http://wiki.debian.org/SELinux</a>.
 				</div></li><li class="listitem"><div class="para">
@@ -11,5 +11,5 @@
 				</div></li><li class="listitem"><div class="para">
 					Linux para Empresas de Red Hat: <a href="http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.2/html/Deployment_Guide/selg-overview.html">Guía de Despliegue del Linux para Empresas de Red Hat</a> y la <a href="http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/selinux-guide/">Guía de SELinux para el Linux para Empresas de Red Hat</a>.
 				</div></li><li class="listitem"><div class="para">
-					Fedora: <a href="http://fedoraproject.org/wiki/SELinux">http://fedoraproject.org/wiki/SELinux</a> y el <a href="http://docs.fedoraproject.org/selinux-faq-fc5/">FAQ de SELinux de Fedora Core 5</a>.
+					Fedora: <a href="http://fedoraproject.org/wiki/SELinux">http://fedoraproject.org/wiki/SELinux</a> and the <a href="http://docs.fedoraproject.org/selinux-faq-fc5/">Fedora Core 5 SELinux FAQ</a>.
 				</div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Introduction-SELinux_Architecture.html"><strong>Anterior</strong>2.3. Arquitectura de SELinux</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-SELinux_Contexts.html"><strong>Siguiente</strong>Capítulo 3. Contextos de SELinux</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_star.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_star.html
index 1321c97..f9583f3 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_star.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_star.html
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.10.5. Archivando archivos con tar</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html" title="5.10. Mantención de las Etiquetas de SELinux" /><link rel="prev" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_tar.html" title="5.10.4. Archivando archivos con tar" /><link rel="next" href="chap-Security-Enhanced_Linux-Confining_Users.html" title="Capítulo 6. Confinando a los Usuarios" /></head><
 body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_tar.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-Confining_Users.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.10.5. Archivando archivos con tar" id="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_star"><div class="titlepage"><div><div kee
 p-together.within-column="always"><h3 class="title">5.10.5. Archivando archivos con tar</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.10.5. Archivando archivos con tar</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html" title="5.10. Mantención de las Etiquetas de SELinux" /><link rel="prev" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_tar.html" title="5.10.4. Archivando archivos con tar" /><link rel="next" href="chap-Security-Enhanced_Linux-Confining_Users.html" title="Capítulo 6. Confinando a los Usuarios" /></head><
 body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_tar.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-Confining_Users.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.10.5. Archivando archivos con tar" id="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_star"><div class="titlepage"><div><d
 iv keep-together.within-column="always"><h3 class="title">5.10.5. Archivando archivos con tar</h3></div></div></div><div class="para">
 				<code class="command">star</code> no retiene los atributos extendidos por defecto. Dado que los contextos SELinux se almacenan en los atributos extendidos, los contextos se pueden perder cuando se crean esos archivos. Use <code class="command">star -xattr -H=exustar</code> para crear archivos que retengan los contextos. El paquete <span class="package">star</span> no se instala por defecto. Para instalar <code class="command">star</code>, ejecute el comando <code class="command">yum install star</code> como usuario root de Linux.
 			</div><div class="para">
 				El siguiente ejemplo muestra la creación de un archivo Star que retiene los contextos SELinux:
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_tar.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_tar.html
index cb42eff..28faca6 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_tar.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_tar.html
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.10.4. Archivando archivos con tar</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html" title="5.10. Mantención de las Etiquetas de SELinux" /><link rel="prev" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context.html" title="5.10.3. Chequeando el Contexto SELinux Predeterminado" /><link rel="next" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_
 star.html" title="5.10.5. Archivando archivos con tar" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_star.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.10.4. Archivando archivos con tar" id="sect-
 Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_tar"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.10.4. Archivando archivos con tar</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.10.4. Archivando archivos con tar</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html" title="5.10. Mantención de las Etiquetas de SELinux" /><link rel="prev" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context.html" title="5.10.3. Chequeando el Contexto SELinux Predeterminado" /><link rel="next" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_
 star.html" title="5.10.5. Archivando archivos con tar" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_star.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.10.4. Archivando archivos con tar" id=
 "sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_tar"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.10.4. Archivando archivos con tar</h3></div></div></div><div class="para">
 				<code class="command">tar</code> no retiene los atributos extendidos por defecto. Dado que los contextos SELinux se almacenan en los atributos extendidos, los contextos se pueden perder cuando se compactan archivos. Use <code class="command">tar --selinux</code> para crear archivos que retengan los contextos. Si un archivo Tar contiene archivos sin los atributos extendidos, o si quiere que los atributos extendidos coincidan con los predeterminados del sistema, ejecute el archivado a través de <code class="command">/sbin/restorecon</code>:
 			</div><pre class="screen">
 $ tar -xvf <em class="replaceable"><code>archive.tar</code></em> | /sbin/restorecon -f -
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context.html
index d8c3b79..7bb639c 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context.html
@@ -1,7 +1,7 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.10.3. Chequeando el Contexto SELinux Predeterminado</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html" title="5.10. Mantención de las Etiquetas de SELinux" /><link rel="prev" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Moving_Files_and_Directories.html" title="5.10.2. Movimiento de Archivos y Directorios" /><link rel="next" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with
 _tar.html" title="5.10.4. Archivando archivos con tar" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Moving_Files_and_Directories.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_tar.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.10.3. Chequeando el Contexto SELinux Predeterminado" 
 id="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.10.3. Chequeando el Contexto SELinux Predeterminado</h3></div></div></div><div class="para">
-				Use the <code class="command">/usr/sbin/matchpathcon</code> command to check if files and directories have the correct SELinux context. From the <span class="citerefentry"><span class="refentrytitle">matchpathcon</span>(8)</span> manual page: "<code class="command">matchpathcon</code> queries the system policy and outputs the default security context associated with the file path."<sup>[<a id="id971013" href="#ftn.id971013" class="footnote">12</a>]</sup>. The following example demonstrates using the <code class="command">/usr/sbin/matchpathcon</code> command to verify that files in <code class="filename">/var/www/html/</code> directory are labeled correctly:
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.10.3. Chequeando el Contexto SELinux Predeterminado</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html" title="5.10. Mantención de las Etiquetas de SELinux" /><link rel="prev" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Moving_Files_and_Directories.html" title="5.10.2. Movimiento de Archivos y Directorios" /><link rel="next" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with
 _tar.html" title="5.10.4. Archivando archivos con tar" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Moving_Files_and_Directories.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_tar.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.10.3. Chequeando el Contexto SELinux Predetermi
 nado" id="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.10.3. Chequeando el Contexto SELinux Predeterminado</h3></div></div></div><div class="para">
+				Use the <code class="command">/usr/sbin/matchpathcon</code> command to check if files and directories have the correct SELinux context. From the <span class="citerefentry"><span class="refentrytitle">matchpathcon</span>(8)</span> manual page: "<code class="command">matchpathcon</code> queries the system policy and outputs the default security context associated with the file path."<sup>[<a id="id892271" href="#ftn.id892271" class="footnote">12</a>]</sup>. The following example demonstrates using the <code class="command">/usr/sbin/matchpathcon</code> command to verify that files in <code class="filename">/var/www/html/</code> directory are labeled correctly:
 			</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
 						Como usuario root de Linux, ejecute el comando <code class="command">touch /var/www/html/archivo{1,2,3}</code> para crear tres archivos (<code class="filename">archivo1</code>, <code class="filename">archivo2</code> y <code class="filename">archivo3</code>). Estos heredan el tipo <code class="computeroutput">httpd_sys_content_t</code> del directorio <code class="filename">/var/www/html/</code>:
 					</div><pre class="screen"># touch /var/www/html/file{1,2,3}
@@ -28,6 +28,6 @@
 			</div><pre class="screen"># /sbin/restorecon -v /var/www/html/file1
 restorecon reset /var/www/html/file1 context unconfined_u:object_r:samba_share_t:s0-&gt;system_u:object_r:httpd_sys_content_t:s0
 
-</pre><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id971013" href="#id971013" class="para">12</a>] </sup>
+</pre><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id892271" href="#id892271" class="para">12</a>] </sup>
 					The <span class="citerefentry"><span class="refentrytitle">matchpathcon</span>(8)</span> manual page, as shipped with the <span class="package">libselinux-utils</span> package in Fedora, is written by Daniel Walsh. Any edits or changes in this version were done by Murray McAllister.
 				</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Moving_Files_and_Directories.html"><strong>Anterior</strong>5.10.2. Movimiento de Archivos y Directorios</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Archiving_Files_with_tar.html"><strong>Siguiente</strong>5.10.4. Archivando archivos con tar</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Moving_Files_and_Directories.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Moving_Files_and_Directories.html
index 8ef98da..de3baf3 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Moving_Files_and_Directories.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Moving_Files_and_Directories.html
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.10.2. Movimiento de Archivos y Directorios</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html" title="5.10. Mantención de las Etiquetas de SELinux" /><link rel="prev" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html" title="5.10. Mantención de las Etiquetas de SELinux" /><link rel="next" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context
 .html" title="5.10.3. Chequeando el Contexto SELinux Predeterminado" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.10.2. Movimiento de Archivos y Dire
 ctorios" id="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Moving_Files_and_Directories"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.10.2. Movimiento de Archivos y Directorios</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.10.2. Movimiento de Archivos y Directorios</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html" title="5.10. Mantención de las Etiquetas de SELinux" /><link rel="prev" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html" title="5.10. Mantención de las Etiquetas de SELinux" /><link rel="next" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context
 .html" title="5.10.3. Chequeando el Contexto SELinux Predeterminado" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.10.2. Movimiento de Archivos 
 y Directorios" id="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Moving_Files_and_Directories"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.10.2. Movimiento de Archivos y Directorios</h3></div></div></div><div class="para">
 				File and directories keep their current SELinux context when they are moved. In many cases, this is incorrect for the location they are being moved to. The following example demonstrates moving a file from a user's home directory to <code class="filename">/var/www/html/</code>, which is used by the Apache HTTP Server. Since the file is moved, it does not inherit the correct SELinux context:
 			</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
 						Ejecute el comando <code class="command">cd</code> sin ningún argumento para cambiar a su directorio de inicio. Una vez ahí, ejecute el comando <code class="command">touch archivo1</code> para crear un archivo. Este archivo se etiqueta con el tipo <code class="computeroutput">user_home_t</code>:
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Mounting_File_Systems-Changing_the_Default_Context.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Mounting_File_Systems-Changing_the_Default_Context.html
index 530ead5..66d38fc 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Mounting_File_Systems-Changing_the_Default_Context.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Mounting_File_Systems-Changing_the_Default_Context.html
@@ -1,7 +1,7 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.9.2. Cambio del Contexto Predeterminado</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html" title="5.9. Montaje de Sistemas de Archivos" /><link rel="prev" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html" title="5.9. Montaje de Sistemas de Archivos" /><link rel="next" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Mounting_an_NFS_File_System.html" title="5.9.3. Montando un Sistema de Arch
 ivos NFS" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Mounting_an_NFS_File_System.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.9.2. Cambio del Contexto Predeterminado" id="sect-Security-Enhanced_Linux-Mounting_File_Systems-Changing_the_Defaul
 t_Context"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.9.2. Cambio del Contexto Predeterminado</h3></div></div></div><div class="para">
-				Como se mencionó en <a class="xref" href="sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types.html" title="5.8. Los tipos file_t y default_t">Sección 5.8, “Los tipos file_t y default_t”</a>, en sistemas de archivo que soportan atributos extendidos, cuando se accede a un archivo en disco que le falta el contexto SELinux, se trata como si hubiera tenido el contexto predeterminado tal como se define en la política SELinux. En políticas comúnes, este contexto predeterminados usa el tipo <code class="computeroutput">file_t</code>. Si se desea usar un contexto predeterminado diferente, monte el sistema de archivo con la opción<code class="option">defcontext</code>.
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.9.2. Cambio del Contexto Predeterminado</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html" title="5.9. Montaje de Sistemas de Archivos" /><link rel="prev" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html" title="5.9. Montaje de Sistemas de Archivos" /><link rel="next" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Mounting_an_NFS_File_System.html" title="5.9.3. Montando un Sistema de Arch
 ivos NFS" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Mounting_an_NFS_File_System.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.9.2. Cambio del Contexto Predeterminado" id="sect-Security-Enhanced_Linux-Mounting_File_Systems-Changing_the_
 Default_Context"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.9.2. Cambio del Contexto Predeterminado</h3></div></div></div><div class="para">
+				As mentioned in <a class="xref" href="sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types.html" title="5.8. Los tipos file_t y default_t">Sección 5.8, “Los tipos file_t y default_t”</a>, on file systems that support extended attributes, when a file that lacks an SELinux context on disk is accessed, it is treated as if it had a default context as defined by SELinux policy. In common policies, this default context uses the <code class="computeroutput">file_t</code> type. If it is desirable to use a different default context, mount the file system with the <code class="option">defcontext</code> option.
 			</div><div class="para">
 				El siguiente ejemplo monta un sistema de archivo recién creado (en <code class="filename">/dev/sda2</code>) en el directorio recién creado <code class="filename">/prueba/</code>. Asume que no hay reglas en <code class="filename">/etc/selinux/targeted/contexts/files/</code> que definan el contexto del directorio <code class="filename">/prueba/</code>:
 			</div><pre class="screen">
@@ -10,11 +10,11 @@
 </pre><div class="para">
 				En este ejemplo:
 			</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
-						the <code class="option">defcontext</code> option defines that <code class="computeroutput">system_u:object_r:samba_share_t:s0</code> is "the default security context for unlabeled files"<sup>[<a id="id1107117" href="#ftn.id1107117" class="footnote">11</a>]</sup>.
+						the <code class="option">defcontext</code> option defines that <code class="computeroutput">system_u:object_r:samba_share_t:s0</code> is "the default security context for unlabeled files"<sup>[<a id="id867095" href="#ftn.id867095" class="footnote">11</a>]</sup>.
 					</div></li><li class="listitem"><div class="para">
 						cuando sea montado, el directorio raíz (<code class="filename">/prueba/</code>) del sistema de archivo se trata como si estuviera etiquetado con el contexto especificado por <code class="option">defcontext</code> (esta etiqueta no se guarda en el disco). Esto afecta el etiquetado de archvios creados en <code class="filename">/prueba/</code>: los archivos nuevos heredan el tipo <code class="computeroutput">samba_share_t</code>, y estas etiquetas se guardan en el disco.
 					</div></li><li class="listitem"><div class="para">
 						los archivos creados bajo <code class="filename">/prueba/</code> mientras el sistema de archivo estaba montado con la opción <code class="option">defcontext</code> retendrán sus etiquetas.
-					</div></li></ul></div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id1107117" href="#id1107117" class="para">11</a>] </sup>
+					</div></li></ul></div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id867095" href="#id867095" class="para">11</a>] </sup>
 							Morris, James. "Filesystem Labeling in SELinux". Published 1 October 2004. Accessed 14 October 2008: <a href="http://www.linuxjournal.com/article/7426">http://www.linuxjournal.com/article/7426</a>.
 						</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html"><strong>Anterior</strong>5.9. Montaje de Sistemas de Archivos</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Mounting_an_NFS_File_System.html"><strong>Siguiente</strong>5.9.3. Montando un Sistema de Archivos NFS</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Mounting_File_Systems-Making_Context_Mounts_Persistent.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Mounting_File_Systems-Making_Context_Mounts_Persistent.html
index d3aa0fb..e060e88 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Mounting_File_Systems-Making_Context_Mounts_Persistent.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Mounting_File_Systems-Making_Context_Mounts_Persistent.html
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.9.5. Haciendo Persistente los Contextos de Montajes</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html" title="5.9. Montaje de Sistemas de Archivos" /><link rel="prev" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Multiple_NFS_Mounts.html" title="5.9.4. Montajes NFS Múltiples" /><link rel="next" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html" title="5.10. Mantención de las Etiqu
 etas de SELinux" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Multiple_NFS_Mounts.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.9.5. Haciendo Persistente los Contextos de Montajes" id="sect-Security-Enhanced_Linux-Mounting_File_Systems-Ma
 king_Context_Mounts_Persistent"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.9.5. Haciendo Persistente los Contextos de Montajes</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.9.5. Haciendo Persistente los Contextos de Montajes</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html" title="5.9. Montaje de Sistemas de Archivos" /><link rel="prev" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Multiple_NFS_Mounts.html" title="5.9.4. Montajes NFS Múltiples" /><link rel="next" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html" title="5.10. Mantención de las Etiqu
 etas de SELinux" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Multiple_NFS_Mounts.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.9.5. Haciendo Persistente los Contextos de Montajes" id="sect-Security-Enhanced_Linux-Mounting_File_Syst
 ems-Making_Context_Mounts_Persistent"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.9.5. Haciendo Persistente los Contextos de Montajes</h3></div></div></div><div class="para">
 				Para hacer que los contextos de montajes persistentes entre remontadas y reiniciadas, agregue las entradas de los sistemas de archivos en <code class="filename">/etc/fstab</code> o un mapa de automontador, y use el contexto deseado como una opción de montaje. El siguiente ejemplo agrega una entrada en <code class="filename">/etc/fstab</code> para un montaje de contexto NFS:
 			</div><pre class="screen">
 server:/export /local/mount/ nfs context="system_u:object_r:httpd_sys_content_t:s0" 0 0
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Mounting_File_Systems-Mounting_an_NFS_File_System.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Mounting_File_Systems-Mounting_an_NFS_File_System.html
index af3c315..9623d92 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Mounting_File_Systems-Mounting_an_NFS_File_System.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Mounting_File_Systems-Mounting_an_NFS_File_System.html
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.9.3. Montando un Sistema de Archivos NFS</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html" title="5.9. Montaje de Sistemas de Archivos" /><link rel="prev" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Changing_the_Default_Context.html" title="5.9.2. Cambio del Contexto Predeterminado" /><link rel="next" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Multiple_NFS_Mounts.html" title="5.9.4. Montajes NFS Múltipl
 es" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Changing_the_Default_Context.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Multiple_NFS_Mounts.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.9.3. Montando un Sistema de Archivos NFS" id="sect-Security-Enhanced_Linux-Mounting_File_Systems-Mounting_an_NFS_File_Sys
 tem"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.9.3. Montando un Sistema de Archivos NFS</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.9.3. Montando un Sistema de Archivos NFS</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html" title="5.9. Montaje de Sistemas de Archivos" /><link rel="prev" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Changing_the_Default_Context.html" title="5.9.2. Cambio del Contexto Predeterminado" /><link rel="next" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Multiple_NFS_Mounts.html" title="5.9.4. Montajes NFS Múltipl
 es" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Changing_the_Default_Context.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Multiple_NFS_Mounts.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.9.3. Montando un Sistema de Archivos NFS" id="sect-Security-Enhanced_Linux-Mounting_File_Systems-Mounting_an_NFS_Fi
 le_System"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.9.3. Montando un Sistema de Archivos NFS</h3></div></div></div><div class="para">
 				Por defecto, los montajes NFS en el lado del cliente son etiquetados con un contexto predeterminado por la política para los sistemas de archivo NFS. En políticas comunes, este contexto predeterminado usa el tipo <code class="computeroutput">nfs_t</code>. Dependiendo de la configuración de la política, los servicios, como el Servidor HTTP Apache y MySQL, pueden no poder leer archivos etiquetados con el tipo <code class="computeroutput">nfs_t</code>. Esto puede prevenir que los sistemas de archivos etiquetados con este tipo se monten y sean leídos o exportados por otros servicios.
 			</div><div class="para">
 				Si desea montar un sistema de archivo NFS y leer o exportar ese sistema de archivo con otro servicio, use la opción <code class="option">contexto</code> cuando monte para anular el tipo <code class="computeroutput">nfs_t</code>. Use la siguiente opción de contexto para montar sistemas de archivo NFS para que puedan compartirse vía el Servidor HTTP Apache:
@@ -10,5 +10,5 @@ context="system_u:object_r:httpd_sys_content_t:s0"
 </pre><div class="para">
 				Dado que los cambios de contexto no se escriben al disco para estas situaciones, el contexto especificado con la opción <code class="option">context</code> sólo se retiene si la opción <code class="option">context</code> se usa en el siguiente montaje, y si el mismo contexto se especifica.
 			</div><div class="para">
-				Como una alternativa a montar sistemas de archivo con la opción <code class="option">contexto</code>, los Booleanos se pueden activar para permitir a los servicios acceder sistemas de archivos etiquetados con el tipo <code class="computeroutput">nfs_t</code>. Vaya a <a class="xref" href="sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS.html" title="5.6.3. Booleanos para NFS y CIFS">Sección 5.6.3, “Booleanos para NFS y CIFS”</a> para instrucciones sobre configuración de Booleanos para permitir a servicios acceder al tipo <code class="computeroutput">nfs_t</code>.
+				As an alternative to mounting file systems with <code class="option">context</code> options, Booleans can be turned on to allow services access to file systems labeled with the <code class="computeroutput">nfs_t</code> type. Refer to <a class="xref" href="sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS.html" title="5.6.3. Booleanos para NFS y CIFS">Sección 5.6.3, “Booleanos para NFS y CIFS”</a> for instructions on configuring Booleans to allow services access to the <code class="computeroutput">nfs_t</code> type.
 			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Changing_the_Default_Context.html"><strong>Anterior</strong>5.9.2. Cambio del Contexto Predeterminado</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Multiple_NFS_Mounts.html"><strong>Siguiente</strong>5.9.4. Montajes NFS Múltiples</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Mounting_File_Systems-Multiple_NFS_Mounts.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Mounting_File_Systems-Multiple_NFS_Mounts.html
index 16421be..7a2bd84 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Mounting_File_Systems-Multiple_NFS_Mounts.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Mounting_File_Systems-Multiple_NFS_Mounts.html
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.9.4. Montajes NFS Múltiples</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html" title="5.9. Montaje de Sistemas de Archivos" /><link rel="prev" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Mounting_an_NFS_File_System.html" title="5.9.3. Montando un Sistema de Archivos NFS" /><link rel="next" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Making_Context_Mounts_Persistent.html" title="5.9.5. Haciendo Persistente
  los Contextos de Montajes" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Mounting_an_NFS_File_System.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Making_Context_Mounts_Persistent.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.9.4. Montajes NFS Múltiples" id="sect-Security-Enhanced_Linux-Mounting_File_Systems-
 Multiple_NFS_Mounts"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.9.4. Montajes NFS Múltiples</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.9.4. Montajes NFS Múltiples</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html" title="5.9. Montaje de Sistemas de Archivos" /><link rel="prev" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Mounting_an_NFS_File_System.html" title="5.9.3. Montando un Sistema de Archivos NFS" /><link rel="next" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Making_Context_Mounts_Persistent.html" title="5.9.5. Haciendo Persistente
  los Contextos de Montajes" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Mounting_an_NFS_File_System.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Making_Context_Mounts_Persistent.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.9.4. Montajes NFS Múltiples" id="sect-Security-Enhanced_Linux-Mounting_File_Sy
 stems-Multiple_NFS_Mounts"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.9.4. Montajes NFS Múltiples</h3></div></div></div><div class="para">
 				Cuando se monten múltiples montajes desde el mismo NFS exportado, el intento de sobreescribir el contexto de SELinux e cada montaje con un contexto diferente, resulta en fallos de los comandos de montaje subsecuentes. En el siguiente ejemplo, el servidor NFS tiene un exportado único, <code class="filename">/export</code>, que tiene dos subdirectorios, <code class="filename">web/</code> and <code class="filename">database/</code>. El siguiente comando intenta dos montajes desde un único export NFS e intenta sobreescribir el contexto para cada uno:
 			</div><pre class="screen">
 # mount server:/export/web /local/web -o\
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Permissive_Domains-Denials_for_Permissive_Domains.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Permissive_Domains-Denials_for_Permissive_Domains.html
index eab3c23..f6ef234 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Permissive_Domains-Denials_for_Permissive_Domains.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Permissive_Domains-Denials_for_Permissive_Domains.html
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.3.4.2. Negaciones para Dominios Permisivos</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains.html" title="7.3.4. Dominios Permisivos" /><link rel="prev" href="sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains.html" title="7.3.4. Dominios Permisivos" /><link rel="next" href="sect-Security-Enhanced_Linux-Fixing_Problems-Searching_For_and_Viewing_Denials.html" title="7.3.5. Búsqueda y Revisión de Negaciones" /></head><body class="t
 oc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Fixing_Problems-Searching_For_and_Viewing_Denials.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="7.3.4.2. Negaciones para Dominios Permisivos" id="sect-Security-Enhanced_Linux-Permissive_Domains-Denials_for_Permissive_Domains"><div class="titlepage"><div>
 <div keep-together.within-column="always"><h4 class="title">7.3.4.2. Negaciones para Dominios Permisivos</h4></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.3.4.2. Negaciones para Dominios Permisivos</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains.html" title="7.3.4. Dominios Permisivos" /><link rel="prev" href="sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains.html" title="7.3.4. Dominios Permisivos" /><link rel="next" href="sect-Security-Enhanced_Linux-Fixing_Problems-Searching_For_and_Viewing_Denials.html" title="7.3.5. Búsqueda y Revisión de Negaciones" /></head><body class="d
 raft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Fixing_Problems-Permissive_Domains.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Fixing_Problems-Searching_For_and_Viewing_Denials.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="7.3.4.2. Negaciones para Dominios Permisivos" id="sect-Security-Enhanced_Linux-Permissive_Domains-Denials_for_Permissive_Domains"><div class="titlepage"
 ><div><div keep-together.within-column="always"><h4 class="title">7.3.4.2. Negaciones para Dominios Permisivos</h4></div></div></div><div class="para">
 					El mensaje <code class="computeroutput">SYSCALL</code> es diferente para dominios permisivos. El siguiente es un ejemplo de una negación de AVC (y la llamada a sistema asociada) desde el Servidor HTTP Apache:
 				</div><pre class="screen">
 type=AVC msg=audit(1226882736.442:86): avc:  denied  { getattr } for  pid=2427 comm="httpd" path="/var/www/html/file1" dev=dm-0 ino=284133 scontext=unconfined_u:system_r:httpd_t:s0 tcontext=unconfined_u:object_r:samba_share_t:s0 tclass=file
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Processes.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Processes.html
index af8e3d7..deea0a3 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Processes.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Processes.html
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.2. Contextos de SELinux para los Procesos</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-SELinux_Contexts.html" title="Capítulo 3. Contextos de SELinux" /><link rel="prev" href="chap-Security-Enhanced_Linux-SELinux_Contexts.html" title="Capítulo 3. Contextos de SELinux" /><link rel="next" href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Users.html" title="3.3. Contextos de SELinux para los Usuarios" /></head><body class="toc_embeded "><div id="tocdiv
 " class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-SELinux_Contexts.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Users.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="3.2. Contextos de SELinux para los Procesos" id="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Processes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="ti
 tle">3.2. Contextos de SELinux para los Procesos</h2></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.2. Contextos de SELinux para los Procesos</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-SELinux_Contexts.html" title="Capítulo 3. Contextos de SELinux" /><link rel="prev" href="chap-Security-Enhanced_Linux-SELinux_Contexts.html" title="Capítulo 3. Contextos de SELinux" /><link rel="next" href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Users.html" title="3.3. Contextos de SELinux para los Usuarios" /></head><body class="draft toc_embeded "><div id="
 tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-SELinux_Contexts.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Users.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="3.2. Contextos de SELinux para los Procesos" id="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Processes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 cla
 ss="title">3.2. Contextos de SELinux para los Procesos</h2></div></div></div><div class="para">
 			Use el comando <code class="command">ps -eZ</code> para ver los contextos de SELinux para los procesos. Por ejemplo:
 		</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
 					Abra una terminal, como la de <span class="guimenu"><strong>Aplicaciones</strong></span> → <span class="guisubmenu"><strong>Herramientas del Sistema</strong></span> → <span class="guimenuitem"><strong>Terminal</strong></span>.
@@ -11,7 +11,7 @@
 				</div><pre class="screen">unconfined_u:unconfined_r:passwd_t:s0-s0:c0.c1023 13212 pts/1 00:00:00 passwd
 
 </pre></li><li class="listitem"><div class="para">
-					En la primer pestaña, presione <strong class="userinput"><code>Ctrl+C</code></strong> para cancelar la aplicación <span class="application"><strong>passwd</strong></span>.
+					In the first tab/terminal, press <strong class="userinput"><code>Ctrl+C</code></strong> to cancel the <span class="application"><strong>passwd</strong></span> application.
 				</div></li></ol></div><div class="para">
 			In this example, when the <code class="filename">/usr/bin/passwd</code> application (labeled with the <code class="computeroutput">passwd_exec_t</code> type) is executed, the user's shell process transitions to the <code class="computeroutput">passwd_t</code> domain. Remember: the type defines a domain for processes, and a type for files.
 		</div><div class="para">
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Users.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Users.html
index d216966..2562fc5 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Users.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Users.html
@@ -1,9 +1,9 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.3. Contextos de SELinux para los Usuarios</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-SELinux_Contexts.html" title="Capítulo 3. Contextos de SELinux" /><link rel="prev" href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Processes.html" title="3.2. Contextos de SELinux para los Procesos" /><link rel="next" href="chap-Security-Enhanced_Linux-Targeted_Policy.html" title="Capítulo 4. Política Destinado" /></head><body class="toc_embeded "><div id="tocd
 iv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Processes.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-Targeted_Policy.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="3.3. Contextos de SELinux para los Usuarios" id="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Users"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="t
 itle">3.3. Contextos de SELinux para los Usuarios</h2></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.3. Contextos de SELinux para los Usuarios</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-SELinux_Contexts.html" title="Capítulo 3. Contextos de SELinux" /><link rel="prev" href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Processes.html" title="3.2. Contextos de SELinux para los Procesos" /><link rel="next" href="chap-Security-Enhanced_Linux-Targeted_Policy.html" title="Capítulo 4. Política Destinado" /></head><body class="draft toc_embeded "><div id
 ="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Processes.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-Targeted_Policy.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="3.3. Contextos de SELinux para los Usuarios" id="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Users"><div class="titlepage"><div><div keep-together.within-column="always"><h2 cl
 ass="title">3.3. Contextos de SELinux para los Usuarios</h2></div></div></div><div class="para">
 			Use el comando <code class="command">id -Z</code> para ver el contexto SELinux asociado con su usuario Linux:
 		</div><pre class="screen">unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
 
 </pre><div class="para">
-			En Fedora, los usuarios Linux corren no confinados por defecto. Este contexto de SELinux muestra que el usuario Linux se mapea al usuario SELinux <code class="computeroutput">unconfined_u</code>, corriendo con el rol <code class="computeroutput">unconfined_r</code> y en el dominio <code class="computeroutput">unconfined_t</code>. <code class="computeroutput">s0-s0</code> es un rango MLS, que en este caso, es el mismo que <code class="computeroutput">s0</code>. Las categorías a las que el usuario tiene acceso se definen por <code class="computeroutput">c0.c1023</code>, que son todas las categorías (<code class="computeroutput">c0</code> a <code class="computeroutput">c1023</code>).
+			In Fedora, Linux users run unconfined by default. This SELinux context shows that the Linux user is mapped to the SELinux <code class="computeroutput">unconfined_u</code> user, running as the <code class="computeroutput">unconfined_r</code> role, and is running in the <code class="computeroutput">unconfined_t</code> domain. <code class="computeroutput">s0-s0</code> is an MLS range, which in this case, is the same as just <code class="computeroutput">s0</code>. The categories the user has access to is defined by <code class="computeroutput">c0.c1023</code>, which is all categories (<code class="computeroutput">c0</code> through to <code class="computeroutput">c1023</code>).
 		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-SELinux_Contexts-SELinux_Contexts_for_Processes.html"><strong>Anterior</strong>3.2. Contextos de SELinux para los Procesos</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-Targeted_Policy.html"><strong>Siguiente</strong>Capítulo 4. Política Destinado</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext.html
index 24a9423..b5986a7 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext.html
@@ -1,14 +1,14 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.7.2. Cambios Persistentes: semanage fcontext</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files.html" title="5.7. Contextos de SELinux - Etiquetado de Archivos" /><link rel="prev" href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files.html" title="5.7. Contextos de SELinux - Etiquetado de Archivos" /><link rel="next" href="sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_
 t_Types.html" title="5.8. Los tipos file_t y default_t" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.7.2. Cambios Persistentes: semanage fcontext" id="sect-Se
 curity-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.7.2. Cambios Persistentes: semanage fcontext</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.7.2. Cambios Persistentes: semanage fcontext</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files.html" title="5.7. Contextos de SELinux - Etiquetado de Archivos" /><link rel="prev" href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files.html" title="5.7. Contextos de SELinux - Etiquetado de Archivos" /><link rel="next" href="sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_
 t_Types.html" title="5.8. Los tipos file_t y default_t" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.7.2. Cambios Persistentes: semanage fcontext" id="s
 ect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.7.2. Cambios Persistentes: semanage fcontext</h3></div></div></div><div class="para">
 				El comando <code class="command">/usr/sbin/semanage fcontext</code> cambia el contexto SELinux de los archivos. Cuando se usa la política destinada, los cambios hechos con este comando se agregan al archivo <code class="filename">/etc/selinux/targeted/contexts/files/file_contexts</code> si los cambios so para archivos que están en <code class="filename">file_contexts</code>, se agregan a <code class="filename">file_contexts.local</code> para archivos nuevos y directorios, como sería al crear un directorio <code class="filename">/web/</code> nuevo. <code class="command">setfiles</code>, que se usa cuando el sistema de archivo es reetiquetado, y <code class="command">/sbin/restorecon</code>, que restaura los contextos de SELinux predeterminados, leen estos archivos, Lo que significa que los cambios hechos por <code class="command">/usr/sbin/semanage fcontext</code> son persistentes, aún si el sistema de archivo es reetiquetado. La política de SELinux controla si los u
 suarios pueden modificar el contexto de SELinux para cualquier archivo dado.
-			</div><div class="formalpara"><h5 class="formalpara">Referencia Rápida</h5>
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Persistent_Changes_semanage_fcontext-Quick_Reference"><h5 class="formalpara">Referencia Rápida</h5>
 					Para hacer que los cambios de contexto de SELinux sobrevivan un reetiquetado del sistema de archivo:
 				</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
 						Ejecute el comando <code class="command">/usr/sbin/semanage fcontext -a <em class="replaceable"><code>opciones</code></em> <em class="replaceable"><code>nombre-de-archivo</code></em>|<em class="replaceable"><code>nombre-de-directorio</code></em></code>, recuerde usar la dirección completa del archivo o del directorio.
 					</div></li><li class="listitem"><div class="para">
 						Ejecute el comando <code class="command">/sbin/restorecon -v <em class="replaceable"><code>nombre-de-archivo</code></em>|<em class="replaceable"><code>nombre-de-directorio</code></em></code> para aplicar los cambios de contexto.
-					</div></li></ol></div><div class="formalpara"><h5 class="formalpara">Changing a File's Type</h5>
+					</div></li></ol></div><div class="formalpara" id="form-Security-Enhanced_Linux-Persistent_Changes_semanage_fcontext-Changing_a_Files_Type"><h5 class="formalpara">Changing a File's Type</h5>
 					The following example demonstrates changing a file's type, and no other attributes of the SELinux context:
 				</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
 						Como usuario root de Linux, ejecute el comando <code class="command">touch /etc/archivo1</code> para crear un archivo nuevo. Por defecto, los archivos recién creados en el directorio <code class="filename">/etc/</code> se etiquetan con el tipo <code class="computeroutput">etc_t</code>:
@@ -34,7 +34,7 @@ restorecon reset /etc/file1 context unconfined_u:object_r:etc_t:s0-&gt;system_u:
 						Como usuario root de Linux, ejecute el comando <code class="command">rm -i /etc/archivo1</code> para borrar el <code class="filename">archivo1</code>.
 					</div></li><li class="listitem"><div class="para">
 						Como usuario root de Linux, ejecute el comando <code class="command">/usr/sbin/semanage fcontext -d /etc/archivo1</code> para eliminar el contexto agregado para <code class="filename">/etc/archivo1</code>. Cuando el contexto se elimina, ejecutando <code class="command">restorecon</code> cambia el tipo a <code class="computeroutput">etc_t</code>, en vez de <code class="computeroutput">samba_share_t</code>.
-					</div></li></ol></div><div class="formalpara"><h5 class="formalpara">Changing a Directory's Type</h5>
+					</div></li></ol></div><div class="formalpara" id="form-Security-Enhanced_Linux-Persistent_Changes_semanage_fcontext-Changing_a_Directorys_Type"><h5 class="formalpara">Changing a Directory's Type</h5>
 					The following example demonstrates creating a new directory and changing that directory's file type, to a type used by Apache HTTP Server:
 				</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
 						Como usuario root de LInux, ejecute el comando <code class="command">mkdir /web</code> para crear un directorio nuevo. Este directorio se etiqueta con el tipo <code class="computeroutput">default_t</code>:
@@ -64,7 +64,7 @@ restorecon reset /web context unconfined_u:object_r:default_t:s0-&gt;system_u:ob
 						Como usuario root de Linux, ejecute el comando <code class="command">/usr/sbin/semanage fcontext -d /web</code> para borrar el contexto agregado para <code class="filename">/web/</code>.
 					</div></li><li class="listitem"><div class="para">
 						Como usuario root de Linux, ejecute el comando <code class="command">/sbin/restorecon -v /web</code> para restaurar el contexto predeterminado de SELinux.
-					</div></li></ol></div><div class="formalpara"><h5 class="formalpara">Cambio de un Directorio y sus Tipos de Contenidos</h5>
+					</div></li></ol></div><div class="formalpara" id="form-Security-Enhanced_Linux-Persistent_Changes_semanage_fcontext-Changing_a_Directory_and_its_Contents_Types"><h5 class="formalpara">Cambio de un Directorio y sus Tipos de Contenidos</h5>
 					The following example demonstrates creating a new directory, and changing the directory's file type (along with its contents) to a type used by Apache HTTP Server. The configuration in this example is used if you want Apache HTTP Server to use a different document root (instead of <code class="filename">/var/www/html/</code>):
 				</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
 						Como usuario root de Linux, ejecute el comando <code class="command">mkdir /web</code> para crear un directorio nuevo, y luego el comando <code class="command">touch /web/archivo{1,2,3}</code> para crear 3 archivos vacíos (<code class="filename">archivo1</code>, <code class="filename">archivo2</code> y <code class="filename">archivo3</code>). El directorio <code class="filename">/web/</code> y los archivos en él son etiquetados con el tipo <code class="computeroutput">default_t</code>:
@@ -102,7 +102,7 @@ restorecon reset /web/file1 context unconfined_u:object_r:default_t:s0-&gt;syste
 						As the Linux root user, run the <code class="command">/usr/sbin/semanage fcontext -d "/web(/.*)?"</code> command to remove the context added for <code class="computeroutput">"/web(/.*)?"</code>.
 					</div></li><li class="listitem"><div class="para">
 						Como usuario root de Linux, ejecute el comando <code class="command">/sbin/restorecon -R -v /web</code> para restaurar el contexto predeterminado de SELinux.
-					</div></li></ol></div><div class="formalpara"><h5 class="formalpara">Borrado de un Contexto agregado</h5>
+					</div></li></ol></div><div class="formalpara" id="form-Security-Enhanced_Linux-Persistent_Changes_semanage_fcontext-Deleting_an_added_Context"><h5 class="formalpara">Borrado de un Contexto agregado</h5>
 					El siguiente ejemplo muestra el agregado y su eliminación del contexto de SELinux:
 				</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
 						Como usuario root de Linux, ejecute el comando <code class="command">/usr/sbin/semanage fcontext -a -t httpd_sys_content_t /prueba</code>. El directorio <code class="filename">/prueba/</code> no tiene que existir. Este comando agrega el siguiente contexto a <code class="filename">/etc/selinux/targeted/contexts/files/file_contexts.local</code>:
@@ -115,7 +115,7 @@ restorecon reset /web/file1 context unconfined_u:object_r:default_t:s0-&gt;syste
 </pre><div class="para">
 						Siendo la primera parte <code class="computeroutput">/prueba</code>. Para evitar que el directorio <code class="filename">/prueba/</code> se etiquete con <code class="computeroutput">httpd_sys_content_t</code> después de ejecutar <code class="command">/sbin/restorecon</code>, o después de un reetiquetado del sistema, ejecute el siguiente comando como usuario root de Linux para eliminar el contexto de <code class="filename">file_contexts.local</code>:
 					</div><div class="para">
-						<code class="command">/usr/sbin/semanage fcontext -d /prueba</code>
+						<code class="command">/usr/sbin/semanage fcontext -d /test</code>
 					</div></li></ol></div><div class="para">
 				Si el contexto es parte de una expresión regular, por ejemplo <code class="computeroutput">/web(/.*)?</code>, use las comillas para encerrar la expresión regular:
 			</div><div class="para">
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users.html
index e73155e..f7a352f 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users.html
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.3. Usuarios Confinados y no Confinados</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Targeted_Policy.html" title="Capítulo 4. Política Destinado" /><link rel="prev" href="sect-Security-Enhanced_Linux-Targeted_Policy-Unconfined_Processes.html" title="4.2. Procesos no Confinados" /><link rel="next" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html" title="Capítulo 5. Trabajando con SELinux" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe 
 id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Targeted_Policy-Unconfined_Processes.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="4.3. Usuarios Confinados y no Confinados" id="sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.3. Usuarios Confinados 
 y no Confinados</h2></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.3. Usuarios Confinados y no Confinados</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Targeted_Policy.html" title="Capítulo 4. Política Destinado" /><link rel="prev" href="sect-Security-Enhanced_Linux-Targeted_Policy-Unconfined_Processes.html" title="4.2. Procesos no Confinados" /><link rel="next" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html" title="Capítulo 5. Trabajando con SELinux" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><i
 frame id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Targeted_Policy-Unconfined_Processes.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="4.3. Usuarios Confinados y no Confinados" id="sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.3. Usuarios Confi
 nados y no Confinados</h2></div></div></div><div class="para">
 			Cada usuario Linux se mapea a un usuario SELinux vía la política de SELinux. Esto permite a los usuarios Linux heredar las restricciones sobre los usuarios SELinux. Este mapeo de usuarios Linux se ve ejecutando el comando <code class="command">semanage login -l</code> como usuario root de Linux:
 		</div><pre class="screen"># /usr/sbin/semanage login -l
 
@@ -11,15 +11,15 @@ root                      unconfined_u              s0-s0:c0.c1023
 system_u                  system_u                  s0-s0:c0.c1023
 
 </pre><div class="para">
-			En Fedora 13, los usuarios de Linux se mapean por defecto al ingreso <code class="computeroutput">__default__</code> de SELinux (el cual se mapea al usuario SELinux <code class="computeroutput">unconfined_u</code>). Lo siguiente define el mapeo por defecto:
+			In Fedora 13, Linux users are mapped to the SELinux <code class="computeroutput">__default__</code> login by default (which is mapped to the SELinux <code class="computeroutput">unconfined_u</code> user). The following defines the default-mapping:
 		</div><pre class="screen">__default__               unconfined_u              s0-s0:c0.c1023
 
 </pre><div class="para">
-			El siguiente ejemplo muestra el agregado de un usuario de Linux nuevo y el mapeo de ese usuario al usuario SELinux <code class="computeroutput">unconfined_u</code>. Asume que el usuario root corre no confinado, como es por defecto en Fedora 13:
+			The following example demonstrates adding a new Linux user, and that Linux user being mapped to the SELinux <code class="computeroutput">unconfined_u</code> user. It assumes that the Linux root user is running unconfined, as it does by default in Fedora 13:
 		</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
 					Como usuario root de Linux, ejecute el comando <code class="command">/usr/sbin/useradd usuarionuevo</code> para crear un nuevo usuario Linux con nombre usuarionuevo.
 				</div></li><li class="listitem"><div class="para">
-					Como usuario root de Linux, corra el comando <code class="command">passwd usuarionuevo</code> para asignar una contraseña para el usuario usuarionuevo de Linux:
+					As the Linux root user, run the <code class="command">passwd newuser</code> command to assign a password to the Linux newuser user:
 				</div><pre class="screen"># passwd newuser
 Changing password for user newuser.
 New UNIX password: <em class="replaceable"><code>Enter a password</code></em> 
@@ -36,8 +36,8 @@ unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
 				</div></li></ol></div><div class="para">
 			Los usuarios Linux confinados y no confinados son sujeto a chequeso de memoria escribible y ejecutable, y también son restringidos por MCS (y MLS, si la política MLS está siendo usada). Si los usuarios Linux no confinados ejecutan una aplicación que la política de SELinux define que puede transicionar del dominio <code class="computeroutput">unconfined_t</code> a su propio dominio confinado, los usuarios Linux no confinados están sujetos a restricciones de ese dominio confinado. El beneficio de seguridad de esto es que, aunque un usuario Linux corra no confinado, la aplicación permanece confinada, y por lo tanto, la explotación de una brecha en la aplicación está limitada por la política. Nota: esto no protege al sistema del usuario. En su defecto, el usuario y el sistema están siendo protegidos de posibles daños causados por una brecha en la aplicación.
 		</div><div class="para">
-			Los siguientes usuarios SELinux confinados están disponibles en Fedora 13:
-		</div><div class="table"><div class="table-contents"><table summary="Capacidades del Usuario SELinux" border="1"><colgroup><col width="17%" /><col width="17%" /><col width="17%" /><col width="17%" /><col width="17%" /><col width="17%" /></colgroup><thead><tr><th>
+			The following confined SELinux users are available in Fedora 13:
+		</div><div class="table" title="Tabla 4.1. Capacidades del Usuario SELinux" id="tabl-Security-Enhanced_Linux-Confined_and_Unconfined_Users-SELinux_User_Capabilities"><div class="table-contents"><table summary="Capacidades del Usuario SELinux" border="1"><colgroup><col width="17%" /><col width="17%" /><col width="17%" /><col width="17%" /><col width="17%" /><col width="17%" /></colgroup><thead><tr><th>
 							Usuario
 						</th><th>
 							Dominio
@@ -110,5 +110,5 @@ unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
 				</div></li></ul></div><div class="para">
 			By default, Linux users in the <code class="computeroutput">guest_t</code> and <code class="computeroutput">xguest_t</code> domains can not execute applications in their home directories or <code class="filename">/tmp/</code>, preventing them from executing applications (which inherit users' permissions) in directories they have write access to. This helps prevent flawed or malicious applications from modifying files users' own.
 		</div><div class="para">
-			Por defecto, los usuarios Linux en los dominios <code class="computeroutput">user_t</code> y <code class="computeroutput">staff_t</code> pueden ejecutar aplicaciones en sus directorios de inicio y en <code class="filename">/tmp/</code>. Vaya a <a class="xref" href="sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications.html" title="6.6. Booleanos para que los Usuarios Ejecuten Aplicaciones">Sección 6.6, “Booleanos para que los Usuarios Ejecuten Aplicaciones”</a> para información sobre permitir y evitar que los usuarios ejecuten aplicaciones en sus directorios de inicio y en <code class="filename">/tmp/</code>.
+			By default, Linux users in the <code class="computeroutput">user_t</code> and <code class="computeroutput">staff_t</code> domains can execute applications in their home directories and <code class="filename">/tmp/</code>. Refer to <a class="xref" href="sect-Security-Enhanced_Linux-Confining_Users-Booleans_for_Users_Executing_Applications.html" title="6.6. Booleanos para que los Usuarios Ejecuten Aplicaciones">Sección 6.6, “Booleanos para que los Usuarios Ejecuten Aplicaciones”</a> for information about allowing and preventing users from executing applications in their home directories and <code class="filename">/tmp/</code>.
 		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Targeted_Policy-Unconfined_Processes.html"><strong>Anterior</strong>4.2. Procesos no Confinados</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html"><strong>Siguiente</strong>Capítulo 5. Trabajando con SELinux</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Targeted_Policy-Unconfined_Processes.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Targeted_Policy-Unconfined_Processes.html
index 7ef9363..3305b85 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Targeted_Policy-Unconfined_Processes.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Targeted_Policy-Unconfined_Processes.html
@@ -1,9 +1,9 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.2. Procesos no Confinados</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Targeted_Policy.html" title="Capítulo 4. Política Destinado" /><link rel="prev" href="chap-Security-Enhanced_Linux-Targeted_Policy.html" title="Capítulo 4. Política Destinado" /><link rel="next" href="sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users.html" title="4.3. Usuarios Confinados y no Confinados" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe
  id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-Targeted_Policy.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="4.2. Procesos no Confinados" id="sect-Security-Enhanced_Linux-Targeted_Policy-Unconfined_Processes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.2. Procesos no Confinados</h2></div></di
 v></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.2. Procesos no Confinados</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Targeted_Policy.html" title="Capítulo 4. Política Destinado" /><link rel="prev" href="chap-Security-Enhanced_Linux-Targeted_Policy.html" title="Capítulo 4. Política Destinado" /><link rel="next" href="sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users.html" title="4.3. Usuarios Confinados y no Confinados" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><
 iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-Targeted_Policy.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="4.2. Procesos no Confinados" id="sect-Security-Enhanced_Linux-Targeted_Policy-Unconfined_Processes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.2. Procesos no Confinados</h2></di
 v></div></div><div class="para">
 			Los procesos no confinados corren en dominios no confinados, por ejemplo, los programas init (del arranque) corren en el dominio no confinado <code class="computeroutput">initrc_t</code>, los procesos no confinados del kernel corren en el dominio <code class="computeroutput">kernel_t</code> y los usuarios no confinados deLInux corren en el dominio <code class="computeroutput">unconfined_t</code>. Para procesos no confinados, las reglas de la política de SELinux son aplicadas, pero hay reglas de la política que permiten que los procesos se ejecuten en dominios no confinados tengan casi todos los accesos. Los procesos que corren en dominios no confinados terminan usando exclusivamente las reglas DAC. Si un proceso no confinado es comprometido, SELinux no impide que un atacante gane acceso a los recursos del sistema y a los datos, pero, por supuesto, las reglas DAC todavía se usan. SELinux es una mejora de seguridad sobre las reglas DAC - no las reemplaza.
 		</div><div class="para">
-			El siguiente ejemplo muestra cómo el Servidor HTTP Apache (<code class="systemitem">httpd</code>) puede acceder datos que se suponen son para ser usados por Samba, cuando se corre no confinado. Nota: en Fedora, el proceso <code class="systemitem">httpd</code> corre en el dominio confinado <code class="computeroutput">httpd_t</code> por defecto. Este es un ejemplo, y no debe usarse en producción. Se asume que los paquetes <span class="package">httpd</span>, <span class="package">wget</span>, <span class="package">setroubleshoot-server</span>, <span class="package">dbus</span> y <span class="package">audit</span> están instalados, que se usa la política destinada de SELinux y que SELinux corre en modo obediente:
+			The following example demonstrates how the Apache HTTP Server (<code class="systemitem">httpd</code>) can access data intended for use by Samba, when running unconfined. Note: in Fedora, the <code class="systemitem">httpd</code> process runs in the confined <code class="computeroutput">httpd_t</code> domain by default. This is an example, and should not be used in production. It assumes that the <span class="package">httpd</span>, <span class="package">wget</span>, <span class="package">setroubleshoot-server</span>, <span class="package">dbus</span> and <span class="package">audit</span> packages are installed, that the SELinux targeted policy is used, and that SELinux is running in enforcing mode:
 		</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
 					Ejecute el comando <code class="command">sestatus</code> para confirmar que SELinux está activado, se ejecuta en modo obligatorio y que la política destinada se está usando:
 				</div><pre class="screen">
@@ -12,11 +12,11 @@ SELinux status:                 enabled
 SELinuxfs mount:                /selinux
 Current mode:                   enforcing
 Mode from config file:          enforcing
-Policy version:                 24
+Policy version:                 23
 Policy from config file:        targeted
 
 </pre><div class="para">
-					<code class="computeroutput">Estado de SELinux: activado</code> se devuelve cuando SELinux está activado. <code class="computeroutput">Modo actual: obediente</code> se devuelve cuando SELinux está ejecutándose en modo obediente. <code class="computeroutput">Política desde el archivo de configuración: destinada</code> se devuelve cuando se usa la política destinada de SELinux.
+					<code class="computeroutput">SELinux status: enabled</code> is returned when SELinux is enabled. <code class="computeroutput">Current mode: enforcing</code> is returned when SELinux is running in enforcing mode. <code class="computeroutput">Policy from config file: targeted</code> is returned when the SELinux targeted policy is used.
 				</div></li><li class="listitem"><div class="para">
 					Como usuario root de Linux, corra el comando <code class="command">touch /var/www/html/prueba2</code> para crear un archivo.
 				</div></li><li class="listitem"><div class="para">
@@ -24,11 +24,11 @@ Policy from config file:        targeted
 				</div><pre class="screen">-rw-r--r--  root root unconfined_u:object_r:httpd_sys_content_t:s0 /var/www/html/test2file
 
 </pre><div class="para">
-					Por defecto, los usuarios Linux corren no confinados en Fedora, razón por la cual el archivo <code class="filename">prueba2</code> está etiquetado con el usuario SELinux <code class="computeroutput">unconfined_u</code>. RBAC se usa para procesos, no para archivos. Los roles no tienen un significado para archivos - el rol <code class="computeroutput">object_r</code> es el rol genérico que se usa para archivos (en almacenamiento persistente y sistemas de archivos de red). Bajo el directorio <code class="filename">/proc/</code>, los archivos relacionados con procesos pueden usar el rol <code class="computeroutput">system_r</code>.<sup>[<a id="id2265626" href="#ftn.id2265626" class="footnote">7</a>]</sup> El tipo <code class="computeroutput">httpd_sys_content_t</code> permite al proceso <code class="systemitem">httpd</code> acceder a este archivo.
+					By default, Linux users run unconfined in Fedora, which is why the <code class="filename">test2file</code> file is labeled with the SELinux <code class="computeroutput">unconfined_u</code> user. RBAC is used for processes, not files. Roles do not have a meaning for files - the <code class="computeroutput">object_r</code> role is a generic role used for files (on persistent storage and network file systems). Under the <code class="filename">/proc/</code> directory, files related to processes may use the <code class="computeroutput">system_r</code> role.<sup>[<a id="id1106159" href="#ftn.id1106159" class="footnote">7</a>]</sup> The <code class="computeroutput">httpd_sys_content_t</code> type allows the <code class="systemitem">httpd</code> process to access this file.
 				</div></li><li class="listitem"><div class="para">
 					El comando <code class="command">chcon</code> reetiqueta archivos; sin embargo, tales cambios de etiquetas no sobreviven cuando el sistema se reetiqueta. Para que los cambios sobrevivan un reetiquetado del sistema, use el comando <code class="command">semanage</code>, que se discute más adelante. Como usuario root de Linux, corra el siguiente comando para cambiar el tipo a un tipo usado por Samba:
 				</div><div class="para">
-					<code class="command">chcon -t samba_share_t /var/www/html/prueba2</code>
+					<code class="command">chcon -t samba_share_t /var/www/html/test2file</code>
 				</div><div class="para">
 					Ejecute el comando <code class="command">ls -Z /var/www/html/prueba2</code> para ver los cambios:
 				</div><pre class="screen">-rw-r--r--  root root unconfined_u:object_r:samba_share_t:s0 /var/www/html/test2file
@@ -119,6 +119,6 @@ Stopping httpd:                                            [  OK  ]
 
 </pre></li></ol></div><div class="para">
 			Los ejemplos en estas secciones muestran cómo proteger los datos desde un proceso confinado comprometido (protegido por SELinux), así como cuánto más accesible son los datos para un atacante si el proceso comprometido estaba no confinado (no protegido por SELinux).
-		</div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id2265626" href="#id2265626" class="para">7</a>] </sup>
-						Cuando se usan otras políticas, tal como la MLS, se pueden usar también otros roles, por ejemplo el <code class="computeroutput">secadm_r</code>.
+		</div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id1106159" href="#id1106159" class="para">7</a>] </sup>
+						When using other policies, such as MLS, other roles may also be used, for example, <code class="computeroutput">secadm_r</code>.
 					</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-Targeted_Policy.html"><strong>Anterior</strong>Capítulo 4. Política Destinado</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Targeted_Policy-Confined_and_Unconfined_Users.html"><strong>Siguiente</strong>4.3. Usuarios Confinados y no Confinados</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Evolving_Rules_and_Broken_Applications.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Evolving_Rules_and_Broken_Applications.html
index abebf80..599665d 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Evolving_Rules_and_Broken_Applications.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Evolving_Rules_and_Broken_Applications.html
@@ -1,7 +1,7 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.2.3. Evolucionando las Reglas y las Aplicaciones Rotas</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html" title="7.2. Tres Principales Causas de Problemas" /><link rel="prev" href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running.html" title="7.2.2. ¿Cómo se Ejecutan los Servicios Confinados?" /><link rel="next" href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html" t
 itle="7.3. Corrección de Problemas" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="7.2.3. Evolucionando las Reglas y las Aplicaciones Rotas" id="sect-Security-Enhanced_Lin
 ux-Top_Three_Causes_of_Problems-Evolving_Rules_and_Broken_Applications"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.2.3. Evolucionando las Reglas y las Aplicaciones Rotas</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.2.3. Evolucionando las Reglas y las Aplicaciones Rotas</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html" title="7.2. Tres Principales Causas de Problemas" /><link rel="prev" href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running.html" title="7.2.2. ¿Cómo se Ejecutan los Servicios Confinados?" /><link rel="next" href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html" t
 itle="7.3. Corrección de Problemas" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="7.2.3. Evolucionando las Reglas y las Aplicaciones Rotas" id="sect-Security-Enhanc
 ed_Linux-Top_Three_Causes_of_Problems-Evolving_Rules_and_Broken_Applications"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.2.3. Evolucionando las Reglas y las Aplicaciones Rotas</h3></div></div></div><div class="para">
 				Las aplicaciones se pueden romper, provocando que SELinux niegue el acceso. También, las reglas de SELinux evolucionan - SELinux no se debe ver como una aplicación que se ejecuta en una cierta forma, haciendo que deniegue el acceso, aún cuando la aplicación está funcionado como se espera que lo haga. Por ejemplo, si una nueva versión de PostgreSQL se lanza, puede realizar acciones sobre la política actual que no han sido vistas antes, haciendo que el acceso sea denegado, aún cuando el acceso debería ser permitido.
 			</div><div class="para">
-				Para estas situaciones, después de que se niegue el acceso, use <code class="command">audit2allow</code> para crear un módulo de política personalizado para permitir el acceso. Vaya a <a class="xref" href="sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow.html" title="7.3.8. Permitiendo el Acceso: audit2allow">Sección 7.3.8, “Permitiendo el Acceso: audit2allow”</a> para más información sobre el uso de <code class="command">audit2allow</code>.
+				For these situations, after access is denied, use <code class="command">audit2allow</code> to create a custom policy module to allow access. Refer to <a class="xref" href="sect-Security-Enhanced_Linux-Fixing_Problems-Allowing_Access_audit2allow.html" title="7.3.8. Permitiendo el Acceso: audit2allow">Sección 7.3.8, “Permitiendo el Acceso: audit2allow”</a> for information about using <code class="command">audit2allow</code>.
 			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running.html"><strong>Anterior</strong>7.2.2. ¿Cómo se Ejecutan los Servicios Confinados?</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html"><strong>Siguiente</strong>7.3. Corrección de Problemas</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running.html
index 23b9916..118ada7 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running.html
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.2.2. ¿Cómo se Ejecutan los Servicios Confinados?</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html" title="7.2. Tres Principales Causas de Problemas" /><link rel="prev" href="sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html" title="7.2. Tres Principales Causas de Problemas" /><link rel="next" href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Evolving_Rules_and_Broken_Applications.html
 " title="7.2.3. Evolucionando las Reglas y las Aplicaciones Rotas" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Evolving_Rules_and_Broken_Applications.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="7.2.2. ¿Cómo se Ejecutan los Servicios
  Confinados?" id="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.2.2. ¿Cómo se Ejecutan los Servicios Confinados?</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.2.2. ¿Cómo se Ejecutan los Servicios Confinados?</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html" title="7.2. Tres Principales Causas de Problemas" /><link rel="prev" href="sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html" title="7.2. Tres Principales Causas de Problemas" /><link rel="next" href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Evolving_Rules_and_Broken_Applications.html
 " title="7.2.3. Evolucionando las Reglas y las Aplicaciones Rotas" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Evolving_Rules_and_Broken_Applications.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="7.2.2. ¿Cómo se Ejecutan los Ser
 vicios Confinados?" id="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.2.2. ¿Cómo se Ejecutan los Servicios Confinados?</h3></div></div></div><div class="para">
 				Los servicios se pueden ejecutar en una variedad de formas. Para cambiar esto, debe decirle a SELinux cómo correrá los servicios. Esto se puede conseguir vía los Booleanos que permiten que parte de las políticas de SELinux se cambien en tiempo de ejecución, sin ningún conocimiento sobre la escritura de políticas de SELinux. Esto permite cambios, tales como permitir a servicios que accedan a sistemas de archivo NFS, sin recargar o recompilar una política SELinux. También, correr servicios en números de puerto no predeterminados requiere que la configuración de la política se actualice vía el comando <code class="command">semanage</code>.
 			</div><div class="para">
 				Por ejemplo, para permitir al Servidor HTTP Apache comunicarse con MySQL, active el Booleano <code class="computeroutput">httpd_can_network_connect_db</code>:
@@ -20,8 +20,8 @@ httpd_enable_ftp_server --&gt; off
 tftp_anon_write --&gt; off
 
 </pre><div class="para">
-				Para una lista de los Booleanos y de si están activos o inactivos, corra el comando <code class="command">/usr/sbin/getsebool -a</code>. Para una lista de los Booleanos y una explicación de lo que son, y de si están activos o no, ejecute el comando <code class="command">/usr/sbin/semanage boolean -l</code> como usuario root de Linux. vaya a <a class="xref" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html" title="5.6. Booleanos">Sección 5.6, “Booleanos”</a> para información sobre listado y configuración de Booleanos.
-			</div><div class="formalpara"><h5 class="formalpara">Números de Puertos</h5>
+				For a list of Booleans and whether they are on or off, run the <code class="command">/usr/sbin/getsebool -a</code> command. For a list of Booleans, an explanation of what each one is, and whether they are on or off, run the <code class="command">/usr/sbin/semanage boolean -l</code> command as the Linux root user. Refer to <a class="xref" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html" title="5.6. Booleanos">Sección 5.6, “Booleanos”</a> for information about listing and configuring Booleans.
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-How_are_Confined_Services_Running-Port_Numbers"><h5 class="formalpara">Números de Puertos</h5>
 					Dependiendo de la configuración de la política, los servicios pueden tener permitido correr sobre ciertos números de puerto. Intentar cambiar el puerto en el que corre un servicio sin cambiar la política puede resultar en un fallo al iniciar el servicio. Por ejemplo, ejecute el comando <code class="command">semanage port -l | grep http</code> como usuario root de Linux para listar los puertos relacionados con <code class="systemitem">http</code>:
 				</div><pre class="screen">
 # /usr/sbin/semanage port -l | grep http
@@ -47,12 +47,12 @@ Unable to open logs
 type=AVC msg=audit(1225948455.061:294): avc:  denied  { name_bind } for  pid=4997 comm="httpd" src=9876 scontext=unconfined_u:system_r:httpd_t:s0 tcontext=system_u:object_r:port_t:s0 tclass=tcp_socket
 
 </pre><div class="para">
-				Para permitir a <code class="systemitem">httpd</code> escuchar en un puerto que no está listado en el tipo de puerto <code class="computeroutput">http_port_t</code>, ejecute el comando <code class="command">semanage port</code> para agregar un puerto a la configuración de la política <sup>[<a id="id2078180" href="#ftn.id2078180" class="footnote">14</a>]</sup>:
+				Para permitir a <code class="systemitem">httpd</code> escuchar en un puerto que no está listado en el tipo de puerto <code class="computeroutput">http_port_t</code>, ejecute el comando <code class="command">semanage port</code> para agregar un puerto a la configuración de la política <sup>[<a id="id950802" href="#ftn.id950802" class="footnote">14</a>]</sup>:
 			</div><pre class="screen">
 # /usr/sbin/semanage port -a -t http_port_t -p tcp 9876
 
 </pre><div class="para">
 				La opción <code class="option">-a</code> agrega un nuevo registro; la opción <code class="option">-t</code> define un tipo; y la opción <code class="option">-p</code> define un protocolo. El último argumento es el número de puerto a agregar.
-			</div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id2078180" href="#id2078180" class="para">14</a>] </sup>
+			</div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id950802" href="#id950802" class="para">14</a>] </sup>
 					El comando <code class="command">semanage port -a</code> agrega una entrada al archivo <code class="filename">/etc/selinux/targeted/modules/active/ports.local</code>. Nota: por defecto, este archivo sólo puede ser visto por el usuario root de Linux.
 				</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html"><strong>Anterior</strong>7.2. Tres Principales Causas de Problemas</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Evolving_Rules_and_Broken_Applications.html"><strong>Siguiente</strong>7.2.3. Evolucionando las Reglas y las Aplicacione...</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html
index c823d63..9f750ca 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Troubleshooting-Fixing_Problems.html
@@ -1,9 +1,9 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.3. Corrección de Problemas</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Troubleshooting.html" title="Capítulo 7. Solución a Problemas" /><link rel="prev" href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Evolving_Rules_and_Broken_Applications.html" title="7.2.3. Evolucionando las Reglas y las Aplicaciones Rotas" /><link rel="next" href="sect-Security-Enhanced_Linux-Fixing_Problems-Possible_Causes_of_Silent_Denials.html" title="7.3.2. Posibles Causas de las 
 Negaciones Silenciosas" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Evolving_Rules_and_Broken_Applications.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Fixing_Problems-Possible_Causes_of_Silent_Denials.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="7.3. Corrección de Problemas" id="sect-Security-Enhanced_Linux-Troubleshootin
 g-Fixing_Problems"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">7.3. Corrección de Problemas</h2></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.3. Corrección de Problemas</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Troubleshooting.html" title="Capítulo 7. Solución a Problemas" /><link rel="prev" href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Evolving_Rules_and_Broken_Applications.html" title="7.2.3. Evolucionando las Reglas y las Aplicaciones Rotas" /><link rel="next" href="sect-Security-Enhanced_Linux-Fixing_Problems-Possible_Causes_of_Silent_Denials.html" title="7.3.2. Posibles Causas de las 
 Negaciones Silenciosas" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Evolving_Rules_and_Broken_Applications.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Fixing_Problems-Possible_Causes_of_Silent_Denials.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="7.3. Corrección de Problemas" id="sect-Security-Enhanced_Linux-Troubles
 hooting-Fixing_Problems"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">7.3. Corrección de Problemas</h2></div></div></div><div class="para">
 			Las siguientes secciones ayudan a resolver problemas. Cubren los temas: chequeo de los permisos de Linux, que se chequean antes que las reglas de SELinux; posibles causas de negaciones de acceso de SELinux, pero no negaciones que se estén guardando; páginas man de los servicios, que contienen información sobre etiquetado y Booleanos; dominios permisivos, para permitir a un proceso correr en modo permisivo, en vez de todo el sistema; cómo buscar y encontrar mensajes; análisis de negaciones; y creación de módulos de políticas personalizados con <code class="command">audit2allow</code>.
 		</div><div class="section" title="7.3.1. Permisos de Linux" id="sect-Security-Enhanced_Linux-Fixing_Problems-Linux_Permissions"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.3.1. Permisos de Linux</h3></div></div></div><div class="para">
-				Cuando el acceso se niega, verifique los permisos estándares de LInux. Como se mencionó en <a class="xref" href="chap-Security-Enhanced_Linux-Introduction.html" title="Capítulo 2. Introducción">Capítulo 2, <i>Introducción</i></a>, la mayoría de los sistemas operativos usan un sistema de Control de Acceso Discrecional (DAC) para controlar el acceso, permitiendo a los usuarios controlar los permisos de sus propios archivos. Las reglas de políticas de SELinux se verifican después de estas reglas DAC. Las reglas de políticas de SELinux no se usan si las reglas DAC niegan el acceso al principio.
+				When access is denied, check standard Linux permissions. As mentioned in <a class="xref" href="chap-Security-Enhanced_Linux-Introduction.html" title="Capítulo 2. Introducción">Capítulo 2, <i>Introducción</i></a>, most operating systems use a Discretionary Access Control (DAC) system to control access, allowing users to control the permissions of files that they own. SELinux policy rules are checked after DAC rules. SELinux policy rules are not used if DAC rules deny access first.
 			</div><div class="para">
 				Si el acceso es denegado y no hay negaciones SELinux guardadas, use el comando <code class="command">ls -l</code> para ver los permisos estándares de Linux:
 			</div><pre class="screen">
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html
index ec4bed6..f5865dd 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems.html
@@ -1,22 +1,22 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.2. Tres Principales Causas de Problemas</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Troubleshooting.html" title="Capítulo 7. Solución a Problemas" /><link rel="prev" href="chap-Security-Enhanced_Linux-Troubleshooting.html" title="Capítulo 7. Solución a Problemas" /><link rel="next" href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running.html" title="7.2.2. ¿Cómo se Ejecutan los Servicios Confinados?" /></head><body class="toc
 _embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-Troubleshooting.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="7.2. Tres Principales Causas de Problemas" id="sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems"><div class="titlepage"><div><div keep-togeth
 er.within-column="always"><h2 class="title">7.2. Tres Principales Causas de Problemas</h2></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.2. Tres Principales Causas de Problemas</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Troubleshooting.html" title="Capítulo 7. Solución a Problemas" /><link rel="prev" href="chap-Security-Enhanced_Linux-Troubleshooting.html" title="Capítulo 7. Solución a Problemas" /><link rel="next" href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running.html" title="7.2.2. ¿Cómo se Ejecutan los Servicios Confinados?" /></head><body class="dra
 ft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-Troubleshooting.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="7.2. Tres Principales Causas de Problemas" id="sect-Security-Enhanced_Linux-Troubleshooting-Top_Three_Causes_of_Problems"><div class="titlepage"><div><div keep-
 together.within-column="always"><h2 class="title">7.2. Tres Principales Causas de Problemas</h2></div></div></div><div class="para">
 			Las siguientes secciones describen las tres principales causas de problemas: problemas de etiquetados, configuración de Booleanos y puertos para servicios, y la evolución de las reglas SELinux.
 		</div><div class="section" title="7.2.1. Problemas de Etiquetados" id="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-Labeling_Problems"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.2.1. Problemas de Etiquetados</h3></div></div></div><div class="para">
 				En sistemas que corren SELinux, todos los procesosy archivos se etiquetan con una etiqueta que contiene información de seguridad relevante. Esta información se llama contexto de SELinux. Si estas etiquetas están mal, el acceso puede ser negado. Si una aplicación se etiqueta incorrectamente, el proceso al que transiciona puede no tener la etiqueta correcta, causando negaciones de acceso de SELinux, y los procesos pueden crear archivo con las etiquetas incorrectas.
 			</div><div class="para">
-				Una causa común de problemas de etiquetados es cuando un directorio no estandar se usa para un servicio. Por ejemplo, en vez de usar <code class="filename">/var/www/html/</code> para un sitio web, un administrador prefiere usar <code class="filename">/srv/miweb/</code>. En Fedora 13, el directorio <code class="filename">/srv/</code> se etiqueta con el tipo <code class="computeroutput">var_t</code>. Los archivos y directorios creados en <code class="filename">/srv/</code> heredan este tipo. También, los directorios de alto nivel recién creados (como <code class="filename">/miservidor/</code>) puede ser etiquetado con el tipo <code class="computeroutput">default_t</code>. SELinux impide al Servidor HTTP Apache (<code class="systemitem">httpd</code>) el acceso a estos dos tipos. Para permitirle el acceso, SELinux debe saber qué archivos en <code class="filename">/srv/miweb/</code> son accesibles a <code class="systemitem">httpd</code>:
+				A common cause of labeling problems is when a non-standard directory is used for a service. For example, instead of using <code class="filename">/var/www/html/</code> for a website, an administrator wants to use <code class="filename">/srv/myweb/</code>. On Fedora 13, the <code class="filename">/srv/</code> directory is labeled with the <code class="computeroutput">var_t</code> type. Files and directories created and <code class="filename">/srv/</code> inherit this type. Also, newly-created top-level directories (such as <code class="filename">/myserver/</code>) may be labeled with the <code class="computeroutput">default_t</code> type. SELinux prevents the Apache HTTP Server (<code class="systemitem">httpd</code>) from accessing both of these types. To allow access, SELinux must know that the files in <code class="filename">/srv/myweb/</code> are to be accessible to <code class="systemitem">httpd</code>:
 			</div><pre class="screen">
 # /usr/sbin/semanage fcontext -a -t httpd_sys_content_t \
 "/srv/myweb(/.*)?"
 
 </pre><div class="para">
-				Este comando <code class="command">semanage</code> agrega el contexto para el directorio <code class="filename">/srv/miweb/</code> (y todos los archivos dentro de él) a la configuración de contexto de archivos de SELinux <sup>[<a id="id2084703" href="#ftn.id2084703" class="footnote">13</a>]</sup>. El comando <code class="command">semanage</code> no cambia el contexto. Como usuario root de Linux, ejecute el comando <code class="command">restorecon</code> para aplicar los cambios:
+				Este comando <code class="command">semanage</code> agrega el contexto para el directorio <code class="filename">/srv/miweb/</code> (y todos los archivos dentro de él) a la configuración de contexto de archivos de SELinux <sup>[<a id="id1202595" href="#ftn.id1202595" class="footnote">13</a>]</sup>. El comando <code class="command">semanage</code> no cambia el contexto. Como usuario root de Linux, ejecute el comando <code class="command">restorecon</code> para aplicar los cambios:
 			</div><pre class="screen">
 # /sbin/restorecon -R -v /srv/myweb
 
 </pre><div class="para">
-				Vaya a <a class="xref" href="sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext.html" title="5.7.2. Cambios Persistentes: semanage fcontext">Sección 5.7.2, “Cambios Persistentes: semanage fcontext”</a> para más información sobre agregado de contextos a la configuración de contexto de archivo.
+				Refer to <a class="xref" href="sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext.html" title="5.7.2. Cambios Persistentes: semanage fcontext">Sección 5.7.2, “Cambios Persistentes: semanage fcontext”</a> for further information about adding contexts to the file-context configuration.
 			</div><div class="section" title="7.2.1.1. ¿Cuál es el contexto correcto?" id="sect-Security-Enhanced_Linux-Labeling_Problems-What_is_the_Correct_Context"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">7.2.1.1. ¿Cuál es el contexto correcto?</h4></div></div></div><div class="para">
 					El comando <code class="command">matchpathcon</code> chequea el contexto de un nombre completo de archivo y lo compara con la etiqueta por defecto para esa dirección. El siguiente ejemplo muestra el uso de <code class="command">matchpathcon</code> en un directorio con archivos etiquetados incorrectamente:
 				</div><pre class="screen">
@@ -38,7 +38,7 @@ restorecon reset /var/www/html/page1.html context unconfined_u:object_r:samba_sh
 restorecon reset /var/www/html/index.html context unconfined_u:object_r:samba_share_t:s0-&gt;system_u:object_r:httpd_sys_content_t:s0
 
 </pre><div class="para">
-					Vaya a <a class="xref" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context.html" title="5.10.3. Chequeando el Contexto SELinux Predeterminado">Sección 5.10.3, “Chequeando el Contexto SELinux Predeterminado”</a> para un ejemplo más detallado de <code class="command">matchpathcon</code>.
-				</div></div></div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id2084703" href="#id2084703" class="para">13</a>] </sup>
+					Refer to <a class="xref" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Checking_the_Default_SELinux_Context.html" title="5.10.3. Chequeando el Contexto SELinux Predeterminado">Sección 5.10.3, “Chequeando el Contexto SELinux Predeterminado”</a> for a more detailed example of <code class="command">matchpathcon</code>.
+				</div></div></div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id1202595" href="#id1202595" class="para">13</a>] </sup>
 					Los archivos en <code class="filename">/etc/selinux/targeted/contexts/files/</code> definen los contextos de archivos y directorios. Los archivos en este directorio son leídos por <code class="command">restorecon</code> y <code class="command">setfiles</code> para restaurar archivos y directorios a sus contextos predeterminados.
 				</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-Troubleshooting.html"><strong>Anterior</strong>Capítulo 7. Solución a Problemas</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Top_Three_Causes_of_Problems-How_are_Confined_Services_Running.html"><strong>Siguiente</strong>7.2.2. ¿Cómo se Ejecutan los Servicios Confinados?</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html
index d2b6a76..179a733 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.6. Booleanos</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html" title="Capítulo 5. Trabajando con SELinux" /><link rel="prev" href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes.html" title="5.5. Modos de SELinux" /><link rel="next" href="sect-Security-Enhanced_Linux-Booleans-Configuring_Booleans.html" title="5.6.2. Configurando los Booleanos" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class
 ="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Booleans-Configuring_Booleans.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.6. Booleanos" id="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.6. Booleanos</h2></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.6. Booleanos</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html" title="Capítulo 5. Trabajando con SELinux" /><link rel="prev" href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes.html" title="5.5. Modos de SELinux" /><link rel="next" href="sect-Security-Enhanced_Linux-Booleans-Configuring_Booleans.html" title="5.6.2. Configurando los Booleanos" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe"
  class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Booleans-Configuring_Booleans.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.6. Booleanos" id="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.6. Booleanos</h2></div></div></div><div class="para">
 			Los booleanos permiten cambiar partes de la política de SELinux en tiempo de ejecución, sin ningún conocimiento sobre la escritura de políticas de SELinux. Esto permite cambios, como permitir el acceso de servicios a sistemas de archivo NFS, sin recargar o recompilar la política de SELinux.
 		</div><div class="section" title="5.6.1. Listando los Booleanos" id="sect-Security-Enhanced_Linux-Booleans-Listing_Booleans"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.6.1. Listando los Booleanos</h3></div></div></div><div class="para">
 				Para una lista de los Booleanos, una explicación de lo que son y de si están activos o inactivos, ejecute el comando <code class="command">semanage boolean -l</code> como usuario root de Linux. El siguiente ejemplo no lista todos los Booleanos:
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html
index 22e0038..b94400a 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.4. Habilitando y Deshabilitando SELinux</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html" title="Capítulo 5. Trabajando con SELinux" /><link rel="prev" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Main_Configuration_File.html" title="5.3. Archivo de Configuración Principal" /><link rel="next" href="sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux.html" title="5.4.2. Deshabilitando SELinux" /></head><body class=
 "toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Main_Configuration_File.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.4. Habilitando y Deshabilitando SELinux" id="sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux"><div class="titlep
 age"><div><div keep-together.within-column="always"><h2 class="title">5.4. Habilitando y Deshabilitando SELinux</h2></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.4. Habilitando y Deshabilitando SELinux</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html" title="Capítulo 5. Trabajando con SELinux" /><link rel="prev" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Main_Configuration_File.html" title="5.3. Archivo de Configuración Principal" /><link rel="next" href="sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux.html" title="5.4.2. Deshabilitando SELinux" /></head><body class=
 "draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Main_Configuration_File.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.4. Habilitando y Deshabilitando SELinux" id="sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux"><div class="
 titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.4. Habilitando y Deshabilitando SELinux</h2></div></div></div><div class="para">
 			Use los comandos <code class="command">/usr/sbin/getenforce</code> o <code class="command">/usr/sbin/sestatus</code> para chequear el estado de SELinux. El comando <code class="command">getenforce</code> devuelve <code class="computeroutput">Obediente</code>, <code class="computeroutput">Permisivo</code>, o <code class="computeroutput">Deshabilitado</code>. El comando <code class="command">getenforce</code> devuelve <code class="computeroutput">Obediente</code> cuando SELinux está habilitado (las reglas de la política de SELinux son aplicadas):
 		</div><pre class="screen">$ /usr/sbin/getenforce
 Enforcing
@@ -18,7 +18,7 @@ Policy version:                 23
 Policy from config file:        targeted
 
 </pre><div class="para">
-			<code class="computeroutput">Estado de SELinux: activado</code> se devuelve cuando SELinux está activado. <code class="computeroutput">Modo actual: obediente</code> se devuelve cuando SELinux corre en modo obediente. <code class="computeroutput">Política desde el archivo de configuración: destinado</code> se devuelve cuando la política destinada de SELinux está en uso.
+			<code class="computeroutput">SELinux status: enabled</code> is returned when SELinux is enabled. <code class="computeroutput">Current mode: enforcing</code> is returned when SELinux is running in enforcing mode. <code class="computeroutput">Policy from config file: targeted</code> is returned when the SELinux targeted policy is used.
 		</div><div class="section" title="5.4.1. Habilitando SELinux" id="sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Enabling_SELinux"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.4.1. Habilitando SELinux</h3></div></div></div><div class="para">
 				En sistemas con SELinux deshabilitado, la opción <code class="computeroutput">SELINUX=disabled</code> se configura en <code class="filename">/etc/selinux/config</code>:
 			</div><pre class="screen"># This file controls the state of SELinux on the system.
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-Main_Configuration_File.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-Main_Configuration_File.html
index 2166928..6efc029 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-Main_Configuration_File.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-Main_Configuration_File.html
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.3. Archivo de Configuración Principal</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html" title="Capítulo 5. Trabajando con SELinux" /><link rel="prev" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used.html" title="5.2. Qué Archivo Log se usa" /><link rel="next" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html" title="5.4. Habilitando y Deshabilitando SELinux" /></head><body class
 ="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.3. Archivo de Configuración Principal" id="sect-Security-Enhanced_Linux-Working_with_SELinux-Main_Configuration_File"><div class="titlepage">
 <div><div keep-together.within-column="always"><h2 class="title">5.3. Archivo de Configuración Principal</h2></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.3. Archivo de Configuración Principal</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html" title="Capítulo 5. Trabajando con SELinux" /><link rel="prev" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used.html" title="5.2. Qué Archivo Log se usa" /><link rel="next" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html" title="5.4. Habilitando y Deshabilitando SELinux" /></head><body class
 ="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.3. Archivo de Configuración Principal" id="sect-Security-Enhanced_Linux-Working_with_SELinux-Main_Configuration_File"><div class="title
 page"><div><div keep-together.within-column="always"><h2 class="title">5.3. Archivo de Configuración Principal</h2></div></div></div><div class="para">
 			El archivo <code class="filename">/etc/selinux/config</code> es el archivo de configuración principal de SELinux. Controla el modo de SELinux y la política de SELinux a usar:
 		</div><pre class="screen"># This file controls the state of SELinux on the system.
 # SELINUX= can take one of these three values:
@@ -13,9 +13,9 @@ SELINUX=enforcing
 #       mls - Multi Level Security protection.
 SELINUXTYPE=targeted
 
-</pre><div class="variablelist"><dl><dt><span class="term"><code class="computeroutput">SELINUX=obediente</code></span></dt><dd><div class="para">
+</pre><div class="variablelist"><dl><dt><span class="term"><code class="computeroutput">SELINUX=enforcing</code></span></dt><dd><div class="para">
 						La opción <code class="option">SELINUX</code> pone el modo en el que corre SELinux. SELinux tiene tres modos: obediente, permisivo y deshabilitado. Cuando se usa modo obediente, la política de SELinux es aplicada y SELinux niega el acceso basándose en las reglas de políticas de SELinux. Los mensajes de negación se guardan. Cuando se usa modo permisivo, la política de SELinux no es obediente. Los mensajes son guardados. SELinux no niega el acceso, pero se guardan las negaciones de acciones que hubieran sido negadas si SELinux estaba en modo obediente. Cuando se usa el modo deshabilitado, SELinux está deshabilitado (el módulo de SELinux no se registra con el kernel de Linux), y sólo se usan las reglas DAC.
-					</div></dd><dt><span class="term"><code class="computeroutput">SELINUXTYPE=destinado</code></span></dt><dd><div class="para">
+					</div></dd><dt><span class="term"><code class="computeroutput">SELINUXTYPE=targeted</code></span></dt><dd><div class="para">
 						La opción <code class="option">SELINUXTYPE</code> pone la política SELinux a usar. La política Destinada es la predeterminada. Sólo cambie esta opción si quiere usar la política MLS. Para usar la política MLS, instale el paquete <span class="package">selinux-policy-mls</span>; configure <code class="option">SELINUXTYPE=mls</code> en <code class="filename">/etc/selinux/config</code>; y reinicie su sistema.
 					</div></dd></dl></div><div class="important"><h2>Importante</h2><div class="para">
 				Cuando los sistemas corren con SELinux en modo permisivo o deshabilitado, los usuarios tiene permiso para etiquetar los archivos incorrectamente. También, los archivos creados con SELinux deshabilitado no son etiquetados. Esto causa problemas cuando se cambia a modo obediente. Para prevenir el etiquetado incorrecto o la falta de etiquetado, los sistemas de archivos son automáticamente reetiquetados cuando se cambie desde el modo deshabilitado al modo permisivo u obediente.
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html
index 2360ea9..680d336 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-Maintaining_SELinux_Labels_.html
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.10. Mantención de las Etiquetas de SELinux</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html" title="Capítulo 5. Trabajando con SELinux" /><link rel="prev" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Making_Context_Mounts_Persistent.html" title="5.9.5. Haciendo Persistente los Contextos de Montajes" /><link rel="next" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Moving_Files_and_Directories.html" title="5.10.2. Movimient
 o de Archivos y Directorios" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Making_Context_Mounts_Persistent.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Moving_Files_and_Directories.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.10. Mantención de las Etiquetas de SELinux" id="sect-Security-Enhanced_Linux
 -Working_with_SELinux-Maintaining_SELinux_Labels_"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.10. Mantención de las Etiquetas de SELinux</h2></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.10. Mantención de las Etiquetas de SELinux</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html" title="Capítulo 5. Trabajando con SELinux" /><link rel="prev" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Making_Context_Mounts_Persistent.html" title="5.9.5. Haciendo Persistente los Contextos de Montajes" /><link rel="next" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Moving_Files_and_Directories.html" title="5.10.2. Movimient
 o de Archivos y Directorios" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Making_Context_Mounts_Persistent.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Moving_Files_and_Directories.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.10. Mantención de las Etiquetas de SELinux" id="sect-Security-Enhanced
 _Linux-Working_with_SELinux-Maintaining_SELinux_Labels_"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.10. Mantención de las Etiquetas de SELinux</h2></div></div></div><div class="para">
 			Estas secciones describen qué les pasa a los contextos SELinux cuando se copia, mueve y compacta archivos y directorios. También explica cómo preservar los contextos cuando se copia o se compacta.
 		</div><div class="section" title="5.10.1. Copia de Directorios y Archivos" id="sect-Security-Enhanced_Linux-Maintaining_SELinux_Labels_-Copying_Files_and_Directories"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.10.1. Copia de Directorios y Archivos</h3></div></div></div><div class="para">
 				When a file or directory is copied, a new file or directory is created if it does not exist. That new file or directory's context is based on default-labeling rules, not the original file or directory's context (unless options were used to preserve the original context). For example, files created in user home directories are labeled with the <code class="computeroutput">user_home_t</code> type:
@@ -22,7 +22,7 @@ $ ls -Z /etc/file1
 				Cuando el <code class="filename">archivo1</code> se copia a <code class="filename">/etc/</code>, si <code class="filename">/etc/archivo1</code> no existe, <code class="filename">/etc/archivo1</code> se crea como un archivo nuevo. Como se muestra en el ejemplo de arriba, <code class="filename">/etc/archivo1</code> se etiqueta con el tipo <code class="computeroutput">etc_t</code>, de acuerdo con las reglas de etiquetado predeterminadas.
 			</div><div class="para">
 				When a file is copied over an existing file, the existing file's context is preserved, unless the user specified <code class="command">cp</code> options to preserve the context of the original file, such as <code class="option">--preserve=context</code>. SELinux policy may prevent contexts from being preserved during copies.
-			</div><div class="formalpara"><h5 class="formalpara">Copia sin Preservar los Contextos de SELinux</h5>
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Copying_Files_and_Directories-Copying_Without_Preserving_SELinux_Contexts"><h5 class="formalpara">Copia sin Preservar los Contextos de SELinux</h5>
 					Cuando se copia un archivo con el comando <code class="command">cp</code>, si no se dan opciones, el tipo se hereda desde el directorio padre destino:
 				</div><pre class="screen">
 $ touch file1
@@ -36,7 +36,7 @@ $ ls -Z /var/www/html/file1
 
 </pre><div class="para">
 				In this example, <code class="filename">file1</code> is created in a user's home directory, and is labeled with the <code class="computeroutput">user_home_t</code> type. The <code class="filename">/var/www/html/</code> directory is labeled with the <code class="computeroutput">httpd_sys_content_t</code> type, as shown with the <code class="command">ls -dZ /var/www/html/</code> command. When <code class="filename">file1</code> is copied to <code class="filename">/var/www/html/</code>, it inherits the <code class="computeroutput">httpd_sys_content_t</code> type, as shown with the <code class="command">ls -Z /var/www/html/file1</code> command.
-			</div><div class="formalpara"><h5 class="formalpara">Preservación de los Contextos de SELinux cuando se copia</h5>
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Copying_Files_and_Directories-Preserving_SELinux_Contexts_When_Copying"><h5 class="formalpara">Preservación de los Contextos de SELinux cuando se copia</h5>
 					Use el comando <code class="command">cp --preserve=context</code> para preservar los contextos cuando se copia:
 				</div><pre class="screen">
 $ touch file1
@@ -50,7 +50,7 @@ $ ls -Z /var/www/html/file1
 
 </pre><div class="para">
 				In this example, <code class="filename">file1</code> is created in a user's home directory, and is labeled with the <code class="computeroutput">user_home_t</code> type. The <code class="filename">/var/www/html/</code> directory is labeled with the <code class="computeroutput">httpd_sys_content_t</code> type, as shown with the <code class="command">ls -dZ /var/www/html/</code> command. Using the <code class="option">--preserve=context</code> option preserves SELinux contexts during copy operations. As shown with the <code class="command">ls -Z /var/www/html/file1</code> command, the <code class="filename">file1</code> <code class="computeroutput">user_home_t</code> type was preserved when the file was copied to <code class="filename">/var/www/html/</code>.
-			</div><div class="formalpara"><h5 class="formalpara">Copiado y Cambio del Contexto</h5>
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Copying_Files_and_Directories-Copying_and_Changing_the_Context"><h5 class="formalpara">Copiado y Cambio del Contexto</h5>
 					Use the <code class="command">cp -Z</code> command to change the destination copy's context. The following example was performed in the user's home directory:
 				</div><pre class="screen">
 $ touch file1
@@ -62,7 +62,7 @@ $ rm file1 file2
 
 </pre><div class="para">
 				En este ejemplo, el contexto se define en la opción <code class="option">-Z</code>. Sin la opción <code class="option">-Z</code>, <code class="filename">archivo2</code> se etiquetaría con el contexto <code class="computeroutput">unconfined_u:object_r:user_home_t</code>.
-			</div><div class="formalpara"><h5 class="formalpara">Copia de un Archivos sobre un otro existente</h5>
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Copying_Files_and_Directories-Copying_a_File_Over_an_Existing_File"><h5 class="formalpara">Copia de un Archivos sobre un otro existente</h5>
 					When a file is copied over an existing file, the existing file's context is preserved (unless an option is used to preserve contexts). For example:
 				</div><pre class="screen">
 # touch /etc/file1
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html
index 62dbf26..bfd621d 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.9. Montaje de Sistemas de Archivos</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html" title="Capítulo 5. Trabajando con SELinux" /><link rel="prev" href="sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types.html" title="5.8. Los tipos file_t y default_t" /><link rel="next" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Changing_the_Default_Context.html" title="5.9.2. Cambio del Contexto Predeterminado" /></head><bo
 dy class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Changing_the_Default_Context.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.9. Montaje de Sistemas de Archivos" id="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems"><div class="ti
 tlepage"><div><div keep-together.within-column="always"><h2 class="title">5.9. Montaje de Sistemas de Archivos</h2></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.9. Montaje de Sistemas de Archivos</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html" title="Capítulo 5. Trabajando con SELinux" /><link rel="prev" href="sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types.html" title="5.8. Los tipos file_t y default_t" /><link rel="next" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Changing_the_Default_Context.html" title="5.9.2. Cambio del Contexto Predeterminado" /></head><bo
 dy class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Mounting_File_Systems-Changing_the_Default_Context.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.9. Montaje de Sistemas de Archivos" id="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems"><div cla
 ss="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.9. Montaje de Sistemas de Archivos</h2></div></div></div><div class="para">
 			Por defecto, cuando un sistema de archivo que soporta atributos extendidos se monta, el contexto de seguridad para cada archivo se obtiene de atributo extendido <span class="emphasis"><em>security.selinux</em></span> del archivo. A los archivos en sistemas de archivo que no dan soporte a atributos extendidos se les asigna un único contexto de seguridad predeterminado desde la configuración de la política, basada en el tipo de sistema de archivo.
 		</div><div class="para">
 			Use el comando <code class="command">mount -o context</code> para superponer los atributos extendidos actuales, o para especificar uno distinto y por defecto para sistemas de archivo que no dan soporte a atributos extendidos. Esto es útil si no confía en que un sistema de archivo provea los atributos correctos, por ejemplo, medios removibles en sistemas múltiples. El comando <code class="command">mount -o context</code> también se puede ussar para dar soporte al etiquetado de sistemas de archivos que no soportan atributos extendidos, tales como la Tabla de Ubicación de Archivos (FAT) o los sistemas de archivo NFS. El contexto especificado con la opción <code class="option">context</code> no se escribe al disco: los contextos originales son preservados, y se ven cuando se lo monta sin la opción <code class="option">context</code> (si el sistema de archivo ya tenía sopoorte para atributos extendidos).
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files.html
index 519e80d..12ac32a 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Contexts_Labeling_Files.html
@@ -1,7 +1,7 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.7. Contextos de SELinux - Etiquetado de Archivos</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html" title="Capítulo 5. Trabajando con SELinux" /><link rel="prev" href="sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS.html" title="5.6.3. Booleanos para NFS y CIFS" /><link rel="next" href="sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext.html" title="5.7.2. Cambios Persistentes: semanage fco
 ntext" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.7. Contextos de SELinux - Etiquetado de Archivos" id="sect-Security-Enhanced_Linux-Working_with_SELinux-SEL
 inux_Contexts_Labeling_Files"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.7. Contextos de SELinux - Etiquetado de Archivos</h2></div></div></div><div class="para">
-			En sistemas que corren SELinux, todos los procesos y archivos son etiquetados con una etiqueta que contiene información de seguridad relevante. Esta información se llama contexto de SELinux. Para archivos, esto se ve usando el comando <code class="command">ls -Z</code>:
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.7. Contextos de SELinux - Etiquetado de Archivos</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html" title="Capítulo 5. Trabajando con SELinux" /><link rel="prev" href="sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS.html" title="5.6.3. Booleanos para NFS y CIFS" /><link rel="next" href="sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext.html" title="5.7.2. Cambios Persistentes: semanage fco
 ntext" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Booleans-Booleans_for_NFS_and_CIFS.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.7. Contextos de SELinux - Etiquetado de Archivos" id="sect-Security-Enhanced_Linux-Working_with_SELin
 ux-SELinux_Contexts_Labeling_Files"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.7. Contextos de SELinux - Etiquetado de Archivos</h2></div></div></div><div class="para">
+			On systems running SELinux, all processes and files are labeled in a way that represents security-relevant information. This information is called the SELinux context. For files, this is viewed using the <code class="command">ls -Z</code> command:
 		</div><pre class="screen">$ ls -Z file1
 -rw-rw-r--  user1 group1 unconfined_u:object_r:user_home_t:s0 file1
 
@@ -10,15 +10,15 @@
 		</div><div class="para">
 			Hay muchos comandos para la administración del contexto de archivos de SELinux, como por ejemplo <code class="command">chcon</code>, <code class="command">semanage fcontext</code>, y <code class="command">restorecon</code>.
 		</div><div class="section" title="5.7.1. Cambios Temporales: chcon" id="sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Temporary_Changes_chcon"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.7.1. Cambios Temporales: chcon</h3></div></div></div><div class="para">
-				El comando <code class="command">chcon</code> cambia el contexto SELinux de los archivos. Estos cambios no sobreviven un reetiquetado del sistema de archivo, o la ejecución del comando <code class="command">/sbin/restorecon</code>. La política de SELinux controla si los usuarios pueden modificar el contexto SELinux de algún archivo. Cuando se usa <code class="command">chcon</code>, los usuarios proveen toda o parte del contexto SELinux a cambiar. Un tipo de archivo incorrecto es una causa común de negación de acceso de SELinux.
-			</div><div class="formalpara"><h5 class="formalpara">Referencia Rápida</h5>
+				The <code class="command">chcon</code> command changes the SELinux context for files. However, changes made with the <code class="command">chcon</code> command do not survive a file system relabel, or the execution of the <code class="command">/sbin/restorecon</code> command. SELinux policy controls whether users are able to modify the SELinux context for any given file. When using <code class="command">chcon</code>, users provide all or part of the SELinux context to change. An incorrect file type is a common cause of SELinux denying access.
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Temporary_Changes_chcon-Quick_Reference"><h5 class="formalpara">Referencia Rápida</h5>
 					<div class="itemizedlist"><ul><li class="listitem"><div class="para">
 								Ejecute el comando <code class="command">chcon -t <em class="replaceable"><code>tipo</code></em> <em class="replaceable"><code>nombre-de-archivo</code></em></code> para cambiar el tipo de archivo, donde <em class="replaceable"><code>tipo</code></em> es el tipo, por ejemplo <code class="computeroutput">httpd_sys_content_t</code>, y <em class="replaceable"><code>nombre-de-archivo</code></em> es un nombre de archivo o de directorio.
 							</div></li><li class="listitem"><div class="para">
 								Ejecute el comando <code class="command">chcon -R -t <em class="replaceable"><code>tipo</code></em> <em class="replaceable"><code>nombre-de-directorio</code></em></code> para cambiar el tipo de un directorio y su contenido, donde <em class="replaceable"><code>tipo</code></em> es el tipo, por ejemplo <code class="computeroutput">httpd_sys_content_t</code>, y <em class="replaceable"><code>nombre-de-directorio</code></em> es un nombre de directorio.
 							</div></li></ul></div>
 
-				</div><div class="formalpara"><h5 class="formalpara">Changing a File's or Directory's Type</h5>
+				</div><div class="formalpara" id="form-Security-Enhanced_Linux-Temporary_Changes_chcon-Changing_a_Files_or_Directorys_Type"><h5 class="formalpara">Changing a File's or Directory's Type</h5>
 					El siguiente ejemplo muestra el cambio de tipo solamente en el contexto de SELinux:
 				</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
 						Ejecute el comando <code class="command">cd</code> sin argumentos para cambiar a su directorio de inicio.
@@ -28,7 +28,7 @@
 -rw-rw-r--  user1 group1 unconfined_u:object_r:user_home_t:s0 file1
 
 </pre><div class="para">
-						En este ejemplo, el contexto SELinux del <code class="filename">archivo1</code> incluye el usuario <code class="computeroutput">unconfined_u</code>, el rol <code class="computeroutput">object_r</code>, el tipo <code class="computeroutput">user_home_t</code>, y el nivel <code class="computeroutput">s0</code>. Para una descripción de cada parte del contexto SELinux, vaya a <a class="xref" href="chap-Security-Enhanced_Linux-SELinux_Contexts.html" title="Capítulo 3. Contextos de SELinux">Capítulo 3, <i>Contextos de SELinux</i></a>.
+						In this example, the SELinux context for <code class="filename">file1</code> includes the SELinux <code class="computeroutput">unconfined_u</code> user, <code class="computeroutput">object_r</code> role, <code class="computeroutput">user_home_t</code> type, and the <code class="computeroutput">s0</code> level. For a description of each part of the SELinux context, refer to <a class="xref" href="chap-Security-Enhanced_Linux-SELinux_Contexts.html" title="Capítulo 3. Contextos de SELinux">Capítulo 3, <i>Contextos de SELinux</i></a>.
 					</div></li><li class="listitem"><div class="para">
 						EJecute el comando <code class="command">chcon -t samba_share_t archivo1</code> para cambiar el tipo a <code class="computeroutput">samba_share_t</code>. La opción <code class="option">-t</code> sólo cambia el tipo. Vea el cambio con <code class="command">ls -Z archivo1</code>:
 					</div><pre class="screen">$ ls -Z file1 
@@ -43,7 +43,7 @@ restorecon reset file1 context unconfined_u:object_r:samba_share_t:s0-&gt;system
 						En este ejemplo, el tipo previo <code class="computeroutput">samba_share_t</code>, se restaura al tipo correcto <code class="computeroutput">user_home_t</code>. Cuando se usa la política destinada (la política SELinux predeterminada en Fedora 11), el comando <code class="command">/sbin/restorecon</code> lee los archivos en el directorio <code class="filename">/etc/selinux/targeted/contexts/files/</code> para ver qué contexto de SELinux deben tener los archivos.
 					</div></li></ol></div><div class="para">
 				El ejemplo en esta sección funciona igual para directorios, por ejemplo, si <code class="filename">archivo1</code> fuera un directorio.
-			</div><div class="formalpara"><h5 class="formalpara">Cambio de un Directorio y sus Tipos de Contenidos</h5>
+			</div><div class="formalpara" id="form-Security-Enhanced_Linux-Temporary_Changes_chcon-Changing_a_Directory_and_its_Contents_Types"><h5 class="formalpara">Cambio de un Directorio y sus Tipos de Contenidos</h5>
 					The following example demonstrates creating a new directory, and changing the directory's file type (along with its contents) to a type used by the Apache HTTP Server. The configuration in this example is used if you want Apache HTTP Server to use a different document root (instead of <code class="filename">/var/www/html/</code>):
 				</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
 						Como usuario root de Linux, ejecute el comando <code class="command">mkdir /web</code> para crear un directorio nuevo, y luego el comando <code class="command">touch /web/archivo{1,2,3}</code> para crear 3 archivos vacíos (<code class="filename">archivo1</code>, <code class="filename">archivo2</code> y <code class="filename">archivo3</code>). El directorio <code class="filename">/web/</code> y los archivos en él son etiquetados con el tipo <code class="computeroutput">default_t</code>:
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes.html
index c2dcc75..451118a 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes.html
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.5. Modos de SELinux</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html" title="Capítulo 5. Trabajando con SELinux" /><link rel="prev" href="sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux.html" title="5.4.2. Deshabilitando SELinux" /><link rel="next" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html" title="5.6. Booleanos" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocfr
 ame" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.5. Modos de SELinux" id="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.5. Modos de SELinux</h2></div></div></div
 ><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.5. Modos de SELinux</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html" title="Capítulo 5. Trabajando con SELinux" /><link rel="prev" href="sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux.html" title="5.4.2. Deshabilitando SELinux" /><link rel="next" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html" title="5.6. Booleanos" /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id=
 "tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.5. Modos de SELinux" id="sect-Security-Enhanced_Linux-Working_with_SELinux-SELinux_Modes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.5. Modos de SELinux</h2></div></div
 ></div><div class="para">
 			SELinux tiene tres modos:
 		</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
 					Obligatorio: la política de SELinux es obligatoria. SELinux niega el acceso basado en las reglas de políticas de SELinux.
@@ -11,5 +11,5 @@
 				</div></li></ul></div><div class="para">
 			Use el comando <code class="command">/usr/sbin/setenforce</code> para cambiar entre los modos obediente y permisivo. Los cambios hechos con <code class="command">/usr/sbin/setenforce</code> no sobreviven a una reiniciada. Para cambiar a modo obediente, como usuario root de Linux, ejecute el comando <code class="command">/usr/sbin/setenforce 1</code>. Para cambiar a modo permisivo, ejecute el comando <code class="command">/usr/sbin/setenforce 0</code>. Use el comando <code class="command">/usr/sbin/getenforce</code> para ver el modo de SELinux actual.
 		</div><div class="para">
-			Los cambios de modo persistentes se cubren en <a class="xref" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html" title="5.4. Habilitando y Deshabilitando SELinux">Sección 5.4, “Habilitando y Deshabilitando SELinux”</a>.
+			Persistent mode changes are covered in <a class="xref" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Enabling_and_Disabling_SELinux.html" title="5.4. Habilitando y Deshabilitando SELinux">Sección 5.4, “Habilitando y Deshabilitando SELinux”</a>.
 		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-Enabling_and_Disabling_SELinux-Disabling_SELinux.html"><strong>Anterior</strong>5.4.2. Deshabilitando SELinux</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Booleans.html"><strong>Siguiente</strong>5.6. Booleanos</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types.html
index cb04ffd..93257bd 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_default_t_Types.html
@@ -1,9 +1,9 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.8. Los tipos file_t y default_t</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html" title="Capítulo 5. Trabajando con SELinux" /><link rel="prev" href="sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext.html" title="5.7.2. Cambios Persistentes: semanage fcontext" /><link rel="next" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html" title="5.9. Montaje de Sistemas de Archivos
 " /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.8. Los tipos file_t y default_t" id="sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_and_de
 fault_t_Types"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.8. Los tipos file_t y default_t</h2></div></div></div><div class="para">
-			En sistemas de archivo que soportan atributos extendidos, cuando se accede a un archivo en disco al que le falta el contexto de SELinux, se trata como si tuviera un contexto predeterminado tal como fue definido en la política de SELinux. En políticas comunes, este conexto por defecto usa el tipo <code class="computeroutput">file_t</code>. Este debería ser el único uso de este tipo, por lo que los archivos sin un contexto en el disco se podrían distinguir en la política, y generalmente mantenerse inaccesibles a dominios confinados. El tipo <code class="computeroutput">file_t</code> no debería existir en sistemas de archivo correctamente etiquetados, porque todos los archivos en un sistema corriendo SELinux deberían tener un contexto de SELinux, y el tipo <code class="computeroutput">file_t</code> no sebería usarse en la configuración de contexto de archivos <sup>[<a id="id893413" href="#ftn.id893413" class="footnote">10</a>]</sup>.
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.8. Los tipos file_t y default_t</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html" title="Capítulo 5. Trabajando con SELinux" /><link rel="prev" href="sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext.html" title="5.7.2. Cambios Persistentes: semanage fcontext" /><link rel="next" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html" title="5.9. Montaje de Sistemas de Archivos
 " /></head><body class="draft toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.8. Los tipos file_t y default_t" id="sect-Security-Enhanced_Linux-Working_with_SELinux-The_file_t_
 and_default_t_Types"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.8. Los tipos file_t y default_t</h2></div></div></div><div class="para">
+			For file systems that support extended attributes, when a file that lacks an SELinux context on disk is accessed, it is treated as if it had a default context as defined by SELinux policy. In common policies, this default context uses the <code class="computeroutput">file_t</code> type. This should be the only use of this type, so that files without a context on disk can be distinguished in policy, and generally kept inaccessible to confined domains. The <code class="computeroutput">file_t</code> type should not exist on correctly-labeled file systems, because all files on a system running SELinux should have an SELinux context, and the <code class="computeroutput">file_t</code> type is never used in file-context configuration<sup>[<a id="id1077049" href="#ftn.id1077049" class="footnote">10</a>]</sup>.
 		</div><div class="para">
-			El tipo <code class="computeroutput">default_t</code> se usa en archivos que no coinciden con ningún otro patrón en la configuración de contexto de archivo, por lo que tales archivos se pueden distinguir de aquellos que no tienen un contexto en el disco, y generalmente mantenerse inaccesibles a los dominios confinados. Si crea un directorio de alto nivel, tal como <code class="filename">/midir/</code>, este directorio puede ser etiquetado con el tipo <code class="computeroutput">default_t</code>. Si los servicios necesitan acceder a tal directorio, actualice la configuración de contextos de archivo para esta ubicación. Vaya a <a class="xref" href="sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext.html" title="5.7.2. Cambios Persistentes: semanage fcontext">Sección 5.7.2, “Cambios Persistentes: semanage fcontext”</a> para más detalles sobre el agregado de un contexto para la configuración de contexto de archivos.
-		</div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id893413" href="#id893413" class="para">10</a>] </sup>
-				Los archivos en <code class="filename">/etc/selinux/targeted/contexts/files/</code> definen los contextos de los archivos y directorios. Los archivos en este directorio son accedidos por <code class="command">restorecon</code> y por <code class="command">setfiles</code> para restaurar al valor predeterminado los contextos de los archivos y directorios.
+			The <code class="computeroutput">default_t</code> type is used on files that do not match any other pattern in file-context configuration, so that such files can be distinguished from files that do not have a context on disk, and generally kept inaccessible to confined domains. If you create a new top-level directory, such as <code class="filename">/mydirectory/</code>, this directory may be labeled with the <code class="computeroutput">default_t</code> type. If services need access to such a directory, update the file-contexts configuration for this location. Refer to <a class="xref" href="sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext.html" title="5.7.2. Cambios Persistentes: semanage fcontext">Sección 5.7.2, “Cambios Persistentes: semanage fcontext”</a> for details on adding a context to the file-context configuration.
+		</div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id1077049" href="#id1077049" class="para">10</a>] </sup>
+				Files in <code class="filename">/etc/selinux/targeted/contexts/files/</code> define contexts for files and directories. Files in this directory are read by <code class="command">restorecon</code> and <code class="command">setfiles</code> to restore files and directories to their default contexts.
 			</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security-Enhanced_Linux-SELinux_Contexts_Labeling_Files-Persistent_Changes_semanage_fcontext.html"><strong>Anterior</strong>5.7.2. Cambios Persistentes: semanage fcontext</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Mounting_File_Systems.html"><strong>Siguiente</strong>5.9. Montaje de Sistemas de Archivos</a></li></ul></body></html>
diff --git a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used.html b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used.html
index 605a2e3..a4b6697 100644
--- a/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used.html
+++ b/public_html/es-ES/Fedora/13/html/Security-Enhanced_Linux/sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used.html
@@ -1,20 +1,20 @@
 <?xml version="1.0" encoding="UTF-8" standalone="no"?>
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.2. Qué Archivo Log se usa</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.5-2" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html" title="Capítulo 5. Trabajando con SELinux" /><link rel="prev" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html" title="Capítulo 5. Trabajando con SELinux" /><link rel="next" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Main_Configuration_File.html" title="5.3. Archivo de Configuración Principal" /></head><body class="toc_embeded "><div id="tocdiv" cla
 ss="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Main_Configuration_File.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.2. Qué Archivo Log se usa" id="sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.2. Qué Arch
 ivo Log se usa</h2></div></div></div><div class="para">
-			En Fedora 13, los paquetes <span class="package">dbus</span>, <span class="package">setroubleshoot-server</span> y <span class="package">audit</span> se instalan si no son eliminados de la selección de paquetes predeterminada.
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.2. Qué Archivo Log se usa</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security-Enhanced_Linux-13-es-ES-1.4-1" /><link rel="home" href="index.html" title="Linux con Seguridad Mejorada" /><link rel="up" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html" title="Capítulo 5. Trabajando con SELinux" /><link rel="prev" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html" title="Capítulo 5. Trabajando con SELinux" /><link rel="next" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Main_Configuration_File.html" title="5.3. Archivo de Configuración Principal" /></head><body class="draft toc_embeded "><div id="tocdi
 v" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security-Enhanced_Linux-Working_with_SELinux.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security-Enhanced_Linux-Working_with_SELinux-Main_Configuration_File.html"><strong>Siguiente</strong></a></li></ul><div class="section" title="5.2. Qué Archivo Log se usa" id="sect-Security-Enhanced_Linux-Working_with_SELinux-Which_Log_File_is_Used"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.2. QuÃ
 © Archivo Log se usa</h2></div></div></div><div class="para">
+			In Fedora 13, the <span class="package">dbus</span>, <span class="package">setroubleshoot-server</span> and <span class="package">audit</span> packages are installed if packages are not removed from the default package selection.
 		</div><div class="para">
 			Los mensajes de negación de SELinux, tales como el siguiente, se escriben por defecto en <code class="filename">/var/log/audit/audit.log</code>:
 		</div><pre class="screen">type=AVC msg=audit(1223024155.684:49): avc:  denied  { getattr } for  pid=2000 comm="httpd" path="/var/www/html/file1" dev=dm-0 ino=399185 scontext=unconfined_u:system_r:httpd_t:s0 tcontext=system_u:object_r:samba_share_t:s0 tclass=file
 
 </pre><div class="para">
-			También, si <code class="systemitem">setroubleshootd</code> está ejecutándose, los mensajes de negación desde <code class="filename">/var/log/audit/audit.log</code> se traducen a una forma más fácil de leer en <code class="filename">/var/log/messages</code>:
+			Also, if <code class="systemitem">setroubleshootd</code> is running, denial messages from <code class="filename">/var/log/audit/audit.log</code> are translated to an easier-to-read form and sent to <code class="filename">/var/log/messages</code>:
 		</div><pre class="screen">May  7 18:55:56 localhost setroubleshoot: SELinux is preventing httpd (httpd_t) "getattr" to /var/www/html/file1 (samba_share_t). For complete SELinux messages. run sealert -l de7e30d6-5488-466d-a606-92c9f40d316d
 
 </pre><div class="para">
 			In Fedora 13, <code class="systemitem">setroubleshootd</code> no longer constantly runs as a service, however it is still used to analyze the AVC messages. Two new programs act as a method to start setroubleshoot when needed: <code class="systemitem">sedispatch</code> and <code class="systemitem">seapplet</code>. <code class="systemitem">sedispatch</code> runs as part of the audit subsystem, and via <code class="systemitem">dbus</code>, sends a message when an AVC denial occurs, which will go straight to <code class="systemitem">setroubleshootd</code> if it is already running, or it will start <code class="systemitem">setroubleshootd</code> if it is not running. <code class="systemitem">seapplet</code> is a tool which runs in the system's toolbar, waiting for dbus messages in <code class="systemitem">setroubleshootd</code>, and will launch the notification bubble, allowing the user to review the denial.
 		</div><div class="para">
 			Los mensajes de negación se envían a una ubicación distinta, dependiendo de cuáles demonios se están ejecutando:
-		</div><div class="segmentedlist"><table border="0"><thead><tr class="segtitle"><th>Demonio</th><th>Ubicación del Log</th></tr></thead><tbody><tr class="seglistitem"><td class="seg">auditd activado</td><td class="seg"><code class="filename">/var/log/audit/audit.log</code></td></tr><tr class="seglistitem"><td class="seg">auditd desactivado; rsyslogd activado</td><td class="seg"><code class="filename">/var/log/messages</code></td></tr><tr class="seglistitem"><td class="seg">rsyslogd y auditd activado</td><td class="seg"><code class="filename">/var/log/audit/audit.log</code>. Mensajes de negación legibles que también se envían a <code class="filename">/var/log/messages</code></td></tr></tbody></table></div><div class="formalpara"><h5 class="formalpara">Iniciando Demonios Automáticamente</h5>
+		</div><div class="segmentedlist"><table border="0"><thead><tr class="segtitle"><th>Daemon</th><th>Log Location</th></tr></thead><tbody><tr class="seglistitem"><td class="seg">auditd on</td><td class="seg"><code class="filename">/var/log/audit/audit.log</code></td></tr><tr class="seglistitem"><td class="seg">auditd off; rsyslogd on</td><td class="seg"><code class="filename">/var/log/messages</code></td></tr><tr class="seglistitem"><td class="seg">rsyslogd and auditd on</td><td class="seg"><code class="filename">/var/log/audit/audit.log</code>. Easier-to-read denial messages also sent to <code class="filename">/var/log/messages</code></td></tr></tbody></table></div><div class="formalpara" id="form-Security-Enhanced_Linux-Which_Log_File_is_Used-Starting_Daemons_Automatically"><h5 class="formalpara">Iniciando Demonios Automáticamente</h5>
 				Para configurar los demonios <code class="systemitem">auditd</code>, <code class="systemitem">rsyslogd</code>, y <code class="systemitem">setroubleshootd</code> para que inicien automáticamente al arrancar, corra los siguientes comandos como usuario root de Linux:
 			</div><pre class="screen">/sbin/chkconfig --levels 2345 auditd on
 
diff --git a/public_html/es-ES/Fedora/13/pdf/Security-Enhanced_Linux/Fedora-13-Security-Enhanced_Linux-es-ES.pdf b/public_html/es-ES/Fedora/13/pdf/Security-Enhanced_Linux/Fedora-13-Security-Enhanced_Linux-es-ES.pdf
index ddc94ad..9d7d869 100644
Binary files a/public_html/es-ES/Fedora/13/pdf/Security-Enhanced_Linux/Fedora-13-Security-Enhanced_Linux-es-ES.pdf and b/public_html/es-ES/Fedora/13/pdf/Security-Enhanced_Linux/Fedora-13-Security-Enhanced_Linux-es-ES.pdf differ
diff --git a/public_html/es-ES/toc.html b/public_html/es-ES/toc.html
index d2fdf8b..35435f4 100644
--- a/public_html/es-ES/toc.html
+++ b/public_html/es-ES/toc.html
@@ -210,7 +210,7 @@
 					</div>
 	        		
 					<div id='Fedora.13.Security-Enhanced_Linux' class="book collapsed" onclick="toggle(event, 'Fedora.13.Security-Enhanced_Linux.types');">
-						<a class="type" href="Fedora/13/html/Security-Enhanced_Linux/index.html" onclick="window.top.location='./Fedora/13/html/Security-Enhanced_Linux/index.html'"><span class="book">Security-Enhanced Linux</span></a> 
+						<a class="type" href="Fedora/13/html/Security-Enhanced_Linux/index.html" onclick="window.top.location='./Fedora/13/html/Security-Enhanced_Linux/index.html'"><span class="book">Linux con Seguridad Mejorada</span></a> 
 						<div id='Fedora.13.Security-Enhanced_Linux.types' class="types hidden" onclick="work=0;">
 						
 							<a class="type" href="./Fedora/13/epub/Security-Enhanced_Linux/Fedora-13-Security-Enhanced_Linux-es-ES.epub" >epub</a>
@@ -471,7 +471,7 @@
 					</div>
 	        		
 					<div id='Fedora.11.Security-Enhanced_Linux' class="book collapsed" onclick="toggle(event, 'Fedora.11.Security-Enhanced_Linux.types');">
-						<a class="type" href="Fedora/11/html/Security-Enhanced_Linux/index.html" onclick="window.top.location='./Fedora/11/html/Security-Enhanced_Linux/index.html'"><span class="book">Security-Enhanced Linux</span></a> 
+						<a class="type" href="Fedora/11/html/Security-Enhanced_Linux/index.html" onclick="window.top.location='./Fedora/11/html/Security-Enhanced_Linux/index.html'"><span class="book">Linux con Seguridad Mejorada</span></a> 
 						<div id='Fedora.11.Security-Enhanced_Linux.types' class="types hidden" onclick="work=0;">
 						
 							<a class="type" href="./Fedora/11/epub/Security-Enhanced_Linux/Fedora-11-Security-Enhanced_Linux-es-ES.epub" >epub</a>
diff --git a/public_html/toc.html b/public_html/toc.html
index 4a1f3dd..49dee3d 100644
--- a/public_html/toc.html
+++ b/public_html/toc.html
@@ -2386,7 +2386,7 @@
 						</div>
 	        			
 						<div class="book">
-							<span id="Security-Enhanced_Linux" class="book">Security-Enhanced Linux</span> 
+							<span id="Security-Enhanced_Linux" class="book">Linux con Seguridad Mejorada</span> 
 							<div class="types">
 							
 								<a class="type" href="./es-ES/Fedora/13/epub/Security-Enhanced_Linux/Fedora-13-Security-Enhanced_Linux-es-ES.epub">epub</a>
@@ -2647,7 +2647,7 @@
 						</div>
 	        			
 						<div class="book">
-							<span id="Security-Enhanced_Linux" class="book">Security-Enhanced Linux</span> 
+							<span id="Security-Enhanced_Linux" class="book">Linux con Seguridad Mejorada</span> 
 							<div class="types">
 							
 								<a class="type" href="./es-ES/Fedora/11/epub/Security-Enhanced_Linux/Fedora-11-Security-Enhanced_Linux-es-ES.epub">epub</a>


More information about the docs-commits mailing list