web/html/docs/security-guide/es_ES/single index.html,1.1,1.2

Wed Jul 29 22:22:00 UTC 2009

Author: sparks

Update of /cvs/fedora/web/html/docs/security-guide/es_ES/single
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv21079/es_ES/single

Modified Files:
	index.html 
Log Message:
Latest Spanish translation.



View full diff with command:
/usr/bin/cvs -f diff  -kk -u -N -r 1.1 -r 1.2 index.html
Index: index.html
===================================================================
RCS file: /cvs/fedora/web/html/docs/security-guide/es_ES/single/index.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2

--- index.html	28 Jul 2009 21:51:41 -0000	1.1
+++ index.html	29 Jul 2009 22:21:59 -0000	1.2
@@ -1,8 +1,8 @@
 <?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-guide</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="" /><meta name="description" content="The Linux Security Guide is designed to assist users of Linux in learning the processes and practices of securing workstations and servers against local and remote intrusion, exploitation, and malicious activity. The Linux Security Guide details the planning and the tools involved in creating a secured computing environment for the data center, workplace, and home. With proper administrative knowledge, vigilance, and tools, systems running Linux can be both fully functional and secured from most common intrusion and exploit methods." /></head><body class=""><div class="book" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div clas
 s="producttitle"><span class="productname">fedora</span> <span class="productnumber">11</span></div><div><h1 id="id237219" class="title">security-guide</h1></div><div><h2 class="subtitle">A Guide to Securing Fedora Linux</h2></div><p class="edition">EdiciÃ³n 1.0</p><div><h3 class="corpauthor">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>guÃa de seguridad</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="" /><meta name="description" content="La GuÃa de Seguridad Linux esta diseÃ±ada para asistir a usuarios de linux en el proceso de aprendizaje y prÃ¡cticas de seguridad en estaciones de trabajo y servidores contra intrusiones locales y remotas, explotaciones, y actividades maliciosas. La GuÃa de Seguridad Linux detalla la planificaciÃ³n y las herramientas involucradas en la creaciÃ³n de un entorno de computaciÃ³n seguro para centros de datos, estaciones de trabajo, y el hogar. Con conocimiento administrativo apropiado, vigilancia, y herramientas, sistemas corriendo Linux pueden ser a la vez completamente funcionales y seguros frente a los mÃ©todos de intrusiÃ³n y explotaciÃ
 ³n mas comunes." /></head><body class=""><div class="book" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div class="producttitle"><span class="productname">fedora</span> <span class="productnumber">11</span></div><div><h1 id="id339482" class="title">guÃa de seguridad</h1></div><div><h2 class="subtitle">Una guÃa para la seguridad en fedora</h2></div><p class="edition">EdiciÃ³n 1.0</p><div><h3 class="corpauthor">
 				<span class="inlinemediaobject"><object data="Common_Content/images/title_logo.svg" type="image/svg+xml"> Logo</object></span>
-			</h3></div><div><div class="authorgroup"><div class="author"><h3 class="author"><span class="firstname">Johnray</span> <span class="surname">Fuller</span></h3><div class="affiliation"><span class="orgname">Red Hat</span></div><code class="email"><a class="email" href="mailto:jrfuller at redhat.com">jrfuller at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="surname">Ha</span></h3><div class="affiliation"><span class="orgname">Red Hat</span></div><code class="email"><a class="email" href="mailto:jha at redhat.com">jha at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">David</span> <span class="surname">O'Brien</span></h3><div class="affiliation"><span class="orgname">Red Hat</span></div><code class="email"><a class="email" href="mailto:daobrien at redhat.com">daobrien 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></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">Eric</span> <span class="surname">Christensen</span></h3><div class="affiliation"><span class="orgname">Fedora Project</span> <span class="orgdiv">Documentation Team</span></div><code class="email"><a class="email" href="mailto:sparks at fedoraproject.org">sparks at fedoraproject.org</a></code></div></div></div><hr /><div><div id="id287416" class="legalnotice"><h1 class="legalnotice">aviso legal</h1><div class="para">
+			</h3></div><div><div class="authorgroup"><div class="author"><h3 class="author"><span class="firstname">Johnray</span> <span class="surname">Fuller</span></h3><div class="affiliation"><span class="orgname">Red Hat</span></div><code class="email"><a class="email" href="mailto:jrfuller at redhat.com">jrfuller at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="surname">Ha</span></h3><div class="affiliation"><span class="orgname">Red Hat</span></div><code class="email"><a class="email" href="mailto:jha at redhat.com">jha at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">David</span> <span class="surname">O'Brien</span></h3><div class="affiliation"><span class="orgname">Red Hat</span></div><code class="email"><a class="email" href="mailto:daobrien at redhat.com">daobrien 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></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">Eric</span> <span class="surname">Christensen</span></h3><div class="affiliation"><span class="orgname">Fedora Project</span> <span class="orgdiv">Documentation Team</span></div><code class="email"><a class="email" href="mailto:sparks at fedoraproject.org">sparks at fedoraproject.org</a></code></div></div></div><hr /><div><div id="id477824" class="legalnotice"><h1 class="legalnotice">aviso legal</h1><div class="para">
 		Copyright <span class="trademark"></span>Â© 2008 Red Hat, Inc. This material may only be distributed subject to the terms and conditions set forth in the Open Publication License, V1.0, (the latest version is presently available at <a href="http://www.opencontent.org/openpub/">http://www.opencontent.org/openpub/</a>).
 	</div><div class="para">
 		Fedora and the Fedora Infinity Design logo are trademarks or registered trademarks of Red Hat, Inc., in the U.S. and other countries.
@@ -12,19 +12,21 @@
 		All other trademarks and copyrights referred to are the property of their respective owners.
 	</div><div class="para">
 		Documentation, as with software itself, may be subject to export control. Read about Fedora Project export controls at <a href="http://fedoraproject.org/wiki/Legal/Export">http://fedoraproject.org/wiki/Legal/Export</a>. 
-	</div></div></div><div><div class="abstract"><h6>Resumen</h6><div class="para">The Linux Security Guide is designed to assist users of Linux in
-learning the processes and practices of securing workstations and
-servers against local and remote intrusion, exploitation, and
-malicious activity. The Linux Security Guide details the planning
-and the tools involved in creating a secured computing environment
-for the data center, workplace, and home. With proper
-administrative knowledge, vigilance, and tools, systems running
-Linux can be both fully functional and secured from most common
-intrusion and exploit methods.</div></div></div></div><hr /></div><div class="toc"><dl><dt><span class="preface"><a href="#pref-Security_Guide-Preface">Prefacio</a></span></dt><dd><dl><dt><span class="section"><a href="#id442720">1. Convenciones del documento</a></span></dt><dd><dl><dt><span class="section"><a href="#id382958">1.1. Convenciones tipogrÃ¡ficas</a></span></dt><dt><span class="section"><a href="#id407594">1.2. Convenciones del documento</a></span></dt><dt><span class="section"><a href="#id438216">1.3. Notas y advertencias</a></span></dt></dl></dd><dt><span class="section"><a href="#We_Need_Feedback">2. Â¡Se necesita retroalimentaciÃ³n!</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Security_Guide-Security_Overview">1. Security Overview</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Introduction_to_Security">1.1. Introduction to Security</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Gui
 de-Introduction_to_Security-What_is_Computer_Security">1.1.1. What is Computer Security?</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Introduction_to_Security-SELinux">1.1.2. SELinux</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Introduction_to_Security-Security_Controls">1.1.3. Security Controls</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Introduction_to_Security-Conclusion">1.1.4. ConclusiÃ³n</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Vulnerability_Assessment">1.2. Vulnerability Assessment</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Vulnerability_Assessment-Thinking_Like_the_Enemy">1.2.1. Pensado como el Enemigo</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Vulnerability_Assessment-Defining_Assessment_and_Testing">1.2.2. Definiendo EvaluaciÃ³n y Pruebas</a></span></dt><dt><span class="section"><a hre
 f="#sect-Security_Guide-Vulnerability_Assessment-Evaluating_the_Tools">1.2.3. Herramientas de EvaluaciÃ³n</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Attackers_and_Vulnerabilities">1.3. Attackers and Vulnerabilities</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Attackers_and_Vulnerabilities-A_Quick_History_of_Hackers">1.3.1. A Quick History of Hackers</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Network_Security">1.3.2. Threats to Network Security</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Server_Security">1.3.3. Threats to Server Security</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Workstation_and_Home_PC_Security">1.3.4. Threats to Workstation and Home PC Security</a></span></dt></dl></dd><dt><span class
 ="section"><a href="#sect-Security_Guide-Common_Exploits_and_Attacks">1.4. Ataques y Aprovechadas ComÃºnes</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Security_Updates">1.5. Actualizaciones de Seguridad</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Security_Updates-Updating_Packages">1.5.1. Updating Packages</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Updating_Packages-Verifying_Signed_Packages">1.5.2. Verifying Signed Packages</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Updating_Packages-Installing_Signed_Packages">1.5.3. Installing Signed Packages</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Updating_Packages-Applying_the_Changes">1.5.4. Applying the Changes</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#chap-Security_Guide-Securing_Your_Network">2. Securing Your Network</a></span></dt><dd><dl><dt><span class="s
 ection"><a href="#sect-Security_Guide-Workstation_Security">2.1. Workstation Security</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Workstation_Security-Evaluating_Workstation_Security">2.1.1. Evaluating Workstation Security</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Workstation_Security-BIOS_and_Boot_Loader_Security">2.1.2. BIOS and Boot Loader Security</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Workstation_Security-Password_Security">2.1.3. Password Security</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Workstation_Security-Administrative_Controls">2.1.4. Administrative Controls</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Workstation_Security-Available_Network_Services">2.1.5. Servicios de Red Disponibles</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Workstation_Security-Personal_Firewalls">2.1.6. Cortafuegos 
 Personal:</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Workstation_Security-Security_Enhanced_Communication_Tools">2.1.7. Security Enhanced Communication Tools</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Server_Security">2.2. Server Security</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Server_Security-Securing_Services_With_TCP_Wrappers_and_xinetd">2.2.1. Securing Services With TCP Wrappers and xinetd</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Server_Security-Securing_Portmap">2.2.2. Securing Portmap</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Server_Security-Securing_NIS">2.2.3. Securing NIS</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Server_Security-Securing_NFS">2.2.4. Securing NFS</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Server_Security-Securing_the_Apache_HTTP_Serv
 er">2.2.5. Securing the Apache HTTP Server</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Server_Security-Securing_FTP">2.2.6. Securing FTP</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Server_Security-Securing_Sendmail">2.2.7. Securing Sendmail</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Server_Security-Verifying_Which_Ports_Are_Listening">2.2.8. Verifying Which Ports Are Listening</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Single_Sign_on_SSO">2.3. Single Sign-on (SSO)</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Single_Sign_on_SSO-Introduction">2.3.1. IntroducciÃ³n</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Single_Sign_on_SSO-Getting_Started_with_your_new_Smart_Card">2.3.2. Getting Started with your new Smart Card</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Single_Sign_on_S
 SO-How_Smart_Card_Enrollment_Works">2.3.3. How Smart Card Enrollment Works</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Login_Works">2.3.4. How Smart Card Login Works</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Single_Sign_on_SSO-Configuring_Firefox_to_use_Kerberos_for_SSO">2.3.5. Configuring Firefox to use Kerberos for SSO</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Pluggable_Authentication_Modules_PAM">2.4. Pluggable Authentication Modules (PAM)</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Advantages_of_PAM">2.4.1. Advantages of PAM</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_Files">2.4.2. PAM Configuration Files</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Pluggable_Authenti
 cation_Modules_PAM-PAM_Configuration_File_Format">2.4.3. PAM Configuration File Format</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Sample_PAM_Configuration_Files">2.4.4. Sample PAM Configuration Files</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Creating_PAM_Modules">2.4.5. Creating PAM Modules</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Administrative_Credential_Caching">2.4.6. PAM and Administrative Credential Caching</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Device_Ownership">2.4.7. PAM and Device Ownership</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Additional_Resources">2.4.8. Additional Resources</a></span></dt></dl></dd><dt><span class="
 section"><a href="#sect-Security_Guide-TCP_Wrappers_and_xinetd">2.5. TCP Wrappers and xinetd</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers">2.5.1. TCP Wrappers</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers_Configuration_Files">2.5.2. TCP Wrappers Configuration Files</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd">2.5.3. xinetd</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd_Configuration_Files">2.5.4. xinetd Configuration Files</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-TCP_Wrappers_and_xinetd-Additional_Resources">2.5.5. Additional Resources</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Kerberos">2.6. Kerberos</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Se
 curity_Guide-Kerberos-What_is_Kerberos">2.6.1. Â¿QuÃ© es Kerberos?</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-Kerberos_Terminology">2.6.2. Kerberos Terminology</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-How_Kerberos_Works">2.6.3. How Kerberos Works</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-Kerberos_and_PAM">2.6.4. Kerberos y PAM</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Server">2.6.5. Configuring a Kerberos 5 Server</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Client">2.6.6. Configuring a Kerberos 5 Client</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-Domain_to_Realm_Mapping">2.6.7. Domain-to-Realm Mapping</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-Setting_Up_Secondary_KDCs"
 >2.6.8. Setting Up Secondary KDCs</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-Setting_Up_Cross_Realm_Authentication">2.6.9. Configurando la AutenticaciÃ³n Cruzada de Reinados</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-Additional_Resources">2.6.10. Additional Resources</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Virtual_Private_Networks_VPNs">2.7. Virtual Private Networks (VPNs)</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Virtual_Private_Networks_VPNs-How_Does_a_VPN_Work">2.7.1. How Does a VPN Work?</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Virtual_Private_Networks_VPNs-VPNs_and_PROD">2.7.2. VPNs and Fedora</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec">2.7.3. IPsec</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Virtual_P
 rivate_Networks_VPNs-Creating_an_IPsec_Connection">2.7.4. Creating an IPsec Connection</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Installation">2.7.5. IPsec Installation</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Host_to_Host_Configuration">2.7.6. IPsec Host-to-Host Configuration</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Network_to_Network_Configuration">2.7.7. IPsec Network-to-Network Configuration</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Virtual_Private_Networks_VPNs-Starting_and_Stopping_an_IPsec_Connection">2.7.8. Starting and Stopping an IPsec Connection</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Firewalls">2.8. Firewalls</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Firewalls-Netf
 ilter_and_IPTables">2.8.1. Netfilter e IPTables</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Firewalls-Basic_Firewall_Configuration">2.8.2. ConfiguraciÃ³n BÃ¡sica del Cortafuego</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Firewalls-Using_IPTables">2.8.3. Uso de IPTables</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Firewalls-Common_IPTables_Filtering">2.8.4. Filtrado ComÃºn de IPTalbes</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Firewalls-FORWARD_and_NAT_Rules">2.8.5. Reglas FORWARD y NAT</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Firewalls-Malicious_Software_and_Spoofed_IP_Addresses">2.8.6. Software Malicioso y SuplantaciÃ³n de Direcciones IP </a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Firewalls-IPTables_and_Connection_Tracking">2.8.7. IPTables y el Seguimiento de ConexiÃ³n</a></span></dt><dt><span class="section"><
 a href="#sect-Security_Guide-Firewalls-IPv6">2.8.8. IPv6</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Firewalls-Additional_Resources">2.8.9. Additional Resources</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-IPTables">2.9. IPTables</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-IPTables-Packet_Filtering">2.9.1. Filtrado de Paquete</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-IPTables-Differences_Between_IPTables_and_IPChains">2.9.2. Differences Between IPTables and IPChains</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-IPTables-Command_Options_for_IPTables">2.9.3. Command Options for IPTables</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-IPTables-Saving_IPTables_Rules">2.9.4. Saving IPTables Rules</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-IPTables-IPTables_Control_Scripts">2.9.5. 
 IPTables Control Scripts</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-IPTables-IPTables_and_IPv6">2.9.6. IPTables y IPv6</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-IPTables-Additional_Resources">2.9.7. Additional Resources</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#chap-Security_Guide-Encryption">3. Encryption</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Encryption-Data_at_Rest">3.1. Datos en Descanso</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Encryption-Protecting_Data_at_Rest-Full_Disk_Encryption">3.2. EncriptaciÃ³n Completa de Disco</a></span></dt><dt><span class="section"><a href="#Security_Guide-Encryption-Protecting_Data_at_Rest-File_Based_Encryption">3.3. EncriptaciÃ³n Basada en Archivo</a></span></dt><dt><span class="section"><a href="#Security_Guide-Encryption-Data_in_Motion">3.4. Datos en Movimiento</a></span></dt><dt><span
  class="section"><a href="#Security_Guide-Encryption-Data_in_Motion-Virtual_Private_Networks">3.5. Virtual Private Networks</a></span></dt><dt><span class="section"><a href="#Security_Guide-Encryption-Data_in_Motion-Secure_Shell">3.6. Shell Seguro</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-LUKS_Disk_Encryption">3.7. LUKS Disk Encryption</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-LUKS_Disk_Encryption-LUKS_Implementation_in_Fedora">3.7.1. LUKS Implementation in Fedora</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories">3.7.2. Manually Encrypting Directories</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-Step_by_Step_Instructions">3.7.3. Step-by-Step Instructions</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encry
 pting_Directories-What_you_have_just_accomplished">3.7.4. What you have just accomplished.</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-LUKS_Disk_Encryption-Links_of_Interest">3.7.5. Links of Interest</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives">3.8. 7-Zip Encrypted Archives</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Installation">3.8.1. 7-Zip Installation in Fedora</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Installation-Instructions">3.8.2. Step-by-Step Installation Instructions</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Usage_Instructions">3.8.3. Step-by-Step Usage Instructions</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Encryption-7_Zip_Encrypted_Archi
 ves-Things_of_note">3.8.4. Things of note</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Encryption-Using_GPG">3.9. Using GNU Privacy Guard (GnuPG)</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Encryption-Using_GPG-Keys_in_GNOME">3.9.1. Creating GPG Keys in GNOME</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE1">3.9.2. Creating GPG Keys in KDE</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE">3.9.3. Creating GPG Keys Using the Command Line</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Encryption-Using_GPG-About_Public_Key_Encryption">3.9.4. About Public Key Encryption</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#chap-Security_Guide-General_Principles_of_Information_Security">4. Principios Generales sobre la Seguridad de la I
 nformaciÃ³n</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-General_Principles_of_Information_Security-Tips_Guides_and_Tools">4.1. Consejos, GuÃas y Herramientas</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Security_Guide-Secure_Installation">5. Secure Installation</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Secure_Installation-Disk_Partitions">5.1. Disk Partitions</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Secure_Installation-Utilize_LUKS_Partition_Encryption">5.2. Utilize LUKS Partition Encryption</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Security_Guide-Software_Maintenance">6. Mantenimiento de Software</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Software_Maintenance-Install_Minimal_Software">6.1. Install Minimal Software</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Software_
 Maintenance-Plan_and_Configure_Security_Updates">6.2. Plan and Configure Security Updates</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates-Adjusting_Automatic_Updates">6.3. Ajustando Actualizaciones AutomÃ¡ticas</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Software_Maintenance-Install_Signed_Packages_from_Well_Known_Repositories">6.4. Install Signed Packages from Well Known Repositories</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Security_Guide-References">7. Referencias</a></span></dt></dl></div><div class="preface" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h1 id="pref-Security_Guide-Preface" class="title">Prefacio</h1></div></div></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h2 class="title" id="id442720">1. Convenciones del documento</h2></div></div></div><div class="para">
+	</div></div></div><div><div class="abstract"><h6>Resumen</h6><div class="para">La GuÃa de Seguridad Linux esta diseÃ±ada para asistir a usuarios de
+linux en el proceso de aprendizaje y prÃ¡cticas de seguridad en
+estaciones de trabajo y servidores contra intrusiones locales y
+remotas, explotaciones, y actividades maliciosas. La GuÃa de
+Seguridad Linux detalla la planificaciÃ³n y las herramientas
+involucradas en la creaciÃ³n de un entorno de computaciÃ³n seguro
+para centros de datos, estaciones de trabajo, y el hogar. Con
+conocimiento administrativo apropiado, vigilancia, y herramientas,
+sistemas corriendo Linux pueden ser a la vez completamente
+funcionales y seguros frente a los mÃ©todos de intrusiÃ³n y
+explotaciÃ³n mas comunes.</div></div></div></div><hr /></div><div class="toc"><dl><dt><span class="preface"><a href="#pref-Security_Guide-Preface">Prefacio</a></span></dt><dd><dl><dt><span class="section"><a href="#id544690">1. Convenciones del documento</a></span></dt><dd><dl><dt><span class="section"><a href="#id527876">1.1. Convenciones tipogrÃ¡ficas</a></span></dt><dt><span class="section"><a href="#id497366">1.2. Convenciones del documento</a></span></dt><dt><span class="section"><a href="#id510897">1.3. Notas y advertencias</a></span></dt></dl></dd><dt><span class="section"><a href="#We_Need_Feedback">2. Â¡Necesitamos retroalimentaciÃ³n!</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Security_Guide-Security_Overview">1. Repaso sobre seguridad</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Introduction_to_Security">1.1. IntroducciÃ³n a la Seguridad</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security
 _Guide-Introduction_to_Security-What_is_Computer_Security">1.1.1. Â¿QuÃ© es la Seguridad de Computadoras?</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Introduction_to_Security-SELinux">1.1.2. SELinux</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Introduction_to_Security-Security_Controls">1.1.3. Controles de seguridad</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Introduction_to_Security-Conclusion">1.1.4. ConclusiÃ³n</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Vulnerability_Assessment">1.2. EvaluaciÃ³n de debilidades</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Vulnerability_Assessment-Thinking_Like_the_Enemy">1.2.1. Pensado como el enemigo</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Vulnerability_Assessment-Defining_Assessment_and_Testing">1.2.2. Definiendo evaluaciÃ³n y pruebas</a></span></dt><dt><spa
 n class="section"><a href="#sect-Security_Guide-Vulnerability_Assessment-Evaluating_the_Tools">1.2.3. Herramientas de evaluaciÃ³n</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Attackers_and_Vulnerabilities">1.3. Atacantes y vulnerabilidades</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Attackers_and_Vulnerabilities-A_Quick_History_of_Hackers">1.3.1. Una breve reseÃ±a acerca de los hackers</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Network_Security">1.3.2. Amenazas a la seguridad de la red</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Server_Security">1.3.3. Amenazas a la Seguridad del Servidor</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Workstation_and_Home_PC_Security">1.3.4. Amenazas a las Estaciones de Tra
 bajo y Seguridad en Equipos HogareÃ±os</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Common_Exploits_and_Attacks">1.4. Ataques y debilidades comunes</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Security_Updates">1.5. Actualizaciones de seguridad</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Security_Updates-Updating_Packages">1.5.1. ActualizaciÃ³n de paquetes</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Updating_Packages-Verifying_Signed_Packages">1.5.2. VerificaciÃ³n de Paquetes Firmados</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Updating_Packages-Installing_Signed_Packages">1.5.3. InstalaciÃ³n de paquetes firmados</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Updating_Packages-Applying_the_Changes">1.5.4. AplicaciÃ³n de los cambios</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#c
 hap-Security_Guide-Securing_Your_Network">2. Asegurando su Red</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Workstation_Security">2.1. Seguridad de la estaciÃ³n de trabajo</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Workstation_Security-Evaluating_Workstation_Security">2.1.1. EvaluaciÃ³n de la seguridad de la estaciÃ³n de trabajo</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Workstation_Security-BIOS_and_Boot_Loader_Security">2.1.2. Seguridad en el BIOS y en el gestor de arranque</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Workstation_Security-Password_Security">2.1.3. Seguridad de contraseÃ±nas</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Workstation_Security-Administrative_Controls">2.1.4. Controles administrativos</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Workstation_Security-Available_Network_Servi
 ces">2.1.5. Servicios de red disponibles</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Workstation_Security-Personal_Firewalls">2.1.6. Cortafuegos Personal:</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Workstation_Security-Security_Enhanced_Communication_Tools">2.1.7. Herramientas de comunicaciÃ³n de seguridad mejorada</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Server_Security">2.2. Seguridad del servidor</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Server_Security-Securing_Services_With_TCP_Wrappers_and_xinetd">2.2.1. Asegurando los servicios con encapsuladores TCP y xinetd</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Server_Security-Securing_Portmap">2.2.2. Asegurando Portmap</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Server_Security-Securing_NIS">2.2.3. Asegurando NIS</a></span></dt><dt><span class
 ="section"><a href="#sect-Security_Guide-Server_Security-Securing_NFS">2.2.4. Asegurando el NFS</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Server_Security-Securing_the_Apache_HTTP_Server">2.2.5. Asegurando al Servidor HTTP Apache</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Server_Security-Securing_FTP">2.2.6. Asegurando FTP</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Server_Security-Securing_Sendmail">2.2.7. Asegurando Sendmail</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Server_Security-Verifying_Which_Ports_Are_Listening">2.2.8. Verificar quÃ© puertos estÃ¡n abiertos</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Single_Sign_on_SSO">2.3. IdentificaciÃ³n Ãºnica (SSO por single sign-on)</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Single_Sign_on_SSO-Introduction">2.3.1. IntroducciÃ³n</a></span></dt><dt
 ><span class="section"><a href="#sect-Security_Guide-Single_Sign_on_SSO-Getting_Started_with_your_new_Smart_Card">2.3.2. Empezar a utilizar su nueva tarjeta inteligente</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Enrollment_Works">2.3.3. Como funciona la inscripciÃ³n de las tarjetas inteligentes.</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Login_Works">2.3.4. CÃ³mo funciona el ingreso con tarjeta inteligente</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Single_Sign_on_SSO-Configuring_Firefox_to_use_Kerberos_for_SSO">2.3.5. Configurar Firefox para la utilizaciÃ³n de Kerberos como SSO</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Pluggable_Authentication_Modules_PAM">2.4. MÃ³dulos de AutenticaciÃ³n Conectables (PAM)</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Plug
 gable_Authentication_Modules_PAM-Advantages_of_PAM">2.4.1. Ventajas de PAM</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_Files">2.4.2. Archivos de ConfiguraciÃ³n de PAM</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_File_Format">2.4.3. Formato del Archivo de ConfiguraciÃ³n de PAM</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Sample_PAM_Configuration_Files">2.4.4. Mueestra de Archivos de ConfiguraciÃ³n de PAM</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Creating_PAM_Modules">2.4.5. CreaciÃ³n de los MÃ³dulos PAM</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Administrative_Credential_Caching">2.4.6. PAM y el Cacheo de la Credencia
 l Administrativa</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Device_Ownership">2.4.7. PAM y la propiedad de los dispositivos</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Additional_Resources">2.4.8. Recursos Adicionales</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-TCP_Wrappers_and_xinetd">2.5. Encapsuladores TCP y xinetd</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers">2.5.1. Encapsuladores TCP</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers_Configuration_Files">2.5.2. Archivos de configuraciÃ³n de los encapsuladores TCP</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd">2.5.3. xinetd</a></span></dt><dt><span class="section"><a hr
 ef="#sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd_Configuration_Files">2.5.4. Archivos de configuraciÃ³n de xinetd</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-TCP_Wrappers_and_xinetd-Additional_Resources">2.5.5. Recursos Adicionales</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Kerberos">2.6. Kerberos</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-What_is_Kerberos">2.6.1. Â¿QuÃ© es Kerberos?</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-Kerberos_Terminology">2.6.2. TerminologÃa de Kerberos</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-How_Kerberos_Works">2.6.3. Como Funciona Kerberos</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-Kerberos_and_PAM">2.6.4. Kerberos y PAM</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-Configuring_a_Kerber
 os_5_Server">2.6.5. Configurando un servidor Kerberos 5</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Client">2.6.6. ConfiguraciÃ³n de un Cliente Kerberos 5</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-Domain_to_Realm_Mapping">2.6.7. Mapeo Dominio-a-Reinado</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-Setting_Up_Secondary_KDCs">2.6.8. Configurando KDCs secundarios</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-Setting_Up_Cross_Realm_Authentication">2.6.9. Configurando la AutenticaciÃ³n Cruzada de Reinados</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-Additional_Resources">2.6.10. Recursos Adicionales</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Virtual_Private_Networks_VPNs">2.7. Redes privadas virtuales (VPNs, por las iniciales en inglÃ©s de Virt
 ual Private Networks)</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Virtual_Private_Networks_VPNs-How_Does_a_VPN_Work">2.7.1. Â¿CÃ³mo funciona una VPN?</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Virtual_Private_Networks_VPNs-VPNs_and_PROD">2.7.2. VPNs y Fedora</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec">2.7.3. IPsec</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Virtual_Private_Networks_VPNs-Creating_an_IPsec_Connection">2.7.4. Creando una conexiÃ³n IPsec</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Installation">2.7.5. InstalaciÃ³n de IPsec</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Host_to_Host_Configuration">2.7.6. ConfiguraciÃ³n de IPsec equipo-a-equipo</a></span></dt><dt><span class="section"><a href
 ="#sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Network_to_Network_Configuration">2.7.7. ConfiguraciÃ³n IPsec red-a-red</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Virtual_Private_Networks_VPNs-Starting_and_Stopping_an_IPsec_Connection">2.7.8. Iniciar y detener una conexiÃ³n IPsec</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Firewalls">2.8. Cortafuegos</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Firewalls-Netfilter_and_IPTables">2.8.1. Netfilter e IPTables</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Firewalls-Basic_Firewall_Configuration">2.8.2. ConfiguraciÃ³n BÃ¡sica del Cortafuego</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Firewalls-Using_IPTables">2.8.3. Uso de IPTables</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Firewalls-Common_IPTables_Filtering">2.8.4. Filtrado ComÃºn de IPTables<
 /a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Firewalls-FORWARD_and_NAT_Rules">2.8.5. Reglas FORWARD y NAT</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Firewalls-Malicious_Software_and_Spoofed_IP_Addresses">2.8.6. Software Malicioso y SuplantaciÃ³n de Direcciones IP </a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Firewalls-IPTables_and_Connection_Tracking">2.8.7. IPTables y el Seguimiento de ConexiÃ³n</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Firewalls-IPv6">2.8.8. IPv6</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Firewalls-Additional_Resources">2.8.9. Recursos Adicionales</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-IPTables">2.9. IPTables</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-IPTables-Packet_Filtering">2.9.1. Filtrado de Paquete</a></span></dt><dt><span class="section">
 <a href="#sect-Security_Guide-IPTables-Differences_Between_IPTables_and_IPChains">2.9.2. Diferencias entre IPTables y IPChains</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-IPTables-Command_Options_for_IPTables">2.9.3. Opciones de la lÃnea de comandos de IPTables</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-IPTables-Saving_IPTables_Rules">2.9.4. Guardando las Reglas de IPTalbes</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-IPTables-IPTables_Control_Scripts">2.9.5. Scripts de Control de IPTables</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-IPTables-IPTables_and_IPv6">2.9.6. IPTables y IPv6</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-IPTables-Additional_Resources">2.9.7. Recursos Adicionales</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#chap-Security_Guide-Encryption">3. EncriptaciÃ³n</a></span></dt><dd><dl><dt><span class="
 section"><a href="#sect-Security_Guide-Encryption-Data_at_Rest">3.1. Datos en Descanso</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Encryption-Protecting_Data_at_Rest-Full_Disk_Encryption">3.2. EncriptaciÃ³n completa del disco</a></span></dt><dt><span class="section"><a href="#Security_Guide-Encryption-Protecting_Data_at_Rest-File_Based_Encryption">3.3. EncriptaciÃ³n Basada en Archivo</a></span></dt><dt><span class="section"><a href="#Security_Guide-Encryption-Data_in_Motion">3.4. Datos en Movimiento</a></span></dt><dt><span class="section"><a href="#Security_Guide-Encryption-Data_in_Motion-Virtual_Private_Networks">3.5. Redes privadas virtuales (VPN)</a></span></dt><dt><span class="section"><a href="#Security_Guide-Encryption-Data_in_Motion-Secure_Shell">3.6. Shell seguro</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-LUKS_Disk_Encryption">3.7. EncriptaciÃ³n de disco LUKS</a></span></dt><dd><dl><dt><span class="section"><a h
 ref="#sect-Security_Guide-LUKS_Disk_Encryption-LUKS_Implementation_in_Fedora">3.7.1. ImplementaciÃ³n de LUKS en Fedora</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories">3.7.2. EncriptaciÃ³n Manual de Directorios</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-Step_by_Step_Instructions">3.7.3. Instrucciones paso a paso</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-What_you_have_just_accomplished">3.7.4. Lo que acaba de hacer.</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-LUKS_Disk_Encryption-Links_of_Interest">3.7.5. Enlaces de InterÃ©s</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives">3.8. Archivos Encriptados 7-Zip</a></span></dt><dd><dl><dt><span class="sec
 tion"><a href="#sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Installation">3.8.1. InstalaciÃ³n de 7-Zip en Fedora</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Installation-Instructions">3.8.2. Instrucciones para instalaciÃ³n paso a paso</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Usage_Instructions">3.8.3. Uso de las instrucciones paso a paso</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Things_of_note">3.8.4. Cosas Notables</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Encryption-Using_GPG">3.9. Utilizando GNU Privacy Guard (GnuPG)</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Encryption-Using_GPG-Keys_in_GNOME">3.9.1. Crear claves GPG en GNOME</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide
 -Encryption-Using_GPG-Creating_GPG_Keys_in_KDE1">3.9.2. Crear claves GPG en KDE</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE">3.9.3. Crear una clave GPG mediante la lÃnea de comandos</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Encryption-Using_GPG-About_Public_Key_Encryption">3.9.4. Acerca del encriptado de la clave pÃºblica</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#chap-Security_Guide-General_Principles_of_Information_Security">4. Principios Generales sobre la Seguridad de la InformaciÃ³n</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-General_Principles_of_Information_Security-Tips_Guides_and_Tools">4.1. Consejos, GuÃas y Herramientas</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Security_Guide-Secure_Installation">5. InstalaciÃ³n segura</a></span></dt><dd><dl><dt><span class="section"><a href="
 #sect-Security_Guide-Secure_Installation-Disk_Partitions">5.1. Particiones de Disco</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Secure_Installation-Utilize_LUKS_Partition_Encryption">5.2. Utilice EncriptaciÃ³n de ParticiÃ³n con LUKS</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Security_Guide-Software_Maintenance">6. Mantenimiento de Software</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Software_Maintenance-Install_Minimal_Software">6.1. Instale el software mÃnimo</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates">6.2. Planifique y configure actualizaciones de seguridad</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates-Adjusting_Automatic_Updates">6.3. Ajustando las actualizaciones automÃ¡ticas</a></span></dt><dt><span class="section"><a hre
 f="#sect-Security_Guide-Software_Maintenance-Install_Signed_Packages_from_Well_Known_Repositories">6.4. Instale paquetes identificados desde repositorios conocidos</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Security_Guide-References">7. Referencias</a></span></dt></dl></div><div class="preface" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h1 id="pref-Security_Guide-Preface" class="title">Prefacio</h1></div></div></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h2 class="title" id="id544690">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" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="id382958">1.1. Convenciones tipogrÃ¡ficas</h3></div></div></div><div class="para">
+	</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="id527876">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>
@@ -74,7 +76,7 @@
 			Aside from standard usage for presenting the title of a work, italics denotes the first use of a new and important term. For example:
 		</div><div class="blockquote"><blockquote class="blockquote"><div class="para">
 				When the Apache HTTP Server accepts requests, it dispatches child processes or threads to handle them. This group of child processes or threads is known as a <em class="firstterm">server-pool</em>. Under Apache HTTP Server 2.0, the responsibility for creating and maintaining these server-pools has been abstracted to a group of modules called <em class="firstterm">Multi-Processing Modules</em> (<em class="firstterm">MPMs</em>). Unlike other modules, only one module from the MPM group can be loaded by the Apache HTTP Server.
-			</div></blockquote></div></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="id407594">1.2. Convenciones del documento</h3></div></div></div><div class="para">
+			</div></blockquote></div></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="id497366">1.2. Convenciones del documento</h3></div></div></div><div class="para">
 			Dos, usualmente de varias lÃneas, los tipos de datos se distinguen visualmente del texto circundante.
 		</div><div class="para">
 			Salida enviada a una terminal estÃ¡ establecida en tipo <code class="computeroutput">romano monoespaciado</code> y presentada asÃ:
@@ -102,7 +104,7 @@
    }
    
 }
-</pre></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="id438216">1.3. Notas y advertencias</h3></div></div></div><div class="para">
+</pre></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="id510897">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 que se tiene a mano para la tarea. Ignorar una nota no deberÃa tener consecuencias negativas, pero podrÃa perderse de algunos trucos que pueden facilitarle las cosas.
@@ -110,189 +112,189 @@
 				Los cuadros de importante dan detalles de cosas que se pueden pasar por alto fÃ¡cilmente: cambios de configuraciÃ³n Ãºnicamente aplicables a la sesiÃ³n actual, o servicios que necesitan reiniciarse antes de que se aplique una actualizaciÃ³n. Ignorar estos cuadros de importante no ocasionarÃ¡ pÃ©rdida de datos, pero puede causar enfado y frustraciÃ³n.
 			</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 class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h2 class="title" id="We_Need_Feedback">2. Â¡Se necesita retroalimentaciÃ³n!</h2></div></div></div><div class="para">
+			</div></div></div></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h2 class="title" id="We_Need_Feedback">2. Â¡Necesitamos retroalimentaciÃ³n!</h2></div></div></div><div class="para">
 		MÃ¡s informaciÃ³n acerca del proyecto GuÃa de Seguridad de Linux se puede encontrar en <a href="https://fedorahosted.org/securityguide">https://fedorahosted.org/securityguide</a>
 	</div><div class="para">
-		To provide feedback for the Security Guide, please file a bug in <a href="https://bugzilla.redhat.com/enter_bug.cgi?component=security-guide&amp;product=Fedora%20Documentation">https://bugzilla.redhat.com/enter_bug.cgi?component=security-guide&amp;product=Fedora%20Documentation</a>. Please select the proper component in the dropdown menu which should be the page name.
-	</div></div></div><div class="chapter" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h2 class="title" id="chap-Security_Guide-Security_Overview">CapÃtulo 1. Security Overview</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Security_Guide-Introduction_to_Security">1.1. Introduction to Security</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Introduction_to_Security-What_is_Computer_Security">1.1.1. What is Computer Security?</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Introduction_to_Security-SELinux">1.1.2. SELinux</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Introduction_to_Security-Security_Controls">1.1.3. Security Controls</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Introduction_to_Security-Conclusion">1.1.4. ConclusiÃ³n</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Vulner
 ability_Assessment">1.2. Vulnerability Assessment</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Vulnerability_Assessment-Thinking_Like_the_Enemy">1.2.1. Pensado como el Enemigo</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Vulnerability_Assessment-Defining_Assessment_and_Testing">1.2.2. Definiendo EvaluaciÃ³n y Pruebas</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Vulnerability_Assessment-Evaluating_the_Tools">1.2.3. Herramientas de EvaluaciÃ³n</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Attackers_and_Vulnerabilities">1.3. Attackers and Vulnerabilities</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Attackers_and_Vulnerabilities-A_Quick_History_of_Hackers">1.3.1. A Quick History of Hackers</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Network_Security">1.3.2. Th
 reats to Network Security</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Server_Security">1.3.3. Threats to Server Security</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Workstation_and_Home_PC_Security">1.3.4. Threats to Workstation and Home PC Security</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Common_Exploits_and_Attacks">1.4. Ataques y Aprovechadas ComÃºnes</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Security_Updates">1.5. Actualizaciones de Seguridad</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Security_Updates-Updating_Packages">1.5.1. Updating Packages</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Updating_Packages-Verifying_Signed_Packages">1.5.2. Verifying Signed Packages</a></span></dt><dt><span class="section"><a 
 href="#sect-Security_Guide-Updating_Packages-Installing_Signed_Packages">1.5.3. Installing Signed Packages</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Updating_Packages-Applying_the_Changes">1.5.4. Applying the Changes</a></span></dt></dl></dd></dl></div><div class="para">
-		Because of the increased reliance on powerful, networked computers to help run businesses and keep track of our personal information, entire industries have been formed around the practice of network and computer security. Enterprises have solicited the knowledge and skills of security experts to properly audit systems and tailor solutions to fit the operating requirements of the organization. Because most organizations are increasingly dynamic in nature, with workers accessing company IT resources locally and remotely, the need for secure computing environments has become more pronounced.
+		Para entregar una retroalimentaciÃ³n de la GuÃa de Seguridad, por favor envÃe un error a <a href="https://bugzilla.redhat.com/enter_bug.cgi?component=security-guide&amp;product=Fedora%20Documentation">https://bugzilla.redhat.com/enter_bug.cgi?component=security-guide&amp;product=Fedora%20Documentation</a>. Por favor seleccione el componente adecuado en el menÃº desplegable, que deberÃa ser el nombre de la pÃ¡gina.
+	</div></div></div><div class="chapter" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h2 class="title" id="chap-Security_Guide-Security_Overview">CapÃtulo 1. Repaso sobre seguridad</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Security_Guide-Introduction_to_Security">1.1. IntroducciÃ³n a la Seguridad</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Introduction_to_Security-What_is_Computer_Security">1.1.1. Â¿QuÃ© es la Seguridad de Computadoras?</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Introduction_to_Security-SELinux">1.1.2. SELinux</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Introduction_to_Security-Security_Controls">1.1.3. Controles de seguridad</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Introduction_to_Security-Conclusion">1.1.4. ConclusiÃ³n</a></span></dt></dl></dd><dt><span class="section"><a href="
 #sect-Security_Guide-Vulnerability_Assessment">1.2. EvaluaciÃ³n de debilidades</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Vulnerability_Assessment-Thinking_Like_the_Enemy">1.2.1. Pensado como el enemigo</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Vulnerability_Assessment-Defining_Assessment_and_Testing">1.2.2. Definiendo evaluaciÃ³n y pruebas</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Vulnerability_Assessment-Evaluating_the_Tools">1.2.3. Herramientas de evaluaciÃ³n</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Attackers_and_Vulnerabilities">1.3. Atacantes y vulnerabilidades</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Attackers_and_Vulnerabilities-A_Quick_History_of_Hackers">1.3.1. Una breve reseÃ±a acerca de los hackers</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Attackers_and_Vulnerabiliti
 es-Threats_to_Network_Security">1.3.2. Amenazas a la seguridad de la red</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Server_Security">1.3.3. Amenazas a la Seguridad del Servidor</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Workstation_and_Home_PC_Security">1.3.4. Amenazas a las Estaciones de Trabajo y Seguridad en Equipos HogareÃ±os</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Common_Exploits_and_Attacks">1.4. Ataques y debilidades comunes</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Security_Updates">1.5. Actualizaciones de seguridad</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Security_Updates-Updating_Packages">1.5.1. ActualizaciÃ³n de paquetes</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Updating_Packages-Verifying_Sig
 ned_Packages">1.5.2. VerificaciÃ³n de Paquetes Firmados</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Updating_Packages-Installing_Signed_Packages">1.5.3. InstalaciÃ³n de paquetes firmados</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Updating_Packages-Applying_the_Changes">1.5.4. AplicaciÃ³n de los cambios</a></span></dt></dl></dd></dl></div><div class="para">
+		Debido a la creciente necesidad por la utilizaciÃ³n de poderosas computadoras conectadas en red para poder mantener una empresa en funcionamiento, y para poder realizar seguimientos de nuestra informaciÃ³n personal, se han desarrollado industrias enteras dedicadas a la prÃ¡ctica de la seguridad de redes y computadoras. Numerosas empresas han solicitado la pericia y el conocimiento de expertos en seguridad para controlar correctamente sus sistemas, y para que diseÃ±en soluciones adecuadas a los requerimientos operativos de la organizaciÃ³n. Debido a la naturaleza dinÃ¡mica de muchas de estas organizaciones, donde los trabajadores deben tener acceso a los recursos informÃ¡ticos, ya sea en forma local o remota, la necesidad de entornos de computaciÃ³n seguros se ha hecho mÃ¡s pronunciada.
 	</div><div class="para">
-		Unfortunately, most organizations (as well as individual users) regard security as an afterthought, a process that is overlooked in favor of increased power, productivity, and budgetary concerns. Proper security implementation is often enacted <em class="firstterm">postmortem</em> â€” after an unauthorized intrusion has already occurred. Security experts agree that taking the correct measures prior to connecting a site to an untrusted network, such as the Internet, is an effective means of thwarting most attempts at intrusion.
-	</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h2 class="title" id="sect-Security_Guide-Introduction_to_Security">1.1. Introduction to Security</h2></div></div></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Introduction_to_Security-What_is_Computer_Security">1.1.1. What is Computer Security?</h3></div></div></div><div class="para">
-			Computer security is a general term that covers a wide area of computing and information processing. Industries that depend on computer systems and networks to conduct daily business transactions and access crucial information regard their data as an important part of their overall assets. Several terms and metrics have entered our daily business vocabulary, such as total cost of ownership (TCO) and quality of service (QoS). Using these metrics, industries can calculate aspects such as data integrity and high-availability as part of their planning and process management costs. In some industries, such as electronic commerce, the availability and trustworthiness of data can be the difference between success and failure.
-		</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-What_is_Computer_Security-How_did_Computer_Security_Come_about">1.1.1.1. How did Computer Security Come about?</h4></div></div></div><div class="para">
-				Information security has evolved over the years due to the increasing reliance on public networks not to disclose personal, financial, and other restricted information. There are numerous instances such as the Mitnick <sup>[<a id="id397660" href="#ftn.id397660" class="footnote">1</a>]</sup>and the Vladimir Levin <sup>[<a id="id397669" href="#ftn.id397669" class="footnote">2</a>]</sup>cases that prompted organizations across all industries to re-think the way they handle information, as well as its transmission and disclosure. The popularity of the Internet was one of the most important developments that prompted an intensified effort in data security.
+		Desafortunadamente, muchas de las organizaciones (y muchos usuarios individuales), luego de pensarlo dos veces, deciden relegar el aspecto de la seguridad a un plano inferior, dÃ¡ndole prioridad a otras Ã¡reas de sus emprendimientos, como ser producciÃ³n, presupuesto, o infraestructura. Y frecuentemente, una implementaciÃ³n adecuada de la seguridad es adoptada <em class="firstterm">postmortem</em> â€” luego que un acceso no autorizado haya ocurrido. Los expertos en seguridad concuerdan en que adoptar las medidas correctas antes de conectar un sitio a una red insegura, como lo es Internet, es una manera efectivo de prevenir la mayorÃa de los intentos de intrusiÃ³n.
+	</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h2 class="title" id="sect-Security_Guide-Introduction_to_Security">1.1. IntroducciÃ³n a la Seguridad</h2></div></div></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Introduction_to_Security-What_is_Computer_Security">1.1.1. Â¿QuÃ© es la Seguridad de Computadoras?</h3></div></div></div><div class="para">
+			La nociÃ³n de seguridad en computaciÃ³n es un concepto general que cubre un Ã¡rea muy extensa dentro del Ã¡mbito de la computaciÃ³n y del procesamiento de la informaciÃ³n. Las industrias que dependen tanto de redes como de sistemas de computaciÃ³n para poder realizar cotidianamente operaciones comerciales, y para acceder a diverso tipo de informaciÃ³n vital, entienden que sus datos son una parte importante de sus activos. En nuestro vocabulario cotidiano han ingresado varios tÃ©rminos y unidades de mediciÃ³n pertenecientes al Ã¡mbito comercial, como son, por ejemplo, por ejemplo, el coste total de propiedad (TCO, por las iniciales en inglÃ©s de Total Cost of Ownership), o servicio de calidad (QoS, por las iniciales en inglÃ©s de Quality of Service). Al utilizar estas unidades, las industrias pueden calcular aspectos tales como ser la integridad de los datos, o el tipo de disponibilidad que tienen, y poder considerarlos parte de los costos de planeamiento y administraciÃ³n
  de procesos. En algunas industrias, como la del comercio electrÃ³nico por ejemplo, el tipo de disponibilidad y la confiabilidad de los datos puede ser un elemento determinante para el Ã©xito o el fracaso.
+		</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-What_is_Computer_Security-How_did_Computer_Security_Come_about">1.1.1.1. Â¿De dÃ³nde viene la idea de seguridad de computadoras?</h4></div></div></div><div class="para">
+				La seguridad en la informaciÃ³n ha evolucionado con el correr de los aÃ±os debido al aumento en la utilizaciÃ³n de redes pÃºblicas y el consecuente riesgo de exposiciÃ³n que en ellas tienen los datos privados, confidenciales o financieros. Existen numerosos antecedentes, como el caso Mitnick <sup>[<a id="id477829" href="#ftn.id477829" class="footnote">1</a>]</sup> o Vladimir Levin <sup>[<a id="id502956" href="#ftn.id502956" class="footnote">2</a>]</sup>, que sugieren a todas las organizaciones de cualquier tipo de industria, replantearse la forma en que tienen organizado el manejo de su propia informaciÃ³n, o como esta es transmitida y revelada. La popularidad que tiene Internet es uno de los motivos fundamentales gracias al cual se han intensificado los esfuerzos relacionados con la seguridad en los datos.
 			</div><div class="para">
-				An ever-growing number of people are using their personal computers to gain access to the resources that the Internet has to offer. From research and information retrieval to electronic mail and commerce transaction, the Internet has been regarded as one of the most important developments of the 20th century.
+				Un nÃºmero creciente de gente estÃ¡n usando sus computadoras personales para obtener acceso a los recursos que ofrece la Internet. Desde investigaciÃ³n y obtenciÃ³n de informaciÃ³n hasta el correo electrÃ³nico y transacciones comerciales, la Internet es considerada como uno de los desarrollos mÃ¡s importantes del siglo 20.
 			</div><div class="para">
-				The Internet and its earlier protocols, however, were developed as a <em class="firstterm">trust-based</em> system. That is, the Internet Protocol was not designed to be secure in itself. There are no approved security standards built into the TCP/IP communications stack, leaving it open to potentially malicious users and processes across the network. Modern developments have made Internet communication more secure, but there are still several incidents that gain national attention and alert us to the fact that nothing is completely safe.
-			</div></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-What_is_Computer_Security-Security_Today">1.1.1.2. Security Today</h4></div></div></div><div class="para">
-				In February of 2000, a Distributed Denial of Service (DDoS) attack was unleashed on several of the most heavily-trafficked sites on the Internet. The attack rendered yahoo.com, cnn.com, amazon.com, fbi.gov, and several other sites completely unreachable to normal users, as it tied up routers for several hours with large-byte ICMP packet transfers, also called a <em class="firstterm">ping flood</em>. The attack was brought on by unknown assailants using specially created, widely available programs that scanned vulnerable network servers, installed client applications called <em class="firstterm">trojans</em> on the servers, and timed an attack with every infected server flooding the victim sites and rendering them unavailable. Many blame the attack on fundamental flaws in the way routers and the protocols used are structured to accept all incoming data, no matter where or for what purpose the packets are sent.
+				Sin embargo, Internet y sus primeros protocolos fueron desarrollados como un sistema <em class="firstterm">basado en la confianza</em>. Esto significa que el Protocolo de Internet no fue diseÃ±ado para ser seguro en sÃ mismo. No existen estÃ¡ndares de seguridad aprobados dentro del bloque de comunicaciones TCP/IP, dejÃ¡ndolo indefenso ante usuarios o procesos de la red potencialmente daÃ±inos. Desarrollos modernos han hecho de las comunicaciones en Internet algo mÃ¡s seguro, pero todavÃa existen varios incidentes que acaparan la atenciÃ³n mundial y nos recuerdan el hecho que nada es completamente seguro.
+			</div></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-What_is_Computer_Security-Security_Today">1.1.1.2. La seguridad hoy</h4></div></div></div><div class="para">
+				En febrero del 2000 un ataque de denegaciÃ³n de servicio distribuido (DDoS, por las iniciales en inglÃ©s de Distributed Denial of Service) fue liberado sobre varios de los sitios de Internet que tenÃan mÃ¡s trÃ¡fico. Este ataque afectÃ³ a yahoo.com, cnn.com, amazon.com, fbi.gov y algunos otros sitios que son completamente inaccesibles para los usuarios normales, dejando a los enrutadores bloqueados durante varias horas con transferencias de grandes paquetes ICMP, tambiÃ©n denominado un <em class="firstterm">ping de la muerte</em>. El ataque fue llevado a cabo por asaltantes desconocidos utilizando programas especialmente creados (y que estÃ¡n a disposiciÃ³n de cualquiera), que buscan servidores de red vulnerables, instalan en esos servidores aplicaciones de cliente denominadas <em class="firstterm">troyanos</em>, y sincronizando un ataque con cada servidor infectado, inundando los sitios elegidos y dejÃ¡ndolos inutilizables. Muchos adjudican el Ã©xito del ataque a falla
 s fundamentales en la forma en que estÃ¡n estructurados los enrutadores y los protocolos que utilizan. Estas fallas tienen que ver con la manera en que se aceptan los datos entrantes, sin importar desde dÃ³nde provengan, o con quÃ© propÃ³sito los paquetes hayan sido enviados.
 			</div><div class="para">
-				In 2007, a data breach exploiting the widely-known weaknesses of the Wired Equivalent Privacy (WEP) wireless encryption protocol resulted in the theft from a global financial institution of over 45 million credit card numbers.<sup>[<a id="id397614" href="#ftn.id397614" class="footnote">3</a>]</sup>
+				En 2007, una explotaciÃ³n de una brecha de debilidad bien conocida en el protocolo de encriptaciÃ³n inalÃ¡mbrica llamada Privacidad Equivalente a la Cableada (WEP) resultÃ³ en el robo de 45 millones de nÃºmeros de tarjetas de crÃ©ditos de una instituciÃ³n financiera global.<sup>[<a id="id544712" href="#ftn.id544712" class="footnote">3</a>]</sup>
 			</div><div class="para">
-				In a separate incident, the billing records of over 2.2 million patients stored on a backup tape were stolen from the front seat of a courier's car.<sup>[<a id="id397601" href="#ftn.id397601" class="footnote">4</a>]</sup>
+				En un incidente separado, los registros de facturaciÃ³n de 2,2 millones de pacientes almacenados en una cinta de respaldo fueron robados del asiento de un vehÃculo de cadeterÃa.<sup>[<a id="id482190" href="#ftn.id482190" class="footnote">4</a>]</sup>
 			</div><div class="para">
-				Currently, an estimated 1.4 billion people use or have used the Internet worldwide.<sup>[<a id="id397587" href="#ftn.id397587" class="footnote">5</a>]</sup> At the same time:
+				Actualmente, se estima que 1,4 mil millones de personas usan o usaron Internet alrededor del mundo <sup>[<a id="id485290" href="#ftn.id485290" class="footnote">5</a>]</sup> A la vez:
 			</div><div class="itemizedlist"><ul><li><div class="para">
-						On any given day, there are approximately 225 major incidences of security breach reported to the CERT Coordination Center at Carnegie Mellon University.<sup>[<a id="id397567" href="#ftn.id397567" class="footnote">6</a>]</sup>
+						En cualquier dÃa, hay aproximadamente 225 incidentes principales de brechas de seguridad informados al Centro de CoordinaciÃ³n CERT en la Universidad de Carnegie Mellon.<sup>[<a id="id537994" href="#ftn.id537994" class="footnote">6</a>]</sup>
 					</div></li><li><div class="para">
-						In 2003, the number of CERT reported incidences jumped to 137,529 from 82,094 in 2002 and from 52,658 in 2001.<sup>[<a id="id397555" href="#ftn.id397555" class="footnote">7</a>]</sup>
+						En 2003, el nÃºmero de incidencias CERT informadas saltÃ³ a 137.529 de 82.094 en 2002 y de 52.658 en 2001.<sup>[<a id="id403427" href="#ftn.id403427" class="footnote">7</a>]</sup>
 					</div></li><li><div class="para">
-						The worldwide economic impact of the three most dangerous Internet Viruses of the last three years was estimated at US$13.2 Billion.<sup>[<a id="id397540" href="#ftn.id397540" class="footnote">8</a>]</sup>
+						El impacto econÃ³mico a nivel mundial de los Virus de Internet mÃ¡s peligrosos de los Ãºltimos tres aÃ±os se estimÃ³ en u$s 13,2 mil millones.<sup>[<a id="id488150" href="#ftn.id488150" class="footnote">8</a>]</sup>
 					</div></li></ul></div><div class="para">
-				From a 2008 global survey of business and technology executives "The Global State of Information Security"<sup>[<a id="id397522" href="#ftn.id397522" class="footnote">9</a>]</sup>, undertaken by <span class="emphasis"><em>CIO Magazine</em></span>, some points are:
+				De un repaso global de 2008 de negocios y de ejecutivos de tecnologÃas "El Estado Global de la Seguridad de la InformaciÃ³n"<sup>[<a id="id465405" href="#ftn.id465405" class="footnote">9</a>]</sup>, llevado por <span class="emphasis"><em>CIO Magazine</em></span>, se extrae lo siguiente:
 			</div><div class="itemizedlist"><ul><li><div class="para">
-						Just 43% of respondents audit or monitor user compliance with security policies
+						SÃ³lo el 43% de los encuestados audita o monitorea el cumplimiento del usuario de las polÃticas de seguridad
 					</div></li><li><div class="para">
-						Only 22% keep an inventory of the outside companies that use their data
+						SÃ³lo el 22% mantiene un inventario de las compaÃ±Ãas externas que usan sus datos
 					</div></li><li><div class="para">
-						The source of nearly half of security incidents was marked as "Unknown"
+						La fuente de casi la mitad de los incidentes de seguridad se marcaron como "Desconocidos"
 					</div></li><li><div class="para">
-						44% of respondents plan to increase security spending in the next year
+						44% de los encuestados planean incrementar sus gastos en seguridad en el aÃ±o siguiente
 					</div></li><li><div class="para">
-						59% have an information security strategy
+						59% tiene una estrategia de seguridad de la informaciÃ³n
 					</div></li></ul></div><div class="para">
-				These results enforce the reality that computer security has become a quantifiable and justifiable expense for IT budgets. Organizations that require data integrity and high availability elicit the skills of system administrators, developers, and engineers to ensure 24x7 reliability of their systems, services, and information. Falling victim to malicious users, processes, or coordinated attacks is a direct threat to the success of the organization.
+				Estos resultados refuerzan la realidad de que la seguridad de computadoras se ha vuelto un gasto cuantificable y justificable en los presupuestos de TI. Las organizaciones que necesitan la integridad de datos y alta disponibilidad lo obtienen de las habilidades de los administradores de sistemas, desarrolladores e ingenieros para asegurar la disponibilidad 24x7 de sus sistemas, servicios e informaciÃ³n. Ser vÃctima de usuarios maliciosos, procesos o ataques coordinados es una amenaza directa al Ã©xito de la organizaciÃ³n.
 			</div><div class="para">
-				Unfortunately, system and network security can be a difficult proposition, requiring an intricate knowledge of how an organization regards, uses, manipulates, and transmits its information. Understanding the way an organization (and the people that make up the organization) conducts business is paramount to implementing a proper security plan.
-			</div></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-What_is_Computer_Security-Standardizing_Security">1.1.1.3. Standardizing Security</h4></div></div></div><div class="para">
-				Enterprises in every industry rely on regulations and rules that are set by standards-making bodies such as the American Medical Association (AMA) or the Institute of Electrical and Electronics Engineers (IEEE). The same ideals hold true for information security. Many security consultants and vendors agree upon the standard security model known as CIA, or <em class="firstterm">Confidentiality, Integrity, and Availability</em>. This three-tiered model is a generally accepted component to assessing risks of sensitive information and establishing security policy. The following describes the CIA model in further detail:
+				Desafortunadamente, la seguridad de sistemas y de la red puede ser una proposiciÃ³n difÃcil, que requiere un conocimiento intrincado de cÃ³mo una organizaciÃ³n expresa, usa, manipula y transmite su informaciÃ³n. El entendimiento de la forma en que una organizaciÃ³n (y la gente que la compone) conduce el negocio es primordial para implementar un plan de seguridad apropiado.
+			</div></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-What_is_Computer_Security-Standardizing_Security">1.1.1.3. Estandarizando la seguridad</h4></div></div></div><div class="para">
+				Las empresas de todas las industrias confÃan en las regulaciones y en las reglas que son puestas por las personas que construyen estÃ¡ndares tales como la AsociaciÃ³n MÃ©dica Americana (AMA) o el Instituto de Ingenieros ElÃ©ctricos y ElectrÃ³nicos (IEEE). Los mismos ideales se aplican a la seguridad de la informaciÃ³n. Muchos consultores y fabricantes se ponen de acuerdo en el modelo de seguridad estÃ¡ndar conocido como CIA, o <em class="firstterm">Confidencialidad, Integridad y Disponibilidad</em>. Este modelo de 3 capas es un componente generalmente aceptado para averiguar los riesgos de la informaciÃ³n sensible y del establecimiento de la polÃtica de seguridad. A continuaciÃ³n se describe el modelo CIA en mÃ¡s detalle:
 			</div><div class="itemizedlist"><ul><li><div class="para">
-						Confidentiality â€” Sensitive information must be available only to a set of pre-defined individuals. Unauthorized transmission and usage of information should be restricted. For example, confidentiality of information ensures that a customer's personal or financial information is not obtained by an unauthorized individual for malicious purposes such as identity theft or credit fraud.
+						Confidencialidad â€” La informaciÃ³n sensible debe estar disponible sÃ³lo para un conjunto de individuos predefinido. La transmisiÃ³n no autorizada y el uso de la informaciÃ³n se debe restringir. Por ejemplo, la confidencialidad de la informaciÃ³n asegura que la informaciÃ³n personal o financiera de un cliente no pueda ser obtenida por un individuo no autorizado para propÃ³sitos malÃ©ficos tales como el robo de identidad o un fraude crediticio.
 					</div></li><li><div class="para">
-						Integrity â€” Information should not be altered in ways that render it incomplete or incorrect. Unauthorized users should be restricted from the ability to modify or destroy sensitive information.
+						Integridad â€” La informaciÃ³n no se debe alterar en formas que hagan que estÃ©n incompletas o incorrectas. Los usuarios no autorizados deben ser restringidos de la habilidad de modificar o destruir informaciÃ³n sensible.
 					</div></li><li><div class="para">
-						Availability â€” Information should be accessible to authorized users any time that it is needed. Availability is a warranty that information can be obtained with an agreed-upon frequency and timeliness. This is often measured in terms of percentages and agreed to formally in Service Level Agreements (SLAs) used by network service providers and their enterprise clients.
+						Disponibilidad â€” La informaciÃ³n debe ser accesible a usuarios autorizados en cualquier momento en el que sea necesario. La disponibilidad es una garantÃa de que la informaciÃ³n se puede obtener en una frecuencia y duraciÃ³n preestablecida. Esto se mide a menudo en tÃ©rminos de porcentajes y se deja sentado formalmente en Acuerdos de Disponibilidad del Servicio (ADS) con los proveedores de servicios de red y sus clientes empresariales.
 					</div></li></ul></div></div></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Introduction_to_Security-SELinux">1.1.2. SELinux</h3></div></div></div><div class="para">
-			Fedora includes an enhancement to the Linux kernel called SELinux, which implements a Mandatory Access Control (MAC) architecture that provides a fine-grained level of control over files, processes, users and applications in the system. Detailed discussion of SELinux is beyond the scope of this document; however, for more information on SELinux and its use in Fedora, refer to the Fedora SELinux User Guide available at <a href="http://docs.fedoraproject.org/selinux-user-guide/">http://docs.fedoraproject.org/selinux-user-guide/</a>. Other available resources for SELinux are listed in <a class="xref" href="#chap-Security_Guide-References" title="CapÃtulo 7. Referencias">CapÃtuloÂ 7, <i>Referencias</i></a>.
-		</div></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Introduction_to_Security-Security_Controls">1.1.3. Security Controls</h3></div></div></div><div class="para">
-			Computer security is often divided into three distinct master categories, commonly referred to as <em class="wordasword">controls</em>:
+			Fedora incluye una mejora al kernel de Linux que se llama SELinux, que implementa la arquitectura de Control de Acceso Obligatorio (MAC), que provee un nivel mÃ¡s fino de control sobre los archivos, procesos, usuarios y aplicaciones en el sistema. La discusiÃ³n detallada sobre SELinux estÃ¡ mÃ¡s allÃ¡ del alcance de este documento; sin embargo, para mÃ¡s informaciÃ³n sobre SELinux y su uso en Fedora, vaya a la GuÃa del Usuario de SELinux de Fedora disponible en <a href="http://docs.fedoraproject.org/selinux-user-guide/">http://docs.fedoraproject.org/selinux-user-guide/</a>. Hay otros recursos de SELinux listados en <a class="xref" href="#chap-Security_Guide-References" title="CapÃtulo 7. Referencias">CapÃtuloÂ 7, <i>Referencias</i></a>.
+		</div></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Introduction_to_Security-Security_Controls">1.1.3. Controles de seguridad</h3></div></div></div><div class="para">
+			La seguridad de computadoras es a menudo dividida en tres categorÃas principales distintas, comÃºnmente referidas como <em class="wordasword">controles</em>:
 		</div><div class="itemizedlist"><ul><li><div class="para">
-					Physical
+					FÃsico
 				</div></li><li><div class="para">
-					Technical
+					TÃ©cnicos
 				</div></li><li><div class="para">
-					Administrative
+					Asministrativos
 				</div></li></ul></div><div class="para">
-			These three broad categories define the main objectives of proper security implementation. Within these controls are sub-categories that further detail the controls and how to implement them.
-		</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Security_Controls-Physical_Controls">1.1.3.1. Physical Controls</h4></div></div></div><div class="para">
-				Physical control is the implementation of security measures in a defined structure used to deter or prevent unauthorized access to sensitive material. Examples of physical controls are:
+			Estas tres amplias categorÃas definen los objetivos principales de una implementaciÃ³n de seguridad apropiada. Dentro de estos controles son subcategorÃas que detallan los controles y cÃ³mo implementarlos.
+		</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Security_Controls-Physical_Controls">1.1.3.1. Control FÃsico</h4></div></div></div><div class="para">
+				El control fÃsico es la implementaciÃ³n de medidas de seguridad en una estructura definida y usada para disuadir o evitar el acceso no autorizado a material sensible. Los ejemplos de controles fÃsicos son:
 			</div><div class="itemizedlist"><ul><li><div class="para">
-						Closed-circuit surveillance cameras
+						Circuito cerrado de cÃ¡maras de vigilancia
 					</div></li><li><div class="para">
-						Motion or thermal alarm systems
+						Sistemas de alarma de movimientos o termales
 					</div></li><li><div class="para">
-						Security guards
+						Guardias de la seguridad
 					</div></li><li><div class="para">
-						Picture IDs
+						IDs de Imagen
 					</div></li><li><div class="para">
-						Locked and dead-bolted steel doors
+						Puertas de acero bloqueadas y selladas
 					</div></li><li><div class="para">
-						Biometrics (includes fingerprint, voice, face, iris, handwriting, and other automated methods used to recognize individuals)
-					</div></li></ul></div></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Security_Controls-Technical_Controls">1.1.3.2. Technical Controls</h4></div></div></div><div class="para">
[...5011 lines suppressed...]
+			A continuaciÃ³n, elija cuÃ¡ndo expiarÃ¡ la clave. es una buena idea elegir una fecha de expiraciÃ³n en lugar de elegir la opciÃ³n establecida por defecto, que es "ninguna". Si, por ejemplo, la direcciÃ³n de correo electrÃ³nico de la clave deja de ser vÃ¡lida, una fecha de expiraciÃ³n le recordarÃ¡ a los demÃ¡s que dejen de utilizar esa clave pÃºblica.
 		</div><div class="para">
-			Please specify how long the key should be valid. 0 = key does not expire d = key expires in n days w = key expires in n weeks m = key expires in n months y = key expires in n years Key is valid for? (0)
+			Por favor indique por cuÃ¡nto tiempo la clave debe ser vÃ¡lida. 0 = la calve no expira, d = la clave expira en n dÃas, w = la clave expira en n semanas, m = la clave expira en n meses, y = la clave expira en n aÃ±os. Â¿La clave es vÃ¡lida por? (0)
 		</div><div class="para">
-			Entering a value of <code class="code">1y</code>, for example, makes the key valid for one year. (You may change this expiration date after the key is generated, if you change your mind.)
+			Ingresar un valor de <code class="code">1y</code>, por ejemplo, hace que la clave sea vÃ¡lida durante un aÃ±o. (Puede modificar esta fecha de expiraciÃ³n luego que la clave haya sido generada, si cambiÃ³ de parecer.)
 		</div><div class="para">
-			Before the <code class="code">gpg</code>code &gt; program asks for signature information, the following prompt appears: <code class="code">Is this correct (y/n)?</code> Enter <code class="code">y</code>code &gt; to finish the process.
+			Antes que el programa <code class="code">gpg</code> le pida informaciÃ³n para la firma, aparece el siguiente mensaje: <code class="code">Es correcto (y/n)?</code>. Ingrese <code class="code">y</code> para finalizar el proceso.
 		</div><div class="para">
-			Next, enter your name and email address. Remember this process is about authenticating you as a real individual. For this reason, include your real name. Do not use aliases or handles, since these disguise or obfuscate your identity.
+			A continuaciÃ³n, ingrese su nombre y direcciÃ³n de correo electrÃ³nico. Recuerde que este proceso se trata de autenticarlo a usted como un individuo real. Por esta razÃ³n, incluya su verdadero nombre. No utilice apodos o alias, ya que esto oscurece o disimula su identidad.
 		</div><div class="para">
-			Enter your real email address for your GPG key. If you choose a bogus email address, it will be more difficult for others to find your public key. This makes authenticating your communications difficult. If you are using this GPG key for [[DocsProject/SelfIntroduction| self-introduction]] on a mailing list, for example, enter the email address you use on that list.
+			Ingrese su direcciÃ³n de correo electrÃ³nico real para su clave GPG. Si elige una falsa o inexistente, serÃ¡ mÃ¡s difÃcil para los demÃ¡s encontrar su clave pÃºblica. Esto hace que autenticar sus comunicaciones sea mÃ¡s difÃcil. Si estÃ¡ utilizando esta clave GPG para [[DocsProject/SelfIntroduction| self-introduction]] en una lista de correo, por ejemplo, ingrese la direcciÃ³n de correo electrÃ³nico que usted utiliza con esa lista.
 		</div><div class="para">
-			Use the comment field to include aliases or other information. (Some people use different keys for different purposes and identify each key with a comment, such as "Office" or "Open Source Projects.")
+			Utilice el campo de comentario para incluir un apodo o cualquier otra informaciÃ³n. (Algunas personas utilizan diferentes claves para diferentes propÃ³sitos, e identifican cada clave con un comentario, como por ejemplo "Oficina", o "Proyectos de cÃ³digo abierto".)
 		</div><div class="para">
-			At the confirmation prompt, enter the letter O to continue if all entries are correct, or use the other options to fix any problems. Finally, enter a passphrase for your secret key. The <code class="code">gpg</code> program asks you to enter your passphrase twice to ensure you made no typing errors.
+			En el mensaje de confirmaciÃ³n, ingrese la letra O para continuar si todas las opciones son correctas, o utilice las opciones propuestas para solucionar cualquier problema. Ingrese una frase de acceso para su clave secreta. El programa GPG le pide que ingrese dos veces su frase de acceso para asegurarse que no haya cometido errores de tipeo.
 		</div><div class="para">
-			Finally, <code class="code">gpg</code> generates random data to make your key as unique as possible. Move your mouse, type random keys, or perform other tasks on the system during this step to speed up the process. Once this step is finished, your keys are complete and ready to use:
-		</div><pre class="screen">pub  1024D/1B2AFA1C 2005-03-31 John Q. Doe (Fedora Docs Project) &lt;jqdoe at example.com&gt;
+			Por Ãºltimo, <code class="code">gpg</code> genera datos aleatorios para hacer que su clave sea lo mÃ¡s autÃ©ntica posible. Mueva su ratÃ³n, presiona teclas de manera azarosa, o realice alguna otra tarea en el sistema durante este paso para acelerar el proceso. Una vez ha finalizado, sus claves estÃ¡n completas y listas para ser utilizadas:
+		</div><pre class="screen">pub  1024D/1B2AFA1C 2005-03-31 Juan Perez (Fedora Docs Project) &lt;jperez at ejemplo.com&gt;
 Key fingerprint = 117C FE83 22EA B843 3E86  6486 4320 545E 1B2A FA1C
 sub  1024g/CEA4B22E 2005-03-31 [expires: 2006-03-31]
 </pre><div class="para">
-			The key fingerprint is a shorthand "signature" for your key. It allows you to confirm to others that they have received your actual public key without any tampering. You do not need to write this fingerprint down. To display the fingerprint at any time, use this command, substituting your email address: <code class="code"> gpg --fingerprint jqdoe at example.com </code>
+			La huella digital de la clave es una "firma" abreviada de su clave. Le permite confirmar a otros que han recibido su clave pÃºblica actual sin haber sido alterada. usted no necesita anotar esta huella. Para verla en cualquier siempre que lo desea, utilice el siguiente comando, sustituyendo su direcciÃ³n de correo electrÃ³nico: <code class="code"> gpg --fingerprint jperez at ejemplo.com </code>
 		</div><div class="para">
-			Your "GPG key ID" consists of 8 hex digits identifying the public key. In the example above, the GPG key ID is 1B2AFA1C. In most cases, if you are asked for the key ID, you should prepend "0x" to the key ID, as in "0x1B2AFA1C".
-		</div><div class="warning"><h2>Warning</h2><div class="para">
-				If you forget your passphrase, the key cannot be used and any data encrypted using that key will be lost.
-			</div></div></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Encryption-Using_GPG-About_Public_Key_Encryption">3.9.4. About Public Key Encryption</h3></div></div></div><div class="orderedlist"><ol><li><div class="para">
+			Su "ID de clave GPG" consiste en 8 dÃgitos hexadecimales identificando la llave pÃºblica. En el ejemplo, el ID de clave GPG es 1B2AFA1C. En la mayorÃa de los casos, si se le pregunta por el ID de su clave deberÃa anteponer "0x" al ID de la clave, como en "0x1B2AFA1C".
+		</div><div class="warning"><h2>Advertencia</h2><div class="para">
+				Si se olvida su frase de acceso, la clave no podrÃ¡ ser utilizada y cualquier dato encriptado por ella serÃ¡ perdido.
+			</div></div></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Encryption-Using_GPG-About_Public_Key_Encryption">3.9.4. Acerca del encriptado de la clave pÃºblica</h3></div></div></div><div class="orderedlist"><ol><li><div class="para">
 					<a href="http://en.wikipedia.org/wiki/Public-key_cryptography">Wikipedia - Public Key Cryptography</a>
 				</div></li><li><div class="para">
 					<a href="http://computer.howstuffworks.com/encryption.htm">HowStuffWorks - Encryption</a>
 				</div></li></ol></div></div></div></div><div class="chapter" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h2 class="title" id="chap-Security_Guide-General_Principles_of_Information_Security">CapÃtulo 4. Principios Generales sobre la Seguridad de la InformaciÃ³n</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Security_Guide-General_Principles_of_Information_Security-Tips_Guides_and_Tools">4.1. Consejos, GuÃas y Herramientas</a></span></dt></dl></div><div class="para">
-		The following general principals provide an overview of good security practices:
+		Los siguientes principios generales ofrecen una visiÃ³n panorÃ¡mica de algunas buenas actitudes para adoptar relacionadas con la seguridad:
 	</div><div class="itemizedlist"><ul><li><div class="para">
-				encrypt all data transmitted over networks to help prevent man-in-the-middle attacks and eavesdropping. It is important to encrypt authentication information, such as passwords.
+				encriptar todos los datos transmitidos por la red para ayudar a prevenir ataques del hombre-en-el-medio y escuchas. Es importante encriptar de la informaciÃ³n de autenticaciÃ³n, como ser contraseÃ±as.
 			</div></li><li><div class="para">
-				minimize the amount of software installed and running services.
+				minimice la cantidad de software instalado y de servicios en ejecuciÃ³n.
 			</div></li><li><div class="para">
-				use security-enhancing software and tools, for example, Security-Enhanced Linux (SELinux) for Mandatory Access Control (MAC), Netfilter iptables for packet filtering (firewall), and the GNU Privacy Guard (GnuPG) for encrypting files.
+				utilice herramientas y software destinadas a mejorar la seguridad de su equipo. Por ejemplo, Security-Enhanced Linux (SELinux) para Control de Acceso Obligatorio (MAC, por las siglas en inglÃ©s de Mandatory Acces Control), Netfilter iptables para filtrar paquetes (cortafuegos), y la ProtecciÃ³n de Privacidad GNU(GnuPG, por las siglas en inglÃ©s de GNU Privacy Guard) para los archivos encriptados.
 			</div></li><li><div class="para">
-				if possible, run each network service on a separate system to minimize the risk of one compromised service being used to compromise other services.
+				si es posible, corra cada servicio de red en un servidor separado para minimizar el riesgo de que un compromiso en uno de los servicios se use para comprometer a los otros.
 			</div></li><li><div class="para">
-				maintain user accounts: create and enforce a strong password policy; delete unused user accounts.
+				mantenga las cuentas de usuario: crear y aplicar una polÃtica buena de contraseÃ±as; borre las cuentas de usuarios no usados.
 			</div></li><li><div class="para">
-				routinely review system and application logs. By default, security-relevant system logs are written to <code class="filename">/var/log/secure</code> and <code class="filename">/var/log/audit/audit.log</code>. Note: sending logs to a dedicated log server helps prevent attackers from easily modifying local logs to avoid detection.
+				periÃ³dicamente consulte los archivos de logs del sistema y de las diferentes aplicaciones que utilice. Por defecto, los archivos de logs del sistema que sean pertinentes para la seguridad del equipo, son almacenados en <code class="filename">/var/log/secure</code> y <code class="filename">/var/log/audit/audit.log</code>. Nota: enviar archivos de logs hacia un servidor dedicado ayuda a prevenir que los atacantes puedan modificar fÃ¡cilmente los archivos de logs locales, y de este modo evitar ser detectados.
 			</div></li><li><div class="para">
-				never log in as the root user unless absolutely necessary. It is recommended that administrators use <code class="command">sudo</code> to execute commands as root when required. Users capable of running <code class="command">sudo</code> are specified in <code class="filename">/etc/sudoers</code>. Use the <code class="command">visudo</code> utility to edit <code class="filename">/etc/sudoers</code>.
+				nunca ingrese como root directamente, a menos de que sea absolutamente necesario. Los administradores deben usar <code class="command">sudo</code> para ejecutar comandos como root cuando sea necesario. Las cuentas capaces de usar <code class="command">sudo</code> se especifican en <code class="filename">/etc/sudoers</code>, que se edita con el utilitario <code class="command">visudo</code>.
 			</div></li></ul></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h2 class="title" id="sect-Security_Guide-General_Principles_of_Information_Security-Tips_Guides_and_Tools">4.1. Consejos, GuÃas y Herramientas</h2></div></div></div><div class="para">
-			The United States' <a href="http://www.nsa.gov/">National Security Agency (NSA)</a> provides hardening guides and tips for many different operating systems, to help government agencies, businesses, and individuals secure their systems against attack. The following guides (in PDF format) provide guidance for Red Hat Enterprise Linux 5:
+			La <a href="www.nsa.gov">Agencia de Seguridad Nacional</a> de los Estados Unidos de NorteamÃ©rica (NSA, por las siglas en inglÃ©s de National Security Agency), ofrece guÃas muy estrictas y consejos para numerosos sistemas operativos, para ayudar a las agencias gubernamentales, empresas e individuos a que prevengan los ataques a la seguridad de sus sistemas. Las siguientes guÃas (en formato PDF) proveen un tutorial para el Linux para Empresas de Red Hat 5:
 		</div><div class="itemizedlist"><ul><li><div class="para">
-					<a href="http://www.nsa.gov/ia/_files/os/redhat/rhel5-pamphlet-i731.pdf">Hardening Tips for the Red Hat Enterprise Linux 5</a>
+					<a href="http://www.nsa.gov/ia/_files/os/redhat/rhel5-pamphlet-i731.pdf">Consejos Reforzados para el Linux para Empresas de Red HAT 5</a>
 				</div></li><li><div class="para">
-					<a href="http://www.nsa.gov/ia/_files/os/redhat/rhel5-guide-i731.pdf">Guide to the Secure Configuration of Red Hat Enterprise Linux 5</a>
+					<a href="http://www.nsa.gov/ia/_files/os/redhat/rhel5-guide-i731.pdf">GuÃa para la ConfiguraciÃ³n Segura del Linux para Empresas de Red Hat 5</a>
 				</div></li></ul></div><div class="para">
-			The <a href="http://www.disa.mil/">Defense Information Systems Agency (DISA)</a> provides documentation, checklists, and tests to help secure your system (<a href="http://iase.disa.mil/index2.html">Information Assurance Support Environment</a>). The <a href="http://iase.disa.mil/stigs/stig/unix-stig-v5r1.pdf">UNIX SECURITY TECHNICAL IMPLEMENTATION GUIDE</a> (PDF) is a very specific guide to UNIX security - an advanced knowledge of UNIX and Linux is recommended before reading this guide.
+			La <a href="http://www.disa.mil/">Agencia de Defensa de InformaciÃ³n de Sistemas (DISA, por las siglas en inglÃ©s de Defense Information Systems Agency)</a> ofrece documentaciÃ³n, evaluaciones, y listas con Ãtems a ser verificados, que le ayudarÃ¡n a asegurar su sistema (<a href="http://iase.disa.mil/index2.html">Soporte para un Entorno Seguro de la InformaciÃ³n</a>). La <a href="http://iase.disa.mil/stigs/stig/unix-stig-v5r1.pdf">GUIA DE IMPLEMENTACION TECNICA DE SEGURIDAD UNIX</a> (PDF) es una guÃa muy especÃfica para la seguridad en sistemas UNIX - antes de leerla, se recomienda poseer un conocimiento avanzado tanto de UNIX como de Linux.
 		</div><div class="para">
-			The DISA <a href="http://iase.disa.mil/stigs/checklist/unix_checklist_v5r1-16_20090215.ZIP">UNIX Security Checklist Version 5, Release 1.16</a> provides a collection of documents and checklists, ranging from the correct ownerships and modes for system files, to patch control.
+			La <a href="http://iase.disa.mil/stigs/checklist/unix_checklist_v5r1-16_20090215.ZIP">Lista de Items a verificarse para la Seguridad de UNIX Version 5, Release 1.16</a> de DISA ofrece diferentes documentos y listas de verificaciÃ³n, abarcando aspectos que van desde el correcto establecimiento de la pertenencia de los archivos del sistema, hasta el control de parches.
 		</div><div class="para">
-			Also, DISA has made available <a href="http://iase.disa.mil/stigs/SRR/unix.html">UNIX SPR scripts</a> that allow administrators to check specific settings on systems. These scripts provide XML-formatted reports listing any known vulnerable settings.
-		</div></div></div><div class="chapter" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h2 class="title" id="chap-Security_Guide-Secure_Installation">CapÃtulo 5. Secure Installation</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Security_Guide-Secure_Installation-Disk_Partitions">5.1. Disk Partitions</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Secure_Installation-Utilize_LUKS_Partition_Encryption">5.2. Utilize LUKS Partition Encryption</a></span></dt></dl></div><div class="para">
-		Security begins with the first time you put that CD or DVD into your disk drive to install Fedora. Configuring your system securely from the beginning makes it easier to implement additional security settings later.
-	</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h2 class="title" id="sect-Security_Guide-Secure_Installation-Disk_Partitions">5.1. Disk Partitions</h2></div></div></div><div class="para">
-			The NSA recommends creating separate partitions for /boot, /, /home, /tmp, and /var/tmp. The reasons for each are different and we will address each partition.
+			Al mismo tiempo, DISA ha puesto a disposiciÃ³n diferentes <a href="http://iase.disa.mil/stigs/SRR/unix.html">programas de UNIX SPR</a> que permiten a los administradores verificar configuraciones especÃficas en sus sistemas. Estos programas ofrecen reportes en formato XML, en los que muestran todas las configuraciones vulnerables conocidas.
+		</div></div></div><div class="chapter" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h2 class="title" id="chap-Security_Guide-Secure_Installation">CapÃtulo 5. InstalaciÃ³n segura</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Security_Guide-Secure_Installation-Disk_Partitions">5.1. Particiones de Disco</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Secure_Installation-Utilize_LUKS_Partition_Encryption">5.2. Utilice EncriptaciÃ³n de ParticiÃ³n con LUKS</a></span></dt></dl></div><div class="para">
+		La seguridad comienza con la primera vez que pone un CD o DVD para instalar Fedora. La configuraciÃ³n de su sistema en forma segura desde el principio hace mÃ¡s fÃ¡cil implementar configuraciones de seguridad adicional mÃ¡s adelante.
+	</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h2 class="title" id="sect-Security_Guide-Secure_Installation-Disk_Partitions">5.1. Particiones de Disco</h2></div></div></div><div class="para">
+			La NSA recomienda crear particiones separadas para /boot, /, /home, /tmp y /var/tmp. Las razones son diferentes y se tratarÃ¡ por separado para cada particiÃ³n.
 		</div><div class="para">
-			/boot - This partition is the first partition that is read by the system during boot up. The boot loader and kernel images that are used to boot your system into Fedora are stored in this partition. This partition should not be encrypted. If this partition is included in / and that partition is encrypted or otherwise becomes unavailable then your system will not be able to boot.
+			/boot - Esta particiÃ³n es la primera particiÃ³n que se lee durante el arranque. El cargador de arranque y las imÃ¡genes del kernel que se usan para arrancar su sistema Fedora se almacenan en esta particiÃ³n. Esta particiÃ³n no debe ser encriptada. Si esta particiÃ³n se incluye en / y la misma es encriptada o de alguna forma se vuelve no disponible, entonces su sistema no podrÃ¡ arrancar.
 		</div><div class="para">
-			/home - When user data (/home) is stored in / instead of in a separate partition, the partition can fill up causing the operating system to become unstable. Also, when upgrading your system to the next version of Fedora it is a lot easier when you can keep your data in the /home partition as it will not be overwritten during installation. If the root partition (/) becomes corrupt your data could be lost forever. By using a separate partition there is slightly more protection against data loss. You can also target this partition for frequent backups.
+			/home - Cuando los datos del usuario (/home) se almacenan en / en vez de una particiÃ³n separada, la particiÃ³n se puede llenar haciendo que el sistema operativo se vuelva inestable. TambiÃ©n, cuando se actualice su sistema a la siguiente versiÃ³n de Fedora, es mucho mÃ¡s fÃ¡cil cuando puede mantener sus datos en una particiÃ³n /home dado que no serÃ¡ sobrescrita durante la instalaciÃ³n. Si la particiÃ³n raÃz (/) se corrompe, sus datos se perderÃ¡n para siempre. Usando una particiÃ³n separada hay un poco mÃ¡s de protecciÃ³n contra la pÃ©rdida de datos. TambiÃ©n se puede elegir esa particiÃ³n para los respaldos frecuentes.
 		</div><div class="para">
-			/tmp and /var/tmp - Both the /tmp and the /var/tmp directories are used to store data that doesn't need to be stored for a long period of time. However if a lot of data floods one of these directories it can consume all of your storage space. If this happens and these directories are stored within / then your system could become unstable and crash. For this reason, moving these directories into their own partitions is a good idea.
-		</div></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h2 class="title" id="sect-Security_Guide-Secure_Installation-Utilize_LUKS_Partition_Encryption">5.2. Utilize LUKS Partition Encryption</h2></div></div></div><div class="para">
-			Since Fedora 9, implementation of <a href="http://fedoraproject.org/wiki/Security_Guide/9/LUKSDiskEncryption">Linux Unified Key Setup-on-disk-format</a>(LUKS) encryption has become a lot easier. During the installation process an option to encrypt your partitions will be presented to the user. The user must supply a passphrase that will be the key to unlock the bulk encryption key that will be used to secure the partition's data.
+			/tmp y /var/tmp - Ambos directorios /tmp y the /var/tmp se usan para almacenar datos que no se necesitan guardar por mucho tiempo. Sin embargo, si un montÃ³n de datos inundan uno de estos directorios, puede consumir todo el espacio libre. Si esto pasa y estos directorios se almacenan en /, entonces su sistema se puede volver inestable y colgarse. Por esta razÃ³n, mover estos directorios a sus propias particiones es una buena idea.
+		</div></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h2 class="title" id="sect-Security_Guide-Secure_Installation-Utilize_LUKS_Partition_Encryption">5.2. Utilice EncriptaciÃ³n de ParticiÃ³n con LUKS</h2></div></div></div><div class="para">
+			Desde Fedora 9 la implementaciÃ³n de <a href="http://fedoraproject.org/wiki/Security_Guide/9/LUKSDiskEncryption">Linux Unified Key Setup-on-disk-format</a>(LUKS) ha permitido que el encriptado sea algo mucho mÃ¡s sencillo. A lo largo del proceso de instalaciÃ³n se le presenta una opciÃ³n al usuario que le permite encriptar sus particiones. El usuario debe suministrar una frase de acceso que serÃ¡ la llave para desbloquear el encriptado en masa que se utilizarÃ¡ para proteger los datos de las particiones.
 		</div><div class="para">
-			Fedora 8, however, does not have LUKS support built-in; however it is easily implemented. <a href="http://fedoraproject.org/wiki/Security_Guide/9/LUKSDiskEncryption#Step-by-Step_Instructions">Step-by-step procedures</a> are available that allow the user to implement partition encryption on their Fedora 8 installation.
-		</div></div></div><div class="chapter" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h2 class="title" id="chap-Security_Guide-Software_Maintenance">CapÃtulo 6. Mantenimiento de Software</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Security_Guide-Software_Maintenance-Install_Minimal_Software">6.1. Install Minimal Software</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates">6.2. Plan and Configure Security Updates</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates-Adjusting_Automatic_Updates">6.3. Ajustando Actualizaciones AutomÃ¡ticas</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Software_Maintenance-Install_Signed_Packages_from_Well_Known_Repositories">6.4. Install Signed Packages from Well Known Repositories</a></span></dt></dl></div><div 
 class="para">
-		Software maintenance is extremely important to maintaining a secure system. It is vital to patch software as soon as it becomes available in order to prevent attackers from using known holes to infiltrate your system.
-	</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h2 class="title" id="sect-Security_Guide-Software_Maintenance-Install_Minimal_Software">6.1. Install Minimal Software</h2></div></div></div><div class="para">
-			It is best practice to install only the packages you will use because each piece of software on your computer could possibly contain a vulnerability. If you are installing from the DVD media take the opportunity to select exactly what packages you want to install during the installation. When you find you need another package, you can always add it to the system later.
-		</div></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h2 class="title" id="sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates">6.2. Plan and Configure Security Updates</h2></div></div></div><div class="para">
-			All software contains bugs. Often, these bugs can result in a vulnerability that can expose your system to malicious users. Unpatched systems are a common cause of computer intrusions. You should have a plan to install security patches in a timely manner to close those vulnerabilities so they can not be exploited.
+			A pesar que Fedora 8 no posea soporte LUKS establecido por defecto, Ã©ste puede ser fÃ¡cilmente implementado. En este enlace estÃ¡n disponibles las <a href="http://fedoraproject.org/wiki/Security_Guide/9/LUKSDiskEncryption#Step-by-Step_Instructions">instrucciones-paso-a-paso</a> que permiten al usuario implementar el encriptado de particiones en su instalaciÃ³n de Fedora.
+		</div></div></div><div class="chapter" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h2 class="title" id="chap-Security_Guide-Software_Maintenance">CapÃtulo 6. Mantenimiento de Software</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Security_Guide-Software_Maintenance-Install_Minimal_Software">6.1. Instale el software mÃnimo</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates">6.2. Planifique y configure actualizaciones de seguridad</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates-Adjusting_Automatic_Updates">6.3. Ajustando las actualizaciones automÃ¡ticas</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Software_Maintenance-Install_Signed_Packages_from_Well_Known_Repositories">6.4. Instale paquetes identificados desde repositorios conocidos</
 a></span></dt></dl></div><div class="para">
+		Una manutenciÃ³n adecuada del software es extremadamente importante a la hora de asegurar un sistema. Es fundamental enmendar software que presenta un fallo en el momento inmediato a la apariciÃ³n de la soluciÃ³n, de modo de evitar que atacantes que conocen ese fallo, lo aprovechen y se infiltren en su sistema.
+	</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h2 class="title" id="sect-Security_Guide-Software_Maintenance-Install_Minimal_Software">6.1. Instale el software mÃnimo</h2></div></div></div><div class="para">
+			La mejor forma de proceder es instalando solo los paquetes que se van a utilizar, ya que cada pieza de software en su computadora posiblemente pueda contener algÃºn tipo de debilidad. Si estÃ¡ realizando una instalaciÃ³n desde un DVD, dese la oportunidad de elegir exactamente quÃ© paquetes quiere instalar en este proceso. Si se da cuenta que necesita otro paquete, siempre puede agregÃ¡rselo luego al sistema.
+		</div></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h2 class="title" id="sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates">6.2. Planifique y configure actualizaciones de seguridad</h2></div></div></div><div class="para">
+			Todo software contiene errores. A menudo, estos errores pueden transformarse en una debilidad que podrÃa dejar a su sistema expuesto a usuarios maliciosos. Sistemas no enmendados son una causa frecuente de intrusiones en las computadoras. DeberÃa tener planificada la instalaciÃ³n de parches de seguridad en una forma sincronizada de manera tal de poder anular esas debilidades, y evitar asÃ que sean aprovechadas.
 		</div><div class="para">
-			For home users, security updates should be installed as soon as possible. Configuring automatic installation of security updates is one way to avoid having to remember, but does carry a slight risk that something can cause a conflict with your configuration or with other software on the system.
+			Para usuarios hogareÃ±os, las actualizaciones de seguridad deberÃan ser instaladas lo antes posible. Configurar instalaciones automÃ¡ticas de ellas es una manera de evitar el tener que recordar constantemente hacerlo, pero podrÃa traer aparejado el pequeÃ±o riesgo de que un determinado paquete entre en conflicto con la configuraciÃ³n de su sistema, o con otro software de su equipo.
 		</div><div class="para">
-			For business or advanced home users, security updates should be tested and schedule for installation. Additional controls will need to be used to protect the system during the time between the patch release and its installation on the system. These controls would depend on the exact vulnerability, but could include additional firewall rules, the use of external firewalls, or changes in software settings.
-		</div></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h2 class="title" id="sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates-Adjusting_Automatic_Updates">6.3. Ajustando Actualizaciones AutomÃ¡ticas</h2></div></div></div><div class="para">
-			Fedora is configured to apply all updates on a daily schedule. If you want to change the how your system installs updates you must do so via '''Software Update Preferences'''. You can change the schedule, the type of updates to apply or to notify you of available updates.
+			Para los comercios o para los usuarios hogareÃ±os avanzados, las actualizaciones de seguridad deberÃan ser probadas y planeadas para ser instaladas. SerÃ¡ necesario utilizar controles adicionales para proteger el sistema durante el lapso de tiempo existente entre el lanzamiento del parche y su instalaciÃ³n definitiva. Estos controles dependen de la debilidad en cuestiÃ³n, pero pueden incluir reglas de cortafuegos adicionales, o el uso de cortafuegos externos, o cambios en las configuraciones del sistema.
+		</div></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h2 class="title" id="sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates-Adjusting_Automatic_Updates">6.3. Ajustando las actualizaciones automÃ¡ticas</h2></div></div></div><div class="para">
+			Fedora estÃ¡ configurado para aplicar todas las actualizaciones en un dÃa designado. Si quiere modificar el modo en que su sistema instala las actualizaciones, debe hacerlo a travÃ©s de las "Preferencias de ActualizaciÃ³n de Software". Puede cambiar el dÃa elegido, el tipo de actualizaciones a ser aplicadas o si desea o no que se le notifique cuando existan actualizaciones disponibles.
 		</div><div class="para">
-			In Gnome, you can find controls for your updates at: <code class="code">System -&gt; Preferences -&gt; System -&gt; Software Updates</code>. In KDE it is located at: <code class="code">Applications -&gt; Settings -&gt; Software Updates</code>.
-		</div></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h2 class="title" id="sect-Security_Guide-Software_Maintenance-Install_Signed_Packages_from_Well_Known_Repositories">6.4. Install Signed Packages from Well Known Repositories</h2></div></div></div><div class="para">
-			Software packages are published through repositories. All well known repositories support package signing. Package signing uses public key technology to prove that the package that was published by the repository has not been changed since the signature was applied. This provides some protection against installing software that may have been maliciously altered after the package was created but before you downloaded it.
+			En Gnome, puede encontrar controles para sus actualizaciones en <code class="code">Sistema -&gt; Preferencias -&gt; Actualizar Software</code>. En KDE puede hacerlo en: <code class="code">Lanzador de Aplicaciones - &gt; Sistema -&gt; Actualizar Software</code>.
+		</div></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h2 class="title" id="sect-Security_Guide-Software_Maintenance-Install_Signed_Packages_from_Well_Known_Repositories">6.4. Instale paquetes identificados desde repositorios conocidos</h2></div></div></div><div class="para">
+			Los paquetes de software son publicados a travÃ©s de repositorios. Todos los repositorios mÃ¡s conocidos tienen soporte para poder identificar sus paquetes. La identificaciÃ³n de los paquetes utiliza tecnologÃa de llave pÃºblica para confirmar que un paquete publicado por un repositorio, no haya sido alterado desde que la identificaciÃ³n fue aplicada. Esto ofrece cierta protecciÃ³n para evitar instalar software que podrÃa haber sido alterado maliciosamente luego de haber sido creado, pero antes que usted lo haya descargado.
 		</div><div class="para">
-			Using too many repositories, untrustworthy repositories, or repositories with unsigned packages has a higher risk of introducing malicious or vulnerable code into your system. Use caution when adding repositories to yum/software update.
+			Si se utilizan demasiados repositorios, o que no sean confiables, o que alojen paquetes sin identificaciÃ³n, se corre un gran riesgo de introducciÃ³n de cÃ³digos maliciosos o que pueden llegar a debilitar su sistema. Sea precavido al agregar repositorios para actualizar su sistema.
 		</div></div></div><div class="chapter" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h2 class="title" id="chap-Security_Guide-References">CapÃtulo 7. Referencias</h2></div></div></div><div class="para">
-		The following references are pointers to additional information that is relevant to SELinux and Fedora but beyond the scope of this guide. Note that due to the rapid development of SELinux, some of this material may only apply to specific releases of Fedora.
-	</div><div class="variablelist" id="vari-Security_Guide-References-Books"><h6>Libros</h6><dl><dt><span class="term">SELinux by Example</span></dt><dd><div class="para">
-					Mayer, MacMillan, and Caplan
+		Las siguientes referencias tienen como objetivo orientar la bÃºsqueda de informaciÃ³n adicional relacionada con SELinux and Fedora pero estÃ¡n mÃ¡s allÃ¡ del alcance de esta guÃa. Tenga en cuenta que debido al veloz desarrollo de SELinux, algunos de estos materiales podrÃan utilizarse sÃ³lo en versiones especÃficas de Fedora.
+	</div><div class="variablelist" id="vari-Security_Guide-References-Books"><h6>Libros</h6><dl><dt><span class="term">SELinux en Ejemplos</span></dt><dd><div class="para">
+					Mayer, MacMillan y Caplan
 				</div><div class="para">
 					Prentice Hall, 2007
-				</div></dd></dl></div><div class="variablelist" id="vari-Security_Guide-References-Tutorials_and_Help"><h6>Tutoriales y Ayuda</h6><dl><dt><span class="term">Understanding and Customizing the Apache HTTP SELinux Policy</span></dt><dd><div class="para">
+				</div></dd></dl></div><div class="variablelist" id="vari-Security_Guide-References-Tutorials_and_Help"><h6>Tutoriales y Ayuda</h6><dl><dt><span class="term">Entendiendo y personalizando la polÃtica de SELinux para HTTP de Apache</span></dt><dd><div class="para">
 					<a href="http://fedora.redhat.com/docs/selinux-apache-fc3/">http://fedora.redhat.com/docs/selinux-apache-fc3/</a>
-				</div></dd><dt><span class="term">Tutorials and talks from Russell Coker</span></dt><dd><div class="para">
+				</div></dd><dt><span class="term">Tutoriales y charlas de Russell Coker</span></dt><dd><div class="para">
 					<a href="http://www.coker.com.au/selinux/talks/ibmtu-2004/">http://www.coker.com.au/selinux/talks/ibmtu-2004/</a>
-				</div></dd><dt><span class="term">Generic Writing SELinux policy HOWTO</span></dt><dd><div class="para">
+				</div></dd><dt><span class="term">Tutorial genÃ©rico para escritura de PolÃticas de SELinux</span></dt><dd><div class="para">
 					<a href="http://www.lurking-grue.org/writingselinuxpolicyHOWTO.html">http://www.lurking-grue.org/writingselinuxpolicyHOWTO.html</a>
-				</div></dd><dt><span class="term">Red Hat Knowledgebase</span></dt><dd><div class="para">
+				</div></dd><dt><span class="term">Base de Conocimientos de Red Hat</span></dt><dd><div class="para">
 					<a href="http://kbase.redhat.com/">http://kbase.redhat.com/</a>
-				</div></dd></dl></div><div class="variablelist" id="vari-Security_Guide-References-General_Information"><h6>InformaciÃ³n General</h6><dl><dt><span class="term">NSA SELinux main website</span></dt><dd><div class="para">
+				</div></dd></dl></div><div class="variablelist" id="vari-Security_Guide-References-General_Information"><h6>InformaciÃ³n General</h6><dl><dt><span class="term">Sitio web principal de SELinux de la NSA</span></dt><dd><div class="para">
 					<a href="http://www.nsa.gov/research/selinux/index.shtml">http://www.nsa.gov/selinux/</a>
 				</div></dd><dt><span class="term">NSA SELinux FAQ</span></dt><dd><div class="para">
 					<a href="http://www.nsa.gov/research/selinux/faqs.shtml">http://www.nsa.gov/selinux/info/faq.cfm</a>
 				</div></dd><dt><span class="term">Fedora SELinux FAQ </span></dt><dd><div class="para">
 					<a href="http://fedora.redhat.com/docs/selinux-faq-fc3/">http://fedora.redhat.com/docs/selinux-faq-fc3/</a>
-				</div></dd><dt><span class="term">SELinux NSA's Open Source Security Enhanced Linux</span></dt><dd><div class="para">
+				</div></dd><dt><span class="term">Linux de seguridad mejorada de cÃ³digo abierto de la NSA</span></dt><dd><div class="para">
 					<a href="http://www.oreilly.com/catalog/selinux/">http://www.oreilly.com/catalog/selinux/</a>
-				</div></dd></dl></div><div class="variablelist" id="vari-Security_Guide-References-Technology"><h6>TecnologÃa</h6><dl><dt><span class="term">An Overview of Object Classes and Permissions</span></dt><dd><div class="para">
+				</div></dd></dl></div><div class="variablelist" id="vari-Security_Guide-References-Technology"><h6>TecnologÃa</h6><dl><dt><span class="term">Un repaso de las clases de objetos y permisos</span></dt><dd><div class="para">
 					<a href="http://www.tresys.com/selinux/obj_perms_help.html">http://www.tresys.com/selinux/obj_perms_help.html</a>
-				</div></dd><dt><span class="term">Integrating Flexible Support for Security Policies into the Linux Operating System (a history of Flask implementation in Linux)</span></dt><dd><div class="para">
+				</div></dd><dt><span class="term">IntegraciÃ³n del soporte flexible para las PolÃticas de Seguridad dentro del Sistema Operativo Linux (una historia de la implementaciÃ³n de Flask en Linux)</span></dt><dd><div class="para">
 					<a href="http://www.nsa.gov/research/_files/selinux/papers/selsymp2005.pdf">http://www.nsa.gov/research/_files/selinux/papers/selsymp2005.pdf</a>
-				</div></dd><dt><span class="term">Implementing SELinux as a Linux Security Module</span></dt><dd><div class="para">
+				</div></dd><dt><span class="term">ImplemenetaciÃ³n de SELinux como un mÃ³dulo de seguridad de linux</span></dt><dd><div class="para">
 					<a href="http://www.nsa.gov/research/_files/publications/implementing_selinux.pdf">http://www.nsa.gov/research/_files/publications/implementing_selinux.pdf</a>
-				</div></dd><dt><span class="term">A Security Policy Configuration for the Security-Enhanced Linux</span></dt><dd><div class="para">
+				</div></dd><dt><span class="term">Una ConfiguraciÃ³n de PolÃtica de Seguridad para el Linux de Seguridad Mejorada</span></dt><dd><div class="para">
 					<a href="http://www.nsa.gov/research/_files/selinux/papers/policy/policy.shtml">http://www.nsa.gov/research/_files/selinux/papers/policy/policy.shtml</a>
-				</div></dd></dl></div><div class="variablelist" id="vari-Security_Guide-References-Community"><h6>Comunidad</h6><dl><dt><span class="term">Fedora SELinux User Guide</span></dt><dd><div class="para">
+				</div></dd></dl></div><div class="variablelist" id="vari-Security_Guide-References-Community"><h6>Comunidad</h6><dl><dt><span class="term">GuÃa del Usuario de SELinux de Fedora</span></dt><dd><div class="para">
 					<a href="http://docs.fedoraproject.org/selinux-user-guide/">http://docs.fedoraproject.org/selinux-user-guide/</a>
-				</div></dd><dt><span class="term">SELinux community page</span></dt><dd><div class="para">
+				</div></dd><dt><span class="term">PÃ¡gina comunitaria de SELinux</span></dt><dd><div class="para">
 					<a href="http://selinux.sourceforge.net">http://selinux.sourceforge.net</a>
 				</div></dd><dt><span class="term">IRC</span></dt><dd><div class="para">
 					irc.freenode.net, #selinux
-				</div></dd></dl></div><div class="variablelist" id="vari-Security_Guide-References-History"><h6>History</h6><dl><dt><span class="term">Quick history of Flask</span></dt><dd><div class="para">
+				</div></dd></dl></div><div class="variablelist" id="vari-Security_Guide-References-History"><h6>Historia</h6><dl><dt><span class="term">Historia breve de Flask</span></dt><dd><div class="para">
 					<a href="http://www.cs.utah.edu/flux/fluke/html/flask.html">http://www.cs.utah.edu/flux/fluke/html/flask.html</a>
-				</div></dd><dt><span class="term">Full background on Fluke</span></dt><dd><div class="para">
+				</div></dd><dt><span class="term">Antecedentes completos sobre Fluke</span></dt><dd><div class="para">
 					<a href="http://www.cs.utah.edu/flux/fluke/html/index.html">http://www.cs.utah.edu/flux/fluke/html/index.html</a>
 				</div></dd></dl></div></div></div></body></html>


