Sun Jul 19 23:53:16 UTC 2009

Author: sparks

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

Added Files:
	Security_Guide-Encryption-Data_in_Motion-Secure_Shell.html 
	Security_Guide-Encryption-Data_in_Motion-Virtual_Private_Networks.html 
	Security_Guide-Encryption-Data_in_Motion.html 
	Security_Guide-Encryption-Protecting_Data_at_Rest-File_Based_Encryption.html 
	We_Need_Feedback.html chap-Security_Guide-Encryption.html 
	chap-Security_Guide-General_Principles_of_Information_Security.html 
	chap-Security_Guide-References.html 
	chap-Security_Guide-Secure_Installation.html 
	chap-Security_Guide-Securing_Your_Network.html 
	chap-Security_Guide-Security_Overview.html 
	chap-Security_Guide-Software_Maintenance.html index.html 
	pref-Security_Guide-Preface.html 
	sect-Security_Guide-Additional_Resources-Related_Books.html 
	sect-Security_Guide-Additional_Resources-Related_Documentation.html 
	sect-Security_Guide-Additional_Resources-Useful_Firewall_Websites.html 
	sect-Security_Guide-Additional_Resources-Useful_IP_Tables_Websites.html 
	sect-Security_Guide-Additional_Resources-Useful_Kerberos_Websites.html 
	sect-Security_Guide-Additional_Resources-Useful_PAM_Websites.html 
	sect-Security_Guide-Additional_Resources-Useful_TCP_Wrappers_Websites.html 
	sect-Security_Guide-Altering_xinetd_Configuration_Files-Access_Control_Options.html 
	sect-Security_Guide-Altering_xinetd_Configuration_Files-Binding_and_Redirection_Options.html 
	sect-Security_Guide-Altering_xinetd_Configuration_Files-Resource_Management_Options.html 
	sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Network_Security.html 
	sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Server_Security.html 
	sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Workstation_and_Home_PC_Security.html 
	sect-Security_Guide-Attackers_and_Vulnerabilities.html 
	sect-Security_Guide-Basic_Firewall_Configuration-Activating_the_IPTables_Service.html 
	sect-Security_Guide-Basic_Firewall_Configuration-Enabling_and_Disabling_the_Firewall.html 
	sect-Security_Guide-Basic_Firewall_Configuration-Other_Ports.html 
	sect-Security_Guide-Basic_Firewall_Configuration-Saving_the_Settings.html 
	sect-Security_Guide-Basic_Firewall_Configuration-Trusted_Services.html 
	sect-Security_Guide-Command_Options_for_IPTables-Command_Options.html 
	sect-Security_Guide-Command_Options_for_IPTables-IPTables_Match_Options.html 
	sect-Security_Guide-Command_Options_for_IPTables-IPTables_Parameter_Options.html 
	sect-Security_Guide-Command_Options_for_IPTables-Listing_Options.html 
	sect-Security_Guide-Command_Options_for_IPTables-Target_Options.html 
	sect-Security_Guide-Common_Exploits_and_Attacks.html 
	sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Installation-Instructions.html 
	sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Things_of_note.html 
	sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Usage_Instructions.html 
	sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives.html 
	sect-Security_Guide-Encryption-Protecting_Data_at_Rest-Full_Disk_Encryption.html 
	sect-Security_Guide-Encryption-Using_GPG-About_Public_Key_Encryption.html 
	sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE.html 
	sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE1.html 
	sect-Security_Guide-Encryption-Using_GPG.html 
	sect-Security_Guide-Evaluating_the_Tools-Anticipating_Your_Future_Needs.html 
	sect-Security_Guide-Evaluating_the_Tools-Nessus.html 
	sect-Security_Guide-Evaluating_the_Tools-Nikto.html 
	sect-Security_Guide-Evaluating_the_Tools-VLAD_the_Scanner.html 
	sect-Security_Guide-FORWARD_and_NAT_Rules-DMZs_and_IPTables.html 
	sect-Security_Guide-FORWARD_and_NAT_Rules-Prerouting.html 
	sect-Security_Guide-Firewalls-Additional_Resources.html 
	sect-Security_Guide-Firewalls-Basic_Firewall_Configuration.html 
	sect-Security_Guide-Firewalls-Common_IPTables_Filtering.html 
	sect-Security_Guide-Firewalls-FORWARD_and_NAT_Rules.html 
	sect-Security_Guide-Firewalls-IPTables_and_Connection_Tracking.html 
	sect-Security_Guide-Firewalls-IPv6.html 
	sect-Security_Guide-Firewalls-Malicious_Software_and_Spoofed_IP_Addresses.html 
	sect-Security_Guide-Firewalls-Using_IPTables.html 
	sect-Security_Guide-Firewalls.html 
	sect-Security_Guide-IPTables-Additional_Resources.html 
	sect-Security_Guide-IPTables-Command_Options_for_IPTables.html 
	sect-Security_Guide-IPTables-Differences_Between_IPTables_and_IPChains.html 
	sect-Security_Guide-IPTables-IPTables_Control_Scripts.html 
	sect-Security_Guide-IPTables-IPTables_and_IPv6.html 
	sect-Security_Guide-IPTables-Saving_IPTables_Rules.html 
	sect-Security_Guide-IPTables.html 
	sect-Security_Guide-IPTables_Match_Options-Additional_Match_Option_Modules.html 
	sect-Security_Guide-IPTables_Match_Options-ICMP_Protocol.html 
	sect-Security_Guide-IPTables_Match_Options-UDP_Protocol.html 
	sect-Security_Guide-IPsec_Host_to_Host_Configuration-Manual_IPsec_Host_to_Host_Configuration.html 
	sect-Security_Guide-IPsec_Network_to_Network_Configuration-Manual_IPsec_Network_to_Network_Configuration.html 
	sect-Security_Guide-Kerberos-Additional_Resources.html 
	sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Client.html 
	sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Server.html 
	sect-Security_Guide-Kerberos-Domain_to_Realm_Mapping.html 
	sect-Security_Guide-Kerberos-How_Kerberos_Works.html 
	sect-Security_Guide-Kerberos-Kerberos_Terminology.html 
	sect-Security_Guide-Kerberos-Kerberos_and_PAM.html 
	sect-Security_Guide-Kerberos-Setting_Up_Cross_Realm_Authentication.html 
	sect-Security_Guide-Kerberos-Setting_Up_Secondary_KDCs.html 
	sect-Security_Guide-Kerberos.html 
	sect-Security_Guide-LUKS_Disk_Encryption-Links_of_Interest.html 
	sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-Step_by_Step_Instructions.html 
	sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-What_you_have_just_accomplished.html 
	sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories.html 
	sect-Security_Guide-LUKS_Disk_Encryption.html 
	sect-Security_Guide-Option_Fields-Access_Control.html 
	sect-Security_Guide-Option_Fields-Expansions.html 
	sect-Security_Guide-Option_Fields-Shell_Commands.html 
	sect-Security_Guide-PAM_Configuration_File_Format-Control_Flag.html 
	sect-Security_Guide-PAM_Configuration_File_Format-Module_Arguments.html 
	sect-Security_Guide-PAM_Configuration_File_Format-Module_Name.html 
	sect-Security_Guide-PAM_and_Administrative_Credential_Caching-Common_pam_timestamp_Directives.html 
	sect-Security_Guide-PAM_and_Device_Ownership-Application_Access.html 
	sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Additional_Resources.html 
	sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Creating_PAM_Modules.html 
	sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_File_Format.html 
	sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_Files.html 
	sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Administrative_Credential_Caching.html 
	sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Device_Ownership.html 
	sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Sample_PAM_Configuration_Files.html 
	sect-Security_Guide-Pluggable_Authentication_Modules_PAM.html 
	sect-Security_Guide-Secure_Installation-Utilize_LUKS_Partition_Encryption.html 
	sect-Security_Guide-Securing_FTP-Anonymous_Access.html 
	sect-Security_Guide-Securing_FTP-Use_TCP_Wrappers_To_Control_Access.html 
	sect-Security_Guide-Securing_FTP-User_Accounts.html 
	sect-Security_Guide-Securing_NFS-Beware_of_Syntax_Errors.html 
	sect-Security_Guide-Securing_NFS-Do_Not_Use_the_no_root_squash_Option.html 
	sect-Security_Guide-Securing_NFS-NFS_Firewall_Configuration.html 
	sect-Security_Guide-Securing_NIS-Assign_Static_Ports_and_Use_iptables_Rules.html 
	sect-Security_Guide-Securing_NIS-Edit_the_varypsecurenets_File.html 
	sect-Security_Guide-Securing_NIS-Use_Kerberos_Authentication.html 
	sect-Security_Guide-Securing_NIS-Use_a_Password_like_NIS_Domain_Name_and_Hostname.html 
	sect-Security_Guide-Securing_Portmap-Protect_portmap_With_iptables.html 
	sect-Security_Guide-Securing_Sendmail-Mail_only_Users.html 
	sect-Security_Guide-Securing_Sendmail-NFS_and_Sendmail.html 
	sect-Security_Guide-Security_Updates.html 
	sect-Security_Guide-Server_Security-Securing_FTP.html 
	sect-Security_Guide-Server_Security-Securing_NFS.html 
	sect-Security_Guide-Server_Security-Securing_NIS.html 
	sect-Security_Guide-Server_Security-Securing_Portmap.html 
	sect-Security_Guide-Server_Security-Securing_Sendmail.html 
	sect-Security_Guide-Server_Security-Securing_the_Apache_HTTP_Server.html 
	sect-Security_Guide-Server_Security-Verifying_Which_Ports_Are_Listening.html 
	sect-Security_Guide-Server_Security.html 
	sect-Security_Guide-Single_Sign_on_SSO-Configuring_Firefox_to_use_Kerberos_for_SSO.html 
	sect-Security_Guide-Single_Sign_on_SSO-Getting_Started_with_your_new_Smart_Card.html 
	sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Enrollment_Works.html 
	sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Login_Works.html 
	sect-Security_Guide-Single_Sign_on_SSO.html 
	sect-Security_Guide-Software_Maintenance-Install_Signed_Packages_from_Well_Known_Repositories.html 
	sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates-Adjusting_Automatic_Updates.html 
	sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates.html 
	sect-Security_Guide-TCP_Wrappers_Configuration_Files-Option_Fields.html 
	sect-Security_Guide-TCP_Wrappers_and_xinetd-Additional_Resources.html 
	sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers_Configuration_Files.html 
	sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd.html 
	sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd_Configuration_Files.html 
	sect-Security_Guide-TCP_Wrappers_and_xinetd.html 
	sect-Security_Guide-Threats_to_Server_Security-Inattentive_Administration.html 
	sect-Security_Guide-Threats_to_Server_Security-Inherently_Insecure_Services.html 
	sect-Security_Guide-Threats_to_Server_Security-Unpatched_Services.html 
	sect-Security_Guide-Threats_to_Workstation_and_Home_PC_Security-Vulnerable_Client_Applications.html 
	sect-Security_Guide-Updating_Packages-Applying_the_Changes.html 
	sect-Security_Guide-Updating_Packages-Installing_Signed_Packages.html 
	sect-Security_Guide-Updating_Packages-Verifying_Signed_Packages.html 
	sect-Security_Guide-Using_IPTables-Basic_Firewall_Policies.html 
	sect-Security_Guide-Using_IPTables-Saving_and_Restoring_IPTables_Rules.html 
	sect-Security_Guide-Virtual_Private_Networks_VPNs-Creating_an_IPsec_Connection.html 
	sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec.html 
	sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Host_to_Host_Configuration.html 
	sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Installation.html 
	sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Network_to_Network_Configuration.html 
	sect-Security_Guide-Virtual_Private_Networks_VPNs-Starting_and_Stopping_an_IPsec_Connection.html 
	sect-Security_Guide-Virtual_Private_Networks_VPNs-VPNs_and_PROD.html 
	sect-Security_Guide-Virtual_Private_Networks_VPNs.html 
	sect-Security_Guide-Vulnerability_Assessment-Defining_Assessment_and_Testing.html 
	sect-Security_Guide-Vulnerability_Assessment-Evaluating_the_Tools.html 
	sect-Security_Guide-Vulnerability_Assessment.html 
	sect-Security_Guide-xinetd_Configuration_Files-Altering_xinetd_Configuration_Files.html 
	sect-Security_Guide-xinetd_Configuration_Files-The_etcxinetd.d_Directory.html 
Log Message:
Adding first complete version of Security Guide in es_ES.

--- NEW FILE Security_Guide-Encryption-Data_in_Motion-Secure_Shell.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.6. Shell Seguro</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="chap-Security_Guide-Encryption.html" title="CapÃtulo 3. Encryption" /><link rel="prev" href="Security_Guide-Encryption-Data_in_Motion-Virtual_Private_Networks.html" title="3.5. Virtual Private Networks" /><link rel="next" href="sect-Security_Guide-LUKS_Disk_Encryption.html" title="3.7. LUKS Disk Encryption" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/im
 ages/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="Security_Guide-Encryption-Data_in_Motion-Virtual_Private_Networks.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-LUKS_Disk_Encryption.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h2 class="title" id="Security_Guide-Encryption-Data_in_Motion-Secure_Shell">3.6. Shell Seguro</h2></div></div></div><div class="para">
			Secure Shell (SSH) is a powerful network protocol used to communicate with another system over a secure channel. The transmissions over SSH are encrypted and protected from interception. Cryptographic log-on can also be utilized to provide a better authentication method over traditional usernames and passwords.
		</div><div class="para">
			SSH is very easy to activate. By simply starting the sshd service, the system will begin to accept connections and will allow access to the system when a correct username and password is provided during the connection process. The standard TCP port for the SSH service is 22, however this can be changed by modifying the configuration file <span class="emphasis"><em>/etc/ssh/sshd_config</em></span> and restarting the service. This file also contains other configuration options for SSH.
		</div><div class="para">
			Secure Shell (SSH) also provides encrypted tunnels between computers but only using a single port. <a href="http://www.redhatmagazine.com/2007/11/27/advanced-ssh-configuration-and-tunneling-we-dont-need-no-stinking-vpn-software">Port forwarding can be done over an SSH tunnel</a> and traffic will be encrypted as it passes over that tunnel but using port forwarding is not as fluid as a VPN.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="Security_Guide-Encryption-Data_in_Motion-Virtual_Private_Networks.html"><strong>Anterior</strong>3.5. Virtual Private Networks</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-LUKS_Disk_Encryption.html"><strong>Siguiente</strong>3.7. LUKS Disk Encryption</a></li></ul></body></html>

--- NEW FILE Security_Guide-Encryption-Data_in_Motion-Virtual_Private_Networks.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.5. Virtual Private Networks</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="chap-Security_Guide-Encryption.html" title="CapÃtulo 3. Encryption" /><link rel="prev" href="Security_Guide-Encryption-Data_in_Motion.html" title="3.4. Datos en Movimiento" /><link rel="next" href="Security_Guide-Encryption-Data_in_Motion-Secure_Shell.html" title="3.6. Shell Seguro" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_ri
 ght.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="Security_Guide-Encryption-Data_in_Motion.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="Security_Guide-Encryption-Data_in_Motion-Secure_Shell.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h2 class="title" id="Security_Guide-Encryption-Data_in_Motion-Virtual_Private_Networks">3.5. Virtual Private Networks</h2></div></div></div><div class="para">
			Las Redes Virtuales Privadas (VPN, por las iniciales en inglÃ©s de Virtual Private Networks), proveen tÃºneles encriptados entre computadoras o redes de computadoras a lo largo de todos los puertos. Esto significa lÃ³gicamente que tanto el cliente como el servidor estÃ¡n conectados a la misma red a travÃ©s de VPN. Los VPNs son muy comunes, y muy fÃ¡ciles de configurar y de utilizar.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="Security_Guide-Encryption-Data_in_Motion.html"><strong>Anterior</strong>3.4. Datos en Movimiento</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="Security_Guide-Encryption-Data_in_Motion-Secure_Shell.html"><strong>Siguiente</strong>3.6. Shell Seguro</a></li></ul></body></html>

--- NEW FILE Security_Guide-Encryption-Data_in_Motion.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.4. Datos en Movimiento</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="chap-Security_Guide-Encryption.html" title="CapÃtulo 3. Encryption" /><link rel="prev" href="Security_Guide-Encryption-Protecting_Data_at_Rest-File_Based_Encryption.html" title="3.3. EncriptaciÃ³n Basada en Archivo" /><link rel="next" href="Security_Guide-Encryption-Data_in_Motion-Virtual_Private_Networks.html" title="3.5. Virtual Private Networks" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://do
 cs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="Security_Guide-Encryption-Protecting_Data_at_Rest-File_Based_Encryption.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="Security_Guide-Encryption-Data_in_Motion-Virtual_Private_Networks.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h2 class="title" id="Security_Guide-Encryption-Data_in_Motion">3.4. Datos en Movimiento</h2></div></div></div><div class="para">
			Los datos en movimiento son datos que estÃ¡n siendo transmitidos en una red. La mayor amenaza a este tipo de datos son las intercepciones y alteraciones que puedan sufrir. Los datos de su nombre de usuario y contraseÃ±a nunca deberÃan ser transmitidos en una red sin que viajen protegidos, ya que podrÃan ser interceptados, y de este modo permitir que alguien se haga pasar por usted, o que pueda obtener acceso a informaciÃ³n importante. Otro tipo de onformaciÃ³n privada, como son por ejemplo los datos de una cuenta bancaria, deberÃan tambiÃ©n ser protegidos cada vez que sean transmitidos a travÃ©s de una red. Si lo que se encripta es la sesiÃ³n entera de red iniciada, entonces no tiene que preocuparse acerca de posibles ataques a los datos que se transmitan en ella.
		</div><div class="para">
			Los datos en movimiento son particularmente vulnerables a los atacantes, ya que ellos no necesitan estar cerca de la computadora en donde estos datos son almacenados: simplemente necesitan estar en algÃºn punto del camino que esos datos estÃ¡n recorriendo. Los tÃºneles de encriptado pueden proteger los datos a lo largo del camino de las comunicaciones.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="Security_Guide-Encryption-Protecting_Data_at_Rest-File_Based_Encryption.html"><strong>Anterior</strong>3.3. EncriptaciÃ³n Basada en Archivo</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="Security_Guide-Encryption-Data_in_Motion-Virtual_Private_Networks.html"><strong>Siguiente</strong>3.5. Virtual Private Networks</a></li></ul></body></html>

--- NEW FILE Security_Guide-Encryption-Protecting_Data_at_Rest-File_Based_Encryption.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.3. EncriptaciÃ³n Basada en Archivo</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="chap-Security_Guide-Encryption.html" title="CapÃtulo 3. Encryption" /><link rel="prev" href="sect-Security_Guide-Encryption-Protecting_Data_at_Rest-Full_Disk_Encryption.html" title="3.2. EncriptaciÃ³n Completa de Disco" /><link rel="next" href="Security_Guide-Encryption-Data_in_Motion.html" title="3.4. Datos en Movimiento" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproje
 ct.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Encryption-Protecting_Data_at_Rest-Full_Disk_Encryption.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="Security_Guide-Encryption-Data_in_Motion.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h2 class="title" id="Security_Guide-Encryption-Protecting_Data_at_Rest-File_Based_Encryption">3.3. EncriptaciÃ³n Basada en Archivo</h2></div></div></div><div class="para">
			GnuPG (GPG) es una versiÃ³n de cÃ³digo abierto de PGP, que le permite firmar y/o encriptar un archivo o mensaje de correo electrÃ³nico. Esto es Ãºtil para mantener la integridad del mensaje o del archivo, y tambiÃ©n protege la confidencialidad de la informaciÃ³n contenida. En el caso del correo electrÃ³nico, GPG brinda una protecciÃ³n doble. No solo puede proveer protecciÃ³n para los datos en reposo, sino tambiÃ©n para los data en movimiento, luego que el mensaje ha sido enviado a travÃ©s de la red.
		</div><div class="para">
			El encriptado de archivos estÃ¡ orientado para proteger un archivo luego que Ã©ste haya abandonado su computadora, como cuando, por ejemplo, envÃa un CD a travÃ©s del correo electrÃ³nico. Algunas herramientas para encriptar archivos pueden dejar rastros de aquellos archivos que encriptan, rastros que podrÃan ser recuperados en algunas circunstancias por atacantes que tengan acceso fÃsico a su equipo. Para proteger de este tipo de ataques a los contenidos de los archivos, utilice la herramienta de encriptado de archivos combinada con alguna otra, como ser por ejemplo, el encriptado total del disco.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Encryption-Protecting_Data_at_Rest-Full_Disk_Encryption.html"><strong>Anterior</strong>3.2. EncriptaciÃ³n Completa de Disco</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="Security_Guide-Encryption-Data_in_Motion.html"><strong>Siguiente</strong>3.4. Datos en Movimiento</a></li></ul></body></html>

--- NEW FILE We_Need_Feedback.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2. Â¡Se necesita retroalimentaciÃ³n!</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="pref-Security_Guide-Preface.html" title="Prefacio" /><link rel="prev" href="pref-Security_Guide-Preface.html" title="Prefacio" /><link rel="next" href="chap-Security_Guide-Security_Overview.html" title="CapÃtulo 1. Security Overview" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p
 ><ul class="docnav"><li class="previous"><a accesskey="p" href="pref-Security_Guide-Preface.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="chap-Security_Guide-Security_Overview.html"><strong>Siguiente</strong></a></li></ul><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">
		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&product=Fedora%20Documentation">https://bugzilla.redhat.com/enter_bug.cgi?component=security-guide&product=Fedora%20Documentation</a>. Please select the proper component in the dropdown menu which should be the page name.
	</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="pref-Security_Guide-Preface.html"><strong>Anterior</strong>Prefacio</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="chap-Security_Guide-Security_Overview.html"><strong>Siguiente</strong>CapÃtulo 1. Security Overview</a></li></ul></body></html>

--- NEW FILE chap-Security_Guide-Encryption.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>CapÃtulo 3. Encryption</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="index.html" title="security-guide" /><link rel="prev" href="sect-Security_Guide-Additional_Resources-Useful_IP_Tables_Websites.html" title="2.9.7.2. Sitios web Ãºtiles sobre IP Tables" /><link rel="next" href="sect-Security_Guide-Encryption-Protecting_Data_at_Rest-Full_Disk_Encryption.html" title="3.2. EncriptaciÃ³n Completa de Disco" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject
 .org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Additional_Resources-Useful_IP_Tables_Websites.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-Protecting_Data_at_Rest-Full_Disk_Encryption.html"><strong>Siguiente</strong></a></li></ul><div class="chapter" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h2 class="title" id="chap-Security_Guide-Encryption">CapÃtulo 3. Encryption</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Security_Guide-Encryption.html#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.html">3.2. EncriptaciÃ³n Completa de Disco</a></span></dt><dt><span class="section"><a href="Secu
 rity_Guide-Encryption-Protecting_Data_at_Rest-File_Based_Encryption.html">3.3. EncriptaciÃ³n Basada en Archivo</a></span></dt><dt><span class="section"><a href="Security_Guide-Encryption-Data_in_Motion.html">3.4. Datos en Movimiento</a></span></dt><dt><span class="section"><a href="Security_Guide-Encryption-Data_in_Motion-Virtual_Private_Networks.html">3.5. Virtual Private Networks</a></span></dt><dt><span class="section"><a href="Security_Guide-Encryption-Data_in_Motion-Secure_Shell.html">3.6. Shell Seguro</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-LUKS_Disk_Encryption.html">3.7. LUKS Disk Encryption</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security_Guide-LUKS_Disk_Encryption.html#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.html">3.7.2. Manu
 ally Encrypting Directories</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-Step_by_Step_Instructions.html">3.7.3. Step-by-Step Instructions</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-What_you_have_just_accomplished.html">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.html">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.html">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.html#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.html">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.html">3.8.3. Step-by-Step Usage Instructions</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Things_of_note.html">3.8.4. Things of note</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Security_Guide-Encryption-Using_GPG.html">3.9. Using GNU Privacy Guard (GnuPG)</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security_Guide-Encryption-Using_GPG.html#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.html">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.html">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.html">3.9.4. About Public Key Encryption</a></span></dt></dl></dd></dl></div><div class="para">
		Existen dos clases principales de datos que deben ser protegidos: datos en reposo y datos en movimiento. Estas clases de datos son protegidas en forma similar utilizando tecnologÃa similar, pero la forma en que se implementa esta protecciÃ³n puede ser completamente diferente en un caso y en otro. Por sÃ solo, ningÃºn modo de protecciÃ³n puede prevenir nuestro sistema de todos los posibles mÃ©todos enque puede llegar a ser daÃ±ado, ya que la misma informaciÃ³n puede estar en descanso y en movimiento en diferentes lugares y al mismo tiempo.
	</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h2 class="title" id="sect-Security_Guide-Encryption-Data_at_Rest">3.1. Datos en Descanso</h2></div></div></div><div class="para">
			Los datos en reposo son los datos que se encuentran almacenados en un disco rÃgido, cinta, CD, DVD, o cualquier otro medio. La amenaza principal de este tipo de informaciÃ³n es la posibilidad de ser fÃsicamente robada. Laptops en los aeropuertos, CDs enviados a traves del correo postal, y cintas de respaldo que se dejan en los lugares equivocados son todos ejemplos de en los que los datos contenidos pueden ser accedidos mediante el robo. Si esos datos estuvieran encriptados en el dispositivo que los contiene, entonces no tendrÃa que preocuparse demasiado acerca de la posibilidad de que alguien mÃ¡s acceda a ellos.
		</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Additional_Resources-Useful_IP_Tables_Websites.html"><strong>Anterior</strong>2.9.7.2. Sitios web Ãºtiles sobre IP Tables</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-Protecting_Data_at_Rest-Full_Disk_Encryption.html"><strong>Siguiente</strong>3.2. EncriptaciÃ³n Completa de Disco</a></li></ul></body></html>

--- NEW FILE chap-Security_Guide-General_Principles_of_Information_Security.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>CapÃtulo 4. Principios Generales sobre la Seguridad de la InformaciÃ³n</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="index.html" title="security-guide" /><link rel="prev" href="sect-Security_Guide-Encryption-Using_GPG-About_Public_Key_Encryption.html" title="3.9.4. About Public Key Encryption" /><link rel="next" href="chap-Security_Guide-Secure_Installation.html" title="CapÃtulo 5. Secure Installation" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraprojec
 t.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Encryption-Using_GPG-About_Public_Key_Encryption.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="chap-Security_Guide-Secure_Installation.html"><strong>Siguiente</strong></a></li></ul><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="chap-Security_Guide-General_Principles_of_Information_Security.html#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:
	</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.
			</div></li><li><div class="para">
				minimize the amount of software installed and running services.
			</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.
			</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.
			</div></li><li><div class="para">
				maintain user accounts: create and enforce a strong password policy; delete unused user accounts.
			</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.
			</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>.
			</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:
		</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>
				</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>
				</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.
		</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.
		</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><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Encryption-Using_GPG-About_Public_Key_Encryption.html"><strong>Anterior</strong>3.9.4. About Public Key Encryption</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="chap-Security_Guide-Secure_Installation.html"><strong>Siguiente</strong>CapÃtulo 5. Secure Installation</a></li></ul></body></html>

--- NEW FILE chap-Security_Guide-References.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>CapÃtulo 7. Referencias</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="index.html" title="security-guide" /><link rel="prev" href="sect-Security_Guide-Software_Maintenance-Install_Signed_Packages_from_Well_Known_Repositories.html" title="6.4. Install Signed Packages from Well Known Repositories" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><
 li class="previous"><a accesskey="p" href="sect-Security_Guide-Software_Maintenance-Install_Signed_Packages_from_Well_Known_Repositories.html"><strong>Anterior</strong></a></li><li class="next"></li></ul><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
				</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">
					<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">
					<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">
					<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">
					<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">
					<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">
					<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">
					<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">
					<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">
					<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">
					<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">
					<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">
					<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">
					<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">
					<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><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Software_Maintenance-Install_Signed_Packages_from_Well_Known_Repositories.html"><strong>Anterior</strong>6.4. Install Signed Packages from Well Known Repo...</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li></ul></body></html>

--- NEW FILE chap-Security_Guide-Secure_Installation.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>CapÃtulo 5. Secure Installation</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="index.html" title="security-guide" /><link rel="prev" href="chap-Security_Guide-General_Principles_of_Information_Security.html" title="CapÃtulo 4. Principios Generales sobre la Seguridad de la InformaciÃ³n" /><link rel="next" href="sect-Security_Guide-Secure_Installation-Utilize_LUKS_Partition_Encryption.html" title="5.2. Utilize LUKS Partition Encryption" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right
 " href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security_Guide-General_Principles_of_Information_Security.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Secure_Installation-Utilize_LUKS_Partition_Encryption.html"><strong>Siguiente</strong></a></li></ul><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="chap-Security_Guide-Secure_Installation.html#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.html">5.2. Utilize LUKS Partition E
 ncryption</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.
		</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.
		</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.
		</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><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security_Guide-General_Principles_of_Information_Security.html"><strong>Anterior</strong>CapÃtulo 4. Principios Generales sobre la Segurid...</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Secure_Installation-Utilize_LUKS_Partition_Encryption.html"><strong>Siguiente</strong>5.2. Utilize LUKS Partition Encryption</a></li></ul></body></html>

--- NEW FILE chap-Security_Guide-Securing_Your_Network.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>CapÃtulo 2. Securing Your Network</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="index.html" title="security-guide" /><link rel="prev" href="sect-Security_Guide-Updating_Packages-Applying_the_Changes.html" title="1.5.4. Applying the Changes" /><link rel="next" href="sect-Security_Guide-Server_Security.html" title="2.2. Server Security" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documenta
 tion Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Updating_Packages-Applying_the_Changes.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Server_Security.html"><strong>Siguiente</strong></a></li></ul><div class="chapter" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h2 class="title" id="chap-Security_Guide-Securing_Your_Network">CapÃtulo 2. Securing Your Network</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Security_Guide-Securing_Your_Network.html#sect-Security_Guide-Workstation_Security">2.1. Workstation Security</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Security_Guide-Securing_Your_Network.html#sect-Security_Guide-Workstation_Security-Evaluating_Workstation_Security">2.1.1. Evaluating Workstation Security</a></span></dt><dt><span class="section"><a href="chap-Security_Guide-Securing_Your_Netwo
 rk.html#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="chap-Security_Guide-Securing_Your_Network.html#sect-Security_Guide-Workstation_Security-Password_Security">2.1.3. Password Security</a></span></dt><dt><span class="section"><a href="chap-Security_Guide-Securing_Your_Network.html#sect-Security_Guide-Workstation_Security-Administrative_Controls">2.1.4. Administrative Controls</a></span></dt><dt><span class="section"><a href="chap-Security_Guide-Securing_Your_Network.html#sect-Security_Guide-Workstation_Security-Available_Network_Services">2.1.5. Servicios de Red Disponibles</a></span></dt><dt><span class="section"><a href="chap-Security_Guide-Securing_Your_Network.html#sect-Security_Guide-Workstation_Security-Personal_Firewalls">2.1.6. Cortafuegos Personal:</a></span></dt><dt><span class="section"><a href="chap-Security_Guide-Securing_Your_Network.html#sect-Secur
 ity_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.html">2.2. Server Security</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security_Guide-Server_Security.html#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.html">2.2.2. Securing Portmap</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Server_Security-Securing_NIS.html">2.2.3. Securing NIS</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Server_Security-Securing_NFS.html">2.2.4. Securing NFS</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Server_Security-Securing_the_Apache_HTTP_Server.html">2.2.5. 
 Securing the Apache HTTP Server</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Server_Security-Securing_FTP.html">2.2.6. Securing FTP</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Server_Security-Securing_Sendmail.html">2.2.7. Securing Sendmail</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Server_Security-Verifying_Which_Ports_Are_Listening.html">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.html">2.3. Single Sign-on (SSO)</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security_Guide-Single_Sign_on_SSO.html#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.html">2.3.2. Getting Started with your new Smart Card</a></span></dt><dt><span class="sec
 tion"><a href="sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Enrollment_Works.html">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.html">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.html">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.html">2.4. Pluggable Authentication Modules (PAM)</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM.html#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.html">2.4.2. PAM Configuration Files</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_File_Format.html">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.html">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.html">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.html">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.html">2.4.7. PAM and Device Ownership</a></span></dt><dt><span class="section"><a hre
 f="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Additional_Resources.html">2.4.8. Additional Resources</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Security_Guide-TCP_Wrappers_and_xinetd.html">2.5. TCP Wrappers and xinetd</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security_Guide-TCP_Wrappers_and_xinetd.html#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.html">2.5.2. TCP Wrappers Configuration Files</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd.html">2.5.3. xinetd</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd_Configuration_Files.html">2.5.4. xinetd Configuration Files</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-TCP_Wrappers_and_xinetd-A
 dditional_Resources.html">2.5.5. Additional Resources</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Security_Guide-Kerberos.html">2.6. Kerberos</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security_Guide-Kerberos.html#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.html">2.6.2. Kerberos Terminology</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Kerberos-How_Kerberos_Works.html">2.6.3. How Kerberos Works</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Kerberos-Kerberos_and_PAM.html">2.6.4. Kerberos y PAM</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Server.html">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.html"
 >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.html">2.6.7. Domain-to-Realm Mapping</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Kerberos-Setting_Up_Secondary_KDCs.html">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.html">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.html">2.6.10. Additional Resources</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Security_Guide-Virtual_Private_Networks_VPNs.html">2.7. Virtual Private Networks (VPNs)</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security_Guide-Virtual_Private_Networks_VPNs.html#sect-Security_Guide-Virtual_Private_Networks_VPNs-How_Does_a_VPN_Work">2.7.1. How D
 oes a VPN Work?</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Virtual_Private_Networks_VPNs-VPNs_and_PROD.html">2.7.2. VPNs and Fedora</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec.html">2.7.3. IPsec</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Virtual_Private_Networks_VPNs-Creating_an_IPsec_Connection.html">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.html">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.html">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.html">2.7.7. IPsec Network-to-Network Configuration</a></span></d
 t><dt><span class="section"><a href="sect-Security_Guide-Virtual_Private_Networks_VPNs-Starting_and_Stopping_an_IPsec_Connection.html">2.7.8. Starting and Stopping an IPsec Connection</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Security_Guide-Firewalls.html">2.8. Firewalls</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security_Guide-Firewalls.html#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.html">2.8.2. ConfiguraciÃ³n BÃ¡sica del Cortafuego</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Firewalls-Using_IPTables.html">2.8.3. Uso de IPTables</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Firewalls-Common_IPTables_Filtering.html">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.html">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.html">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.html">2.8.7. IPTables y el Seguimiento de ConexiÃ³n</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Firewalls-IPv6.html">2.8.8. IPv6</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Firewalls-Additional_Resources.html">2.8.9. Additional Resources</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Security_Guide-IPTables.html">2.9. IPTables</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security_Guide-IPTables.html#sect-Security_Guide-IPTables-Packet_Filtering">2.9.1. Filtrado de Paquete</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-IP
 Tables-Differences_Between_IPTables_and_IPChains.html">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.html">2.9.3. Command Options for IPTables</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-IPTables-Saving_IPTables_Rules.html">2.9.4. Saving IPTables Rules</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-IPTables-IPTables_Control_Scripts.html">2.9.5. IPTables Control Scripts</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-IPTables-IPTables_and_IPv6.html">2.9.6. IPTables y IPv6</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-IPTables-Additional_Resources.html">2.9.7. Additional Resources</a></span></dt></dl></dd></dl></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h2 class="title" id="sect-Security_Guide-Workstation_Security">2.1. Workstat
 ion Security</h2></div></div></div><div class="para">
		Securing a Linux environment begins with the workstation. Whether locking down a personal machine or securing an enterprise system, sound security policy begins with the individual computer. A computer network is only as secure as its weakest node.
	</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Workstation_Security-Evaluating_Workstation_Security">2.1.1. Evaluating Workstation Security</h3></div></div></div><div class="para">
			When evaluating the security of a Fedora workstation, consider the following:
		</div><div class="itemizedlist"><ul><li><div class="para">
					<span class="emphasis"><em>BIOS and Boot Loader Security</em></span> â€” Can an unauthorized user physically access the machine and boot into single user or rescue mode without a password?
				</div></li><li><div class="para">
					<span class="emphasis"><em>Password Security</em></span> â€” How secure are the user account passwords on the machine?
				</div></li><li><div class="para">
					<span class="emphasis"><em>Administrative Controls</em></span> â€” Who has an account on the system and how much administrative control do they have?
				</div></li><li><div class="para">
					<span class="emphasis"><em>Available Network Services</em></span> â€” What services are listening for requests from the network and should they be running at all?
				</div></li><li><div class="para">
					<span class="emphasis"><em>Personal Firewalls</em></span> â€” What type of firewall, if any, is necessary?
				</div></li><li><div class="para">
					<span class="emphasis"><em>Security Enhanced Communication Tools</em></span> â€” Which tools should be used to communicate between workstations and which should be avoided?
				</div></li></ul></div></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Workstation_Security-BIOS_and_Boot_Loader_Security">2.1.2. BIOS and Boot Loader Security</h3></div></div></div><div class="para">
			Password protection for the BIOS (or BIOS equivalent) and the boot loader can prevent unauthorized users who have physical access to systems from booting using removable media or obtaining root privileges through single user mode. The security measures you should take to protect against such attacks depends both on the sensitivity of the information on the workstation and the location of the machine.
		</div><div class="para">
			For example, if a machine is used in a trade show and contains no sensitive information, then it may not be critical to prevent such attacks. However, if an employee's laptop with private, unencrypted SSH keys for the corporate network is left unattended at that same trade show, it could lead to a major security breach with ramifications for the entire company.
		</div><div class="para">
			If the workstation is located in a place where only authorized or trusted people have access, however, then securing the BIOS or the boot loader may not be necessary.
		</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-BIOS_and_Boot_Loader_Security-BIOS_Passwords">2.1.2.1. ContraseÃ±a BIOS</h4></div></div></div><div class="para">
				The two primary reasons for password protecting the BIOS of a computer are<sup>[<a id="id2989569" href="#ftn.id2989569" class="footnote">11</a>]</sup>:
			</div><div class="orderedlist"><ol><li><div class="para">
						<span class="emphasis"><em>Preventing Changes to BIOS Settings</em></span> â€” If an intruder has access to the BIOS, they can set it to boot from a diskette or CD-ROM. This makes it possible for them to enter rescue mode or single user mode, which in turn allows them to start arbitrary processes on the system or copy sensitive data.
					</div></li><li><div class="para">
						<span class="emphasis"><em>Preventing System Booting</em></span> â€” Some BIOSes allow password protection of the boot process. When activated, an attacker is forced to enter a password before the BIOS launches the boot loader.
					</div></li></ol></div><div class="para">
				Because the methods for setting a BIOS password vary between computer manufacturers, consult the computer's manual for specific instructions.
			</div><div class="para">
				If you forget the BIOS password, it can either be reset with jumpers on the motherboard or by disconnecting the CMOS battery. For this reason, it is good practice to lock the computer case if possible. However, consult the manual for the computer or motherboard before attempting to disconnect the CMOS battery.
			</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h5 class="title" id="sect-Security_Guide-BIOS_Passwords-Securing_Non_x86_Platforms">2.1.2.1.1. Securing Non-x86 Platforms</h5></div></div></div><div class="para">
					Other architectures use different programs to perform low-level tasks roughly equivalent to those of the BIOS on x86 systems. For instance, <span class="trademark">Intel</span>Â® <span class="trademark">Itanium</span>â„¢ computers use the <em class="firstterm">Extensible Firmware Interface</em> (<em class="firstterm">EFI</em>) shell.
				</div><div class="para">
					For instructions on password protecting BIOS-like programs on other architectures, refer to the manufacturer's instructions.
				</div></div></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-BIOS_and_Boot_Loader_Security-Boot_Loader_Passwords">2.1.2.2. Boot Loader Passwords</h4></div></div></div><div class="para">
				The primary reasons for password protecting a Linux boot loader are as follows:
			</div><div class="orderedlist"><ol><li><div class="para">
						<span class="emphasis"><em>Preventing Access to Single User Mode</em></span> â€” If attackers can boot the system into single user mode, they are logged in automatically as root without being prompted for the root password.
					</div></li><li><div class="para">
						<span class="emphasis"><em>Preventing Access to the GRUB Console</em></span> â€” If the machine uses GRUB as its boot loader, an attacker can use the GRUB editor interface to change its configuration or to gather information using the <code class="command">cat</code> command.
					</div></li><li><div class="para">
						<span class="emphasis"><em>Preventing Access to Insecure Operating Systems</em></span> â€” If it is a dual-boot system, an attacker can select an operating system at boot time (for example, DOS), which ignores access controls and file permissions.
					</div></li></ol></div><div class="para">
				Fedora ships with the GRUB boot loader on the x86 platform. For a detailed look at GRUB, refer to the Red Hat Installation Guide.
			</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h5 class="title" id="sect-Security_Guide-Boot_Loader_Passwords-Password_Protecting_GRUB">2.1.2.2.1. Password Protecting GRUB</h5></div></div></div><div class="para">
					You can configure GRUB to address the first two issues listed in <a class="xref" href="chap-Security_Guide-Securing_Your_Network.html#sect-Security_Guide-BIOS_and_Boot_Loader_Security-Boot_Loader_Passwords" title="2.1.2.2. Boot Loader Passwords">SecciÃ³nÂ 2.1.2.2, â€œBoot Loader Passwordsâ€</a> by adding a password directive to its configuration file. To do this, first choose a strong password, open a shell, log in as root, and then type the following command:
				</div><pre class="screen"><code class="command">/sbin/grub-md5-crypt</code>
</pre><div class="para">
					When prompted, type the GRUB password and press <span class="keycap"><strong>Enter</strong></span>. This returns an MD5 hash of the password.
				</div><div class="para">
					Next, edit the GRUB configuration file <code class="filename">/boot/grub/grub.conf</code>. Open the file and below the <code class="command">timeout</code> line in the main section of the document, add the following line:
				</div><pre class="screen"><code class="command">password --md5 <em class="replaceable"><code><password-hash></code></em></code>
</pre><div class="para">
					Replace <em class="replaceable"><code><password-hash></code></em> with the value returned by <code class="command">/sbin/grub-md5-crypt</code><sup>[<a id="id2989320" href="#ftn.id2989320" class="footnote">12</a>]</sup>.
				</div><div class="para">
					The next time the system boots, the GRUB menu prevents access to the editor or command interface without first pressing <span class="keycap"><strong>p</strong></span> followed by the GRUB password.
				</div><div class="para">
					Unfortunately, this solution does not prevent an attacker from booting into an insecure operating system in a dual-boot environment. For this, a different part of the <code class="filename">/boot/grub/grub.conf</code> file must be edited.
				</div><div class="para">
					Look for the <code class="computeroutput">title</code> line of the operating system that you want to secure, and add a line with the <code class="command">lock</code> directive immediately beneath it.
				</div><div class="para">
					For a DOS system, the stanza should begin similar to the following:
				</div><pre class="screen"><code class="computeroutput">title DOS lock</code>
</pre><div class="warning"><h2>Warning</h2><div class="para">
						A <code class="computeroutput">password</code> line must be present in the main section of the <code class="filename">/boot/grub/grub.conf</code> file for this method to work properly. Otherwise, an attacker can access the GRUB editor interface and remove the lock line.
					</div></div><div class="para">
					To create a different password for a particular kernel or operating system, add a <code class="command">lock</code> line to the stanza, followed by a password line.
				</div><div class="para">
					Each stanza protected with a unique password should begin with lines similar to the following example:
				</div><pre class="screen"><code class="computeroutput">title DOS lock password --md5 <em class="replaceable"><code><password-hash></code></em></code>
</pre></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-Workstation_Security-Password_Security">2.1.3. Password Security</h3></div></div></div><div class="para">
			Passwords are the primary method that Fedora uses to verify a user's identity. This is why password security is so important for protection of the user, the workstation, and the network.
		</div><div class="para">
			For security purposes, the installation program configures the system to use <em class="firstterm">Message-Digest Algorithm</em> (<span class="emphasis"><em>MD5</em></span>) and shadow passwords. It is highly recommended that you do not alter these settings.
		</div><div class="para">
			If MD5 passwords are deselected during installation, the older <em class="firstterm">Data Encryption Standard</em> (<em class="firstterm"><acronym class="acronym">DES</acronym></em>) format is used. This format limits passwords to eight alphanumeric characters (disallowing punctuation and other special characters), and provides a modest 56-bit level of encryption.
		</div><div class="para">
			If shadow passwords are deselected during installation, all passwords are stored as a one-way hash in the world-readable <code class="filename">/etc/passwd</code> file, which makes the system vulnerable to offline password cracking attacks. If an intruder can gain access to the machine as a regular user, he can copy the <code class="filename">/etc/passwd</code> file to his own machine and run any number of password cracking programs against it. If there is an insecure password in the file, it is only a matter of time before the password cracker discovers it.
		</div><div class="para">
			Shadow passwords eliminate this type of attack by storing the password hashes in the file <code class="filename">/etc/shadow</code>, which is readable only by the root user.
		</div><div class="para">
			This forces a potential attacker to attempt password cracking remotely by logging into a network service on the machine, such as SSH or FTP. This sort of brute-force attack is much slower and leaves an obvious trail as hundreds of failed login attempts are written to system files. Of course, if the cracker starts an attack in the middle of the night on a system with weak passwords, the cracker may have gained access before dawn and edited the log files to cover his tracks.
		</div><div class="para">
			In addition to format and storage considerations is the issue of content. The single most important thing a user can do to protect his account against a password cracking attack is create a strong password.
		</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Password_Security-Creating_Strong_Passwords">2.1.3.1. Creating Strong Passwords</h4></div></div></div><div class="para">
				When creating a secure password, it is a good idea to follow these guidelines:
			</div><div class="itemizedlist"><ul><li><div class="para">
						<span class="emphasis"><em>Do Not Use Only Words or Numbers</em></span> â€” Never use only numbers or words in a password.
					</div><div class="para">
						Algunos ejemplos inseguros incluyen los siguientes:
					</div><div class="itemizedlist"><ul><li><div class="para">
								8675309
							</div></li><li><div class="para">
								juan
							</div></li><li><div class="para">
								hackme
							</div></li></ul></div></li><li><div class="para">
						<span class="emphasis"><em>Do Not Use Recognizable Words</em></span> â€” Words such as proper names, dictionary words, or even terms from television shows or novels should be avoided, even if they are bookended with numbers.
					</div><div class="para">
						Algunos ejemplos inseguros incluyen los siguientes:
					</div><div class="itemizedlist"><ul><li><div class="para">
								john1
							</div></li><li><div class="para">
								DS-9
							</div></li><li><div class="para">
								mentat123
							</div></li></ul></div></li><li><div class="para">
						<span class="emphasis"><em>Do Not Use Words in Foreign Languages</em></span> â€” Password cracking programs often check against word lists that encompass dictionaries of many languages. Relying on foreign languages for secure passwords is not secure.
					</div><div class="para">
						Algunos ejemplos inseguros incluyen los siguientes:
					</div><div class="itemizedlist"><ul><li><div class="para">
								cheguevara
							</div></li><li><div class="para">
								bienvenido1
							</div></li><li><div class="para">
								1dumbKopf
							</div></li></ul></div></li><li><div class="para">
						<span class="emphasis"><em>Do Not Use Hacker Terminology</em></span> â€” If you think you are elite because you use hacker terminology â€” also called l337 (LEET) speak â€” in your password, think again. Many word lists include LEET speak.
					</div><div class="para">
						Algunos ejemplos inseguros incluyen los siguientes:
					</div><div class="itemizedlist"><ul><li><div class="para">
								H4X0R
							</div></li><li><div class="para">
								1337
							</div></li></ul></div></li><li><div class="para">
						<span class="emphasis"><em>Do Not Use Personal Information</em></span> â€” Avoid using any personal information in your passwords. If the attacker knows your identity, the task of deducing your password becomes easier. The following is a list of the types of information to avoid when creating a password:
					</div><div class="para">
						Algunos ejemplos inseguros incluyen los siguientes:
					</div><div class="itemizedlist"><ul><li><div class="para">
								Su nombre
							</div></li><li><div class="para">
								El nombre de su mascota
							</div></li><li><div class="para">
								El nombre de un miembro de la familia
							</div></li><li><div class="para">
								Cualquier fecha de cumpleaÃ±os
							</div></li><li><div class="para">
								Su nÃºmero de telefono o su codigo postal
							</div></li></ul></div></li><li><div class="para">
						<span class="emphasis"><em>Do Not Invert Recognizable Words</em></span> â€” Good password checkers always reverse common words, so inverting a bad password does not make it any more secure.
					</div><div class="para">
						Algunos ejemplos inseguros incluyen los siguientes:
					</div><div class="itemizedlist"><ul><li><div class="para">
								R0X4H
							</div></li><li><div class="para">
								nauj
							</div></li><li><div class="para">
								9-DS
							</div></li></ul></div></li><li><div class="para">
						<span class="emphasis"><em>Do Not Write Down Your Password</em></span> â€” Never store a password on paper. It is much safer to memorize it.
					</div></li><li><div class="para">
						<span class="emphasis"><em>Do Not Use the Same Password For All Machines</em></span> â€” It is important to make separate passwords for each machine. This way if one system is compromised, all of your machines are not immediately at risk.
					</div></li></ul></div><div class="para">
				The following guidelines will help you to create a strong password:
			</div><div class="itemizedlist"><ul><li><div class="para">
						<span class="emphasis"><em>Make the Password at Least Eight Characters Long</em></span> â€” The longer the password, the better. If using MD5 passwords, it should be 15 characters or longer. With DES passwords, use the maximum length (eight characters).
					</div></li><li><div class="para">
						<span class="emphasis"><em>Mix Upper and Lower Case Letters</em></span> â€” Fedora is case sensitive, so mix cases to enhance the strength of the password.
					</div></li><li><div class="para">
						<span class="emphasis"><em>Mix Letters and Numbers</em></span> â€” Adding numbers to passwords, especially when added to the middle (not just at the beginning or the end), can enhance password strength.
					</div></li><li><div class="para">
						<span class="emphasis"><em>Include Non-Alphanumeric Characters</em></span> â€” Special characters such as &, $, and > can greatly improve the strength of a password (this is not possible if using DES passwords).
					</div></li><li><div class="para">
						<span class="emphasis"><em>Pick a Password You Can Remember</em></span> â€” The best password in the world does little good if you cannot remember it; use acronyms or other mnemonic devices to aid in memorizing passwords.
					</div></li></ul></div><div class="para">
				With all these rules, it may seem difficult to create a password that meets all of the criteria for good passwords while avoiding the traits of a bad one. Fortunately, there are some steps you can take to generate an easily-remembered, secure password.
			</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h5 class="title" id="sect-Security_Guide-Creating_Strong_Passwords-Secure_Password_Creation_Methodology">2.1.3.1.1. MetodologÃa de CreaciÃ³n de ContraseÃ±a Segura</h5></div></div></div><div class="para">
					There are many methods that people use to create secure passwords. One of the more popular methods involves acronyms. For example:
				</div><div class="itemizedlist"><ul><li><div class="para">
							Think of an easily-remembered phrase, such as:
						</div><div class="para">
							"over the river and through the woods, to grandmother's house we go."
						</div></li><li><div class="para">
							Next, turn it into an acronym (including the punctuation).
						</div><div class="para">
							<strong class="userinput"><code>otrattw,tghwg.</code></strong>
						</div></li><li><div class="para">
							Add complexity by substituting numbers and symbols for letters in the acronym. For example, substitute <strong class="userinput"><code>7</code></strong> for <strong class="userinput"><code>t</code></strong> and the at symbol (<strong class="userinput"><code>@</code></strong>) for <strong class="userinput"><code>a</code></strong>:
						</div><div class="para">
							<strong class="userinput"><code>o7r at 77w,7ghwg.</code></strong>
						</div></li><li><div class="para">
							Add more complexity by capitalizing at least one letter, such as <strong class="userinput"><code>H</code></strong>.
						</div><div class="para">
							<strong class="userinput"><code>o7r at 77w,7gHwg.</code></strong>
						</div></li><li><div class="para">
							<span class="emphasis"><em>Finally, do not use the example password above for any systems, ever</em></span>.
						</div></li></ul></div><div class="para">
					While creating secure passwords is imperative, managing them properly is also important, especially for system administrators within larger organizations. The following section details good practices for creating and managing user passwords within an organization.
				</div></div></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Password_Security-Creating_User_Passwords_Within_an_Organization">2.1.3.2. Creating User Passwords Within an Organization</h4></div></div></div><div class="para">
				If an organization has a large number of users, the system administrators have two basic options available to force the use of good passwords. They can create passwords for the user, or they can let users create their own passwords, while verifying the passwords are of acceptable quality.
			</div><div class="para">
				Creating the passwords for the users ensures that the passwords are good, but it becomes a daunting task as the organization grows. It also increases the risk of users writing their passwords down.
			</div><div class="para">
				For these reasons, most system administrators prefer to have the users create their own passwords, but actively verify that the passwords are good and, in some cases, force users to change their passwords periodically through password aging.
			</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h5 class="title" id="sect-Security_Guide-Creating_User_Passwords_Within_an_Organization-Forcing_Strong_Passwords">2.1.3.2.1. Forcing Strong Passwords</h5></div></div></div><div class="para">
					To protect the network from intrusion it is a good idea for system administrators to verify that the passwords used within an organization are strong ones. When users are asked to create or change passwords, they can use the command line application <code class="command">passwd</code>, which is <em class="firstterm">Pluggable Authentication Manager</em> (<em class="firstterm">PAM</em>) aware and therefore checks to see if the password is too short or otherwise easy to crack. This check is performed using the <code class="filename">pam_cracklib.so</code> PAM module. Since PAM is customizable, it is possible to add more password integrity checkers, such as <code class="filename">pam_passwdqc</code> (available from <a href="http://www.openwall.com/passwdqc/">http://www.openwall.com/passwdqc/</a>) or to write a new module. For a list of available PAM modules, refer to <a href="http://www.kernel.org/pub/linux/libs/pam/modules.html">http://www.kernel.org/pub/linux/libs/pam/mod
 ules.html</a>. For more information about PAM, refer to <a class="xref" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM.html" title="2.4. Pluggable Authentication Modules (PAM)">SecciÃ³nÂ 2.4, â€œPluggable Authentication Modules (PAM)â€</a>.
				</div><div class="para">
					The password check that is performed at the time of their creation does not discover bad passwords as effectively as running a password cracking program against the passwords.
				</div><div class="para">
					Many password cracking programs are available that run under Fedora, although none ship with the operating system. Below is a brief list of some of the more popular password cracking programs:
				</div><div class="note"><h2>Note</h2><div class="para">
						None of these tools are supplied with Fedora and are therefore not supported by Fedora in any way.
					</div></div><div class="itemizedlist"><ul><li><div class="para">
							<span class="emphasis"><em><span class="application"><strong>John The Ripper</strong></span></em></span> â€” A fast and flexible password cracking program. It allows the use of multiple word lists and is capable of brute-force password cracking. It is available online at <a href="http://www.openwall.com/john/">http://www.openwall.com/john/</a>.
						</div></li><li><div class="para">
							<span class="emphasis"><em><span class="application"><strong>Crack</strong></span></em></span> â€” Perhaps the most well known password cracking software, <span class="application"><strong>Crack</strong></span> is also very fast, though not as easy to use as <span class="application"><strong>John The Ripper</strong></span>. It can be found online at <a href="http://www.crypticide.com/alecm/security/c50-faq.html">http://www.crypticide.com/alecm/security/c50-faq.html</a>.
						</div></li><li><div class="para">
							<span class="emphasis"><em><span class="application"><strong>Slurpie</strong></span></em></span> â€” <span class="application"><strong>Slurpie</strong></span> is similar to <span class="application"><strong>John The Ripper</strong></span> and <span class="application"><strong>Crack</strong></span>, but it is designed to run on multiple computers simultaneously, creating a distributed password cracking attack. It can be found along with a number of other distributed attack security evaluation tools online at <a href="http://www.ussrback.com/distributed.htm">http://www.ussrback.com/distributed.htm</a>.
						</div></li></ul></div><div class="warning"><h2>Warning</h2><div class="para">
						Always get authorization in writing before attempting to crack passwords within an organization.
					</div></div></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h5 class="title" id="sect-Security_Guide-Passphrases">2.1.3.2.2. Passphrases</h5></div></div></div><div class="para">
					Passphrases and passwords are the cornerstone to security in most of today's systems. Unfortunately, techniques such as biometrics and two-factor authentication have not yet become mainstream in many systems which has become a major problem. If passwords are going to be used to secure a system, then the use of passphrases should be considered. Passphrases are longer than passwords and provide better protection than a password even when implemented with non-standard characters such as numbers and symbols.
				</div></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h5 class="title" id="sect-Security_Guide-Creating_User_Passwords_Within_an_Organization-Password_Aging">2.1.3.2.3. Password Aging</h5></div></div></div><div class="para">
					Password aging is another technique used by system administrators to defend against bad passwords within an organization. Password aging means that after a specified period (usually 90 days), the user is prompted to create a new password. The theory behind this is that if a user is forced to change his password periodically, a cracked password is only useful to an intruder for a limited amount of time. The downside to password aging, however, is that users are more likely to write their passwords down.
				</div><div class="para">
					There are two primary programs used to specify password aging under Fedora: the <code class="command">chage</code> command or the graphical <span class="application"><strong>User Manager</strong></span> (<code class="command">system-config-users</code>) application.
				</div><div class="para">
					The <code class="option">-M</code> option of the <code class="command">chage</code> command specifies the maximum number of days the password is valid. For example, to set a user's password to expire in 90 days, use the following command:
				</div><pre class="screen"><code class="command">chage -M 90 <em class="replaceable"><code><username></code></em></code>
</pre><div class="para">
					In the above command, replace <em class="replaceable"><code><username></code></em> with the name of the user. To disable password expiration, it is traditional to use a value of <code class="command">99999</code> after the <code class="option">-M</code> option (this equates to a little over 273 years).
				</div><div class="para">
					You can also use the <code class="command">chage</code> command in interactive mode to modify multiple password aging and account details. Use the following command to enter interactive mode:
				</div><pre class="screen"><code class="command">chage <em class="replaceable"><code><username></code></em></code>
</pre><div class="para">
					The following is a sample interactive session using this command:
				</div><pre class="screen">[root at interch-dev1 ~]# chage davido 
Changing the aging information for davido 
Enter the new value, or press ENTER for the default 
Minimum Password Age [0]: 10
Maximum Password Age [99999]: 90 
Last Password Change (YYYY-MM-DD) [2006-08-18]: 
Password Expiration Warning [7]: 
Password Inactive [-1]: 
Account Expiration Date (YYYY-MM-DD) [1969-12-31]: 
[root at interch-dev1 ~]#
</pre><div class="para">
					Refer to the man page for chage for more information on the available options.
				</div><div class="para">
					You can also use the graphical <span class="application"><strong>User Manager</strong></span> application to create password aging policies, as follows. Note: you need Administrator privileges to perform this procedure.
				</div><div class="procedure"><ol class="1"><li><div class="para">
							Click the <span class="guimenu"><strong>System</strong></span> menu on the Panel, point to <span class="guisubmenu"><strong>Administration</strong></span> and then click <span class="guimenuitem"><strong>Users and Groups</strong></span> to display the User Manager. Alternatively, type the command <code class="command">system-config-users</code> at a shell prompt.
						</div></li><li><div class="para">
							Click the <span class="guilabel"><strong>Users</strong></span> tab, and select the required user in the list of users.
						</div></li><li><div class="para">
							Click <span class="guibutton"><strong>Properties</strong></span> on the toolbar to display the User Properties dialog box (or choose <span class="guimenuitem"><strong>Properties</strong></span> on the <span class="guimenu"><strong>File</strong></span> menu).
						</div></li><li><div class="para">
							Click the <span class="guilabel"><strong>Password Info</strong></span> tab, and select the check box for <span class="guilabel"><strong>Enable password expiration</strong></span>.
						</div></li><li><div class="para">
							Enter the required value in the <span class="guilabel"><strong>Days before change required</strong></span> field, and click <span class="guibutton"><strong>OK</strong></span>.
						</div></li></ol></div><div class="figure" id="figu-Security_Guide-Password_Aging-Specifying_password_aging_options"><div class="figure-contents"><div class="mediaobject"><img src="images/fed-user_pass_info.png" alt="Specifying password aging options" /><div class="longdesc"><div class="para">
								<span class="guilabel"><strong>Password Info</strong></span> pane illustration.
							</div></div></div></div><h6>Figura 2.1. Specifying password aging options</h6></div><br class="figure-break" /></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-Workstation_Security-Administrative_Controls">2.1.4. Administrative Controls</h3></div></div></div><div class="para">
			When administering a home machine, the user must perform some tasks as the root user or by acquiring effective root privileges via a <em class="firstterm">setuid</em> program, such as <code class="command">sudo</code> or <code class="command">su</code>. A setuid program is one that operates with the user ID (<span class="emphasis"><em>UID</em></span>) of the program's owner rather than the user operating the program. Such programs are denoted by an <code class="computeroutput">s</code> in the owner section of a long format listing, as in the following example:
		</div><pre class="screen"><code class="computeroutput">-rwsr-xr-x 1 root root 47324 May 1 08:09 /bin/su</code>
</pre><div class="note"><h2>Note</h2><div class="para">
				The <code class="computeroutput">s</code> may be upper case or lower case. If it appears as upper case, it means that the underlying permission bit has not been set.
			</div></div><div class="para">
			For the system administrators of an organization, however, choices must be made as to how much administrative access users within the organization should have to their machine. Through a PAM module called <code class="filename">pam_console.so</code>, some activities normally reserved only for the root user, such as rebooting and mounting removable media are allowed for the first user that logs in at the physical console (refer to <a class="xref" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM.html" title="2.4. Pluggable Authentication Modules (PAM)">SecciÃ³nÂ 2.4, â€œPluggable Authentication Modules (PAM)â€</a> for more information about the <code class="filename">pam_console.so</code> module.) However, other important system administration tasks, such as altering network settings, configuring a new mouse, or mounting network devices, are not possible without administrative privileges. As a result, system administrators must decide how much access the users
  on their network should receive.
		</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Administrative_Controls-Allowing_Root_Access">2.1.4.1. Permitiendo Accesos Root</h4></div></div></div><div class="para">
				If the users within an organization are trusted and computer-literate, then allowing them root access may not be an issue. Allowing root access by users means that minor activities, like adding devices or configuring network interfaces, can be handled by the individual users, leaving system administrators free to deal with network security and other important issues.
			</div><div class="para">
				On the other hand, giving root access to individual users can lead to the following issues:
			</div><div class="itemizedlist"><ul><li><div class="para">
						<span class="emphasis"><em>Machine Misconfiguration</em></span> â€” Users with root access can misconfigure their machines and require assistance to resolve issues. Even worse, they might open up security holes without knowing it.
					</div></li><li><div class="para">
						<span class="emphasis"><em>Running Insecure Services</em></span> â€” Users with root access might run insecure servers on their machine, such as FTP or Telnet, potentially putting usernames and passwords at risk. These services transmit this information over the network in plain text.
					</div></li><li><div class="para">
						<span class="emphasis"><em>Running Email Attachments As Root</em></span> â€” Although rare, email viruses that affect Linux do exist. The only time they are a threat, however, is when they are run by the root user.
					</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-Administrative_Controls-Disallowing_Root_Access">2.1.4.2. Disallowing Root Access</h4></div></div></div><div class="para">
				If an administrator is uncomfortable allowing users to log in as root for these or other reasons, the root password should be kept secret, and access to runlevel one or single user mode should be disallowed through boot loader password protection (refer to <a class="xref" href="chap-Security_Guide-Securing_Your_Network.html#sect-Security_Guide-BIOS_and_Boot_Loader_Security-Boot_Loader_Passwords" title="2.1.2.2. Boot Loader Passwords">SecciÃ³nÂ 2.1.2.2, â€œBoot Loader Passwordsâ€</a> for more information on this topic.)
			</div><div class="para">
				<a class="xref" href="chap-Security_Guide-Securing_Your_Network.html#tabl-Security_Guide-Disallowing_Root_Access-Methods_of_Disabling_the_Root_Account" title="Tabla 2.1. Methods of Disabling the Root Account">TablaÂ 2.1, â€œMethods of Disabling the Root Accountâ€</a> describes ways that an administrator can further ensure that root logins are disallowed:
			</div><div class="table" id="tabl-Security_Guide-Disallowing_Root_Access-Methods_of_Disabling_the_Root_Account"><div class="table-contents"><table summary="Methods of Disabling the Root Account" border="1"><colgroup><col /><col /><col /><col /></colgroup><thead><tr><th>
								Method
							</th><th>
								Description
							</th><th>
								Efectos
							</th><th>
								Does Not Affect
							</th></tr></thead><tbody><tr><td>
								Changing the root shell.
							</td><td>
								Edit the <code class="filename">/etc/passwd</code> file and change the shell from <code class="command">/bin/bash</code> to <code class="command">/sbin/nologin</code>.
							</td><td>
								<table class="simplelist" border="0" summary="Simple list"><tr><td>Prevents access to the root shell and logs any such attempts. </td></tr><tr><td>The following programs are prevented from accessing the root account: </td></tr><tr><td>Â· <code class="command">login</code></td></tr><tr><td>Â· <code class="command">gdm</code></td></tr><tr><td>Â· <code class="command">kdm</code></td></tr><tr><td>Â· <code class="command">xdm</code></td></tr><tr><td>Â· <code class="command">su</code></td></tr><tr><td>Â· <code class="command">ssh</code></td></tr><tr><td>Â· <code class="command">scp</code></td></tr><tr><td>Â· <code class="command">sftp</code></td></tr></table>
							</td><td>
								<table class="simplelist" border="0" summary="Simple list"><tr><td>Programs that do not require a shell, such as FTP clients, mail clients, and many setuid programs. </td></tr><tr><td>The following programs are <span class="emphasis"><em>not</em></span> prevented from accessing the root account: </td></tr><tr><td>Â· <code class="command">sudo</code></td></tr><tr><td>Â· FTP clients </td></tr><tr><td>Â· Email clients </td></tr></table>
							</td></tr><tr><td>
								Disabling root access via any console device (tty).
							</td><td>
								An empty <code class="filename">/etc/securetty</code> file prevents root login on any devices attached to the computer.
							</td><td>
								<table class="simplelist" border="0" summary="Simple list"><tr><td>Prevents access to the root account via the console or the network. The following programs are prevented from accessing the root account: </td></tr><tr><td>Â· <code class="command">login</code></td></tr><tr><td>Â· <code class="command">gdm</code></td></tr><tr><td>Â· <code class="command">kdm</code></td></tr><tr><td>Â· <code class="command">xdm</code></td></tr><tr><td>Â· Other network services that open a tty </td></tr></table>
							</td><td>
								<table class="simplelist" border="0" summary="Simple list"><tr><td>Programs that do not log in as root, but perform administrative tasks through setuid or other mechanisms. </td></tr><tr><td>The following programs are <span class="emphasis"><em>not</em></span> prevented from accessing the root account: </td></tr><tr><td>Â· <code class="command">su</code></td></tr><tr><td>Â· <code class="command">sudo</code></td></tr><tr><td>Â· <code class="command">ssh</code></td></tr><tr><td>Â· <code class="command">scp</code></td></tr><tr><td>Â· <code class="command">sftp</code></td></tr></table>
							</td></tr><tr><td>
								Disabling root SSH logins.
							</td><td>
								Edit the <code class="filename">/etc/ssh/sshd_config</code> file and set the <code class="command">PermitRootLogin</code> parameter to <code class="command">no</code>.
							</td><td>
								<table class="simplelist" border="0" summary="Simple list"><tr><td>Prevents root access via the OpenSSH suite of tools. The following programs are prevented from accessing the root account: </td></tr><tr><td>Â· <code class="command">ssh</code></td></tr><tr><td>Â· <code class="command">scp</code></td></tr><tr><td>Â· <code class="command">sftp</code></td></tr></table>
							</td><td>
								<table class="simplelist" border="0" summary="Simple list"><tr><td>This only prevents root access to the OpenSSH suite of tools. </td></tr></table>
							</td></tr><tr><td>
								Use PAM to limit root access to services.
							</td><td>
								Edit the file for the target service in the <code class="filename">/etc/pam.d/</code> directory. Make sure the <code class="filename">pam_listfile.so</code> is required for authentication.<sup>[<a id="id2884484" href="#ftn.id2884484" class="footnote">a</a>]</sup>
							</td><td>
								<table class="simplelist" border="0" summary="Simple list"><tr><td>Prevents root access to network services that are PAM aware. </td></tr><tr><td>The following services are prevented from accessing the root account: </td></tr><tr><td>Â· FTP clients </td></tr><tr><td>Â· Email clients </td></tr><tr><td>Â· <code class="command">login</code></td></tr><tr><td>Â· <code class="command">gdm</code></td></tr><tr><td>Â· <code class="command">kdm</code></td></tr><tr><td>Â· <code class="command">xdm</code></td></tr><tr><td>Â· <code class="command">ssh</code></td></tr><tr><td>Â· <code class="command">scp</code></td></tr><tr><td>Â· <code class="command">sftp</code></td></tr><tr><td>Â· Any PAM aware services </td></tr></table>
							</td><td>
								<table class="simplelist" border="0" summary="Simple list"><tr><td>Programs and services that are not PAM aware. </td></tr></table>
							</td></tr></tbody><tbody class="footnotes"><tr><td colspan="4"><div class="footnote"><p><sup>[<a id="ftn.id2884484" href="#id2884484" class="para">a</a>] </sup>
									Refer to <a class="xref" href="chap-Security_Guide-Securing_Your_Network.html#sect-Security_Guide-Disallowing_Root_Access-Disabling_Root_Using_PAM" title="2.1.4.2.4. Desabilitando Root Usando PAM">SecciÃ³nÂ 2.1.4.2.4, â€œDesabilitando Root Usando PAMâ€</a> for details.
								</p></div></td></tr></tbody></table></div><h6>Tabla 2.1. Methods of Disabling the Root Account</h6></div><br class="table-break" /><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h5 class="title" id="sect-Security_Guide-Disallowing_Root_Access-Disabling_the_Root_Shell">2.1.4.2.1. Disabling the Root Shell</h5></div></div></div><div class="para">
					To prevent users from logging in directly as root, the system administrator can set the root account's shell to <code class="command">/sbin/nologin</code> in the <code class="filename">/etc/passwd</code> file. This prevents access to the root account through commands that require a shell, such as the <code class="command">su</code> and the <code class="command">ssh</code> commands.
				</div><div class="important"><h2>Important</h2><div class="para">
						Programs that do not require access to the shell, such as email clients or the <code class="command">sudo</code> command, can still access the root account.
					</div></div></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h5 class="title" id="sect-Security_Guide-Disallowing_Root_Access-Disabling_Root_Logins">2.1.4.2.2. Disabling Root Logins</h5></div></div></div><div class="para">
					To further limit access to the root account, administrators can disable root logins at the console by editing the <code class="filename">/etc/securetty</code> file. This file lists all devices the root user is allowed to log into. If the file does not exist at all, the root user can log in through any communication device on the system, whether via the console or a raw network interface. This is dangerous, because a user can log in to his machine as root via Telnet, which transmits the password in plain text over the network. By default, Fedora's <code class="filename">/etc/securetty</code> file only allows the root user to log in at the console physically attached to the machine. To prevent root from logging in, remove the contents of this file by typing the following command:
				</div><pre class="screen"><code class="command">echo > /etc/securetty</code>
</pre><div class="warning"><h2>Warning</h2><div class="para">
						A blank <code class="filename">/etc/securetty</code> file does <span class="emphasis"><em>not</em></span> prevent the root user from logging in remotely using the OpenSSH suite of tools because the console is not opened until after authentication.
					</div></div></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h5 class="title" id="sect-Security_Guide-Disallowing_Root_Access-Disabling_Root_SSH_Logins">2.1.4.2.3. Disabling Root SSH Logins</h5></div></div></div><div class="para">
					Root logins via the SSH protocol are disabled by default in Fedora; however, if this option has been enabled, it can be disabled again by editing the SSH daemon's configuration file (<code class="filename">/etc/ssh/sshd_config</code>). Change the line that reads:
				</div><pre class="screen"><code class="computeroutput">PermitRootLogin yes</code>
</pre><div class="para">
					to read as follows:
				</div><pre class="screen"><code class="computeroutput">PermitRootLogin no</code>
</pre><div class="para">
					For these changes to take effect, the SSH daemon must be restarted. This can be done via the following command:
				</div><pre class="screen"><code class="computeroutput">kill -HUP `cat /var/run/sshd.pid`</code>
</pre></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h5 class="title" id="sect-Security_Guide-Disallowing_Root_Access-Disabling_Root_Using_PAM">2.1.4.2.4. Desabilitando Root Usando PAM</h5></div></div></div><div class="para">
					PAM, through the <code class="filename">/lib/security/pam_listfile.so</code> module, allows great flexibility in denying specific accounts. The administrator can use this module to reference a list of users who are not allowed to log in. Below is an example of how the module is used for the <code class="command">vsftpd</code> FTP server in the <code class="filename">/etc/pam.d/vsftpd</code> PAM configuration file (the <code class="computeroutput">\</code> character at the end of the first line in the following example is <span class="emphasis"><em>not</em></span> necessary if the directive is on one line):
				</div><pre class="screen">auth required /lib/security/pam_listfile.so item=user \ 
sense=deny file=/etc/vsftpd.ftpusers onerr=succeed
</pre><div class="para">
					This instructs PAM to consult the <code class="filename">/etc/vsftpd.ftpusers</code> file and deny access to the service for any listed user. The administrator can change the name of this file, and can keep separate lists for each service or use one central list to deny access to multiple services.
				</div><div class="para">
					If the administrator wants to deny access to multiple services, a similar line can be added to the PAM configuration files, such as <code class="filename">/etc/pam.d/pop</code> and <code class="filename">/etc/pam.d/imap</code> for mail clients, or <code class="filename">/etc/pam.d/ssh</code> for SSH clients.
				</div><div class="para">
					For more information about PAM, refer to <a class="xref" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM.html" title="2.4. Pluggable Authentication Modules (PAM)">SecciÃ³nÂ 2.4, â€œPluggable Authentication Modules (PAM)â€</a>.
				</div></div></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Administrative_Controls-Limiting_Root_Access">2.1.4.3. Limitando Acceso como Root</h4></div></div></div><div class="para">
				Rather than completely denying access to the root user, the administrator may want to allow access only via setuid programs, such as <code class="command">su</code> or <code class="command">sudo</code>.
			</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h5 class="title" id="sect-Security_Guide-Limiting_Root_Access-The_su_Command">2.1.4.3.1. El Comando <code class="command">su</code></h5></div></div></div><div class="para">
					When a user executes the <code class="command">su</code> command, they are prompted for the root password and, after authentication, is given a root shell prompt.
				</div><div class="para">
					Once logged in via the <code class="command">su</code> command, the user <span class="emphasis"><em>is</em></span> the root user and has absolute administrative access to the system<sup>[<a id="id2936846" href="#ftn.id2936846" class="footnote">13</a>]</sup>. In addition, once a user has become root, it is possible for them to use the <code class="command">su</code> command to change to any other user on the system without being prompted for a password.
				</div><div class="para">
					Because this program is so powerful, administrators within an organization may wish to limit who has access to the command.
				</div><div class="para">
					One of the simplest ways to do this is to add users to the special administrative group called <em class="firstterm">wheel</em>. To do this, type the following command as root:
				</div><pre class="screen"><code class="command">usermod -G wheel <em class="replaceable"><code><nombreusuario></code></em></code>
</pre><div class="para">
					In the previous command, replace <em class="replaceable"><code><username></code></em> with the username you want to add to the <code class="command">wheel</code> group.
				</div><div class="para">
					You can also use the <span class="application"><strong>User Manager</strong></span> to modify group memberships, as follows. Note: you need Administrator privileges to perform this procedure.
				</div><div class="procedure"><ol class="1"><li><div class="para">
							Click the <span class="guimenu"><strong>System</strong></span> menu on the Panel, point to <span class="guisubmenu"><strong>Administration</strong></span> and then click <span class="guimenuitem"><strong>Users and Groups</strong></span> to display the User Manager. Alternatively, type the command <code class="command">system-config-users</code> at a shell prompt.
						</div></li><li><div class="para">
							Click the <span class="guilabel"><strong>Users</strong></span> tab, and select the required user in the list of users.
						</div></li><li><div class="para">
							Click <span class="guibutton"><strong>Properties</strong></span> on the toolbar to display the User Properties dialog box (or choose <span class="guimenuitem"><strong>Properties</strong></span> on the <span class="guimenu"><strong>File</strong></span> menu).
						</div></li><li><div class="para">
							Click the <span class="guilabel"><strong>Groups</strong></span> tab, select the check box for the wheel group, and then click <span class="guibutton"><strong>OK</strong></span>. Refer to <a class="xref" href="chap-Security_Guide-Securing_Your_Network.html#figu-Security_Guide-The_su_Command-Adding_users_to_the_wheel_group." title="Figura 2.2. AÃ±adiendo usuario al grupo "wheel"">FiguraÂ 2.2, â€œAÃ±adiendo usuario al grupo "wheel"â€</a>.
						</div></li><li><div class="para">
							Open the PAM configuration file for <code class="command">su</code> (<code class="filename">/etc/pam.d/su</code>) in a text editor and remove the comment <span class="keycap"><strong>#</strong></span> from the following line:
						</div><pre class="screen">auth  required /lib/security/$ISA/pam_wheel.so use_uid
</pre><div class="para">
							Este cambio significa que solo miembros del grupo administrativo <code class="computeroutput">wheel</code> pueden usar este programa.
						</div></li></ol></div><div class="figure" id="figu-Security_Guide-The_su_Command-Adding_users_to_the_wheel_group."><div class="figure-contents"><div class="mediaobject"><img src="images/fed-user_pass_groups.png" alt="AÃ±adiendo usuario al grupo "wheel"" /><div class="longdesc"><div class="para">
								IlustraciÃ³n del panel <span class="guilabel"><strong>Grupos</strong></span>
							</div></div></div></div><h6>Figura 2.2. AÃ±adiendo usuario al grupo "wheel"</h6></div><br class="figure-break" /><div class="note"><h2>Note</h2><div class="para">
						El usuario root es por defecto miembro del grupo<code class="computeroutput">wheel</code>.
					</div></div></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h5 class="title" id="sect-Security_Guide-Limiting_Root_Access-The_sudo_Command">2.1.4.3.2. El comando <code class="command">sudo</code></h5></div></div></div><div class="para">
					The <code class="command">sudo</code> command offers another approach to giving users administrative access. When trusted users precede an administrative command with <code class="command">sudo</code>, they are prompted for <span class="emphasis"><em>their own</em></span> password. Then, when they have been authenticated and assuming that the command is permitted, the administrative command is executed as if they were the root user.
				</div><div class="para">
					Los formatos basicos del comando <code class="command">sudo</code> son los siguientes:
				</div><pre class="screen"><code class="command">sudo <em class="replaceable"><code><comando></code></em></code>
</pre><div class="para">
					In the above example, <em class="replaceable"><code><command></code></em> would be replaced by a command normally reserved for the root user, such as <code class="command">mount</code>.
				</div><div class="important"><h2>Important</h2><div class="para">
						Users of the <code class="command">sudo</code> command should take extra care to log out before walking away from their machines since sudoers can use the command again without being asked for a password within a five minute period. This setting can be altered via the configuration file, <code class="filename">/etc/sudoers</code>.
					</div></div><div class="para">
					The <code class="command">sudo</code> command allows for a high degree of flexibility. For instance, only users listed in the <code class="filename">/etc/sudoers</code> configuration file are allowed to use the <code class="command">sudo</code> command and the command is executed in <span class="emphasis"><em>the user's</em></span> shell, not a root shell. This means the root shell can be completely disabled, as shown in <a class="xref" href="chap-Security_Guide-Securing_Your_Network.html#sect-Security_Guide-Disallowing_Root_Access-Disabling_the_Root_Shell" title="2.1.4.2.1. Disabling the Root Shell">SecciÃ³nÂ 2.1.4.2.1, â€œDisabling the Root Shellâ€</a>.
				</div><div class="para">
					The <code class="command">sudo</code> command also provides a comprehensive audit trail. Each successful authentication is logged to the file <code class="filename">/var/log/messages</code> and the command issued along with the issuer's user name is logged to the file <code class="filename">/var/log/secure</code>.
				</div><div class="para">
					Another advantage of the <code class="command">sudo</code> command is that an administrator can allow different users access to specific commands based on their needs.
				</div><div class="para">
					Administrators wanting to edit the <code class="command">sudo</code> configuration file, <code class="filename">/etc/sudoers</code>, should use the <code class="command">visudo</code> command.
				</div><div class="para">
					To give someone full administrative privileges, type <code class="command">visudo</code> and add a line similar to the following in the user privilege specification section:
				</div><pre class="screen"><code class="command">juan ALL=(ALL) ALL</code>
</pre><div class="para">
					This example states that the user, <code class="computeroutput">juan</code>, can use <code class="command">sudo</code> from any host and execute any command.
				</div><div class="para">
					The example below illustrates the granularity possible when configuring <code class="command">sudo</code>:
				</div><pre class="screen"><code class="command">%users localhost=/sbin/shutdown -h now</code>
</pre><div class="para">
					This example states that any user can issue the command <code class="command">/sbin/shutdown -h now</code> as long as it is issued from the console.
				</div><div class="para">
					The man page for <code class="filename">sudoers</code> has a detailed listing of options for this file.
				</div></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-Workstation_Security-Available_Network_Services">2.1.5. Servicios de Red Disponibles</h3></div></div></div><div class="para">
			While user access to administrative controls is an important issue for system administrators within an organization, monitoring which network services are active is of paramount importance to anyone who administers and operates a Linux system.
		</div><div class="para">
			Many services under Fedora behave as network servers. If a network service is running on a machine, then a server application (called a <em class="firstterm">daemon</em>), is listening for connections on one or more network ports. Each of these servers should be treated as a potential avenue of attack.
		</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Available_Network_Services-Risks_To_Services">2.1.5.1. Riesgos a Servicios</h4></div></div></div><div class="para">
				Servicios de red puede plantear numerosos riesgos para sistemas Linux. Abajo hay una lista de algunas de las cuestiones principales:
			</div><div class="itemizedlist"><ul><li><div class="para">
						<span class="emphasis"><em>Denial of Service Attacks (DoS)</em></span> â€” By flooding a service with requests, a denial of service attack can render a system unusable as it tries to log and answer each request.
					</div></li><li><div class="para">
						<span class="emphasis"><em>Script Vulnerability Attacks</em></span> â€” If a server is using scripts to execute server-side actions, as Web servers commonly do, a cracker can attack improperly written scripts. These script vulnerability attacks can lead to a buffer overflow condition or allow the attacker to alter files on the system.
					</div></li><li><div class="para">
						<span class="emphasis"><em>Buffer Overflow Attacks</em></span> â€” Services that connect to ports numbered 0 through 1023 must run as an administrative user. If the application has an exploitable buffer overflow, an attacker could gain access to the system as the user running the daemon. Because exploitable buffer overflows exist, crackers use automated tools to identify systems with vulnerabilities, and once they have gained access, they use automated rootkits to maintain their access to the system.
					</div></li></ul></div><div class="note"><h2>Note</h2><div class="para">
					The threat of buffer overflow vulnerabilities is mitigated in Fedora by <em class="firstterm">ExecShield</em>, an executable memory segmentation and protection technology supported by x86-compatible uni- and multi-processor kernels. ExecShield reduces the risk of buffer overflow by separating virtual memory into executable and non-executable segments. Any program code that tries to execute outside of the executable segment (such as malicious code injected from a buffer overflow exploit) triggers a segmentation fault and terminates.
				</div><div class="para">
					Execshield also includes support for <em class="firstterm">No eXecute</em> (<acronym class="acronym">NX</acronym>) technology on AMD64 platforms and <em class="firstterm">eXecute Disable</em> (<acronym class="acronym">XD</acronym>) technology on Itanium and <span class="trademark">Intel</span>Â® 64 systems. These technologies work in conjunction with ExecShield to prevent malicious code from running in the executable portion of virtual memory with a granularity of 4KB of executable code, lowering the risk of attack from stealthy buffer overflow exploits.
				</div></div><div class="important"><h2>Important</h2><div class="para">
					Para limitar la exposiciÃ±on a ataques en la red, todos los servicios que no son utilizados deben ser apagados.
				</div></div></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Available_Network_Services-Identifying_and_Configuring_Services">2.1.5.2. Identificando y Configurando Servicios</h4></div></div></div><div class="para">
				Para mejorar la seguridad, muchos de los servicios de red instalados con Fedora estan apagados por defecto. Hay, de todas formas, algunas notables excepciones:
			</div><div class="itemizedlist"><ul><li><div class="para">
						<code class="command">cupsd</code> â€” El servidor de impresiÃ³n por defecto para Fedora.
					</div></li><li><div class="para">
						<code class="command">lpd</code> â€” Un servidor de impresiÃ³n alternativo.
					</div></li><li><div class="para">
						<code class="command">xinetd</code> â€” A super server that controls connections to a range of subordinate servers, such as <code class="command">gssftp</code> and <code class="command">telnet</code>.
					</div></li><li><div class="para">
						<code class="command">sendmail</code> â€” The Sendmail <em class="firstterm">Mail Transport Agent</em> (<abbr class="abbrev">MTA</abbr>) is enabled by default, but only listens for connections from the <span class="interface">localhost</span>.
					</div></li><li><div class="para">
						<code class="command">sshd</code> â€” El servidor OpenSSH, es un reemplazo seguro para Telnet.
					</div></li></ul></div><div class="para">
				When determining whether to leave these services running, it is best to use common sense and err on the side of caution. For example, if a printer is not available, do not leave <code class="command">cupsd</code> running. The same is true for <code class="command">portmap</code>. If you do not mount NFSv3 volumes or use NIS (the <code class="command">ypbind</code> service), then <code class="command">portmap</code> should be disabled.
			</div><div class="figure" id="figu-Security_Guide-Identifying_and_Configuring_Services-Services_Configuration_Tool"><div class="figure-contents"><div class="mediaobject"><img src="images/fed-service_config.png" alt="Herramienta de ConfiguraciÃ³n de Servicios" /><div class="longdesc"><div class="para">
							IlustraciÃ³n <span class="application"><strong>Herramienta de ConfiguraciÃ³n de Servicios</strong></span>
						</div></div></div></div><h6>Figura 2.3. <span class="application">Herramienta de ConfiguraciÃ³n de Servicios</span></h6></div><br class="figure-break" /><div class="para">
				If unsure of the purpose for a particular service, the <span class="application"><strong>Services Configuration Tool</strong></span> has a description field, illustrated in <a class="xref" href="chap-Security_Guide-Securing_Your_Network.html#figu-Security_Guide-Identifying_and_Configuring_Services-Services_Configuration_Tool" title="Figura 2.3. Herramienta de ConfiguraciÃ³n de Servicios">FiguraÂ 2.3, â€œHerramienta de ConfiguraciÃ³n de Serviciosâ€</a>, that provides additional information.
			</div><div class="para">
				Checking which network services are available to start at boot time is only part of the story. You should also check which ports are open and listening. Refer to <a class="xref" href="sect-Security_Guide-Server_Security-Verifying_Which_Ports_Are_Listening.html" title="2.2.8. Verifying Which Ports Are Listening">SecciÃ³nÂ 2.2.8, â€œVerifying Which Ports Are Listeningâ€</a> for more information.
			</div></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Available_Network_Services-Insecure_Services">2.1.5.3. Servicios inseguros</h4></div></div></div><div class="para">
				Potentially, any network service is insecure. This is why turning off unused services is so important. Exploits for services are routinely revealed and patched, making it very important to regularly update packages associated with any network service. Refer to <a class="xref" href="sect-Security_Guide-Security_Updates.html" title="1.5. Actualizaciones de Seguridad">SecciÃ³nÂ 1.5, â€œActualizaciones de Seguridadâ€</a> for more information.
			</div><div class="para">
				Algunos protocolos de red son inherentemente mÃ¡s inseguros que otros. Estos incluyen los servicios que:
			</div><div class="itemizedlist"><ul><li><div class="para">
						<span class="emphasis"><em>Transmit Usernames and Passwords Over a Network Unencrypted</em></span> â€” Many older protocols, such as Telnet and FTP, do not encrypt the authentication session and should be avoided whenever possible.
					</div></li><li><div class="para">
						<span class="emphasis"><em>Transmit Sensitive Data Over a Network Unencrypted</em></span> â€” Many protocols transmit data over the network unencrypted. These protocols include Telnet, FTP, HTTP, and SMTP. Many network file systems, such as NFS and SMB, also transmit information over the network unencrypted. It is the user's responsibility when using these protocols to limit what type of data is transmitted.
					</div><div class="para">
						Servicios de volcado de memoria remoto, como <code class="command">netdump</code>, transmiten el contenido de la memoria sobre una red sin encriptar . Los volcados de memoria pueden contener contraseÃ±as o, peor aÃºn, entradas a base de datos o informaciÃ³n sencible.
					</div><div class="para">
						Otros servicios como <code class="command">finger</code> y <code class="command">rwhod</code> revelan informaciÃ³n sobre usuarios del sistema.
					</div></li></ul></div><div class="para">
				Ejemplos de servicios inherentemente inseguros incluyen <code class="command">rlogin</code>, <code class="command">rsh</code>, <code class="command">telnet</code>, y <code class="command">vsftpd</code>.
			</div><div class="para">
				All remote login and shell programs (<code class="command">rlogin</code>, <code class="command">rsh</code>, and <code class="command">telnet</code>) should be avoided in favor of SSH. Refer to <a class="xref" href="chap-Security_Guide-Securing_Your_Network.html#sect-Security_Guide-Workstation_Security-Security_Enhanced_Communication_Tools" title="2.1.7. Security Enhanced Communication Tools">SecciÃ³nÂ 2.1.7, â€œSecurity Enhanced Communication Toolsâ€</a> for more information about <code class="command">sshd</code>.
			</div><div class="para">
				FTP is not as inherently dangerous to the security of the system as remote shells, but FTP servers must be carefully configured and monitored to avoid problems. Refer to <a class="xref" href="sect-Security_Guide-Server_Security-Securing_FTP.html" title="2.2.6. Securing FTP">SecciÃ³nÂ 2.2.6, â€œSecuring FTPâ€</a> for more information about securing FTP servers.
			</div><div class="para">
				Services that should be carefully implemented and behind a firewall include:
			</div><div class="itemizedlist"><ul><li><div class="para">
						<code class="command">finger</code>
					</div></li><li><div class="para">
						<code class="command">authd</code> (antes llamado <code class="command">identd</code> en versiones anteriores de Fedora.)
					</div></li><li><div class="para">
						<code class="command">netdump</code>
					</div></li><li><div class="para">
						<code class="command">netdump-server</code>
					</div></li><li><div class="para">
						<code class="command">nfs</code>
					</div></li><li><div class="para">
						<code class="command">rwhod</code>
					</div></li><li><div class="para">
						<code class="command">sendmail</code>
					</div></li><li><div class="para">
						<code class="command">smb</code> (Samba)
					</div></li><li><div class="para">
						<code class="command">yppasswdd</code>
					</div></li><li><div class="para">
						<code class="command">ypserv</code>
					</div></li><li><div class="para">
						<code class="command">ypxfrd</code>
					</div></li></ul></div><div class="para">
				More information on securing network services is available in <a class="xref" href="sect-Security_Guide-Server_Security.html" title="2.2. Server Security">SecciÃ³nÂ 2.2, â€œServer Securityâ€</a>.
			</div><div class="para">
				La siguiente secciÃ³n discute las herramientas disponibles para crear un cortafuegos sencillo.
			</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-Workstation_Security-Personal_Firewalls">2.1.6. Cortafuegos Personal:</h3></div></div></div><div class="para">
			After the <span class="emphasis"><em>necessary</em></span> network services are configured, it is important to implement a firewall.
		</div><div class="important"><h2>Important</h2><div class="para">
				You should configure the necessary services and implement a firewall <span class="emphasis"><em>before</em></span> connecting to the Internet or any other network that you do not trust.
			</div></div><div class="para">
			Firewalls prevent network packets from accessing the system's network interface. If a request is made to a port that is blocked by a firewall, the request is ignored. If a service is listening on one of these blocked ports, it does not receive the packets and is effectively disabled. For this reason, care should be taken when configuring a firewall to block access to ports not in use, while not blocking access to ports used by configured services.
		</div><div class="para">
			For most users, the best tool for configuring a simple firewall is the graphical firewall configuration tool which ships with Fedora: the <span class="application"><strong>Firewall Configuration Tool</strong></span> (<code class="command">system-config-firewall</code>). This tool creates broad <code class="command">iptables</code> rules for a general-purpose firewall using a control panel interface.
		</div><div class="para">
			Refer to <a class="xref" href="sect-Security_Guide-Firewalls-Basic_Firewall_Configuration.html" title="2.8.2. ConfiguraciÃ³n BÃ¡sica del Cortafuego">SecciÃ³nÂ 2.8.2, â€œConfiguraciÃ³n BÃ¡sica del Cortafuegoâ€</a> for more information about using this application and its available options.
		</div><div class="para">
			For advanced users and server administrators, manually configuring a firewall with <code class="command">iptables</code> is probably a better option. Refer to <a class="xref" href="sect-Security_Guide-Firewalls.html" title="2.8. Firewalls">SecciÃ³nÂ 2.8, â€œFirewallsâ€</a> for more information. Refer to <a class="xref" href="sect-Security_Guide-IPTables.html" title="2.9. IPTables">SecciÃ³nÂ 2.9, â€œIPTablesâ€</a> for a comprehensive guide to the <code class="command">iptables</code> command.
		</div></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Workstation_Security-Security_Enhanced_Communication_Tools">2.1.7. Security Enhanced Communication Tools</h3></div></div></div><div class="para">
			As the size and popularity of the Internet has grown, so has the threat of communication interception. Over the years, tools have been developed to encrypt communications as they are transferred over the network.
		</div><div class="para">
			Fedora ships with two basic tools that use high-level, public-key-cryptography-based encryption algorithms to protect information as it travels over the network.
		</div><div class="itemizedlist"><ul><li><div class="para">
					<span class="emphasis"><em>OpenSSH</em></span> â€” A free implementation of the SSH protocol for encrypting network communication.
				</div></li><li><div class="para">
					<span class="emphasis"><em>Gnu Privacy Guard (GPG)</em></span> â€” A free implementation of the PGP (Pretty Good Privacy) encryption application for encrypting data.
				</div></li></ul></div><div class="para">
			OpenSSH is a safer way to access a remote machine and replaces older, unencrypted services like <code class="command">telnet</code> and <code class="command">rsh</code>. OpenSSH includes a network service called <code class="command">sshd</code> and three command line client applications:
		</div><div class="itemizedlist"><ul><li><div class="para">
					<code class="command">ssh</code> â€” A secure remote console access client.
				</div></li><li><div class="para">
					<code class="command">scp</code> â€” A secure remote copy command.
				</div></li><li><div class="para">
					<code class="command">sftp</code> â€” A secure pseudo-ftp client that allows interactive file transfer sessions.
				</div></li></ul></div><div class="para">
			Refer to <a class="xref" href="Security_Guide-Encryption-Data_in_Motion-Secure_Shell.html" title="3.6. Shell Seguro">SecciÃ³nÂ 3.6, â€œShell Seguroâ€</a> for more information regarding OpenSSH.
		</div><div class="important"><h2>Important</h2><div class="para">
				Although the <code class="command">sshd</code> service is inherently secure, the service <span class="emphasis"><em>must</em></span> be kept up-to-date to prevent security threats. Refer to <a class="xref" href="sect-Security_Guide-Security_Updates.html" title="1.5. Actualizaciones de Seguridad">SecciÃ³nÂ 1.5, â€œActualizaciones de Seguridadâ€</a> for more information.
			</div></div><div class="para">
			GPG is one way to ensure private email communication. It can be used both to email sensitive data over public networks and to protect sensitive data on hard drives.
		</div></div></div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id2989569" href="#id2989569" class="para">11</a>] </sup>
					Since system BIOSes differ between manufacturers, some may not support password protection of either type, while others may support one type but not the other.
				</p></div><div class="footnote"><p><sup>[<a id="ftn.id2989320" href="#id2989320" class="para">12</a>] </sup>
						GRUB also accepts unencrypted passwords, but it is recommended that an MD5 hash be used for added security.
					</p></div><div class="footnote"><p><sup>[<a id="ftn.id2936846" href="#id2936846" class="para">13</a>] </sup>
						This access is still subject to the restrictions imposed by SELinux, if it is enabled.
					</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Updating_Packages-Applying_the_Changes.html"><strong>Anterior</strong>1.5.4. Applying the Changes</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Server_Security.html"><strong>Siguiente</strong>2.2. Server Security</a></li></ul></body></html>

--- NEW FILE chap-Security_Guide-Security_Overview.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>CapÃtulo 1. Security Overview</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="index.html" title="security-guide" /><link rel="prev" href="We_Need_Feedback.html" title="2. Â¡Se necesita retroalimentaciÃ³n!" /><link rel="next" href="sect-Security_Guide-Vulnerability_Assessment.html" title="1.2. Vulnerability Assessment" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></
 p><ul class="docnav"><li class="previous"><a accesskey="p" href="We_Need_Feedback.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Vulnerability_Assessment.html"><strong>Siguiente</strong></a></li></ul><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="chap-Security_Guide-Security_Overview.html#sect-Security_Guide-Introduction_to_Security">1.1. Introduction to Security</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Security_Guide-Security_Overview.html#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="chap-Security_Guide-Security_Overview.html#sect-Security_Guide-Introduction_to_Security-SELinux">1.1.2. SE
 Linux</a></span></dt><dt><span class="section"><a href="chap-Security_Guide-Security_Overview.html#sect-Security_Guide-Introduction_to_Security-Security_Controls">1.1.3. Security Controls</a></span></dt><dt><span class="section"><a href="chap-Security_Guide-Security_Overview.html#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.html">1.2. Vulnerability Assessment</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security_Guide-Vulnerability_Assessment.html#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.html">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.html">1.2.3. Herramientas de EvaluaciÃ³n</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Security_Guide-Attackers_and_Vulnerabilities.html">1.3. Attackers and Vulnerabilities</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security_Guide-Attackers_and_Vulnerabilities.html#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.html">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.html">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.html">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.html">1.4. Ataques y Aprovechadas ComÃºnes</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Security_Updates.html">1.5. Actualizaciones de Seguridad</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security_Guide-Security_Updates.html#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.html">1.5.2. Verifying Signed Packages</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Updating_Packages-Installing_Signed_Packages.html">1.5.3. Installing Signed Packages</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Updating_Packages-Applying_the_Changes.html">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.
	</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="id2935210" href="#ftn.id2935210" class="footnote">1</a>]</sup>and the Vladimir Levin <sup>[<a id="id2920281" href="#ftn.id2920281" 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.
			</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.
			</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.
			</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="id2871672" href="#ftn.id2871672" 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="id2904980" href="#ftn.id2904980" 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="id2953596" href="#ftn.id2953596" class="footnote">5</a>]</sup> At the same time:
			</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="id2873499" href="#ftn.id2873499" 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="id2862502" href="#ftn.id2862502" 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="id2898770" href="#ftn.id2898770" 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="id2880029" href="#ftn.id2880029" class="footnote">9</a>]</sup>, undertaken by <span class="emphasis"><em>CIO Magazine</em></span>, some points are:
			</div><div class="itemizedlist"><ul><li><div class="para">
						Just 43% of respondents audit or monitor user compliance with security policies
					</div></li><li><div class="para">
						Only 22% keep an inventory of the outside companies that use their data
					</div></li><li><div class="para">
						The source of nearly half of security incidents was marked as "Unknown"
					</div></li><li><div class="para">
						44% of respondents plan to increase security spending in the next year
					</div></li><li><div class="para">
						59% have an information security strategy
					</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.
			</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:
			</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.
					</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.
					</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.
					</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.html" 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>:
		</div><div class="itemizedlist"><ul><li><div class="para">
					Physical
				</div></li><li><div class="para">
					Technical
				</div></li><li><div class="para">
					Administrative
				</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:
			</div><div class="itemizedlist"><ul><li><div class="para">
						Closed-circuit surveillance cameras
					</div></li><li><div class="para">
						Motion or thermal alarm systems
					</div></li><li><div class="para">
						Security guards
					</div></li><li><div class="para">
						Picture IDs
					</div></li><li><div class="para">
						Locked and dead-bolted steel doors
					</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">
				Technical controls use technology as a basis for controlling the access and usage of sensitive data throughout a physical structure and over a network. Technical controls are far-reaching in scope and encompass such technologies as:
			</div><div class="itemizedlist"><ul><li><div class="para">
						Encryption
					</div></li><li><div class="para">
						Smart cards
					</div></li><li><div class="para">
						Network authentication
					</div></li><li><div class="para">
						Access control lists (ACLs)
					</div></li><li><div class="para">
						File integrity auditing software
					</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-Administrative_Controls">1.1.3.3. Administrative Controls</h4></div></div></div><div class="para">
				Administrative controls define the human factors of security. They involve all levels of personnel within an organization and determine which users have access to what resources and information by such means as:
			</div><div class="itemizedlist"><ul><li><div class="para">
						Training and awareness
					</div></li><li><div class="para">
						Disaster preparedness and recovery plans
					</div></li><li><div class="para">
						Personnel recruitment and separation strategies
					</div></li><li><div class="para">
						Personnel registration and accounting
					</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-Conclusion">1.1.4. ConclusiÃ³n</h3></div></div></div><div class="para">
			Now that you have learned about the origins, reasons, and aspects of security, you will find it easier to determine the appropriate course of action with regard to Fedora. It is important to know what factors and conditions make up security in order to plan and implement a proper strategy. With this information in mind, the process can be formalized and the path becomes clearer as you delve deeper into the specifics of the security process.
		</div></div></div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id2935210" href="#id2935210" class="para">1</a>] </sup>
					http://law.jrank.org/pages/3791/Kevin-Mitnick-Case-1999.html
				</p></div><div class="footnote"><p><sup>[<a id="ftn.id2920281" href="#id2920281" class="para">2</a>] </sup>
					http://www.livinginternet.com/i/ia_hackers_levin.htm
				</p></div><div class="footnote"><p><sup>[<a id="ftn.id2871672" href="#id2871672" class="para">3</a>] </sup>
					http://www.theregister.co.uk/2007/05/04/txj_nonfeasance/
				</p></div><div class="footnote"><p><sup>[<a id="ftn.id2904980" href="#id2904980" class="para">4</a>] </sup>
					http://www.healthcareitnews.com/story.cms?id=9408
				</p></div><div class="footnote"><p><sup>[<a id="ftn.id2953596" href="#id2953596" class="para">5</a>] </sup>
					http://www.internetworldstats.com/stats.htm
				</p></div><div class="footnote"><p><sup>[<a id="ftn.id2873499" href="#id2873499" class="para">6</a>] </sup>
							http://www.cert.org
						</p></div><div class="footnote"><p><sup>[<a id="ftn.id2862502" href="#id2862502" class="para">7</a>] </sup>
							http://www.cert.org/stats/fullstats.html
						</p></div><div class="footnote"><p><sup>[<a id="ftn.id2898770" href="#id2898770" class="para">8</a>] </sup>
							http://www.newsfactor.com/perl/story/16407.html
						</p></div><div class="footnote"><p><sup>[<a id="ftn.id2880029" href="#id2880029" class="para">9</a>] </sup>
					http://www.csoonline.com/article/454939/The_Global_State_of_Information_Security_
				</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="We_Need_Feedback.html"><strong>Anterior</strong>2. Â¡Se necesita retroalimentaciÃ³n!</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Vulnerability_Assessment.html"><strong>Siguiente</strong>1.2. Vulnerability Assessment</a></li></ul></body></html>

--- NEW FILE chap-Security_Guide-Software_Maintenance.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>CapÃtulo 6. Mantenimiento de Software</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="index.html" title="security-guide" /><link rel="prev" href="sect-Security_Guide-Secure_Installation-Utilize_LUKS_Partition_Encryption.html" title="5.2. Utilize LUKS Partition Encryption" /><link rel="next" href="sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates.html" title="6.2. Plan and Configure Security Updates" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="htt
 p://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Secure_Installation-Utilize_LUKS_Partition_Encryption.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates.html"><strong>Siguiente</strong></a></li></ul><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="chap-Security_Guide-Software_Maintenance.html#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.ht
 ml">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.html">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.html">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><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Secure_Installation-Utilize_LUKS_Partition_Encryption.html"><strong>Anterior</strong>5.2. Utilize LUKS Partition Encryption</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates.html"><strong>Siguiente</strong>6.2. Plan and Configure Security Updates</a></li></ul></body></html>

--- NEW FILE index.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>security-guide</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><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." /><link rel="home" href="index.html" title="security-guide" /><l
 ink rel="next" href="pref-Security_Guide-Preface.html" title="Prefacio" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"></li><li class="next"><a accesskey="n" href="pref-Security_Guide-Preface.html"><strong>Siguiente</strong></a></li></ul><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="id2715584" 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">
				<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="id2863429" 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.
	</div><div class="para">
		Red Hat and the Red Hat "Shadow Man" logo are registered trademarks of Red Hat Inc. in the United States and other countries.
	</div><div class="para">
		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.html">Prefacio</a></span></dt><dd><dl><dt><span class="section"><a href="pref-Security_Guide-Preface.html#id2955917">1. Convenciones del documento</a></span></dt><dd><dl><dt><span class="section"><a href="pref-Security_Guide-Preface.html#id2921728">1.1. Convenciones tipogrÃ¡ficas</a></span></dt><dt><span class="section"><a href="pref-Security_Guide-Preface.html#id2875062">1.2. Convenciones del documento</a></span></dt><dt><span class="section"><a href="pref-Security_Guide-Preface.html#id2870552">1.3. Notas y advertencias</a></span></dt></dl></dd><dt><span class="section"><a href="We_Need_Feedback.html">2. Â¡Se necesita retroalimentaciÃ³n!</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Security_Guide-Security_Overview.html">1. Security Overview</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Secur
 ity_Guide-Security_Overview.html#sect-Security_Guide-Introduction_to_Security">1.1. Introduction to Security</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Security_Guide-Security_Overview.html#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="chap-Security_Guide-Security_Overview.html#sect-Security_Guide-Introduction_to_Security-SELinux">1.1.2. SELinux</a></span></dt><dt><span class="section"><a href="chap-Security_Guide-Security_Overview.html#sect-Security_Guide-Introduction_to_Security-Security_Controls">1.1.3. Security Controls</a></span></dt><dt><span class="section"><a href="chap-Security_Guide-Security_Overview.html#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.html">1.2. Vulnerability Assessment</a></span></dt><dd>
 <dl><dt><span class="section"><a href="sect-Security_Guide-Vulnerability_Assessment.html#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.html">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.html">1.2.3. Herramientas de EvaluaciÃ³n</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Security_Guide-Attackers_and_Vulnerabilities.html">1.3. Attackers and Vulnerabilities</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security_Guide-Attackers_and_Vulnerabilities.html#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_Vulnerabi
 lities-Threats_to_Network_Security.html">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.html">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.html">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.html">1.4. Ataques y Aprovechadas ComÃºnes</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Security_Updates.html">1.5. Actualizaciones de Seguridad</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security_Guide-Security_Updates.html#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_Package
 s-Verifying_Signed_Packages.html">1.5.2. Verifying Signed Packages</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Updating_Packages-Installing_Signed_Packages.html">1.5.3. Installing Signed Packages</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Updating_Packages-Applying_the_Changes.html">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.html">2. Securing Your Network</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Security_Guide-Securing_Your_Network.html#sect-Security_Guide-Workstation_Security">2.1. Workstation Security</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Security_Guide-Securing_Your_Network.html#sect-Security_Guide-Workstation_Security-Evaluating_Workstation_Security">2.1.1. Evaluating Workstation Security</a></span></dt><dt><span class="section"><a href="chap-Security_Guide-Securing_Your_Networ
 k.html#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="chap-Security_Guide-Securing_Your_Network.html#sect-Security_Guide-Workstation_Security-Password_Security">2.1.3. Password Security</a></span></dt><dt><span class="section"><a href="chap-Security_Guide-Securing_Your_Network.html#sect-Security_Guide-Workstation_Security-Administrative_Controls">2.1.4. Administrative Controls</a></span></dt><dt><span class="section"><a href="chap-Security_Guide-Securing_Your_Network.html#sect-Security_Guide-Workstation_Security-Available_Network_Services">2.1.5. Servicios de Red Disponibles</a></span></dt><dt><span class="section"><a href="chap-Security_Guide-Securing_Your_Network.html#sect-Security_Guide-Workstation_Security-Personal_Firewalls">2.1.6. Cortafuegos Personal:</a></span></dt><dt><span class="section"><a href="chap-Security_Guide-Securing_Your_Network.html#sect-Securi
 ty_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.html">2.2. Server Security</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security_Guide-Server_Security.html#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.html">2.2.2. Securing Portmap</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Server_Security-Securing_NIS.html">2.2.3. Securing NIS</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Server_Security-Securing_NFS.html">2.2.4. Securing NFS</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Server_Security-Securing_the_Apache_HTTP_Server.html">2.2.5. S
 ecuring the Apache HTTP Server</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Server_Security-Securing_FTP.html">2.2.6. Securing FTP</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Server_Security-Securing_Sendmail.html">2.2.7. Securing Sendmail</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Server_Security-Verifying_Which_Ports_Are_Listening.html">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.html">2.3. Single Sign-on (SSO)</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security_Guide-Single_Sign_on_SSO.html#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.html">2.3.2. Getting Started with your new Smart Card</a></span></dt><dt><span class="sect
 ion"><a href="sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Enrollment_Works.html">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.html">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.html">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.html">2.4. Pluggable Authentication Modules (PAM)</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM.html#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.html">2.4.2. PAM Configuration Files</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_File_Format.html">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.html">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.html">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.html">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.html">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.html">2.4.8. Additional Resources</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Security_Guide-TCP_Wrappers_and_xinetd.html">2.5. TCP Wrappers and xinetd</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security_Guide-TCP_Wrappers_and_xinetd.html#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.html">2.5.2. TCP Wrappers Configuration Files</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd.html">2.5.3. xinetd</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd_Configuration_Files.html">2.5.4. xinetd Configuration Files</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-TCP_Wrappers_and_xinetd-Ad
 ditional_Resources.html">2.5.5. Additional Resources</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Security_Guide-Kerberos.html">2.6. Kerberos</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security_Guide-Kerberos.html#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.html">2.6.2. Kerberos Terminology</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Kerberos-How_Kerberos_Works.html">2.6.3. How Kerberos Works</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Kerberos-Kerberos_and_PAM.html">2.6.4. Kerberos y PAM</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Server.html">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.html">
 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.html">2.6.7. Domain-to-Realm Mapping</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Kerberos-Setting_Up_Secondary_KDCs.html">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.html">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.html">2.6.10. Additional Resources</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Security_Guide-Virtual_Private_Networks_VPNs.html">2.7. Virtual Private Networks (VPNs)</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security_Guide-Virtual_Private_Networks_VPNs.html#sect-Security_Guide-Virtual_Private_Networks_VPNs-How_Does_a_VPN_Work">2.7.1. How Do
 es a VPN Work?</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Virtual_Private_Networks_VPNs-VPNs_and_PROD.html">2.7.2. VPNs and Fedora</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec.html">2.7.3. IPsec</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Virtual_Private_Networks_VPNs-Creating_an_IPsec_Connection.html">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.html">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.html">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.html">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.html">2.7.8. Starting and Stopping an IPsec Connection</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Security_Guide-Firewalls.html">2.8. Firewalls</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security_Guide-Firewalls.html#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.html">2.8.2. ConfiguraciÃ³n BÃ¡sica del Cortafuego</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Firewalls-Using_IPTables.html">2.8.3. Uso de IPTables</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Firewalls-Common_IPTables_Filtering.html">2.8.4. Filtrado ComÃºn de IPTalbes</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Firewalls-FORWARD_a
 nd_NAT_Rules.html">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.html">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.html">2.8.7. IPTables y el Seguimiento de ConexiÃ³n</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Firewalls-IPv6.html">2.8.8. IPv6</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Firewalls-Additional_Resources.html">2.8.9. Additional Resources</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Security_Guide-IPTables.html">2.9. IPTables</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security_Guide-IPTables.html#sect-Security_Guide-IPTables-Packet_Filtering">2.9.1. Filtrado de Paquete</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-IPT
 ables-Differences_Between_IPTables_and_IPChains.html">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.html">2.9.3. Command Options for IPTables</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-IPTables-Saving_IPTables_Rules.html">2.9.4. Saving IPTables Rules</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-IPTables-IPTables_Control_Scripts.html">2.9.5. IPTables Control Scripts</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-IPTables-IPTables_and_IPv6.html">2.9.6. IPTables y IPv6</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-IPTables-Additional_Resources.html">2.9.7. Additional Resources</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="chap-Security_Guide-Encryption.html">3. Encryption</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Security_Guide
 -Encryption.html#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.html">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.html">3.3. EncriptaciÃ³n Basada en Archivo</a></span></dt><dt><span class="section"><a href="Security_Guide-Encryption-Data_in_Motion.html">3.4. Datos en Movimiento</a></span></dt><dt><span class="section"><a href="Security_Guide-Encryption-Data_in_Motion-Virtual_Private_Networks.html">3.5. Virtual Private Networks</a></span></dt><dt><span class="section"><a href="Security_Guide-Encryption-Data_in_Motion-Secure_Shell.html">3.6. Shell Seguro</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-LUKS_Disk_Encryption.html">3.7. LUKS Disk Encryption</a></span></dt><dd><dl><dt><span class="secti
 on"><a href="sect-Security_Guide-LUKS_Disk_Encryption.html#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.html">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.html">3.7.3. Step-by-Step Instructions</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-What_you_have_just_accomplished.html">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.html">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.html">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.html#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.html">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.html">3.8.3. Step-by-Step Usage Instructions</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Things_of_note.html">3.8.4. Things of note</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Security_Guide-Encryption-Using_GPG.html">3.9. Using GNU Privacy Guard (GnuPG)</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Security_Guide-Encryption-
 Using_GPG.html#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.html">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.html">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.html">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.html">4. Principios Generales sobre la Seguridad de la InformaciÃ³n</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Security_Guide-General_Principles_of_Information_Security.html#sect-Security_Guide-General_Principles_of_Information_Security-Tips_Guid
 es_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.html">5. Secure Installation</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Security_Guide-Secure_Installation.html#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.html">5.2. Utilize LUKS Partition Encryption</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Security_Guide-Software_Maintenance.html">6. Mantenimiento de Software</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Security_Guide-Software_Maintenance.html#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_Upd
 ates.html">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.html">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.html">6.4. Install Signed Packages from Well Known Repositories</a></span></dt></dl></dd><dt><span class="chapter"><a href="chap-Security_Guide-References.html">7. Referencias</a></span></dt></dl></div></div><ul class="docnav"><li class="previous"></li><li class="next"><a accesskey="n" href="pref-Security_Guide-Preface.html"><strong>Siguiente</strong>Prefacio</a></li></ul></body></html>

--- NEW FILE pref-Security_Guide-Preface.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Prefacio</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="index.html" title="security-guide" /><link rel="prev" href="index.html" title="security-guide" /><link rel="next" href="We_Need_Feedback.html" title="2. Â¡Se necesita retroalimentaciÃ³n!" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="index.html"
 ><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="We_Need_Feedback.html"><strong>Siguiente</strong></a></li></ul><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="id2955917">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="id2921728">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>
		</div><div class="para">
			Utilizada para resaltar la entrada del sistema, incluyendo comandos de shell, nombres de archivo y rutas. TambiÃ©n se utiliza para resaltar teclas claves y combinaciones de teclas.
		</div><div class="blockquote"><blockquote class="blockquote"><div class="para">
				To see the contents of the file <code class="filename">my_next_bestselling_novel</code> in your current working directory, enter the <code class="command">cat my_next_bestselling_novel</code> command at the shell prompt and press <span class="keycap"><strong>Enter</strong></span> to execute the command.
			</div></blockquote></div><div class="para">
			The above includes a file name, a shell command and a key cap, all presented in Mono-spaced Bold and all distinguishable thanks to context.
		</div><div class="para">
			Key-combinations can be distinguished from key caps by the hyphen connecting each part of a key-combination. For example:
		</div><div class="blockquote"><blockquote class="blockquote"><div class="para">
				Press <span class="keycap"><strong>Enter</strong></span> to execute the command.
			</div><div class="para">
				Press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>F1</strong></span> to switch to the first virtual terminal. Press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>F7</strong></span> to return to your X-Windows session.
			</div></blockquote></div><div class="para">
			The first sentence highlights the particular key cap to press. The second highlights two sets of three key caps, each set pressed simultaneously.
		</div><div class="para">
			If source code is discussed, class names, methods, functions, variable names and returned values mentioned within a paragraph will be presented as above, in <code class="literal">Mono-spaced Bold</code>. For example:
		</div><div class="blockquote"><blockquote class="blockquote"><div class="para">
				File-related classes include <code class="classname">filesystem</code> for file systems, <code class="classname">file</code> for files, and <code class="classname">dir</code> for directories. Each class has its own associated set of permissions.
			</div></blockquote></div><div class="para">
			<span class="application"><strong>Proportional Bold</strong></span>
		</div><div class="para">
			This denotes words or phrases encountered on a system, including application names; dialogue box text; labelled buttons; check-box and radio button labels; menu titles and sub-menu titles. For example:
		</div><div class="blockquote"><blockquote class="blockquote"><div class="para">
				Choose <span class="guimenu"><strong>System > Preferences > Mouse</strong></span> from the main menu bar to launch <span class="application"><strong>Mouse Preferences</strong></span>. In the <span class="guilabel"><strong>Buttons</strong></span> tab, click the <span class="guilabel"><strong>Left-handed mouse</strong></span> check box and click <span class="guibutton"><strong>Close</strong></span> to switch the primary mouse button from the left to the right (making the mouse suitable for use in the left hand).
			</div><div class="para">
				To insert a special character into a <span class="application"><strong>gedit</strong></span> file, choose <span class="guimenu"><strong>Applications > Accessories > Character Map</strong></span> from the main menu bar. Next, choose <span class="guimenu"><strong>Search > Findâ€¦</strong></span> from the <span class="application"><strong>Character Map</strong></span> menu bar, type the name of the character in the <span class="guilabel"><strong>Search</strong></span> field and click <span class="guibutton"><strong>Next</strong></span>. The character you sought will be highlighted in the <span class="guilabel"><strong>Character Table</strong></span>. Double-click this highlighted character to place it in the <span class="guilabel"><strong>Text to copy</strong></span> field and then click the <span class="guibutton"><strong>Copy</strong></span> button. Now switch back to your document and choose <span class="guimenu"><strong>Edit > Paste</strong></span> from the <
 span class="application"><strong>gedit</strong></span> menu bar.
			</div></blockquote></div><div class="para">
			The above text includes application names; system-wide menu names and items; application-specific menu names; and buttons and text found within a GUI interface, all presented in Proportional Bold and all distinguishable by context.
		</div><div class="para">
			Note the <span class="guimenu"><strong> ></strong></span> shorthand used to indicate traversal through a menu and its sub-menus. This is to avoid the difficult-to-follow 'Select <span class="guimenuitem"><strong>Mouse</strong></span> from the <span class="guimenu"><strong>Preferences</strong></span> sub-menu in the <span class="guimenu"><strong>System</strong></span> menu of the main menu bar' approach.
		</div><div class="para">
			<code class="command"><em class="replaceable"><code>Mono-spaced Bold Italic</code></em></code> or <span class="application"><strong><em class="replaceable"><code>Proportional Bold Italic</code></em></strong></span>
		</div><div class="para">
			Whether Mono-spaced Bold or Proportional Bold, the addition of Italics indicates replaceable or variable text. Italics denotes text you do not input literally or displayed text that changes depending on circumstance. For example:
		</div><div class="blockquote"><blockquote class="blockquote"><div class="para">
				To connect to a remote machine using ssh, type <code class="command">ssh <em class="replaceable"><code>username</code></em>@<em class="replaceable"><code>domain.name</code></em></code> at a shell prompt. If the remote machine is <code class="filename">example.com</code> and your username on that machine is john, type <code class="command">ssh john at example.com</code>.
			</div><div class="para">
				The <code class="command">mount -o remount <em class="replaceable"><code>file-system</code></em></code> command remounts the named file system. For example, to remount the <code class="filename">/home</code> file system, the command is <code class="command">mount -o remount /home</code>.
			</div><div class="para">
				To see the version of a currently installed package, use the <code class="command">rpm -q <em class="replaceable"><code>package</code></em></code> command. It will return a result as follows: <code class="command"><em class="replaceable"><code>package-version-release</code></em></code>.
			</div></blockquote></div><div class="para">
			Note the words in bold italics above â€” username, domain.name, file-system, package, version and release. Each word is a placeholder, either for text you enter when issuing a command or for text displayed by the system.
		</div><div class="para">
			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="id2875062">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Ã:
		</div><pre class="screen">libros        Escritorio   documentaciÃ³n  borradores  mss    fotos   cosas  svn
libros_tests  Escritorio1  descargas      imÃ¡genes  notas  scripts  svgs
</pre><div class="para">
			Los listados de cÃ³digo fuente tambiÃ©n se establecen en <code class="computeroutput">romano monoespaciado</code>, pero se presentan y resaltan de la siguiente manera:
		</div><pre class="programlisting">package org.jboss.book.jca.ex1;

import javax.naming.InitialContext;

public class ExClient
{
   public static void main(String args[]) 
       throws Exception
   {
      InitialContext iniCtx = new InitialContext();
      Object         ref    = iniCtx.lookup("EchoBean");
      EchoHome       home   = (EchoHome) ref;
      Echo           echo   = home.create();

      System.out.println("Created Echo");

      System.out.println("Echo.echo('Hello') = " + echo.echo("Hello"));
   }

}
</pre></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="id2870552">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.
			</div></div><div class="important"><h2>Importante</h2><div class="para">
				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><ul class="docnav"><li class="previous"><a accesskey="p" href="index.html"><strong>Anterior</strong>security-guide</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="We_Need_Feedback.html"><strong>Siguiente</strong>2. Â¡Se necesita retroalimentaciÃ³n!</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Additional_Resources-Related_Books.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.5.5.3. Related Books</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-TCP_Wrappers_and_xinetd-Additional_Resources.html" title="2.5.5. Additional Resources" /><link rel="prev" href="sect-Security_Guide-Additional_Resources-Useful_TCP_Wrappers_Websites.html" title="2.5.5.2. Useful TCP Wrappers Websites" /><link rel="next" href="sect-Security_Guide-Kerberos.html" title="2.6. Kerberos" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.o
 rg"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Additional_Resources-Useful_TCP_Wrappers_Websites.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Kerberos.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Additional_Resources-Related_Books">2.5.5.3. Related Books</h4></div></div></div><div class="itemizedlist"><ul><li><div class="para">
						<em class="citetitle">Hacking Linux Exposed</em> by Brian Hatch, James Lee, and George Kurtz; Osbourne/McGraw-Hill â€” An excellent security resource with information about TCP Wrappers and <code class="systemitem">xinetd</code>.
					</div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Additional_Resources-Useful_TCP_Wrappers_Websites.html"><strong>Anterior</strong>2.5.5.2. Useful TCP Wrappers Websites</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Kerberos.html"><strong>Siguiente</strong>2.6. Kerberos</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Additional_Resources-Related_Documentation.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.9.3. DocumentaciÃ³n Relacionada</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Firewalls-Additional_Resources.html" title="2.8.9. Additional Resources" /><link rel="prev" href="sect-Security_Guide-Additional_Resources-Useful_Firewall_Websites.html" title="2.8.9.2. Sitios web de Cortafuego Ãºtiles" /><link rel="next" href="sect-Security_Guide-IPTables.html" title="2.9. IPTables" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.or
 g"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Additional_Resources-Useful_Firewall_Websites.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-IPTables.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Additional_Resources-Related_Documentation">2.8.9.3. DocumentaciÃ³n Relacionada</h4></div></div></div><div class="itemizedlist"><ul><li><div class="para">
						<em class="citetitle">Red Hat Linux Firewalls</em>, por Bill McCarty; Red Hat Press â€” un manual de referencia completo para poder levantar cortafuegos de red o para servidores utilizando tecnologÃa de cÃ³digo abierto para filtrado de paquetes, como por ejemplo Netfilter o <code class="command">iptables</code>. Los temas que se tratan van desde el analisis de logs de cortafuegos, desarrollo de reglas de cortafuegos, y diferentes metodos de personalizaciÃ³n del cortafuegos utilizando numerosas herramientas grÃ¡ficas.
					</div></li><li><div class="para">
						<em class="citetitle">Linux Firewalls</em>, por Robert Ziegler; New Riders Press â€” contiene gran cantidad de informaciÃ³n para poder levantar cortafuegos utilizando tanto <code class="command">ipchains</code> de un kernel 2.2, como Netfilter o <code class="command">iptables</code>. TambiÃ©n son tratados otros temas relacionados con la seguridad, como problemas con el acceso remoto, o detecciÃ³n de intrusos en el sistema.
					</div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Additional_Resources-Useful_Firewall_Websites.html"><strong>Anterior</strong>2.8.9.2. Sitios web de Cortafuego Ãºtiles</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-IPTables.html"><strong>Siguiente</strong>2.9. IPTables</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Additional_Resources-Useful_Firewall_Websites.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.9.2. Sitios web de Cortafuego Ãºtiles</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Firewalls-Additional_Resources.html" title="2.8.9. Additional Resources" /><link rel="prev" href="sect-Security_Guide-Firewalls-Additional_Resources.html" title="2.8.9. Additional Resources" /><link rel="next" href="sect-Security_Guide-Additional_Resources-Related_Documentation.html" title="2.8.9.3. DocumentaciÃ³n Relacionada" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" h
 ref="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Firewalls-Additional_Resources.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Additional_Resources-Related_Documentation.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Additional_Resources-Useful_Firewall_Websites">2.8.9.2. Sitios web de Cortafuego Ãºtiles</h4></div></div></div><div class="itemizedlist"><ul><li><div class="para">
						<a href="http://www.netfilter.org/">http://www.netfilter.org/</a> â€” La pÃ¡gina oficial del proyecto Netfilter e <code class="command">iptables</code>.
					</div></li><li><div class="para">
						<a href="http://www.tldp.org/">http://www.tldp.org/</a> â€” El Proyecto de DocumentaciÃ³n de Linux contiene varias guÃas Ãºtiles sobre la creaciÃ³n y administraciÃ³n de cortafuegos.
					</div></li><li><div class="para">
						<a href="http://www.iana.org/assignments/port-numbers">http://www.iana.org/assignments/port-numbers</a> â€” La lista oficial de puertos de servicios comÃºnes y registrados segÃºn fueron asignados por la Autoridad de NÃºmeros de Internet Asignados.
					</div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Firewalls-Additional_Resources.html"><strong>Anterior</strong>2.8.9. Additional Resources</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Additional_Resources-Related_Documentation.html"><strong>Siguiente</strong>2.8.9.3. DocumentaciÃ³n Relacionada</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Additional_Resources-Useful_IP_Tables_Websites.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.9.7.2. Sitios web Ãºtiles sobre IP Tables</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-IPTables-Additional_Resources.html" title="2.9.7. Additional Resources" /><link rel="prev" href="sect-Security_Guide-IPTables-Additional_Resources.html" title="2.9.7. Additional Resources" /><link rel="next" href="chap-Security_Guide-Encryption.html" title="CapÃtulo 3. Encryption" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src
 ="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-IPTables-Additional_Resources.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="chap-Security_Guide-Encryption.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Additional_Resources-Useful_IP_Tables_Websites">2.9.7.2. Sitios web Ãºtiles sobre IP Tables</h4></div></div></div><div class="itemizedlist"><ul><li><div class="para">
						<a href="http://www.netfilter.org/">http://www.netfilter.org/</a> â€” El hogar del proyecto netfilter/iptables. Contiene informaciÃ³n ordenada acerca de <code class="command">iptables</code>, incluyendo un FAQ que describe problemas especÃficos, y varias guÃas utiles realizadas por Rusty Russell, el encargado del cortafuegos para IP de Linux. Los diferentes tutoriales del sitio abarcan diferentes temas, como ser por ejemplo, una descripciÃ³n de los conceptos bÃ¡sicos de trabajo en redes, filtros de paquetes del kernel y configuraciones NAT.
					</div></li><li><div class="para">
						<a href="http://www.linuxnewbie.org/nhf/Security/IPtables_Basics.html">http://www.linuxnewbie.org/nhf/Security/IPtables_Basics.html</a> â€” Una introducciÃ³n acerca de cÃ³mo los paquetes se trasladan dentro del kernel de Linux, mÃ¡s una introducciÃ³n para saber cÃ³mo construir comandos bÃ¡sicos de <code class="command">iptables</code>.
					</div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-IPTables-Additional_Resources.html"><strong>Anterior</strong>2.9.7. Additional Resources</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="chap-Security_Guide-Encryption.html"><strong>Siguiente</strong>CapÃtulo 3. Encryption</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Additional_Resources-Useful_Kerberos_Websites.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.6.10.2. Useful Kerberos Websites</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Kerberos-Additional_Resources.html" title="2.6.10. Additional Resources" /><link rel="prev" href="sect-Security_Guide-Kerberos-Additional_Resources.html" title="2.6.10. Additional Resources" /><link rel="next" href="sect-Security_Guide-Virtual_Private_Networks_VPNs.html" title="2.7. Virtual Private Networks (VPNs)" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fe
 doraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Kerberos-Additional_Resources.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Virtual_Private_Networks_VPNs.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Additional_Resources-Useful_Kerberos_Websites">2.6.10.2. Useful Kerberos Websites</h4></div></div></div><div class="itemizedlist"><ul><li><div class="para">
						<a href="http://web.mit.edu/kerberos/www/">http://web.mit.edu/kerberos/www/</a> â€” <em class="citetitle">Kerberos: El Protocolo de AutenticaciÃ³n de Red</em> del MIT.
					</div></li><li><div class="para">
						<a href="http://www.nrl.navy.mil/CCS/people/kenh/kerberos-faq.html">http://www.nrl.navy.mil/CCS/people/kenh/kerberos-faq.html</a> â€” Las Preguntas Frecuentes de Kerberos (FAQ).
					</div></li><li><div class="para">
						<a href="ftp://athena-dist.mit.edu/pub/kerberos/doc/usenix.PS">ftp://athena-dist.mit.edu/pub/kerberos/doc/usenix.PS</a> â€” The PostScript version of <em class="citetitle">Kerberos: An Authentication Service for Open Network Systems</em> by Jennifer G. Steiner, Clifford Neuman, and Jeffrey I. Schiller. This document is the original paper describing Kerberos.
					</div></li><li><div class="para">
						<a href="http://web.mit.edu/kerberos/www/dialogue.html">http://web.mit.edu/kerberos/www/dialogue.html</a> â€” <em class="citetitle">Designing an Authentication System: a Dialogue in Four Scenes</em> originally by Bill Bryant in 1988, modified by Theodore Ts'o in 1997. This document is a conversation between two developers who are thinking through the creation of a Kerberos-style authentication system. The conversational style of the discussion make this a good starting place for people who are completely unfamiliar with Kerberos.
					</div></li><li><div class="para">
						<a href="http://www.ornl.gov/~jar/HowToKerb.html">http://www.ornl.gov/~jar/HowToKerb.html</a> â€” <em class="citetitle">CÃ³mo Kerberizar su sitio</em> es una buena referencia para kerberizar su red.
					</div></li><li><div class="para">
						<a href="http://www.networkcomputing.com/netdesign/kerb1.html">http://www.networkcomputing.com/netdesign/kerb1.html</a> â€” <em class="citetitle">Manual de DiseÃ±o de Red con Kerberos</em> es un repaso extenso sobre el sistema Kerberos.
					</div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Kerberos-Additional_Resources.html"><strong>Anterior</strong>2.6.10. Additional Resources</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Virtual_Private_Networks_VPNs.html"><strong>Siguiente</strong>2.7. Virtual Private Networks (VPNs)</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Additional_Resources-Useful_PAM_Websites.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.4.8.2. Useful PAM Websites</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Additional_Resources.html" title="2.4.8. Additional Resources" /><link rel="prev" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Additional_Resources.html" title="2.4.8. Additional Resources" /><link rel="next" href="sect-Security_Guide-TCP_Wrappers_and_xinetd.html" title="2.5. TCP Wrappers and xinetd" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a 
 class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Additional_Resources.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-TCP_Wrappers_and_xinetd.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Additional_Resources-Useful_PAM_Websites">2.4.8.2. Useful PAM Websites</h4></div></div></div><div class="itemizedlist"><ul><li><div class="para">
						<a href="http://www.kernel.org/pub/linux/libs/pam/">http://www.kernel.org/pub/linux/libs/pam/</a> â€” The primary distribution website for the Linux-PAM project, containing information on various PAM modules, a FAQ, and additional PAM documentation.
					</div><div class="note"><h2>Note</h2><div class="para">
							The documentation in the above website is for the last released upstream version of PAM and might not be 100% accurate for the PAM version included in Fedora.
						</div></div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Additional_Resources.html"><strong>Anterior</strong>2.4.8. Additional Resources</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-TCP_Wrappers_and_xinetd.html"><strong>Siguiente</strong>2.5. TCP Wrappers and xinetd</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Additional_Resources-Useful_TCP_Wrappers_Websites.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.5.5.2. Useful TCP Wrappers Websites</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-TCP_Wrappers_and_xinetd-Additional_Resources.html" title="2.5.5. Additional Resources" /><link rel="prev" href="sect-Security_Guide-TCP_Wrappers_and_xinetd-Additional_Resources.html" title="2.5.5. Additional Resources" /><link rel="next" href="sect-Security_Guide-Additional_Resources-Related_Books.html" title="2.5.5.3. Related Books" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right
 " href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-TCP_Wrappers_and_xinetd-Additional_Resources.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Additional_Resources-Related_Books.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Additional_Resources-Useful_TCP_Wrappers_Websites">2.5.5.2. Useful TCP Wrappers Websites</h4></div></div></div><div class="itemizedlist"><ul><li><div class="para">
						<a href="http://www.xinetd.org">http://www.xinetd.org/</a> â€” The home of <code class="systemitem">xinetd</code>, containing sample configuration files, a full listing of features, and an informative FAQ.
					</div></li><li><div class="para">
						<a href="http://www.docstoc.com/docs/2133633/An-Unofficial-Xinetd-Tutorial">http://www.docstoc.com/docs/2133633/An-Unofficial-Xinetd-Tutorial</a> â€” A thorough tutorial that discusses many different ways to optimize default <code class="systemitem">xinetd</code> configuration files to meet specific security goals.
					</div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-TCP_Wrappers_and_xinetd-Additional_Resources.html"><strong>Anterior</strong>2.5.5. Additional Resources</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Additional_Resources-Related_Books.html"><strong>Siguiente</strong>2.5.5.3. Related Books</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Altering_xinetd_Configuration_Files-Access_Control_Options.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.5.4.3.2. Access Control Options</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-xinetd_Configuration_Files-Altering_xinetd_Configuration_Files.html" title="2.5.4.3. Altering xinetd Configuration Files" /><link rel="prev" href="sect-Security_Guide-xinetd_Configuration_Files-Altering_xinetd_Configuration_Files.html" title="2.5.4.3. Altering xinetd Configuration Files" /><link rel="next" href="sect-Security_Guide-Altering_xinetd_Configuration_Files-Binding_and_Redirection_Options.html" title="2.5.4.3.3. Binding and Redirection Options" /></head><body class=""><p id="title"><a class="left" href=
 "http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-xinetd_Configuration_Files-Altering_xinetd_Configuration_Files.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Altering_xinetd_Configuration_Files-Binding_and_Redirection_Options.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h5 class="title" id="sect-Security_Guide-Altering_xinetd_Configuration_Files-Access_Control_Options">2.5.4.3.2. Access Control Options</h5></div></div></div><div class="para">
					Users of <code class="systemitem">xinetd</code> services can choose to use the TCP Wrappers hosts access rules, provide access control via the <code class="systemitem">xinetd</code> configuration files, or a mixture of both. Refer to <a class="xref" href="sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers_Configuration_Files.html" title="2.5.2. TCP Wrappers Configuration Files">SecciÃ³nÂ 2.5.2, â€œTCP Wrappers Configuration Filesâ€</a> for more information about TCP Wrappers hosts access control files.
				</div><div class="para">
					This section discusses using <code class="systemitem">xinetd</code> to control access to services.
				</div><div class="note"><h2>Note</h2><div class="para">
						Unlike TCP Wrappers, changes to access control only take effect if the <code class="systemitem">xinetd</code> administrator restarts the <code class="systemitem">xinetd</code> service.
					</div><div class="para">
						Also, unlike TCP Wrappers, access control through <code class="systemitem">xinetd</code> only affects services controlled by <code class="systemitem">xinetd</code>.
					</div></div><div class="para">
					The <code class="systemitem">xinetd</code> hosts access control differs from the method used by TCP Wrappers. While TCP Wrappers places all of the access configuration within two files, <code class="filename">/etc/hosts.allow</code> and <code class="filename">/etc/hosts.deny</code>, <code class="systemitem">xinetd</code>'s access control is found in each service's configuration file in the <code class="filename">/etc/xinetd.d/</code> directory.
				</div><div class="para">
					The following hosts access options are supported by <code class="systemitem">xinetd</code>:
				</div><div class="itemizedlist"><ul><li><div class="para">
							<code class="option">only_from</code> â€” Allows only the specified hosts to use the service.
						</div></li><li><div class="para">
							<code class="option">no_access</code> â€” Blocks listed hosts from using the service.
						</div></li><li><div class="para">
							<code class="option">access_times</code> â€” Specifies the time range when a particular service may be used. The time range must be stated in 24-hour format notation, HH:MM-HH:MM.
						</div></li></ul></div><div class="para">
					The <code class="option">only_from</code> and <code class="option">no_access</code> options can use a list of IP addresses or host names, or can specify an entire network. Like TCP Wrappers, combining <code class="systemitem">xinetd</code> access control with the enhanced logging configuration can increase security by blocking requests from banned hosts while verbosely recording each connection attempt.
				</div><div class="para">
					For example, the following <code class="filename">/etc/xinetd.d/telnet</code> file can be used to block Telnet access from a particular network group and restrict the overall time range that even allowed users can log in:
				</div><pre class="screen">service telnet
{
         disable         = no
         flags           = REUSE
         socket_type     = stream
         wait            = no
         user            = root
         server          = /usr/kerberos/sbin/telnetd
         log_on_failure  += USERID
         no_access       = 172.16.45.0/24
         log_on_success  += PID HOST EXIT
         access_times    = 09:45-16:15
}
</pre><div class="para">
					In this example, when a client system from the <code class="systemitem">10.0.1.0/24</code> network, such as <code class="systemitem">10.0.1.2</code>, tries to access the Telnet service, it receives the following message:
				</div><pre class="screen">Connection closed by foreign host.
</pre><div class="para">
					In addition, their login attempts are logged in <code class="filename">/var/log/messages</code> as follows:
				</div><pre class="screen">Sep  7 14:58:33 localhost xinetd[5285]: FAIL: telnet address from=172.16.45.107
Sep  7 14:58:33 localhost xinetd[5283]: START: telnet pid=5285 from=172.16.45.107
Sep  7 14:58:33 localhost xinetd[5283]: EXIT: telnet status=0 pid=5285 duration=0(sec)
</pre><div class="para">
					When using TCP Wrappers in conjunction with <code class="systemitem">xinetd</code> access controls, it is important to understand the relationship between the two access control mechanisms.
				</div><div class="para">
					The following is the sequence of events followed by <code class="systemitem">xinetd</code> when a client requests a connection:
				</div><div class="orderedlist"><ol><li><div class="para">
							The <code class="systemitem">xinetd</code> daemon accesses the TCP Wrappers hosts access rules using a <code class="filename">libwrap.a</code> library call. If a deny rule matches the client, the connection is dropped. If an allow rule matches the client, the connection is passed to <code class="systemitem">xinetd</code>.
						</div></li><li><div class="para">
							The <code class="systemitem">xinetd</code> daemon checks its own access control rules both for the <code class="systemitem">xinetd</code> service and the requested service. If a deny rule matches the client, the connection is dropped. Otherwise, <code class="systemitem">xinetd</code> starts an instance of the requested service and passes control of the connection to that service.
						</div></li></ol></div><div class="important"><h2>Important</h2><div class="para">
						Care should be taken when using TCP Wrappers access controls in conjunction with <code class="systemitem">xinetd</code> access controls. Misconfiguration can cause undesirable effects.
					</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-xinetd_Configuration_Files-Altering_xinetd_Configuration_Files.html"><strong>Anterior</strong>2.5.4.3. Altering xinetd Configuration Files</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Altering_xinetd_Configuration_Files-Binding_and_Redirection_Options.html"><strong>Siguiente</strong>2.5.4.3.3. Binding and Redirection Options</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Altering_xinetd_Configuration_Files-Binding_and_Redirection_Options.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.5.4.3.3. Binding and Redirection Options</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-xinetd_Configuration_Files-Altering_xinetd_Configuration_Files.html" title="2.5.4.3. Altering xinetd Configuration Files" /><link rel="prev" href="sect-Security_Guide-Altering_xinetd_Configuration_Files-Access_Control_Options.html" title="2.5.4.3.2. Access Control Options" /><link rel="next" href="sect-Security_Guide-Altering_xinetd_Configuration_Files-Resource_Management_Options.html" title="2.5.4.3.4. Resource Management Options" /></head><body class=""><p id="title"><a class="left" href="http://www.fe
 doraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Altering_xinetd_Configuration_Files-Access_Control_Options.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Altering_xinetd_Configuration_Files-Resource_Management_Options.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h5 class="title" id="sect-Security_Guide-Altering_xinetd_Configuration_Files-Binding_and_Redirection_Options">2.5.4.3.3. Binding and Redirection Options</h5></div></div></div><div class="para">
					The service configuration files for <code class="systemitem">xinetd</code> support binding the service to an IP address and redirecting incoming requests for that service to another IP address, hostname, or port.
				</div><div class="para">
					Binding is controlled with the <code class="option">bind</code> option in the service-specific configuration files and links the service to one IP address on the system. When this is configured, the <code class="option">bind</code> option only allows requests to the correct IP address to access the service. You can use this method to bind different services to different network interfaces based on requirements.
				</div><div class="para">
					This is particularly useful for systems with multiple network adapters or with multiple IP addresses. On such a system, insecure services (for example, Telnet), can be configured to listen only on the interface connected to a private network and not to the interface connected to the Internet.
				</div><div class="para">
					The <code class="option">redirect</code> option accepts an IP address or hostname followed by a port number. It configures the service to redirect any requests for this service to the specified host and port number. This feature can be used to point to another port number on the same system, redirect the request to a different IP address on the same machine, shift the request to a totally different system and port number, or any combination of these options. A user connecting to a certain service on a system may therefore be rerouted to another system without disruption.
				</div><div class="para">
					The <code class="systemitem">xinetd</code> daemon is able to accomplish this redirection by spawning a process that stays alive for the duration of the connection between the requesting client machine and the host actually providing the service, transferring data between the two systems.
				</div><div class="para">
					The advantages of the <code class="option">bind</code> and <code class="option">redirect</code> options are most clearly evident when they are used together. By binding a service to a particular IP address on a system and then redirecting requests for this service to a second machine that only the first machine can see, an internal system can be used to provide services for a totally different network. Alternatively, these options can be used to limit the exposure of a particular service on a multi-homed machine to a known IP address, as well as redirect any requests for that service to another machine especially configured for that purpose.
				</div><div class="para">
					For example, consider a system that is used as a firewall with this setting for its Telnet service:
				</div><pre class="screen">service telnet
{
         socket_type                = stream
         wait                        = no
         server                        = /usr/kerberos/sbin/telnetd
         log_on_success                += DURATION USERID
         log_on_failure                += USERID
         bind                    = 123.123.123.123
         redirect                = 10.0.1.13 23
}
</pre><div class="para">
					The <code class="option">bind</code> and <code class="option">redirect</code> options in this file ensure that the Telnet service on the machine is bound to the external IP address (<code class="systemitem">123.123.123.123</code>), the one facing the Internet. In addition, any requests for Telnet service sent to <code class="systemitem">123.123.123.123</code> are redirected via a second network adapter to an internal IP address (<code class="systemitem">10.0.1.13</code>) that only the firewall and internal systems can access. The firewall then sends the communication between the two systems, and the connecting system thinks it is connected to <code class="systemitem">123.123.123.123</code> when it is actually connected to a different machine.
				</div><div class="para">
					This feature is particularly useful for users with broadband connections and only one fixed IP address. When using Network Address Translation (NAT), the systems behind the gateway machine, which are using internal-only IP addresses, are not available from outside the gateway system. However, when certain services controlled by <code class="systemitem">xinetd</code> are configured with the <code class="option">bind</code> and <code class="option">redirect</code> options, the gateway machine can act as a proxy between outside systems and a particular internal machine configured to provide the service. In addition, the various <code class="systemitem">xinetd</code> access control and logging options are also available for additional protection.
				</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Altering_xinetd_Configuration_Files-Access_Control_Options.html"><strong>Anterior</strong>2.5.4.3.2. Access Control Options</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Altering_xinetd_Configuration_Files-Resource_Management_Options.html"><strong>Siguiente</strong>2.5.4.3.4. Resource Management Options</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Altering_xinetd_Configuration_Files-Resource_Management_Options.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.5.4.3.4. Resource Management Options</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-xinetd_Configuration_Files-Altering_xinetd_Configuration_Files.html" title="2.5.4.3. Altering xinetd Configuration Files" /><link rel="prev" href="sect-Security_Guide-Altering_xinetd_Configuration_Files-Binding_and_Redirection_Options.html" title="2.5.4.3.3. Binding and Redirection Options" /><link rel="next" href="sect-Security_Guide-TCP_Wrappers_and_xinetd-Additional_Resources.html" title="2.5.5. Additional Resources" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"
 ><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Altering_xinetd_Configuration_Files-Binding_and_Redirection_Options.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-TCP_Wrappers_and_xinetd-Additional_Resources.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h5 class="title" id="sect-Security_Guide-Altering_xinetd_Configuration_Files-Resource_Management_Options">2.5.4.3.4. Resource Management Options</h5></div></div></div><div class="para">
					The <code class="systemitem">xinetd</code> daemon can add a basic level of protection from Denial of Service (DoS) attacks. The following is a list of directives which can aid in limiting the effectiveness of such attacks:
				</div><div class="itemizedlist"><ul><li><div class="para">
							<code class="option">per_source</code> â€” Defines the maximum number of instances for a service per source IP address. It accepts only integers as an argument and can be used in both <code class="filename">xinetd.conf</code> and in the service-specific configuration files in the <code class="filename">xinetd.d/</code> directory.
						</div></li><li><div class="para">
							<code class="option">cps</code> â€” Defines the maximum number of connections per second. This directive takes two integer arguments separated by white space. The first argument is the maximum number of connections allowed to the service per second. The second argument is the number of seconds that <code class="systemitem">xinetd</code> must wait before re-enabling the service. It accepts only integers as arguments and can be used in either the <code class="filename">xinetd.conf</code> file or the service-specific configuration files in the <code class="filename">xinetd.d/</code> directory.
						</div></li><li><div class="para">
							<code class="option">max_load</code> â€” Defines the CPU usage or load average threshold for a service. It accepts a floating point number argument.
						</div><div class="para">
							The load average is a rough measure of how many processes are active at a given time. See the <code class="command">uptime</code>, <code class="command">who</code>, and <code class="command">procinfo</code> commands for more information about load average.
						</div></li></ul></div><div class="para">
					There are more resource management options available for <code class="systemitem">xinetd</code>. Refer to the <code class="filename">xinetd.conf</code> man page for more information.
				</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Altering_xinetd_Configuration_Files-Binding_and_Redirection_Options.html"><strong>Anterior</strong>2.5.4.3.3. Binding and Redirection Options</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-TCP_Wrappers_and_xinetd-Additional_Resources.html"><strong>Siguiente</strong>2.5.5. Additional Resources</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Network_Security.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.3.2. Threats to Network Security</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Attackers_and_Vulnerabilities.html" title="1.3. Attackers and Vulnerabilities" /><link rel="prev" href="sect-Security_Guide-Attackers_and_Vulnerabilities.html" title="1.3. Attackers and Vulnerabilities" /><link rel="next" href="sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Server_Security.html" title="1.3.3. Threats to Server Security" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><
 a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Attackers_and_Vulnerabilities.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Server_Security.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Network_Security">1.3.2. Threats to Network Security</h3></div></div></div><div class="para">
			Bad practices when configuring the following aspects of a network can increase the risk of attack.
		</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Threats_to_Network_Security-Insecure_Architectures">1.3.2.1. Insecure Architectures</h4></div></div></div><div class="para">
				A misconfigured network is a primary entry point for unauthorized users. Leaving a trust-based, open local network vulnerable to the highly-insecure Internet is much like leaving a door ajar in a crime-ridden neighborhood â€” nothing may happen for an arbitrary amount of time, but <span class="emphasis"><em>eventually</em></span> someone exploits the opportunity.
			</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h5 class="title" id="sect-Security_Guide-Insecure_Architectures-Broadcast_Networks">1.3.2.1.1. Broadcast Networks</h5></div></div></div><div class="para">
					System administrators often fail to realize the importance of networking hardware in their security schemes. Simple hardware such as hubs and routers rely on the broadcast or non-switched principle; that is, whenever a node transmits data across the network to a recipient node, the hub or router sends a broadcast of the data packets until the recipient node receives and processes the data. This method is the most vulnerable to address resolution protocol (<em class="firstterm">arp</em>) or media access control (<em class="firstterm">MAC</em>) address spoofing by both outside intruders and unauthorized users on local hosts.
				</div></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h5 class="title" id="sect-Security_Guide-Insecure_Architectures-Centralized_Servers">1.3.2.1.2. Centralized Servers</h5></div></div></div><div class="para">
					Another potential networking pitfall is the use of centralized computing. A common cost-cutting measure for many businesses is to consolidate all services to a single powerful machine. This can be convenient as it is easier to manage and costs considerably less than multiple-server configurations. However, a centralized server introduces a single point of failure on the network. If the central server is compromised, it may render the network completely useless or worse, prone to data manipulation or theft. In these situations, a central server becomes an open door which allows access to the entire network.
				</div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Attackers_and_Vulnerabilities.html"><strong>Anterior</strong>1.3. Attackers and Vulnerabilities</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Server_Security.html"><strong>Siguiente</strong>1.3.3. Threats to Server Security</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Server_Security.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.3.3. Threats to Server Security</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Attackers_and_Vulnerabilities.html" title="1.3. Attackers and Vulnerabilities" /><link rel="prev" href="sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Network_Security.html" title="1.3.2. Threats to Network Security" /><link rel="next" href="sect-Security_Guide-Threats_to_Server_Security-Unpatched_Services.html" title="1.3.3.2. Unpatched Services" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Sit
 e" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Network_Security.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Threats_to_Server_Security-Unpatched_Services.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Server_Security">1.3.3. Threats to Server Security</h3></div></div></div><div class="para">
			Server security is as important as network security because servers often hold a great deal of an organization's vital information. If a server is compromised, all of its contents may become available for the cracker to steal or manipulate at will. The following sections detail some of the main issues.
		</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Threats_to_Server_Security-Unused_Services_and_Open_Ports">1.3.3.1. Unused Services and Open Ports</h4></div></div></div><div class="para">
				A full installation of Fedora contains 1000+ application and library packages. However, most server administrators do not opt to install every single package in the distribution, preferring instead to install a base installation of packages, including several server applications.
			</div><div class="para">
				A common occurrence among system administrators is to install the operating system without paying attention to what programs are actually being installed. This can be problematic because unneeded services may be installed, configured with the default settings, and possibly turned on. This can cause unwanted services, such as Telnet, DHCP, or DNS, to run on a server or workstation without the administrator realizing it, which in turn can cause unwanted traffic to the server, or even, a potential pathway into the system for crackers. Refer To <a class="xref" href="sect-Security_Guide-Server_Security.html" title="2.2. Server Security">SecciÃ³nÂ 2.2, â€œServer Securityâ€</a> for information on closing ports and disabling unused services.
			</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Network_Security.html"><strong>Anterior</strong>1.3.2. Threats to Network Security</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Threats_to_Server_Security-Unpatched_Services.html"><strong>Siguiente</strong>1.3.3.2. Unpatched Services</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Workstation_and_Home_PC_Security.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.3.4. Threats to Workstation and Home PC Security</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Attackers_and_Vulnerabilities.html" title="1.3. Attackers and Vulnerabilities" /><link rel="prev" href="sect-Security_Guide-Threats_to_Server_Security-Inherently_Insecure_Services.html" title="1.3.3.4. Inherently Insecure Services" /><link rel="next" href="sect-Security_Guide-Threats_to_Workstation_and_Home_PC_Security-Vulnerable_Client_Applications.html" title="1.3.4.2. Vulnerable Client Applications" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img 
 src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Threats_to_Server_Security-Inherently_Insecure_Services.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Threats_to_Workstation_and_Home_PC_Security-Vulnerable_Client_Applications.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Workstation_and_Home_PC_Security">1.3.4. Threats to Workstation and Home PC Security</h3></div></div></div><div class="para">
			Workstations and home PCs may not be as prone to attack as networks or servers, but since they often contain sensitive data, such as credit card information, they are targeted by system crackers. Workstations can also be co-opted without the user's knowledge and used by attackers as "slave" machines in coordinated attacks. For these reasons, knowing the vulnerabilities of a workstation can save users the headache of reinstalling the operating system, or worse, recovering from data theft.
		</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Threats_to_Workstation_and_Home_PC_Security-Bad_Passwords">1.3.4.1. Bad Passwords</h4></div></div></div><div class="para">
				Bad passwords are one of the easiest ways for an attacker to gain access to a system. For more on how to avoid common pitfalls when creating a password, refer to <a class="xref" href="chap-Security_Guide-Securing_Your_Network.html#sect-Security_Guide-Workstation_Security-Password_Security" title="2.1.3. Password Security">SecciÃ³nÂ 2.1.3, â€œPassword Securityâ€</a>.
			</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Threats_to_Server_Security-Inherently_Insecure_Services.html"><strong>Anterior</strong>1.3.3.4. Inherently Insecure Services</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Threats_to_Workstation_and_Home_PC_Security-Vulnerable_Client_Applications.html"><strong>Siguiente</strong>1.3.4.2. Vulnerable Client Applications</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Attackers_and_Vulnerabilities.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.3. Attackers and Vulnerabilities</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="chap-Security_Guide-Security_Overview.html" title="CapÃtulo 1. Security Overview" /><link rel="prev" href="sect-Security_Guide-Evaluating_the_Tools-Anticipating_Your_Future_Needs.html" title="1.2.3.5. Anticipando sus Necesidades Futuras" /><link rel="next" href="sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Network_Security.html" title="1.3.2. Threats to Network Security" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Pro
 duct Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Evaluating_the_Tools-Anticipating_Your_Future_Needs.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Network_Security.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h2 class="title" id="sect-Security_Guide-Attackers_and_Vulnerabilities">1.3. Attackers and Vulnerabilities</h2></div></div></div><div class="para">
		To plan and implement a good security strategy, first be aware of some of the issues which determined, motivated attackers exploit to compromise systems. However, before detailing these issues, the terminology used when identifying an attacker must be defined.
	</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Attackers_and_Vulnerabilities-A_Quick_History_of_Hackers">1.3.1. A Quick History of Hackers</h3></div></div></div><div class="para">
			The modern meaning of the term <em class="firstterm">hacker</em> has origins dating back to the 1960s and the Massachusetts Institute of Technology (MIT) Tech Model Railroad Club, which designed train sets of large scale and intricate detail. Hacker was a name used for club members who discovered a clever trick or workaround for a problem.
		</div><div class="para">
			The term hacker has since come to describe everything from computer buffs to gifted programmers. A common trait among most hackers is a willingness to explore in detail how computer systems and networks function with little or no outside motivation. Open source software developers often consider themselves and their colleagues to be hackers, and use the word as a term of respect.
		</div><div class="para">
			Typically, hackers follow a form of the <em class="firstterm">hacker ethic</em> which dictates that the quest for information and expertise is essential, and that sharing this knowledge is the hackers duty to the community. During this quest for knowledge, some hackers enjoy the academic challenges of circumventing security controls on computer systems. For this reason, the press often uses the term hacker to describe those who illicitly access systems and networks with unscrupulous, malicious, or criminal intent. The more accurate term for this type of computer hacker is <em class="firstterm">cracker</em> â€” a term created by hackers in the mid-1980s to differentiate the two communities.
		</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-A_Quick_History_of_Hackers-Shades_of_Gray">1.3.1.1. Shades of Gray</h4></div></div></div><div class="para">
				Within the community of individuals who find and exploit vulnerabilities in systems and networks are several distinct groups. These groups are often described by the shade of hat that they "wear" when performing their security investigations and this shade is indicative of their intent.
			</div><div class="para">
				The <em class="firstterm">white hat hacker</em> is one who tests networks and systems to examine their performance and determine how vulnerable they are to intrusion. Usually, white hat hackers crack their own systems or the systems of a client who has specifically employed them for the purposes of security auditing. Academic researchers and professional security consultants are two examples of white hat hackers.
			</div><div class="para">
				A <em class="firstterm">black hat hacker</em> is synonymous with a cracker. In general, crackers are less focused on programming and the academic side of breaking into systems. They often rely on available cracking programs and exploit well known vulnerabilities in systems to uncover sensitive information for personal gain or to inflict damage on the target system or network.
			</div><div class="para">
				The <em class="firstterm">gray hat hacker</em>, on the other hand, has the skills and intent of a white hat hacker in most situations but uses his knowledge for less than noble purposes on occasion. A gray hat hacker can be thought of as a white hat hacker who wears a black hat at times to accomplish his own agenda.
			</div><div class="para">
				Gray hat hackers typically subscribe to another form of the hacker ethic, which says it is acceptable to break into systems as long as the hacker does not commit theft or breach confidentiality. Some would argue, however, that the act of breaking into a system is in itself unethical.
			</div><div class="para">
				Regardless of the intent of the intruder, it is important to know the weaknesses a cracker may likely attempt to exploit. The remainder of the chapter focuses on these issues.
			</div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Evaluating_the_Tools-Anticipating_Your_Future_Needs.html"><strong>Anterior</strong>1.2.3.5. Anticipando sus Necesidades Futuras</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Network_Security.html"><strong>Siguiente</strong>1.3.2. Threats to Network Security</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Basic_Firewall_Configuration-Activating_the_IPTables_Service.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.2.6. Activando el Servicio IPTables</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Firewalls-Basic_Firewall_Configuration.html" title="2.8.2. ConfiguraciÃ³n BÃ¡sica del Cortafuego" /><link rel="prev" href="sect-Security_Guide-Basic_Firewall_Configuration-Saving_the_Settings.html" title="2.8.2.5. Guardando la ConfiguraciÃ³n" /><link rel="next" href="sect-Security_Guide-Firewalls-Using_IPTables.html" title="2.8.3. Uso de IPTables" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a
 ><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Basic_Firewall_Configuration-Saving_the_Settings.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Firewalls-Using_IPTables.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Basic_Firewall_Configuration-Activating_the_IPTables_Service">2.8.2.6. Activando el Servicio IPTables</h4></div></div></div><div class="para">
				Las reglas del cortafuego estÃ¡n solamente activas si el servicio <code class="command">iptables</code> se estÃ¡ ejecutando. Para iniciar manualmente el servicio, use el siguiente comando:
			</div><pre class="screen">[root at miServidor ~] # service iptables restart
</pre><div class="para">
				Para asegurarse de que <code class="command">iptables</code> se inicie cuando el sistema arranque, use el siguiente comando:
			</div><pre class="screen">[root at miServidor ~] # chkconfig --level 345 iptables on
</pre><div class="para">
				El servicio <code class="command">ipchains</code> no estÃ¡ incluido en Fedora. Sin embargo, si se instala <code class="command">ipchains</code> (por ejemplo, fue realizada una actualizaciÃ³n de una sistema que ya tenÃa <code class="command">ipchains</code> previamente instalado), los servicios <code class="command">ipchains</code> e <code class="command">iptables</code> no deberÃan activarse simultÃ¡neamente. Para asegurarse que el servicio <code class="command">ipchains</code> se encuentra desactivado y configurado para que no se inicie durante el arranque, utilice los siguientes comandos:
			</div><pre class="screen">[root at miServidor ~] # service ipchains stop
[root at miServidor ~] # chkconfig --level 345 ipchains off
</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Basic_Firewall_Configuration-Saving_the_Settings.html"><strong>Anterior</strong>2.8.2.5. Guardando la ConfiguraciÃ³n</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Firewalls-Using_IPTables.html"><strong>Siguiente</strong>2.8.3. Uso de IPTables</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Basic_Firewall_Configuration-Enabling_and_Disabling_the_Firewall.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.2.2. Habilitando y Deshabilitando el Cortafuego</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Firewalls-Basic_Firewall_Configuration.html" title="2.8.2. ConfiguraciÃ³n BÃ¡sica del Cortafuego" /><link rel="prev" href="sect-Security_Guide-Firewalls-Basic_Firewall_Configuration.html" title="2.8.2. ConfiguraciÃ³n BÃ¡sica del Cortafuego" /><link rel="next" href="sect-Security_Guide-Basic_Firewall_Configuration-Trusted_Services.html" title="2.8.2.3. Servicios Confiables" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/im
 age_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Firewalls-Basic_Firewall_Configuration.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Basic_Firewall_Configuration-Trusted_Services.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Basic_Firewall_Configuration-Enabling_and_Disabling_the_Firewall">2.8.2.2. Habilitando y Deshabilitando el Cortafuego</h4></div></div></div><div class="para">
				Seleccione una de las opciones siguientes para el cortafuego:
			</div><div class="itemizedlist"><ul><li><div class="para">
						<span class="guilabel"><strong>Disabled</strong></span> â€” Deshabilitar el cortafuegos proporciona un acceso completo a su sistema y no se realiza ninguna verificaciÃ³n de seguridad. Esto debe ser seleccionado sÃ³lo si estÃ¡ ejecutando una red segura (no Internet), o necesite configurar un cortafuego personalizado utilizando la herramienta de la lÃnea de comandos iptables.
					</div><div class="warning"><h2>Warning</h2><div class="para">
							Las configuraciones del cortafuego y cualquier reglas de cortafuegos personalizadas se almacenan en el archivo <code class="filename">/etc/sysconfig/iptables</code>. Si elije <span class="guilabel"><strong>Deshabilitado</strong></span> y hace clic en <span class="guibutton"><strong>Aceptar</strong></span>, estas configuraciones y reglas del cortafuego se perderÃ¡n.
						</div></div></li><li><div class="para">
						<span class="guilabel"><strong>Habilitado</strong></span> â€” Esta opciÃ³n configura el sistema para rechazar conexiones entrantes que no son en respuestas a pedidos hechos, tales como respuestas de DNS o pedidos DHCP. Si se necesita el acceso a servicios de esta mÃ¡quina, puede elegir habilitar servicios especÃficos a travÃ©s del cortafuego.
					</div><div class="para">
						Si estÃ¡ conectando su sistema a Internet, pero no planea hacerlo funcionar como servidor, esta es la opciÃ³n mÃ¡s segura.
					</div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Firewalls-Basic_Firewall_Configuration.html"><strong>Anterior</strong>2.8.2. ConfiguraciÃ³n BÃ¡sica del Cortafuego</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Basic_Firewall_Configuration-Trusted_Services.html"><strong>Siguiente</strong>2.8.2.3. Servicios Confiables</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Basic_Firewall_Configuration-Other_Ports.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.2.4. Otros Puertos</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Firewalls-Basic_Firewall_Configuration.html" title="2.8.2. ConfiguraciÃ³n BÃ¡sica del Cortafuego" /><link rel="prev" href="sect-Security_Guide-Basic_Firewall_Configuration-Trusted_Services.html" title="2.8.2.3. Servicios Confiables" /><link rel="next" href="sect-Security_Guide-Basic_Firewall_Configuration-Saving_the_Settings.html" title="2.8.2.5. Guardando la ConfiguraciÃ³n" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product 
 Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Basic_Firewall_Configuration-Trusted_Services.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Basic_Firewall_Configuration-Saving_the_Settings.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Basic_Firewall_Configuration-Other_Ports">2.8.2.4. Otros Puertos</h4></div></div></div><div class="para">
				El <span class="application"><strong>Firewall Configuration Tool</strong></span> incluye una secciÃ³n de <span class="guilabel"><strong>Oros Puertos</strong></span> para especificar puertos IP personalizados de modo tal de considerarlos como seguros por <code class="command">iptables</code>. Por ejemplo, para permitir que protocolos IRC o de impresiÃ³n a travÃ©s de Internet(IPP, por las siglas en inglÃ©s de Internet Printing Protocol) pasen a travÃ©s del cortafuegos, aÃ±ada la siguiente lÃnea a la secciÃ³n de <span class="guilabel"><strong>Other ports</strong></span>:
			</div><div class="para">
				<code class="computeroutput">194:tcp,631:tcp</code>
			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Basic_Firewall_Configuration-Trusted_Services.html"><strong>Anterior</strong>2.8.2.3. Servicios Confiables</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Basic_Firewall_Configuration-Saving_the_Settings.html"><strong>Siguiente</strong>2.8.2.5. Guardando la ConfiguraciÃ³n</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Basic_Firewall_Configuration-Saving_the_Settings.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.2.5. Guardando la ConfiguraciÃ³n</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Firewalls-Basic_Firewall_Configuration.html" title="2.8.2. ConfiguraciÃ³n BÃ¡sica del Cortafuego" /><link rel="prev" href="sect-Security_Guide-Basic_Firewall_Configuration-Other_Ports.html" title="2.8.2.4. Otros Puertos" /><link rel="next" href="sect-Security_Guide-Basic_Firewall_Configuration-Activating_the_IPTables_Service.html" title="2.8.2.6. Activando el Servicio IPTables" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.p
 ng" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Basic_Firewall_Configuration-Other_Ports.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Basic_Firewall_Configuration-Activating_the_IPTables_Service.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Basic_Firewall_Configuration-Saving_the_Settings">2.8.2.5. Guardando la ConfiguraciÃ³n</h4></div></div></div><div class="para">
				Haga click en <span class="guibutton"><strong>OK</strong></span> para guardar los cambios y activar o desactivar el cortafuegos. Si fue seleccionado <span class="guilabel"><strong>Activar cortafuegos</strong></span>, las opciones seleccionadas serÃ¡n trasladadas a los comandos <code class="command">iptables</code> y escritos en el archivo <code class="filename">/etc/sysconfig/iptables</code>. El servicio <code class="command">iptables</code> es tambiÃ©n iniciado de modo que el cortafuegos sea activado inmediatamente luego de guardar las opciones seleccionadas. Si fue seleccionado <span class="guilabel"><strong>Disactivar cortafuegos</strong></span>, el archivo <code class="filename">/etc/sysconfig/iptables</code> es eliminado y el servicio <code class="command">iptables</code> es inmediatamente detenido.
			</div><div class="para">
				Las opciones seleccionadas son tabiÃ©n escritas al archivo <code class="filename">/etc/sysconfig/system-config-securitylevel</code> para que la configuraciÃ³n pueda restaurarse la prÃ³xima vez que se inicie la aplicaciÃ³n. No edite este archivo a mano.
			</div><div class="para">
				Aunque el cortafuegos es activado inmediatamente, el servicio <code class="command">iptables</code> no estÃ¡ configurado para que se inicie automÃ¡ticamente durante el arranque del equipo. Vea <a class="xref" href="sect-Security_Guide-Basic_Firewall_Configuration-Activating_the_IPTables_Service.html" title="2.8.2.6. Activando el Servicio IPTables">SecciÃ³nÂ 2.8.2.6, â€œActivando el Servicio IPTablesâ€</a> para obtener mÃ¡s informaciÃ³n.
			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Basic_Firewall_Configuration-Other_Ports.html"><strong>Anterior</strong>2.8.2.4. Otros Puertos</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Basic_Firewall_Configuration-Activating_the_IPTables_Service.html"><strong>Siguiente</strong>2.8.2.6. Activando el Servicio IPTables</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Basic_Firewall_Configuration-Trusted_Services.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.2.3. Servicios Confiables</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Firewalls-Basic_Firewall_Configuration.html" title="2.8.2. ConfiguraciÃ³n BÃ¡sica del Cortafuego" /><link rel="prev" href="sect-Security_Guide-Basic_Firewall_Configuration-Enabling_and_Disabling_the_Firewall.html" title="2.8.2.2. Habilitando y Deshabilitando el Cortafuego" /><link rel="next" href="sect-Security_Guide-Basic_Firewall_Configuration-Other_Ports.html" title="2.8.2.4. Otros Puertos" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/ima
 ge_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Basic_Firewall_Configuration-Enabling_and_Disabling_the_Firewall.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Basic_Firewall_Configuration-Other_Ports.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Basic_Firewall_Configuration-Trusted_Services">2.8.2.3. Servicios Confiables</h4></div></div></div><div class="para">
				Habilitando opciones en la lista de <span class="guilabel"><strong>Servicios confiables</strong></span> le permite al servicio especificado pasar a travÃ©s del cortafuego.
			</div><div class="variablelist"><dl><dt><span class="term"><span class="guilabel"><strong>WWW (HTTP)</strong></span></span></dt><dd><div class="para">
							El protocolo HTTP es utilizado por Apache (y por otros servidores Web) para ofrecer pÃ¡ginas web. Si tiene pensado hacer que su servidor web estÃ¡ disponible al pÃºblico eb general, tilde esta casilla. Esta opciÃ³n no es requerida para ver pÃ¡ginas en forma local, o para desarrollar pÃ¡ginas web. Este servicio requiere que el paquete <code class="filename">httpd</code> estÃ© disponible.
						</div><div class="para">
							Habilitando <span class="guilabel"><strong>WWW (HTTP)</strong></span> no abrirÃ¡ el puerto de HTTPS, la versiÃ³n SSL de HTTP. Si se necesita este servicio, Elija la casilla <span class="guilabel"><strong>WWW Seguro (HTTPS)</strong></span>.
						</div></dd><dt><span class="term"><span class="guilabel"><strong>FTP</strong></span></span></dt><dd><div class="para">
							El protocolo FTP se usa para transferir archivos entre mÃ¡quinas de una red. Si planea hacer su servidor FTP disponible pÃºblicamente, marque este casillero. Este servicio requiere que se instale el paquete <code class="filename">vsftpd</code>.
						</div></dd><dt><span class="term"><span class="guilabel"><strong>SSH</strong></span></span></dt><dd><div class="para">
							Secure Shell (SSH) es una suite de herramientas para loguearse en un equipo remoto y poder ejecutar comandos en Ã©l. Para permitir acceso remoto a una mÃ¡quina utilizando ssh, tilde esta casilla. Este servicio requiere que el paquete <code class="filename">openssh-server</code> se encuentre instalado.
						</div></dd><dt><span class="term"><span class="guilabel"><strong>Telnet</strong></span></span></dt><dd><div class="para">
							Telnet es un protocolo que permite loguearse en equipos remotos. Las comunicaciones a travÃ©s de Telnet no estÃ¡n encriptadas y no ofrece protecciÃ³n ante posibles espÃas que se encuentren en la red. No se recomienda permitir el acceso a travÃ©s de Telnet. Para permitirlo, tilde esta casilla. Este servicio requiere que el paquete <code class="filename">telnet-server</code> se encuentre instalado.
						</div></dd><dt><span class="term"><span class="guilabel"><strong>Correo (SMTP)</strong></span></span></dt><dd><div class="para">
							SMTP es un protocolo que permite a equipos remotos conectarse directamente con su mÃ¡quina para enviar correos electrÃ³nicos. No necesita activar este servicio si obtiene su correo electrÃ³nico a travÃ©s de su servidor ISP, utilizando POP3 o IMAP, o si utiliza una herramienta como <code class="command">fetchmail</code>. Para permitir el envÃo de correos electrÃ³nico hacia su mÃ¡quina, seleccione esta casilla. FÃjese que una configuraciÃ³n incorrecta de un servidor SMTP puede permitir que otros equipos utilicen su servidor para enviar correo basura.
						</div></dd><dt><span class="term"><span class="guilabel"><strong>NFS4</strong></span></span></dt><dd><div class="para">
							El Sistema de Archivos de Res (NFS, por las siglas en inglÃ©s de Network File System), es un protocolo para compartir archivos comÃºnmente utilizado en sistemas *NIX. La versiÃ³n 4 de este protocolo es mÃ¡s segura que sus predecesoras. Si quiere compartir archivos y directorios de su sistema con otros en red, tilde esta casilla.
						</div></dd><dt><span class="term"><span class="guilabel"><strong>Samba</strong></span></span></dt><dd><div class="para">
							Samba es una implementaciÃ³n del protocolo de red SMB de Microsoft. Si necesita compartir archivos, directorios o impresoras conectadas localmente con computadoras con Microsoft Windows, marque esta casilla.
						</div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Basic_Firewall_Configuration-Enabling_and_Disabling_the_Firewall.html"><strong>Anterior</strong>2.8.2.2. Habilitando y Deshabilitando el Cortafue...</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Basic_Firewall_Configuration-Other_Ports.html"><strong>Siguiente</strong>2.8.2.4. Otros Puertos</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Command_Options_for_IPTables-Command_Options.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.9.3.2. Command Options</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-IPTables-Command_Options_for_IPTables.html" title="2.9.3. Command Options for IPTables" /><link rel="prev" href="sect-Security_Guide-IPTables-Command_Options_for_IPTables.html" title="2.9.3. Command Options for IPTables" /><link rel="next" href="sect-Security_Guide-Command_Options_for_IPTables-IPTables_Parameter_Options.html" title="2.9.3.3. IPTables Parameter Options" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site
 " /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-IPTables-Command_Options_for_IPTables.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Command_Options_for_IPTables-IPTables_Parameter_Options.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Command_Options_for_IPTables-Command_Options">2.9.3.2. Command Options</h4></div></div></div><div class="para">
				Las opciones de comando dan instrucciones a <code class="command">iptables</code> para que realice una acciÃ³n especÃfica. Solo una opciÃ³n de comando es permitida para cada comando <code class="command">iptables</code>. Con la excepciÃ³n del comando help, todos los demÃ¡s deben ser escritos con caracteres mayÃºsculos.
			</div><div class="para">
				Los comandos de <code class="command">iptables</code> son los siguientes:
			</div><div class="itemizedlist"><ul><li><div class="para">
						<code class="option">-A</code> â€” Agregan una regla al final de la cadena especificada. A diferencia de la opciÃ³n <code class="option">-I</code> descripta mÃ¡s abajo, No toma un entero como argumento. Siempre agrega la regla al final de la cadena especificada.
					</div></li><li><div class="para">
						<code class="option">-C</code> â€” Verifica una regla determinada antes de aÃ±adirla a la cadena especificada por el usuario. Este comando puede ayudarle a construir reglas complejas de <code class="command">iptables</code> al solicitarle parÃ¡metros y opciones adicionales.
					</div></li><li><div class="para">
						<code class="option">-D <integer> | <rule></code> â€” Elimina una regla de una cadena determinada por su nÃºmero (como por ejemplo <code class="option">5</code> para la quinta regla de una cadena), o por su especificaciÃ³n. La especificaciÃ³n de la regla debe coincidir exactamente con la regla existente.
					</div></li><li><div class="para">
						<code class="option">-E</code> â€” Renombra una cadena definida por el usuario. Una cadena definida por el usuario es cualquier cadena que no sea una de las ya existentes, establecidas por defecto. (Vea mÃ¡s abajo la opciÃ³n <code class="option">-N</code> para obtener informaciÃ³n acerca de como crear cadenas definidas por el usuario). Este es un cambio de tipo estÃ©tico y no afecta la estructura de la tabla.
					</div><div class="note"><h2>Note</h2><div class="para">
							Si intenta renombrar alguna de las cadenas predeterminadas, el sistema informarÃ¡ un error de <code class="computeroutput">Coincidencia no encontrada</code>. No puede renombrar las cadenas predeterminadas.
						</div></div></li><li><div class="para">
						<code class="option">-F</code> â€” Limpia la cadena seleccionada, lo que efectivamente borra cada regla en la cadena. Si no se especifica una cadena, limpia todas las reglas de cada cadena.
					</div></li><li><div class="para">
						<code class="option">-h</code> â€” Provee una lista de estructuras de comando, asÃ como un resumen rÃ¡pido de los parÃ¡metros y opciones de los comandos.
					</div></li><li><div class="para">
						<code class="option">-I [<entero>]</code> â€” Inserta una regla en la cadena en el punto especificado por el argumento entero dado por el usuario. Si no se especifica un argumento, se inserta al comienzo de la cadena.
					</div><div class="important"><h2>Important</h2><div class="para">
							Como se mencionÃ³ arriba, el orden de las reglas en una cadena determina cuÃ¡les reglas se aplican a quÃ© paquetes. Esto es importante para recordar cuando se agreguen reglas que usen la opciÃ³n <code class="option">-A</code> o <code class="option">-I</code>.
						</div><div class="para">
							Esto es especialmente importante cuando se agregan reglas utilizando la opciÃ³n <code class="option">-I</code> con un argumento entero. Si especifica un nÃºmero existente cuando agregue una regla a una cadena, <code class="command">iptables</code> aÃ±ade la nueva regla <span class="emphasis"><em>antes</em></span> que (o sobre) la regla existente.
						</div></div></li><li><div class="para">
						<code class="option">-L</code> â€” Muestra todas las reglas en la cadena especificada luego del comando. Para listar todas las reglas de todas las cadenas en la tabla de <code class="option">filtro</code> establecida por defecto, no especifique ni una cadena ni una tabla. De lo contrario, la siguiente sintaxis deberÃa ser utilizada para listar las reglas de una cadena determinada, en una tabla determinada:
					</div><pre class="screen"><code class="computeroutput"> iptables -L <em class="replaceable"><code><nombre-de-cadena></code></em> -t <em class="replaceable"><code><nombre-de-tabla></code></em></code>
</pre><div class="para">
						Las opciones adicionales para la opciÃ³n <code class="option">-L</code> del comando, que proveen el nÃºmero de regla y permiten descripciones de reglas mÃ¡s detalladas se describen en <a class="xref" href="sect-Security_Guide-Command_Options_for_IPTables-Listing_Options.html" title="2.9.3.6. Listing Options">SecciÃ³nÂ 2.9.3.6, â€œListing Optionsâ€</a>.
					</div></li><li><div class="para">
						<code class="option">-N</code> â€” Crea una nueva cadena con un nombre dado por el usuario. El nombre debe ser Ãºnico, sino se mostrarÃ¡ un mensaje de error.
					</div></li><li><div class="para">
						<code class="option">-P</code> â€” Pone la polÃtica predeterminada para la cadena especificada, para que cuando los paquetes atraviesen toda la cadena sin encontrar una regla con la que coincidan, se los envÃa al destino especificado, sea ACCEPT o DROP.
					</div></li><li><div class="para">
						<code class="option">-R</code> â€” Reemplaza una regla en la cadena especificada. El nÃºmero de regla debe especificarse despuÃ©s del nombre de la cadena. La primera regla en una cadena corresponde a la regla nÃºmero uno.
					</div></li><li><div class="para">
						<code class="option">-X</code> â€” Borra una cadena definida por el usuario. No se puede borrar una cadena predefinida.
					</div></li><li><div class="para">
						<code class="option">-Z</code> â€” Pone los contadores de bytes y de paquetes a 0 en todas las cadenas de una tabla.
					</div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-IPTables-Command_Options_for_IPTables.html"><strong>Anterior</strong>2.9.3. Command Options for IPTables</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Command_Options_for_IPTables-IPTables_Parameter_Options.html"><strong>Siguiente</strong>2.9.3.3. IPTables Parameter Options</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Command_Options_for_IPTables-IPTables_Match_Options.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.9.3.4. IPTables Match Options</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-IPTables-Command_Options_for_IPTables.html" title="2.9.3. Command Options for IPTables" /><link rel="prev" href="sect-Security_Guide-Command_Options_for_IPTables-IPTables_Parameter_Options.html" title="2.9.3.3. IPTables Parameter Options" /><link rel="next" href="sect-Security_Guide-IPTables_Match_Options-UDP_Protocol.html" title="2.9.3.4.2. Protocolo UDP" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></
 a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Command_Options_for_IPTables-IPTables_Parameter_Options.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-IPTables_Match_Options-UDP_Protocol.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Command_Options_for_IPTables-IPTables_Match_Options">2.9.3.4. IPTables Match Options</h4></div></div></div><div class="para">
				Los diferentes protocolos de red proveen opciones especializadas de correspondencia, que pueden ser configuradas para relacionar un paquete determinado, que utilice el protocolo en cuestiÃ³n. Sin embargo, el protocolo debe ser previamente especificado en el comando <code class="command">iptables</code>. Por ejemplo, <code class="option">-p <em class="replaceable"><code><protocol-name></code></em></code> habilita opciones para el protocolo especÃfico. FÃjese que incluso puede utilizar el ID del protocolo, en lugar del nombre del protocolo. Observe los siguientes ejemplos, cada uno de los cuales tiene el mismo efecto:
			</div><pre class="screen"><code class="command"> iptables -A INPUT -p icmp --icmp-type any -j ACCEPT </code>
</pre><pre class="screen"><code class="command"> iptables -A INPUT -p 5813 --icmp-type any -j ACCEPT </code>
</pre><div class="para">
				Las definiciones de los servicios son provistas en el archivo <code class="filename">/etc/services</code>. Para una mejor lectura, es recomendable que se utilice el nombre de los servicios, en luhar de los nÃºmeros de puertos.
			</div><div class="warning"><h2>Warning</h2><div class="para">
					Asegure el archivo <code class="filename">/etc/services</code> de manera de poder evitar que sea editado por usuarios no autorizados. Si este archivo es editable, los crackers pueden utilizarlo para habilitar puertos en su equipo que de otra manera permanecerÃan cerrados. Para segurar este archivo, ingrese los siguiente comandos siendo usuario root:
				</div><pre class="screen">[root at myServer ~]# chown root.root /etc/services 
[root at myServer ~]# chmod 0644 /etc/services
[root at myServer ~]# chattr +i /etc/services
</pre><div class="para">
					Esto previene que se pueda renombrar, borrar o crear enlaces al archivo.
				</div></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h5 class="title" id="sect-Security_Guide-IPTables_Match_Options-TCP_Protocol">2.9.3.4.1. Protocolo TCP</h5></div></div></div><div class="para">
					Estas opciones de comparaciÃ³n estÃ¡n disponibles para el protocolo TCP (<code class="option">-p tcp</code>):
				</div><div class="itemizedlist"><ul><li><div class="para">
							<code class="option">--dport</code> â€” Pone el puerto destino del paquete.
						</div><div class="para">
							Para configurar esta opciÃ³n, use un nombre de servicio de red (tal como www o smtp); o un nÃºmero de puerto; o un rango de nÃºmeros de puerto.
						</div><div class="para">
							Para especificar un rango de nÃºmeros de puerto, separe los dos nÃºmeros con dos puntos (<code class="option">:</code>). Por ejemplo: <code class="option">-p tcp --dport 3000:3200</code>. El rango mÃ¡s grande aceptable es <code class="option">0:65535</code>.
						</div><div class="para">
							Use el signo de exclamaciÃ³n (<code class="option">!</code>) despuÃ©s de la opciÃ³n <code class="option">--dport</code> para que seleccione todos los paquetes que <span class="emphasis"><em>no</em></span> usen ese servicio de red o puerto.
						</div><div class="para">
							Para navegar por los nombres o alias de servicios de red y sus nÃºmeros de puerto, vea el archivo <code class="filename">/etc/services</code>.
						</div><div class="para">
							La opciÃ³n <code class="option">--destination-port</code> es sinÃ³nimo de <code class="option">--dport</code>.
						</div></li><li><div class="para">
							<code class="option">--sport</code> â€” Pone el puerto de origen del paquete y usa las mismas opciones que <code class="option">--dport</code>. La opciÃ³n <code class="option">--source-port</code> es sinÃ³nimo de <code class="option">--sport</code>.
						</div></li><li><div class="para">
							<code class="option">--syn</code> â€” Se aplica a todos los paquetes TCP diseÃ±ados para iniciar una comunicaciÃ³n, comÃºnmente llamados <em class="firstterm">paquetes SYN</em>. Cualquier paquete que lleve datos no se toca.
						</div><div class="para">
							Use un signo de exclamaciÃ³n (<code class="option">!</code>) despuÃ©s de <code class="option">--syn</code> para que seleccione los paquetes no-SYN.
						</div></li><li><div class="para">
							<code class="option">--tcp-flags <lista de chequeo de banderas> <lista de banderas puestas></code> â€” Permite paquetes TCP que tengan ciertos bits (banderas) especÃficos puestos, para que coincidan con la regla.
						</div><div class="para">
							La opciÃ³n de correspondencia <code class="option">--tcp-flags</code> acepta dos parÃ¡metros. El primero es la mÃ¡scara; una lista separada por comas de las marcas a ser examinadas en el paquete. El segundo parÃ¡metro es una lista separada por comas de las marcas que deben ser definidas en la regla con la que se pretende concordar.
						</div><div class="para">
							Las posibles banderas son:
						</div><div class="itemizedlist"><ul><li><div class="para">
									<code class="option">ACK</code>
								</div></li><li><div class="para">
									<code class="option">FIN</code>
								</div></li><li><div class="para">
									<code class="option">PSH</code>
								</div></li><li><div class="para">
									<code class="option">RST</code>
								</div></li><li><div class="para">
									<code class="option">SYN</code>
								</div></li><li><div class="para">
									<code class="option">URG</code>
								</div></li><li><div class="para">
									<code class="option">ALL</code>
								</div></li><li><div class="para">
									<code class="option">NONE</code>
								</div></li></ul></div><div class="para">
							Por ejemplo, una regla <code class="command">iptables</code> que contenga las siguientes especificaciones solo se corresponderÃ¡ con paquetes TCP que tengan definida la marca SYN, y que no tengan definidas las marcas ACK ni FIN:
						</div><div class="para">
							<code class="command">--tcp-flags ACK,FIN,SYN SYN</code>
						</div><div class="para">
							Use el signo de exclamaciÃ³n (<code class="option">!</code>) despuÃ©s de <code class="option">--tcp-flags</code> para revertir el efecto de coincidencia de la opciÃ³n.
						</div></li><li><div class="para">
							<code class="option">--tcp-option</code> â€” Intenta corresponderse con opciones especÃficas de TCP que puedan establecerse dentro de un paquete determinado. Esta opciÃ³n de correspondencia puede tambiÃ©n revertirse con el signo de exclamaciÃ³n (<code class="option">!</code>).
						</div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Command_Options_for_IPTables-IPTables_Parameter_Options.html"><strong>Anterior</strong>2.9.3.3. IPTables Parameter Options</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-IPTables_Match_Options-UDP_Protocol.html"><strong>Siguiente</strong>2.9.3.4.2. Protocolo UDP</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Command_Options_for_IPTables-IPTables_Parameter_Options.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.9.3.3. IPTables Parameter Options</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-IPTables-Command_Options_for_IPTables.html" title="2.9.3. Command Options for IPTables" /><link rel="prev" href="sect-Security_Guide-Command_Options_for_IPTables-Command_Options.html" title="2.9.3.2. Command Options" /><link rel="next" href="sect-Security_Guide-Command_Options_for_IPTables-IPTables_Match_Options.html" title="2.9.3.4. IPTables Match Options" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"
  /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Command_Options_for_IPTables-Command_Options.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Command_Options_for_IPTables-IPTables_Match_Options.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Command_Options_for_IPTables-IPTables_Parameter_Options">2.9.3.3. IPTables Parameter Options</h4></div></div></div><div class="para">
				Ciertos comandos de <code class="command">iptables</code>, incluyen aquellos para agregar, adjuntar, borrar, insertar o borrar reglas dentro de una cadena particular, que requieren varios parÃ¡metros para construir una regla de filtrado de paquetes.
			</div><div class="itemizedlist"><ul><li><div class="para">
						<code class="option">-c</code> â€” Resetea los contadores de una regla particular. Este parÃ¡metro acepta las opciones <code class="option">PKTS</code> y <code class="option">BYTES</code> para especificar quÃ© contadores resetear.
					</div></li><li><div class="para">
						<code class="option">-d</code> â€” Pone el destino por nombre, direcciÃ³n IP o red para un paquete que coincide con la regla. Cuando se especifique una red, los siguientes formatos de direcciÃ³n de IP /mÃ¡scara de red son soportados:
					</div><div class="itemizedlist"><ul><li><div class="para">
								<code class="option"><em class="replaceable"><code>N.N.N.N</code></em>/<em class="replaceable"><code>M.M.M.M</code></em></code> â€” Donde <em class="replaceable"><code>N.N.N.N</code></em> es el rango de direcciones ip y <em class="replaceable"><code>M.M.M.M</code></em> es la mÃ¡scara de red.
							</div></li><li><div class="para">
								<code class="option"><em class="replaceable"><code>N.N.N.N</code></em>/<em class="replaceable"><code>M</code></em></code> â€” Donde <em class="replaceable"><code>N.N.N.N</code></em> es el rango de direcciones IP y <em class="replaceable"><code>M</code></em> son los bits de mÃ¡scara.
							</div></li></ul></div></li><li><div class="para">
						<code class="option">-f</code> â€” Aplica esta regla sÃ³lo a paquetes fragmentados.
					</div><div class="para">
						Puede usar el signo de exclamaciÃ³n <code class="option">!</code>) despuÃ©s de este parÃ¡metro para especificar que solamente se aceptan paquetes desfragmentados.
					</div><div class="note"><h2>Note</h2><div class="para">
							La distinciÃ³n entre paquetes fragmentados y desfragmentados es deseable, sin importar que los paquetes fragmentados sean una parte estÃ¡ndar del protocolo IP.
						</div><div class="para">
							Originalmente diseÃ±ada para permitir que los paquetes IP viajen a travÃ©s de redes con marcos de diferentes tamaÃ±os, hoy en dÃa la fragmentaciÃ³n es comÃºnmente utilizada para generar ataques DoS, mediante paquetes mal formados. Tampoco sirve de mucho que IPv6 no permita en absoluto la fragmentaciÃ³n.
						</div></div></li><li><div class="para">
						<code class="option">-i</code> â€” Establece la interfaz de red entrante, como ser por ejemplo, <code class="option">eth0</code> o <code class="option">ppp0</code>. Con <code class="command">iptables</code>, este parÃ¡metro opcional solo puede ser utilizado con las cadenas de INPUT y FORWARD, cuando sean utilizadas con la tabla de <code class="option">filter</code>, y la cadena PREROUTING con las tablas <code class="option">nat</code> y <code class="option">mangle</code>.
					</div><div class="para">
						Este parÃ¡metro tambiÃ©n da soporte a todas las siguientes opciones especiales:
					</div><div class="itemizedlist"><ul><li><div class="para">
								El signo de exclamaciÃ³n (<code class="option">!</code>) â€” Revierte la directiva, significando que las interfases especificadas de excluyen de esta regla.
							</div></li><li><div class="para">
								Signo de suma (<code class="option">+</code>) â€” Un caracter comodÃn utilizado para relacionar a todas las interfases que se correspondan con una cadena determinada. Por ejemplo, el parÃ¡metro <code class="option">-i eth+</code> aplicarÃa esta regla a cualquier interfaz Ethernet, pero excluirÃa el resto de las interfases, como por ejemplo, <code class="option">ppp0</code>.
							</div></li></ul></div><div class="para">
						Si el parÃ¡metro <code class="option">-i</code> se usa pero no se especifica una interfase, entonces todas las interfases son afectadas por esta regla.
					</div></li><li><div class="para">
						<code class="option">-j</code> â€” Salta al destino especificado si un paquete coincide con una regla en particular.
					</div><div class="para">
						Los destinos estÃ¡ndares son <code class="option">ACCEPT</code>, <code class="option">DROP</code>, <code class="option">QUEUE</code>, y <code class="option">RETURN</code>.
					</div><div class="para">
						Existen tambiÃ©n a disposiciÃ³n algunas opciones extendidas, a travÃ©s de mÃ³dulos cargados por defecto con el paquete RPM <code class="command">iptables</code> de Fedora. Algunas de las acciones vÃ¡lidas de ese mÃ³dulo son <code class="option">LOG</code>, <code class="option">MARK</code>, y <code class="option">REJECT</code>, entre otras. Para obtener mayor informaciÃ³n acerca de estas y de otras acciones, consulte la pÃ¡gina man de <code class="command">iptables</code>.
					</div><div class="para">
						Esta opciÃ³n tambiÃ©n puede usarse para dirigir el paquete coincidente a una regla particular en una cadena del usuario fuera de la cadena actual, para que se le puedan aplicar otras reglas al paquete.
					</div><div class="para">
						Si no se especifica un destino, el paquete se mueve a la regla siguiente sin hacer nada. El contador de esta regla, sin embargo, se incrementa por uno.
					</div></li><li><div class="para">
						<code class="option">-o</code> â€” Establece la interfaz de red saliente para una regla. Esta opciÃ³n sÃ³lo es vÃ¡lida para las cadenas OUTPUT y FORWARD en la tabla <code class="option">filter</code>, y para la cadena POSTROUTING en las tablas <code class="option">nat</code> y <code class="option">mangle</code> tables. Este parÃ¡metro acepta las mismas opciones que el parÃ¡metro para la interfaz de red entrante (<code class="option">-i</code>).
					</div></li><li><div class="para">
						<code class="option">-p <protocol></code> â€” Establece el protocolo IP afectado por la regla. Este puede ser <code class="option">icmp</code>, <code class="option">tcp</code>, <code class="option">udp</code>, o <code class="option">all</code>, o tambiÃ©n puede ser un valor numÃ©rico, representando alguno de estos protocolos, o alguno diferente. TambiÃ©n puede utilizar cualquiera de los protocolos listados en el archivo <code class="filename">/etc/protocols</code>.
					</div><div class="para">
						El protocolo "<code class="option">all</code>" significa que esta regla se aplica a todos los protocolos soportados. Si no se lista ningÃºn protocolo con esta regla, por defecto se asume "<code class="option">all</code>".
					</div></li><li><div class="para">
						<code class="option">-s</code> â€” Pone el fuente de un paquete particular usando la misma sintaxis del parÃ¡metro de destino (<code class="option">-d</code>).
					</div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Command_Options_for_IPTables-Command_Options.html"><strong>Anterior</strong>2.9.3.2. Command Options</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Command_Options_for_IPTables-IPTables_Match_Options.html"><strong>Siguiente</strong>2.9.3.4. IPTables Match Options</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Command_Options_for_IPTables-Listing_Options.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.9.3.6. Listing Options</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-IPTables-Command_Options_for_IPTables.html" title="2.9.3. Command Options for IPTables" /><link rel="prev" href="sect-Security_Guide-Command_Options_for_IPTables-Target_Options.html" title="2.9.3.5. Target Options" /><link rel="next" href="sect-Security_Guide-IPTables-Saving_IPTables_Rules.html" title="2.9.4. Saving IPTables Rules" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://
 docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Command_Options_for_IPTables-Target_Options.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-IPTables-Saving_IPTables_Rules.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Command_Options_for_IPTables-Listing_Options">2.9.3.6. Listing Options</h4></div></div></div><div class="para">
				La lista de comandos establecida por defecto, <code class="command">iptables -L [<chain-name>]</code> provee resumen bÃ¡sico de las cadenas de tablas de filtrado establecidas por defecto. Opciones adicionales brindan mÃ¡s informaciÃ³n:
			</div><div class="itemizedlist"><ul><li><div class="para">
						<code class="option">-v</code> â€” Muestra informaciÃ³n adicional, como por ejemplo la cantidad de paquetes y los bytes que ha procesado cada cadena, el la cantidad de paquetes y los bytes que se ha correspondido con cada regla, y quÃ© interfases se aplican a una regla determinada.
					</div></li><li><div class="para">
						<code class="option">-x</code> â€” Expande los nÃºmeros a sus valores exactos. En un sistema activo, el nÃºmero de los paquetes y la cantidad de bytes procesados por una cadena o regla determinada puede estar abreviado en <code class="computeroutput">Kilobytes</code>, <code class="computeroutput">Megabytes</code> (Megabytes) o <code class="computeroutput">Gigabytes</code>. Esta opciÃ³n obliga a ser mostrado el nÃºmero entero.
					</div></li><li><div class="para">
						<code class="option">-n</code> â€” Muestra las direcciones IP y los nÃºmeros de puerto en su formato numÃ©rico, en vez del formato predeterminado de nombre de equipo y nombre de servicio.
					</div></li><li><div class="para">
						<code class="option">--line-numbers</code> â€” Muestra las reglas en cada cadena junto a su orden numÃ©rico en dicha cadena. Esta opciÃ³n es Ãºtil si se intenta eliminar una regla especÃfica de una cadena, o para saber dÃ³nde insertar una regla dentro de una cadena.
					</div></li><li><div class="para">
						<code class="option">-t <nombre-de-tabla></code> â€” Especifica el nombre de una tabla. Si se omite, se usa filter como nombre de tabla.
					</div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Command_Options_for_IPTables-Target_Options.html"><strong>Anterior</strong>2.9.3.5. Target Options</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-IPTables-Saving_IPTables_Rules.html"><strong>Siguiente</strong>2.9.4. Saving IPTables Rules</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Command_Options_for_IPTables-Target_Options.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.9.3.5. Target Options</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-IPTables-Command_Options_for_IPTables.html" title="2.9.3. Command Options for IPTables" /><link rel="prev" href="sect-Security_Guide-IPTables_Match_Options-Additional_Match_Option_Modules.html" title="2.9.3.4.4. Additional Match Option Modules" /><link rel="next" href="sect-Security_Guide-Command_Options_for_IPTables-Listing_Options.html" title="2.9.3.6. Listing Options" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Sit
 e" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-IPTables_Match_Options-Additional_Match_Option_Modules.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Command_Options_for_IPTables-Listing_Options.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Command_Options_for_IPTables-Target_Options">2.9.3.5. Target Options</h4></div></div></div><div class="para">
				Cuando un paquete concuerde con una regla en particular, la regla puede dirigir el paquete hacia un nÃºmero de destinos diferentes determinados por la acciÃ³n apropiada. Cada cadena tiene un objetivo establecido por defecto, que serÃ¡ utilizado si ninguna de las reglas en esa cadena concuerdan con un paquete, o si ninguna de las reglas que concuerdan con el paquete especifica un destino.
			</div><div class="para">
				The following are the standard targets:
			</div><div class="itemizedlist"><ul><li><div class="para">
						<code class="option"><em class="replaceable"><code><user-defined-chain></code></em></code> â€” A user-defined chain within the table. User-defined chain names must be unique. This target passes the packet to the specified chain.
					</div></li><li><div class="para">
						<code class="option">ACCEPT</code> â€” Permite pasar al paquete a su destino o a otra cadena.
					</div></li><li><div class="para">
						<code class="option">DROP</code> â€” Descarta el paquete sin responder. El sistema que mandÃ³ el paquete no es notificado de la falla.
					</div></li><li><div class="para">
						<code class="option">QUEUE</code> â€” El paquete es encolado para su manejo por una aplicaciÃ³n en el espacio del usuario.
					</div></li><li><div class="para">
						<code class="option">RETURN</code> â€” Detiene el chequeo del paquete contra las reglas restantes de la cadena. Si el paquete con un destino <code class="option">RETURN</code> coincide con una regla en una cadena llamada por otra cadena,El paquete es devuelto a la primera cadena y continÃºa el chequeo donde quedÃ³ antes de saltar. Si la regla <code class="option">RETURN</code> se usa en una cadena predefinida y el paquete no se puede mover a una cadena previa, se usa el destino predeterminado para la cadena.
					</div></li></ul></div><div class="para">
				In addition, extensions are available which allow other targets to be specified. These extensions are called target modules or match option modules and most only apply to specific tables and situations. Refer to <a class="xref" href="sect-Security_Guide-IPTables_Match_Options-Additional_Match_Option_Modules.html" title="2.9.3.4.4. Additional Match Option Modules">SecciÃ³nÂ 2.9.3.4.4, â€œAdditional Match Option Modulesâ€</a> for more information about match option modules.
			</div><div class="para">
				Many extended target modules exist, most of which only apply to specific tables or situations. Some of the most popular target modules included by default in Fedora are:
			</div><div class="itemizedlist"><ul><li><div class="para">
						<code class="option">LOG</code> â€” Registra todos los paquetes que se correspondan con esta regla. Debido a que los paquetes son registrados por el kernel, el archivo <code class="filename">/etc/syslog.conf</code> determina donde son escritas estas entradas de registro. Por defecto, son ubicadas en el archivo <code class="filename">/var/log/messages</code>.
					</div><div class="para">
						Hay opciones adicionales que se pueden usar despuÃ©s del destino <code class="option">LOG</code> para especificar la forma en que se realiza el log:
					</div><div class="itemizedlist"><ul><li><div class="para">
								<code class="option">--log-level</code> â€” Pone la prioridad de registrado del evento. Vaya a la pÃ¡gina man de <code class="filename">syslog.conf</code> para una lista de los niveles de prioridad.
							</div></li><li><div class="para">
								<code class="option">--log-ip-options</code> â€” Registra todas las opciones puestas en la cabecera de un paquete IP.
							</div></li><li><div class="para">
								<code class="option">--log-prefix</code> â€” Pone una cadena de hasta 29 caracteres antes de la lÃnea de registro cuando se escribe. Esto es Ãºtil cuando se escribe filtros syslog para usar junto con el registrado de paquetes.
							</div><div class="note"><h2>Note</h2><div class="para">
									Debido a una cuestiÃ³n con esta opciÃ³n, se debe agregar un espacio al final del valor <em class="replaceable"><code>log-prefix</code></em>.
								</div></div></li><li><div class="para">
								<code class="option">--log-tcp-options</code> â€” Registra todas las opciones puestas en la cabecera de un paquete TCP.
							</div></li><li><div class="para">
								<code class="option">--log-tcp-sequence</code> â€” Escribe el nÃºmero de secuencia de un paquete en el log.
							</div></li></ul></div></li><li><div class="para">
						<code class="option">REJECT</code> â€” EnvÃa un paquete de error como respuesta al sistema remoto y descarta el paquete.
					</div><div class="para">
						The <code class="option">REJECT</code> target accepts <code class="option">--reject-with <em class="replaceable"><code><type></code></em></code> (where <em class="replaceable"><code><type></code></em> is the rejection type) allowing more detailed information to be returned with the error packet. The message <code class="computeroutput">port-unreachable</code> is the default error type given if no other option is used. Refer to the <code class="command">iptables</code> man page for a full list of <code class="option"><em class="replaceable"><code><type></code></em></code> options.
					</div></li></ul></div><div class="para">
				Other target extensions, including several that are useful for IP masquerading using the <code class="option">nat</code> table, or with packet alteration using the <code class="option">mangle</code> table, can be found in the <code class="command">iptables</code> man page.
			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-IPTables_Match_Options-Additional_Match_Option_Modules.html"><strong>Anterior</strong>2.9.3.4.4. Additional Match Option Modules</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Command_Options_for_IPTables-Listing_Options.html"><strong>Siguiente</strong>2.9.3.6. Listing Options</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Common_Exploits_and_Attacks.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.4. Ataques y Aprovechadas ComÃºnes</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="chap-Security_Guide-Security_Overview.html" title="CapÃtulo 1. Security Overview" /><link rel="prev" href="sect-Security_Guide-Threats_to_Workstation_and_Home_PC_Security-Vulnerable_Client_Applications.html" title="1.3.4.2. Vulnerable Client Applications" /><link rel="next" href="sect-Security_Guide-Security_Updates.html" title="1.5. Actualizaciones de Seguridad" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a cl
 ass="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Threats_to_Workstation_and_Home_PC_Security-Vulnerable_Client_Applications.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Security_Updates.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h2 class="title" id="sect-Security_Guide-Common_Exploits_and_Attacks">1.4. Ataques y Aprovechadas ComÃºnes</h2></div></div></div><div class="para">
		<a class="xref" href="sect-Security_Guide-Common_Exploits_and_Attacks.html#tabl-Security_Guide-Common_Exploits_and_Attacks-Common_Exploits" title="Tabla 1.1. Ataques ComÃºnes">TablaÂ 1.1, â€œAtaques ComÃºnesâ€</a> detalles acerca de los puntos explotados y de ingreso mÃ¡s utilizados por intrusos, que pretenden acceder a los recursos de diferentes redes. La clave para defender estos puntos son las explicaciones acerca de cÃ³mo se desarrollan, y cÃ³mo los administradores pueden salvaguardar adecuadamente sus redes contra tales ataques.
	</div><div class="table" id="tabl-Security_Guide-Common_Exploits_and_Attacks-Common_Exploits"><div class="table-contents"><table summary="Ataques ComÃºnes" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>
						Aprovechadas
					</th><th>
						Description
					</th><th>
						Notas
					</th></tr></thead><tbody><tr><td>
						ContraseÃ±as Nulas o Predeterminadas
					</td><td>
						Leaving administrative passwords blank or using a default password set by the product vendor. This is most common in hardware such as routers and firewalls, though some services that run on Linux can contain default administrator passwords (though Fedora 11 does not ship with them).
					</td><td>
						<table class="simplelist" border="0" summary="Simple list"><tr><td>Asociados comÃºnmente a equipos de red como ruteadores, cortafuegos, VPNs y aparatos de almacenamiento conectados a la red (NAS). </td></tr><tr><td>Common in many legacy operating systems, especially those that bundle services (such as UNIX and Windows.) </td></tr><tr><td>Administrators sometimes create privileged user accounts in a rush and leave the password null, creating a perfect entry point for malicious users who discover the account. </td></tr></table>
					</td></tr><tr><td>
						Claves Compartidas Predeterminadas
					</td><td>
						Los servicios de seguridad algunas veces empaquetan claves de seguridad establecidas por defecto, ya sea para su desarrollo, o para comprobar su desempeÃ±o. Si estas claves se mantienen inalteradas y se colocan en un entorno de producciÃ³n en Internet <span class="emphasis"><em>todos</em></span> los usuarios con las misma claves establecidas por defecto tendrÃ¡n acceso a ese recurso de clave compartida, y a cualquier tipo de informaciÃ³n que en Ã©l se guarde.
					</td><td>
						<table class="simplelist" border="0" summary="Simple list"><tr><td>Los puntos de acceso inalÃ¡mbricos y aparatos servidores seguros preconfigurados mÃ¡s comunes. </td></tr></table>
					</td></tr><tr><td>
						ImitaciÃ³n de IP
					</td><td>
						Una mÃ¡quina remota actÃºa como un nodo en su red local, busca vulnerabilidades con sus servidores e instala un programa de puerta trasera o troyano para ganar el control de los recursos de la red.
					</td><td>
						<table class="simplelist" border="0" summary="Simple list"><tr><td>Spoofing is quite difficult as it involves the attacker predicting TCP/IP sequence numbers to coordinate a connection to target systems, but several tools are available to assist crackers in performing such a vulnerability. </td></tr><tr><td>Depends on target system running services (such as <code class="command">rsh</code>, <code class="command">telnet</code>, FTP and others) that use <em class="firstterm">source-based</em> authentication techniques, which are not recommended when compared to PKI or other forms of encrypted authentication used in <code class="command">ssh</code> or SSL/TLS. </td></tr></table>
					</td></tr><tr><td>
						Escuchas
					</td><td>
						La escucha se realiza para la colecciÃ³n de datos que pasa entre dos nodos activos en una red.
					</td><td>
						<table class="simplelist" border="0" summary="Simple list"><tr><td>Este tipo de ataque funciona principalmente con protocolos de transmisiÃ³n de texto plano tales como las transferencias Telnet, FTP y HTTP. </td></tr><tr><td>El atacante remoto debe tener acceso a un sistema comprometido en una LAN para poder realizar el ataque; usualmente el atacante usÃ³ un ataque activo (tal como la suplantaciÃ³n de IP o la del hombre en el medio) para comprometer un sistema en la LAN. </td></tr><tr><td>Las medidas preventivas incluyen servicios con cambio de claves criptogrÃ¡ficas, contraseÃ±as de un solo uso, o autenticaciÃ³n encriptada para prevenir la adivinaciÃ³n de contraseÃ±as; una fuerte encriptaciÃ³n durante la transmisiÃ³n tambiÃ©n es recomendada. </td></tr></table>
					</td></tr><tr><td>
						Vulnerabilidades de Servicios
					</td><td>
						Un atacante encuentra una brecha o hueco en un servicio que corre a travÃ©s de innternet; a travÃ©s de esta vulnerabilidad, el atacante compromete el sistema entero y cualquier dato que pueda contener, y puede posiblemente comprometer otros sistemas en la red.
					</td><td>
						<table class="simplelist" border="0" summary="Simple list"><tr><td>HTTP-based services such as CGI are vulnerable to remote command execution and even interactive shell access. Even if the HTTP service runs as a non-privileged user such as "nobody", information such as configuration files and network maps can be read, or the attacker can start a denial of service attack which drains system resources or renders it unavailable to other users. </td></tr><tr><td>Los servicios algunas veces pueden presentar vulnerabilidades que no son visibles a lo largo de los procesos de desarrollo o de prueba. Estas vulnerabilidades pueden darle a un atacante un control administrativo total, como es el caso de un <em class="firstterm">desbordamientos del bÃºfer</em>: los atacantes destruyen un sistema utilzando valores arbitrarios que agotan la memoria del bÃºfer de una determinada aplicaciÃ³n, y obteniendo asÃ una consola desde la cual poder ejecutar comandos. </td></tr><tr><td>Los admi
 nistradores se deben asegurar que los servicios no corren como el usuario root, y deben vigilar los parches y actualizaciones de errata de las aplicaciones de vendedores u organizaciones de seguridad como CERT y CVE. </td></tr></table>
					</td></tr><tr><td>
						Vulnerabilidades de Aplicaciones
					</td><td>
						Los atacantes encuentran fallas en las aplicaciones de un equipo de escritorio o de una estaciÃ³n de trabajo (como ser por ejemplo un cliente de correo electrÃ³nico), y ejecutan un cÃ³digo cualquiera, colocan caballos trojanos para futuros daÃ±os, o simplemente destruyen el sistema. Pueden ocurrir futuras catÃ¡strofes si la estaciÃ³n de trabajo vulnerada posee privilegios administrativos sobre el resto de la red.
					</td><td>
						<table class="simplelist" border="0" summary="Simple list"><tr><td>Las estaciones de trabajo y los equipos personales son ideales para ser vulnerados dado que sus usuarios no tienen ni la experiencia ni el conocimiento para prevenir o detectar irregularidades. Es de suma importancia informar a los individuos del riesgo que corren cada vez que instalan software no autorizado, o cuando abren archivos adjuntos de correos electrÃ³nicos no solicitados. </td></tr><tr><td>Pueden ser implementados "salvavidas" tales como configurar al cliente de correo electrÃ³nico que se estÃ© utilizando de modo tal que no abra ni ejecute archivos adjuntos en forma automÃ¡tica. AdemÃ¡s, la actualizaciÃ³n automÃ¡tica de la estaciÃ³n de trabajo a travÃ©s de Red Hat Network o mediante algÃºn otro servicio de gerenciamiento de sistemas, es una forma de aliviar la tarea de las descargas de seguridad de tipo multi usuario. </td></tr></table>
					</td></tr><tr><td>
						Ataques de NegaciÃ³n de Servicio (DoS)
					</td><td>
						Un atacante, o un grupo de atacantes coordinados contra la red o los recursos de red de alguna organizaciÃ³n, enviando paquetes no autorizados al equipo elegido (ya sea un servidor, un enrutador o una estaciÃ³n de trabajo). Esto obliga al recurso atacado a quedar inhabilitado para ser utilizado por los usuarios legÃtimos.
					</td><td>
						<table class="simplelist" border="0" summary="Simple list"><tr><td>El caso DoS mÃ¡s informado en los Estados Unidos ocurriÃ³ en el aÃ±o 2000. Diferentes sitios comerciales y gubernamentales con alta densidad de trÃ¡fico quedaron incapacitados por un ataque coordinado de flujo de ping, utilizando diversos sistemas con conexiones de banda ancha previamente vulnerados, que actuaban como <em class="firstterm">zombies</em>, o que redireccionaban nodos de transmisiÃ³n. </td></tr><tr><td>Los paquetes fuentes son usualmente moldeados (asÃ como reenviados), investigando sobre la verdadera fuente del ataque. </td></tr><tr><td>Advances in ingress filtering (IETF rfc2267) using <code class="command">iptables</code> and Network Intrusion Detection Systems such as <code class="command">snort</code> assist administrators in tracking down and preventing distributed DoS attacks. </td></tr></table>
					</td></tr></tbody></table></div><h6>Tabla 1.1. Ataques ComÃºnes</h6></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Threats_to_Workstation_and_Home_PC_Security-Vulnerable_Client_Applications.html"><strong>Anterior</strong>1.3.4.2. Vulnerable Client Applications</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Security_Updates.html"><strong>Siguiente</strong>1.5. Actualizaciones de Seguridad</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Installation-Instructions.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.8.2. Step-by-Step Installation Instructions</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives.html" title="3.8. 7-Zip Encrypted Archives" /><link rel="prev" href="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives.html" title="3.8. 7-Zip Encrypted Archives" /><link rel="next" href="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Usage_Instructions.html" title="3.8.3. Step-by-Step Usage Instructions" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Produ
 ct Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Usage_Instructions.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Installation-Instructions">3.8.2. Step-by-Step Installation Instructions</h3></div></div></div><div class="itemizedlist"><ul><li><div class="para">
					Open a Terminal: <code class="code">Click ''Applications'' -> ''System Tools'' -> ''Terminal''</code>
				</div></li><li><div class="para">
					Install 7-Zip with sudo access: <code class="code">sudo yum install p7zip</code>
				</div></li><li><div class="para">
					Close the Terminal: <code class="code">exit</code>
				</div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives.html"><strong>Anterior</strong>3.8. 7-Zip Encrypted Archives</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Usage_Instructions.html"><strong>Siguiente</strong>3.8.3. Step-by-Step Usage Instructions</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Things_of_note.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.8.4. Things of note</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives.html" title="3.8. 7-Zip Encrypted Archives" /><link rel="prev" href="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Usage_Instructions.html" title="3.8.3. Step-by-Step Usage Instructions" /><link rel="next" href="sect-Security_Guide-Encryption-Using_GPG.html" title="3.9. Using GNU Privacy Guard (GnuPG)" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" 
 href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Usage_Instructions.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-Using_GPG.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Things_of_note">3.8.4. Things of note</h3></div></div></div><div class="para">
			7-Zip is not shipped by default with Microsoft Windows or Mac OS X. If you need to use your 7-Zip files on those platforms you will need to install the appropriate version of 7-Zip on those computers. See the 7-Zip <a href="http://www.7-zip.org/download.html">download page</a>.
		</div><div class="para">
			GNOME's File Roller application will recognize your .7z files and attempt to open them, but it will fail with the error "''An error occurred while loading the archive.''" when it attempts to do so. This is because File Roller does not currently support the extraction of encrypted 7-Zip files. A bug report ([http://bugzilla.gnome.org/show_bug.cgi?id=490732 Gnome Bug 490732]) has been submitted.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Usage_Instructions.html"><strong>Anterior</strong>3.8.3. Step-by-Step Usage Instructions</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-Using_GPG.html"><strong>Siguiente</strong>3.9. Using GNU Privacy Guard (GnuPG)</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Usage_Instructions.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.8.3. Step-by-Step Usage Instructions</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives.html" title="3.8. 7-Zip Encrypted Archives" /><link rel="prev" href="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Installation-Instructions.html" title="3.8.2. Step-by-Step Installation Instructions" /><link rel="next" href="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Things_of_note.html" title="3.8.4. Things of note" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.p
 ng" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Installation-Instructions.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Things_of_note.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Usage_Instructions">3.8.3. Step-by-Step Usage Instructions</h3></div></div></div><div class="para">
			By following these instructions you are going to compress and encrypt your "Documents" directory. Your original "Documents" directory will remain unaltered. This technique can be applied to any directory or file you have access to on the filesystem.
		</div><div class="itemizedlist"><ul><li><div class="para">
					Open a Terminal:<code class="code">Click ''Applications'' -> ''System Tools'' -> ''Terminal''</code>
				</div></li><li><div class="para">
					Compress and Encrypt: (enter a password when prompted) <code class="code">7za a -mhe=on -ms=on -p Documents.7z Documents/</code>
				</div></li></ul></div><div class="para">
			The "Documents" directory is now compressed and encrypted. The following instructions will move the encrypted archive somewhere new and then extract it.
		</div><div class="itemizedlist"><ul><li><div class="para">
					Create a new directory: <code class="code">mkdir newplace</code>
				</div></li><li><div class="para">
					Move the encrypted file: <code class="code">mv Documents.7z newplace</code>
				</div></li><li><div class="para">
					Go to the new directory: <code class="code">cd newplace</code>
				</div></li><li><div class="para">
					Extract the file: (enter the password when prompted) <code class="code">7za x Documents.7z</code>
				</div></li></ul></div><div class="para">
			The archive is now extracted into the new location. The following instructions will clean up all the prior steps and restore your computer to its previous state.
		</div><div class="itemizedlist"><ul><li><div class="para">
					Go up a directory: <code class="code">cd ..</code>
				</div></li><li><div class="para">
					Delete the test archive and test extraction: <code class="code">rm -r newplace</code>
				</div></li><li><div class="para">
					Close the Terminal: <code class="code">exit</code>
				</div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Installation-Instructions.html"><strong>Anterior</strong>3.8.2. Step-by-Step Installation Instructions</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Things_of_note.html"><strong>Siguiente</strong>3.8.4. Things of note</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.8. 7-Zip Encrypted Archives</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="chap-Security_Guide-Encryption.html" title="CapÃtulo 3. Encryption" /><link rel="prev" href="sect-Security_Guide-LUKS_Disk_Encryption-Links_of_Interest.html" title="3.7.5. Links of Interest" /><link rel="next" href="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Installation-Instructions.html" title="3.8.2. Step-by-Step Installation Instructions" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" hre
 f="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-LUKS_Disk_Encryption-Links_of_Interest.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Installation-Instructions.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h2 class="title" id="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives">3.8. 7-Zip Encrypted Archives</h2></div></div></div><div class="para">
		<a href="http://www.7-zip.org/">7-Zip</a> is a cross-platform, next generation, file compression tool that can also use strong encryption (AES-256) to protect the contents of the archive. This is extremely useful when you need to move data between multiple computers that use varying operating systems (i.e. Linux at home, Windows at work) and you want a portable encryption solution.
	</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Installation">3.8.1. 7-Zip Installation in Fedora</h3></div></div></div><div class="para">
			7-Zip is not a base package in Fedora, but it is available in the software repository. Once installed, the package will update alongside the rest of the software on the computer with no special attention necessary.
		</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-LUKS_Disk_Encryption-Links_of_Interest.html"><strong>Anterior</strong>3.7.5. Links of Interest</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Installation-Instructions.html"><strong>Siguiente</strong>3.8.2. Step-by-Step Installation Instructions</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Encryption-Protecting_Data_at_Rest-Full_Disk_Encryption.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.2. EncriptaciÃ³n Completa de Disco</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="chap-Security_Guide-Encryption.html" title="CapÃtulo 3. Encryption" /><link rel="prev" href="chap-Security_Guide-Encryption.html" title="CapÃtulo 3. Encryption" /><link rel="next" href="Security_Guide-Encryption-Protecting_Data_at_Rest-File_Based_Encryption.html" title="3.3. EncriptaciÃ³n Basada en Archivo" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img sr
 c="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security_Guide-Encryption.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="Security_Guide-Encryption-Protecting_Data_at_Rest-File_Based_Encryption.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h2 class="title" id="sect-Security_Guide-Encryption-Protecting_Data_at_Rest-Full_Disk_Encryption">3.2. EncriptaciÃ³n Completa de Disco</h2></div></div></div><div class="para">
			Encriptar todo un disco, o toda una particiÃ³n, es una de las mejores maneras de proteger sus datos. De esta manera no solo se protege a cada uno de los archivos, sino que tambiÃ©n se protege al almaceniamiento temporal, que puede llegar a contener partes de estos archivos. Al encriptar el disco entero, y al ser todos sus archivos protegidos, no tendrÃ¡ que preocuparse acerca de la elecciÃ³n sobre quÃ© archivos quiere proteger, y dejar abierta la posibilidad de olvidarse de alguno.
		</div><div class="para">
			Fedora 9, and later, natively supports LUKS Encryption. LUKS will bulk encrypt your hard drive partitions so that while your computer is off your data is protected. This will also protect your computer from attackers attempting to use single-user-mode to login to your computer or otherwise gain access.
		</div><div class="para">
			Las herramientas de encriptado total del diso rÃgido, como LUKS, solo protegen sus datos cuando su computadora se encuentra apagada. Una vez que la computadora se encienda, y LUKS haya decriptado el disco, los archivos en ese disco quedarÃ¡n disponibles para cualquiera que pueda acceder normalmente a ellos. Para proteger sus archivos cuando su computadora estÃ© encendida, utilice la herramienta de encriptado total del disco combinada con alguna otra, como ser por ejemplo, el encriptado de archivos. Recuerde tambiÃ©n bloquear su computadora siempre que se encuentre lejos de ella. Una frase de acceso protegiendo el salvapantallas, establecida para que se active a los pocos minutos de inactividad del equipo, es una buena forma de mantener a los intrusos alejados de Ã©l.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security_Guide-Encryption.html"><strong>Anterior</strong>CapÃtulo 3. Encryption</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="Security_Guide-Encryption-Protecting_Data_at_Rest-File_Based_Encryption.html"><strong>Siguiente</strong>3.3. EncriptaciÃ³n Basada en Archivo</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Encryption-Using_GPG-About_Public_Key_Encryption.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.9.4. About Public Key Encryption</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Encryption-Using_GPG.html" title="3.9. Using GNU Privacy Guard (GnuPG)" /><link rel="prev" href="sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE.html" title="3.9.3. Creating GPG Keys Using the Command Line" /><link rel="next" href="chap-Security_Guide-General_Principles_of_Information_Security.html" title="CapÃtulo 4. Principios Generales sobre la Seguridad de la InformaciÃ³n" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/ima
 ges/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="chap-Security_Guide-General_Principles_of_Information_Security.html"><strong>Siguiente</strong></a></li></ul><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">
					<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><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE.html"><strong>Anterior</strong>3.9.3. Creating GPG Keys Using the Command Line</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="chap-Security_Guide-General_Principles_of_Information_Security.html"><strong>Siguiente</strong>CapÃtulo 4. Principios Generales sobre la Segurid...</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.9.3. Creating GPG Keys Using the Command Line</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Encryption-Using_GPG.html" title="3.9. Using GNU Privacy Guard (GnuPG)" /><link rel="prev" href="sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE1.html" title="3.9.2. Creating GPG Keys in KDE" /><link rel="next" href="sect-Security_Guide-Encryption-Using_GPG-About_Public_Key_Encryption.html" title="3.9.4. About Public Key Encryption" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product 
 Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE1.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-Using_GPG-About_Public_Key_Encryption.html"><strong>Siguiente</strong></a></li></ul><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-Creating_GPG_Keys_in_KDE">3.9.3. Creating GPG Keys Using the Command Line</h3></div></div></div><div class="para">
			Use the following shell command: <code class="code">gpg --gen-key</code>
		</div><div class="para">
			This command generates a key pair that consists of a public and a private key. Other people use your public key to authenticate and/or decrypt your communications. Distribute your public key as widely as possible, especially to people who you know will want to receive authentic communications from you, such as a mailing list. The Fedora Documentation Project, for example, asks participants to include a GPG public key in their self-introduction.
		</div><div class="para">
			A series of prompts directs you through the process. Press the <code class="code">Enter</code> key to assign a default value if desired. The first prompt asks you to select what kind of key you prefer:
		</div><div class="para">
			Please select what kind of key you want: (1) DSA and ElGamal (default) (2) DSA (sign only) (4) RSA (sign only) Your selection? In almost all cases, the default is the correct choice. A DSA/ElGamal key allows you not only to sign communications, but also to encrypt files.
		</div><div class="para">
			Next, choose the key size: minimum keysize is 768 bits default keysize is 1024 bits highest suggested keysize is 2048 bits What keysize do you want? (1024) Again, the default is sufficient for almost all users, and represents an ''extremely'' strong level of security.
		</div><div class="para">
			Next, choose when the key will expire. It is a good idea to choose an expiration date instead of using the default, which is ''none.'' If, for example, the email address on the key becomes invalid, an expiration date will remind others to stop using that public key.
		</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)
		</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.)
		</div><div class="para">
			Before the <code class="code">gpg</code>code > 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 > to finish the process.
		</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.
		</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.
		</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.")
		</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.
		</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) <jqdoe at example.com>
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>
		</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><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE1.html"><strong>Anterior</strong>3.9.2. Creating GPG Keys in KDE</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-Using_GPG-About_Public_Key_Encryption.html"><strong>Siguiente</strong>3.9.4. About Public Key Encryption</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE1.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.9.2. Creating GPG Keys in KDE</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Encryption-Using_GPG.html" title="3.9. Using GNU Privacy Guard (GnuPG)" /><link rel="prev" href="sect-Security_Guide-Encryption-Using_GPG.html" title="3.9. Using GNU Privacy Guard (GnuPG)" /><link rel="next" href="sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE.html" title="3.9.3. Creating GPG Keys Using the Command Line" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right
 " href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Encryption-Using_GPG.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE.html"><strong>Siguiente</strong></a></li></ul><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-Creating_GPG_Keys_in_KDE1">3.9.2. Creating GPG Keys in KDE</h3></div></div></div><div class="para">
			Start the KGpg program from the main menu by selecting Applications > Utilities > Encryption Tool. If you have never used KGpg before, the program walks you through the process of creating your own GPG keypair. A dialog box appears prompting you to create a new key pair. Enter your name, email address, and an optional comment. You can also choose an expiration time for your key, as well as the key strength (number of bits) and algorithms. The next dialog box prompts you for your passphrase. At this point, your key appears in the main <code class="code">KGpg</code> window.
		</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 class="para">
			To find your GPG key ID, look in the ''Key ID'' column next to the newly created key. In most cases, if you are asked for the key ID, you should prepend "0x" to the key ID, as in "0x6789ABCD". You should make a backup of your private key and store it somewhere secure.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Encryption-Using_GPG.html"><strong>Anterior</strong>3.9. Using GNU Privacy Guard (GnuPG)</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE.html"><strong>Siguiente</strong>3.9.3. Creating GPG Keys Using the Command Line</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Encryption-Using_GPG.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.9. Using GNU Privacy Guard (GnuPG)</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="chap-Security_Guide-Encryption.html" title="CapÃtulo 3. Encryption" /><link rel="prev" href="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Things_of_note.html" title="3.8.4. Things of note" /><link rel="next" href="sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE1.html" title="3.9.2. Creating GPG Keys in KDE" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://doc
 s.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Things_of_note.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE1.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h2 class="title" id="sect-Security_Guide-Encryption-Using_GPG">3.9. Using GNU Privacy Guard (GnuPG)</h2></div></div></div><div class="para">
		GPG is used to identify yourself and authenticate your communications, including those with people you don't know. GPG allows anyone reading a GPG-signed email to verify its authenticity. In other words, GPG allows someone to be reasonably certain that communications signed by you actually are from you. GPG is useful because it helps prevent third parties from altering code or intercepting conversations and altering the message.
	</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-Keys_in_GNOME">3.9.1. Creating GPG Keys in GNOME</h3></div></div></div><div class="para">
			Install the Seahorse utility, which makes GPG key management easier. From the main menu, select <code class="code">System > Administration > Add/Remove Software</code> and wait for PackageKit to start. Enter <code class="code">Seahorse</code> into the text box and select the Find. Select the checkbox next to the ''seahorse'' package and select ''Apply'' to add the software. You can also install <code class="code">Seahorse</code> at the command line with the command <code class="code">su -c "yum install seahorse"</code>.
		</div><div class="para">
			To create a key, from the ''Applications > Accessories'' menu select ''Passwords and Encryption Keys'', which starts the application <code class="code">Seahorse</code>. From the ''Key'' menu select ''Create New Key...'' then ''PGP Key'' then click ''Continue''. Type your full name, email address, and an optional comment describing who are you (e.g.: John C. Smith, jsmith at example.com, The Man). Click ''Create''. A dialog is displayed asking for a passphrase for the key. Choose a strong passphrase but also easy to remember. Click ''OK'' and the key is created.
		</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 class="para">
			To find your GPG key ID, look in the ''Key ID'' column next to the newly created key. In most cases, if you are asked for the key ID, you should prepend "0x" to the key ID, as in "0x6789ABCD". You should make a backup of your private key and store it somewhere secure.
		</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Things_of_note.html"><strong>Anterior</strong>3.8.4. Things of note</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE1.html"><strong>Siguiente</strong>3.9.2. Creating GPG Keys in KDE</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Evaluating_the_Tools-Anticipating_Your_Future_Needs.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.2.3.5. Anticipando sus Necesidades Futuras</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Vulnerability_Assessment-Evaluating_the_Tools.html" title="1.2.3. Herramientas de EvaluaciÃ³n" /><link rel="prev" href="sect-Security_Guide-Evaluating_the_Tools-VLAD_the_Scanner.html" title="1.2.3.4. VLAD the Scanner" /><link rel="next" href="sect-Security_Guide-Attackers_and_Vulnerabilities.html" title="1.3. Attackers and Vulnerabilities" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a
  class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Evaluating_the_Tools-VLAD_the_Scanner.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Attackers_and_Vulnerabilities.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Evaluating_the_Tools-Anticipating_Your_Future_Needs">1.2.3.5. Anticipando sus Necesidades Futuras</h4></div></div></div><div class="para">
				Depending upon your target and resources, there are many tools available. There are tools for wireless networks, Novell networks, Windows systems, Linux systems, and more. Another essential part of performing assessments may include reviewing physical security, personnel screening, or voice/PBX network assessment. New concepts, such as <em class="firstterm">war walking</em>, which involves scanning the perimeter of your enterprise's physical structures for wireless network vulnerabilities, are some emerging concepts that you can investigate and, if needed, incorporate into your assessments. Imagination and exposure are the only limits of planning and conducting vulnerability assessments.
			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Evaluating_the_Tools-VLAD_the_Scanner.html"><strong>Anterior</strong>1.2.3.4. VLAD the Scanner</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Attackers_and_Vulnerabilities.html"><strong>Siguiente</strong>1.3. Attackers and Vulnerabilities</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Evaluating_the_Tools-Nessus.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.2.3.2. Nessus</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Vulnerability_Assessment-Evaluating_the_Tools.html" title="1.2.3. Herramientas de EvaluaciÃ³n" /><link rel="prev" href="sect-Security_Guide-Vulnerability_Assessment-Evaluating_the_Tools.html" title="1.2.3. Herramientas de EvaluaciÃ³n" /><link rel="next" href="sect-Security_Guide-Evaluating_the_Tools-Nikto.html" title="1.2.3.3. Nikto" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fe
 doraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Vulnerability_Assessment-Evaluating_the_Tools.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Evaluating_the_Tools-Nikto.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Evaluating_the_Tools-Nessus">1.2.3.2. Nessus</h4></div></div></div><div class="para">
				Nessus is a full-service security scanner. The plug-in architecture of Nessus allows users to customize it for their systems and networks. As with any scanner, Nessus is only as good as the signature database it relies upon. Fortunately, Nessus is frequently updated and features full reporting, host scanning, and real-time vulnerability searches. Remember that there could be false positives and false negatives, even in a tool as powerful and as frequently updated as Nessus.
			</div><div class="note"><h2>Note</h2><div class="para">
					Nessus is not included with Fedora and is not supported. It has been included in this document as a reference to users who may be interested in using this popular application.
				</div></div><div class="para">
				For more information about Nessus, refer to the official website at the following URL:
			</div><div class="para">
				<a href="http://www.nessus.org/">http://www.nessus.org/</a>
			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Vulnerability_Assessment-Evaluating_the_Tools.html"><strong>Anterior</strong>1.2.3. Herramientas de EvaluaciÃ³n</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Evaluating_the_Tools-Nikto.html"><strong>Siguiente</strong>1.2.3.3. Nikto</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Evaluating_the_Tools-Nikto.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.2.3.3. Nikto</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Vulnerability_Assessment-Evaluating_the_Tools.html" title="1.2.3. Herramientas de EvaluaciÃ³n" /><link rel="prev" href="sect-Security_Guide-Evaluating_the_Tools-Nessus.html" title="1.2.3.2. Nessus" /><link rel="next" href="sect-Security_Guide-Evaluating_the_Tools-VLAD_the_Scanner.html" title="1.2.3.4. VLAD the Scanner" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"
 ><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Evaluating_the_Tools-Nessus.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Evaluating_the_Tools-VLAD_the_Scanner.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Evaluating_the_Tools-Nikto">1.2.3.3. Nikto</h4></div></div></div><div class="para">
				Nikto is an excellent common gateway interface (CGI) script scanner. Nikto not only checks for CGI vulnerabilities but does so in an evasive manner, so as to elude intrusion detection systems. It comes with thorough documentation which should be carefully reviewed prior to running the program. If you have Web servers serving up CGI scripts, Nikto can be an excellent resource for checking the security of these servers.
			</div><div class="note"><h2>Note</h2><div class="para">
					Nikto is not included with Fedora and is not supported. It has been included in this document as a reference to users who may be interested in using this popular application.
				</div></div><div class="para">
				MÃ¡s informaciÃ³n sobre Nikto se puede encontrar en la siguiente URL:
			</div><div class="para">
				<a href="http://www.cirt.net/code/nikto.shtml">http://www.cirt.net/code/nikto.shtml</a>
			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Evaluating_the_Tools-Nessus.html"><strong>Anterior</strong>1.2.3.2. Nessus</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Evaluating_the_Tools-VLAD_the_Scanner.html"><strong>Siguiente</strong>1.2.3.4. VLAD the Scanner</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Evaluating_the_Tools-VLAD_the_Scanner.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.2.3.4. VLAD the Scanner</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Vulnerability_Assessment-Evaluating_the_Tools.html" title="1.2.3. Herramientas de EvaluaciÃ³n" /><link rel="prev" href="sect-Security_Guide-Evaluating_the_Tools-Nikto.html" title="1.2.3.3. Nikto" /><link rel="next" href="sect-Security_Guide-Evaluating_the_Tools-Anticipating_Your_Future_Needs.html" title="1.2.3.5. Anticipando sus Necesidades Futuras" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="r
 ight" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Evaluating_the_Tools-Nikto.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Evaluating_the_Tools-Anticipating_Your_Future_Needs.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Evaluating_the_Tools-VLAD_the_Scanner">1.2.3.4. VLAD the Scanner</h4></div></div></div><div class="para">
				VLAD is a vulnerabilities scanner developed by the <acronym class="acronym">RAZOR</acronym> team at Bindview, Inc., which checks for the SANS Top Ten list of common security issues (SNMP issues, file sharing issues, etc.). While not as full-featured as Nessus, VLAD is worth investigating.
			</div><div class="note"><h2>Note</h2><div class="para">
					VLAD is not included with Fedora and is not supported. It has been included in this document as a reference to users who may be interested in using this popular application.
				</div></div><div class="para">
				MÃ¡s informaciÃ³n sobre VLAD se puede encontrar el sitio web del equipo RAZOR en la siguiente URL:
			</div><div class="para">
				<a href="http://www.bindview.com/Support/Razor/Utilities/">http://www.bindview.com/Support/Razor/Utilities/</a>
			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Evaluating_the_Tools-Nikto.html"><strong>Anterior</strong>1.2.3.3. Nikto</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Evaluating_the_Tools-Anticipating_Your_Future_Needs.html"><strong>Siguiente</strong>1.2.3.5. Anticipando sus Necesidades Futuras</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-FORWARD_and_NAT_Rules-DMZs_and_IPTables.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.5.3. IPTables y las ZDM</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Firewalls-FORWARD_and_NAT_Rules.html" title="2.8.5. Reglas FORWARD y NAT" /><link rel="prev" href="sect-Security_Guide-FORWARD_and_NAT_Rules-Prerouting.html" title="2.8.5.2. Preruteo" /><link rel="next" href="sect-Security_Guide-Firewalls-Malicious_Software_and_Spoofed_IP_Addresses.html" title="2.8.6. Software Malicioso y SuplantaciÃ³n de Direcciones IP" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a c
 lass="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-FORWARD_and_NAT_Rules-Prerouting.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Firewalls-Malicious_Software_and_Spoofed_IP_Addresses.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-FORWARD_and_NAT_Rules-DMZs_and_IPTables">2.8.5.3. IPTables y las ZDM</h4></div></div></div><div class="para">
				Puede crear reglas de <code class="command">iptables</code> para enrutar trÃ¡fico a ciertos equipos, como por ejemplo un servidor HTTP o FTP dedicado, en una <em class="firstterm">zona desmilitarizada</em> (<acronym class="acronym">DMZ</acronym>, por las iniciales en inglÃ©s de DeMilitarized Zone). Un <acronym class="acronym">DMZ</acronym> es una subred local especial dedicada a proveer servicios en un transporte pÃºblico, como lo es Internet.
			</div><div class="para">
				Por ejemplo, para establecer una regla para enrutar peticiones HTTP entrantes a un servidor dedicad HTTP en 10-0-4-2 (fuera del rango 192.168.1.0/24 de la LAN), NAT utiliza la tabla <code class="computeroutput">PREROUTING</code> para reenviar los paquetes a la direcciÃ³n apropiada:
			</div><pre class="screen">[root at miServidor ~ ] # iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 80 -j DNAT --to-destination 10.0.4.2:80
</pre><div class="para">
				With this command, all HTTP connections to port 80 from outside of the LAN are routed to the HTTP server on a network separate from the rest of the internal network. This form of network segmentation can prove safer than allowing HTTP connections to a machine on the network.
			</div><div class="para">
				Si el servidor HTTP estÃ¡ configurado para aceptar conexiones seguras, entonces el puerto 443 debe ser reenviado tambiÃ©n.
			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-FORWARD_and_NAT_Rules-Prerouting.html"><strong>Anterior</strong>2.8.5.2. Preruteo</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Firewalls-Malicious_Software_and_Spoofed_IP_Addresses.html"><strong>Siguiente</strong>2.8.6. Software Malicioso y SuplantaciÃ³n de Direc...</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-FORWARD_and_NAT_Rules-Prerouting.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.5.2. Preruteo</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Firewalls-FORWARD_and_NAT_Rules.html" title="2.8.5. Reglas FORWARD y NAT" /><link rel="prev" href="sect-Security_Guide-Firewalls-FORWARD_and_NAT_Rules.html" title="2.8.5. Reglas FORWARD y NAT" /><link rel="next" href="sect-Security_Guide-FORWARD_and_NAT_Rules-DMZs_and_IPTables.html" title="2.8.5.3. IPTables y las ZDM" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.or
 g"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Firewalls-FORWARD_and_NAT_Rules.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-FORWARD_and_NAT_Rules-DMZs_and_IPTables.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-FORWARD_and_NAT_Rules-Prerouting">2.8.5.2. Preruteo</h4></div></div></div><div class="para">
				If you have a server on your internal network that you want make available externally, you can use the <code class="option">-j DNAT</code> target of the PREROUTING chain in NAT to specify a destination IP address and port where incoming packets requesting a connection to your internal service can be forwarded.
			</div><div class="para">
				Por ejemplo, si quiere reenviar pedidos HTTP entrantes a su servidor HTTP Apache dedicado en 172.31.0.23, use el siguiente comando:
			</div><pre class="screen">[root at miServidor ~ ] # iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 80 -j DNAT --to 172.31.0.23:80
</pre><div class="para">
				Esta regla especifica que la tabla <acronym class="acronym">nat</acronym> usa la cadena predefinida PREROUTING para enviar pedidos HTTP entrantes exclusivamente al la direcciÃ³n IP destino listado 172.31.0.23.
			</div><div class="note"><h2>Note</h2><div class="para">
					Si tiene una polÃtica predeterminada de DROP en su cadena FORWARD, debe agregar una regla para reenviar todos los pedidos HTTP entrantes para que sea posible el ruteo NAT destino. Para hacerlo, use el siguiente comando:
				</div><pre class="screen">[root at miServidor ~ ] # iptables -A FORWARD -i eth0 -p tcp --dport 80 -d 172.31.0.23 -j ACCEPT
</pre><div class="para">
					Esta regla reenvÃa todos los pedidos HTTP entrantes desde el cortafuego al destino pretendido; el Servidor HTTP APache detrÃ¡s del cortafuego.
				</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Firewalls-FORWARD_and_NAT_Rules.html"><strong>Anterior</strong>2.8.5. Reglas FORWARD y NAT</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-FORWARD_and_NAT_Rules-DMZs_and_IPTables.html"><strong>Siguiente</strong>2.8.5.3. IPTables y las ZDM</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Firewalls-Additional_Resources.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.9. Additional Resources</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Firewalls.html" title="2.8. Firewalls" /><link rel="prev" href="sect-Security_Guide-Firewalls-IPv6.html" title="2.8.8. IPv6" /><link rel="next" href="sect-Security_Guide-Additional_Resources-Useful_Firewall_Websites.html" title="2.8.9.2. Sitios web de Cortafuego Ãºtiles" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/ima
 ge_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Firewalls-IPv6.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Additional_Resources-Useful_Firewall_Websites.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Firewalls-Additional_Resources">2.8.9. Additional Resources</h3></div></div></div><div class="para">
			Hay varios aspectos de cortafuegos y del subsistema Netfilter de Linux que no pueden ser cubiertos en este capÃtulo. Para mÃ¡s informaciÃ³n vaya a los siguientes recursos.
		</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Additional_Resources-Installed_Firewall_Documentation">2.8.9.1. DocumentaciÃ³n Instalada del Cortafuego</h4></div></div></div><div class="itemizedlist"><ul><li><div class="para">
						Vaya a <a class="xref" href="sect-Security_Guide-IPTables.html" title="2.9. IPTables">SecciÃ³nÂ 2.9, â€œIPTablesâ€</a> para informaciÃ³n mÃ¡s detallada del comando <code class="command">iptables</code>, incluyendo definiciones de muchas opciones de comando.
					</div></li><li><div class="para">
						La pÃ¡gina man de <code class="command">iptables</code> contiene un resumen de las opciones.
					</div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Firewalls-IPv6.html"><strong>Anterior</strong>2.8.8. IPv6</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Additional_Resources-Useful_Firewall_Websites.html"><strong>Siguiente</strong>2.8.9.2. Sitios web de Cortafuego Ãºtiles</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Firewalls-Basic_Firewall_Configuration.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.2. ConfiguraciÃ³n BÃ¡sica del Cortafuego</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Firewalls.html" title="2.8. Firewalls" /><link rel="prev" href="sect-Security_Guide-Firewalls.html" title="2.8. Firewalls" /><link rel="next" href="sect-Security_Guide-Basic_Firewall_Configuration-Enabling_and_Disabling_the_Firewall.html" title="2.8.2.2. Habilitando y Deshabilitando el Cortafuego" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproj
 ect.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Firewalls.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Basic_Firewall_Configuration-Enabling_and_Disabling_the_Firewall.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Firewalls-Basic_Firewall_Configuration">2.8.2. ConfiguraciÃ³n BÃ¡sica del Cortafuego</h3></div></div></div><div class="para">
			Del mismo modo que con cortafuegos en un edificio intenta prevenir que se propague un incendio, un cortafuegos en una computadora intenta prevenir que algÃºn tipo de sofware malicioso se propague en su equipo. TambiÃ©n ayuda a prevenir que usuarios no autorizados accedan a su computadora.
		</div><div class="para">
			En una instalaciÃ³n por defecto de Fedora existe un cortafuegos entre su computadora o red, y cualquier otra red considerada como no segura, como por ejemplo lo es Internet. Determina quÃ© servicios en su computadora pueden ser accedidos por usuarios remotos. Un cortafuegos correctamente configurado puede incrementar enormemente la seguridad de su sistema. Se recomienda que configure un cortafuegos para cualquier sistema Fedora que tenga una conexiÃ³n a Internet.
		</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Basic_Firewall_Configuration-RHSECLEVELTOOL">2.8.2.1. <span class="application"><strong>Firewall Configuration Tool</strong></span></h4></div></div></div><div class="para">
				En la pantalla de <span class="guilabel"><strong>ConfiguraciÃ³n del Cortafuego</strong></span> en la instalaciÃ³n de Fedora, se le dieron las opciones para habilitar el cortafuego bÃ¡sico asÃ como la habilitaciÃ³n de ciertos dispositivos, servicios entrantes y puertos.
			</div><div class="para">
				DespuÃ©s de la instalaciÃ³n, puede cambiar esta preferencia usando <span class="application"><strong>Firewall Configuration Tool</strong></span>.
			</div><div class="para">
				Para iniciar esta aplicaciÃ³n, use el siguiente comando:
			</div><pre class="screen">[root at myServer ~] # system-config-firewall
</pre><div class="figure" id="figu-Security_Guide-RHSECLEVELTOOL-RHSECLEVELTOOL"><div class="figure-contents"><div class="mediaobject"><img src="images/fed-firewall_config.png" alt="Firewall Configuration Tool" /><div class="longdesc"><div class="para">
							ConfiguraciÃ³n del Nivel de Seguridad
						</div></div></div></div><h6>Figura 2.15. <span class="application">Firewall Configuration Tool</span></h6></div><br class="figure-break" /><div class="note"><h2>Note</h2><div class="para">
					<span class="application"><strong>Firewall Configuration Tool</strong></span> solo configura el cortafuego bÃ¡sico. Si el sistema necesita reglas mÃ¡s complejas, vaya a <a class="xref" href="sect-Security_Guide-IPTables.html" title="2.9. IPTables">SecciÃ³nÂ 2.9, â€œIPTablesâ€</a> para mÃ¡s detalles sobre la configuraciÃ³n de reglas especÃficas con <code class="command">iptables</code>.
				</div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Firewalls.html"><strong>Anterior</strong>2.8. Firewalls</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Basic_Firewall_Configuration-Enabling_and_Disabling_the_Firewall.html"><strong>Siguiente</strong>2.8.2.2. Habilitando y Deshabilitando el Cortafue...</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Firewalls-Common_IPTables_Filtering.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.4. Filtrado ComÃºn de IPTalbes</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Firewalls.html" title="2.8. Firewalls" /><link rel="prev" href="sect-Security_Guide-Using_IPTables-Saving_and_Restoring_IPTables_Rules.html" title="2.8.3.3. Guardando y Restaurando las Reglas de IPTables" /><link rel="next" href="sect-Security_Guide-Firewalls-FORWARD_and_NAT_Rules.html" title="2.8.5. Reglas FORWARD y NAT" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://
 docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Using_IPTables-Saving_and_Restoring_IPTables_Rules.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Firewalls-FORWARD_and_NAT_Rules.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Firewalls-Common_IPTables_Filtering">2.8.4. Filtrado ComÃºn de IPTalbes</h3></div></div></div><div class="para">
			La prevenciÃ³n del acceso a la red de atacantes remotos es uno de los aspectos mÃ¡s importantes de la seguridad de la red. La integridad de la LAN debe protegerse de los usuarios remotos maliciosos a traves del uso de las reglas estrictas de cortafuego.
		</div><div class="para">
			Sin embargo, con una polÃtica por defecto de bloquear todos los paquetes entrantes, saliente y reenviados, es imposible para el cortafuego/puerta de enlace y los usuarios internos de la LAN de que se comuniquen entre si o con recursos externos.
		</div><div class="para">
			Para permitir que los usuarios realicen funciones relacionadas con la red y de que puedan usar aplicaciones de red, los administradores deben abrir ciertos puertos para la comunicaciÃ³n.
		</div><div class="para">
			Por ejemplo, para permitir el acceso al puerto 80 <span class="emphasis"><em>en el cortafuego</em></span>, agregar la siguiente regla:
		</div><pre class="screen">[root at miServidor ~ ] # iptables -A INPUT -p tcp -m tcp --dport 80 -j ACCEPT
</pre><div class="para">
			Esto permite a los usuarios navegar sitios que se comunican usando el puerto estÃ¡ndar 80. Para permitir el acceso a sitios web seguros (por ejemplo, https://www.ejemplo.com/), tambiÃ©n necesita proveer el acceso al puerto 443, como sigue:
		</div><pre class="screen">[root at miServidor ~ ] # iptables -A INPUT -p tcp -m tcp --dport 443 -j ACCEPT
</pre><div class="important"><h2>Important</h2><div class="para">
				Cuando se crea un conjunto de reglas de <code class="command">iptables</code>, el orden es importante.
			</div><div class="para">
				Si una regla especifica que cualquier paquete desde la subred 192.168.100.0/24 debe ignorarse, y esto es seguido por una regla que permite los paquetes de 192.168.100.13 (que estÃ¡ dentro de la subred ignorada), la segunda regla se ignora.
			</div><div class="para">
				La regla para permitir los paquetes de 192.168.100.13 debe estar antes de la que elimina los restantes de la subred.
			</div><div class="para">
				Para insertar una regla en una ubicaciÃ³n especÃfica en una cadena existente, use la opciÃ³n <code class="option">-I</code>. Por ejemplo:
			</div><pre class="screen">[root at miServidor ~ ] # iptables -I INPUT 1 -i lo -p all -j ACCEPT
</pre><div class="para">
				Esta regla es insertada como la primera regla en la cadena INPUT para permitir el trÃ¡fico en el dispositivo loopback local.
			</div></div><div class="para">
			Pueden haber veces cuando se requiera acceso remoto a la LAN. Los servicios seguros, por ejemplo SSH, se pueden unsar para encriptar la conexiÃ³n remota a los servicios de la LAN.
		</div><div class="para">
			Administrators with PPP-based resources (such as modem banks or bulk ISP accounts), dial-up access can be used to securely circumvent firewall barriers. Because they are direct connections, modem connections are typically behind a firewall/gateway.
		</div><div class="para">
			Sin embargo, pueden relizarse casos especiales para usuarios remotos con conexiones de banda ancha. Usted puede configurar <code class="command">iptables</code> para aceptar conexiones de clientes remotos SSH. Por ejemplo, las siguientes reglas permiten acceso remoto SSH:
		</div><pre class="screen">[root at miServidor ~ ] # iptables -A INPUT -p tcp --dport 22 -j ACCEPT
[root at miServidor ~ ] # iptables -A OUTPUT -p tcp --sport 22 -j ACCEPT
</pre><div class="para">
			Estas reglas permiten ingreso y egreso para un sistema individual, como una PC directamente conectada a Internet, o a un cortafuegos/puerta de enlace. Sin embrago, no permiten a los nodos detrÃ¡s de un cortafiegos/puerta de enlace que tengan acceso a estos servicios. Para permitir acceso LAN a estos servicios, puese utilizar <em class="firstterm">Network Address Translation</em> (<acronym class="acronym">NAT</acronym>) con reglas de filtro <code class="command">iptables</code>.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Using_IPTables-Saving_and_Restoring_IPTables_Rules.html"><strong>Anterior</strong>2.8.3.3. Guardando y Restaurando las Reglas de IP...</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Firewalls-FORWARD_and_NAT_Rules.html"><strong>Siguiente</strong>2.8.5. Reglas FORWARD y NAT</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Firewalls-FORWARD_and_NAT_Rules.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.5. Reglas FORWARD y NAT</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Firewalls.html" title="2.8. Firewalls" /><link rel="prev" href="sect-Security_Guide-Firewalls-Common_IPTables_Filtering.html" title="2.8.4. Filtrado ComÃºn de IPTalbes" /><link rel="next" href="sect-Security_Guide-FORWARD_and_NAT_Rules-Prerouting.html" title="2.8.5.2. Preruteo" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/ima
 ges/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Firewalls-Common_IPTables_Filtering.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-FORWARD_and_NAT_Rules-Prerouting.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Firewalls-FORWARD_and_NAT_Rules">2.8.5. Reglas <code class="computeroutput">FORWARD</code> y <acronym class="acronym">NAT</acronym></h3></div></div></div><div class="para">
			La mayorÃa de los ISPs proveen sÃ³lo un nÃºmero limitados de direcciones IP disponibles pÃºblicamente para sus clientes.
		</div><div class="para">
			Los administradores deber, por lo tanto, encontrar formas alternativas de compartir el acceso a los servicios de Internet, sin darle por ello una direcciÃ³n IP pÃºblica a cada nodo de la LAN. Utilizar direcciones IP privadas es la manera mÃ¡s comÃºn de permitirle a todos los nodos de una LAN, que tengan un acceso correcto, tanto interno como externo, a los servicios de red.
		</div><div class="para">
			Los enrutadores de borde (como los cortafuegos) pueden recibir transmisiones entrantes desde Internet y enrutar los paquetes hacia el nodo LAN correspondiente. Al mismo tiempo, los cortafuegos/puertas de enlace pueden enrutar peticiones salientes de un nodo de la LAN hacia el servicio de Internet remoto.
		</div><div class="para">
			Este reenvÃo de trafico de red puede convertirse algunas veces en algo peligroso, especialmente con la disponibilidad de herramientas de crackeo modernas que pueden espiar direcciones IP <span class="emphasis"><em>internas</em></span> y hacer que el el equipo del atacante remoto actÃºe como un nodo de su LAN.
		</div><div class="para">
			Para impedir esto, <code class="command">iptables</code> provee polÃticas de ruteado y reenvÃo que se pueden implementar para prevenir el uso anormal de los recursos de red.
		</div><div class="para">
			La cadena <code class="computeroutput">FORWARD</code> permite a un administrador controlar hacia dÃ³nde se pueden rutear los paquetes dentro de la LAN. Por ejemplo, para permitir el reenvÃo para toda la LAN (asumiendo que el cortafuego/puerta de enlace tiene asignado una direcciÃ³n IP interna en eth1), use las siguientes reglas:
		</div><pre class="screen">[root at miServidor ~ ] # iptables -A FORWARD -i eth1 -j ACCEPT
[root at miServidor ~ ] # iptables -A FORWARD -o eth1 -j ACCEPT
</pre><div class="para">
			Esta regla le da a los sistemas detrÃ¡s del cortafuego/puerta de enlace el acceso a la red interna. La puerta de enlace rutea los paquetes desde un nodo de la LAN a su nodo destino deseado, pasando todos los paquetes a travÃ©s del dispositivo <code class="filename">eth1</code>.
		</div><div class="note"><h2>Note</h2><div class="para">
				Por defecto, la polÃtica IPv4 en kernels de Fedora deshabilita el soporte para reenvÃo de IP. Esto evita que mÃ¡quinas que corran Fedora funcionen como un ruteador dedicado. Para habilitar el reenvÃo de IP, use el siguiente comando:
			</div><pre class="screen">[root at miServidor ~ ] # sysctl -w net.ipv4.ip_forward=1
</pre><div class="para">
				Este cambio en la configuraciÃ³n sÃ³lo es vÃ¡lido para la sesiÃ³n actual; no persiste luego de un reinicio de equipo o del servicio de red. Para poner el reenvÃo de IP permanente, edite el archivo<code class="filename">/etc/sysctl.conf</code> como sigue:
			</div><div class="para">
				Ubique la siguiente lÃnea:
			</div><pre class="screen">net.ipv4.ip_forward = 0
</pre><div class="para">
				Edite para que se lea como sigue:
			</div><pre class="screen">net.ipv4.ip_forward = 1
</pre><div class="para">
				Use el siguiente comando para habilitar el cambio en el archivo <code class="filename">sysctl.conf</code>:
			</div><pre class="screen">[root at miServidor ~ ] # sysctl -p /etc/sysctl.conf
</pre></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-FORWARD_and_NAT_Rules-Postrouting_and_IP_Masquerading">2.8.5.1. Postruteado y Enmascarado de IP</h4></div></div></div><div class="para">
				La aceptaciÃ³n de paquetes reenviados a travÃ©s de la IP interna del cortafuego lo permite a los nodos de la LAN comunicarse entre si; sin embargo, todavÃa no se pueden comunicar externamente con internet.
			</div><div class="para">
				Para permitira que los nodos de una LAN con direcciones IP privadas puedan comunicarse con redes pÃºblicas externas, configura su cortafuegos para que realice <em class="firstterm">enmascaramiento de IP</em>, que enmascara las peticiones desde los nodos LAN con la direcciÃ³n IP del cortafuegos del dispositivo externo (en este caso, eth0):
			</div><pre class="screen">[root at miServidor ~ ] # iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
</pre><div class="para">
				Esta regla usa la tabla de comparaciÃ³n de paquetes NAT (<code class="option">-t nat</code>) y especifica la cadena predefinida POSTROUTING para hacer NAT (<code class="option">-A POSTROUTING</code>) en el dispositivo externo del cortafuego (<code class="option">-o eth0</code>).
			</div><div class="para">
				POSTROUTING permite que los paquetes se puedan alterar antes de salir del cortafuego's al dispositivo externo.
			</div><div class="para">
				El destino <code class="option">-j MASQUERADE</code> se especifica para enmascarar la direcciÃ³n IP privada de un nodo con la direcciÃ³n IP exxterna del cortafuego/puerta de enlace.
			</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Firewalls-Common_IPTables_Filtering.html"><strong>Anterior</strong>2.8.4. Filtrado ComÃºn de IPTalbes</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-FORWARD_and_NAT_Rules-Prerouting.html"><strong>Siguiente</strong>2.8.5.2. Preruteo</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Firewalls-IPTables_and_Connection_Tracking.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.7. IPTables y el Seguimiento de ConexiÃ³n</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Firewalls.html" title="2.8. Firewalls" /><link rel="prev" href="sect-Security_Guide-Firewalls-Malicious_Software_and_Spoofed_IP_Addresses.html" title="2.8.6. Software Malicioso y SuplantaciÃ³n de Direcciones IP" /><link rel="next" href="sect-Security_Guide-Firewalls-IPv6.html" title="2.8.8. IPv6" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproj
 ect.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Firewalls-Malicious_Software_and_Spoofed_IP_Addresses.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Firewalls-IPv6.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Firewalls-IPTables_and_Connection_Tracking">2.8.7. IPTables y el Seguimiento de ConexiÃ³n</h3></div></div></div><div class="para">
			Puede inspeccionar y restringir conexiones a servicios basados en sus <em class="firstterm">estados de conexiÃ³n</em>. Un mÃ³dulo dentro de <code class="command">iptables</code> utiliza un mÃ©tode denominado <em class="firstterm">rastreo de conexiÃ³n</em> para almacenar datos acerca de las conexiones recibidas. Puede permitir o negar acceso basÃ¡ndose en los siguientes estados de conexciÃ³n:
		</div><div class="itemizedlist"><ul><li><div class="para">
					<code class="option">NEW</code> â€” Un paquete que pide una nueva conexiÃ³n, tal como un pedido HTTP.
				</div></li><li><div class="para">
					<code class="option">ESTABLISHED</code> â€” Un paquete que es parte de una conexiÃ³n existente.
				</div></li><li><div class="para">
					<code class="option">RELATED</code> â€” Un paquete que estÃ¡ pidiendo una nueva conexiÃ³n, pero que es parte de una existente. Por ejemplo, FTP usa el puerto 21 para establecer una conexiÃ³n, pero los datos se transfieren en un puerto diferente (normalmente el puerto 20).
				</div></li><li><div class="para">
					<code class="option">INVALID</code> â€” Un paquete que no es parte de ninguna conexiÃ³n en la tabla de seguimiento de conexiones.
				</div></li></ul></div><div class="para">
			You can use the stateful functionality of <code class="command">iptables</code> connection tracking with any network protocol, even if the protocol itself is stateless (such as UDP). The following example shows a rule that uses connection tracking to forward only the packets that are associated with an established connection:
		</div><pre class="screen">[root at miServidor ~ ] # iptables -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT
</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Firewalls-Malicious_Software_and_Spoofed_IP_Addresses.html"><strong>Anterior</strong>2.8.6. Software Malicioso y SuplantaciÃ³n de Direc...</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Firewalls-IPv6.html"><strong>Siguiente</strong>2.8.8. IPv6</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Firewalls-IPv6.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.8. IPv6</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Firewalls.html" title="2.8. Firewalls" /><link rel="prev" href="sect-Security_Guide-Firewalls-IPTables_and_Connection_Tracking.html" title="2.8.7. IPTables y el Seguimiento de ConexiÃ³n" /><link rel="next" href="sect-Security_Guide-Firewalls-Additional_Resources.html" title="2.8.9. Additional Resources" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_C
 ontent/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Firewalls-IPTables_and_Connection_Tracking.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Firewalls-Additional_Resources.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Firewalls-IPv6">2.8.8. IPv6</h3></div></div></div><div class="para">
			La introducciÃ³n de la siguiente generaciÃ³n del Protocolo de Internet, llamado IPv6, expande mÃ¡s allÃ¡ de los lÃmites de las direcciones de 32-bit de IPv4 (o IP). IPv6 soporta direcciones de 128-bit, y las redes transportadoras que pueden soportar IPv6 son por lo tanto capaces de manejar un nÃºmero mÃ¡s grande de direcciones ruteables que el IPv4.
		</div><div class="para">
			Fedora supports IPv6 firewall rules using the Netfilter 6 subsystem and the <code class="command">ip6tables</code> command. In Fedora 11, both IPv4 and IPv6 services are enabled by default.
		</div><div class="para">
			La sintaxis del comando <code class="command">ip6tables</code> es idÃ©ntica a <code class="command">iptables</code> en todos los aspectos menos en que soporta direcciones de 128-bit. Por ejemplo, use el siguiente comando para habilitar conexiones SSH en un servidor de red para IPv6:
		</div><pre class="screen">[root at miServidor ~ ] # ip6tables -A INPUT -i eth0 -p tcp -s 3ffe:ffff:100::1/128 --dport 22 -j ACCEPT
</pre><div class="para">
			Para mÃ¡s informaciÃ³n acerca de redes IPv6, vaya a la PÃ¡gina de InformaciÃ³n sobre IPv6 en <a href="http://www.ipv6.org/">http://www.ipv6.org/</a>.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Firewalls-IPTables_and_Connection_Tracking.html"><strong>Anterior</strong>2.8.7. IPTables y el Seguimiento de ConexiÃ³n</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Firewalls-Additional_Resources.html"><strong>Siguiente</strong>2.8.9. Additional Resources</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Firewalls-Malicious_Software_and_Spoofed_IP_Addresses.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.6. Software Malicioso y SuplantaciÃ³n de Direcciones IP</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Firewalls.html" title="2.8. Firewalls" /><link rel="prev" href="sect-Security_Guide-FORWARD_and_NAT_Rules-DMZs_and_IPTables.html" title="2.8.5.3. IPTables y las ZDM" /><link rel="next" href="sect-Security_Guide-Firewalls-IPTables_and_Connection_Tracking.html" title="2.8.7. IPTables y el Seguimiento de ConexiÃ³n" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right
 " href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-FORWARD_and_NAT_Rules-DMZs_and_IPTables.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Firewalls-IPTables_and_Connection_Tracking.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Firewalls-Malicious_Software_and_Spoofed_IP_Addresses">2.8.6. Software Malicioso y SuplantaciÃ³n de Direcciones IP </h3></div></div></div><div class="para">
			Reglas mÃ¡s elaboradas pueden ser creadas para que controlen el acceso a subredes especÃficas, o incluso para nodos especÃficos, dentro de la LAN. Puede tambiÃ©n restringir ciertas aplicaciones o programas de carÃ¡cter dudoso como trojanos, gusanos, y demÃ¡s virus cliente/servidor, y evitar que entren en contacto con sus servidores.
		</div><div class="para">
			Por ejemplo, algunos troyanos examinan redes para ver los servicios en los puertos 31337 a 31340 (llamados los puertos<span class="emphasis"><em>elite</em></span> en la terminologÃa de craqueo).
		</div><div class="para">
			Dado que no hay servicios legÃtimos que se comunican vÃa estos puertos no estÃ¡ndares, su bloqueo puede disminuir efectivamente las posibilidades de que nodos infectados en su red se comuniquen con sus servidores maestros remotos.
		</div><div class="para">
			Las siguientes reglas eliminan todo el trÃ¡fico TCP que intenta usar el puerto 31337:
		</div><pre class="screen">[root at miServidor ~ ] # iptables -A OUTPUT -o eth0 -p tcp --dport 31337 --sport 31337 -j DROP
[root at miServidor ~ ] # iptables -A FORWARD -o eth0 -p tcp --dport 31337 --sport 31337 -j DROP
</pre><div class="para">
			TambiÃ©n se puede bloquear conexiones salientes que intenten suplantar los rangos de direcciones IP privadas para infiltrarse en su LAN.
		</div><div class="para">
			Por ejemplo, si su red usa el rango 192.168.1.0/24, se puede diseÃ±ar una regla que instruya al dispositivo de red del lado de Internet (por ejemplo, eth0) para que descarte cualquier paquete en ese dispositivo con una direcciÃ³n en el rango IP de su red local.
		</div><div class="para">
			Dado que se recomienda rechazar paquetes reenviados como una polÃtica predeterminada, cualquier otra direcciÃ³n IP mentida al dispositivo del lado externo (eth0) se rechaza automÃ¡ticamente.
		</div><pre class="screen">[root at miServidor ~ ] # iptables -A FORWARD -s 192.168.1.0/24 -i eth0 -j DROP
</pre><div class="note"><h2>Note</h2><div class="para">
				Hay una distinciÃ³n entre los destinos <code class="computeroutput">DROP</code> y <code class="computeroutput">REJECT</code> cuando se trabaja con reglas <span class="emphasis"><em>agregadas</em></span>.
			</div><div class="para">
				El destino <code class="computeroutput">RECHAZAR</code> niega acceso y regresa un error de <code class="computeroutput">conexiÃ³n denegada</code> a los usuarios que intenten conectarse al servicio. El destino <code class="computeroutput">ABANDONAR</code>, como su nombre lo indica, abandona el paquete sin previo aviso.
			</div><div class="para">
				Los administradores pueden usar su propia discreciÃ³n cuando usen estos destinos. Sin embargo, para evitar la confusiÃ³n del usuario e intentos de continuar conectando, el destino <code class="computeroutput">REJECT</code> es recomendado.
			</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-FORWARD_and_NAT_Rules-DMZs_and_IPTables.html"><strong>Anterior</strong>2.8.5.3. IPTables y las ZDM</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Firewalls-IPTables_and_Connection_Tracking.html"><strong>Siguiente</strong>2.8.7. IPTables y el Seguimiento de ConexiÃ³n</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Firewalls-Using_IPTables.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.3. Uso de IPTables</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Firewalls.html" title="2.8. Firewalls" /><link rel="prev" href="sect-Security_Guide-Basic_Firewall_Configuration-Activating_the_IPTables_Service.html" title="2.8.2.6. Activando el Servicio IPTables" /><link rel="next" href="sect-Security_Guide-Using_IPTables-Basic_Firewall_Policies.html" title="2.8.3.2. PolÃticas BÃ¡sicas del Cortafuego" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="ht
 tp://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Basic_Firewall_Configuration-Activating_the_IPTables_Service.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Using_IPTables-Basic_Firewall_Policies.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Firewalls-Using_IPTables">2.8.3. Uso de IPTables</h3></div></div></div><div class="para">
			El primer paso en el uso de <code class="command">iptables</code> es iniciar el servicio <code class="command">iptables</code>. Use el siguiente comando para iniciar el servicio <code class="command">iptables</code>:
		</div><pre class="screen">[root at miServidor ~] # service iptables start
</pre><div class="note"><h2>Note</h2><div class="para">
				El servicio <code class="command">ip6tables</code> puede ser desactivado si usted intenta utilizar solamente el servicio <code class="command">iptables</code>. Si desactiva el servicio <code class="command">ip6tables</code>, recuerde tambiÃ©n desactivar la red IPv6. Nunca deje un dispositivo de red activo sin su correspondiente cortafuegos.
			</div></div><div class="para">
			Para forzar a <code class="command">iptables</code> para que se inicie por defecto cuando el sistema arranque, use el siguiente comando:
		</div><pre class="screen">[root at miServidor ~] # chkconfig --level 345 iptables on
</pre><div class="para">
			Esto fuerza a <code class="command">iptables</code> a que se inicie cuando el sistema arranque en los niveles de ejecuciÃ³n 3, 4 o 5.
		</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Using_IPTables-IPTables_Command_Syntax">2.8.3.1. Sintaxis de Comando de IPTables</h4></div></div></div><div class="para">
				El siguiente comando <code class="command">iptables</code> ilustra la sintaxis bÃ¡sica de comandos:
			</div><pre class="screen">[root at miServidor ~ ] # iptables -A <em class="replaceable"><code><cadena></code></em> -j <em class="replaceable"><code><destino></code></em>
</pre><div class="para">
				La opciÃ³n <code class="option">-A</code> especifica que la regla se agregarÃ¡ a la <em class="firstterm"><cadena></em>. Cada cadena se compone de una o mÃ¡s <em class="firstterm">reglas</em>, por lo que se conoce tambiÃ©n como un <em class="firstterm">conjunto de reglas</em>.
			</div><div class="para">
				Las tres cadenas predefinidas son INPUT, OUTPUT, y FORWARD. Estas cadenas son permanentes y no se pueden borrar. La cadena especifica el punto en el que el paquete es manipulado.
			</div><div class="para">
				La opciÃ³n <code class="option">-j <em class="replaceable"><code><destino></code></em></code> especifica el destino de la regla; es decir, quÃ© hacer si un paquete coincide con la regla. Ejemplos de destinos predeterminados son ACCEPT, DROP, y REJECT.
			</div><div class="para">
				Vaya a la pÃ¡gina man de <code class="command">iptables</code> para mÃ¡s informaciÃ³n sobre las cadenas, opciones y destinos disponibles.
			</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Basic_Firewall_Configuration-Activating_the_IPTables_Service.html"><strong>Anterior</strong>2.8.2.6. Activando el Servicio IPTables</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Using_IPTables-Basic_Firewall_Policies.html"><strong>Siguiente</strong>2.8.3.2. PolÃticas BÃ¡sicas del Cortafuego</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Firewalls.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8. Firewalls</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="chap-Security_Guide-Securing_Your_Network.html" title="CapÃtulo 2. Securing Your Network" /><link rel="prev" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-Starting_and_Stopping_an_IPsec_Connection.html" title="2.7.8. Starting and Stopping an IPsec Connection" /><link rel="next" href="sect-Security_Guide-Firewalls-Basic_Firewall_Configuration.html" title="2.8.2. ConfiguraciÃ³n BÃ¡sica del Cortafuego" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="
 Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-Starting_and_Stopping_an_IPsec_Connection.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Firewalls-Basic_Firewall_Configuration.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h2 class="title" id="sect-Security_Guide-Firewalls">2.8. Firewalls</h2></div></div></div><div class="para">
		La seguridad de la informaciÃ³n es comÃºnmente entendida como un proceso, y no como un producto. Sin embargo, generalmente las implementaciones standard de seguridad utilizan alguna forma de mecanismo especÃfico para controlar los accesos privilegiados y restringir los recursos de red, a usuarios que debidamente autorizados para ello, y que al mismo tiempo puedan ser identificados y rastreados. Fedora incluye diferentes herramientas para ayudar a los administradores y a los ingenieros en seguridad, con los diferentes problemas que puedan surgir al controlar los accesos jerarquizados a la red.
	</div><div class="para">
		Los cortafuegos son uno de los componetes fundamentales para la implementaciÃ³n de la seguridad en una red. Diversos proveedores del mercado ofrecen herramientas para cortafuegos para todos los niveles del mercado: desde usuarios hogareÃ±os protegiendo los datos de su PC, hasta herramientas para centros de datos que permitan proteger los datos vitales de una empresa. Los cortafuegos pueden ser herramientas para un sÃ³lo equipo fÃsico, como las aplicaciones de cortafuego que ofrecen Cisco, Nokia y Sonicwall. Proveedores como Checkpoint, McAfee y Symantec tambiÃ©n han desarrollado herramientas de cortafuegos de cÃ³digo propietario, tanto para el hogar como para los segmentos comerciales del mercado.
	</div><div class="para">
		AdemÃ¡s de las diferencias entre los cortafuegos de hardware y de software, existen tambiÃ©n diferencias en la manera en que el cortafuego funciona, separando una herramienta de otra. <a class="xref" href="sect-Security_Guide-Firewalls.html#tabl-Security_Guide-Firewalls-Firewall_Types" title="Tabla 2.2. tipos de cortafuegos">TablaÂ 2.2, â€œtipos de cortafuegosâ€</a> muestra tres tipos comunes de cortafuegos y cÃ³mo funciona cada uno de ellos:
	</div><div class="table" id="tabl-Security_Guide-Firewalls-Firewall_Types"><div class="table-contents"><table summary="tipos de cortafuegos" border="1"><colgroup><col /><col /><col /><col /></colgroup><thead><tr><th>
						Method
					</th><th>
						Description
					</th><th>
						Ventajas
					</th><th>
						Desventajas
					</th></tr></thead><tbody><tr><td>
						NAT
					</td><td>
						<em class="firstterm">TraducciÃ³n de DirecciÃ³n de Red</em> (NAT, por las siglas en inglÃ©s de Network Address Translation), coloca direcciones IP de subredes privadas, detrÃ¡s de un pequeÃ±o grupo de direcciones IP pÃºblicas, enmascarando todas las peticiones hacia un recurso, en lugar de varios. El kernel de Linux tiene una funcionalidad NAT predefinida, mediante el subsistema del kernel Netfilter.
					</td><td>
						<table class="simplelist" border="0" summary="Simple list"><tr><td>Â· Se puede configurar transparentemente para mÃ¡quinas en una LAN </td></tr><tr><td>Â· La protecciÃ³n de muchas mÃ¡quinas y servicios detrÃ¡s de una o mÃ¡s direcciones IP externas simplifica las tareas de administraciÃ³n </td></tr><tr><td>Â· La restricciÃ³n del acceso a usuarios dentro y fuera de la LAN se puede configurar abriendo o cerrando puertos en el cortafuego/puerta de enlace NAT </td></tr></table>
					</td><td>
						<table class="simplelist" border="0" summary="Simple list"><tr><td>Â· No se puede prevenir la actividad maliciosa una vez que los usuarios de conecten a un servicio fuera del cortafuego </td></tr></table>
					</td></tr><tr><td>
						Filtro de Paquete
					</td><td>
						Un paquete de filtros de cortafuego lee cada uno de los datos que viajan a travÃ©s de una LAN. Puede leer y procesar paquetes segÃºn la informaciÃ³n de sus encabezados, y filtrar el paquete basÃ¡ndose en un conjunto de reglas programables implementadas por el adminsitrador del cortafuegos. El kernel de Linux tiene una funcionalidad de filtro de paquetes predefinida, mediante el subsistema del kernel Netfilter.
					</td><td>
						<table class="simplelist" border="0" summary="Simple list"><tr><td>Â· Personalizable a travÃ©s del utilitario <code class="command">iptables</code> </td></tr><tr><td>Â· No necesita cualquier personalizaciÃ³n del lado del cliente, dado que toda la actividad de red se filtra en el nivel del ruteador en vez de a nivel de aplicaciÃ³n. </td></tr><tr><td>Â· Dado a que los paquetes no se transmiten a travÃ©s de un proxy, la performance de la red es mÃ¡s rÃ¡pida debido a la conexiÃ³n directa entre el cliente y el equipo remoto </td></tr></table>
					</td><td>
						<table class="simplelist" border="0" summary="Simple list"><tr><td>Â· No se pueden filtrar paquetes para contenidos como en los cortafuegos proxy </td></tr><tr><td>Â· Procesa los paquetes en la capa del protocolo, pero no los puede filtrar en la capa de aplicaciÃ³n </td></tr><tr><td>Â· Las arquitecturas de red complejas pueden complicar el armado de las reglas de filtrado de paquetes, especialmente si se lo hace con el <em class="firstterm">enmascarado de IP</em> o con subredes locales y redes de zonas desmilitarizadas </td></tr></table>
					</td></tr><tr><td>
						Proxy
					</td><td>
						El proxy del cortafuegos filtra todas las peticiones de los clientes LAN de un determinado protocolo, o tipo, hacia una mÃ¡quina proxy, la que luego realiza esas mismas peticiones a Internet, en nombre del cliente local. Una mÃ¡quina proxy actÃºa como un bÃºfer entre usuarios remotos maliciosos y la red interna de mÃ¡quinas clientes.
					</td><td>
						<table class="simplelist" border="0" summary="Simple list"><tr><td>Â· Le da a los administradores el control sobre quÃ© aplicaciones y protocolos funcinan fuera de la LAN </td></tr><tr><td>Â· Algunos servidores proxy, pueden hacer cache de datos accedidos frecuentemente en vez de tener que usar la conexiÃ³n a internet para bajarlos. Esto ayuda a reducir el consumo de ancho de banda </td></tr><tr><td>Â· Los servicios de proxy pueden ser registrados y monitoreados mÃ¡s de cerca, lo que permite un control mÃ¡s estricto sobre el uso de los recursos de la red </td></tr></table>
					</td><td>
						<table class="simplelist" border="0" summary="Simple list"><tr><td>Â· Los proxies son a menudo especÃficos a una aplicaciÃ³n (HTTP, Telnet, etc.), o restringidos a un protocolo (la mayorÃa de los proxies funcionan sÃ³lo con servicios que usan conexiones TCP) </td></tr><tr><td>Â· Los servicios de aplicaciÃ³n no se pueden ejecutar detrÃ¡s de un proxy, por lo que su servidores de aplicaciÃ³n deben usar una forma separada de seguridad de red </td></tr><tr><td>Â· Los proxis se pueden volver cuellos de botellas, dado que todos los pedidos y transmisiones son pasados a travÃ©s de una fuente en vez de directamente del cliente al servicio remoto </td></tr></table>
					</td></tr></tbody></table></div><h6>Tabla 2.2. tipos de cortafuegos</h6></div><br class="table-break" /><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Firewalls-Netfilter_and_IPTables">2.8.1. Netfilter e IPTables</h3></div></div></div><div class="para">
			El kernel de Linux posee un poderoso subsistema de red denominado <em class="firstterm">Netfilter</em>. El subsistema Netfilter ofrece filtro total o parcial de paquetes, asÃ como servicios de enmascaramiento NAT e IP. Netfilter tambiÃ©n tiene la habilidad de <em class="firstterm">transformar</em> la informaciÃ³n de los encabezados IP para enrutamiento avanzado y administraciÃ³n del estado de la conexiÃ³n. Netfilter es controlado mediante la utilizacion de la herramienta <code class="command">iptables</code>.
		</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Netfilter_and_IPTables-IPTables_Overview">2.8.1.1. Repaso de IPTables</h4></div></div></div><div class="para">
				El poder y la flexibilidad de Netfilter se implementa usando la herramienta de administraciÃ³n <code class="command">iptables</code>, una lÃnea de comando con sintaxis similar a su predecesor, <code class="command">ipchains</code>.
			</div><div class="para">
				Una sintaxis similar no significa una implementaciÃ³n similar, sin embargo, <code class="command">ipchains</code> requiere un conjunto de reglas intrincadas para: filtrar las direcciones fuente; filtrar las direcciones destino; y filtrar los puertos de conexiÃ³n fuente y destino.
			</div><div class="para">
				En contraste <code class="command">iptables</code> utiliza el subsistema Netfilter para incrementar la conexiÃ³n de red, inspeccionar y procesar. <code class="command">iptables</code> provee logueo avanzado, acciones pre y post enrutamiento, traducciÃ³n de direcciones de red y reenvÃo de puerto, todo en una interfaz de lÃnea de comandos.
			</div><div class="para">
				Esta secciÃ³n provee un repaso de <code class="command">iptables</code>. Para una informaciÃ³n mÃ¡s detallada, vaya a <a class="xref" href="sect-Security_Guide-IPTables.html" title="2.9. IPTables">SecciÃ³nÂ 2.9, â€œIPTablesâ€</a>.
			</div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-Starting_and_Stopping_an_IPsec_Connection.html"><strong>Anterior</strong>2.7.8. Starting and Stopping an IPsec Connection</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Firewalls-Basic_Firewall_Configuration.html"><strong>Siguiente</strong>2.8.2. ConfiguraciÃ³n BÃ¡sica del Cortafuego</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-IPTables-Additional_Resources.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.9.7. Additional Resources</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-IPTables.html" title="2.9. IPTables" /><link rel="prev" href="sect-Security_Guide-IPTables-IPTables_and_IPv6.html" title="2.9.6. IPTables y IPv6" /><link rel="next" href="sect-Security_Guide-Additional_Resources-Useful_IP_Tables_Websites.html" title="2.9.7.2. Sitios web Ãºtiles sobre IP Tables" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="C
 ommon_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-IPTables-IPTables_and_IPv6.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Additional_Resources-Useful_IP_Tables_Websites.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-IPTables-Additional_Resources">2.9.7. Additional Resources</h3></div></div></div><div class="para">
			Vaya a las siguientes fuentes para informaciÃ³n adicional sobre el filtrado de paquetes con <code class="command">iptables</code>.
		</div><div class="itemizedlist"><ul><li><div class="para">
					<a class="xref" href="sect-Security_Guide-Firewalls.html" title="2.8. Firewalls">SecciÃ³nÂ 2.8, â€œFirewallsâ€</a> â€” Contiene un capÃtulo acerca del rol de los cortafuegos dentro de una estrategia de seguridad general, asÃ como las estrategias para construir las reglas del mismo.
				</div></li></ul></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Additional_Resources-Installed_IP_Tables_Documentation">2.9.7.1. DocumentaciÃ³n de IP Tables instalada</h4></div></div></div><div class="itemizedlist"><ul><li><div class="para">
						<code class="command">man iptables</code> â€” Contiene la descripciÃ³n de <code class="command">iptables</code> asÃ como una lista comprensiva de los destinos, opciones y extensiones de comparaciÃ³n.
					</div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-IPTables-IPTables_and_IPv6.html"><strong>Anterior</strong>2.9.6. IPTables y IPv6</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Additional_Resources-Useful_IP_Tables_Websites.html"><strong>Siguiente</strong>2.9.7.2. Sitios web Ãºtiles sobre IP Tables</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-IPTables-Command_Options_for_IPTables.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.9.3. Command Options for IPTables</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-IPTables.html" title="2.9. IPTables" /><link rel="prev" href="sect-Security_Guide-IPTables-Differences_Between_IPTables_and_IPChains.html" title="2.9.2. Differences Between IPTables and IPChains" /><link rel="next" href="sect-Security_Guide-Command_Options_for_IPTables-Command_Options.html" title="2.9.3.2. Command Options" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http:
 //docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-IPTables-Differences_Between_IPTables_and_IPChains.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Command_Options_for_IPTables-Command_Options.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-IPTables-Command_Options_for_IPTables">2.9.3. Command Options for IPTables</h3></div></div></div><div class="para">
			Las reglas para el filtrado de paquetes se crean usando el comando <code class="command">iptables</code>. Los aspectos siguientes del paquete son los mÃ¡s usados como criterios:
		</div><div class="itemizedlist"><ul><li><div class="para">
					<span class="emphasis"><em>Tipo de Paquete</em></span> â€” Especifica el tipo de paquete que filtra el comando.
				</div></li><li><div class="para">
					<span class="emphasis"><em>Fuente/Destino del Paquete</em></span> â€” Especifica quÃ© paquete se filtra basado en el fuente/destino del paquete.
				</div></li><li><div class="para">
					<span class="emphasis"><em>Destino</em></span> â€” Especifica quÃ© acciÃ³n se toma sobre los paquetes que coinciden con el criterio de mÃ¡s arriba.
				</div></li></ul></div><div class="para">
			Para mÃ¡s informaciÃ³n acerca de opciones especÃficas acerca de estos aspectos de los paquetes, por favor vea <a class="xref" href="sect-Security_Guide-Command_Options_for_IPTables-IPTables_Match_Options.html" title="2.9.3.4. IPTables Match Options">SecciÃ³nÂ 2.9.3.4, â€œIPTables Match Optionsâ€</a> y <a class="xref" href="sect-Security_Guide-Command_Options_for_IPTables-Target_Options.html" title="2.9.3.5. Target Options">SecciÃ³nÂ 2.9.3.5, â€œTarget Optionsâ€</a>.
		</div><div class="para">
			Las opciones utilizadas con reglas especÃficas de <code class="command">iptables</code>, para que puedan ser vÃ¡lidas, deben ser agrupadas lÃ³gicamente, fundamentadas en el propÃ³sito y las condiciones de la regla en su totalidad. En el recordatorio de esta secciÃ³n se explican opciones comÃºnmente utilizadas para el comando <code class="command">iptables</code>.
		</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Command_Options_for_IPTables-Structure_of_IPTables_Command_Options">2.9.3.1. Structure of IPTables Command Options</h4></div></div></div><div class="para">
				Muchos comandos <code class="command">iptables</code> tienen la siguiente estructura:
			</div><pre class="screen"><code class="computeroutput"> iptables [-t <em class="replaceable"><code><nombre-de-tabla></code></em>] <em class="replaceable"><code><comando></code></em> <em class="replaceable"><code><nombre-de-cadena></code></em> \ <em class="replaceable"><code><parametro-1></code></em> <em class="replaceable"><code><opciÃ³n-1></code></em> \ <em class="replaceable"><code><parametro-n></code></em> <em class="replaceable"><code><opciÃ³n-n></code></em></code>
</pre><div class="para">
				<em class="replaceable"><code><nombre-de-tabla></code></em> â€” Especifica a quÃ© tabla se aplica la regla. Si se omite, se usa la tabla <code class="option">filter</code>.
			</div><div class="para">
				<em class="replaceable"><code><comando></code></em> â€” Especifica la acciÃ³n a realziar, tal como agregar o eliminar una regla.
			</div><div class="para">
				<em class="replaceable"><code><nombre-de-cadena></code></em> â€” Especifica la cadena a editar, crear o borrar.
			</div><div class="para">
				pares de <em class="replaceable"><code><parametro>-<opciÃ³n></code></em> â€” Los parÃ¡metros y las opciones asociadas que especifican cÃ³mo se procesa el paquete que coincide con una regla.
			</div><div class="para">
				La longitud y complejidad de un comando <code class="command">iptables</code> puede cambiar significativamente, basado en su propÃ³sito.
			</div><div class="para">
				Por ejemplo, un comando para eliminar una regla de una cadena puede ser muy corto:
			</div><div class="para">
				<code class="command">iptables -D <em class="replaceable"><code><nombre-de-cadena> <nÃºmero-de-lÃnea></code></em></code>
			</div><div class="para">
				En contraste, un comando que aÃ±ada una regla que filtre los paquetes provenientes de una subred determinada, utilizando una variedad de parÃ¡metros y opciones especÃficas, podrÃa ser bastante extenso. Cuando construya comandos <code class="command">iptables</code>, es importante recordar que algunos parÃ¡metros y opciones requieren de otros parÃ¡metros y de otras opciones para poder constituir una regla vÃ¡lida. Esto puede producir un efecto cascada, con los futuros parÃ¡metros pidiendo otros nuevos. La regla no serÃ¡ vÃ¡lida hasta que no se satisfagan cada parÃ¡metro y cada opciÃ³n que requiera otro conjunto de opciones y parÃ¡metros.
			</div><div class="para">
				Con <code class="command">iptables -h</code> se puede ver una lista comprensiva de la estructura de los comandos de <code class="command">iptables</code>.
			</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-IPTables-Differences_Between_IPTables_and_IPChains.html"><strong>Anterior</strong>2.9.2. Differences Between IPTables and IPChains</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Command_Options_for_IPTables-Command_Options.html"><strong>Siguiente</strong>2.9.3.2. Command Options</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-IPTables-Differences_Between_IPTables_and_IPChains.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.9.2. Differences Between IPTables and IPChains</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-IPTables.html" title="2.9. IPTables" /><link rel="prev" href="sect-Security_Guide-IPTables.html" title="2.9. IPTables" /><link rel="next" href="sect-Security_Guide-IPTables-Command_Options_for_IPTables.html" title="2.9.3. Command Options for IPTables" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/im
 age_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-IPTables.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-IPTables-Command_Options_for_IPTables.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-IPTables-Differences_Between_IPTables_and_IPChains">2.9.2. Differences Between IPTables and IPChains</h3></div></div></div><div class="para">
			Tanto <code class="command">ipchains</code> como <code class="command">iptables</code> utilizan cadenas de reglas que operan dentro del kernel Linux, para filtrar paquetes basados su correspondencia con una regla o un conjunto de reglas determinado. Sin embargo, <code class="command">iptables</code> ofrece una forma mÃ¡s amplia de filtrado de paquetes, dÃ¡ndole al administrador un control superior sobre su sistema, sin por ello tener que crear en Ã©l complejidades innecesarias.
		</div><div class="para">
			Debe estÃ¡r atento a las siguientes diferencias significativas entre <code class="command">ipchains</code> e <code class="command">iptables</code>:
		</div><div class="variablelist"><dl><dt><span class="term"><span class="emphasis"><em>Al usar <code class="command">iptables</code>, cada paquete filtrado se procesa usando reglas de una sola cadena en vez de mÃºltiples cadenas.</em></span></span></dt><dd><div class="para">
						Por ejemplo, un paquete FORWARD ingresando en un sistema que utiliza <code class="command">ipchains</code> deberÃa tener que atravesar por las cadenas de INPUT, FORWARD y OUTPUT antes de poder continuar hacia su destino. Sin embargo, <code class="command">iptables</code> solo envÃa paquetes a la cadena de ENTRADA si es que estÃ¡n destinados para el sistema local, y solo envÃa paquetes a la cadena de SALIDA si el sistema local es quien ha generado esos paquetes. Es importante, por lo tanto, colocar la regla destinada a detener un paquete determinado, dentro de la cadena que manipula realmente ese paquete.
					</div></dd><dt><span class="term"><span class="emphasis"><em>El destino DENY se cambiÃ³ a DROP.</em></span></span></dt><dd><div class="para">
						En <code class="command">ipchains</code>, los paquetes que coincidÃan con una regla en una cadena podÃan ser direccionadas al destino DENY. Este destino se debe cambiar a DROP en <code class="command">iptables</code>.
					</div></dd><dt><span class="term"><span class="emphasis"><em>El orden importa cuando se ponen opciones en una regla.</em></span></span></dt><dd><div class="para">
						En <code class="command">ipchains</code>, el orden de las opciones de la regla no importa.
					</div><div class="para">
						El comando <code class="command">iptables</code> tiene una sintaxis mÃ¡s estricta. Requires que el protocolo (ICMP, TCP, o UDP) se especifique antes de los puertos fuente o destinos.
					</div></dd><dt><span class="term"><span class="emphasis"><em>Las placas de red deben estar asociadas con la correctas cadenas en las reglas del cortafuego.</em></span></span></dt><dd><div class="para">
						Por ejemplo, las placas entrantes (opciÃ³n <code class="option">-i</code>) sÃ³lo se puede usar en las cadenas INPUT o FORWARD. De la misma forma, las placas salientes (opciÃ³n <code class="option">-o</code>) sÃ³lo se pueden usar en las cadenas FORWARD o OUTPUT.
					</div><div class="para">
						En otras palabras, las cadenas INPUT y las interfases entrantes trabajan juntas; las cadenas OUTPUT y las interfases salientes trabajan juntas. Las cadenas FORWARD trabajan con la interfases entrantes y salientes.
					</div><div class="para">
						Las cadenas OUTPUT ya no se usan en interfases entrantes, y las cadenas INPUT no son vistas por paquetes que se mueven a travÃ©s de interfases salientes.
					</div></dd></dl></div><div class="para">
			Esta no es una lista comprensiva de los cambios. Vaya a <a class="xref" href="sect-Security_Guide-IPTables-Additional_Resources.html" title="2.9.7. Additional Resources">SecciÃ³nÂ 2.9.7, â€œAdditional Resourcesâ€</a> para informaciÃ³n mÃ¡s especÃfica.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-IPTables.html"><strong>Anterior</strong>2.9. IPTables</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-IPTables-Command_Options_for_IPTables.html"><strong>Siguiente</strong>2.9.3. Command Options for IPTables</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-IPTables-IPTables_Control_Scripts.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.9.5. IPTables Control Scripts</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-IPTables.html" title="2.9. IPTables" /><link rel="prev" href="sect-Security_Guide-IPTables-Saving_IPTables_Rules.html" title="2.9.4. Saving IPTables Rules" /><link rel="next" href="sect-Security_Guide-IPTables-IPTables_and_IPv6.html" title="2.9.6. IPTables y IPv6" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_
 right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-IPTables-Saving_IPTables_Rules.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-IPTables-IPTables_and_IPv6.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-IPTables-IPTables_Control_Scripts">2.9.5. IPTables Control Scripts</h3></div></div></div><div class="para">
			Hay dos mÃ©todos bÃ¡sicos de controlar <code class="command">iptables</code> en Fedora:
		</div><div class="itemizedlist"><ul><li><div class="para">
					<span class="application"><strong>Firewall Configuration Tool</strong></span> (<code class="command">system-config-securitylevel</code>) â€” Una interfase grÃ¡fica para crear, activar y grabar las reglas bÃ¡sicas del cortafuego. Vea en <a class="xref" href="sect-Security_Guide-Firewalls-Basic_Firewall_Configuration.html" title="2.8.2. ConfiguraciÃ³n BÃ¡sica del Cortafuego">SecciÃ³nÂ 2.8.2, â€œConfiguraciÃ³n BÃ¡sica del Cortafuegoâ€</a> para mÃ¡s informaciÃ³n.
				</div></li><li><div class="para">
					<code class="command">/sbin/service iptables <em class="replaceable"><code><opciÃ³n></code></em></code> â€” Que se usa para manipular varias funciones de <code class="command">iptables</code> usando su script de inicio. Las siguientes opciones estÃ¡n disponibles:
				</div><div class="itemizedlist"><ul><li><div class="para">
							<code class="command">start</code> â€” Si el cortafuego estÃ¡ configurado (es decir, <code class="filename">/etc/sysconfig/iptables</code> existe), se detienen todos los <code class="command">iptables</code> completamente y se los vuelve a iniciar con el comando <code class="command">/sbin/iptables-restore</code>. Esta opciÃ³n funciona solamente si el mÃ³dulo de kernel <code class="command">ipchains</code> no es cargado. Para chequear si este mÃ³dulo estÃ¡ cargado, teclee el siguiente comando como root:
						</div><pre class="screen"><code class="command"> [root at miServidor ~]# lsmod | grep ipchains </code>
</pre><div class="para">
							Si este comando no muestra salida, significa que no estÃ¡ cargado. Si es necesario, use el comando <code class="command">/sbin/rmmod</code> para eliminar el mÃ³dulo.
						</div></li><li><div class="para">
							<code class="command">stop</code> â€” Si el cortafuego estÃ¡ ejecutandose, las reglas del cortafuego en la memoria son limpiadas y todos los mÃ³dulos y ayudantes de iptables son descargados.
						</div><div class="para">
							Si la directiva <code class="command">IPTABLES_SAVE_ON_STOP</code> del archivo de configuraciÃ³n <code class="filename">/etc/sysconfig/iptables-config</code> es alterada de su valor original a <code class="command">yes</code>, las reglas actuales serÃ¡n gurdadas en <code class="filename">/etc/sysconfig/iptables</code> y todas las reglas existentes seran trasladadas a <code class="filename">/etc/sysconfig/iptables.save</code>.
						</div><div class="para">
							Vea en <a class="xref" href="sect-Security_Guide-IPTables-IPTables_Control_Scripts.html#sect-Security_Guide-IPTables_Control_Scripts-IPTables_Control_Scripts_Configuration_File" title="2.9.5.1. Archivo de ConfiguraciÃ³n de los Scripts de Control de IPTables">SecciÃ³nÂ 2.9.5.1, â€œArchivo de ConfiguraciÃ³n de los Scripts de Control de IPTablesâ€</a> mÃ¡s informaciÃ³n del archivo <code class="filename">iptables-config</code>.
						</div></li><li><div class="para">
							<code class="command">restart</code> â€” Si un cortafuegos estÃ¡ ejecutÃ¡ndose, sus reglas en la memoria serÃ¡n eliminadas, y el cortafuegos es iniciado nuvamente si es que estÃ¡ configurado en <code class="filename">/etc/sysconfig/iptables</code>. Esta opciÃ³n solo funciona si el mÃ³dulo <code class="command">ipchains</code> del kernel no estÃ¡ cargado.
						</div><div class="para">
							Si la directiva <code class="command">IPTABLES_SAVE_ON_RESTART</code> en el archivo de configuraciÃ³n <code class="filename">/etc/sysconfig/iptables-config</code> es alterada de su valor original a <code class="command">yes</code>, las reglas actuales serÃ¡n guardadas en <code class="filename">/etc/sysconfig/iptables</code> y cualquier otra regla existente serÃ¡ trasladada a <code class="filename">/etc/sysconfig/iptables.save</code>.
						</div><div class="para">
							Vea en <a class="xref" href="sect-Security_Guide-IPTables-IPTables_Control_Scripts.html#sect-Security_Guide-IPTables_Control_Scripts-IPTables_Control_Scripts_Configuration_File" title="2.9.5.1. Archivo de ConfiguraciÃ³n de los Scripts de Control de IPTables">SecciÃ³nÂ 2.9.5.1, â€œArchivo de ConfiguraciÃ³n de los Scripts de Control de IPTablesâ€</a> mÃ¡s informaciÃ³n del archivo <code class="filename">iptables-config</code>.
						</div></li><li><div class="para">
							<code class="command">status</code> â€” Muestra el estado del cortafuego y lista todas las reglas activas
						</div><div class="para">
							La configuraciÃ³n establecida por defecto para esta opciÃ³n muestra direcciones IP en cada regla. Para mostrar dominios y nombres de equipos, edite el archivo <code class="filename">/etc/sysconfig/iptables-config</code> y cambie el valor de <code class="command">IPTABLES_STATUS_NUMERIC</code> a <code class="command">no</code>. Para obtener mÃ¡s informaciÃ³n acerca del archivo <code class="filename">iptables-config</code>, consulte <a class="xref" href="sect-Security_Guide-IPTables-IPTables_Control_Scripts.html#sect-Security_Guide-IPTables_Control_Scripts-IPTables_Control_Scripts_Configuration_File" title="2.9.5.1. Archivo de ConfiguraciÃ³n de los Scripts de Control de IPTables">SecciÃ³nÂ 2.9.5.1, â€œArchivo de ConfiguraciÃ³n de los Scripts de Control de IPTablesâ€</a>.
						</div></li><li><div class="para">
							<code class="command">panic</code> â€” Limpia todas las reglas del cortafuego. Se configura como polÃtica para todas las tablas a <code class="command">DROP</code>.
						</div><div class="para">
							Esta opciÃ³n puede ser Ãºtil si se sabe que un servidor estÃ¡ comprometido. En vez de desconectarlo fÃsicamente de la red o apagarlo, puede usar esta opciÃ³n para detener todo trÃ¡fico posterior pero dejando a la computadora lista para un anÃ¡lisis forense.
						</div></li><li><div class="para">
							<code class="command">save</code> â€” Guarda las reglas del cortafuego en <code class="filename">/etc/sysconfig/iptables</code> usando <code class="command">iptables-save</code>. Vea en <a class="xref" href="sect-Security_Guide-IPTables-Saving_IPTables_Rules.html" title="2.9.4. Saving IPTables Rules">SecciÃ³nÂ 2.9.4, â€œSaving IPTables Rulesâ€</a> mÃ¡s informaciÃ³n.
						</div></li></ul></div></li></ul></div><div class="note"><h2>Note</h2><div class="para">
				Para utilizar los mismos comandos del programa init para controlar a netfilter para IPv6, sustituya <code class="command">ip6tables</code> por <code class="command">iptables</code> en los comandos <code class="command">/sbin/service</code> listados en esta secciÃ³n. Para obtener mayor infirmaciÃ³n acerca de IPv6 o netfilter, vea <a class="xref" href="sect-Security_Guide-IPTables-IPTables_and_IPv6.html" title="2.9.6. IPTables y IPv6">SecciÃ³nÂ 2.9.6, â€œIPTables y IPv6â€</a>.
			</div></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-IPTables_Control_Scripts-IPTables_Control_Scripts_Configuration_File">2.9.5.1. Archivo de ConfiguraciÃ³n de los Scripts de Control de IPTables</h4></div></div></div><div class="para">
				El comportamiento de los scripts de inicio de <code class="command">iptables</code> se controlan por el archivo de configuraciÃ³n <code class="filename">/etc/sysconfig/iptables-config</code>. La siguiente es una lista de las directivas contenidas en este archivo:
			</div><div class="itemizedlist"><ul><li><div class="para">
						<code class="command">IPTABLES_MODULES</code> â€” Especifica una lista separada por comas de los mÃ³dulos <code class="command">iptables</code> adicionales a cargar cuando se active el cortafuego. Estos pueden incluir el rastreo de conexiÃ³n y ayudantes NAT.
					</div></li><li><div class="para">
						<code class="command">IPTABLES_MODULES_UNLOAD</code> â€” Descarga los mÃ³dulos al reiniciar y detener. Esta directiva acepta los siguientes valores:
					</div><div class="itemizedlist"><ul><li><div class="para">
								<code class="command">yes</code> â€” El valor por defecto. Esta opciÃ³n debe ser pueesta para conseguir un estado correcto de un reinicio o detenida de un cortafuego.
							</div></li><li><div class="para">
								<code class="command">no</code> â€” Esta opciÃ³n debe ser puesta sÃ³lo si hay problemas al descargar los mÃ³dulos de netfilter.
							</div></li></ul></div></li><li><div class="para">
						<code class="command">IPTABLES_SAVE_ON_STOP</code> â€” Guarda las reglas actuales en <code class="filename">/etc/sysconfig/iptables</code> cuando el cortafuego es detenido. Esta directiva acepta los siguientes valores:
					</div><div class="itemizedlist"><ul><li><div class="para">
								<code class="command">yes</code> â€” Guarda las reglas existentes en <code class="filename">/etc/sysconfig/iptables</code> cuando se detiene el cortafuego, moviendo la versiÃ³n previa al archivo <code class="filename">/etc/sysconfig/iptables.save</code>.
							</div></li><li><div class="para">
								<code class="command">no</code> â€” El valor por defecto. No guarda las reglas existentes cuando el cortafuego es detenido.
							</div></li></ul></div></li><li><div class="para">
						<code class="command">IPTABLES_SAVE_ON_RESTART</code> â€” Guarda las reglas actuales del cortafuego cuando es reiniciado. Esta directiva acepta los siguientes valores:
					</div><div class="itemizedlist"><ul><li><div class="para">
								<code class="command">yes</code> â€” Guarda las reglas existentes en <code class="filename">/etc/sysconfig/iptables</code> cuando el cortafuego es reiniciado, moviendo la versiÃ³n previa al archivo <code class="filename">/etc/sysconfig/iptables.save</code>.
							</div></li><li><div class="para">
								<code class="command">no</code> â€” El valor predeterminado. No guarda las reglas existentes cuando se reinicia el cortafuego.
							</div></li></ul></div></li><li><div class="para">
						<code class="command">IPTABLES_SAVE_COUNTER</code> â€” Guarda y restaura todos los contadores de paquetes y de bytes en todas las cadenas y reglas. Esta directiva acepta los siguientes valores:
					</div><div class="itemizedlist"><ul><li><div class="para">
								<code class="command">yes</code> â€” Guarda los valores de los contadores.
							</div></li><li><div class="para">
								<code class="command">no</code> â€” El valor predeterminado. No guarda los valores de los contadores.
							</div></li></ul></div></li><li><div class="para">
						<code class="command">IPTABLES_STATUS_NUMERIC</code> â€” Muestra las direcciones IP en formato numÃ©rico en vez de dominios y nombres de equipo. Esta directiva acepta los siguientes valores:
					</div><div class="itemizedlist"><ul><li><div class="para">
								<code class="command">yes</code> â€” El valor predeterminado. Solo devuelve la direcciÃ³n IP dentro de una salida de estado.
							</div></li><li><div class="para">
								<code class="command">no</code> â€” Devuelve el dominio o nombres de equipos en una salida de estado.
							</div></li></ul></div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-IPTables-Saving_IPTables_Rules.html"><strong>Anterior</strong>2.9.4. Saving IPTables Rules</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-IPTables-IPTables_and_IPv6.html"><strong>Siguiente</strong>2.9.6. IPTables y IPv6</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-IPTables-IPTables_and_IPv6.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.9.6. IPTables y IPv6</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-IPTables.html" title="2.9. IPTables" /><link rel="prev" href="sect-Security_Guide-IPTables-IPTables_Control_Scripts.html" title="2.9.5. IPTables Control Scripts" /><link rel="next" href="sect-Security_Guide-IPTables-Additional_Resources.html" title="2.9.7. Additional Resources" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/i
 mage_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-IPTables-IPTables_Control_Scripts.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-IPTables-Additional_Resources.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-IPTables-IPTables_and_IPv6">2.9.6. IPTables y IPv6</h3></div></div></div><div class="para">
			Si se instala el paquete <code class="filename">iptables-ipv6</code>, netfilter en Fedora puede filtrar la siguiente generaciÃ³n del protocolo de Internet IPv6. El comando usado para manipular el netfilter de IPv6 es <code class="command">ip6tables</code>.
		</div><div class="para">
			La maorÃa de las directivas para este comando son identicas a aquellas utilizadas para <code class="command">iptables</code>, excepto que la tabla <code class="command">nat</code> no es aÃºn soportada. Esto significa que aÃºn no es posible realizar tareas de traslados sobre direcciones de redes IPv6, como ser, por ejemplo, enmascaramiento y reenvÃo de puertos.
		</div><div class="para">
			Las reglas de <code class="command">ip6tables</code> se guardan en el archivo <code class="filename">/etc/sysconfig/ip6tables</code>. Las reglas previas guardadas antes por los scripts de inicio de <code class="command">ip6tables</code> se guardan en el archivo <code class="filename">/etc/sysconfig/ip6tables.save</code>.
		</div><div class="para">
			Las opciones de configuraciÃ³n para el programa init <code class="command">ip6tables</code> son almacenadas en <code class="filename">/etc/sysconfig/ip6tables-config</code>, y los nombres para cada directiva varÃan significativamente de los correspondientes en <code class="command">iptables</code>.
		</div><div class="para">
			Por ejemplo, la directiva <code class="command">IPTABLES_MODULES</code> de <code class="filename">iptables-config</code>: el equivalente en el archivo <code class="filename">ip6tables-config</code> es <code class="command">IP6TABLES_MODULES</code>.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-IPTables-IPTables_Control_Scripts.html"><strong>Anterior</strong>2.9.5. IPTables Control Scripts</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-IPTables-Additional_Resources.html"><strong>Siguiente</strong>2.9.7. Additional Resources</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-IPTables-Saving_IPTables_Rules.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.9.4. Saving IPTables Rules</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-IPTables.html" title="2.9. IPTables" /><link rel="prev" href="sect-Security_Guide-Command_Options_for_IPTables-Listing_Options.html" title="2.9.3.6. Listing Options" /><link rel="next" href="sect-Security_Guide-IPTables-IPTables_Control_Scripts.html" title="2.9.5. IPTables Control Scripts" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Commo
 n_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Command_Options_for_IPTables-Listing_Options.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-IPTables-IPTables_Control_Scripts.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-IPTables-Saving_IPTables_Rules">2.9.4. Saving IPTables Rules</h3></div></div></div><div class="para">
			Las reglas creadas con el comando <code class="command">iptables</code> son almacenadas en la memoria. Si el sistema es reiniciado antes de guardar el conjunto de reglas de <code class="command">iptables</code>, estas reglas se perderÃ¡n. Para que las reglas de netfilter sigan vigentes luego de reiniciar el sistema, necesitan ser gurdadas. Para salvar reglas de netfilter, ingrese el siguiente comando como usuario root:
		</div><pre class="screen"><code class="command"> /sbin/service iptables save </code>
</pre><div class="para">
			Esto ejecuta el programa init de <code class="command">iptables</code>, que a su vez ejecuta el programa <code class="command">/sbin/iptables-save</code> y escribe la configuraciÃ³n actual de <code class="command">iptables</code> a <code class="filename">/etc/sysconfig/iptables</code>. El archivo existente <code class="filename">/etc/sysconfig/iptables</code> es guardado como <code class="filename">/etc/sysconfig/iptables.save</code>.
		</div><div class="para">
			La prÃ³xima vez que el sistema se reinicie, el programa init de <code class="command">iptables</code> aplica nuevamente las reglas guardadas en <code class="filename">/etc/sysconfig/iptables</code> utilizando el comando <code class="command">/sbin/iptables-restore</code>.
		</div><div class="para">
			Si bien siempre es una buena idea probar una nueva regla <code class="command">iptables</code> antes de incluirla en el archivo <code class="filename">/etc/sysconfig/iptables</code>, es posible copiar reglas <code class="command">iptables</code> a este archivo desde una versiÃ³n diferente del mismo archivo. Esto permite una rÃ¡pida distribuciÃ³n de los conjuntos de reglas <code class="command">iptables</code> en diversas mÃ¡quinas.
		</div><div class="para">
			TambiÃ©n puede grabar las reglas de iptables a un archivo separado para distribuir, respaldar u otros propÃ³sitos. Para guardar sus reglas de iptables, ingrese el siguiente comando como root:
		</div><pre class="screen"><code class="command"> [root at myServer ~]# iptables-save > <em class="replaceable"><code><filename></code></em></code>where <em class="replaceable"><code><filename></code></em> is a user-defined name for your ruleset.
</pre><div class="important"><h2>Important</h2><div class="para">
				Si va a distribuir el archivo <code class="filename">/etc/sysconfig/iptables</code> a otras mÃ¡quinas, debe teclear <code class="command">/sbin/service iptables restart</code> para que las nuevas reglas tengan efecto.
			</div></div><div class="note"><h2>Note</h2><div class="para">
				FÃjese la diferencia entre el <span class="emphasis"><em>command</em></span> <code class="command">iptables</code> (<code class="command">/sbin/iptables</code>), que es utilizado para manipular las tablas y cadenas que constituyen las funcionalidades de <code class="command">iptables</code>, y el <span class="emphasis"><em>service</em></span> <code class="command">iptables</code> (<code class="command">/sbin/iptables service</code>), que es utilizado para activar y desactivar el servicio de <code class="command">iptables</code> en sÃ.
			</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Command_Options_for_IPTables-Listing_Options.html"><strong>Anterior</strong>2.9.3.6. Listing Options</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-IPTables-IPTables_Control_Scripts.html"><strong>Siguiente</strong>2.9.5. IPTables Control Scripts</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-IPTables.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.9. IPTables</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="chap-Security_Guide-Securing_Your_Network.html" title="CapÃtulo 2. Securing Your Network" /><link rel="prev" href="sect-Security_Guide-Additional_Resources-Related_Documentation.html" title="2.8.9.3. DocumentaciÃ³n Relacionada" /><link rel="next" href="sect-Security_Guide-IPTables-Differences_Between_IPTables_and_IPChains.html" title="2.9.2. Differences Between IPTables and IPChains" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a clas
 s="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Additional_Resources-Related_Documentation.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-IPTables-Differences_Between_IPTables_and_IPChains.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h2 class="title" id="sect-Security_Guide-IPTables">2.9. IPTables</h2></div></div></div><div class="para">
		Con Fedora estÃ¡n incluidas herramientas avanzadas para el <em class="firstterm">filtrado de paquetes</em> â€” el proceso adherido al kernel que permite controlar a los paquetes de red mientras estÃ¡n ingresando a nuestro entorno, mientras lo estÃ¡n recorriendo y cuando lo abandonan. Las versiones del kernel anteriores a la 2.4, dependÃan de <code class="command">ipchains</code> para el filtrado de paquetes, y utilizaban listas de reglas aplicadas a los paquetes en cada paso del proceso de filtrado. El kernel 2.4 introdujo la utilizaciÃ³n de <code class="command">iptables</code> (tambiÃ©n llamado <em class="firstterm">netfilter</em>), que si bien es similar a <code class="command">ipchains</code>, expande enormemente el rango y la posibilidad de control disponible para filtrar los paquetes de red.
	</div><div class="para">
		El siguiente capÃtulo se dedica a los conceptos bÃ¡sicos del filtrado de paquetes, establece las diferencias entre <code class="command">ipchains</code> e <code class="command">iptables</code>, explica las diferentes opciones disponibles con los comandos de <code class="command">iptables</code>, y explica como las reglas de filtrado pueden ser preservadas entre los reinicios del sistema.
	</div><div class="para">
		Vaya a <a class="xref" href="sect-Security_Guide-IPTables-Additional_Resources.html" title="2.9.7. Additional Resources">SecciÃ³nÂ 2.9.7, â€œAdditional Resourcesâ€</a> para instrucciones sobre cÃ³mo construir reglas de <code class="command">iptables</code> y configurar un cortafuego para que las use.
	</div><div class="important"><h2>Important</h2><div class="para">
			El mecanismo de un cortafuegos establecido por defecto con un kernel 2.4 o superior es <code class="command">iptables</code>, pero <code class="command">iptables</code> no puede ser utilizado si <code class="command">ipchains</code> se encuentra en ejecuciÃ³n. Si <code class="command">ipchains</code> estÃ¡ presente en el momento del arranque, el kernel envÃa un mensaje de error y no puede iniciar <code class="command">iptables</code>.
		</div><div class="para">
			La funcionalidad de <code class="command">ipchains</code> no es afectada por estos errores.
		</div></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-IPTables-Packet_Filtering">2.9.1. Filtrado de Paquete</h3></div></div></div><div class="para">
			El kernel de Linux utiliza la herramienta <span class="application"><strong>Netfilter</strong></span> para filtrar los paquetes, permitiendo que alguno de ellos sean recibidos por el sistema (o que pasen a travÃ©s de Ã©l), y evitando que lo hagan otros. Esta herramienta estÃ¡ predefinida en el kernel, y posee tres <em class="firstterm">tablas</em> o <em class="firstterm">listas de reglas</em> predeterminadas de la forma siguiente:
		</div><div class="itemizedlist"><ul><li><div class="para">
					<code class="option">filter</code> â€” La tabla predeterminada para el manejo de paquetes de red.
				</div></li><li><div class="para">
					<code class="option">nat</code> â€” Se usa para alterar paquetes que crean una nueva conexiÃ³n y para <em class="firstterm">TraducciÃ³n de DirecciÃ³n de Red</em> (<em class="firstterm">NAT</em>).
				</div></li><li><div class="para">
					<code class="option">mangle</code> â€” Usada para tipos especÃficos de alteraciones de paquetes.
				</div></li></ul></div><div class="para">
			Cada tabla tiene un grupo de <em class="firstterm">cadenas</em> predefinidas, que corresponden a las acciones realizadas por <code class="command">netfilter</code> sobre el paquete.
		</div><div class="para">
			Las cadenas predefinidas para la tabla <code class="option">filter</code> son las siguientes:
		</div><div class="itemizedlist"><ul><li><div class="para">
					<em class="firstterm">INPUT</em> â€” Se aplica a paquetes de red que son destinados a este equipo.
				</div></li><li><div class="para">
					<em class="firstterm">OUTPUT</em> â€” Se aplica a paquetes de red generados localmente.
				</div></li><li><div class="para">
					<em class="firstterm">FORWARD</em> â€” Se aplica a paquetes de la red ruteados a travÃ©s de este equipo.
				</div></li></ul></div><div class="para">
			Las cadenas predeterminadas para la tabla <code class="option">nat</code> son las siguientes:
		</div><div class="itemizedlist"><ul><li><div class="para">
					<em class="firstterm">PREROUTING</em> â€” Altera los paquetes de la red cuando llegan.
				</div></li><li><div class="para">
					<em class="firstterm">OUTPUT</em> â€” Altera los paquetes de la red generados localmente antes de que se envÃen.
				</div></li><li><div class="para">
					<em class="firstterm">POSTROUTING</em> â€” Altera los paquetes de la red antes de ser enviados.
				</div></li></ul></div><div class="para">
			Las cadenas predeterminadas para la tabla <code class="option">mangle</code> son:
		</div><div class="itemizedlist"><ul><li><div class="para">
					<em class="firstterm">INPUT</em> â€” Altera los paquetes de red destinados a este equipo.
				</div></li><li><div class="para">
					<em class="firstterm">OUTPUT</em> â€” Altera los paquetes de la red generados localmente antes de que se envÃen.
				</div></li><li><div class="para">
					<em class="firstterm">FORWARD</em> â€” Altera los paquetes de red ruteados a travÃ©s de este equipo.
				</div></li><li><div class="para">
					<em class="firstterm">PREROUTING</em> â€” Altera los paquetes que vienen de la red antes de ser ruteados.
				</div></li><li><div class="para">
					<em class="firstterm">POSTROUTING</em> â€” Altera los paquetes de la red antes de ser enviados.
				</div></li></ul></div><div class="para">
			Cada paquete de red recibido por, o ennviado con un sistema Linux es sujeto de (o por) al menos una tabla. Sin embargo, un paquete puede ser sujeto por varias reglas pertenecientes a cada tabla, antes de poder emerger al final de la cadena. La estructura y el propÃ³sito de estas reglas pueden variar, pero por lo general lo que buscan es un paquete yendo o viniendo desde una direcciÃ³n IP determinada (o conjunto de direcciones), cada vez que se utilice un protocolo y un servicio de red determinados.
		</div><div class="note"><h2>Note</h2><div class="para">
				Por defecto, las reglas del cortafuego se graban en los archivos <code class="filename">/etc/sysconfig/iptables</code> o <code class="filename">/etc/sysconfig/ip6tables</code>.
			</div><div class="para">
				El servicio <code class="command">iptables</code> se activa antes que cualquier otro servicio relacionado con DNS, cuando el sistema Linux es iniciado. Esto significa que las rglas de cortafuegos pueden sÃ³lo hacer referencia a direcciones IP numÃ©ricas (como por ejemplo, 192.168.0.1). En este tiop de reglas, los nombres del dominio (por ejemplo, host.example.com) producen errores.
			</div></div><div class="para">
			Dejando de lado el destino que tengan, cuando los paquetes se corresponden con una regla en particular de una de estas tablas, una <em class="firstterm">acciÃ³n</em> es aplicada a ellos. Si la regla especifica una acciÃ³n <code class="command">ACCEPT</code> para un paquete que se corresponde con ella, ese paquete se saltea el resto de la regla y le es permitido continuar hacia su destino, cualquiera que este sea. Si una regla especifica una acciÃ³n <code class="command">DROP</code>, a ese paquete se le niega acceso al sistema y nada es devuelto al equipo que lo enviÃ³. Si una regla especifica la acciÃ³n <code class="command">QUEUE</code>, el paquete es colocado en un espacio de usuario. Si una regla especifica la acciÃ³n optativa <code class="command">REJECT</code>, el paquete es abandonado, pero un paquete de error es a la vez enviado a quien lo originÃ³.
		</div><div class="para">
			Cada cadena posee una polÃtica por defecto para las acciones de <code class="command">ACCEPT</code>, <code class="command">DROP</code>, <code class="command">REJECT</code>, o <code class="command">QUEUE</code>. Si ninguna de estas reglas en la cadena se aplica al paquete, entonces el paquete es tratado de acuerdo a la polÃtica establecida por defecto.
		</div><div class="para">
			El comando <code class="command">iptables</code> configura estas tablas, asÃ como crea algunas nuevas si es necesario.
		</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Additional_Resources-Related_Documentation.html"><strong>Anterior</strong>2.8.9.3. DocumentaciÃ³n Relacionada</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-IPTables-Differences_Between_IPTables_and_IPChains.html"><strong>Siguiente</strong>2.9.2. Differences Between IPTables and IPChains</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-IPTables_Match_Options-Additional_Match_Option_Modules.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.9.3.4.4. Additional Match Option Modules</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Command_Options_for_IPTables-IPTables_Match_Options.html" title="2.9.3.4. IPTables Match Options" /><link rel="prev" href="sect-Security_Guide-IPTables_Match_Options-ICMP_Protocol.html" title="2.9.3.4.3. Protocolo ICMP" /><link rel="next" href="sect-Security_Guide-Command_Options_for_IPTables-Target_Options.html" title="2.9.3.5. Target Options" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a
 ><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-IPTables_Match_Options-ICMP_Protocol.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Command_Options_for_IPTables-Target_Options.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h5 class="title" id="sect-Security_Guide-IPTables_Match_Options-Additional_Match_Option_Modules">2.9.3.4.4. Additional Match Option Modules</h5></div></div></div><div class="para">
					Opciones de coincidencias adicionales estÃ¡n disponibles a travÃ©s de los mÃ³dulos cargados por el comando <code class="command">iptables</code>.
				</div><div class="para">
					Para usar un mÃ³dulo de comparaciÃ³n, cargue el mÃ³dulo por su nombre con <code class="option">-m <em class="replaceable"><code><nombre-de-mÃ³dulo></code></em></code>, donde <em class="replaceable"><code><nombre-de-mÃ³dulo></code></em> es el nombre del mÃ³dulo.
				</div><div class="para">
					Por defecto hay disponibles muchos mÃ³dulos. TambiÃ©n puede crear mÃ³dulos para proveer funcionalidad adicional.
				</div><div class="para">
					La siguiente es una lista parcial de los mÃ³dulos mÃ¡s comÃºnmente usados:
				</div><div class="itemizedlist"><ul><li><div class="para">
							MÃ³dulo <code class="option">limit</code> â€” Pone lÃmites sobre cuÃ¡ntos paquetes se toman para una regla particular.
						</div><div class="para">
							Cuando se usa junto con el destino <code class="command">LOG</code>, el mÃ³dulo <code class="option">limit</code> puede prevenir una inundaciÃ³n de paquetes coincidentes que pudieran sobrecargar al sistema de log con mensajes repetitivos o acabar los recursos del sistema.
						</div><div class="para">
							Vaya a <a class="xref" href="sect-Security_Guide-Command_Options_for_IPTables-Target_Options.html" title="2.9.3.5. Target Options">SecciÃ³nÂ 2.9.3.5, â€œTarget Optionsâ€</a> para mÃ¡s informaciÃ³n sobre el destino <code class="command">LOG</code>.
						</div><div class="para">
							El mÃ³dulo <code class="option">limit</code> habilita las siguientes opciones:
						</div><div class="itemizedlist"><ul><li><div class="para">
									<code class="option">--limit</code> â€” Establece la cantidad mÃ¡xima posible de correspondencias en un perÃodo de tiempo determinado, especificado como un par <code class="option"><em class="replaceable"><code><value>/<period></code></em></code>. Por ejemplo, utilizar <code class="option">--limit 5/hour</code> permite 5 correspondencias con la regla a cada hora.
								</div><div class="para">
									Los perÃodos se pueden especificar en segundos, minutos, horas o dÃas.
								</div><div class="para">
									Si no se usa un nÃºmero o modificador de tiempo, el valor predeterminado de <code class="option">3/hour</code> es asumido.
								</div></li><li><div class="para">
									<code class="option">--limit-burst</code> â€” Pone un lÃmite en el nÃºmero de paquetes que pueden coincidir con la regla en cada momento.
								</div><div class="para">
									Esta opciÃ³n se especifica como un entero y no se debe usar junto con la opciÃ³n <code class="option">--limit</code>.
								</div><div class="para">
									Si no se especifica un valor, el valor predeterminado cinco (5) es asumido.
								</div></li></ul></div></li><li><div class="para">
							MÃ³dulo <code class="option">state</code> â€” Habilita el chequeo del estado.
						</div><div class="para">
							El mÃ³dulo <code class="option">state</code> habilita las siguientes opciones:
						</div><div class="itemizedlist"><ul><li><div class="para">
									<code class="option">--state</code> â€” chequea a un paquete con los siguientes estados de conexiÃ³n:
								</div><div class="itemizedlist"><ul><li><div class="para">
											<code class="option">ESTABLISHED</code> â€” El paquete estÃ¡ asociado a otros paquetes en una conexiÃ³n establecida. Necesita aceptar este estado si quiere mantener una conexiÃ³n entre un cliente y un servidor.
										</div></li><li><div class="para">
											<code class="option">INVALID</code> â€” El paquete es chequeado no estÃ¡ asociado a una conexiÃ³n conocida.
										</div></li><li><div class="para">
											<code class="option">NEW</code> â€” El paquete chequeado es para crear una conexiÃ³n nueva o es parte de una conexiÃ³n de doble vÃa que no fue vista previamente. Necesita aceptar eeste estado si quiere permitir conexiones nuevas a un servicio.
										</div></li><li><div class="para">
											<code class="option">RELATED</code> â€” El paquete coincidente estÃ¡ iniciando una conexiÃ³n relacionada de alguna manera a otra existente. Un ejemplo de esto es FTP, que usa una conexiÃ³n para el control del trÃ¡fico (puerto 21) y una conexiÃ³n separada para la transferencia de datos (puerto 20).
										</div></li></ul></div><div class="para">
									Estos estados de conexiÃ³n pueden ser utilizados combinados con otros, si se los separa con comas, como por ejemplo <code class="option">-m state --state INVALID,NEW</code>.
								</div></li></ul></div></li><li><div class="para">
							MÃ³dulo <code class="option">mac</code> â€” Habilita el chequeo de la direcciÃ³n MAC de hardware.
						</div><div class="para">
							El mÃ³dulo <code class="option">mac</code> habilita la siguiente opciÃ³n:
						</div><div class="itemizedlist"><ul><li><div class="para">
									<code class="option">--mac-source</code> â€” Hace corresponder una direcciÃ³n MAC de la tarjeta de interfaz de red que haya enviado el paquete. Para excluir una direcciÃ³n MAC de la regla, coloque un signo de admiraciÃ³n (<code class="option">!</code>) luego de la opciÃ³n de correspondencia <code class="option">--mac-source</code>.
								</div></li></ul></div></li></ul></div><div class="para">
					Vea en la pÃ¡gina man de <code class="command">iptables</code> para mÃ¡s opciones de comparaciÃ³n disponibles a travÃ©s de mÃ³dulos.
				</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-IPTables_Match_Options-ICMP_Protocol.html"><strong>Anterior</strong>2.9.3.4.3. Protocolo ICMP</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Command_Options_for_IPTables-Target_Options.html"><strong>Siguiente</strong>2.9.3.5. Target Options</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-IPTables_Match_Options-ICMP_Protocol.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.9.3.4.3. Protocolo ICMP</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Command_Options_for_IPTables-IPTables_Match_Options.html" title="2.9.3.4. IPTables Match Options" /><link rel="prev" href="sect-Security_Guide-IPTables_Match_Options-UDP_Protocol.html" title="2.9.3.4.2. Protocolo UDP" /><link rel="next" href="sect-Security_Guide-IPTables_Match_Options-Additional_Match_Option_Modules.html" title="2.9.3.4.4. Additional Match Option Modules" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product 
 Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-IPTables_Match_Options-UDP_Protocol.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-IPTables_Match_Options-Additional_Match_Option_Modules.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h5 class="title" id="sect-Security_Guide-IPTables_Match_Options-ICMP_Protocol">2.9.3.4.3. Protocolo ICMP</h5></div></div></div><div class="para">
					Las siguientes opciones de coincidencias estÃ¡n disponibles en el Protocolo de Mensajes de Control de Internet (ICMP) (<code class="option">-p icmp</code>):
				</div><div class="itemizedlist"><ul><li><div class="para">
							<code class="option">--icmp-type</code> â€” Establece el nombre y nÃºmero del tipo de ICMP a corresponderse con la regla. Puede obtenerse una lista de nombres ICMP vÃ¡lidos al ingresar el comando <code class="command">iptables -p icmp -h</code>.
						</div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-IPTables_Match_Options-UDP_Protocol.html"><strong>Anterior</strong>2.9.3.4.2. Protocolo UDP</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-IPTables_Match_Options-Additional_Match_Option_Modules.html"><strong>Siguiente</strong>2.9.3.4.4. Additional Match Option Modules</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-IPTables_Match_Options-UDP_Protocol.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.9.3.4.2. Protocolo UDP</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Command_Options_for_IPTables-IPTables_Match_Options.html" title="2.9.3.4. IPTables Match Options" /><link rel="prev" href="sect-Security_Guide-Command_Options_for_IPTables-IPTables_Match_Options.html" title="2.9.3.4. IPTables Match Options" /><link rel="next" href="sect-Security_Guide-IPTables_Match_Options-ICMP_Protocol.html" title="2.9.3.4.3. Protocolo ICMP" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><
 a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Command_Options_for_IPTables-IPTables_Match_Options.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-IPTables_Match_Options-ICMP_Protocol.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h5 class="title" id="sect-Security_Guide-IPTables_Match_Options-UDP_Protocol">2.9.3.4.2. Protocolo UDP</h5></div></div></div><div class="para">
					Estas opciones de coincidencias estÃ¡n disponibles para el protocolo UDP (<code class="option">-p udp</code>):
				</div><div class="itemizedlist"><ul><li><div class="para">
							<code class="option">--dport</code> â€” Especifica el puerto de destino del paquete UDP, utilizando el nombre del servicio, el nÃºmero de puerto, o rango de nÃºmeros de puerto. La opciÃ³n de correspondencia <code class="option">--destination-port</code> es equivalente.
						</div></li><li><div class="para">
							<code class="option">--sport</code> â€” Especifica el puerto de origen del paquete UDP, utilizando el nombre del servicio, el nÃºmero de puerto, o rango de nÃºmeros de puertos. La opciÃ³n de correspondencia <code class="option">--source-port</code> es equivalente.
						</div></li></ul></div><div class="para">
					Con las opciones <code class="option">--dport</code> y <code class="option">--sport</code>, para especificar un rango vÃ¡lido de puertos, separe ambos nÃºmeros del rango con dos puntos (:). Por ejemplo: <code class="option">-p tcp --dport 3000:3200</code>. El rango vÃ¡lido mÃ¡s extenso que puede aceptarse es 0:65535.
				</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Command_Options_for_IPTables-IPTables_Match_Options.html"><strong>Anterior</strong>2.9.3.4. IPTables Match Options</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-IPTables_Match_Options-ICMP_Protocol.html"><strong>Siguiente</strong>2.9.3.4.3. Protocolo ICMP</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-IPsec_Host_to_Host_Configuration-Manual_IPsec_Host_to_Host_Configuration.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.7.6.2. Manual IPsec Host-to-Host Configuration</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Host_to_Host_Configuration.html" title="2.7.6. IPsec Host-to-Host Configuration" /><link rel="prev" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Host_to_Host_Configuration.html" title="2.7.6. IPsec Host-to-Host Configuration" /><link rel="next" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Network_to_Network_Configuration.html" title="2.7.7. IPsec Network-to-Network Configuration" /></head><body class=""><p id="title"><a class="le
 ft" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Host_to_Host_Configuration.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Network_to_Network_Configuration.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-IPsec_Host_to_Host_Configuration-Manual_IPsec_Host_to_Host_Configuration">2.7.6.2. Manual <abbr class="abbrev">IPsec</abbr> Host-to-Host Configuration</h4></div></div></div><div class="para">
				The first step in creating a connection is to gather system and network information from each workstation. For a host-to-host connection, you need the following:
			</div><div class="itemizedlist"><ul><li><div class="para">
						The IP address of each host
					</div></li><li><div class="para">
						A unique name, for example, <code class="computeroutput">ipsec1</code>. This is used to identify the <abbr class="abbrev">IPsec</abbr> connection and to distinguish it from other devices or connections.
					</div></li><li><div class="para">
						A fixed encryption key or one automatically generated by <code class="command">racoon</code>.
					</div></li><li><div class="para">
						A pre-shared authentication key that is used during the initial stage of the connection and to exchange encryption keys during the session.
					</div></li></ul></div><div class="para">
				For example, suppose Workstation A and Workstation B want to connect to each other through an <abbr class="abbrev">IPsec</abbr> tunnel. They want to connect using a pre-shared key with the value of <code class="computeroutput">Key_Value01</code>, and the users agree to let <code class="command">racoon</code> automatically generate and share an authentication key between each host. Both host users decide to name their connections <code class="computeroutput">ipsec1</code>.
			</div><div class="note"><h2>Note</h2><div class="para">
					You should choose a PSK that uses a mixture of upper- and lower-case characters, numbers and punctuation. An easily-guessable PSK constitutes a security risk.
				</div><div class="para">
					It is not necessary to use the same connection name for each host. You should choose a name that is convenient and meaningful for your installation.
				</div></div><div class="para">
				The following is the <abbr class="abbrev">IPsec</abbr> configuration file for Workstation A for a host-to-host <abbr class="abbrev">IPsec</abbr> connection with Workstation B. The unique name to identify the connection in this example is <em class="replaceable"><code>ipsec1</code></em>, so the resulting file is called <code class="filename">/etc/sysconfig/network-scripts/ifcfg-ipsec1</code>.
			</div><pre class="screen">DST=<em class="replaceable"><code>X.X.X.X</code></em>TYPE=IPSEC
ONBOOT=no
IKE_METHOD=PSK
</pre><div class="para">
				For Workstation A, <em class="replaceable"><code>X.X.X.X</code></em> is the IP address of Workstation B. For Workstation B, <em class="replaceable"><code>X.X.X.X</code></em> is the IP address of Workstation A. This connection is not set to initiate on boot-up (<code class="computeroutput">ONBOOT=no</code>) and it uses the pre-shared key method of authentication (<code class="computeroutput">IKE_METHOD=PSK</code>).
			</div><div class="para">
				The following is the content of the pre-shared key file (called <code class="filename">/etc/sysconfig/network-scripts/keys-ipsec1</code>) that both workstations need to authenticate each other. The contents of this file should be identical on both workstations, and only the root user should be able to read or write this file.
			</div><pre class="screen">IKE_PSK=Key_Value01
</pre><div class="important"><h2>Important</h2><div class="para">
					To change the <code class="filename">keys-ipsec1</code> file so that only the root user can read or edit the file, use the following command after creating the file:
				</div><pre class="screen">[root at myServer ~] # chmod 600 /etc/sysconfig/network-scripts/keys-ipsec1
</pre></div><div class="para">
				To change the authentication key at any time, edit the <code class="filename">keys-ipsec1</code> file on both workstations. <span class="emphasis"><em>Both authentication keys must be identical for proper connectivity</em></span>.
			</div><div class="para">
				The next example shows the specific configuration for the phase 1 connection to the remote host. The file is called <code class="filename"><em class="replaceable"><code>X.X.X.X</code></em>.conf</code>, where <em class="replaceable"><code>X.X.X.X</code></em> is the IP address of the remote <abbr class="abbrev">IPsec</abbr> host. Note that this file is automatically generated when the <abbr class="abbrev">IPsec</abbr> tunnel is activated and should not be edited directly.
			</div><pre class="screen">remote <em class="replaceable"><code>X.X.X.X</code></em>{
         exchange_mode aggressive, main;
         my_identifier address;
         proposal {
                 encryption_algorithm 3des;
                hash_algorithm sha1;
                authentication_method pre_shared_key;
                dh_group 2 ;
        }
}
</pre><div class="para">
				The default phase 1 configuration file that is created when an <abbr class="abbrev">IPsec</abbr> connection is initialized contains the following statements used by the Fedora implementation of IPsec:
			</div><div class="variablelist"><dl><dt><span class="term">remote <em class="replaceable"><code>X.X.X.X</code></em></span></dt><dd><div class="para">
							Specifies that the subsequent stanzas of this configuration file apply only to the remote node identified by the <em class="replaceable"><code>X.X.X.X</code></em> IP address.
						</div></dd><dt><span class="term">exchange_mode aggressive</span></dt><dd><div class="para">
							The default configuration for <abbr class="abbrev">IPsec</abbr> on Fedora uses an aggressive authentication mode, which lowers the connection overhead while allowing configuration of several <abbr class="abbrev">IPsec</abbr> connections with multiple hosts.
						</div></dd><dt><span class="term">my_identifier address</span></dt><dd><div class="para">
							Specifies the identification method to use when authenticating nodes. Fedora uses IP addresses to identify nodes.
						</div></dd><dt><span class="term">encryption_algorithm 3des</span></dt><dd><div class="para">
							Specifies the encryption cipher used during authentication. By default, <em class="firstterm">Triple Data Encryption Standard</em> (<acronym class="acronym">3DES</acronym>) is used.
						</div></dd><dt><span class="term">hash_algorithm sha1;</span></dt><dd><div class="para">
							Specifies the hash algorithm used during phase 1 negotiation between nodes. By default, Secure Hash Algorithm version 1 is used.
						</div></dd><dt><span class="term">authentication_method pre_shared_key</span></dt><dd><div class="para">
							Specifies the authentication method used during node negotiation. By default, Fedora uses pre-shared keys for authentication.
						</div></dd><dt><span class="term">dh_group 2</span></dt><dd><div class="para">
							Specifies the Diffie-Hellman group number for establishing dynamically-generated session keys. By default, modp1024 (group 2) is used.
						</div></dd></dl></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h5 class="title" id="sect-Security_Guide-Manual_IPsec_Host_to_Host_Configuration-The_Racoon_Configuration_File">2.7.6.2.1. El Archivo de ConfiguraciÃ³n Racoon</h5></div></div></div><div class="para">
					The <code class="filename">/etc/racoon/racoon.conf</code> files should be identical on all <abbr class="abbrev">IPsec</abbr> nodes <span class="emphasis"><em>except</em></span> for the <code class="command">include "/etc/racoon/<em class="replaceable"><code>X.X.X.X</code></em>.conf"</code> statement. This statement (and the file it references) is generated when the <abbr class="abbrev">IPsec</abbr> tunnel is activated. For Workstation A, the <em class="replaceable"><code>X.X.X.X</code></em> in the <code class="command">include</code> statement is Workstation B's IP address. The opposite is true of Workstation B. The following shows a typical <code class="filename">racoon.conf</code> file when the <abbr class="abbrev">IPsec</abbr> connection is activated.
				</div><pre class="screen"># Racoon IKE daemon configuration file.
# See 'man racoon.conf' for a description of the format and entries.

path include "/etc/racoon";
path pre_shared_key "/etc/racoon/psk.txt";
path certificate "/etc/racoon/certs";

sainfo anonymous
{
        pfs_group 2;
        lifetime time 1 hour ;
        encryption_algorithm 3des, blowfish 448, rijndael ;
        authentication_algorithm hmac_sha1, hmac_md5 ;
        compression_algorithm deflate ;
}
include "/etc/racoon/X.X.X.X.conf";
</pre><div class="para">
					This default <code class="filename">racoon.conf</code> file includes defined paths for <abbr class="abbrev">IPsec</abbr> configuration, pre-shared key files, and certificates. The fields in <code class="computeroutput">sainfo anonymous</code> describe the phase 2 SA between the <abbr class="abbrev">IPsec</abbr> nodes â€” the nature of the <abbr class="abbrev">IPsec</abbr> connection (including the supported encryption algorithms used) and the method of exchanging keys. The following list defines the fields of phase 2:
				</div><div class="variablelist"><dl><dt><span class="term">sainfo anonymous</span></dt><dd><div class="para">
								Denotes that SA can anonymously initialize with any peer provided that the <abbr class="abbrev">IPsec</abbr> credentials match.
							</div></dd><dt><span class="term">pfs_group 2</span></dt><dd><div class="para">
								Defines the Diffie-Hellman key exchange protocol, which determines the method by which the <abbr class="abbrev">IPsec</abbr> nodes establish a mutual temporary session key for the second phase of <abbr class="abbrev">IPsec</abbr> connectivity. By default, the Fedora implementation of <abbr class="abbrev">IPsec</abbr> uses group 2 (or <code class="computeroutput">modp1024</code>) of the Diffie-Hellman cryptographic key exchange groups. Group 2 uses a 1024-bit modular exponentiation that prevents attackers from decrypting previous <abbr class="abbrev">IPsec</abbr> transmissions even if a private key is compromised.
							</div></dd><dt><span class="term">lifetime time 1 hour</span></dt><dd><div class="para">
								This parameter specifies the lifetime of an SA and can be quantified either by time or by bytes of data. The default Fedora implementation of <abbr class="abbrev">IPsec</abbr> specifies a one hour lifetime.
							</div></dd><dt><span class="term">encryption_algorithm 3des, blowfish 448, rijndael</span></dt><dd><div class="para">
								Specifies the supported encryption ciphers for phase 2. Fedora supports 3DES, 448-bit Blowfish, and Rijndael (the cipher used in the <em class="firstterm">Advanced Encryption Standard</em>, or <acronym class="acronym">AES</acronym>).
							</div></dd><dt><span class="term">authentication_algorithm hmac_sha1, hmac_md5</span></dt><dd><div class="para">
								Lists the supported hash algorithms for authentication. Supported modes are sha1 and md5 hashed message authentication codes (HMAC).
							</div></dd><dt><span class="term">compression_algorithm deflate</span></dt><dd><div class="para">
								Defines the Deflate compression algorithm for IP Payload Compression (IPCOMP) support, which allows for potentially faster transmission of IP datagrams over slow connections.
							</div></dd></dl></div><div class="para">
					To start the connection, use the following command on each host:
				</div><pre class="screen">[root at myServer ~]# /sbin/ifup <nickname>
</pre><div class="para">
					where <nickname> is the name you specified for the <abbr class="abbrev">IPsec</abbr> connection.
				</div><div class="para">
					To test the <abbr class="abbrev">IPsec</abbr> connection, run the <code class="command">tcpdump</code> utility to view the network packets being transfered between the hosts and verify that they are encrypted via IPsec. The packet should include an AH header and should be shown as ESP packets. ESP means it is encrypted. For example:
				</div><pre class="screen">[root at myServer ~]# tcpdump -n -i eth0 host <targetSystem>

IP 172.16.45.107 > 172.16.44.192: AH(spi=0x0954ccb6,seq=0xbb): ESP(spi=0x0c9f2164,seq=0xbb)
</pre></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Host_to_Host_Configuration.html"><strong>Anterior</strong>2.7.6. IPsec Host-to-Host Configuration</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Network_to_Network_Configuration.html"><strong>Siguiente</strong>2.7.7. IPsec Network-to-Network Configuration</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-IPsec_Network_to_Network_Configuration-Manual_IPsec_Network_to_Network_Configuration.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.7.7.2. Manual IPsec Network-to-Network Configuration</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Network_to_Network_Configuration.html" title="2.7.7. IPsec Network-to-Network Configuration" /><link rel="prev" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Network_to_Network_Configuration.html" title="2.7.7. IPsec Network-to-Network Configuration" /><link rel="next" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-Starting_and_Stopping_an_IPsec_Connection.html" title="2.7.8. Starting and Stopping an IPsec Connection" /></head><body
  class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Network_to_Network_Configuration.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-Starting_and_Stopping_an_IPsec_Connection.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-IPsec_Network_to_Network_Configuration-Manual_IPsec_Network_to_Network_Configuration">2.7.7.2. Manual <abbr class="abbrev">IPsec</abbr> Network-to-Network Configuration</h4></div></div></div><div class="par
 a">
				Suppose <acronym class="acronym">LAN</acronym> A (lana.example.com) and <acronym class="acronym">LAN</acronym> B (lanb.example.com) want to connect to each other through an <abbr class="abbrev">IPsec</abbr> tunnel. The network address for <acronym class="acronym">LAN</acronym> A is in the 192.168.1.0/24 range, while <acronym class="acronym">LAN</acronym> B uses the 192.168.2.0/24 range. The gateway IP address is 192.168.1.254 for <acronym class="acronym">LAN</acronym> A and 192.168.2.254 for <acronym class="acronym">LAN</acronym> B. The <abbr class="abbrev">IPsec</abbr> routers are separate from each <acronym class="acronym">LAN</acronym> gateway and use two network devices: eth0 is assigned to an externally-accessible static IP address which accesses the Internet, while eth1 acts as a routing point to process and transmit <acronym class="acronym">LAN</acronym> packets from one network node to the remote network nodes.
			</div><div class="para">
				The <abbr class="abbrev">IPsec</abbr> connection between each network uses a pre-shared key with the value of <code class="computeroutput">r3dh4tl1nux</code>, and the administrators of A and B agree to let <code class="command">racoon</code> automatically generate and share an authentication key between each <abbr class="abbrev">IPsec</abbr> router. The administrator of <acronym class="acronym">LAN</acronym> A decides to name the <abbr class="abbrev">IPsec</abbr> connection <code class="computeroutput">ipsec0</code>, while the administrator of <acronym class="acronym">LAN</acronym> B names the <abbr class="abbrev">IPsec</abbr> connection <code class="computeroutput">ipsec1</code>.
			</div><div class="para">
				The following example shows the contents of the <code class="filename">ifcfg</code> file for a network-to-network <abbr class="abbrev">IPsec</abbr> connection for <acronym class="acronym">LAN</acronym> A. The unique name to identify the connection in this example is <em class="replaceable"><code>ipsec0</code></em>, so the resulting file is called <code class="filename">/etc/sysconfig/network-scripts/ifcfg-ipsec0</code>.
			</div><pre class="screen">TYPE=IPSEC
ONBOOT=yes
IKE_METHOD=PSK
SRCGW=192.168.1.254
DSTGW=192.168.2.254
SRCNET=192.168.1.0/24
DSTNET=192.168.2.0/24
DST=<em class="replaceable"><code>X.X.X.X</code></em>
</pre><div class="para">
				The following list describes the contents of this file:
			</div><div class="variablelist"><dl><dt><span class="term">TYPE=IPSEC</span></dt><dd><div class="para">
							Especifica el tipo de conexiÃ³n.
						</div></dd><dt><span class="term">ONBOOT=yes</span></dt><dd><div class="para">
							Specifies that the connection should initiate on boot-up.
						</div></dd><dt><span class="term">IKE_METHOD=PSK</span></dt><dd><div class="para">
							Specifies that the connection uses the pre-shared key method of authentication.
						</div></dd><dt><span class="term">SRCGW=192.168.1.254</span></dt><dd><div class="para">
							The IP address of the source gateway. For LAN A, this is the LAN A gateway, and for LAN B, the LAN B gateway.
						</div></dd><dt><span class="term">DSTGW=192.168.2.254</span></dt><dd><div class="para">
							The IP address of the destination gateway. For LAN A, this is the LAN B gateway, and for LAN B, the LAN A gateway.
						</div></dd><dt><span class="term">SRCNET=192.168.1.0/24</span></dt><dd><div class="para">
							Specifies the source network for the <abbr class="abbrev">IPsec</abbr> connection, which in this example is the network range for LAN A.
						</div></dd><dt><span class="term">DSTNET=192.168.2.0/24</span></dt><dd><div class="para">
							Specifies the destination network for the <abbr class="abbrev">IPsec</abbr> connection, which in this example is the network range for <acronym class="acronym">LAN</acronym> B.
						</div></dd><dt><span class="term">DST=X.X.X.X</span></dt><dd><div class="para">
							The externally-accessible IP address of <acronym class="acronym">LAN</acronym> B.
						</div></dd></dl></div><div class="para">
				The following example is the content of the pre-shared key file called <code class="filename">/etc/sysconfig/network-scripts/keys-ipsec<em class="replaceable"><code>X</code></em></code> (where <em class="replaceable"><code>X</code></em> is 0 for <acronym class="acronym">LAN</acronym> A and 1 for <acronym class="acronym">LAN</acronym> B) that both networks use to authenticate each other. The contents of this file should be identical and only the root user should be able to read or write this file.
			</div><pre class="screen">IKE_PSK=r3dh4tl1nux
</pre><div class="important"><h2>Important</h2><div class="para">
					To change the <code class="filename">keys-ipsec<em class="replaceable"><code>X</code></em></code> file so that only the root user can read or edit the file, use the following command after creating the file:
				</div><pre class="screen">chmod 600 /etc/sysconfig/network-scripts/keys-ipsec1
</pre></div><div class="para">
				To change the authentication key at any time, edit the <code class="filename">keys-ipsec<em class="replaceable"><code>X</code></em></code> file on both <abbr class="abbrev">IPsec</abbr> routers. <span class="emphasis"><em>Both keys must be identical for proper connectivity</em></span>.
			</div><div class="para">
				The following example is the contents of the <code class="filename">/etc/racoon/racoon.conf</code> configuration file for the <abbr class="abbrev">IPsec</abbr> connection. Note that the <code class="computeroutput">include</code> line at the bottom of the file is automatically generated and only appears if the <abbr class="abbrev">IPsec</abbr> tunnel is running.
			</div><pre class="screen"># Racoon IKE daemon configuration file.
# See 'man racoon.conf' for a description of the format and entries.
path include "/etc/racoon";
path pre_shared_key "/etc/racoon/psk.txt";
path certificate "/etc/racoon/certs";

sainfo anonymous
{
        pfs_group 2;
        lifetime time 1 hour ;
        encryption_algorithm 3des, blowfish 448, rijndael ;
        authentication_algorithm hmac_sha1, hmac_md5 ;
        compression_algorithm deflate ;
}
include "/etc/racoon/<em class="replaceable"><code>X.X.X.X</code></em>.conf"
</pre><div class="para">
				The following is the specific configuration for the connection to the remote network. The file is called <code class="filename"><em class="replaceable"><code>X.X.X.X</code></em>.conf</code> (where <em class="replaceable"><code>X.X.X.X</code></em> is the IP address of the remote <abbr class="abbrev">IPsec</abbr> router). Note that this file is automatically generated when the <abbr class="abbrev">IPsec</abbr> tunnel is activated and should not be edited directly.
			</div><pre class="screen">remote <em class="replaceable"><code>X.X.X.X</code></em>{
        exchange_mode aggressive, main;
        my_identifier address;
        proposal {
                encryption_algorithm 3des;
                hash_algorithm sha1;
                authentication_method pre_shared_key;
                dh_group 2 ;
        }
}
</pre><div class="para">
				Prior to starting the <abbr class="abbrev">IPsec</abbr> connection, IP forwarding should be enabled in the kernel. To enable IP forwarding:
			</div><div class="orderedlist"><ol><li><div class="para">
						Edit <code class="filename">/etc/sysctl.conf</code> and set <code class="computeroutput">net.ipv4.ip_forward</code> to <strong class="userinput"><code>1</code></strong>.
					</div></li><li><div class="para">
						Use el siguiente comando para habilitar los cambios:
					</div><pre class="screen">[root at myServer ~] # sysctl -p /etc/sysctl.conf
</pre></li></ol></div><div class="para">
				To start the <abbr class="abbrev">IPsec</abbr> connection, use the following command on each router:
			</div><pre class="screen">[root at myServer ~] # /sbin/ifup ipsec0
</pre><div class="para">
				The connections are activated, and both <acronym class="acronym">LAN</acronym> A and <acronym class="acronym">LAN</acronym> B are able to communicate with each other. The routes are created automatically via the initialization script called by running <code class="command">ifup</code> on the <abbr class="abbrev">IPsec</abbr> connection. To show a list of routes for the network, use the following command:
			</div><pre class="screen">[root at myServer ~] # /sbin/ip route list
</pre><div class="para">
				To test the <abbr class="abbrev">IPsec</abbr> connection, run the <code class="command">tcpdump</code> utility on the externally-routable device (eth0 in this example) to view the network packets being transfered between the hosts (or networks), and verify that they are encrypted via IPsec. For example, to check the <abbr class="abbrev">IPsec</abbr> connectivity of <acronym class="acronym">LAN</acronym> A, use the following command:
			</div><pre class="screen">[root at myServer ~] # tcpdump -n -i eth0 host <em class="replaceable"><code>lana.example.com</code></em>
</pre><div class="para">
				The packet should include an AH header and should be shown as ESP packets. ESP means it is encrypted. For example (back slashes denote a continuation of one line):
			</div><pre class="screen">12:24:26.155529 lanb.example.com > lana.example.com: AH(spi=0x021c9834,seq=0x358): \
        lanb.example.com > lana.example.com: ESP(spi=0x00c887ad,seq=0x358) (DF) \
        (ipip-proto-4)
</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Network_to_Network_Configuration.html"><strong>Anterior</strong>2.7.7. IPsec Network-to-Network Configuration</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-Starting_and_Stopping_an_IPsec_Connection.html"><strong>Siguiente</strong>2.7.8. Starting and Stopping an IPsec Connection</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Kerberos-Additional_Resources.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.6.10. Additional Resources</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Kerberos.html" title="2.6. Kerberos" /><link rel="prev" href="sect-Security_Guide-Kerberos-Setting_Up_Cross_Realm_Authentication.html" title="2.6.9. Configurando la AutenticaciÃ³n Cruzada de Reinados" /><link rel="next" href="sect-Security_Guide-Additional_Resources-Useful_Kerberos_Websites.html" title="2.6.10.2. Useful Kerberos Websites" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" hr
 ef="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Kerberos-Setting_Up_Cross_Realm_Authentication.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Additional_Resources-Useful_Kerberos_Websites.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Kerberos-Additional_Resources">2.6.10. Additional Resources</h3></div></div></div><div class="para">
			Para mÃ¡s informaciÃ³n sobre Kerberos, vaya a los siguientes recursos.
		</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Additional_Resources-Installed_Kerberos_Documentation">2.6.10.1. Installed Kerberos Documentation</h4></div></div></div><div class="itemizedlist"><ul><li><div class="para">
						The <em class="citetitle">Kerberos V5 Installation Guide</em> and the <em class="citetitle">Kerberos V5 System Administrator's Guide</em> in PostScript and HTML formats. These can be found in the <code class="filename">/usr/share/doc/krb5-server-<em class="replaceable"><code><version-number></code></em>/</code> directory (where <em class="replaceable"><code><version-number></code></em> is the version number of the <code class="command">krb5-server</code> package installed on your system).
					</div></li><li><div class="para">
						The <em class="citetitle">Kerberos V5 UNIX User's Guide</em> in PostScript and HTML formats. These can be found in the <code class="filename">/usr/share/doc/krb5-workstation-<em class="replaceable"><code><version-number></code></em>/</code> directory (where <em class="replaceable"><code><version-number></code></em> is the version number of the <code class="command">krb5-workstation</code> package installed on your system).
					</div></li><li><div class="para">
						PÃ¡ginas man de Kerberos â€” Hay un nÃºmero de pÃ¡ginas man para las varias aplicaciones y archivos de configuraciÃ³n involucrados con una implementaciÃ³n de Kerberos. La siguiente es una lista de algunas de las pÃ¡ginas man mÃ¡s importantes.
					</div><div class="variablelist"><dl><dt><span class="term">Aplicaciones Cliente</span></dt><dd><div class="itemizedlist"><ul><li><div class="para">
											<code class="command">man kerberos</code> â€” Una introducciÃ³n al sistema Kerberos que describe cÃ³mo funcionan las credenciales y provee recomendaciones para obtener y destruir tiques de Kerberos. Al final de la pÃ¡gina man hay referencias hacia otras pÃ¡ginas man relacionadas con el tema.
										</div></li><li><div class="para">
											<code class="command">man kinit</code> â€” Describe cÃ³mo usar este comando para obtener y hacer cachÃ© de un tique de garantÃa de tiques.
										</div></li><li><div class="para">
											<code class="command">man kdestroy</code> â€” Describe cÃ³mo usar este comando para destruir las credenciales de Kerberos.
										</div></li><li><div class="para">
											<code class="command">man klist</code> â€” Describe cÃ³mo usar este comando para listar las credenciales cacheadas de Kerberos.
										</div></li></ul></div></dd><dt><span class="term">Aplicaciones Administrativas</span></dt><dd><div class="itemizedlist"><ul><li><div class="para">
											<code class="command">man kadmin</code> â€” Describe cÃ³mo usar este comando para administrar con la base de datos de Kerberos V5.
										</div></li><li><div class="para">
											<code class="command">man kdb5_util</code> â€” Describe cÃ³mo usar este comando para crear y realizar funciones administrativas de bajo nivel en la base de datos de Kerberos V5.
										</div></li></ul></div></dd><dt><span class="term">Server Applications</span></dt><dd><div class="itemizedlist"><ul><li><div class="para">
											<code class="command">man krb5kdc</code> â€” Describe las opcioens de la lÃnea de comando del KDC de Kerberos V5.
										</div></li><li><div class="para">
											<code class="command">man kadmind</code> â€” Describe las opciones de la lÃnea de comando para el servidor de administraciÃ³n de Kerberos V5.
										</div></li></ul></div></dd><dt><span class="term">Configuration Files</span></dt><dd><div class="itemizedlist"><ul><li><div class="para">
											<code class="command">man krb5.conf</code> â€” Describe el formato y las opciones disponibles dentro del archivo de configuraciÃ³n para la biblioteca de Kerberos V5.
										</div></li><li><div class="para">
											<code class="command">man kdc.conf</code> â€” Describe el formato y las opciones disponibles dentro del archivo de configuraciÃ³n del AS y el KDC de Kerberos V5.
										</div></li></ul></div></dd></dl></div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Kerberos-Setting_Up_Cross_Realm_Authentication.html"><strong>Anterior</strong>2.6.9. Configurando la AutenticaciÃ³n Cruzada de R...</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Additional_Resources-Useful_Kerberos_Websites.html"><strong>Siguiente</strong>2.6.10.2. Useful Kerberos Websites</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Client.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.6.6. Configuring a Kerberos 5 Client</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Kerberos.html" title="2.6. Kerberos" /><link rel="prev" href="sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Server.html" title="2.6.5. Configuring a Kerberos 5 Server" /><link rel="next" href="sect-Security_Guide-Kerberos-Domain_to_Realm_Mapping.html" title="2.6.7. Domain-to-Realm Mapping" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.or
 g"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Server.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Kerberos-Domain_to_Realm_Mapping.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Client">2.6.6. Configuring a Kerberos 5 Client</h3></div></div></div><div class="para">
			Configurar un cliente de Kerberos 5 es menos complicado que configurar un servidor. Como mÃnimo, instale los paquetes del cliente y otÃ³rguele a cada cliente un archivo de configuraciÃ³n <code class="filename">krb5.conf</code> vÃ¡lido. Mientras que <code class="command">ssh</code> y <code class="command">slogin</code> son los mÃ©todos preferidos para loguearse remotamente en sistemas cliente, las versiones Kerberizadas de <code class="command">rsh</code> y <code class="command">rlogin</code> siguen estando disponibles, aunque para habilitarlas es necesario relizar algunos cambios adicionales en la configuraciÃ³n.
		</div><div class="procedure"><ol class="1"><li><div class="para">
					AsegÃºrese que la sincronizaciÃ³n del tiempo existe entre el cliente Kerberos y KDC. Vaya a <a class="xref" href="sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Server.html" title="2.6.5. Configuring a Kerberos 5 Server">SecciÃ³nÂ 2.6.5, â€œConfiguring a Kerberos 5 Serverâ€</a> para mÃ¡s informaciÃ³n. AdemÃ¡s, verifique que el DNS estÃ¡ funcionando apropiadamente en el cliente Kerberos antes de continuar con los programas cliente de Kerberos.
				</div></li><li><div class="para">
					Instale los paquetes <code class="filename">krb5-libs</code> y <code class="filename">krb5-workstation</code> en todas las mÃ¡quinas clientes. Provea un archivo <code class="filename">/etc/krb5.conf</code> vÃ¡lido para cada cliente (normalmente este puede ser el mismo archivo <code class="filename">krb5.conf</code> usado por el KDC).
				</div></li><li><div class="para">
					Antes que una estaciÃ³n de trabajo del reinado pueda utilizar a Kerberos para autenticar los usuarios que se conectan mediante <code class="command">ssh</code>, o mediante los <code class="command">rsh</code> o <code class="command">rlogin</code> Kerberizados, debe tener su propio equipo principal en la base de datos de Kerberos. Los programas de servidor <code class="command">sshd</code>, <code class="command">kshd</code>, y <code class="command">klogind</code>, necesitan todos acceder a las llaves para los servicios del <span class="emphasis"><em>host</em></span> principal. AdemÃ¡s, para poder utilizar los servicios kerberizados <code class="command">rsh</code> y <code class="command">rlogin</code>, esa estaciÃ³n de trabajo debe tener el paquete <code class="filename">xinetd</code> instalado.
				</div><div class="para">
					Al utilizar <code class="command">kadmin</code> se agrega un prinicipal de equipo para la estaciÃ³n de trabajo en el KDC. En este caso, la instancia es el nombre del equipo de la estaciÃ³n de trabajo. Utilice la opciÃ³n <code class="command">-randkey</code> para el comando <code class="command">addprinc</code> de <code class="command">kadmin</code>, para crear el principal y asignarle una llave en forma azarosa:
				</div><pre class="screen">addprinc -randkey host/<em class="replaceable"><code>bla.ejemplo.com</code></em>
</pre><div class="para">
					Ahora que se ha creado el principal, las claves se pueden extraer para la estaciÃ³n trabajo ejecutando <code class="command">kadmin</code> <span class="emphasis"><em>en la misma estaciÃ³n de trabajo</em></span> y usando el comando <code class="command">ktadd</code> dentro de <code class="command">kadmin</code>:
				</div><pre class="screen">ktadd -k /etc/krb5.keytab host/<em class="replaceable"><code>bla.ejemplo.com</code></em>
</pre></li><li><div class="para">
					Para usar otros servicios de red kerberizados, primero deben iniciarse. Abajo estÃ¡ una lista de los servicios kerberizados comÃºnes y las instrucciones de cÃ³mo habilitarlos:
				</div><div class="itemizedlist"><ul><li><div class="para">
							<code class="command">ssh</code> â€” OpenSSH usa GSS-API para autenticar los usuarios en los servidores si la configuraciÃ³n del cliente y del servidor tienen ambas <code class="option">GSSAPIAuthentication</code> habilitado. Si el cliente tiene tambiÃ©n <code class="option">GSSAPIDelegateCredentials</code> habilitado, las credenciales del usuario se hacen disponibles en el sistema remoto.
						</div></li><li><div class="para">
							<code class="command">rsh</code> y <code class="command">rlogin</code> â€” Para usar las versiones kerberizadas de <code class="command">rsh</code> y <code class="command">rlogin</code>, habilite <code class="command">klogin</code>, <code class="command">eklogin</code> y <code class="command">kshell</code>.
						</div></li><li><div class="para">
							Telnet â€” Para usar Telnet kerberizado, debe habilitar <code class="command">krb5-telnet</code>.
						</div></li><li><div class="para">
							FTP â€” Para proveer acceso FTP, crear y extraer una clave para el principal con una raÃz de <code class="computeroutput">ftp</code>. AsegÃºrese de poner la instancia al nombre de equipo completo del servidor FTP, luego habilite <code class="command">gssftp</code>.
						</div></li><li><div class="para">
							IMAP â€” Para utilizar un servidor kerberizado IMAP, el paquete <code class="filename">cyrus-imap</code> utilizarÃ¡ Kerberos 5, si tambiÃ©n se encuentra instalado el paquete <code class="filename">cyrus-sasl-gssapi</code>. El paquete <code class="filename">cyrus-sasl-gssapi</code> contiene el complemento Cyrus SASL que tiene soporte para autenticaciÃ³n GSS-API. Cyrus IMAP deberÃa funcionar correctamente con Kerberos siempre y cuando el usuario <code class="command">cyrus</code> sea capaz de encontrar la llave correspondiente en <code class="filename">/etc/krb5.keytab</code>, y que la raÃz para el principal estÃ¡ definida para <code class="command">imap</code> (creada con <code class="command">kadmin</code>).
						</div><div class="para">
							Una alternativa a <code class="filename">cyrus-imap</code> se puede encontrar en el paquete <code class="command">dovecot</code>, que tambiÃ©n se incluye en Fedora. Este paquete contiene un servidor IMAP pero no da soporte a GSS-API y Kerberos por el momento.
						</div></li><li><div class="para">
							CVS â€” Para usar un servidor CVS kerberizado, <code class="command">gserver</code> usa un principal con una raÃz de <code class="computeroutput">cvs</code> y por lo demÃ¡s es idÃ©ntico al servidor CVS <code class="command">pserver</code>.
						</div></li></ul></div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Server.html"><strong>Anterior</strong>2.6.5. Configuring a Kerberos 5 Server</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Kerberos-Domain_to_Realm_Mapping.html"><strong>Siguiente</strong>2.6.7. Domain-to-Realm Mapping</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Server.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.6.5. Configuring a Kerberos 5 Server</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Kerberos.html" title="2.6. Kerberos" /><link rel="prev" href="sect-Security_Guide-Kerberos-Kerberos_and_PAM.html" title="2.6.4. Kerberos y PAM" /><link rel="next" href="sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Client.html" title="2.6.6. Configuring a Kerberos 5 Client" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Com
 mon_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Kerberos-Kerberos_and_PAM.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Client.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Server">2.6.5. Configuring a Kerberos 5 Server</h3></div></div></div><div class="para">
			Cuando se configure Kerberos, primero instale el KDC. Si es necesario configurar servidores esclavos, instale el maestro primero.
		</div><div class="para">
			Para configurar el primer KDC de Kerberos, siga estos pasos:
		</div><div class="procedure"><ol class="1"><li><div class="para">
					AsegÃºrese que la sincronizaciÃ³n de hora y DNS estÃ©n funcionando correctamente en todos los clientes y mÃ¡quinas del servidor antes de continuar Kerberos. Preste una atenciÃ³n especial a la sincronizaciÃ³n entre el servidor Kerberos y sus clientes. Si la diferencia horaria entre el servidor y el cliente es mayor a cinco minutos (esto es configurable en Kerberos 5), los clientes de Kerberos no podrÃ¡n autenticarse en el servidor. Esta sincronizaciÃ³n es necesaria para prevenir que un atacante utilice un comprobante antiguo de Kerberos enmascarado como el de un usuario vÃ¡lido.
				</div><div class="para">
					Es recomendable configurar una red cliente/servidor compatible con el Protocolo de Horario de Red (NTP, por las siglas en inglÃ©s de Network Time Protocol), aÃºn cuando no se estÃ© utilizando Kerberos. Fedora incluye el paquete <code class="filename">ntp</code> para este propÃ³sito. Consulte <code class="filename">/usr/share/doc/ntp-<em class="replaceable"><code><version-number></code></em>/index.html</code> (donde <em class="replaceable"><code><version-number></code></em> es el nÃºmero de versiÃ³n del paquete <code class="filename">ntp</code> instalado en su sistema) para conocer detalles acerca de cÃ³mo configurar servidores con Protocolos de Horario de Red, o <a href="http://www.ntp.org">http://www.ntp.org</a>, para obtener mÃ¡s informaciÃ³n acerca de NTP.
				</div></li><li><div class="para">
					Instale los paquetes <code class="filename">krb5-libs</code>, <code class="filename">krb5-server</code> y <code class="filename">krb5-workstation</code> en la mÃ¡quina dedicada que correrÃ¡ KDC. Esta mÃ¡quina necesita ser muy segura â€” si es posible, no debe correr ningÃºn otro servicio mÃ¡s que KDC.
				</div></li><li><div class="para">
					Edite los archivos de configuraciÃ³n <code class="filename">/etc/krb5.conf</code> y <code class="filename">/var/kerberos/krb5kdc/kdc.conf</code> para reflejar el nombre del reinado y los mapeos dominio-a-reinado. Un reinado simple puede ser construido reemplazando instancias de <em class="replaceable"><code>EJEMPLO.COM</code></em> y <em class="replaceable"><code>ejemplo.com</code></em> con el nombre correcto del dominio â€” siendo seguro mantener la forma correcta de los nombres en mayÃºscula y en mÃnuscula â€” y cambiando el KDC de <em class="replaceable"><code>kerberos.example.com</code></em> al nombre del servidor kerberos. Por convenciÃ³n, todos los nombres de reinados se esceriben en mayÃºsculas, y todos los nombres de equipos y de dominios DNS en minÃºsuclas. Para obtener informaciÃ³n detallada acerca de los formatos de estos archivos de configuraciÃ³n, consulte sus respectivas pÃ¡ginas man.
				</div></li><li><div class="para">
					Crear la base de datos usando el utilitario <code class="command">kdb5_util</code> desde una terminal:
				</div><pre class="screen">/usr/kerberos/sbin/kdb5_util create -s
</pre><div class="para">
					El comando <code class="command">create</code> genera la base de datos que almacena las llaves para el reinado de Kerberos. El interruptor <code class="command">-s</code> obliga a la creaciÃ³n de un archivo <em class="firstterm">stash</em> en cual la llave del servidor principal es almacenada. Si no existe un archivo stash desde donde poder leer la llave, el servidor kerberos (<code class="command">krb5kdc</code>) le pedirÃ¡ al usuario que ingrese la contraseÃ±a principal del servidor (que puede ser ytilizada para generar nuevamente la llave) cada vez que se inicie.
				</div></li><li><div class="para">
					Edite el archivo <code class="filename">/var/kerberos/krb5kdc/kadm5.acl</code>. Este archivo es usado por <code class="command">kadmind</code> para determinar quÃ© principales tienen acceso administrativo a la base de datos de Kerberos y sus niveles de acceso. La mayorÃa de las organizaciones pueden obtenerlo por una Ãºnica lÃnea:
				</div><pre class="screen">*/admin at EJEMPLO.COMÂ Â *
</pre><div class="para">
					La mayorÃa de los usuarios de representan en la base de datos por un principal Ãºnico (con una instancia <span class="emphasis"><em>NULL</em></span>, o vacÃa, tal como <span class="emphasis"><em>joe at EJEMPLO.COM</em></span>). En esta configuraciÃ³n, los usuarios con un segundo principal con una instancia de <span class="emphasis"><em>admin</em></span> (por ejemplo, <span class="emphasis"><em>joe/admin at EJEMPLO.COM</em></span>) pueden manejar con poder completo sobre el territorio de la base de datos de Kerberos.
				</div><div class="para">
					DespuÃ©s de que se inicie <code class="command">kadmind</code> en el servidor, cualquier usuario puede acceder sus servicios ejecutando <code class="command">kadmin</code> en cualquier cliente o servidores en el reino. Sin embargo, sÃ³lo los usuarios listados en el archivo <code class="filename">kadm5.acl</code> pueden modificar la base de datos de ninguna forma, excepto para cambiar sus propias contraseÃ±as.
				</div><div class="note"><h2>Note</h2><div class="para">
						La herramienta <code class="command">kadmin</code> permite la comunicaciÃ³n con el servidor <code class="command">kadmind</code> a travÃ©s de la red, y utiliza kerberos para manipular la autenticaciÃ³n. Consecuentemente, el primer principal debe existir previamente antes de intentar conectarse con el servidor a travÃ©s de la red para administrarlo. Genere el primer principal con el comando <code class="command">kadmin.local</code>, que ha sido especÃficamente diseÃ±ado para ser utilizado en el mismo equipo en el que funciona el KDC, y no utiliza Kerberos para su autenticaciÃ³n.
					</div></div><div class="para">
					Ingrese el comando siguiente <code class="command">kadmin.local</code> en la terminal KDC para crear el primer principal:
				</div><pre class="screen">/usr/kerberos/sbin/kadmin.local -q "addprinc <em class="replaceable"><code>username</code></em>/admin"
</pre></li><li><div class="para">
					Start Kerberos using the following commands:
				</div><pre class="screen">/sbin/service krb5kdc start
/sbin/service kadmin start
/sbin/service krb524 start
</pre></li><li><div class="para">
					Agregue prinicipales para los usuarios mediante el comando <code class="command">addprinc</code> dentro de <code class="command">kadmin</code>. <code class="command">kadmin</code> y <code class="command">kadmin.local</code> son interfases de lÃneas de comando al KDC. Como este, existen disponibles otros comandos â€” como por ejemplo <code class="command">addprinc</code> â€” luego de iniciar el programa <code class="command">kadmin</code>. Para obtener mas informaciÃ³n, consulte la pÃ¡gina man de <code class="command">kadmin</code>.
				</div></li><li><div class="para">
					Verifique que KDC estÃ¡ emitiendo tiques. Primero, corra <code class="command">kinit</code> para obtener un tique y guardarlo en un archivo cache de credencial. Luego, use <code class="command">klist</code> para ver la lista de credenciales en el cachÃ© y use <code class="command">kdestroy</code> para destruir el cachÃ© y las credenciales que contiene.
				</div><div class="note"><h2>Note</h2><div class="para">
						Por defecto, <code class="command">kinit</code> intenta autenticarse utilizando el mismo nombre de usuario del de inicio de sesiÃ³n (no el del servidor Kerberos). Si ese nombre de usuario no se corresponde con un prinicipal en la base de datos de Kerberos, <code class="command">kinit</code> envÃa un mensaje de error. Si eso sucede, indiquele a <code class="command">kinit</code> el nombre del principal correcto, como un argumento en la lÃnea de comando (<code class="command">kinit <em class="replaceable"><code><principal></code></em></code>).
					</div></div></li></ol></div><div class="para">
			Una vez que estos pasos sean completados, el servidor Kerberos ya deberÃa estar listo y ejecutÃ¡ndose.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Kerberos-Kerberos_and_PAM.html"><strong>Anterior</strong>2.6.4. Kerberos y PAM</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Client.html"><strong>Siguiente</strong>2.6.6. Configuring a Kerberos 5 Client</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Kerberos-Domain_to_Realm_Mapping.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.6.7. Domain-to-Realm Mapping</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Kerberos.html" title="2.6. Kerberos" /><link rel="prev" href="sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Client.html" title="2.6.6. Configuring a Kerberos 5 Client" /><link rel="next" href="sect-Security_Guide-Kerberos-Setting_Up_Secondary_KDCs.html" title="2.6.8. Setting Up Secondary KDCs" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><
 img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Client.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Kerberos-Setting_Up_Secondary_KDCs.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Kerberos-Domain_to_Realm_Mapping">2.6.7. Domain-to-Realm Mapping</h3></div></div></div><div class="para">
			Cuando un cliente intenta acceder un servicio que corre en un servidor particular, sabe el nombre del (<span class="emphasis"><em>equipo</em></span>) del servicio y el nombre del servidor (<span class="emphasis"><em>foo.ejemplo.com</em></span>), pero como se pueden desplegar mÃ¡s de un reinado en su red, debe averiguar el nombre del reinado en el que reside el servicio.
		</div><div class="para">
			Por defecto, el nombre del territorio se toma como el nombre de dominio DNS del servidor, en mayÃºsculas.
		</div><div class="literallayout"><p>foo.ejemplo.orgÂ â†’Â EJEMPLO.ORG<br />
Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â foo.ejemplo.comÂ â†’Â EJEMPLO.COM<br />
Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â foo.hq.ejemplo.comÂ â†’Â HQ.EJEMPLO.COM<br />
</p></div><div class="para">
			En algunas configuraciones esto serÃ¡ suficiente, pero en otras, el nombre del reinado derivado serÃ¡ el nombre de un reinado no existente. En estos casos, el mapeo desde el nombre del dominio DNS del servidor, hacia su reinado, debe estar especificado en la secciÃ³n <span class="emphasis"><em>domain_realm</em></span> del sistema <code class="filename">krb5.conf</code> del cliente. Por ejemplo:
		</div><pre class="screen">[domain_realm]
.ejemplo.com = EJEMPLO.COM
ejemplo.com = EJEMPLO.COM
</pre><div class="para">
			En la configuraciÃ³n de arriba se especifica dos mapeos. El primero especifica que cualquier sistema en el dominio de DNS "ejemplo.com" pertenecen al reinado <span class="emphasis"><em>EJEMPLO.COM</em></span>. El segundo especifica que el nombre exacto "ejemplo.com" estÃ¡ tambiÃ©n en el reinado. (La distinciÃ³n entre el dominio y un equipo especÃfico se marca por la presencia o ausencia del "." inicial.) El mapeo tambiÃ©n se puede almacenar directamente en el DNS.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Client.html"><strong>Anterior</strong>2.6.6. Configuring a Kerberos 5 Client</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Kerberos-Setting_Up_Secondary_KDCs.html"><strong>Siguiente</strong>2.6.8. Setting Up Secondary KDCs</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Kerberos-How_Kerberos_Works.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.6.3. How Kerberos Works</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Kerberos.html" title="2.6. Kerberos" /><link rel="prev" href="sect-Security_Guide-Kerberos-Kerberos_Terminology.html" title="2.6.2. Kerberos Terminology" /><link rel="next" href="sect-Security_Guide-Kerberos-Kerberos_and_PAM.html" title="2.6.4. Kerberos y PAM" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png"
  alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Kerberos-Kerberos_Terminology.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Kerberos-Kerberos_and_PAM.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Kerberos-How_Kerberos_Works">2.6.3. How Kerberos Works</h3></div></div></div><div class="para">
			Kerberos se diferencia de los mÃ©todos de autenticaciÃ³n de tipo nombre de usuario/contraseÃ±a. En lugar de autenticar cada usuario en cada servicio de red, Kerberos utiliza encriptaciones simÃ©tricas y un servicio adicional confiable (un KDC), para autenticar usuarios en conjunto de servicios de red. Cuando un usuario se autentica en el KDC, el KDC devuelve a la mÃ¡quina del usuario en cuestiÃ³n un comprobante especÃfico para esa sesiÃ³n, y cualquier servicio kerberizado busca el comprobante en la mÃ¡quina del usuario, en lugar de pedir que el usuario se autentique utilizando una contraseÃ±a.
		</div><div class="para">
			Cuando un usuario kerberizado de una red se loguea en su estaciÃ³n de trabajo, su principal es enviado al KDC como parte de un pedido para un TGT del servidor de AutenticaciÃ³n. Este pedido puede ser enviado por el programa de logueo de modo que sea transparente para el usuario, o puede ser enviado por el programa <code class="command">kinit</code> luego que el usuario se haya logueado.
		</div><div class="para">
			El KDC entonces verifica con el principal en su base de datos. Si el principal es encontrado, el KDC crea un TGT, que se encripta usando la clave del usuario y se lo devuelve a ese usuario.
		</div><div class="para">
			El login, o programa <code class="command">kinit</code> en el cliente que decripta el TGT utilizando la clave del usuario, que se analiza desde la contraseÃ±a del usuario. La clave del usuario es utilizada sÃ³lo en la mÃ¡quina cliente y que <span class="emphasis"><em>no</em></span> se transmite en la red.
		</div><div class="para">
			El TGT es configurado para que caduque en un determinado perÃodo de tiempo (generalmente de diez a veinticuatro horas), y es almacenado en el cachÃ© de credenciales en la mÃ¡quina del cliente. Un tiempo de expiraciÃ³n es definido para que, en el supuesto caso que exista un TGT vulnerado, pueda ser utilizado por un atacante sÃ³lo durante un breve perÃodo de tiempo. Luego que se ha emitido un TGT, el usuario no necesita reingresar su contraseÃ±a hasta que este no expire, o hasta que haya finalizado su sesiÃ³n, y haya vuelto a iniciarla.
		</div><div class="para">
			Siempre que el usuario necesite acceso a un servicio de red, el software del cliente utiliza el TGT para pedirle al TGS un nuevo comprobante especÃficamente para ese servicio. El comprobante del servicio es entonces utilizado para autenticar de manera transparente al usuario frente al servicio en cuestiÃ³n.
		</div><div class="warning"><h2>Warning</h2><div class="para">
				El sistema Kerberos puede ser vulnerado si un usuario en la red se autentica frente a un servicio no kerberizado transmitiendo una contraseÃ±a con formato de texto simple. La utilizaciÃ³n de servicios no kerberizados es altamente desalentada. Entre tales servicios se encuentra Telnet y FTP. Es preferible la utilizaciÃ³n de otros protocolos encriptados, como servicios asegurados mediante SSH o SSL, aunque no es lo ideal.
			</div></div><div class="para">
			Este es solamente un resumen amplio de cÃ³mo funciona la autenticaciÃ³n de Kerberos. Vaya a <a class="xref" href="sect-Security_Guide-Kerberos-Additional_Resources.html" title="2.6.10. Additional Resources">SecciÃ³nÂ 2.6.10, â€œAdditional Resourcesâ€</a> para mÃ¡s enlaces con informaciÃ³n mÃ¡s detallada.
		</div><div class="note"><h2>Note</h2><div class="para">
				Kerberos depende de los siguientes servicios de red para funcionar correctamente. 
				<div class="itemizedlist"><ul><li><div class="para">
							SincronizaciÃ³n de reloj aproximado entre las mÃ¡quinas de la red.
						</div><div class="para">
							Un programa de sincronizaciÃ³n de relojes deberÃa ser configurado para la red, como por ejemplo <code class="command">ntpd</code>. Consulte <code class="filename">/usr/share/doc/ntp-<em class="replaceable"><code><version-number></code></em>/index.html</code> para obtener mÃ¡s detalles acerca de cÃ³mo definir servidores de Protocolos de Horarios de Red (donde <em class="replaceable"><code><version-number></code></em>) es el nÃºmero de versiÃ³n del paquete <code class="filename">ntp</code> instalado en su sistema).
						</div></li><li><div class="para">
							Domain Name Service (DNS).
						</div><div class="para">
							DeberÃa asegurarse que las entradas DNS y los equipos en la red se encuentren todos configurados adecuadamente. Vea <em class="citetitle">Kerberos V5 System Administrator's Guide</em> en <code class="filename">/usr/share/doc/krb5-server-<em class="replaceable"><code><version-number></code></em></code> para obtener mauro informaciÃ³n, (donde <em class="replaceable"><code><version-number></code></em> es el nÃºmero de versiÃ³n del paquete <code class="filename">krb5-server</code> instalado en su sistema).
						</div></li></ul></div>
			</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Kerberos-Kerberos_Terminology.html"><strong>Anterior</strong>2.6.2. Kerberos Terminology</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Kerberos-Kerberos_and_PAM.html"><strong>Siguiente</strong>2.6.4. Kerberos y PAM</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Kerberos-Kerberos_Terminology.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.6.2. Kerberos Terminology</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Kerberos.html" title="2.6. Kerberos" /><link rel="prev" href="sect-Security_Guide-Kerberos.html" title="2.6. Kerberos" /><link rel="next" href="sect-Security_Guide-Kerberos-How_Kerberos_Works.html" title="2.6.3. How Kerberos Works" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /
 ></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Kerberos.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Kerberos-How_Kerberos_Works.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Kerberos-Kerberos_Terminology">2.6.2. Kerberos Terminology</h3></div></div></div><div class="para">
			Kerberos tiene su propia terminologÃa para definir varios aspectos del servicio. Antes de aprender cÃ³mo funciona Kerberos, es importante aprender los siguientes tÃ©rminos.
		</div><div class="variablelist"><dl><dt><span class="term">authentication server (AS)</span></dt><dd><div class="para">
						Un servidor que envÃa comprobantes para un servicio determinado, comprobantes que en su momento serÃ¡n enviados a los usuarios para que puedan acceder a ese servicio. El AS responde con una peticiÃ³n a las solicitudes de los clientes que, o no tienen o no han enviado sus credenciales de autenticaciÃ³n. Generalmente, para utilizar el servicio que ofrece el servidor que emite los comprobantes (TGS, por las siglas en inglÃ©s de Ticket-Granting Server), se envÃa un comprobante de obtenciÃ³n de comprobantes (TGT, Ticket-Granting Ticket). Por Ãºltimo, el AS generalmente se ejecuta en el mismo equipo que el centro de distribuciÃ³n de claves (KDC, Key Distribution Center).
					</div></dd><dt><span class="term">ciphertext</span></dt><dd><div class="para">
						Encrypted data.
					</div></dd><dt><span class="term">cliente</span></dt><dd><div class="para">
						Una entidad en la red (un usuario, equipo o aplicaciÃ³n) que puede recibir tiques desde Kerberos.
					</div></dd><dt><span class="term">credentials</span></dt><dd><div class="para">
						Un conjunto de credenciales electrÃ³nicas temporales que verifican la identidad de un cliente para un servicio particular. TambiÃ©n llamado tique.
					</div></dd><dt><span class="term">cachÃ© de credenciales o archivo de tique</span></dt><dd><div class="para">
						Un archivo que contiene las claves para encriptar las comunicaciones entre un usuario y varios servicios de red. Kerberos 5 soporta un marco de trabajo para el uso de otros tipos de cache, tales como memoria compartida, pero los archivos son los mÃ¡s completamente soportados.
					</div></dd><dt><span class="term">crypt hash</span></dt><dd><div class="para">
						Un hash de una vuelta se usa para autenticar los usuarios. Estos son mÃ¡s seguros que usar datos no encriptados, pero todavÃa son relativamente fÃ¡ciles de desencriptar para craqueadores experimentados.
					</div></dd><dt><span class="term">GSS-API</span></dt><dd><div class="para">
						La Interfaz del Programa de la AplicaciÃ³n de Servicios Generales de Seguridad (API, por las siglas en inglÃ©s de Generic Security Service Application Program Interface), es un conjunto de funciones que proveen servicios de seguridad, definida en RFC-2743, publicada por el Equipo de Tareas de IngenierÃa de Internet. La API es utilizada por servicios y clientes para autenticarse mutuamente sin que sus programas posean conocimientos especÃficos de los mecanismos subyacentes. Si un servicio de red (como por ejemplo cyrus-IMAP) utiliza GSS-API, entonces puede autenticarse mediante Kerberos.
					</div></dd><dt><span class="term">hash</span></dt><dd><div class="para">
						TambiÃ©n conocido como <em class="firstterm">valor hash</em>. Un valor generado por el paso de una cadena a travÃ©s de una <em class="firstterm">funciÃ³n hash</em>. Estos valores son tÃpicamente usados para asegurar que los datos transmitidos no fueron interceptados y modificados.
					</div></dd><dt><span class="term">funciÃ³n hash</span></dt><dd><div class="para">
						Una forma de generar una "huella digital" desde los datos de entrada. Estas funciones reacomodan, trasponen o alteran de otras formas para producir un <em class="firstterm">valor hash</em>.
					</div></dd><dt><span class="term">key</span></dt><dd><div class="para">
						Los datos usados cuando se encriptan o desencriptan otros datos. Los datos encriptados no pueden ser desencriptados sin una clave apropiada o una extrema buena suerte de parte del craqueador.
					</div></dd><dt><span class="term">centro de distribuciÃ³n de claves (KDC)</span></dt><dd><div class="para">
						Un servicio que emite tiques de Kerberos, y que usualmente corre en el mismo equipo que el servidor de garantÃa de tique (TGS).
					</div></dd><dt><span class="term">keytab (or key table)</span></dt><dd><div class="para">
						Un archivo que incluye una lista no encriptada de principales con sus respectivas claves. Los servidores obtienen las claves que necesitan desde los archivos keytab en lugar de utilizar <code class="command">kinit</code>. El archivo keytab establecido por defecto es <code class="filename">/etc/krb5.keytab</code>. El servidor que administra el KDC <code class="command">/usr/kerberos/sbin/kadmind</code>, es el Ãºnico servicio que utiliza cualquier otro archivo (utiliza <code class="filename">/var/kerberos/krb5kdc/kadm5.keytab</code>).
					</div></dd><dt><span class="term">kinit</span></dt><dd><div class="para">
						El comando <code class="command">kinit</code> permite a un principal que ya ingresÃ³ obtener y hacer cachÃ© del tique inicial de garantÃa de tiques (TGT). Vaya a la pÃ¡gina man de <code class="command">kinit</code> para mÃ¡s informaciÃ³n.
					</div></dd><dt><span class="term">principal (or principal name)</span></dt><dd><div class="para">
						El principal es el nombre Ãºnico de un servicio o de un usuario al que le es permitido autenticarse mediante Kerberos. El principal tiene la forma de <code class="computeroutput">root[/instance]@REALM</code>. Para un usuario tÃpico, el root es el mismo que su ID de inicio de sesiÃ³n. La <code class="computeroutput">instance</code> es opcional. Si el principal tiene una instanci, serÃ¡ diferenciada del root con una barra ("/"). Una cadena vacÃa ("") es considerada una instancia vÃ¡lida (que difiere de la instancia <code class="computeroutput">NULL</code> establecida por defecto), pero utilizarla puede llegar a ser confuso. Todos los principales de un dominio poseen su propia clave, que para los usuarios es derivada desde una contraseÃ±a, o es un conjunto de servicios aleatorios.
					</div></dd><dt><span class="term">realm</span></dt><dd><div class="para">
						Una red que use Kerberos, compuesta de uno o mÃ¡s servidores llamados KDCs y un nÃºmero potencialmente grande de clientes.
					</div></dd><dt><span class="term">servicio</span></dt><dd><div class="para">
						A program accessed over the network.
					</div></dd><dt><span class="term">ticket</span></dt><dd><div class="para">
						Un conjunto temporal de credenciales electrÃ³nicas que verifican la identidad de un cliente para un servicio particular. TambiÃ©n llamados credenciales.
					</div></dd><dt><span class="term">servidor de garantÃas de tiques (TGS)</span></dt><dd><div class="para">
						Un servidor que emite tiques para un servicio deseado que son a su vez dados a los usuarios para acceder al servicio. El TGS corre normalmente en el mismo equipo que el KDC.
					</div></dd><dt><span class="term">ticket-granting ticket (TGT)</span></dt><dd><div class="para">
						Un tique especial que permite al cliente obtener tiques adicionales sin aplicar nuevamente en el KDC.
					</div></dd><dt><span class="term">unencrypted password</span></dt><dd><div class="para">
						Una contraseÃ±a en texto plano, legible al humano.
					</div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Kerberos.html"><strong>Anterior</strong>2.6. Kerberos</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Kerberos-How_Kerberos_Works.html"><strong>Siguiente</strong>2.6.3. How Kerberos Works</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Kerberos-Kerberos_and_PAM.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.6.4. Kerberos y PAM</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Kerberos.html" title="2.6. Kerberos" /><link rel="prev" href="sect-Security_Guide-Kerberos-How_Kerberos_Works.html" title="2.6.3. How Kerberos Works" /><link rel="next" href="sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Server.html" title="2.6.5. Configuring a Kerberos 5 Server" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content
 /images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Kerberos-How_Kerberos_Works.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Server.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Kerberos-Kerberos_and_PAM">2.6.4. Kerberos y PAM</h3></div></div></div><div class="para">
			Los servicios kerberizados actualmente no utilizan MÃ³dulos de AutenticaciÃ³n Conectables (PAM, por las siglas en inglÃ©s de Pluggable Authentication Modules) â€” estos servicios evitan completamente a PAM. Sin embargo, las aplicaciones que utilicen PAM pueden utilizar a Kerberos para autenticarse si el mÃ³dulo <code class="filename">pam_krb5</code> (provisto en el paquete <code class="filename">pam_krb5</code>) se encuentra instalado. El paquete <code class="filename">pam_krb5</code> contiene archivos de ejemplos de configuraciÃ³n que permiten que servicios como <code class="command">login</code> o <code class="command">gdm</code> puedan autenticar usuarios al mismo tiempo que obtienen credenciales de inicio utilizando sus contraseÃ±as. Si el acceso a los servicios de red es siempre realizado utilizando servicios kerberizados, o servicios que utilicen GSS-API como por ejemplo lo es IMAP, entonces puede considerarse a la red como razonablemente segura.
		</div><div class="important"><h2>Important</h2><div class="para">
				Los administradores deben tener la precauciÃ³n de no permitir que los usuarios se autentiquen a determinados servicios de red, utilizando contraseÃ±as Kerberos. Muchos protocolos utilizados por estos servicios no encriptan las contraseÃ±as antes de enviarlas a travÃ©s de la red, destrutendo los beneficios del sistema Kerberos. Por ejemplo, los usuarios no deberÃan tener permitido autenticarse a servicios Telnet con la misma contraseÃ±a que utilizan para la autenticaciÃ³n en Kerberos.
			</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Kerberos-How_Kerberos_Works.html"><strong>Anterior</strong>2.6.3. How Kerberos Works</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Server.html"><strong>Siguiente</strong>2.6.5. Configuring a Kerberos 5 Server</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Kerberos-Setting_Up_Cross_Realm_Authentication.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.6.9. Configurando la AutenticaciÃ³n Cruzada de Reinados</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Kerberos.html" title="2.6. Kerberos" /><link rel="prev" href="sect-Security_Guide-Kerberos-Setting_Up_Secondary_KDCs.html" title="2.6.8. Setting Up Secondary KDCs" /><link rel="next" href="sect-Security_Guide-Kerberos-Additional_Resources.html" title="2.6.10. Additional Resources" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.
 org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Kerberos-Setting_Up_Secondary_KDCs.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Kerberos-Additional_Resources.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Kerberos-Setting_Up_Cross_Realm_Authentication">2.6.9. Configurando la AutenticaciÃ³n Cruzada de Reinados</h3></div></div></div><div class="para">
			La <span class="emphasis"><em>autenticaciÃ³n cruzada de reinado</em></span> es el tÃ©rmino usado para describir situaciones en que los clientes (normalmente usuarios) de un reinado usa Kerberos para autenticar con servicios (tÃpicamente procesos servidor corriendo en un sistema servidor particular) que pertenecen a otro reinado distinto al propio.
		</div><div class="para">
			Para el caso mÃ¡s simple, para que un cliente de un reinado con nombre <code class="literal">A.EJEMPLO.COM</code> acceda a un servicio en el reinado <code class="literal">B.EJEMPLO.COM</code>, ambos reinados deben compartir una clave para el principal con nombre <code class="literal">krbtgt/B.EJEMPLO.COM at A.EJEMPLO.COM</code>, y ambas claves deben tener el mismo nÃºmero de versiÃ³n de clave asociadas a ellas.
		</div><div class="para">
			Para hacer esto, debe seleccionar una contraseÃ±a o frase de paso muy fuerte y crear una entrada para el principal de ambos reinados usando kadmin.
		</div><div class="literallayout"><p><code class="computeroutput"><code class="prompt">#</code>Â <strong class="userinput"><code>kadminÂ -rÂ A.EXAMPLE.COM</code></strong></code>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â <code class="computeroutput"><code class="prompt">kadmin:</code>Â <strong class="userinput"><code>add_principalÂ krbtgt/B.EXAMPLE.COM at A.EXAMPLE.COM</code></strong></code>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â <code class="computeroutput">EnterÂ passwordÂ forÂ principalÂ "krbtgt/B.EXAMPLE.COM at A.EXAMPLE.COM":</code>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â <code class="computeroutput">Re-enterÂ passwordÂ forÂ principalÂ "krbtgt/B.EXAMPLE.COM at A.EXAMPLE.COM":</code>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â <code class="computeroutput">PrincipalÂ "krbtgt/B.EXAMPLE.COM at A.EXAMPLE.COM"Â created.</code>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â <strong class="userinput"><code>quit</code></strong>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â <code class="computeroutput"><code class="prompt">#</code>Â <strong class="userinput"><cod
 e>kadminÂ -rÂ B.EXAMPLE.COM</code></strong></code>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â <code class="computeroutput"><code class="prompt">kadmin:</code>Â <strong class="userinput"><code>add_principalÂ krbtgt/B.EXAMPLE.COM at A.EXAMPLE.COM</code></strong></code>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â <code class="computeroutput">EnterÂ passwordÂ forÂ principalÂ "krbtgt/B.EXAMPLE.COM at A.EXAMPLE.COM":</code>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â <code class="computeroutput">Re-enterÂ passwordÂ forÂ principalÂ "krbtgt/B.EXAMPLE.COM at A.EXAMPLE.COM":</code>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â <code class="computeroutput">PrincipalÂ "krbtgt/B.EXAMPLE.COM at A.EXAMPLE.COM"Â created.</code>Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â <strong class="userinput"><code>quit</code></strong><br />
</p></div><div class="para">
			Use el comando <code class="command">get_principal</code> para verificar que ambas entradas tienen un nÃºmero de versiÃ³n de claves (valores <code class="literal">kvno</code>) y tipos de encriptados coincidentes.
		</div><div class="important"><h2>El Volcado de la Base de Datos no lo hace</h2><div class="para">
				Security-conscious administrators may attempt to use the <code class="command">add_principal</code> command's <code class="literal">-randkey</code> option to assign a random key instead of a password, dump the new entry from the database of the first realm, and import it into the second. This will not work unless the master keys for the realm databases are identical, as the keys contained in a database dump are themselves encrypted using the master key.
			</div></div><div class="para">
			Clients in the <code class="literal">A.EXAMPLE.COM</code> realm are now able to authenticate to services in the <code class="literal">B.EXAMPLE.COM</code> realm. Put another way, the <code class="literal">B.EXAMPLE.COM</code> realm now <span class="emphasis"><em>trusts</em></span> the <code class="literal">A.EXAMPLE.COM</code> realm, or phrased even more simply, <code class="literal">B.EXAMPLE.COM</code> now <span class="emphasis"><em>trusts</em></span> <code class="literal">A.EXAMPLE.COM</code>.
		</div><div class="para">
			This brings us to an important point: cross-realm trust is unidirectional by default. The KDC for the <code class="literal">B.EXAMPLE.COM</code> realm may trust clients from the <code class="literal">A.EXAMPLE.COM</code> to authenticate to services in the <code class="literal">B.EXAMPLE.COM</code> realm, but the fact that it does has no effect on whether or not clients in the <code class="literal">B.EXAMPLE.COM</code> realm are trusted to authenticate to services in the <code class="literal">A.EXAMPLE.COM</code> realm. To establish trust in the other direction, both realms would need to share keys for the <code class="literal">krbtgt/A.EXAMPLE.COM at B.EXAMPLE.COM</code> service (take note of the reversed in order of the two realms compared to the example above).
		</div><div class="para">
			If direct trust relationships were the only method for providing trust between realms, networks which contain multiple realms would be very difficult to set up. Luckily, cross-realm trust is transitive. If clients from <code class="literal">A.EXAMPLE.COM</code> can authenticate to services in <code class="literal">B.EXAMPLE.COM</code>, and clients from <code class="literal">B.EXAMPLE.COM</code> can authenticate to services in <code class="literal">C.EXAMPLE.COM</code>, then clients in <code class="literal">A.EXAMPLE.COM</code> can also authenticate to services in <code class="literal">C.EXAMPLE.COM</code>, <span class="emphasis"><em>even if <code class="literal">C.EXAMPLE.COM</code> doesn't directly trust <code class="literal">A.EXAMPLE.COM</code></em></span>. This means that, on a network with multiple realms which all need to trust each other, making good choices about which trust relationships to set up can greatly reduce the amount of effort required.
		</div><div class="para">
			Ahora se enfrenta a problemas mÃ¡s convencionales: el sistema cliente debe ser configurado para que pueda deducir apropiadamente el reinado al que un servicio particular pertenece, y debe poder determinar cÃ³mo obtener las credenciales en ese reinado.
		</div><div class="para">
			Las primeras cosas primero: el nombre del principal para un servicio provisto desde un sistema servidor especÃfico en un reinado dado normalmente es parecido a:
		</div><div class="literallayout"><p>service/server.example.com at EXAMPLE.COM<br />
</p></div><div class="para">
			In this example, <span class="emphasis"><em>service</em></span> is typically either the name of the protocol in use (other common values include <span class="emphasis"><em>ldap</em></span>, <span class="emphasis"><em>imap</em></span>, <span class="emphasis"><em>cvs</em></span>, and <span class="emphasis"><em>HTTP</em></span>) or <span class="emphasis"><em>host</em></span>, <span class="emphasis"><em>server.example.com</em></span> is the fully-qualified domain name of the system which runs the service, and <code class="literal">EXAMPLE.COM</code> is the name of the realm.
		</div><div class="para">
			To deduce the realm to which the service belongs, clients will most often consult DNS or the <code class="literal">domain_realm</code> section of <code class="filename">/etc/krb5.conf</code> to map either a hostname (<span class="emphasis"><em>server.example.com</em></span>) or a DNS domain name (<span class="emphasis"><em>.example.com</em></span>) to the name of a realm (<span class="emphasis"><em>EXAMPLE.COM</em></span>).
		</div><div class="para">
			Habiendo determinado a quÃ© reinado pertenece el servicio, un cliente tiene que determinar luego el conjunto de reinados que debe contactar y en quÃ© orden debe hacerlo, para obtener las credenciales a usar en la autenticaciÃ³n con el servicio.
		</div><div class="para">
			Esto se puede hacer de una o dos formas.
		</div><div class="para">
			The default method, which requires no explicit configuration, is to give the realms names within a shared hierarchy. For an example, assume realms named <code class="literal">A.EXAMPLE.COM</code>, <code class="literal">B.EXAMPLE.COM</code>, and <code class="literal">EXAMPLE.COM</code>. When a client in the <code class="literal">A.EXAMPLE.COM</code> realm attempts to authenticate to a service in <code class="literal">B.EXAMPLE.COM</code>, it will, by default, first attempt to get credentials for the <code class="literal">EXAMPLE.COM</code> realm, and then to use those credentials to obtain credentials for use in the <code class="literal">B.EXAMPLE.COM</code> realm.
		</div><div class="para">
			The client in this scenario treats the realm name as one might treat a DNS name. It repeatedly strips off the components of its own realm's name to generate the names of realms which are "above" it in the hierarchy until it reaches a point which is also "above" the service's realm. At that point it begins prepending components of the service's realm name until it reaches the service's realm. Each realm which is involved in the process is another "hop".
		</div><div class="para">
			Por ejemplo, el uso de credenciales en <code class="literal">A.EJEMPLO.COM</code>, autenticando a un servicio en <code class="literal">B.EJEMPLO.COM</code><code class="literal">A.EJEMPLO.COM â†’ EJEMPLO.COM â†’ B.EJEMPLO.COM </code> <div class="itemizedlist"><ul><li><div class="para">
						<code class="literal">A.EJEMPLO.COM</code> y <code class="literal">EJEMPLO.COM</code> comparten una clave para <code class="literal">krbtgt/EJEMPLO.COM at A.EJEMPLO.COM</code>
					</div></li><li><div class="para">
						<code class="literal">EJEMPLO.COM</code> y <code class="literal">B.EJEMPLO.COM</code> comparten una clave <code class="literal">krbtgt/B.EJEMPLO.COM at EJEMPLO.COM</code>
					</div></li></ul></div>
		</div><div class="para">
			Otro ejemplo, usando credenciales en <code class="literal">SITIO1.VENTAS.EJEMPLO.COM</code>, para autenticar a un servicio en <code class="literal">CUALQUIERLUGAR.EJEMPLO.COM</code><code class="literal">SITIO1.VENTAS.EJEMPLO.COM â†’ VENTAS.EJEMPLO.COM â†’ EJEMPLO.COM â†’ CUALQUIERLUGAR.EJEMPLO.COM </code> <div class="itemizedlist"><ul><li><div class="para">
						<code class="literal">SITIO1.VENTAS.EJEMPLO.COM</code> y <code class="literal">VENTAS.EJEMPLO.COM</code> comparten una clave para <code class="literal">krbtgt/VENTAS.EJEMPLO.COM at SITIO1.VENTAS.EJEMPLO.COM</code>
					</div></li><li><div class="para">
						<code class="literal">VENTAS.EJEMPLO.COM</code> y <code class="literal">EJEMPLO.COM</code> comparten una clave para <code class="literal">krbtgt/EJEMPLO.COM at VENTAS.EJEMPLO.COM</code>
					</div></li><li><div class="para">
						<code class="literal">EJEMPLO.COM</code> y <code class="literal">CUALQUIERLUGAR.EJEMPO.COM</code> comparten una clave para <code class="literal">krbtgt/CUALQUIERLUGAR.EJEMPLO.COM at EJEMPLO.COM</code>
					</div></li></ul></div>
		</div><div class="para">
			Another example, this time using realm names whose names share no common suffix (<code class="literal">DEVEL.EXAMPLE.COM</code> and <code class="literal">PROD.EXAMPLE.ORG</code><code class="literal"> DEVEL.EXAMPLE.COM â†’ EXAMPLE.COM â†’ COM â†’ ORG â†’ EXAMPLE.ORG â†’ PROD.EXAMPLE.ORG </code> <div class="itemizedlist"><ul><li><div class="para">
						<code class="literal">DEVEL.EJEMPLO.COM</code> y <code class="literal">EJEMPLO.COM</code> comparten una clave para <code class="literal">krbtgt/EJEMPLO.COM at DEVEL.EJEMPLO.COM</code>
					</div></li><li><div class="para">
						<code class="literal">EJEMPLO.COM</code> y <code class="literal">COM</code> comparten una clave para <code class="literal">krbtgt/COM at EJEMPLO.COM</code>
					</div></li><li><div class="para">
						<code class="literal">COM</code> y <code class="literal">ORG</code> comparten una clave para <code class="literal">krbtgt/ORG at COM</code>
					</div></li><li><div class="para">
						<code class="literal">ORG</code> y <code class="literal">EJEMPLO.ORG</code> share a key for <code class="literal">krbtgt/EJEMPLO.ORG at ORG</code>
					</div></li><li><div class="para">
						<code class="literal">EJEMPLO.ORG</code> y <code class="literal">PROD.EJEMPLO.ORG</code> comparten una clave para <code class="literal">krbtgt/PROD.EJEMPLO.ORG at EJEMPLO.ORG</code>
					</div></li></ul></div>
		</div><div class="para">
			The more complicated, but also more flexible, method involves configuring the <code class="literal">capaths</code> section of <code class="filename">/etc/krb5.conf</code>, so that clients which have credentials for one realm will be able to look up which realm is next in the chain which will eventually lead to the being able to authenticate to servers.
		</div><div class="para">
			The format of the <code class="literal">capaths</code> section is relatively straightforward: each entry in the section is named after a realm in which a client might exist. Inside of that subsection, the set of intermediate realms from which the client must obtain credentials is listed as values of the key which corresponds to the realm in which a service might reside. If there are no intermediate realms, the value "." is used.
		</div><div class="para">
			Here's an example:
		</div><div class="literallayout"><p>[capaths]<br />
Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â A.EXAMPLE.COMÂ =Â {<br />
Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â B.EXAMPLE.COMÂ =Â .<br />
Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â C.EXAMPLE.COMÂ =Â B.EXAMPLE.COM<br />
Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â D.EXAMPLE.COMÂ =Â B.EXAMPLE.COM<br />
Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â D.EXAMPLE.COMÂ =Â C.EXAMPLE.COM<br />
Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â }<br />
</p></div><div class="para">
			En este ejemplo, los clientes en el reinado <code class="literal">A.EJEMPLO.COM</code> pueden obtener credenciales de reinados cruzados para <code class="literal">B.EJEMPLO.COM</code> directamente del KDC de <code class="literal">A.EJEMPLO.COM</code>.
		</div><div class="para">
			If those clients wish to contact a service in the<code class="literal">C.EXAMPLE.COM</code> realm, they will first need to obtain necessary credentials from the <code class="literal">B.EXAMPLE.COM</code> realm (this requires that <code class="literal">krbtgt/B.EXAMPLE.COM at A.EXAMPLE.COM</code> exist), and then use <code class="literal">those</code> credentials to obtain credentials for use in the <code class="literal">C.EXAMPLE.COM</code> realm (using <code class="literal">krbtgt/C.EXAMPLE.COM at B.EXAMPLE.COM</code>).
		</div><div class="para">
			If those clients wish to contact a service in the <code class="literal">D.EXAMPLE.COM</code> realm, they will first need to obtain necessary credentials from the <code class="literal">B.EXAMPLE.COM</code> realm, and then credentials from the <code class="literal">C.EXAMPLE.COM</code> realm, before finally obtaining credentials for use with the <code class="literal">D.EXAMPLE.COM</code> realm.
		</div><div class="note"><h2>Note</h2><div class="para">
				Sin una entrada que indique lo contrario, Kerberos asume que las relaciones de confianza de reinados cruzados forman una jerarquÃa.
			</div><div class="para">
				Los clientes en el reinado <code class="literal">A.EJEMPLO.COM</code> pueden obtener credenciales cruzadas del reinado <code class="literal">B.EJEMPLO.COM</code> directamente. Sin el "." indicando esto, el cliente intentarÃa sino usar un camino jerÃ¡rquico, en este caso:
			</div><div class="literallayout"><p>A.EXAMPLE.COMÂ â†’Â EXAMPLE.COMÂ â†’Â B.EXAMPLE.COM<br />
</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Kerberos-Setting_Up_Secondary_KDCs.html"><strong>Anterior</strong>2.6.8. Setting Up Secondary KDCs</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Kerberos-Additional_Resources.html"><strong>Siguiente</strong>2.6.10. Additional Resources</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Kerberos-Setting_Up_Secondary_KDCs.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.6.8. Setting Up Secondary KDCs</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Kerberos.html" title="2.6. Kerberos" /><link rel="prev" href="sect-Security_Guide-Kerberos-Domain_to_Realm_Mapping.html" title="2.6.7. Domain-to-Realm Mapping" /><link rel="next" href="sect-Security_Guide-Kerberos-Setting_Up_Cross_Realm_Authentication.html" title="2.6.9. Configurando la AutenticaciÃ³n Cruzada de Reinados" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://do
 cs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Kerberos-Domain_to_Realm_Mapping.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Kerberos-Setting_Up_Cross_Realm_Authentication.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Kerberos-Setting_Up_Secondary_KDCs">2.6.8. Setting Up Secondary KDCs</h3></div></div></div><div class="para">
			Por diversas razones, usted puede elegir ejecutar varios KDCs para un reinado dado. En este escenario, un KDC (el <span class="emphasis"><em>KDC maestro</em></span> conserva una copia modificable de la base de datos del reinado, y ejecuta <code class="command">kadmind</code> (que tambiÃ©n es el <span class="emphasis"><em>admin server</em></span> de su reinado), y uno o mÃ¡s KDCs (<span class="emphasis"><em>esclavos</em></span>) conservan copias de solo lectura de la base de datos, y ejecutan <code class="command">kpropd</code>.
		</div><div class="para">
			El procedimiento de propagaciÃ³n maestro-esclavo requiere que el KDC maestro vuelque su base de datos a un archivo de volcado temporal y luego transmita ese archivo a cada uno de sus esclaveos, que luego sobreescriben sus copias sÃ³lo lectura de la base de datos recibidas antes, con el contenido del archivo de volcado.
		</div><div class="para">
			Para configurar un KDC esclavo, primero asegÃºrese que los archivos <code class="filename">krb5.conf</code> y <code class="filename">kdc.conf</code> del KDC maestro fueron copiados al KDC esclavo.
		</div><div class="para">
			Inicie <code class="command">kadmin.local</code> desde una consola raÃz en el KDC maestro, y utilice su comando <code class="command">add_principal</code> para crear una nueva entrada para el servicio <span class="emphasis"><em>host</em></span> del KDC maestro, y luego utilice su comando <code class="command">ktadd</code> para definir una llave aleatoria para el servicio, y al mismo tiempo almacenarla en el archivo keytab establecido por defecto. Esta llave serÃ¡ utilizada por el comando <code class="command">kprop</code> para autenticarse al los servidores esclavos. Ustede necesitarÃ¡ hacer esto sÃ³lo una vez, sin importar la cantidad de servidores esclavos que tenga instalados.
		</div><pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>kadmin.local -r EXAMPLE.COM</code></strong>

Authenticating as principal root/admin at EXAMPLE.COM with password. 

<code class="prompt">kadmin:</code> <strong class="userinput"><code>add_principal -randkey host/masterkdc.example.com</code></strong> 

Principal "host/host/masterkdc.example.com at EXAMPLE.COM" created. 

<code class="prompt">kadmin:</code> <strong class="userinput"><code>ktadd host/masterkdc.example.com</code></strong> 

Entry for principal host/masterkdc.example.com with kvno 3, encryption type Triple DES cbc mode with HMAC/sha1 added to keytab WRFILE:/etc/krb5.keytab. 

Entry for principal host/masterkdc.example.com with kvno 3, encryption type ArcFour with HMAC/md5 added to keytab WRFILE:/etc/krb5.keytab. 

Entry for principal host/masterkdc.example.com with kvno 3, encryption type DES with HMAC/sha1 added to keytab WRFILE:/etc/krb5.keytab. 

Entry for principal host/masterkdc.example.com with kvno 3, encryption type DES cbc mode with RSA-MD5 added to keytab WRFILE:/etc/krb5.keytab.

<code class="prompt">kadmin:</code> <strong class="userinput"><code>quit</code></strong>
</pre><div class="para">
			Start <code class="command">kadmin</code> from a root shell on the slave KDC and use its <code class="command">add_principal</code> command to create a new entry for the slave KDC's <span class="emphasis"><em>host</em></span> service, and then use <code class="command">kadmin</code>'s <code class="command">ktadd</code> command to simultaneously set a random key for the service and store the random key in the slave's default keytab file. This key is used by the <code class="command">kpropd</code> service when authenticating clients.
		</div><pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>kadmin -p jimbo/admin at EXAMPLE.COM -r EXAMPLE.COM</code></strong>

Authenticating as principal jimbo/admin at EXAMPLE.COM with password. 

<code class="prompt">Password for jimbo/admin at EXAMPLE.COM: </code>

<code class="prompt">kadmin:</code> <strong class="userinput"><code>add_principal -randkey host/slavekdc.example.com</code></strong> 

Principal "host/slavekdc.example.com at EXAMPLE.COM" created. 

<code class="prompt">kadmin:</code> <strong class="userinput"><code>ktadd host/slavekdc.example.com at EXAMPLE.COM</code></strong> 

Entry for principal host/slavekdc.example.com with kvno 3, encryption type Triple DES cbc mode with HMAC/sha1 added to keytab WRFILE:/etc/krb5.keytab. 

Entry for principal host/slavekdc.example.com with kvno 3, encryption type ArcFour with HMAC/md5 added to keytab WRFILE:/etc/krb5.keytab. 

Entry for principal host/slavekdc.example.com with kvno 3, encryption type DES with HMAC/sha1 added to keytab WRFILE:/etc/krb5.keytab. 

Entry for principal host/slavekdc.example.com with kvno 3, encryption type DES cbc mode with RSA-MD5 added to keytab WRFILE:/etc/krb5.keytab. 

<code class="prompt">kadmin:</code> <strong class="userinput"><code>quit</code></strong>
</pre><div class="para">
			With its service key, the slave KDC could authenticate any client which would connect to it. Obviously, not all of them should be allowed to provide the slave's <code class="command">kprop</code> service with a new realm database. To restrict access, the <code class="command">kprop</code> service on the slave KDC will only accept updates from clients whose principal names are listed in <code class="filename">/var/kerberos/krb5kdc/kpropd.acl</code>. Add the master KDC's host service's name to that file.
		</div><div class="literallayout"><p><code class="computeroutput"><code class="prompt">#</code>Â <strong class="userinput"><code>echoÂ equipo/kdcmaestro.ejemplo.com at EJEMPLO.COMÂ >Â /var/kerberos/krb5kdc/kpropd.acl</code></strong></code><br />
</p></div><div class="para">
			Once the slave KDC has obtained a copy of the database, it will also need the master key which was used to encrypt it. If your KDC database's master key is stored in a <span class="emphasis"><em>stash</em></span> file on the master KDC (typically named <code class="filename">/var/kerberos/krb5kdc/.k5.REALM</code>, either copy it to the slave KDC using any available secure method, or create a dummy database and identical stash file on the slave KDC by running <code class="command">kdb5_util create -s</code> (the dummy database will be overwritten by the first successful database propagation) and supplying the same password.
		</div><div class="para">
			AsegÃºrese que el cortafuego del KDC esclavo permite al KDC maestro contactarlo usando el puerto 754 con TCP (<span class="emphasis"><em>krb5_prop</em></span>), e inicie el servicio <code class="command">kprop</code>. Luego, vuelva a chequear si el servicio <code class="command">kadmin</code> estÃ¡ <span class="emphasis"><em>deshabilitado</em></span>.
		</div><div class="para">
			Ahora realice una prueba manual de propagaciÃ³n de la base de datos volcando la base de datos del reinado, en el KDC maestro, al archivo de datos predeterminado desde donde el comando <code class="command">kprop</code> leerÃ¡ (<code class="filename">/var/kerberos/krb5kdc/slave_datatrans</code>) y luego use el comando <code class="command">kprop</code> para transmitir su contenido al KDC esclavo.
		</div><div class="literallayout"><p><code class="computeroutput"><code class="prompt">#</code>Â <strong class="userinput"><code>/usr/kerberos/sbin/kdb5_utilÂ dumpÂ /var/kerberos/krb5kdc/slave_datatrans</code></strong><code class="prompt">#</code>Â <strong class="userinput"><code>kpropÂ slavekdc.example.com</code></strong></code><br />
</p></div><div class="para">
			Usando <code class="command">kinit</code>, verifique que un sistema cliente cuyo <code class="filename">krb5.conf</code> lista sÃ³lo el KDC esclavo en su lista de KDCs para su reinado puede ahora obtener correctamente las credenciales iniciales del KDC esclavo.
		</div><div class="para">
			Hecho esto, simplemente cree un script que vuelque la base de datos del reinado y ejecute el comando <code class="command">kprop</code> para transmitir la base de datos a cada KDC esclavo por vez, y configure el servicio <code class="command">cron</code> para correr el script perÃodicamente.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Kerberos-Domain_to_Realm_Mapping.html"><strong>Anterior</strong>2.6.7. Domain-to-Realm Mapping</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Kerberos-Setting_Up_Cross_Realm_Authentication.html"><strong>Siguiente</strong>2.6.9. Configurando la AutenticaciÃ³n Cruzada de R...</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Kerberos.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.6. Kerberos</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="chap-Security_Guide-Securing_Your_Network.html" title="CapÃtulo 2. Securing Your Network" /><link rel="prev" href="sect-Security_Guide-Additional_Resources-Related_Books.html" title="2.5.5.3. Related Books" /><link rel="next" href="sect-Security_Guide-Kerberos-Kerberos_Terminology.html" title="2.6.2. Kerberos Terminology" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common
 _Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Additional_Resources-Related_Books.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Kerberos-Kerberos_Terminology.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h2 class="title" id="sect-Security_Guide-Kerberos">2.6. Kerberos</h2></div></div></div><div class="para">
		La seguridad e integridad del sistema dentro de la red puede ser complejo. Puede ocupar el tiempo de varios administradores sÃ³lo para rastrear quÃ© servicios se estÃ¡n corriendo en una red y la manera en que se usan esos servicios.
	</div><div class="para">
		Y mÃ¡s aÃºn, la autenticaciÃ³n de usuarios en los servicios de red pueden ser peligrosos cuando los mÃ©todos usados por el protocolo es inherentemente inseguro, como se lo evidenciÃ³ la transferencias de contraseÃ±as desencriptadas sobre una red usando los protocolos tradicionales FTP y Telnet.
	</div><div class="para">
		Kerberos es una forma de eliminar la necesidad de protocolos que permitan mÃ©todos inseguros de autenticaciÃ³n, por lo que mejora la seguridad general de la red.
	</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Kerberos-What_is_Kerberos">2.6.1. Â¿QuÃ© es Kerberos?</h3></div></div></div><div class="para">
			Kerberos es un protocolo de autenticaciÃ³n de red creado por MIT, y utiliza una criptografÃa de llave simÃ©trica <sup>[<a id="id2972072" href="#ftn.id2972072" class="footnote">14</a>]</sup> para autenticar a los usuarios de los servicios de red, lo que en pocas palabras significa que las contraseÃ±as nunca son enviadas a travÃ©s de la red.
		</div><div class="para">
			Consecuentemente, cuando los usuarios se autentican con servicios de red usando Kerberos, los usuarios no autorizados que intenten averiguar las contraseÃ±as monitoreando el trÃ¡fico de red son efectivamente bloqueados.
		</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_Kerberos-Advantages_of_Kerberos">2.6.1.1. Advantages of Kerberos</h4></div></div></div><div class="para">
				La mayorÃa de servicios convencionales de red utilizan esquemas de autenticaciÃ³n basados en contraseÃ±as. Estos esquemas piden que los usuarios se identifiquen en un servidor de red determinado mediante su nombre y contraseÃ±a. Desafortunadamente, la transmisiÃ³n de los datos para la autenticaciÃ³n de muchos servicios no es encriptada. Para que este tipo de esquemas sean seguros, la red tiene que permanecer inaccesible a los usuarios extraÃ±os a ella, y todos los equipos y todos los usuarios pertenecientes deben ser considerados confiables.
			</div><div class="para">
				AÃºn si este es el caso, una red que se encuentre conectada a Internet no puede ser concebida como una red segura. Cualquier atacante que obtenga acceso a la red puede utilizar un simple analizador de paquetes, tambiÃ©n conocido como "rastreador" de paquetes, para interceptar nombres de usuario y contraseÃ±as, comprometiendo las cuentas de usuario y la integridad de toda la infraestructura de seguridad.
			</div><div class="para">
				El objetivo primario del diseÃ±o de Kerberos es eliminar la transmisiÃ³n de contraseÃ±as encriptadas en la red. Si se usa apropiadamente, Kerberos elimina efectivamente la amenaza de los husmeadores (sniffers) de paquetes en la red.
			</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_Kerberos-Disadvantages_of_Kerberos">2.6.1.2. Disadvantages of Kerberos</h4></div></div></div><div class="para">
				Aunque Kerberos elimina una amenaza de seguridad comÃºn y severa, puede ser difÃcil de implementar por una variedad de razones:
			</div><div class="itemizedlist"><ul><li><div class="para">
						Puede ser algo muy tedioso migrar las contraseÃ±as de los usuarios de una base de datos UNIX standard, como ser por ejemplo <code class="filename">/etc/passwd</code> o <code class="filename">/etc/shadow</code> hacia una base de datos para contraseÃ±as Kerberos, ya que no hay ningÃºn mecanismo automatizado para realizar esta tarea. Consulte la pregunta 2.23 en el FAQ en lÃnea de Kerberos:
					</div><div class="para">
						<a href="http://www.nrl.navy.mil/CCS/people/kenh/kerberos-faq.html#pwconvert">http://www.nrl.navy.mil/CCS/people/kenh/kerberos-faq.html</a>
					</div></li><li><div class="para">
						Kerberos sÃ³lo tiene compatibilidad parcial con el sistema (PAM) de MÃ³dulos de AutenticaciÃ³n Enchufables usados por la mayorÃa de los servidores Fedora. vaya a <a class="xref" href="sect-Security_Guide-Kerberos-Kerberos_and_PAM.html" title="2.6.4. Kerberos y PAM">SecciÃ³nÂ 2.6.4, â€œKerberos y PAMâ€</a> para mÃ¡s informaciÃ³n al respecto.
					</div></li><li><div class="para">
						Kerberos presupone que cada usuario es confiable, pero que estÃ¡n utilizando un equipo o una red que no lo son. Su objetivo principal es prevenir la transmisiÃ³n en la red de contraseÃ±as no encriptadas. Sin embargo, si alguien mÃ¡s tiene acceso al Ãºnico equipo que envÃa los comprobantes utilizados para la autenticaciÃ³n â€” denominado el <em class="firstterm">centro de distribuciÃ³n de claves</em> (<em class="firstterm">KDC</em>, por las siglas en inglÃ©s de Key Distribution Center) â€”, ademÃ¡s del usuario correspondiente, entonces todo el sistema de autenticaciÃ³n Kerberos estÃ¡ corriendo riesgo.
					</div></li><li><div class="para">
						Para que una aplicaciÃ³n utilice Kerberos, su origen debe ser modificado para que puede realizar las llamadas apropiadas a las librerÃas de Kerberos. Las aplicaciones asÃ modificadas son consideradas como <em class="firstterm">atentas a Kerberos</em>, o <em class="firstterm">kerberizadas</em>. Para algunas, esto puede ser bastante problemÃ¡tico debido al tamaÃ±o de la aplicaciÃ³n o debido a su diseÃ±o. Para otras aplicaciones incompatibles, los cambios deben ser hechos de manera tal de permitir que el cliente y el servidor puedan comunicarse. De nuevo, esto puede necesitar una programaciÃ³n extensa. Las aplicaciones de cÃ³digo propietario que no tienen soporte para Kerberos por defecto, son por lo general las mÃ¡s problemÃ¡ticas.
					</div></li><li><div class="para">
						Kerberos es una herramienta de tipo "todo o nada". Si Kerberos es utilizado en la red, cualquier contraseÃ±a no encriptada transferida a un servicio no atento a Kerberos (o no Kerberizado), se encuentra en riesgo. Por lo tanto, la red no obtiene beneficio alguno al utilizarlo. Para asegurar una red con Kerberos, se debe utilizar verisiones kerberizadas de <span class="emphasis"><em>todas</em></span> las aplicaciones de tipo servidor/cliente que transmitan contraseÃ±as no encriptadas, o que no utilicen <span class="emphasis"><em>ninguna</em></span> de este tipo de aplicaciones.
					</div></li></ul></div></div></div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id2972072" href="#id2972072" class="para">14</a>] </sup>
				Un sistema donde tanto el cliente como el servidor comparten una clave comÃºn que es utilizada para encriptar y decriptar comunicaciones a travÃ©s de una red.
			</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Additional_Resources-Related_Books.html"><strong>Anterior</strong>2.5.5.3. Related Books</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Kerberos-Kerberos_Terminology.html"><strong>Siguiente</strong>2.6.2. Kerberos Terminology</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-LUKS_Disk_Encryption-Links_of_Interest.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.7.5. Links of Interest</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-LUKS_Disk_Encryption.html" title="3.7. LUKS Disk Encryption" /><link rel="prev" href="sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-What_you_have_just_accomplished.html" title="3.7.4. What you have just accomplished." /><link rel="next" href="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives.html" title="3.8. 7-Zip Encrypted Archives" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" 
 /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-What_you_have_just_accomplished.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-LUKS_Disk_Encryption-Links_of_Interest">3.7.5. Links of Interest</h3></div></div></div><div class="para">
			Para informaciÃ³n adicional sobre LUKS o encriptaciÃ³n de discos duros bajo Fedora, por favor visite alguno de los siguientes enlaces:
		</div><div class="itemizedlist"><ul><li><div class="para">
					<a href="http://clemens.endorphin.org/LUKS/">LUKS - ConfiguraciÃ³n de Clave Unificada de Linux (Linux Unified Key Setup) </a>
				</div></li><li><div class="para">
					<a href="https://bugzilla.redhat.com/attachment.cgi?id=161912">COMO: Crear un VolÃºmen FÃsico encriptado usando un segundo disco duro, pvmove y un CD Vivo de Fedora</a>
				</div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-What_you_have_just_accomplished.html"><strong>Anterior</strong>3.7.4. What you have just accomplished.</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives.html"><strong>Siguiente</strong>3.8. 7-Zip Encrypted Archives</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-Step_by_Step_Instructions.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.7.3. Step-by-Step Instructions</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-LUKS_Disk_Encryption.html" title="3.7. LUKS Disk Encryption" /><link rel="prev" href="sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories.html" title="3.7.2. Manually Encrypting Directories" /><link rel="next" href="sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-What_you_have_just_accomplished.html" title="3.7.4. What you have just accomplished." /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/i
 mage_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-What_you_have_just_accomplished.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-Step_by_Step_Instructions">3.7.3. Step-by-Step Instructions</h3></div></div></div><div class="orderedlist"><ol><li><div class="para">
					enter runlevel 1: <code class="code">telinit 1</code>
				</div></li><li><div class="para">
					desmonte su /home actual: <code class="code"> umount /home</code>
				</div></li><li><div class="para">
					si falla, use <code class="code">fuser</code> para encontrar y matar los procesos que retienen a /home: <code class="code">fuser -mvk /home</code>
				</div></li><li><div class="para">
					verifique que /home ya no estÃ¡ montado: <code class="code">cat /proc/mounts | grep home</code>
				</div></li><li><div class="para">
					Fill your partition with random data: <code class="code">dd if=/dev/urandom of=/dev/VG00/LV_home</code> This process takes many hours to complete.
				</div><div class="important"><h2>Important</h2><div class="para">
						The process, however, is imperative in order to have good protection against break-in attempts. Just let it run overnight.
					</div></div></li><li><div class="para">
					inicialice su particiÃ³n: <code class="code">cryptsetup --verbose --verify-passphrase luksFormat /dev/VG00/LV_home</code>
				</div></li><li><div class="para">
					abra el dispositivo nuevo encriptado: <code class="code">cryptsetup luksOpen /dev/VG00/LV_home home</code>
				</div></li><li><div class="para">
					verifique que estÃ¡ ahÃ: <code class="code">ls -l /dev/mapper | grep home</code>
				</div></li><li><div class="para">
					cree un sistema de archivo: <code class="code">mkfs.ext3 /dev/mapper/home</code>
				</div></li><li><div class="para">
					mÃ³ntelo: <code class="code">mount /dev/mapper/home /home</code>
				</div></li><li><div class="para">
					verifique que es visible: <code class="code">df -h | grep home</code>
				</div></li><li><div class="para">
					agregue lo siguiente a /etc/crypttab: <code class="code">home /dev/VG00/LV_home none</code>
				</div></li><li><div class="para">
					edite su /etc/fstab, elimine la entrada vieja de /home y agregue <code class="code">/dev/mapper/home /home ext3 defaults 1 2</code>
				</div></li><li><div class="para">
					verifique su entrada fstab: <code class="code">mount /home</code>
				</div></li><li><div class="para">
					restaure los contextos de seguridad de SELinux: <code class="code">/sbin/restorecon -v -R /home</code>
				</div></li><li><div class="para">
					reiniciar: <code class="code">shutdown -r now</code>
				</div></li><li><div class="para">
					La entrada en /etc/crypttab hace que su computadora le pregunte su frase de paso <code class="code">luks</code> al arrancar
				</div></li><li><div class="para">
					Ingrese como root y restaure su respaldo
				</div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories.html"><strong>Anterior</strong>3.7.2. Manually Encrypting Directories</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-What_you_have_just_accomplished.html"><strong>Siguiente</strong>3.7.4. What you have just accomplished.</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-What_you_have_just_accomplished.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.7.4. What you have just accomplished.</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-LUKS_Disk_Encryption.html" title="3.7. LUKS Disk Encryption" /><link rel="prev" href="sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-Step_by_Step_Instructions.html" title="3.7.3. Step-by-Step Instructions" /><link rel="next" href="sect-Security_Guide-LUKS_Disk_Encryption-Links_of_Interest.html" title="3.7.5. Links of Interest" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" 
 /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-Step_by_Step_Instructions.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-LUKS_Disk_Encryption-Links_of_Interest.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-What_you_have_just_accomplished">3.7.4. What you have just accomplished.</h3></div></div></div><div class="para">
			Felicitaciones, ahora tiene una particiÃ³n encriptada para que todos sus datos descansen mientras la computadora estÃ© apagada.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-Step_by_Step_Instructions.html"><strong>Anterior</strong>3.7.3. Step-by-Step Instructions</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-LUKS_Disk_Encryption-Links_of_Interest.html"><strong>Siguiente</strong>3.7.5. Links of Interest</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.7.2. Manually Encrypting Directories</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-LUKS_Disk_Encryption.html" title="3.7. LUKS Disk Encryption" /><link rel="prev" href="sect-Security_Guide-LUKS_Disk_Encryption.html" title="3.7. LUKS Disk Encryption" /><link rel="next" href="sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-Step_by_Step_Instructions.html" title="3.7.3. Step-by-Step Instructions" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="ri
 ght" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-LUKS_Disk_Encryption.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-Step_by_Step_Instructions.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories">3.7.2. Manually Encrypting Directories</h3></div></div></div><div class="warning"><h2>Warning</h2><div class="para">
				Following this procedure will remove all data on the partition that you are encrypting. You WILL lose all your information! Make sure you backup your data to an external source before beginning this procedure!
			</div></div><div class="para">
			Si estÃ¡ corriendo una versiÃ³n de Fedora anterior a la 9 y quiere encriptar una particiÃ³n, o si quiere encriptar una particiÃ³n despuÃ©s de la instalaciÃ³n de la versiÃ³n actual de Fedora, las siguientes instrucciones son para Ud. El ejemplo de mÃ¡s abajo muestra la encriptaciÃ³n de su particiÃ³n /home pero no se puede usar ninguna particiÃ³n.
		</div><div class="para">
			El siguiente procedimiento borrarÃ¡ todos los datos existentes, por lo que asegÃºrese que que hizo un respaldo antes de comenzar. Esto tambiÃ©n requiere que tenga una particiÃ³n separada para /home (en mi caso es /dev/VG00/LV_home). Todo lo siguiente debe ser hecho como root. No puede continuar con el paso siguiente sin haber terminado con Ã©xito con el paso actual.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-LUKS_Disk_Encryption.html"><strong>Anterior</strong>3.7. LUKS Disk Encryption</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-Step_by_Step_Instructions.html"><strong>Siguiente</strong>3.7.3. Step-by-Step Instructions</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-LUKS_Disk_Encryption.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.7. LUKS Disk Encryption</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="chap-Security_Guide-Encryption.html" title="CapÃtulo 3. Encryption" /><link rel="prev" href="Security_Guide-Encryption-Data_in_Motion-Secure_Shell.html" title="3.6. Shell Seguro" /><link rel="next" href="sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories.html" title="3.7.2. Manually Encrypting Directories" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org
 "><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="Security_Guide-Encryption-Data_in_Motion-Secure_Shell.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h2 class="title" id="sect-Security_Guide-LUKS_Disk_Encryption">3.7. LUKS Disk Encryption</h2></div></div></div><div class="para">
		La ConfiguraciÃ³n de Clave Unificada de Linux en el formato de disco (o LUKS en inglÃ©s) le permite encriptar particiones en su computadora Linux. Esto es particularmente importante cuando se trata de computadoras mÃ³biles y de medios removibles. LUKS le permite claves mÃºltiples de usuario para desencriptar una clave maestra que se usa para la encriptaciÃ³n de la particiÃ³n.
	</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-LUKS_Disk_Encryption-LUKS_Implementation_in_Fedora">3.7.1. LUKS Implementation in Fedora</h3></div></div></div><div class="para">
			Fedora 9, and later, utilizes LUKS to perform file system encryption. By default, the option to encrypt the file system is unchecked during the installation. If you select the option to encrypt you hard drive, you will be prompted for a passphrase that will be asked every time you boot the computer. This passphrase "unlocks" the bulk encryption key that is used to decrypt your partition. If you choose to modify the default partition table you can choose which partitions you want to encrypt. This is set in the partition table settings
		</div><div class="para">
			Fedora's default implementation of LUKS is AES 128 with a SHA256 hashing. Ciphers that are available are:
		</div><div class="itemizedlist"><ul><li><div class="para">
					AES - Advanced Encryption Standard - <a href="http://csrc.nist.gov/publications/fips/fips197/fips-197.pdf">FIPS PUB 197</a>
				</div></li><li><div class="para">
					Twofish (A 128-bit Block Cipher)
				</div></li><li><div class="para">
					Serpent
				</div></li><li><div class="para">
					cast5 - <a href="http://www.ietf.org/rfc/rfc2144.txt">RFC 2144</a>
				</div></li><li><div class="para">
					cast6 - <a href="http://www.ietf.org/rfc/rfc2612.txt">RFC 2612</a>
				</div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="Security_Guide-Encryption-Data_in_Motion-Secure_Shell.html"><strong>Anterior</strong>3.6. Shell Seguro</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories.html"><strong>Siguiente</strong>3.7.2. Manually Encrypting Directories</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Option_Fields-Access_Control.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.5.2.2.2. Control de Acceso</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-TCP_Wrappers_Configuration_Files-Option_Fields.html" title="2.5.2.2. Option Fields" /><link rel="prev" href="sect-Security_Guide-TCP_Wrappers_Configuration_Files-Option_Fields.html" title="2.5.2.2. Option Fields" /><link rel="next" href="sect-Security_Guide-Option_Fields-Shell_Commands.html" title="2.5.2.2.3. Shell Commands" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://doc
 s.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-TCP_Wrappers_Configuration_Files-Option_Fields.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Option_Fields-Shell_Commands.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h5 class="title" id="sect-Security_Guide-Option_Fields-Access_Control">2.5.2.2.2. Control de Acceso</h5></div></div></div><div class="para">
					Option fields also allow administrators to explicitly allow or deny hosts in a single rule by adding the <code class="option">allow</code> or <code class="option">deny</code> directive as the final option.
				</div><div class="para">
					For example, the following two rules allow SSH connections from <code class="systemitem">client-1.example.com</code>, but deny connections from <code class="systemitem">client-2.example.com</code>:
				</div><pre class="screen">sshd : client-1.example.com : allow
sshd : client-2.example.com : deny
</pre><div class="para">
					By allowing access control on a per-rule basis, the option field allows administrators to consolidate all access rules into a single file: either <code class="filename">hosts.allow</code> or <code class="filename">hosts.deny</code>. Some administrators consider this an easier way of organizing access rules.
				</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-TCP_Wrappers_Configuration_Files-Option_Fields.html"><strong>Anterior</strong>2.5.2.2. Option Fields</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Option_Fields-Shell_Commands.html"><strong>Siguiente</strong>2.5.2.2.3. Shell Commands</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Option_Fields-Expansions.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.5.2.2.4. Expansions</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-TCP_Wrappers_Configuration_Files-Option_Fields.html" title="2.5.2.2. Option Fields" /><link rel="prev" href="sect-Security_Guide-Option_Fields-Shell_Commands.html" title="2.5.2.2.3. Shell Commands" /><link rel="next" href="sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd.html" title="2.5.3. xinetd" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="C
 ommon_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Option_Fields-Shell_Commands.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h5 class="title" id="sect-Security_Guide-Option_Fields-Expansions">2.5.2.2.4. Expansions</h5></div></div></div><div class="para">
					Expansions, when used in conjunction with the <code class="command">spawn</code> and <code class="command">twist</code> directives, provide information about the client, server, and processes involved.
				</div><div class="para">
					The following is a list of supported expansions:
				</div><div class="itemizedlist"><ul><li><div class="para">
							<code class="option">%a</code> â€” Returns the client's IP address.
						</div></li><li><div class="para">
							<code class="option">%A</code> â€” Returns the server's IP address.
						</div></li><li><div class="para">
							<code class="option">%c</code> â€” Returns a variety of client information, such as the username and hostname, or the username and IP address.
						</div></li><li><div class="para">
							<code class="option">%d</code> â€” Returns the daemon process name.
						</div></li><li><div class="para">
							<code class="option">%h</code> â€” Returns the client's hostname (or IP address, if the hostname is unavailable).
						</div></li><li><div class="para">
							<code class="option">%H</code> â€” Returns the server's hostname (or IP address, if the hostname is unavailable).
						</div></li><li><div class="para">
							<code class="option">%n</code> â€” Returns the client's hostname. If unavailable, <code class="computeroutput">unknown</code> is printed. If the client's hostname and host address do not match, <code class="computeroutput">paranoid</code> is printed.
						</div></li><li><div class="para">
							<code class="option">%N</code> â€” Returns the server's hostname. If unavailable, <code class="computeroutput">unknown</code> is printed. If the server's hostname and host address do not match, <code class="computeroutput">paranoid</code> is printed.
						</div></li><li><div class="para">
							<code class="option">%p</code> â€” Returns the daemon's process ID.
						</div></li><li><div class="para">
							<code class="option">%s</code> â€”Returns various types of server information, such as the daemon process and the host or IP address of the server.
						</div></li><li><div class="para">
							<code class="option">%u</code> â€” Returns the client's username. If unavailable, <code class="computeroutput">unknown</code> is printed.
						</div></li></ul></div><div class="para">
					The following sample rule uses an expansion in conjunction with the <code class="command">spawn</code> command to identify the client host in a customized log file.
				</div><div class="para">
					When connections to the SSH daemon (<code class="systemitem">sshd</code>) are attempted from a host in the <code class="systemitem">example.com</code> domain, execute the <code class="command">echo</code> command to log the attempt, including the client hostname (by using the <code class="option">%h</code> expansion), to a special file:
				</div><pre class="screen">sshd : .example.com  \
        : spawn /bin/echo `/bin/date` access denied to %h>>/var/log/sshd.log \
        : deny
</pre><div class="para">
					Similarly, expansions can be used to personalize messages back to the client. In the following example, clients attempting to access FTP services from the <code class="systemitem">example.com</code> domain are informed that they have been banned from the server:
				</div><pre class="screen">vsftpd : .example.com \
: twist /bin/echo "421 %h has been banned from this server!"
</pre><div class="para">
					For a full explanation of available expansions, as well as additional access control options, refer to section 5 of the man pages for <code class="filename">hosts_access</code> (<code class="command">man 5 hosts_access</code>) and the man page for <code class="filename">hosts_options</code>.
				</div><div class="para">
					Refer to <a class="xref" href="sect-Security_Guide-TCP_Wrappers_and_xinetd-Additional_Resources.html" title="2.5.5. Additional Resources">SecciÃ³nÂ 2.5.5, â€œAdditional Resourcesâ€</a> for more information about TCP Wrappers.
				</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Option_Fields-Shell_Commands.html"><strong>Anterior</strong>2.5.2.2.3. Shell Commands</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd.html"><strong>Siguiente</strong>2.5.3. xinetd</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Option_Fields-Shell_Commands.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.5.2.2.3. Shell Commands</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-TCP_Wrappers_Configuration_Files-Option_Fields.html" title="2.5.2.2. Option Fields" /><link rel="prev" href="sect-Security_Guide-Option_Fields-Access_Control.html" title="2.5.2.2.2. Control de Acceso" /><link rel="next" href="sect-Security_Guide-Option_Fields-Expansions.html" title="2.5.2.2.4. Expansions" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><i
 mg src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Option_Fields-Access_Control.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Option_Fields-Expansions.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h5 class="title" id="sect-Security_Guide-Option_Fields-Shell_Commands">2.5.2.2.3. Shell Commands</h5></div></div></div><div class="para">
					Option fields allow access rules to launch shell commands through the following two directives:
				</div><div class="itemizedlist"><ul><li><div class="para">
							<code class="command">spawn</code> â€” Launches a shell command as a child process. This directive can perform tasks like using <code class="command">/usr/sbin/safe_finger</code> to get more information about the requesting client or create special log files using the <code class="command">echo</code> command.
						</div><div class="para">
							In the following example, clients attempting to access Telnet services from the <code class="systemitem">example.com</code> domain are quietly logged to a special file:
						</div><pre class="screen">in.telnetd : .example.com \
        : spawn /bin/echo `/bin/date` from %h>>/var/log/telnet.log \
        : allow
</pre></li><li><div class="para">
							<code class="command">twist</code> â€” Replaces the requested service with the specified command. This directive is often used to set up traps for intruders (also called "honey pots"). It can also be used to send messages to connecting clients. The <code class="command">twist</code> directive must occur at the end of the rule line.
						</div><div class="para">
							In the following example, clients attempting to access FTP services from the <code class="systemitem">example.com</code> domain are sent a message using the <code class="command">echo</code> command:
						</div><pre class="screen">vsftpd : .example.com \
        : twist /bin/echo "421 This domain has been black-listed. Access denied!"
</pre></li></ul></div><div class="para">
					For more information about shell command options, refer to the <code class="filename">hosts_options</code> man page.
				</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Option_Fields-Access_Control.html"><strong>Anterior</strong>2.5.2.2.2. Control de Acceso</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Option_Fields-Expansions.html"><strong>Siguiente</strong>2.5.2.2.4. Expansions</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-PAM_Configuration_File_Format-Control_Flag.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.4.3.2. Control Flag</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_File_Format.html" title="2.4.3. PAM Configuration File Format" /><link rel="prev" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_File_Format.html" title="2.4.3. PAM Configuration File Format" /><link rel="next" href="sect-Security_Guide-PAM_Configuration_File_Format-Module_Name.html" title="2.4.3.3. Module Name" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image
 _left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_File_Format.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-PAM_Configuration_File_Format-Module_Name.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-PAM_Configuration_File_Format-Control_Flag">2.4.3.2. Control Flag</h4></div></div></div><div class="para">
				Todos los mÃ³dulos PAM generan un resultado de Ã©xito o fracaso cuando se llaman. Las banderas de control le dicen a PAM quÃ© hacer con el resultado. Los mÃ³dulos se pueden apilar en un orden particular, y las banderas de control determinan cuÃ¡n importante es el Ã©xito o fracaso de un mÃ³dulo particular es para el objetivo general de autenticaciÃ³n del usuario con el servicio.
			</div><div class="para">
				Hay cuatro banderas de control predefinidas:
			</div><div class="itemizedlist"><ul><li><div class="para">
						<code class="command">required</code> â€” El resultado del mÃ³dulo debe ser exitoso para que pueda continuar la autenticaciÃ³n. Si la prueba falla en este punto, el usuario no se notifica hasta que se completan con los resultados de todas las pruebas de los mÃ³dulos que referencian a esa interfase.
					</div></li><li><div class="para">
						<code class="command">requisite</code> â€” El resultado del mÃ³dulo debe ser exitosa para que continÃºe la autenticaciÃ³n. Sin embargo, si una prueba falla en este punto, el usuario se notifica inmediatamente con un mensaje que muestra el primer fallo del mÃ³dulo <code class="command">required</code> <span class="emphasis"><em>o</em></span> <code class="command">requisite</code>.
					</div></li><li><div class="para">
						<code class="command">sufficient</code> â€” El resultado del mÃ³dulo es ignorado si falla. Sin embargo, si el resultado se un mÃ³dulo con bandera <code class="command">sufficient</code> tiene Ã©xito <span class="emphasis"><em>y</em></span> no hay mÃ³dulos previos marcados con <code class="command">required</code> han fallado, entonces no se necesitan otros resultados y el usuario es autenticado con el servicio.
					</div></li><li><div class="para">
						<code class="command">optional</code> â€” El resultado del mÃ³dulo se ignora. Un mÃ³dulo marcado como <code class="command">optional</code> sÃ³lo se vuelve ncesario para una autenticaciÃ³n exittosa cuando no hay otros mÃ³dulos referenciados en la interfase.
					</div></li></ul></div><div class="important"><h2>Important</h2><div class="para">
					El orden en el que los mÃ³dulos <code class="command">required</code> se llaman no es crÃtico. SÃ³lo las banderas <code class="command">sufficient</code> y <code class="command">requisite</code> hacen que el orden se haga importante.
				</div></div><div class="para">
				Una sintaxis de bandera de control nueva que permite un control mÃ¡s preciso estÃ¡ disponible para PAM.
			</div><div class="para">
				The <code class="command">pam.d</code> man page, and the PAM documentation, located in the <code class="filename">/usr/share/doc/pam-<em class="replaceable"><code><version-number></code></em>/</code> directory, where <em class="replaceable"><code><version-number></code></em> is the version number for PAM on your system, describe this newer syntax in detail.
			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_File_Format.html"><strong>Anterior</strong>2.4.3. PAM Configuration File Format</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-PAM_Configuration_File_Format-Module_Name.html"><strong>Siguiente</strong>2.4.3.3. Module Name</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-PAM_Configuration_File_Format-Module_Arguments.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.4.3.4. Module Arguments</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_File_Format.html" title="2.4.3. PAM Configuration File Format" /><link rel="prev" href="sect-Security_Guide-PAM_Configuration_File_Format-Module_Name.html" title="2.4.3.3. Module Name" /><link rel="next" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Sample_PAM_Configuration_Files.html" title="2.4.4. Sample PAM Configuration Files" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images
 /image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-PAM_Configuration_File_Format-Module_Name.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Sample_PAM_Configuration_Files.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-PAM_Configuration_File_Format-Module_Arguments">2.4.3.4. Module Arguments</h4></div></div></div><div class="para">
				PAM usa <em class="firstterm">argumentos</em> para pasar informaciÃ³n a un mÃ³dulo complemento durante la autenticaciÃ³n para algunos mÃ³dulos.
			</div><div class="para">
				For example, the <code class="filename">pam_userdb.so</code> module uses information stored in a Berkeley DB file to authenticate the user. Berkeley DB is an open source database system embedded in many applications. The module takes a <code class="filename">db</code> argument so that Berkeley DB knows which database to use for the requested service.
			</div><div class="para">
				El siguiente es una lÃnea tÃpica <code class="filename">pam_userdb.so</code> en una configuraciÃ³n de PAM. El <em class="replaceable"><code><direccion-del-archivo></code></em> es la direcciÃ³n completa del archivo base de datos DB de Berkeley:
			</div><pre class="screen">auth        required        pam_userdb.so db=<em class="replaceable"><code><direccion-del-archivo></code></em>
</pre><div class="para">
				Invalid arguments are <span class="emphasis"><em>generally</em></span> ignored and do not otherwise affect the success or failure of the PAM module. Some modules, however, may fail on invalid arguments. Most modules report errors to the <code class="filename">/var/log/secure</code> file.
			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-PAM_Configuration_File_Format-Module_Name.html"><strong>Anterior</strong>2.4.3.3. Module Name</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Sample_PAM_Configuration_Files.html"><strong>Siguiente</strong>2.4.4. Sample PAM Configuration Files</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-PAM_Configuration_File_Format-Module_Name.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.4.3.3. Module Name</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_File_Format.html" title="2.4.3. PAM Configuration File Format" /><link rel="prev" href="sect-Security_Guide-PAM_Configuration_File_Format-Control_Flag.html" title="2.4.3.2. Control Flag" /><link rel="next" href="sect-Security_Guide-PAM_Configuration_File_Format-Module_Arguments.html" title="2.4.3.4. Module Arguments" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" 
 /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-PAM_Configuration_File_Format-Control_Flag.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-PAM_Configuration_File_Format-Module_Arguments.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-PAM_Configuration_File_Format-Module_Name">2.4.3.3. Module Name</h4></div></div></div><div class="para">
				The module name provides PAM with the name of the pluggable module containing the specified module interface. In older versions of Fedora, the full path to the module was provided in the PAM configuration file. However, since the advent of <em class="firstterm">multilib</em> systems, which store 64-bit PAM modules in the <code class="filename">/lib64/security/</code> directory, the directory name is omitted because the application is linked to the appropriate version of <code class="filename">libpam</code>, which can locate the correct version of the module.
			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-PAM_Configuration_File_Format-Control_Flag.html"><strong>Anterior</strong>2.4.3.2. Control Flag</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-PAM_Configuration_File_Format-Module_Arguments.html"><strong>Siguiente</strong>2.4.3.4. Module Arguments</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-PAM_and_Administrative_Credential_Caching-Common_pam_timestamp_Directives.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.4.6.2. Common pam_timestamp Directives</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Administrative_Credential_Caching.html" title="2.4.6. PAM and Administrative Credential Caching" /><link rel="prev" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Administrative_Credential_Caching.html" title="2.4.6. PAM and Administrative Credential Caching" /><link rel="next" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Device_Ownership.html" title="2.4.7. PAM and Device Ownership" /></head><body class=""><p id
 ="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Administrative_Credential_Caching.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Device_Ownership.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-PAM_and_Administrative_Credential_Caching-Common_pam_timestamp_Directives">2.4.6.2. Common pam_timestamp Directives</h4></div></div></div><div class="para">
				The <code class="filename">pam_timestamp.so</code> module accepts several directives. The following are the two most commonly used options:
			</div><div class="itemizedlist"><ul><li><div class="para">
						<code class="command">timestamp_timeout</code> â€” Specifies the period (in seconds) for which the timestamp file is valid. The default value is 300 (five minutes).
					</div></li><li><div class="para">
						<code class="command">timestampdir</code> â€” Specifies the directory in which the timestamp file is stored. The default value is <code class="command">/var/run/sudo/</code>.
					</div></li></ul></div><div class="para">
				Refer to <a class="xref" href="sect-Security_Guide-Firewalls-Additional_Resources.html#sect-Security_Guide-Additional_Resources-Installed_Firewall_Documentation" title="2.8.9.1. DocumentaciÃ³n Instalada del Cortafuego">SecciÃ³nÂ 2.8.9.1, â€œDocumentaciÃ³n Instalada del Cortafuegoâ€</a> for more information about controlling the <code class="filename">pam_timestamp.so</code> module.
			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Administrative_Credential_Caching.html"><strong>Anterior</strong>2.4.6. PAM and Administrative Credential Caching</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Device_Ownership.html"><strong>Siguiente</strong>2.4.7. PAM and Device Ownership</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-PAM_and_Device_Ownership-Application_Access.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.4.7.2. Application Access</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Device_Ownership.html" title="2.4.7. PAM and Device Ownership" /><link rel="prev" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Device_Ownership.html" title="2.4.7. PAM and Device Ownership" /><link rel="next" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Additional_Resources.html" title="2.4.8. Additional Resources" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/ima
 ges/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Device_Ownership.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Additional_Resources.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-PAM_and_Device_Ownership-Application_Access">2.4.7.2. Application Access</h4></div></div></div><div class="para">
				The console user also has access to certain programs configured for use in the <code class="filename">/etc/security/console.apps/</code> directory.
			</div><div class="para">
				This directory contains configuration files which enable the console user to run certain applications in <code class="filename">/sbin</code> and <code class="filename">/usr/sbin</code>.
			</div><div class="para">
				These configuration files have the same name as the applications that they set up.
			</div><div class="para">
				One notable group of applications that the console user has access to are three programs that shut down or reboot the system:
			</div><div class="itemizedlist"><ul><li><div class="para">
						<code class="command">/sbin/halt</code>
					</div></li><li><div class="para">
						<code class="command">/sbin/reboot</code>
					</div></li><li><div class="para">
						<code class="command">/sbin/poweroff</code>
					</div></li></ul></div><div class="para">
				Because these are PAM-aware applications, they call the <code class="filename">pam_console.so</code> module as a requirement for use.
			</div><div class="para">
				Refer to <a class="xref" href="sect-Security_Guide-Firewalls-Additional_Resources.html#sect-Security_Guide-Additional_Resources-Installed_Firewall_Documentation" title="2.8.9.1. DocumentaciÃ³n Instalada del Cortafuego">SecciÃ³nÂ 2.8.9.1, â€œDocumentaciÃ³n Instalada del Cortafuegoâ€</a> for more information.
			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Device_Ownership.html"><strong>Anterior</strong>2.4.7. PAM and Device Ownership</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Additional_Resources.html"><strong>Siguiente</strong>2.4.8. Additional Resources</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Additional_Resources.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.4.8. Additional Resources</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM.html" title="2.4. Pluggable Authentication Modules (PAM)" /><link rel="prev" href="sect-Security_Guide-PAM_and_Device_Ownership-Application_Access.html" title="2.4.7.2. Application Access" /><link rel="next" href="sect-Security_Guide-Additional_Resources-Useful_PAM_Websites.html" title="2.4.8.2. Useful PAM Websites" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a cla
 ss="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-PAM_and_Device_Ownership-Application_Access.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Additional_Resources-Useful_PAM_Websites.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Additional_Resources">2.4.8. Additional Resources</h3></div></div></div><div class="para">
			The following resources further explain methods to use and configure PAM. In addition to these resources, read the PAM configuration files on the system to better understand how they are structured.
		</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Additional_Resources-Installed_PAM_Documentation">2.4.8.1. Installed PAM Documentation</h4></div></div></div><div class="itemizedlist"><ul><li><div class="para">
						PAM-related man pages â€” Several man pages exist for the various applications and configuration files involved with PAM. The following is a list of some of the more important man pages.
					</div><div class="variablelist"><dl><dt><span class="term">Configuration Files</span></dt><dd><div class="itemizedlist"><ul><li><div class="para">
											<code class="command">pam</code> â€” Good introductory information on PAM, including the structure and purpose of the PAM configuration files.
										</div><div class="para">
											Note that this man page discusses both <code class="filename">/etc/pam.conf</code> and individual configuration files in the <code class="filename">/etc/pam.d/</code> directory. By default, Fedora uses the individual configuration files in the <code class="filename">/etc/pam.d/</code> directory, ignoring <code class="filename">/etc/pam.conf</code> even if it exists.
										</div></li><li><div class="para">
											<code class="command">pam_console</code> â€” Describes the purpose of the <code class="filename">pam_console.so</code> module. It also describes the appropriate syntax for an entry within a PAM configuration file.
										</div></li><li><div class="para">
											<code class="command">console.apps</code> â€” Describes the format and options available in the <code class="filename">/etc/security/console.apps</code> configuration file, which defines which applications are accessible by the console user assigned by PAM.
										</div></li><li><div class="para">
											<code class="command">console.perms</code> â€” Describes the format and options available in the <code class="filename">/etc/security/console.perms</code> configuration file, which specifies the console user permissions assigned by PAM.
										</div></li><li><div class="para">
											<code class="command">pam_timestamp</code> â€” Describes the <code class="filename">pam_timestamp.so</code> module.
										</div></li></ul></div></dd></dl></div></li><li><div class="para">
						<code class="filename">/usr/share/doc/pam-<em class="replaceable"><code><version-number></code></em></code> â€” Contains a <em class="citetitle">System Administrators' Guide</em>, a <em class="citetitle">Module Writers' Manual</em>, and the <em class="citetitle">Application Developers' Manual</em>, as well as a copy of the PAM standard, DCE-RFC 86.0, where <em class="replaceable"><code><version-number></code></em> is the version number of PAM.
					</div></li><li><div class="para">
						<code class="filename">/usr/share/doc/pam-<em class="replaceable"><code><version-number></code></em>/txts/README.pam_timestamp</code> â€” Contains information about the <code class="filename">pam_timestamp.so</code> PAM module, where <em class="replaceable"><code><version-number></code></em> is the version number of PAM.
					</div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-PAM_and_Device_Ownership-Application_Access.html"><strong>Anterior</strong>2.4.7.2. Application Access</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Additional_Resources-Useful_PAM_Websites.html"><strong>Siguiente</strong>2.4.8.2. Useful PAM Websites</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Creating_PAM_Modules.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.4.5. Creating PAM Modules</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM.html" title="2.4. Pluggable Authentication Modules (PAM)" /><link rel="prev" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Sample_PAM_Configuration_Files.html" title="2.4.4. Sample PAM Configuration Files" /><link rel="next" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Administrative_Credential_Caching.html" title="2.4.6. PAM and Administrative Credential Caching" /></head><body class=""><p id="title"><a class="left" href="http://www.fedora
 project.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Sample_PAM_Configuration_Files.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Administrative_Credential_Caching.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Creating_PAM_Modules">2.4.5. Creating PAM Modules</h3></div></div></div><div class="para">
			You can create or add new PAM modules at any time for use by PAM-aware applications.
		</div><div class="para">
			For example, a developer might create a one-time-password creation method and write a PAM module to support it. PAM-aware programs can immediately use the new module and password method without being recompiled or otherwise modified.
		</div><div class="para">
			This allows developers and system administrators to mix-and-match, as well as test, authentication methods for different programs without recompiling them.
		</div><div class="para">
			Documentation on writing modules is included in the <code class="filename">/usr/share/doc/pam-<em class="replaceable"><code><version-number></code></em>/</code> directory, where <em class="replaceable"><code><version-number></code></em> is the version number for PAM on your system.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Sample_PAM_Configuration_Files.html"><strong>Anterior</strong>2.4.4. Sample PAM Configuration Files</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Administrative_Credential_Caching.html"><strong>Siguiente</strong>2.4.6. PAM and Administrative Credential Caching</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_File_Format.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.4.3. PAM Configuration File Format</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM.html" title="2.4. Pluggable Authentication Modules (PAM)" /><link rel="prev" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_Files.html" title="2.4.2. PAM Configuration Files" /><link rel="next" href="sect-Security_Guide-PAM_Configuration_File_Format-Control_Flag.html" title="2.4.3.2. Control Flag" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Pr
 oduct Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_Files.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-PAM_Configuration_File_Format-Control_Flag.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_File_Format">2.4.3. PAM Configuration File Format</h3></div></div></div><div class="para">
			Cada archivo de configuraciÃ³n PAM contiene un grupo de directivas formateadas como sigue:
		</div><pre class="screen"><em class="replaceable"><code><interfase del mÃ³dulo></code></em>  <em class="replaceable"><code><bandera de control></code></em>   <em class="replaceable"><code><nombre de mÃ³dulo></code></em>   <em class="replaceable"><code><argumentos del mÃ³dulo></code></em>
</pre><div class="para">
			Cada uno de estos elementos se explica en las siguientes secciones.
		</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-PAM_Configuration_File_Format-Module_Interface">2.4.3.1. Module Interface</h4></div></div></div><div class="para">
				Hay disponibles cuatro tipos de interfase de mÃ³dulos PAM. Cada uno corresponde a distintos aspectos del proceso de autorizaciÃ³n:
			</div><div class="itemizedlist"><ul><li><div class="para">
						<code class="command">auth</code> â€” Esta interfase de mÃ³dulo autentica el uso. Por ejemplo, pide y verifica la validez de una contraseÃ±a. Los mÃ³dulos con esta interfase tambiÃ©n pueden poner credenciales, como membresÃas de grupo o tiques Kerberos.
					</div></li><li><div class="para">
						<code class="command">account</code> â€” Esta interfase de mÃ³dulo verifica que el acceso estÃ¡ permitido. Por ejemplo, puede chequear si una cuenta a vencido o si un usario puede ingresar en una hora particular del dÃa.
					</div></li><li><div class="para">
						<code class="command">password</code> â€” Esta interfase de mÃ³dulo se usa para cambiar contraseÃ±as del usuario.
					</div></li><li><div class="para">
						<code class="command">session</code> â€” Esta interfase de mÃ³dulo configura y administra sesiones del usuario. Los mÃ³dulos con esta interfase pueden tambiÃ©n permitir tareas adicionales que necesitan permitir accesos, tales como el montaje del directorio de inicio del usuario y poner disponible la casilla de correo del usuario.
					</div></li></ul></div><div class="note"><h2>Note</h2><div class="para">
					Un mÃ³dulo individual puede proveer cualquiera o todas las interfases de mÃ³dulo. Por ejemplo <code class="filename">pam_unix.so</code> proee las cuatro interfases de mÃ³dulo.
				</div></div><div class="para">
				En un archivo de configuraciÃ³n PAM, la interfase de mÃ³dulo es el primer campo definido. Por ejemplo, una lÃnea tÃpica en una configuraciÃ³n puede verse como sigue:
			</div><pre class="screen">auth        required        pam_unix.so
</pre><div class="para">
				Esto instruye a PAM a que use la interfase <code class="command">auth</code> del mÃ³dulo <code class="filename">pam_unix.so</code>.
			</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h5 class="title" id="sect-Security_Guide-Module_Interface-Stacking_Module_Interfaces">2.4.3.1.1. Stacking Module Interfaces</h5></div></div></div><div class="para">
					Module interface directives can be <span class="emphasis"><em>stacked</em></span>, or placed upon one another, so that multiple modules are used together for one purpose. If a module's control flag uses the "sufficient" or "requisite" value (refer to <a class="xref" href="sect-Security_Guide-PAM_Configuration_File_Format-Control_Flag.html" title="2.4.3.2. Control Flag">SecciÃ³nÂ 2.4.3.2, â€œControl Flagâ€</a> for more information on these flags), then the order in which the modules are listed is important to the authentication process.
				</div><div class="para">
					El apilado hace fÃ¡cil para un administrador pedir que se den ciertas condiciones especÃficas antes de permitir al usuario autenticar. Por ejemplo, el comando <code class="command">reboot</code> normalmente usa varios mÃ³dulos apilados, como se ve en su archivo de configuraciÃ³n PAM:
				</div><pre class="screen">[root at MyServer ~]# cat /etc/pam.d/reboot
#%PAM-1.0
auth        sufficient        pam_rootok.so
auth        required        pam_console.so
#auth        include                system-auth
account        required        pam_permit.so
</pre><div class="itemizedlist"><ul><li><div class="para">
							La primera lÃnea es un comentario y no se procesa.
						</div></li><li><div class="para">
							<code class="command">auth sufficient pam_rootok.so</code> â€” Esta lÃnea usa el mÃ³dulo <code class="filename">pam_rootok.so</code> para chequear si el usuario actual es root, verificando que su UID es 0. Si esto tiene Ã©xito, no se consulta ningÃºn otro mÃ³dulo y el comando se ejecuta. Si esto falla, se consulta el mÃ³dulo siguiente.
						</div></li><li><div class="para">
							<code class="command">auth required pam_console.so</code> â€” This line uses the <code class="filename">pam_console.so</code> module to attempt to authenticate the user. If this user is already logged in at the console, <code class="filename">pam_console.so</code> checks whether there is a file in the <code class="filename">/etc/security/console.apps/</code> directory with the same name as the service name (reboot). If such a file exists, authentication succeeds and control is passed to the next module.
						</div></li><li><div class="para">
							<code class="command">#auth include system-auth</code> â€” Esta lÃnea es comentada y no se procesa.
						</div></li><li><div class="para">
							<code class="command">account required pam_permit.so</code> â€” Esta lÃnea usa el mÃ³dulo <code class="filename">pam_permit.so</code> para permitir al usuario root o cualquier otro que haya ingresado en la consola reiniciar el sistema.
						</div></li></ul></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_Files.html"><strong>Anterior</strong>2.4.2. PAM Configuration Files</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-PAM_Configuration_File_Format-Control_Flag.html"><strong>Siguiente</strong>2.4.3.2. Control Flag</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_Files.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.4.2. PAM Configuration Files</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM.html" title="2.4. Pluggable Authentication Modules (PAM)" /><link rel="prev" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM.html" title="2.4. Pluggable Authentication Modules (PAM)" /><link rel="next" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_File_Format.html" title="2.4.3. PAM Configuration File Format" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/i
 mage_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_File_Format.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_Files">2.4.2. PAM Configuration Files</h3></div></div></div><div class="para">
			El directorio <code class="filename">/etc/pam.d/</code> contiene los archivos de configuraciÃ³n de PAM para cada aplicaciÃ³n que usa PAM. En versiones anteriores de PAM, se usaba el archivo <code class="filename">/etc/pam.conf</code>, pero este archivo ahora se deja de usar y sÃ³lo se usarÃ¡ si el directorio <code class="filename">/etc/pam.d/</code> no existe.
		</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-PAM_Configuration_Files-PAM_Service_Files">2.4.2.1. PAM Service Files</h4></div></div></div><div class="para">
				Cada aplicaciÃ³n con capacidades PAM o <em class="firstterm">servicio</em> tiene un archivo en el directorio <code class="filename">/etc/pam.d/</code>. Cada archivo en este directorio tiene el mismo nombre del servicio al que controla el acceso.
			</div><div class="para">
				El programa que usa PAM es responsable por definir su nombre de servicio e instalar su propio archivo de configuraciÃ³n PAM en el directorio <code class="filename">/etc/pam.d/</code>. Por ejemplo, el programa <code class="command">login</code> define su nombre de servicio como <code class="command">login</code> e instala el archivo de configuraciÃ³n PAM <code class="filename">/etc/pam.d/login</code>.
			</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM.html"><strong>Anterior</strong>2.4. Pluggable Authentication Modules (PAM)</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_File_Format.html"><strong>Siguiente</strong>2.4.3. PAM Configuration File Format</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Administrative_Credential_Caching.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.4.6. PAM and Administrative Credential Caching</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM.html" title="2.4. Pluggable Authentication Modules (PAM)" /><link rel="prev" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Creating_PAM_Modules.html" title="2.4.5. Creating PAM Modules" /><link rel="next" href="sect-Security_Guide-PAM_and_Administrative_Credential_Caching-Common_pam_timestamp_Directives.html" title="2.4.6.2. Common pam_timestamp Directives" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"
 ><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Creating_PAM_Modules.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-PAM_and_Administrative_Credential_Caching-Common_pam_timestamp_Directives.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Administrative_Credential_Caching">2.4.6. PAM and Administrative Credential Caching</h3></div></div></div><div class="para">
			A number of graphical administrative tools in Fedora provide users with elevated privileges for up to five minutes using the <code class="filename">pam_timestamp.so</code> module. It is important to understand how this mechanism works, because a user who walks away from a terminal while <code class="filename">pam_timestamp.so</code> is in effect leaves the machine open to manipulation by anyone with physical access to the console.
		</div><div class="para">
			In the PAM timestamp scheme, the graphical administrative application prompts the user for the root password when it is launched. When the user has been authenticated, the <code class="filename">pam_timestamp.so</code> module creates a timestamp file. By default, this is created in the <code class="filename">/var/run/sudo/</code> directory. If the timestamp file already exists, graphical administrative programs do not prompt for a password. Instead, the <code class="filename">pam_timestamp.so</code> module freshens the timestamp file, reserving an extra five minutes of unchallenged administrative access for the user.
		</div><div class="para">
			You can verify the actual state of the timestamp file by inspecting the <code class="filename">/var/run/sudo/<user></code> file. For the desktop, the relevant file is <code class="filename">unknown:root</code>. If it is present and its timestamp is less than five minutes old, the credentials are valid.
		</div><div class="para">
			The existence of the timestamp file is indicated by an authentication icon, which appears in the notification area of the panel.
		</div><div class="figure" id="figu-Security_Guide-PAM_and_Administrative_Credential_Caching-The_Authentication_Icon"><div class="figure-contents"><div class="mediaobject"><img src="images/authicon.png" alt="The Authentication Icon" /><div class="longdesc"><div class="para">
						Illustration of the authentication icon.
					</div></div></div></div><h6>Figura 2.7. The Authentication Icon</h6></div><br class="figure-break" /><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-PAM_and_Administrative_Credential_Caching-Removing_the_Timestamp_File">2.4.6.1. Removing the Timestamp File</h4></div></div></div><div class="para">
				Before abandoning a console where a PAM timestamp is active, it is recommended that the timestamp file be destroyed. To do this from a graphical environment, click the authentication icon on the panel. This causes a dialog box to appear. Click the <span class="guibutton"><strong>Forget Authorization</strong></span> button to destroy the active timestamp file.
			</div><div class="figure" id="figu-Security_Guide-Removing_the_Timestamp_File-Dismiss_Authentication_Dialog"><div class="figure-contents"><div class="mediaobject"><img src="images/auth-panel.png" alt="Dismiss Authentication Dialog" /><div class="longdesc"><div class="para">
							Illustration of the authentication dismissal dialog box.
						</div></div></div></div><h6>Figura 2.8. Dismiss Authentication Dialog</h6></div><br class="figure-break" /><div class="para">
				You should be aware of the following with respect to the PAM timestamp file:
			</div><div class="itemizedlist"><ul><li><div class="para">
						If logged in to the system remotely using <code class="command">ssh</code>, use the <code class="command">/sbin/pam_timestamp_check -k root</code> command to destroy the timestamp file.
					</div></li><li><div class="para">
						You need to run the <code class="command">/sbin/pam_timestamp_check -k root</code> command from the same terminal window from which you launched the privileged application.
					</div></li><li><div class="para">
						You must be logged in as the user who originally invoked the <code class="filename">pam_timestamp.so</code> module in order to use the <code class="command">/sbin/pam_timestamp_check -k</code> command. Do not log in as root to use this command.
					</div></li><li><div class="para">
						If you want to kill the credentials on the desktop (without using the <span class="guibutton"><strong>Forget Authorization</strong></span> action on the icon), use the following command:
					</div><pre class="screen">/sbin/pam_timestamp_check -k root </dev/null >/dev/null 2>/dev/null
</pre><div class="para">
						Failure to use this command will only remove the credentials (if any) from the pty where you run the command.
					</div></li></ul></div><div class="para">
				Refer to the <code class="filename">pam_timestamp_check</code> man page for more information about destroying the timestamp file using <code class="command">pam_timestamp_check</code>.
			</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Creating_PAM_Modules.html"><strong>Anterior</strong>2.4.5. Creating PAM Modules</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-PAM_and_Administrative_Credential_Caching-Common_pam_timestamp_Directives.html"><strong>Siguiente</strong>2.4.6.2. Common pam_timestamp Directives</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Device_Ownership.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.4.7. PAM and Device Ownership</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM.html" title="2.4. Pluggable Authentication Modules (PAM)" /><link rel="prev" href="sect-Security_Guide-PAM_and_Administrative_Credential_Caching-Common_pam_timestamp_Directives.html" title="2.4.6.2. Common pam_timestamp Directives" /><link rel="next" href="sect-Security_Guide-PAM_and_Device_Ownership-Application_Access.html" title="2.4.7.2. Application Access" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/image
 s/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-PAM_and_Administrative_Credential_Caching-Common_pam_timestamp_Directives.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-PAM_and_Device_Ownership-Application_Access.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Device_Ownership">2.4.7. PAM and Device Ownership</h3></div></div></div><div class="para">
			In Fedora, the first user who logs in at the physical console of the machine can manipulate certain devices and perform certain tasks normally reserved for the root user. This is controlled by a PAM module called <code class="filename">pam_console.so</code>.
		</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-PAM_and_Device_Ownership-Device_Ownership">2.4.7.1. Device Ownership</h4></div></div></div><div class="para">
				When a user logs in to a Fedora system, the <code class="filename">pam_console.so</code> module is called by <code class="command">login</code> or the graphical login programs, <span class="application"><strong>gdm</strong></span>, <span class="application"><strong>kdm</strong></span>, and <span class="application"><strong>xdm</strong></span>. If this user is the first user to log in at the physical console â€” referred to as the <em class="firstterm">console user</em> â€” the module grants the user ownership of a variety of devices normally owned by root. The console user owns these devices until the last local session for that user ends. After this user has logged out, ownership of the devices reverts back to the root user.
			</div><div class="para">
				The devices affected include, but are not limited to, sound cards, diskette drives, and CD-ROM drives.
			</div><div class="para">
				This facility allows a local user to manipulate these devices without obtaining root access, thus simplifying common tasks for the console user.
			</div><div class="para">
				You can modify the list of devices controlled by <code class="filename">pam_console.so</code> by editing the following files: 
				<div class="itemizedlist"><ul><li><div class="para">
							<code class="filename">/etc/security/console.perms</code>
						</div></li><li><div class="para">
							<code class="filename">/etc/security/console.perms.d/50-default.perms</code>
						</div></li></ul></div>
			</div><div class="para">
				You can change the permissions of different devices than those listed in the above files, or override the specified defaults. Rather than modify the <code class="filename">50-default.perms</code> file, you should create a new file (for example, <code class="filename"><em class="replaceable"><code>xx</code></em>-name.perms</code>) and enter the required modifications. The name of the new default file must begin with a number higher than 50 (for example, <code class="filename">51-default.perms</code>). This will override the defaults in the <code class="filename">50-default.perms</code> file.
			</div><div class="warning"><h2>Warning</h2><div class="para">
					If the <span class="application"><strong>gdm</strong></span>, <span class="application"><strong>kdm</strong></span>, or <span class="application"><strong>xdm</strong></span> display manager configuration file has been altered to allow remote users to log in <span class="emphasis"><em>and</em></span> the host is configured to run at runlevel 5, it is advisable to change the <code class="command"><console></code> and <code class="command"><xconsole></code> directives in the <code class="filename">/etc/security/console.perms</code> to the following values:
				</div><pre class="screen"><console>=tty[0-9][0-9]* vc/[0-9][0-9]* :0\.[0-9] :0 
<xconsole>=:0\.[0-9] :0
</pre><div class="para">
					This prevents remote users from gaining access to devices and restricted applications on the machine.
				</div><div class="para">
					If the <span class="application"><strong>gdm</strong></span>, <span class="application"><strong>kdm</strong></span>, or <span class="application"><strong>xdm</strong></span> display manager configuration file has been altered to allow remote users to log in <span class="emphasis"><em>and</em></span> the host is configured to run at any multiple user runlevel other than 5, it is advisable to remove the <code class="command"><xconsole></code> directive entirely and change the <code class="command"><console></code> directive to the following value:
				</div><pre class="screen"><console>=tty[0-9][0-9]* vc/[0-9][0-9]*
</pre></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-PAM_and_Administrative_Credential_Caching-Common_pam_timestamp_Directives.html"><strong>Anterior</strong>2.4.6.2. Common pam_timestamp Directives</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-PAM_and_Device_Ownership-Application_Access.html"><strong>Siguiente</strong>2.4.7.2. Application Access</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Sample_PAM_Configuration_Files.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.4.4. Sample PAM Configuration Files</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM.html" title="2.4. Pluggable Authentication Modules (PAM)" /><link rel="prev" href="sect-Security_Guide-PAM_Configuration_File_Format-Module_Arguments.html" title="2.4.3.4. Module Arguments" /><link rel="next" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Creating_PAM_Modules.html" title="2.4.5. Creating PAM Modules" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt=
 "Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-PAM_Configuration_File_Format-Module_Arguments.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Creating_PAM_Modules.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Sample_PAM_Configuration_Files">2.4.4. Sample PAM Configuration Files</h3></div></div></div><div class="para">
			El siguiente es una muestra del archivo de configuraciÃ³n PAM de una aplicaciÃ³n:
		</div><pre class="screen">#%PAM-1.0
auth                required  pam_securetty.so
auth                required  pam_unix.so nullok
auth                required  pam_nologin.so
account                required  pam_unix.so
password        required  pam_cracklib.so retry=3
password        required  pam_unix.so shadow nullok use_authtok
session        required  pam_unix.so
</pre><div class="itemizedlist"><ul><li><div class="para">
					La primera lÃnea es un comentario, indicado por el numeral (<code class="command">#</code>) al comienzo de la lÃnea.
				</div></li><li><div class="para">
					Las lÃneas 2 a la 4 apila tres mÃ³dulos para la autenticaciÃ³n de ingreso.
				</div><div class="para">
					<code class="command">auth required pam_securetty.so</code> â€” Este mÃ³dulo asegura que <span class="emphasis"><em>si</em></span> el usuario intenta ingresar como root, el tty donde el usuario estÃ¡ ingresando debe estÃ¡r listada en el archivo <code class="filename">/etc/securetty</code>, <span class="emphasis"><em>si</em></span> ese archivo existe.
				</div><div class="para">
					If the tty is not listed in the file, any attempt to log in as root fails with a <code class="computeroutput">Login incorrect</code> message.
				</div><div class="para">
					<code class="command">auth required pam_unix.so nullok</code> â€” This module prompts the user for a password and then checks the password using the information stored in <code class="filename">/etc/passwd</code> and, if it exists, <code class="filename">/etc/shadow</code>.
				</div><div class="itemizedlist"><ul><li><div class="para">
							The argument <code class="command">nullok</code> instructs the <code class="filename">pam_unix.so</code> module to allow a blank password.
						</div></li></ul></div></li><li><div class="para">
					<code class="command">auth required pam_nologin.so</code> â€” This is the final authentication step. It checks whether the <code class="filename">/etc/nologin</code> file exists. If it exists and the user is not root, authentication fails.
				</div><div class="note"><h2>Note</h2><div class="para">
						In this example, all three <code class="command">auth</code> modules are checked, even if the first <code class="command">auth</code> module fails. This prevents the user from knowing at what stage their authentication failed. Such knowledge in the hands of an attacker could allow them to more easily deduce how to crack the system.
					</div></div></li><li><div class="para">
					<code class="command">account required pam_unix.so</code> â€” This module performs any necessary account verification. For example, if shadow passwords have been enabled, the account interface of the <code class="filename">pam_unix.so</code> module checks to see if the account has expired or if the user has not changed the password within the allowed grace period.
				</div></li><li><div class="para">
					<code class="command">password required pam_cracklib.so retry=3</code> â€” If a password has expired, the password component of the <code class="filename">pam_cracklib.so</code> module prompts for a new password. It then tests the newly created password to see whether it can easily be determined by a dictionary-based password cracking program.
				</div><div class="itemizedlist"><ul><li><div class="para">
							The argument <code class="command">retry=3</code> specifies that if the test fails the first time, the user has two more chances to create a strong password.
						</div></li></ul></div></li><li><div class="para">
					<code class="command">password required pam_unix.so shadow nullok use_authtok</code> â€” This line specifies that if the program changes the user's password, it should use the <code class="command">password</code> interface of the <code class="filename">pam_unix.so</code> module to do so.
				</div><div class="itemizedlist"><ul><li><div class="para">
							The argument <code class="command">shadow</code> instructs the module to create shadow passwords when updating a user's password.
						</div></li><li><div class="para">
							The argument <code class="command">nullok</code> instructs the module to allow the user to change their password <span class="emphasis"><em>from</em></span> a blank password, otherwise a null password is treated as an account lock.
						</div></li><li><div class="para">
							The final argument on this line, <code class="command">use_authtok</code>, provides a good example of the importance of order when stacking PAM modules. This argument instructs the module not to prompt the user for a new password. Instead, it accepts any password that was recorded by a previous password module. In this way, all new passwords must pass the <code class="filename">pam_cracklib.so</code> test for secure passwords before being accepted.
						</div></li></ul></div></li><li><div class="para">
					<code class="command">session required pam_unix.so</code> â€” The final line instructs the session interface of the <code class="filename">pam_unix.so</code> module to manage the session. This module logs the user name and the service type to <code class="filename">/var/log/secure</code> at the beginning and end of each session. This module can be supplemented by stacking it with other session modules for additional functionality.
				</div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-PAM_Configuration_File_Format-Module_Arguments.html"><strong>Anterior</strong>2.4.3.4. Module Arguments</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Creating_PAM_Modules.html"><strong>Siguiente</strong>2.4.5. Creating PAM Modules</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Pluggable_Authentication_Modules_PAM.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.4. Pluggable Authentication Modules (PAM)</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="chap-Security_Guide-Securing_Your_Network.html" title="CapÃtulo 2. Securing Your Network" /><link rel="prev" href="sect-Security_Guide-Single_Sign_on_SSO-Configuring_Firefox_to_use_Kerberos_for_SSO.html" title="2.3.5. Configuring Firefox to use Kerberos for SSO" /><link rel="next" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_Files.html" title="2.4.2. PAM Configuration Files" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Conten
 t/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Single_Sign_on_SSO-Configuring_Firefox_to_use_Kerberos_for_SSO.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_Files.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h2 class="title" id="sect-Security_Guide-Pluggable_Authentication_Modules_PAM">2.4. Pluggable Authentication Modules (PAM)</h2></div></div></div><div class="para">
		Los programas programas que permiten el acceso del usuario a un sistema usan la <em class="firstterm">autenticaciÃ³n</em> para verificar la identidad de cada uno (es decir, para establecer que el usuario es quien dice ser).
	</div><div class="para">
		HistÃ³ricamente, cada programa tenÃa su propia forma de autenticar los usuarios. En Fedora, muchos programas se configuran para usar el mecanismo de autenticaciÃ³n centralizado llamado <em class="firstterm">MÃ³dulos de AutenticaciÃ³n con Complementos</em> (<acronym class="acronym">PAM</acronym>).
	</div><div class="para">
		PAM usa una arquitectura modular, con complementos, que le da al administrador del sistema un buen grado de flexibilidad en la configuraciÃ³n de las polÃticas de autenticaciÃ³n para el sistema.
	</div><div class="para">
		In most situations, the default PAM configuration file for a PAM-aware application is sufficient. Sometimes, however, it is necessary to edit a PAM configuration file. Because misconfiguration of PAM can compromise system security, it is important to understand the structure of these files before making any modifications. Refer to <a class="xref" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_File_Format.html" title="2.4.3. PAM Configuration File Format">SecciÃ³nÂ 2.4.3, â€œPAM Configuration File Formatâ€</a> for more information.
	</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Advantages_of_PAM">2.4.1. Advantages of PAM</h3></div></div></div><div class="para">
			PAM ofrece las siguientes ventajas;
		</div><div class="itemizedlist"><ul><li><div class="para">
					un esquema de autenticaciÃ³n comÃºn que se puede usar en una amplia variedad de aplicaciones.
				</div></li><li><div class="para">
					flexibilidad significativa y control sobre la autenticaciÃ³n para administradores del sistema y desarrolladores de aplicaciones.
				</div></li><li><div class="para">
					una Ãºnica biblioteca bien documentada que permite a los desarrolladores escribir programas sin tener que crear sus propios esquemas de autenticaciÃ³n.
				</div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Single_Sign_on_SSO-Configuring_Firefox_to_use_Kerberos_for_SSO.html"><strong>Anterior</strong>2.3.5. Configuring Firefox to use Kerberos for SSO</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_Files.html"><strong>Siguiente</strong>2.4.2. PAM Configuration Files</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Secure_Installation-Utilize_LUKS_Partition_Encryption.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.2. Utilize LUKS Partition Encryption</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="chap-Security_Guide-Secure_Installation.html" title="CapÃtulo 5. Secure Installation" /><link rel="prev" href="chap-Security_Guide-Secure_Installation.html" title="CapÃtulo 5. Secure Installation" /><link rel="next" href="chap-Security_Guide-Software_Maintenance.html" title="CapÃtulo 6. Mantenimiento de Software" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org
 "><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security_Guide-Secure_Installation.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="chap-Security_Guide-Software_Maintenance.html"><strong>Siguiente</strong></a></li></ul><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.
		</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><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security_Guide-Secure_Installation.html"><strong>Anterior</strong>CapÃtulo 5. Secure Installation</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="chap-Security_Guide-Software_Maintenance.html"><strong>Siguiente</strong>CapÃtulo 6. Mantenimiento de Software</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Securing_FTP-Anonymous_Access.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.6.2. Anonymous Access</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Server_Security-Securing_FTP.html" title="2.2.6. Securing FTP" /><link rel="prev" href="sect-Security_Guide-Server_Security-Securing_FTP.html" title="2.2.6. Securing FTP" /><link rel="next" href="sect-Security_Guide-Securing_FTP-User_Accounts.html" title="2.2.6.3. Cuentas de Usurio" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/
 images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Server_Security-Securing_FTP.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_FTP-User_Accounts.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Securing_FTP-Anonymous_Access">2.2.6.2. Anonymous Access</h4></div></div></div><div class="para">
				The presence of the <code class="filename">/var/ftp/</code> directory activates the anonymous account.
			</div><div class="para">
				The easiest way to create this directory is to install the <code class="filename">vsftpd</code> package. This package establishes a directory tree for anonymous users and configures the permissions on directories to read-only for anonymous users.
			</div><div class="para">
				By default the anonymous user cannot write to any directories.
			</div><div class="warning"><h2>Warning</h2><div class="para">
					If enabling anonymous access to an FTP server, be aware of where sensitive data is stored.
				</div></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h5 class="title" id="sect-Security_Guide-Anonymous_Access-Anonymous_Upload">2.2.6.2.1. Anonymous Upload</h5></div></div></div><div class="para">
					To allow anonymous users to upload files, it is recommended that a write-only directory be created within <code class="filename">/var/ftp/pub/</code>.
				</div><div class="para">
					To do this, type the following command:
				</div><pre class="screen">mkdir /var/ftp/pub/subidas
</pre><div class="para">
					Next, change the permissions so that anonymous users cannot view the contents of the directory:
				</div><pre class="screen">chmod 730 /var/ftp/pub/subidas
</pre><div class="para">
					A long format listing of the directory should look like this:
				</div><pre class="screen">drwx-wx---    2 root     ftp          4096 Feb 13 20:05 subidas
</pre><div class="warning"><h2>Warning</h2><div class="para">
						Administrators who allow anonymous users to read and write in directories often find that their servers become a repository of stolen software.
					</div></div><div class="para">
					Additionally, under <code class="command">vsftpd</code>, add the following line to the <code class="filename">/etc/vsftpd/vsftpd.conf</code> file:
				</div><pre class="screen">anon_upload_enable=YES
</pre></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Server_Security-Securing_FTP.html"><strong>Anterior</strong>2.2.6. Securing FTP</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_FTP-User_Accounts.html"><strong>Siguiente</strong>2.2.6.3. Cuentas de Usurio</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Securing_FTP-Use_TCP_Wrappers_To_Control_Access.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.6.4. Use TCP Wrappers To Control Access</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Server_Security-Securing_FTP.html" title="2.2.6. Securing FTP" /><link rel="prev" href="sect-Security_Guide-Securing_FTP-User_Accounts.html" title="2.2.6.3. Cuentas de Usurio" /><link rel="next" href="sect-Security_Guide-Server_Security-Securing_Sendmail.html" title="2.2.7. Securing Sendmail" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.or
 g"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_FTP-User_Accounts.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Server_Security-Securing_Sendmail.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Securing_FTP-Use_TCP_Wrappers_To_Control_Access">2.2.6.4. Use TCP Wrappers To Control Access</h4></div></div></div><div class="para">
				Use TCP Wrappers to control access to either FTP daemon as outlined in <a class="xref" href="sect-Security_Guide-Server_Security.html#sect-Security_Guide-Securing_Services_With_TCP_Wrappers_and_xinetd-Enhancing_Security_With_TCP_Wrappers" title="2.2.1.1. Enhancing Security With TCP Wrappers">SecciÃ³nÂ 2.2.1.1, â€œEnhancing Security With TCP Wrappersâ€</a>.
			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_FTP-User_Accounts.html"><strong>Anterior</strong>2.2.6.3. Cuentas de Usurio</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Server_Security-Securing_Sendmail.html"><strong>Siguiente</strong>2.2.7. Securing Sendmail</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Securing_FTP-User_Accounts.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.6.3. Cuentas de Usurio</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Server_Security-Securing_FTP.html" title="2.2.6. Securing FTP" /><link rel="prev" href="sect-Security_Guide-Securing_FTP-Anonymous_Access.html" title="2.2.6.2. Anonymous Access" /><link rel="next" href="sect-Security_Guide-Securing_FTP-Use_TCP_Wrappers_To_Control_Access.html" title="2.2.6.4. Use TCP Wrappers To Control Access" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://doc
 s.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_FTP-Anonymous_Access.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_FTP-Use_TCP_Wrappers_To_Control_Access.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Securing_FTP-User_Accounts">2.2.6.3. Cuentas de Usurio</h4></div></div></div><div class="para">
				Because FTP transmits unencrypted usernames and passwords over insecure networks for authentication, it is a good idea to deny system users access to the server from their user accounts.
			</div><div class="para">
				To disable all user accounts in <code class="command">vsftpd</code>, add the following directive to <code class="filename">/etc/vsftpd/vsftpd.conf</code>:
			</div><pre class="screen">local_enable=NO
</pre><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h5 class="title" id="sect-Security_Guide-User_Accounts-Restricting_User_Accounts">2.2.6.3.1. Restringiendo Cuentas de Usuario</h5></div></div></div><div class="para">
					To disable FTP access for specific accounts or specific groups of accounts, such as the root user and those with <code class="command">sudo</code> privileges, the easiest way is to use a PAM list file as described in <a class="xref" href="chap-Security_Guide-Securing_Your_Network.html#sect-Security_Guide-Disallowing_Root_Access-Disabling_Root_Using_PAM" title="2.1.4.2.4. Desabilitando Root Usando PAM">SecciÃ³nÂ 2.1.4.2.4, â€œDesabilitando Root Usando PAMâ€</a>. The PAM configuration file for <code class="command">vsftpd</code> is <code class="filename">/etc/pam.d/vsftpd</code>.
				</div><div class="para">
					It is also possible to disable user accounts within each service directly.
				</div><div class="para">
					To disable specific user accounts in <code class="command">vsftpd</code>, add the username to <code class="filename">/etc/vsftpd.ftpusers</code>
				</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_FTP-Anonymous_Access.html"><strong>Anterior</strong>2.2.6.2. Anonymous Access</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_FTP-Use_TCP_Wrappers_To_Control_Access.html"><strong>Siguiente</strong>2.2.6.4. Use TCP Wrappers To Control Access</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Securing_NFS-Beware_of_Syntax_Errors.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.4.2. Beware of Syntax Errors</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Server_Security-Securing_NFS.html" title="2.2.4. Securing NFS" /><link rel="prev" href="sect-Security_Guide-Server_Security-Securing_NFS.html" title="2.2.4. Securing NFS" /><link rel="next" href="sect-Security_Guide-Securing_NFS-Do_Not_Use_the_no_root_squash_Option.html" title="2.2.4.3. Do Not Use the no_root_squash Option" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://
 docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Server_Security-Securing_NFS.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_NFS-Do_Not_Use_the_no_root_squash_Option.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Securing_NFS-Beware_of_Syntax_Errors">2.2.4.2. Beware of Syntax Errors</h4></div></div></div><div class="para">
				The NFS server determines which file systems to export and which hosts to export these directories to by consulting the <code class="filename">/etc/exports</code> file. Be careful not to add extraneous spaces when editing this file.
			</div><div class="para">
				For instance, the following line in the <code class="filename">/etc/exports</code> file shares the directory <code class="command">/tmp/nfs/</code> to the host <code class="command">bob.example.com</code> with read/write permissions.
			</div><pre class="screen">/tmp/nfs/     bob.example.com(rw)
</pre><div class="para">
				The following line in the <code class="filename">/etc/exports</code> file, on the other hand, shares the same directory to the host <code class="computeroutput">bob.example.com</code> with read-only permissions and shares it to the <span class="emphasis"><em>world</em></span> with read/write permissions due to a single space character after the hostname.
			</div><pre class="screen">/tmp/nfs/     bob.example.com (rw)
</pre><div class="para">
				It is good practice to check any configured NFS shares by using the <code class="command">showmount</code> command to verify what is being shared:
			</div><pre class="screen">showmount -e <em class="replaceable"><code><hostname></code></em>
</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Server_Security-Securing_NFS.html"><strong>Anterior</strong>2.2.4. Securing NFS</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_NFS-Do_Not_Use_the_no_root_squash_Option.html"><strong>Siguiente</strong>2.2.4.3. Do Not Use the no_root_squash Option</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Securing_NFS-Do_Not_Use_the_no_root_squash_Option.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.4.3. Do Not Use the no_root_squash Option</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Server_Security-Securing_NFS.html" title="2.2.4. Securing NFS" /><link rel="prev" href="sect-Security_Guide-Securing_NFS-Beware_of_Syntax_Errors.html" title="2.2.4.2. Beware of Syntax Errors" /><link rel="next" href="sect-Security_Guide-Securing_NFS-NFS_Firewall_Configuration.html" title="2.2.4.4. NFS Firewall Configuration" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right"
  href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_NFS-Beware_of_Syntax_Errors.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_NFS-NFS_Firewall_Configuration.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Securing_NFS-Do_Not_Use_the_no_root_squash_Option">2.2.4.3. Do Not Use the <code class="command">no_root_squash</code> Option</h4></div></div></div><div class="para">
				By default, NFS shares change the root user to the <code class="command">nfsnobody</code> user, an unprivileged user account. This changes the owner of all root-created files to <code class="command">nfsnobody</code>, which prevents uploading of programs with the setuid bit set.
			</div><div class="para">
				If <code class="command">no_root_squash</code> is used, remote root users are able to change any file on the shared file system and leave applications infected by trojans for other users to inadvertently execute.
			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_NFS-Beware_of_Syntax_Errors.html"><strong>Anterior</strong>2.2.4.2. Beware of Syntax Errors</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_NFS-NFS_Firewall_Configuration.html"><strong>Siguiente</strong>2.2.4.4. NFS Firewall Configuration</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Securing_NFS-NFS_Firewall_Configuration.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.4.4. NFS Firewall Configuration</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Server_Security-Securing_NFS.html" title="2.2.4. Securing NFS" /><link rel="prev" href="sect-Security_Guide-Securing_NFS-Do_Not_Use_the_no_root_squash_Option.html" title="2.2.4.3. Do Not Use the no_root_squash Option" /><link rel="next" href="sect-Security_Guide-Server_Security-Securing_the_Apache_HTTP_Server.html" title="2.2.5. Securing the Apache HTTP Server" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product S
 ite" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_NFS-Do_Not_Use_the_no_root_squash_Option.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Server_Security-Securing_the_Apache_HTTP_Server.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Securing_NFS-NFS_Firewall_Configuration">2.2.4.4. NFS Firewall Configuration</h4></div></div></div><div class="para">
				The ports used for NFS are assigned dynamically by rpcbind, which can cause problems when creating firewall rules. To simplify this process, use the <span class="emphasis"><em>/etc/sysconfig/nfs</em></span> file to specify which ports are to be used:
			</div><div class="itemizedlist"><ul><li><div class="para">
						<code class="command">MOUNTD_PORT</code> â€” TCP and UDP port for mountd (rpc.mountd)
					</div></li><li><div class="para">
						<code class="command">STATD_PORT</code> â€” TCP and UDP port for status (rpc.statd)
					</div></li><li><div class="para">
						<code class="command">LOCKD_TCPPORT</code> â€” TCP port for nlockmgr (rpc.lockd)
					</div></li><li><div class="para">
						<code class="command">LOCKD_UDPPORT</code> â€” UDP port nlockmgr (rpc.lockd)
					</div></li></ul></div><div class="para">
				Port numbers specified must not be used by any other service. Configure your firewall to allow the port numbers specified, as well as TCP and UDP port 2049 (NFS).
			</div><div class="para">
				Run the <code class="command">rpcinfo -p</code> command on the NFS server to see which ports and RPC programs are being used.
			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_NFS-Do_Not_Use_the_no_root_squash_Option.html"><strong>Anterior</strong>2.2.4.3. Do Not Use the no_root_squash Option</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Server_Security-Securing_the_Apache_HTTP_Server.html"><strong>Siguiente</strong>2.2.5. Securing the Apache HTTP Server</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Securing_NIS-Assign_Static_Ports_and_Use_iptables_Rules.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.3.4. Assign Static Ports and Use iptables Rules</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Server_Security-Securing_NIS.html" title="2.2.3. Securing NIS" /><link rel="prev" href="sect-Security_Guide-Securing_NIS-Edit_the_varypsecurenets_File.html" title="2.2.3.3. Edit the /var/yp/securenets File" /><link rel="next" href="sect-Security_Guide-Securing_NIS-Use_Kerberos_Authentication.html" title="2.2.3.5. Use Kerberos Authentication" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site"
  /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_NIS-Edit_the_varypsecurenets_File.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_NIS-Use_Kerberos_Authentication.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Securing_NIS-Assign_Static_Ports_and_Use_iptables_Rules">2.2.3.4. Assign Static Ports and Use iptables Rules</h4></div></div></div><div class="para">
				All of the servers related to NIS can be assigned specific ports except for <code class="command">rpc.yppasswdd</code> â€” the daemon that allows users to change their login passwords. Assigning ports to the other two NIS server daemons, <code class="command">rpc.ypxfrd</code> and <code class="command">ypserv</code>, allows for the creation of firewall rules to further protect the NIS server daemons from intruders.
			</div><div class="para">
				To do this, add the following lines to <code class="filename">/etc/sysconfig/network</code>:
			</div><pre class="screen">YPSERV_ARGS="-p 834" YPXFRD_ARGS="-p 835"
</pre><div class="para">
				The following iptables rules can then be used to enforce which network the server listens to for these ports:
			</div><pre class="screen">iptables -A INPUT -p ALL -s! 192.168.0.0/24  --dport 834 -j DROP
iptables -A INPUT -p ALL -s! 192.168.0.0/24  --dport 835 -j DROP
</pre><div class="para">
				This means that the server only allows connections to ports 834 and 835 if the requests come from the 192.168.0.0/24 network, regardless of the protocol.
			</div><div class="note"><h2>Note</h2><div class="para">
					Refer to <a class="xref" href="sect-Security_Guide-Firewalls.html" title="2.8. Firewalls">SecciÃ³nÂ 2.8, â€œFirewallsâ€</a> for more information about implementing firewalls with iptables commands.
				</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_NIS-Edit_the_varypsecurenets_File.html"><strong>Anterior</strong>2.2.3.3. Edit the /var/yp/securenets File</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_NIS-Use_Kerberos_Authentication.html"><strong>Siguiente</strong>2.2.3.5. Use Kerberos Authentication</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Securing_NIS-Edit_the_varypsecurenets_File.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.3.3. Edit the /var/yp/securenets File</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Server_Security-Securing_NIS.html" title="2.2.3. Securing NIS" /><link rel="prev" href="sect-Security_Guide-Securing_NIS-Use_a_Password_like_NIS_Domain_Name_and_Hostname.html" title="2.2.3.2. Use a Password-like NIS Domain Name and Hostname" /><link rel="next" href="sect-Security_Guide-Securing_NIS-Assign_Static_Ports_and_Use_iptables_Rules.html" title="2.2.3.4. Assign Static Ports and Use iptables Rules" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="C
 ommon_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_NIS-Use_a_Password_like_NIS_Domain_Name_and_Hostname.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_NIS-Assign_Static_Ports_and_Use_iptables_Rules.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Securing_NIS-Edit_the_varypsecurenets_File">2.2.3.3. Edit the <code class="filename">/var/yp/securenets</code> File</h4></div></div></div><div class="para">
				If the <code class="filename">/var/yp/securenets</code> file is blank or does not exist (as is the case after a default installation), NIS listens to all networks. One of the first things to do is to put netmask/network pairs in the file so that <code class="command">ypserv</code> only responds to requests from the appropriate network.
			</div><div class="para">
				Below is a sample entry from a <code class="filename">/var/yp/securenets</code> file:
			</div><pre class="screen">255.255.255.0     192.168.0.0
</pre><div class="warning"><h2>Warning</h2><div class="para">
					Never start an NIS server for the first time without creating the <code class="filename">/var/yp/securenets</code> file.
				</div></div><div class="para">
				This technique does not provide protection from an IP spoofing attack, but it does at least place limits on what networks the NIS server services.
			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_NIS-Use_a_Password_like_NIS_Domain_Name_and_Hostname.html"><strong>Anterior</strong>2.2.3.2. Use a Password-like NIS Domain Name and ...</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_NIS-Assign_Static_Ports_and_Use_iptables_Rules.html"><strong>Siguiente</strong>2.2.3.4. Assign Static Ports and Use iptables Rul...</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Securing_NIS-Use_Kerberos_Authentication.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.3.5. Use Kerberos Authentication</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Server_Security-Securing_NIS.html" title="2.2.3. Securing NIS" /><link rel="prev" href="sect-Security_Guide-Securing_NIS-Assign_Static_Ports_and_Use_iptables_Rules.html" title="2.2.3.4. Assign Static Ports and Use iptables Rules" /><link rel="next" href="sect-Security_Guide-Server_Security-Securing_NFS.html" title="2.2.4. Securing NFS" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="righ
 t" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_NIS-Assign_Static_Ports_and_Use_iptables_Rules.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Server_Security-Securing_NFS.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Securing_NIS-Use_Kerberos_Authentication">2.2.3.5. Use Kerberos Authentication</h4></div></div></div><div class="para">
				One of the issues to consider when NIS is used for authentication is that whenever a user logs into a machine, a password hash from the <code class="filename">/etc/shadow</code> map is sent over the network. If an intruder gains access to an NIS domain and sniffs network traffic, they can collect usernames and password hashes. With enough time, a password cracking program can guess weak passwords, and an attacker can gain access to a valid account on the network.
			</div><div class="para">
				Since Kerberos uses secret-key cryptography, no password hashes are ever sent over the network, making the system far more secure. Refer to <a class="xref" href="sect-Security_Guide-Kerberos.html" title="2.6. Kerberos">SecciÃ³nÂ 2.6, â€œKerberosâ€</a> for more information about Kerberos.
			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_NIS-Assign_Static_Ports_and_Use_iptables_Rules.html"><strong>Anterior</strong>2.2.3.4. Assign Static Ports and Use iptables Rul...</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Server_Security-Securing_NFS.html"><strong>Siguiente</strong>2.2.4. Securing NFS</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Securing_NIS-Use_a_Password_like_NIS_Domain_Name_and_Hostname.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.3.2. Use a Password-like NIS Domain Name and Hostname</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Server_Security-Securing_NIS.html" title="2.2.3. Securing NIS" /><link rel="prev" href="sect-Security_Guide-Server_Security-Securing_NIS.html" title="2.2.3. Securing NIS" /><link rel="next" href="sect-Security_Guide-Securing_NIS-Edit_the_varypsecurenets_File.html" title="2.2.3.3. Edit the /var/yp/securenets File" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right"
  href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Server_Security-Securing_NIS.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_NIS-Edit_the_varypsecurenets_File.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Securing_NIS-Use_a_Password_like_NIS_Domain_Name_and_Hostname">2.2.3.2. Use a Password-like NIS Domain Name and Hostname</h4></div></div></div><div class="para">
				Any machine within an NIS domain can use commands to extract information from the server without authentication, as long as the user knows the NIS server's DNS hostname and NIS domain name.
			</div><div class="para">
				For instance, if someone either connects a laptop computer into the network or breaks into the network from outside (and manages to spoof an internal IP address), the following command reveals the <code class="command">/etc/passwd</code> map:
			</div><pre class="screen">ypcat -d <em class="replaceable"><code><NIS_domain></code></em> -h <em class="replaceable"><code><DNS_hostname></code></em> passwd
</pre><div class="para">
				If this attacker is a root user, they can obtain the <code class="command">/etc/shadow</code> file by typing the following command:
			</div><pre class="screen">ypcat -d <em class="replaceable"><code><NIS_domain></code></em> -h <em class="replaceable"><code><DNS_hostname></code></em> shadow
</pre><div class="note"><h2>Note</h2><div class="para">
					If Kerberos is used, the <code class="command">/etc/shadow</code> file is not stored within an NIS map.
				</div></div><div class="para">
				To make access to NIS maps harder for an attacker, create a random string for the DNS hostname, such as <code class="filename">o7hfawtgmhwg.domain.com</code>. Similarly, create a <span class="emphasis"><em>different</em></span> randomized NIS domain name. This makes it much more difficult for an attacker to access the NIS server.
			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Server_Security-Securing_NIS.html"><strong>Anterior</strong>2.2.3. Securing NIS</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_NIS-Edit_the_varypsecurenets_File.html"><strong>Siguiente</strong>2.2.3.3. Edit the /var/yp/securenets File</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Securing_Portmap-Protect_portmap_With_iptables.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.2.2. Protect portmap With iptables</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Server_Security-Securing_Portmap.html" title="2.2.2. Securing Portmap" /><link rel="prev" href="sect-Security_Guide-Server_Security-Securing_Portmap.html" title="2.2.2. Securing Portmap" /><link rel="next" href="sect-Security_Guide-Server_Security-Securing_NIS.html" title="2.2.3. Securing NIS" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><
 img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Server_Security-Securing_Portmap.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Server_Security-Securing_NIS.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Securing_Portmap-Protect_portmap_With_iptables">2.2.2.2. Protect portmap With iptables</h4></div></div></div><div class="para">
				To further restrict access to the <code class="command">portmap</code> service, it is a good idea to add iptables rules to the server and restrict access to specific networks.
			</div><div class="para">
				Below are two example iptables commands. The first allows TCP connections to the port 111 (used by the <code class="command">portmap</code> service) from the 192.168.0.0/24 network. The second allows TCP connections to the same port from the localhost. This is necessary for the <code class="command">sgi_fam</code> service used by <span class="application"><strong>Nautilus</strong></span>. All other packets are dropped.
			</div><pre class="screen">iptables -A INPUT -p tcp -s! 192.168.0.0/24 --dport 111 -j DROP
iptables -A INPUT -p tcp -s 127.0.0.1  --dport 111 -j ACCEPT
</pre><div class="para">
				To similarly limit UDP traffic, use the following command.
			</div><pre class="screen">iptables -A INPUT -p udp -s! 192.168.0.0/24  --dport 111 -j DROP
</pre><div class="note"><h2>Note</h2><div class="para">
					Refer to <a class="xref" href="sect-Security_Guide-Firewalls.html" title="2.8. Firewalls">SecciÃ³nÂ 2.8, â€œFirewallsâ€</a> for more information about implementing firewalls with iptables commands.
				</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Server_Security-Securing_Portmap.html"><strong>Anterior</strong>2.2.2. Securing Portmap</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Server_Security-Securing_NIS.html"><strong>Siguiente</strong>2.2.3. Securing NIS</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Securing_Sendmail-Mail_only_Users.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.7.3. Mail-only Users</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Server_Security-Securing_Sendmail.html" title="2.2.7. Securing Sendmail" /><link rel="prev" href="sect-Security_Guide-Securing_Sendmail-NFS_and_Sendmail.html" title="2.2.7.2. NFS y Sendmail" /><link rel="next" href="sect-Security_Guide-Server_Security-Verifying_Which_Ports_Are_Listening.html" title="2.2.8. Verifying Which Ports Are Listening" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" hr
 ef="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_Sendmail-NFS_and_Sendmail.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Server_Security-Verifying_Which_Ports_Are_Listening.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Securing_Sendmail-Mail_only_Users">2.2.7.3. Mail-only Users</h4></div></div></div><div class="para">
				To help prevent local user exploits on the Sendmail server, it is best for mail users to only access the Sendmail server using an email program. Shell accounts on the mail server should not be allowed and all user shells in the <code class="filename">/etc/passwd</code> file should be set to <code class="command">/sbin/nologin</code> (with the possible exception of the root user).
			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_Sendmail-NFS_and_Sendmail.html"><strong>Anterior</strong>2.2.7.2. NFS y Sendmail</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Server_Security-Verifying_Which_Ports_Are_Listening.html"><strong>Siguiente</strong>2.2.8. Verifying Which Ports Are Listening</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Securing_Sendmail-NFS_and_Sendmail.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.7.2. NFS y Sendmail</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Server_Security-Securing_Sendmail.html" title="2.2.7. Securing Sendmail" /><link rel="prev" href="sect-Security_Guide-Server_Security-Securing_Sendmail.html" title="2.2.7. Securing Sendmail" /><link rel="next" href="sect-Security_Guide-Securing_Sendmail-Mail_only_Users.html" title="2.2.7.3. Mail-only Users" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><i
 mg src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Server_Security-Securing_Sendmail.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_Sendmail-Mail_only_Users.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Securing_Sendmail-NFS_and_Sendmail">2.2.7.2. NFS y Sendmail</h4></div></div></div><div class="para">
				Never put the mail spool directory, <code class="filename">/var/spool/mail/</code>, on an NFS shared volume.
			</div><div class="para">
				Because NFSv2 and NFSv3 do not maintain control over user and group IDs, two or more users can have the same UID, and receive and read each other's mail.
			</div><div class="note"><h2>Note</h2><div class="para">
					With NFSv4 using Kerberos, this is not the case, since the <code class="filename">SECRPC_GSS</code> kernel module does not utilize UID-based authentication. However, it is still considered good practice <span class="emphasis"><em>not</em></span> to put the mail spool directory on NFS shared volumes.
				</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Server_Security-Securing_Sendmail.html"><strong>Anterior</strong>2.2.7. Securing Sendmail</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_Sendmail-Mail_only_Users.html"><strong>Siguiente</strong>2.2.7.3. Mail-only Users</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Security_Updates.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.5. Actualizaciones de Seguridad</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="chap-Security_Guide-Security_Overview.html" title="CapÃtulo 1. Security Overview" /><link rel="prev" href="sect-Security_Guide-Common_Exploits_and_Attacks.html" title="1.4. Ataques y Aprovechadas ComÃºnes" /><link rel="next" href="sect-Security_Guide-Updating_Packages-Verifying_Signed_Packages.html" title="1.5.2. Verifying Signed Packages" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://do
 cs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Common_Exploits_and_Attacks.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Updating_Packages-Verifying_Signed_Packages.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h2 class="title" id="sect-Security_Guide-Security_Updates">1.5. Actualizaciones de Seguridad</h2></div></div></div><div class="para">
		As security vulnerabilities are discovered, the affected software must be updated in order to limit any potential security risks. If the software is part of a package within a Fedora distribution that is currently supported, Fedora is committed to releasing updated packages that fix the vulnerability as soon as is possible. Often, announcements about a given security exploit are accompanied with a patch (or source code that fixes the problem). This patch is then applied to the Fedora package and tested and released as an errata update. However, if an announcement does not include a patch, a developer first works with the maintainer of the software to fix the problem. Once the problem is fixed, the package is tested and released as an errata update.
	</div><div class="para">
		If an errata update is released for software used on your system, it is highly recommended that you update the affected packages as soon as possible to minimize the amount of time the system is potentially vulnerable.
	</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Security_Updates-Updating_Packages">1.5.1. Updating Packages</h3></div></div></div><div class="para">
			When updating software on a system, it is important to download the update from a trusted source. An attacker can easily rebuild a package with the same version number as the one that is supposed to fix the problem but with a different security exploit and release it on the Internet. If this happens, using security measures such as verifying files against the original RPM does not detect the exploit. Thus, it is very important to only download RPMs from trusted sources, such as from Fedora and to check the signature of the package to verify its integrity.
		</div><div class="note"><h2>Note</h2><div class="para">
				Fedora includes a convenient panel icon that displays visible alerts when there is an update for a Fedora system.
			</div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Common_Exploits_and_Attacks.html"><strong>Anterior</strong>1.4. Ataques y Aprovechadas ComÃºnes</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Updating_Packages-Verifying_Signed_Packages.html"><strong>Siguiente</strong>1.5.2. Verifying Signed Packages</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Server_Security-Securing_FTP.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.6. Securing FTP</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Server_Security.html" title="2.2. Server Security" /><link rel="prev" href="sect-Security_Guide-Server_Security-Securing_the_Apache_HTTP_Server.html" title="2.2.5. Securing the Apache HTTP Server" /><link rel="next" href="sect-Security_Guide-Securing_FTP-Anonymous_Access.html" title="2.2.6.2. Anonymous Access" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><im
 g src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Server_Security-Securing_the_Apache_HTTP_Server.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_FTP-Anonymous_Access.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Server_Security-Securing_FTP">2.2.6. Securing FTP</h3></div></div></div><div class="para">
			The <em class="firstterm">File Transfer Protocol</em> (<abbr class="abbrev">FTP</abbr>) is an older TCP protocol designed to transfer files over a network. Because all transactions with the server, including user authentication, are unencrypted, it is considered an insecure protocol and should be carefully configured.
		</div><div class="para">
			Fedora provee tres servidores FTP.
		</div><div class="itemizedlist"><ul><li><div class="para">
					<code class="command">gssftpd</code> â€” A Kerberos-aware <code class="command">xinetd</code>-based FTP daemon that does not transmit authentication information over the network.
				</div></li><li><div class="para">
					<span class="application"><strong>Red Hat Content Accelerator</strong></span> (<code class="command">tux</code>) â€” A kernel-space Web server with FTP capabilities.
				</div></li><li><div class="para">
					<code class="command">vsftpd</code> â€” A standalone, security oriented implementation of the FTP service.
				</div></li></ul></div><div class="para">
			The following security guidelines are for setting up the <code class="command">vsftpd</code> FTP service.
		</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Securing_FTP-FTP_Greeting_Banner">2.2.6.1. FTP Greeting Banner</h4></div></div></div><div class="para">
				Before submitting a username and password, all users are presented with a greeting banner. By default, this banner includes version information useful to crackers trying to identify weaknesses in a system.
			</div><div class="para">
				To change the greeting banner for <code class="command">vsftpd</code>, add the following directive to the <code class="filename">/etc/vsftpd/vsftpd.conf</code> file:
			</div><pre class="screen">ftpd_banner=<em class="replaceable"><code><insert_greeting_here></code></em>
</pre><div class="para">
				Replace <em class="replaceable"><code><insert_greeting_here></code></em> in the above directive with the text of the greeting message.
			</div><div class="para">
				For mutli-line banners, it is best to use a banner file. To simplify management of multiple banners, place all banners in a new directory called <code class="filename">/etc/banners/</code>. The banner file for FTP connections in this example is <code class="filename">/etc/banners/ftp.msg</code>. Below is an example of what such a file may look like:
			</div><pre class="screen">######### # Hello, all activity on ftp.example.com is logged. #########
</pre><div class="note"><h2>Note</h2><div class="para">
					It is not necessary to begin each line of the file with <code class="command">220</code> as specified in <a class="xref" href="sect-Security_Guide-Server_Security.html#sect-Security_Guide-Enhancing_Security_With_TCP_Wrappers-TCP_Wrappers_and_Connection_Banners" title="2.2.1.1.1. TCP Wrappers and Connection Banners">SecciÃ³nÂ 2.2.1.1.1, â€œTCP Wrappers and Connection Bannersâ€</a>.
				</div></div><div class="para">
				To reference this greeting banner file for <code class="command">vsftpd</code>, add the following directive to the <code class="filename">/etc/vsftpd/vsftpd.conf</code> file:
			</div><pre class="screen">banner_file=/etc/banners/ftp.msg
</pre><div class="para">
				It also is possible to send additional banners to incoming connections using TCP Wrappers as described in <a class="xref" href="sect-Security_Guide-Server_Security.html#sect-Security_Guide-Enhancing_Security_With_TCP_Wrappers-TCP_Wrappers_and_Connection_Banners" title="2.2.1.1.1. TCP Wrappers and Connection Banners">SecciÃ³nÂ 2.2.1.1.1, â€œTCP Wrappers and Connection Bannersâ€</a>.
			</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Server_Security-Securing_the_Apache_HTTP_Server.html"><strong>Anterior</strong>2.2.5. Securing the Apache HTTP Server</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_FTP-Anonymous_Access.html"><strong>Siguiente</strong>2.2.6.2. Anonymous Access</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Server_Security-Securing_NFS.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.4. Securing NFS</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Server_Security.html" title="2.2. Server Security" /><link rel="prev" href="sect-Security_Guide-Securing_NIS-Use_Kerberos_Authentication.html" title="2.2.3.5. Use Kerberos Authentication" /><link rel="next" href="sect-Security_Guide-Securing_NFS-Beware_of_Syntax_Errors.html" title="2.2.4.2. Beware of Syntax Errors" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org
 "><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_NIS-Use_Kerberos_Authentication.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_NFS-Beware_of_Syntax_Errors.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Server_Security-Securing_NFS">2.2.4. Securing NFS</h3></div></div></div><div class="important"><h2>Important</h2><div class="para">
				The version of NFS included in Fedora, NFSv4, no longer requires the <code class="command">portmap</code> service as outlined in <a class="xref" href="sect-Security_Guide-Server_Security-Securing_Portmap.html" title="2.2.2. Securing Portmap">SecciÃ³nÂ 2.2.2, â€œSecuring Portmapâ€</a>. NFS traffic now utilizes TCP in all versions, rather than UDP, and requires it when using NFSv4. NFSv4 now includes Kerberos user and group authentication, as part of the <code class="filename">RPCSEC_GSS</code> kernel module. Information on <code class="command">portmap</code> is still included, since Fedora supports NFSv2 and NFSv3, both of which utilize <code class="command">portmap</code>.
			</div></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Securing_NFS-Carefully_Plan_the_Network">2.2.4.1. Carefully Plan the Network</h4></div></div></div><div class="para">
				Now that NFSv4 has the ability to pass all information encrypted using Kerberos over a network, it is important that the service be configured correctly if it is behind a firewall or on a segmented network. NFSv2 and NFSv3 still pass data insecurely, and this should be taken into consideration. Careful network design in all of these regards can help prevent security breaches.
			</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_NIS-Use_Kerberos_Authentication.html"><strong>Anterior</strong>2.2.3.5. Use Kerberos Authentication</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_NFS-Beware_of_Syntax_Errors.html"><strong>Siguiente</strong>2.2.4.2. Beware of Syntax Errors</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Server_Security-Securing_NIS.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.3. Securing NIS</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Server_Security.html" title="2.2. Server Security" /><link rel="prev" href="sect-Security_Guide-Securing_Portmap-Protect_portmap_With_iptables.html" title="2.2.2.2. Protect portmap With iptables" /><link rel="next" href="sect-Security_Guide-Securing_NIS-Use_a_Password_like_NIS_Domain_Name_and_Hostname.html" title="2.2.3.2. Use a Password-like NIS Domain Name and Hostname" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" 
 /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_Portmap-Protect_portmap_With_iptables.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_NIS-Use_a_Password_like_NIS_Domain_Name_and_Hostname.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Server_Security-Securing_NIS">2.2.3. Securing NIS</h3></div></div></div><div class="para">
			The <em class="firstterm">Network Information Service</em> (<acronym class="acronym">NIS</acronym>) is an RPC service, called <code class="command">ypserv</code>, which is used in conjunction with <code class="command">portmap</code> and other related services to distribute maps of usernames, passwords, and other sensitive information to any computer claiming to be within its domain.
		</div><div class="para">
			An NIS server is comprised of several applications. They include the following:
		</div><div class="itemizedlist"><ul><li><div class="para">
					<code class="command">/usr/sbin/rpc.yppasswdd</code> â€” Also called the <code class="command">yppasswdd</code> service, this daemon allows users to change their NIS passwords.
				</div></li><li><div class="para">
					<code class="command">/usr/sbin/rpc.ypxfrd</code> â€” Also called the <code class="command">ypxfrd</code> service, this daemon is responsible for NIS map transfers over the network.
				</div></li><li><div class="para">
					<code class="command">/usr/sbin/yppush</code> â€” This application propagates changed NIS databases to multiple NIS servers.
				</div></li><li><div class="para">
					<code class="command">/usr/sbin/ypserv</code> â€” This is the NIS server daemon.
				</div></li></ul></div><div class="para">
			NIS is somewhat insecure by today's standards. It has no host authentication mechanisms and transmits all of its information over the network unencrypted, including password hashes. As a result, extreme care must be taken when setting up a network that uses NIS. This is further complicated by the fact that the default configuration of NIS is inherently insecure.
		</div><div class="para">
			It is recommended that anyone planning to implement an NIS server first secure the <code class="command">portmap</code> service as outlined in <a class="xref" href="sect-Security_Guide-Server_Security-Securing_Portmap.html" title="2.2.2. Securing Portmap">SecciÃ³nÂ 2.2.2, â€œSecuring Portmapâ€</a>, then address the following issues, such as network planning.
		</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Securing_NIS-Carefully_Plan_the_Network">2.2.3.1. Carefully Plan the Network</h4></div></div></div><div class="para">
				Because NIS transmits sensitive information unencrypted over the network, it is important the service be run behind a firewall and on a segmented and secure network. Whenever NIS information is transmitted over an insecure network, it risks being intercepted. Careful network design can help prevent severe security breaches.
			</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_Portmap-Protect_portmap_With_iptables.html"><strong>Anterior</strong>2.2.2.2. Protect portmap With iptables</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_NIS-Use_a_Password_like_NIS_Domain_Name_and_Hostname.html"><strong>Siguiente</strong>2.2.3.2. Use a Password-like NIS Domain Name and ...</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Server_Security-Securing_Portmap.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.2. Securing Portmap</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Server_Security.html" title="2.2. Server Security" /><link rel="prev" href="sect-Security_Guide-Server_Security.html" title="2.2. Server Security" /><link rel="next" href="sect-Security_Guide-Securing_Portmap-Protect_portmap_With_iptables.html" title="2.2.2.2. Protect portmap With iptables" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Co
 ntent/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Server_Security.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_Portmap-Protect_portmap_With_iptables.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Server_Security-Securing_Portmap">2.2.2. Securing Portmap</h3></div></div></div><div class="para">
			The <code class="command">portmap</code> service is a dynamic port assignment daemon for RPC services such as NIS and NFS. It has weak authentication mechanisms and has the ability to assign a wide range of ports for the services it controls. For these reasons, it is difficult to secure.
		</div><div class="note"><h2>Note</h2><div class="para">
				Securing <code class="command">portmap</code> only affects NFSv2 and NFSv3 implementations, since NFSv4 no longer requires it. If you plan to implement an NFSv2 or NFSv3 server, then <code class="command">portmap</code> is required, and the following section applies.
			</div></div><div class="para">
			If running RPC services, follow these basic rules.
		</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Securing_Portmap-Protect_portmap_With_TCP_Wrappers">2.2.2.1. Protect portmap With TCP Wrappers</h4></div></div></div><div class="para">
				It is important to use TCP Wrappers to limit which networks or hosts have access to the <code class="command">portmap</code> service since it has no built-in form of authentication.
			</div><div class="para">
				Further, use <span class="emphasis"><em>only</em></span> IP addresses when limiting access to the service. Avoid using hostnames, as they can be forged by DNS poisoning and other methods.
			</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Server_Security.html"><strong>Anterior</strong>2.2. Server Security</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_Portmap-Protect_portmap_With_iptables.html"><strong>Siguiente</strong>2.2.2.2. Protect portmap With iptables</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Server_Security-Securing_Sendmail.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.7. Securing Sendmail</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Server_Security.html" title="2.2. Server Security" /><link rel="prev" href="sect-Security_Guide-Securing_FTP-Use_TCP_Wrappers_To_Control_Access.html" title="2.2.6.4. Use TCP Wrappers To Control Access" /><link rel="next" href="sect-Security_Guide-Securing_Sendmail-NFS_and_Sendmail.html" title="2.2.7.2. NFS y Sendmail" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedorapro
 ject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_FTP-Use_TCP_Wrappers_To_Control_Access.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_Sendmail-NFS_and_Sendmail.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Server_Security-Securing_Sendmail">2.2.7. Securing Sendmail</h3></div></div></div><div class="para">
			Sendmail is a Mail Transfer Agent (MTA) that uses the Simple Mail Transfer Protocol (SMTP) to deliver electronic messages between other MTAs and to email clients or delivery agents. Although many MTAs are capable of encrypting traffic between one another, most do not, so sending email over any public networks is considered an inherently insecure form of communication.
		</div><div class="para">
			It is recommended that anyone planning to implement a Sendmail server address the following issues.
		</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Securing_Sendmail-Limiting_a_Denial_of_Service_Attack">2.2.7.1. Limiting a Denial of Service Attack</h4></div></div></div><div class="para">
				Because of the nature of email, a determined attacker can flood the server with mail fairly easily and cause a denial of service. By setting limits to the following directives in <code class="filename">/etc/mail/sendmail.mc</code>, the effectiveness of such attacks is limited.
			</div><div class="itemizedlist"><ul><li><div class="para">
						<code class="command">confCONNECTION_RATE_THROTTLE</code> â€” The number of connections the server can receive per second. By default, Sendmail does not limit the number of connections. If a limit is set and reached, further connections are delayed.
					</div></li><li><div class="para">
						<code class="command">confMAX_DAEMON_CHILDREN</code> â€” The maximum number of child processes that can be spawned by the server. By default, Sendmail does not assign a limit to the number of child processes. If a limit is set and reached, further connections are delayed.
					</div></li><li><div class="para">
						<code class="command">confMIN_FREE_BLOCKS</code> â€” The minimum number of free blocks which must be available for the server to accept mail. The default is 100 blocks.
					</div></li><li><div class="para">
						<code class="command">confMAX_HEADERS_LENGTH</code> â€” The maximum acceptable size (in bytes) for a message header.
					</div></li><li><div class="para">
						<code class="command">confMAX_MESSAGE_SIZE</code> â€” The maximum acceptable size (in bytes) for a single message.
					</div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_FTP-Use_TCP_Wrappers_To_Control_Access.html"><strong>Anterior</strong>2.2.6.4. Use TCP Wrappers To Control Access</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_Sendmail-NFS_and_Sendmail.html"><strong>Siguiente</strong>2.2.7.2. NFS y Sendmail</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Server_Security-Securing_the_Apache_HTTP_Server.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.5. Securing the Apache HTTP Server</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Server_Security.html" title="2.2. Server Security" /><link rel="prev" href="sect-Security_Guide-Securing_NFS-NFS_Firewall_Configuration.html" title="2.2.4.4. NFS Firewall Configuration" /><link rel="next" href="sect-Security_Guide-Server_Security-Securing_FTP.html" title="2.2.6. Securing FTP" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><i
 mg src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_NFS-NFS_Firewall_Configuration.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Server_Security-Securing_FTP.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Server_Security-Securing_the_Apache_HTTP_Server">2.2.5. Securing the Apache HTTP Server</h3></div></div></div><div class="para">
			The Apache HTTP Server is one of the most stable and secure services that ships with Fedora. A large number of options and techniques are available to secure the Apache HTTP Server â€” too numerous to delve into deeply here. The following section briefly explains good practices when running the Apache HTTP Server.
		</div><div class="para">
			Always verify that any scripts running on the system work as intended <span class="emphasis"><em>before</em></span> putting them into production. Also, ensure that only the root user has write permissions to any directory containing scripts or CGIs. To do this, run the following commands as the root user:
		</div><div class="orderedlist"><ol><li><pre class="screen">chown root <em class="replaceable"><code><directory_name></code></em>
</pre></li><li><pre class="screen">chmod 755 <em class="replaceable"><code><directory_name></code></em>
</pre></li></ol></div><div class="para">
			System administrators should be careful when using the following configuration options (configured in <code class="filename">/etc/httpd/conf/httpd.conf</code>):
		</div><div class="variablelist"><dl><dt><span class="term"><code class="option">FollowSymLinks</code></span></dt><dd><div class="para">
						This directive is enabled by default, so be sure to use caution when creating symbolic links to the document root of the Web server. For instance, it is a bad idea to provide a symbolic link to <code class="filename">/</code>.
					</div></dd><dt><span class="term"><code class="option">Indexes</code></span></dt><dd><div class="para">
						This directive is enabled by default, but may not be desirable. To prevent visitors from browsing files on the server, remove this directive.
					</div></dd><dt><span class="term"><code class="option">UserDir</code></span></dt><dd><div class="para">
						The <code class="option">UserDir</code> directive is disabled by default because it can confirm the presence of a user account on the system. To enable user directory browsing on the server, use the following directives:
					</div><div class="para">

<pre class="screen">UserDir enabled
UserDir disabled root
</pre>
					</div><div class="para">
						These directives activate user directory browsing for all user directories other than <code class="filename">/root/</code>. To add users to the list of disabled accounts, add a space-delimited list of users on the <code class="option">UserDir disabled</code> line.
					</div></dd></dl></div><div class="important"><h2>Importante</h2><div class="para">
				Do not remove the <code class="option">IncludesNoExec</code> directive. By default, the <em class="firstterm">Server-Side Includes</em> (<abbr class="abbrev">SSI</abbr>) module cannot execute commands. It is recommended that you do not change this setting unless absolutely necessary, as it could, potentially, enable an attacker to execute commands on the system.
			</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_NFS-NFS_Firewall_Configuration.html"><strong>Anterior</strong>2.2.4.4. NFS Firewall Configuration</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Server_Security-Securing_FTP.html"><strong>Siguiente</strong>2.2.6. Securing FTP</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Server_Security-Verifying_Which_Ports_Are_Listening.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.8. Verifying Which Ports Are Listening</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Server_Security.html" title="2.2. Server Security" /><link rel="prev" href="sect-Security_Guide-Securing_Sendmail-Mail_only_Users.html" title="2.2.7.3. Mail-only Users" /><link rel="next" href="sect-Security_Guide-Single_Sign_on_SSO.html" title="2.3. Single Sign-on (SSO)" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Co
 ntent/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_Sendmail-Mail_only_Users.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Single_Sign_on_SSO.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Server_Security-Verifying_Which_Ports_Are_Listening">2.2.8. Verifying Which Ports Are Listening</h3></div></div></div><div class="para">
			After configuring network services, it is important to pay attention to which ports are actually listening on the system's network interfaces. Any open ports can be evidence of an intrusion.
		</div><div class="para">
			There are two basic approaches for listing the ports that are listening on the network. The less reliable approach is to query the network stack using commands such as <code class="command">netstat -an</code> or <code class="command">lsof -i</code>. This method is less reliable since these programs do not connect to the machine from the network, but rather check to see what is running on the system. For this reason, these applications are frequent targets for replacement by attackers. Crackers attempt to cover their tracks if they open unauthorized network ports by replacing <code class="command">netstat</code> and <code class="command">lsof</code> with their own, modified versions.
		</div><div class="para">
			A more reliable way to check which ports are listening on the network is to use a port scanner such as <code class="command">nmap</code>.
		</div><div class="para">
			The following command issued from the console determines which ports are listening for TCP connections from the network:
		</div><pre class="screen">nmap -sT -O localhost
</pre><div class="para">
			The output of this command appears as follows:
		</div><pre class="screen">Starting Nmap 4.68 ( http://nmap.org ) at 2009-03-06 12:08 EST
Interesting ports on localhost.localdomain (127.0.0.1):
Not shown: 1711 closed ports
PORT      STATE SERVICE
22/tcp    open  ssh 
25/tcp    open  smtp
111/tcp   open  rpcbind
113/tcp   open  auth
631/tcp   open  ipp
834/tcp   open  unknown
2601/tcp  open  zebra
32774/tcp open  sometimes-rpc11
Device type: general purpose
Running: Linux 2.6.X
OS details: Linux 2.6.17 - 2.6.24
Uptime: 4.122 days (since Mon Mar  2 09:12:31 2009)
Network Distance: 0 hops
OS detection performed. Please report any incorrect results at http://nmap.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 1.420 seconds
</pre><div class="para">
			This output shows the system is running <code class="command">portmap</code> due to the presence of the <code class="computeroutput">sunrpc</code> service. However, there is also a mystery service on port 834. To check if the port is associated with the official list of known services, type:
		</div><pre class="screen">cat /etc/services | grep 834
</pre><div class="para">
			This command returns no output. This indicates that while the port is in the reserved range (meaning 0 through 1023) and requires root access to open, it is not associated with a known service.
		</div><div class="para">
			Next, check for information about the port using <code class="command">netstat</code> or <code class="command">lsof</code>. To check for port 834 using <code class="command">netstat</code>, use the following command:
		</div><pre class="screen">netstat -anp | grep 834
</pre><div class="para">
			The command returns the following output:
		</div><pre class="screen">tcp   0    0 0.0.0.0:834    0.0.0.0:*   LISTEN   653/ypbind
</pre><div class="para">
			The presence of the open port in <code class="command">netstat</code> is reassuring because a cracker opening a port surreptitiously on a hacked system is not likely to allow it to be revealed through this command. Also, the <code class="option">[p]</code> option reveals the process ID (PID) of the service that opened the port. In this case, the open port belongs to <code class="command">ypbind</code> (<abbr class="abbrev">NIS</abbr>), which is an <abbr class="abbrev">RPC</abbr> service handled in conjunction with the <code class="command">portmap</code> service.
		</div><div class="para">
			The <code class="command">lsof</code> command reveals similar information to <code class="command">netstat</code> since it is also capable of linking open ports to services:
		</div><pre class="screen">lsof -i | grep 834
</pre><div class="para">
			The relevant portion of the output from this command follows:
		</div><pre class="screen">ypbind      653        0    7u  IPv4       1319                 TCP *:834 (LISTEN)
ypbind      655        0    7u  IPv4       1319                 TCP *:834 (LISTEN)
ypbind      656        0    7u  IPv4       1319                 TCP *:834 (LISTEN)
ypbind      657        0    7u  IPv4       1319                 TCP *:834 (LISTEN)
</pre><div class="para">
			These tools reveal a great deal about the status of the services running on a machine. These tools are flexible and can provide a wealth of information about network services and configuration. Refer to the man pages for <code class="command">lsof</code>, <code class="command">netstat</code>, <code class="command">nmap</code>, and <code class="filename">services</code> for more information.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_Sendmail-Mail_only_Users.html"><strong>Anterior</strong>2.2.7.3. Mail-only Users</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Single_Sign_on_SSO.html"><strong>Siguiente</strong>2.3. Single Sign-on (SSO)</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Server_Security.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2. Server Security</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="chap-Security_Guide-Securing_Your_Network.html" title="CapÃtulo 2. Securing Your Network" /><link rel="prev" href="chap-Security_Guide-Securing_Your_Network.html" title="CapÃtulo 2. Securing Your Network" /><link rel="next" href="sect-Security_Guide-Server_Security-Securing_Portmap.html" title="2.2.2. Securing Portmap" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="C
 ommon_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security_Guide-Securing_Your_Network.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Server_Security-Securing_Portmap.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h2 class="title" id="sect-Security_Guide-Server_Security">2.2. Server Security</h2></div></div></div><div class="para">
		When a system is used as a server on a public network, it becomes a target for attacks. Hardening the system and locking down services is therefore of paramount importance for the system administrator.
	</div><div class="para">
		Before delving into specific issues, review the following general tips for enhancing server security:
	</div><div class="itemizedlist"><ul><li><div class="para">
				Keep all services current, to protect against the latest threats.
			</div></li><li><div class="para">
				Use secure protocols whenever possible.
			</div></li><li><div class="para">
				Serve only one type of network service per machine whenever possible.
			</div></li><li><div class="para">
				Monitor all servers carefully for suspicious activity.
			</div></li></ul></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Server_Security-Securing_Services_With_TCP_Wrappers_and_xinetd">2.2.1. Securing Services With TCP Wrappers and xinetd</h3></div></div></div><div class="para">
			<em class="firstterm">TCP Wrappers</em> provide access control to a variety of services. Most modern network services, such as SSH, Telnet, and FTP, make use of TCP Wrappers, which stand guard between an incoming request and the requested service.
		</div><div class="para">
			The benefits offered by TCP Wrappers are enhanced when used in conjunction with <code class="command">xinetd</code>, a super server that provides additional access, logging, binding, redirection, and resource utilization control.
		</div><div class="note"><h2>Note</h2><div class="para">
				It is a good idea to use iptables firewall rules in conjunction with TCP Wrappers and <code class="command">xinetd</code> to create redundancy within service access controls. Refer to <a class="xref" href="sect-Security_Guide-Firewalls.html" title="2.8. Firewalls">SecciÃ³nÂ 2.8, â€œFirewallsâ€</a> for more information about implementing firewalls with iptables commands.
			</div></div><div class="para">
			The following subsections assume a basic knowledge of each topic and focus on specific security options.
		</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Securing_Services_With_TCP_Wrappers_and_xinetd-Enhancing_Security_With_TCP_Wrappers">2.2.1.1. Enhancing Security With TCP Wrappers</h4></div></div></div><div class="para">
				TCP Wrappers are capable of much more than denying access to services. This section illustrates how they can be used to send connection banners, warn of attacks from particular hosts, and enhance logging functionality. Refer to the <code class="filename">hosts_options</code> man page for information about the TCP Wrapper functionality and control language.
			</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h5 class="title" id="sect-Security_Guide-Enhancing_Security_With_TCP_Wrappers-TCP_Wrappers_and_Connection_Banners">2.2.1.1.1. TCP Wrappers and Connection Banners</h5></div></div></div><div class="para">
					Displaying a suitable banner when users connect to a service is a good way to let potential attackers know that the system administrator is being vigilant. You can also control what information about the system is presented to users. To implement a TCP Wrappers banner for a service, use the <code class="option">banner</code> option.
				</div><div class="para">
					This example implements a banner for <code class="command">vsftpd</code>. To begin, create a banner file. It can be anywhere on the system, but it must have same name as the daemon. For this example, the file is called <code class="filename">/etc/banners/vsftpd</code> and contains the following line:
				</div><pre class="screen">220-Hello, %c 
220-All activity on ftp.example.com is logged.
220-Inappropriate use will result in your access privileges being removed.
</pre><div class="para">
					The <code class="command">%c</code> token supplies a variety of client information, such as the username and hostname, or the username and IP address to make the connection even more intimidating.
				</div><div class="para">
					For this banner to be displayed to incoming connections, add the following line to the <code class="filename">/etc/hosts.allow</code> file:
				</div><pre class="screen"><code class="command"> vsftpd : ALL : banners /etc/banners/ </code>
</pre></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h5 class="title" id="sect-Security_Guide-Enhancing_Security_With_TCP_Wrappers-TCP_Wrappers_and_Attack_Warnings">2.2.1.1.2. TCP Wrappers and Attack Warnings</h5></div></div></div><div class="para">
					If a particular host or network has been detected attacking the server, TCP Wrappers can be used to warn the administrator of subsequent attacks from that host or network using the <code class="command">spawn</code> directive.
				</div><div class="para">
					In this example, assume that a cracker from the 206.182.68.0/24 network has been detected attempting to attack the server. Place the following line in the <code class="filename">/etc/hosts.deny</code> file to deny any connection attempts from that network, and to log the attempts to a special file:
				</div><pre class="screen"><code class="command"> ALL : 206.182.68.0 : spawn /bin/ 'date' %c %d >> /var/log/intruder_alert </code>
</pre><div class="para">
					The <code class="command">%d</code> token supplies the name of the service that the attacker was trying to access.
				</div><div class="para">
					To allow the connection and log it, place the <code class="command">spawn</code> directive in the <code class="filename">/etc/hosts.allow</code> file.
				</div><div class="note"><h2>Note</h2><div class="para">
						Because the <code class="command">spawn</code> directive executes any shell command, it is a good idea to create a special script to notify the administrator or execute a chain of commands in the event that a particular client attempts to connect to the server.
					</div></div></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h5 class="title" id="sect-Security_Guide-Enhancing_Security_With_TCP_Wrappers-TCP_Wrappers_and_Enhanced_Logging">2.2.1.1.3. TCP Wrappers and Enhanced Logging</h5></div></div></div><div class="para">
					If certain types of connections are of more concern than others, the log level can be elevated for that service using the <code class="command">severity</code> option.
				</div><div class="para">
					For this example, assume that anyone attempting to connect to port 23 (the Telnet port) on an FTP server is a cracker. To denote this, place an <code class="command">emerg</code> flag in the log files instead of the default flag, <code class="command">info</code>, and deny the connection.
				</div><div class="para">
					To do this, place the following line in <code class="filename">/etc/hosts.deny</code>:
				</div><pre class="screen"><code class="command"> in.telnetd : ALL : severity emerg </code>
</pre><div class="para">
					This uses the default <code class="command">authpriv</code> logging facility, but elevates the priority from the default value of <code class="command">info</code> to <code class="command">emerg</code>, which posts log messages directly to the console.
				</div></div></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Securing_Services_With_TCP_Wrappers_and_xinetd-Enhancing_Security_With_xinetd">2.2.1.2. Enhancing Security With xinetd</h4></div></div></div><div class="para">
				This section focuses on using <code class="command">xinetd</code> to set a trap service and using it to control resource levels available to any given <code class="command">xinetd</code> service. Setting resource limits for services can help thwart <em class="firstterm">Denial of Service</em> (<acronym class="acronym">DoS</acronym>) attacks. Refer to the man pages for <code class="command">xinetd</code> and <code class="filename">xinetd.conf</code> for a list of available options.
			</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h5 class="title" id="sect-Security_Guide-Enhancing_Security_With_xinetd-Setting_a_Trap">2.2.1.2.1. Setting a Trap</h5></div></div></div><div class="para">
					One important feature of <code class="command">xinetd</code> is its ability to add hosts to a global <code class="filename">no_access</code> list. Hosts on this list are denied subsequent connections to services managed by <code class="command">xinetd</code> for a specified period or until <code class="command">xinetd</code> is restarted. You can do this using the <code class="command">SENSOR</code> attribute. This is an easy way to block hosts attempting to scan the ports on the server.
				</div><div class="para">
					The first step in setting up a <code class="command">SENSOR</code> is to choose a service you do not plan on using. For this example, Telnet is used.
				</div><div class="para">
					Edit the file <code class="filename">/etc/xinetd.d/telnet</code> and change the <code class="option">flags</code> line to read:
				</div><pre class="screen">flags           = SENSOR
</pre><div class="para">
					Add the following line:
				</div><pre class="screen">deny_time       = 30
</pre><div class="para">
					This denies any further connection attempts to that port by that host for 30 minutes. Other acceptable values for the <code class="command">deny_time</code> attribute are FOREVER, which keeps the ban in effect until <code class="command">xinetd</code> is restarted, and NEVER, which allows the connection and logs it.
				</div><div class="para">
					Finally, the last line should read:
				</div><pre class="screen">disable         = no
</pre><div class="para">
					This enables the trap itself.
				</div><div class="para">
					While using <code class="option">SENSOR</code> is a good way to detect and stop connections from undesirable hosts, it has two drawbacks:
				</div><div class="itemizedlist"><ul><li><div class="para">
							It does not work against stealth scans.
						</div></li><li><div class="para">
							An attacker who knows that a <code class="option">SENSOR</code> is running can mount a Denial of Service attack against particular hosts by forging their IP addresses and connecting to the forbidden port.
						</div></li></ul></div></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h5 class="title" id="sect-Security_Guide-Enhancing_Security_With_xinetd-Controlling_Server_Resources">2.2.1.2.2. Controlling Server Resources</h5></div></div></div><div class="para">
					Another important feature of <code class="command">xinetd</code> is its ability to set resource limits for services under its control.
				</div><div class="para">
					It does this using the following directives:
				</div><div class="itemizedlist"><ul><li><div class="para">
							<code class="option">cps = <number_of_connections> <wait_period></code> â€” Limits the rate of incoming connections. This directive takes two arguments:
						</div><div class="itemizedlist"><ul><li><div class="para">
									<code class="option"><number_of_connections></code> â€” The number of connections per second to handle. If the rate of incoming connections is higher than this, the service is temporarily disabled. The default value is fifty (50).
								</div></li><li><div class="para">
									<code class="option"><wait_period></code> â€” The number of seconds to wait before re-enabling the service after it has been disabled. The default interval is ten (10) seconds.
								</div></li></ul></div></li><li><div class="para">
							<code class="option">instances = <number_of_connections></code> â€” Specifies the total number of connections allowed to a service. This directive accepts either an integer value or <code class="command">UNLIMITED</code>.
						</div></li><li><div class="para">
							<code class="option">per_source = <number_of_connections></code> â€” Specifies the number of connections allowed to a service by each host. This directive accepts either an integer value or <code class="command">UNLIMITED</code>.
						</div></li><li><div class="para">
							<code class="option">rlimit_as = <number[K|M]></code> â€” Specifies the amount of memory address space the service can occupy in kilobytes or megabytes. This directive accepts either an integer value or <code class="command">UNLIMITED</code>.
						</div></li><li><div class="para">
							<code class="option">rlimit_cpu = <number_of_seconds></code> â€” Specifies the amount of time in seconds that a service may occupy the CPU. This directive accepts either an integer value or <code class="command">UNLIMITED</code>.
						</div></li></ul></div><div class="para">
					Using these directives can help prevent any single <code class="command">xinetd</code> service from overwhelming the system, resulting in a denial of service.
				</div></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security_Guide-Securing_Your_Network.html"><strong>Anterior</strong>CapÃtulo 2. Securing Your Network</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Server_Security-Securing_Portmap.html"><strong>Siguiente</strong>2.2.2. Securing Portmap</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Single_Sign_on_SSO-Configuring_Firefox_to_use_Kerberos_for_SSO.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.3.5. Configuring Firefox to use Kerberos for SSO</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Single_Sign_on_SSO.html" title="2.3. Single Sign-on (SSO)" /><link rel="prev" href="sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Login_Works.html" title="2.3.4. How Smart Card Login Works" /><link rel="next" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM.html" title="2.4. Pluggable Authentication Modules (PAM)" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a>
 <a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Login_Works.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Single_Sign_on_SSO-Configuring_Firefox_to_use_Kerberos_for_SSO">2.3.5. Configuring Firefox to use Kerberos for SSO</h3></div></div></div><div class="para">
			You can configure Firefox to use Kerberos for Single Sign-on. In order for this functionality to work correctly, you need to configure your web browser to send your Kerberos credentials to the appropriate <abbr class="abbrev">KDC</abbr>.The following section describes the configuration changes and other requirements to achieve this.
		</div><div class="orderedlist"><ol><li><div class="para">
					In the address bar of Firefox, type <strong class="userinput"><code>about:config</code></strong> to display the list of current configuration options.
				</div></li><li><div class="para">
					In the <span class="guilabel"><strong>Filter</strong></span> field, type <strong class="userinput"><code>negotiate</code></strong> to restrict the list of options.
				</div></li><li><div class="para">
					Double-click the <span class="emphasis"><em>network.negotiate-auth.trusted-uris</em></span> entry to display the <span class="emphasis"><em>Enter string value</em></span> dialog box.
				</div></li><li><div class="para">
					Enter the name of the domain against which you want to authenticate, for example, <em class="replaceable"><code>.example.com</code></em>.
				</div></li><li><div class="para">
					Repeat the above procedure for the <span class="emphasis"><em>network.negotiate-auth.delegation-uris</em></span> entry, using the same domain.
				</div><div class="para">
					<div class="note"><h2>Note</h2><div class="para">
							You can leave this value blank, as it allows Kerberos ticket passing, which is not required.
						</div><div class="para">
							If you do not see these two configuration options listed, your version of Firefox may be too old to support Negotiate authentication, and you should consider upgrading.
						</div></div>
				</div></li></ol></div><div class="figure" id="figu-Security_Guide-Configuring_Firefox_to_use_Kerberos_for_SSO-Configuring_Firefox_for_SSO_with_Kerberos"><div class="figure-contents"><div class="mediaobject"><img src="images/fed-firefox_kerberos_SSO.png" alt="Configuring Firefox for SSO with Kerberos" /><div class="longdesc"><div class="para">
						Configuring Firefox to use Kerberos for SSO.
					</div></div></div></div><h6>Figura 2.6. Configuring Firefox for SSO with Kerberos</h6></div><br class="figure-break" /><div class="para">
			You now need to ensure that you have Kerberos tickets. In a command shell, type <code class="command">kinit</code> to retrieve Kerberos tickets. To display the list of available tickets, type <code class="command">klist</code>. The following shows an example output from these commands:
		</div><pre class="screen">[user at host ~] $ kinit
Password for user at EXAMPLE.COM:

[user at host ~] $ klist
Ticket cache: FILE:/tmp/krb5cc_10920
Default principal: user at EXAMPLE.COM

Valid starting     Expires            Service principal
10/26/06 23:47:54  10/27/06 09:47:54  krbtgt/USER.COM at USER.COM
        renew until 10/26/06 23:47:54

Kerberos 4 ticket cache: /tmp/tkt10920
klist: You have no tickets cached
</pre><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Configuring_Firefox_to_use_Kerberos_for_SSO-Troubleshooting">2.3.5.1. Troubleshooting</h4></div></div></div><div class="para">
				If you have followed the configuration steps above and Negotiate authentication is not working, you can turn on verbose logging of the authentication process. This could help you find the cause of the problem. To enable verbose logging, use the following procedure:
			</div><div class="orderedlist"><ol><li><div class="para">
						Close all instances of Firefox.
					</div></li><li><div class="para">
						Open a command shell, and enter the following commands:
					</div><pre class="screen">export NSPR_LOG_MODULES=negotiateauth:5
export NSPR_LOG_FILE=/tmp/moz.log
</pre></li><li><div class="para">
						Restart Firefox <span class="emphasis"><em>from that shell</em></span>, and visit the website you were unable to authenticate to earlier. Information will be logged to <code class="filename">/tmp/moz.log</code>, and may give a clue to the problem. For example:
					</div><pre class="screen">-1208550944[90039d0]: entering nsNegotiateAuth::GetNextToken()
-1208550944[90039d0]: gss_init_sec_context() failed: Miscellaneous failure
No credentials cache found
</pre><div class="para">
						This indicates that you do not have Kerberos tickets, and need to run <code class="command">kinit</code>.
					</div></li></ol></div><div class="para">
				If you are able to run <code class="command">kinit</code> successfully from your machine but you are unable to authenticate, you might see something like this in the log file:
			</div><pre class="screen">-1208994096[8d683d8]: entering nsAuthGSSAPI::GetNextToken()
-1208994096[8d683d8]: gss_init_sec_context() failed: Miscellaneous failure
Server not found in Kerberos database
</pre><div class="para">
				This generally indicates a Kerberos configuration problem. Make sure that you have the correct entries in the [domain_realm] section of the <code class="filename">/etc/krb5.conf</code> file. For example:
			</div><pre class="screen">.example.com = EXAMPLE.COM
example.com = EXAMPLE.COM
</pre><div class="para">
				If nothing appears in the log it is possible that you are behind a proxy, and that proxy is stripping off the HTTP headers required for Negotiate authentication. As a workaround, you can try to connect to the server using HTTPS instead, which allows the request to pass through unmodified. Then proceed to debug using the log file, as described above.
			</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Login_Works.html"><strong>Anterior</strong>2.3.4. How Smart Card Login Works</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM.html"><strong>Siguiente</strong>2.4. Pluggable Authentication Modules (PAM)</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Single_Sign_on_SSO-Getting_Started_with_your_new_Smart_Card.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.3.2. Getting Started with your new Smart Card</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Single_Sign_on_SSO.html" title="2.3. Single Sign-on (SSO)" /><link rel="prev" href="sect-Security_Guide-Single_Sign_on_SSO.html" title="2.3. Single Sign-on (SSO)" /><link rel="next" href="sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Enrollment_Works.html" title="2.3.3. How Smart Card Enrollment Works" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http:/
 /docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Single_Sign_on_SSO.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Enrollment_Works.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Single_Sign_on_SSO-Getting_Started_with_your_new_Smart_Card">2.3.2. Getting Started with your new Smart Card</h3></div></div></div><div class="para">
			Before you can use your smart card to log in to your system and take advantage of the increased security options this technology provides, you need to perform some basic installation and configuration steps. These are described below.
		</div><div class="note"><h2>Note</h2><div class="para">
				This section provides a high-level view of getting started with your smart card. More detailed information is available in the Red Hat Certificate System Enterprise Security Client Guide.
			</div></div><div class="procedure"><ol class="1"><li><div class="para">
					Log in with your Kerberos name and password
				</div></li><li><div class="para">
					Make sure you have the <code class="filename">nss-tools</code> package loaded.
				</div></li><li><div class="para">
					Download and install your corporate-specific root certificates. Use the following command to install the root CA certificate:
				</div><pre class="screen">certutil -A -d /etc/pki/nssdb -n "root ca cert" -t "CT,C,C" -i ./ca_cert_in_base64_format.crt
</pre></li><li><div class="para">
					Verify that you have the following RPMs installed on your system: esc, pam_pkcs11, coolkey, ifd-egate, ccid, gdm, authconfig, and authconfig-gtk.
				</div></li><li><div class="para">
					Enable Smart Card Login Support
				</div><ol class="a"><li><div class="para">
							On the Gnome Title Bar, select System->Administration->Authentication.
						</div></li><li><div class="para">
							Type your machine's root password if necessary.
						</div></li><li><div class="para">
							In the Authentication Configuration dialog, click the <span class="guilabel"><strong>Authentication</strong></span> tab.
						</div></li><li><div class="para">
							Select the <span class="guilabel"><strong>Enable Smart Card Support</strong></span> check box.
						</div></li><li><div class="para">
							Click the <span class="guibutton"><strong>Configure Smart Card...</strong></span> button to display the Smartcard Settings dialog, and specify the required settings:
						</div><div class="para">
							<div class="itemizedlist"><ul><li><div class="para">
										<span class="guilabel"><strong>Require smart card for login</strong></span> â€” Clear this check box. After you have successfully logged in with the smart card you can select this option to prevent users from logging in without a smart card.
									</div></li><li><div class="para">
										<span class="guilabel"><strong>Card Removal Action</strong></span> â€” This controls what happens when you remove the smart card after you have logged in. The available options are:
									</div><div class="para">
										<div class="itemizedlist"><ul><li><div class="para">
													<span class="guilabel"><strong>Lock</strong></span> â€” Removing the smart card locks the X screen.
												</div></li><li><div class="para">
													<span class="guilabel"><strong>Ignore</strong></span> â€” Removing the smart card has no effect.
												</div></li></ul></div>
									</div></li></ul></div>
						</div></li></ol></li><li><div class="para">
					If you need to enable the Online Certificate Status Protocol (<abbr class="abbrev">OCSP</abbr>), open the <code class="filename">/etc/pam_pkcs11/pam_pkcs11.conf</code> file, and locate the following line:
				</div><div class="para">
					<code class="command">enable_ocsp = false;</code>
				</div><div class="para">
					Change this value to true, as follows:
				</div><div class="para">
					<code class="command">enable_ocsp = true;</code>
				</div></li><li><div class="para">
					Enroll your smart card
				</div></li><li><div class="para">
					If you are using a CAC card, you also need to perform the following steps:
				</div><ol class="a"><li><div class="para">
							Change to the root account and create a file called <code class="filename">/etc/pam_pkcs11/cn_map</code>.
						</div></li><li><div class="para">
							Add the following entry to the <code class="filename">cn_map</code> file:
						</div><div class="para">
							<em class="replaceable"><code>MY.CAC_CN.123454</code></em> -> <em class="replaceable"><code>myloginid</code></em>
						</div><div class="para">
							where <em class="replaceable"><code>MY.CAC_CN.123454</code></em> is the Common Name on your CAC and <em class="replaceable"><code>myloginid</code></em> is your UNIX login ID.
						</div></li></ol></li><li><div class="para">
					Salida
				</div></li></ol></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Getting_Started_with_your_new_Smart_Card-Troubleshooting">2.3.2.1. Troubleshooting</h4></div></div></div><div class="para">
				If you have trouble getting your smart card to work, try using the following command to locate the source of the problem:
			</div><pre class="screen">pklogin_finder debug
</pre><div class="para">
				If you run the <code class="command">pklogin_finder</code> tool in debug mode while an enrolled smart card is plugged in, it attempts to output information about the validity of certificates, and if it is successful in attempting to map a login ID from the certificates that are on the card.
			</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Single_Sign_on_SSO.html"><strong>Anterior</strong>2.3. Single Sign-on (SSO)</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Enrollment_Works.html"><strong>Siguiente</strong>2.3.3. How Smart Card Enrollment Works</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Enrollment_Works.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.3.3. How Smart Card Enrollment Works</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Single_Sign_on_SSO.html" title="2.3. Single Sign-on (SSO)" /><link rel="prev" href="sect-Security_Guide-Single_Sign_on_SSO-Getting_Started_with_your_new_Smart_Card.html" title="2.3.2. Getting Started with your new Smart Card" /><link rel="next" href="sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Login_Works.html" title="2.3.4. How Smart Card Login Works" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Produ
 ct Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Single_Sign_on_SSO-Getting_Started_with_your_new_Smart_Card.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Login_Works.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Enrollment_Works">2.3.3. How Smart Card Enrollment Works</h3></div></div></div><div class="para">
			Smart cards are said to be <em class="firstterm">enrolled</em> when they have received an appropriate certificate signed by a valid Certificate Authority (<abbr class="abbrev">CA</abbr>). This involves several steps, described below:
		</div><div class="orderedlist"><ol><li><div class="para">
					The user inserts their smart card into the smart card reader on their workstation. This event is recognized by the Enterprise Security Client (<abbr class="abbrev">ESC</abbr>).
				</div></li><li><div class="para">
					The enrollment page is displayed on the user's desktop. The user completes the required details and the user's system then connects to the Token Processing System (<abbr class="abbrev">TPS</abbr>) and the <abbr class="abbrev">CA</abbr>.
				</div></li><li><div class="para">
					The <abbr class="abbrev">TPS</abbr> enrolls the smart card using a certificate signed by the <abbr class="abbrev">CA</abbr>.
				</div></li></ol></div><div class="figure" id="figu-Security_Guide-How_Smart_Card_Enrollment_Works-How_Smart_Card_Enrollment_Works"><div class="figure-contents"><div class="mediaobject"><img src="images/SCLoginEnrollment.png" alt="How Smart Card Enrollment Works" /><div class="longdesc"><div class="para">
						How Smart Card Enrollment Works.
					</div></div></div></div><h6>Figura 2.4. How Smart Card Enrollment Works</h6></div><br class="figure-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Single_Sign_on_SSO-Getting_Started_with_your_new_Smart_Card.html"><strong>Anterior</strong>2.3.2. Getting Started with your new Smart Card</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Login_Works.html"><strong>Siguiente</strong>2.3.4. How Smart Card Login Works</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Login_Works.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.3.4. How Smart Card Login Works</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Single_Sign_on_SSO.html" title="2.3. Single Sign-on (SSO)" /><link rel="prev" href="sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Enrollment_Works.html" title="2.3.3. How Smart Card Enrollment Works" /><link rel="next" href="sect-Security_Guide-Single_Sign_on_SSO-Configuring_Firefox_to_use_Kerberos_for_SSO.html" title="2.3.5. Configuring Firefox to use Kerberos for SSO" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png"
  alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Enrollment_Works.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Single_Sign_on_SSO-Configuring_Firefox_to_use_Kerberos_for_SSO.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Login_Works">2.3.4. How Smart Card Login Works</h3></div></div></div><div class="para">
			This section provides a brief overview of the process of logging in using a smart card.
		</div><div class="orderedlist"><ol><li><div class="para">
					When the user inserts their smart card into the smart card reader, this event is recognized by the PAM facility, which prompts for the user's PIN.
				</div></li><li><div class="para">
					The system then looks up the user's current certificates and verifies their validity. The certificate is then mapped to the user's UID.
				</div></li><li><div class="para">
					This is validated against the KDC and login granted.
				</div></li></ol></div><div class="figure" id="figu-Security_Guide-How_Smart_Card_Login_Works-How_Smart_Card_Login_Works"><div class="figure-contents"><div class="mediaobject"><img src="images/SCLogin.png" alt="How Smart Card Login Works" /><div class="longdesc"><div class="para">
						How Smart Card Login Works.
					</div></div></div></div><h6>Figura 2.5. How Smart Card Login Works</h6></div><br class="figure-break" /><div class="note"><h2>Note</h2><div class="para">
				You cannot log in with a card that has not been enrolled, even if it has been formatted. You need to log in with a formatted, enrolled card, or not using a smart card, before you can enroll a new card.
			</div></div><div class="para">
			Refer to <a class="xref" href="sect-Security_Guide-Kerberos.html" title="2.6. Kerberos">SecciÃ³nÂ 2.6, â€œKerberosâ€</a> and <a class="xref" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM.html" title="2.4. Pluggable Authentication Modules (PAM)">SecciÃ³nÂ 2.4, â€œPluggable Authentication Modules (PAM)â€</a> for more information on Kerberos and <acronym class="acronym">PAM</acronym>.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Enrollment_Works.html"><strong>Anterior</strong>2.3.3. How Smart Card Enrollment Works</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Single_Sign_on_SSO-Configuring_Firefox_to_use_Kerberos_for_SSO.html"><strong>Siguiente</strong>2.3.5. Configuring Firefox to use Kerberos for SSO</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Single_Sign_on_SSO.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.3. Single Sign-on (SSO)</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="chap-Security_Guide-Securing_Your_Network.html" title="CapÃtulo 2. Securing Your Network" /><link rel="prev" href="sect-Security_Guide-Server_Security-Verifying_Which_Ports_Are_Listening.html" title="2.2.8. Verifying Which Ports Are Listening" /><link rel="next" href="sect-Security_Guide-Single_Sign_on_SSO-Getting_Started_with_your_new_Smart_Card.html" title="2.3.2. Getting Started with your new Smart Card" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.p
 ng" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Server_Security-Verifying_Which_Ports_Are_Listening.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Single_Sign_on_SSO-Getting_Started_with_your_new_Smart_Card.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h2 class="title" id="sect-Security_Guide-Single_Sign_on_SSO">2.3. Single Sign-on (SSO)</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-Single_Sign_on_SSO-Introduction">2.3.1. IntroducciÃ³n</h3></div></div></div><div class="para">
			The Fedora SSO functionality reduces the number of times Fedora desktop users have to enter their passwords. Several major applications leverage the same underlying authentication and authorization mechanisms so that users can log in to Fedora from the log-in screen, and then not need to re-enter their passwords. These applications are detailed below.
		</div><div class="para">
			In addition, users can log in to their machines even when there is no network (<em class="firstterm">offline mode</em>) or where network connectivity is unreliable, for example, wireless access. In the latter case, services will degrade gracefully.
		</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Introduction-Supported_Applications">2.3.1.1. Aplicaciones Soportadas</h4></div></div></div><div class="para">
				The following applications are currently supported by the unified log-in scheme in Fedora:
			</div><div class="itemizedlist"><ul><li><div class="para">
						Entrada
					</div></li><li><div class="para">
						Salvapantallas
					</div></li><li><div class="para">
						Firefox and Thunderbird
					</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-Introduction-Supported_Authentication_Mechanisms">2.3.1.2. Supported Authentication Mechanisms</h4></div></div></div><div class="para">
				Fedora currently supports the following authentication mechanisms:
			</div><div class="itemizedlist"><ul><li><div class="para">
						Kerberos name/password login
					</div></li><li><div class="para">
						Smart card/PIN login
					</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-Introduction-Supported_Smart_Cards">2.3.1.3. Supported Smart Cards</h4></div></div></div><div class="para">
				Fedora has been tested with the Cyberflex e-gate card and reader, but any card that complies with both Java card 2.1.1 and Global Platform 2.0.1 specifications should operate correctly, as should any reader that is supported by PCSC-lite.
			</div><div class="para">
				Fedora has also been tested with Common Access Cards (CAC). The supported reader for CAC is the SCM SCR 331 USB Reader.
			</div><div class="para">
				As of Fedora 5.2, Gemalto smart cards (Cyberflex Access 64k v2, standard with DER SHA1 value configured as in PKCSI v2.1) are now supported. These smart cards now use readers compliant with Chip/Smart Card Interface Devices (CCID).
			</div></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Introduction-Advantages_of_PROD_Single_Sign_on">2.3.1.4. Advantages of Fedora Single Sign-on</h4></div></div></div><div class="para">
				Numerous security mechanisms currently exist that utilize a large number of protocols and credential stores. Examples include SSL, SSH, IPsec, and Kerberos. Fedora SSO aims to unify these schemes to support the requirements listed above. This does not mean replacing Kerberos with X.509v3 certificates, but rather uniting them to reduce the burden on both system users and the administrators who manage them.
			</div><div class="para">
				To achieve this goal, Fedora:
			</div><div class="itemizedlist"><ul><li><div class="para">
						Provides a single, shared instance of the NSS crypto libraries on each operating system.
					</div></li><li><div class="para">
						Ships the Certificate System's Enterprise Security Client (ESC) with the base operating system. The ESC application monitors smart card insertion events. If it detects that the user has inserted a smart card that was designed to be used with the Fedora Certificate System server product, it displays a user interface instructing the user how to enroll that smart card.
					</div></li><li><div class="para">
						Unifies Kerberos and NSS so that users who log in to the operating system using a smart card also obtain a Kerberos credential (which allows them to log in to file servers, etc.)
					</div></li></ul></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Server_Security-Verifying_Which_Ports_Are_Listening.html"><strong>Anterior</strong>2.2.8. Verifying Which Ports Are Listening</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Single_Sign_on_SSO-Getting_Started_with_your_new_Smart_Card.html"><strong>Siguiente</strong>2.3.2. Getting Started with your new Smart Card</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Software_Maintenance-Install_Signed_Packages_from_Well_Known_Repositories.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.4. Install Signed Packages from Well Known Repositories</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="chap-Security_Guide-Software_Maintenance.html" title="CapÃtulo 6. Mantenimiento de Software" /><link rel="prev" href="sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates-Adjusting_Automatic_Updates.html" title="6.3. Ajustando Actualizaciones AutomÃ¡ticas" /><link rel="next" href="chap-Security_Guide-References.html" title="CapÃtulo 7. Referencias" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png"
  alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates-Adjusting_Automatic_Updates.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="chap-Security_Guide-References.html"><strong>Siguiente</strong></a></li></ul><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.
		</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.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates-Adjusting_Automatic_Updates.html"><strong>Anterior</strong>6.3. Ajustando Actualizaciones AutomÃ¡ticas</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="chap-Security_Guide-References.html"><strong>Siguiente</strong>CapÃtulo 7. Referencias</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates-Adjusting_Automatic_Updates.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.3. Ajustando Actualizaciones AutomÃ¡ticas</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="chap-Security_Guide-Software_Maintenance.html" title="CapÃtulo 6. Mantenimiento de Software" /><link rel="prev" href="sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates.html" title="6.2. Plan and Configure Security Updates" /><link rel="next" href="sect-Security_Guide-Software_Maintenance-Install_Signed_Packages_from_Well_Known_Repositories.html" title="6.4. Install Signed Packages from Well Known Repositories" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.o
 rg"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Software_Maintenance-Install_Signed_Packages_from_Well_Known_Repositories.html"><strong>Siguiente</strong></a></li></ul><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.
		</div><div class="para">
			In Gnome, you can find controls for your updates at: <code class="code">System -> Preferences -> System -> Software Updates</code>. In KDE it is located at: <code class="code">Applications -> Settings -> Software Updates</code>.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates.html"><strong>Anterior</strong>6.2. Plan and Configure Security Updates</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Software_Maintenance-Install_Signed_Packages_from_Well_Known_Repositories.html"><strong>Siguiente</strong>6.4. Install Signed Packages from Well Known Repo...</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.2. Plan and Configure Security Updates</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="chap-Security_Guide-Software_Maintenance.html" title="CapÃtulo 6. Mantenimiento de Software" /><link rel="prev" href="chap-Security_Guide-Software_Maintenance.html" title="CapÃtulo 6. Mantenimiento de Software" /><link rel="next" href="sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates-Adjusting_Automatic_Updates.html" title="6.3. Ajustando Actualizaciones AutomÃ¡ticas" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_le
 ft.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security_Guide-Software_Maintenance.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates-Adjusting_Automatic_Updates.html"><strong>Siguiente</strong></a></li></ul><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.
		</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.
		</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><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security_Guide-Software_Maintenance.html"><strong>Anterior</strong>CapÃtulo 6. Mantenimiento de Software</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates-Adjusting_Automatic_Updates.html"><strong>Siguiente</strong>6.3. Ajustando Actualizaciones AutomÃ¡ticas</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-TCP_Wrappers_Configuration_Files-Option_Fields.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.5.2.2. Option Fields</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers_Configuration_Files.html" title="2.5.2. TCP Wrappers Configuration Files" /><link rel="prev" href="sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers_Configuration_Files.html" title="2.5.2. TCP Wrappers Configuration Files" /><link rel="next" href="sect-Security_Guide-Option_Fields-Access_Control.html" title="2.5.2.2.2. Control de Acceso" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Pr
 oduct Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers_Configuration_Files.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Option_Fields-Access_Control.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-TCP_Wrappers_Configuration_Files-Option_Fields">2.5.2.2. Option Fields</h4></div></div></div><div class="para">
				In addition to basic rules that allow and deny access, the Fedora implementation of TCP Wrappers supports extensions to the access control language through <em class="firstterm">option fields</em>. By using option fields in hosts access rules, administrators can accomplish a variety of tasks such as altering log behavior, consolidating access control, and launching shell commands.
			</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h5 class="title" id="sect-Security_Guide-Option_Fields-Logging">2.5.2.2.1. Logging</h5></div></div></div><div class="para">
					Option fields let administrators easily change the log facility and priority level for a rule by using the <code class="option">severity</code> directive.
				</div><div class="para">
					In the following example, connections to the SSH daemon from any host in the <code class="systemitem">example.com</code> domain are logged to the default <code class="option">authpriv</code> <code class="option">syslog</code> facility (because no facility value is specified) with a priority of <code class="option">emerg</code>:
				</div><pre class="screen">sshd : .example.com : severity emerg
</pre><div class="para">
					It is also possible to specify a facility using the <code class="option">severity</code> option. The following example logs any SSH connection attempts by hosts from the <code class="systemitem">example.com</code> domain to the <code class="option">local0</code> facility with a priority of <code class="option">alert</code>:
				</div><pre class="screen">sshd : .example.com : severity local0.alert
</pre><div class="note"><h2>Note</h2><div class="para">
						In practice, this example does not work until the syslog daemon (<code class="systemitem">syslogd</code>) is configured to log to the <code class="command">local0</code> facility. Refer to the <code class="filename">syslog.conf</code> man page for information about configuring custom log facilities.
					</div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers_Configuration_Files.html"><strong>Anterior</strong>2.5.2. TCP Wrappers Configuration Files</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Option_Fields-Access_Control.html"><strong>Siguiente</strong>2.5.2.2.2. Control de Acceso</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-TCP_Wrappers_and_xinetd-Additional_Resources.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.5.5. Additional Resources</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-TCP_Wrappers_and_xinetd.html" title="2.5. TCP Wrappers and xinetd" /><link rel="prev" href="sect-Security_Guide-Altering_xinetd_Configuration_Files-Resource_Management_Options.html" title="2.5.4.3.4. Resource Management Options" /><link rel="next" href="sect-Security_Guide-Additional_Resources-Useful_TCP_Wrappers_Websites.html" title="2.5.5.2. Useful TCP Wrappers Websites" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Produ
 ct Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Altering_xinetd_Configuration_Files-Resource_Management_Options.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Additional_Resources-Useful_TCP_Wrappers_Websites.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-TCP_Wrappers_and_xinetd-Additional_Resources">2.5.5. Additional Resources</h3></div></div></div><div class="para">
			More information about TCP Wrappers and <code class="systemitem">xinetd</code> is available from system documentation and on the Internet.
		</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Additional_Resources-Installed_TCP_Wrappers_Documentation">2.5.5.1. Installed TCP Wrappers Documentation</h4></div></div></div><div class="para">
				The documentation on your system is a good place to start looking for additional configuration options for TCP Wrappers, <code class="systemitem">xinetd</code>, and access control.
			</div><div class="itemizedlist"><ul><li><div class="para">
						<code class="filename">/usr/share/doc/tcp_wrappers-<em class="replaceable"><code><version></code></em>/</code> â€” This directory contains a <code class="filename">README</code> file that discusses how TCP Wrappers work and the various hostname and host address spoofing risks that exist.
					</div></li><li><div class="para">
						<code class="filename">/usr/share/doc/xinetd-<em class="replaceable"><code><version></code></em>/</code> â€” This directory contains a <code class="filename">README</code> file that discusses aspects of access control and a <code class="filename">sample.conf</code> file with various ideas for modifying service-specific configuration files in the <code class="filename">/etc/xinetd.d/</code> directory.
					</div></li><li><div class="para">
						TCP Wrappers and <code class="systemitem">xinetd</code>-related man pages â€” A number of man pages exist for the various applications and configuration files involved with TCP Wrappers and <code class="systemitem">xinetd</code>. The following are some of the more important man pages:
					</div><div class="variablelist"><dl><dt><span class="term">Server Applications</span></dt><dd><div class="itemizedlist"><ul><li><div class="para">
											<code class="command">man xinetd</code> â€” The man page for <code class="systemitem">xinetd</code>.
										</div></li></ul></div></dd><dt><span class="term">Configuration Files</span></dt><dd><div class="itemizedlist"><ul><li><div class="para">
											<code class="command">man 5 hosts_access</code> â€” The man page for the TCP Wrappers hosts access control files.
										</div></li><li><div class="para">
											<code class="command">man hosts_options</code> â€” The man page for the TCP Wrappers options fields.
										</div></li><li><div class="para">
											<code class="command">man xinetd.conf</code> â€” The man page listing <code class="systemitem">xinetd</code> configuration options.
										</div></li></ul></div></dd></dl></div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Altering_xinetd_Configuration_Files-Resource_Management_Options.html"><strong>Anterior</strong>2.5.4.3.4. Resource Management Options</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Additional_Resources-Useful_TCP_Wrappers_Websites.html"><strong>Siguiente</strong>2.5.5.2. Useful TCP Wrappers Websites</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers_Configuration_Files.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.5.2. TCP Wrappers Configuration Files</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-TCP_Wrappers_and_xinetd.html" title="2.5. TCP Wrappers and xinetd" /><link rel="prev" href="sect-Security_Guide-TCP_Wrappers_and_xinetd.html" title="2.5. TCP Wrappers and xinetd" /><link rel="next" href="sect-Security_Guide-TCP_Wrappers_Configuration_Files-Option_Fields.html" title="2.5.2.2. Option Fields" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedora
 project.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-TCP_Wrappers_and_xinetd.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-TCP_Wrappers_Configuration_Files-Option_Fields.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers_Configuration_Files">2.5.2. TCP Wrappers Configuration Files</h3></div></div></div><div class="para">
			To determine if a client is allowed to connect to a service, TCP Wrappers reference the following two files, which are commonly referred to as <em class="firstterm">hosts access</em> files:
		</div><div class="itemizedlist"><ul><li><div class="para">
					<code class="filename">/etc/hosts.allow</code>
				</div></li><li><div class="para">
					<code class="filename">/etc/hosts.deny</code>
				</div></li></ul></div><div class="para">
			When a TCP-wrapped service receives a client request, it performs the following steps:
		</div><div class="orderedlist"><ol><li><div class="para">
					<span class="emphasis"><em>It references <code class="filename">/etc/hosts.allow</code>.</em></span> â€” The TCP-wrapped service sequentially parses the <code class="filename">/etc/hosts.allow</code> file and applies the first rule specified for that service. If it finds a matching rule, it allows the connection. If not, it moves on to the next step.
				</div></li><li><div class="para">
					<span class="emphasis"><em>It references <code class="filename">/etc/hosts.deny</code>.</em></span> â€” The TCP-wrapped service sequentially parses the <code class="filename">/etc/hosts.deny</code> file. If it finds a matching rule, it denies the connection. If not, it grants access to the service.
				</div></li></ol></div><div class="para">
			The following are important points to consider when using TCP Wrappers to protect network services:
		</div><div class="itemizedlist"><ul><li><div class="para">
					Because access rules in <code class="filename">hosts.allow</code> are applied first, they take precedence over rules specified in <code class="filename">hosts.deny</code>. Therefore, if access to a service is allowed in <code class="filename">hosts.allow</code>, a rule denying access to that same service in <code class="filename">hosts.deny</code> is ignored.
				</div></li><li><div class="para">
					The rules in each file are read from the top down and the first matching rule for a given service is the only one applied. The order of the rules is extremely important.
				</div></li><li><div class="para">
					If no rules for the service are found in either file, or if neither file exists, access to the service is granted.
				</div></li><li><div class="para">
					TCP-wrapped services do not cache the rules from the hosts access files, so any changes to <code class="filename">hosts.allow</code> or <code class="filename">hosts.deny</code> take effect immediately, without restarting network services.
				</div></li></ul></div><div class="warning"><h2>Warning</h2><div class="para">
				If the last line of a hosts access file is not a newline character (created by pressing the <span class="keycap"><strong>Enter</strong></span> key), the last rule in the file fails and an error is logged to either <code class="filename">/var/log/messages</code> or <code class="filename">/var/log/secure</code>. This is also the case for a rule that spans multiple lines without using the backslash character. The following example illustrates the relevant portion of a log message for a rule failure due to either of these circumstances:
			</div><pre class="screen">warning: /etc/hosts.allow, line 20: missing newline or line too long
</pre></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-TCP_Wrappers_Configuration_Files-Formatting_Access_Rules">2.5.2.1. Formatting Access Rules</h4></div></div></div><div class="para">
				The format for both <code class="filename">/etc/hosts.allow</code> and <code class="filename">/etc/hosts.deny</code> is identical. Each rule must be on its own line. Blank lines or lines that start with a hash (#) are ignored.
			</div><div class="para">
				Each rule uses the following basic format to control access to network services:
			</div><pre class="screen"><em class="replaceable"><code><daemon list></code></em>: <em class="replaceable"><code><client list></code></em> [: <em class="replaceable"><code><option></code></em>: <em class="replaceable"><code><option></code></em>: ...]
</pre><div class="itemizedlist"><ul><li><div class="para">
						<em class="replaceable"><code><daemon list></code></em> â€” A comma-separated list of process names (<span class="emphasis"><em>not</em></span> service names) or the <code class="option">ALL</code> wildcard. The daemon list also accepts operators (refer to <a class="xref" href="sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers_Configuration_Files.html#sect-Security_Guide-Formatting_Access_Rules-Operators" title="2.5.2.1.4. Operadores">SecciÃ³nÂ 2.5.2.1.4, â€œOperadoresâ€</a>) to allow greater flexibility.
					</div></li><li><div class="para">
						<em class="replaceable"><code><client list></code></em> â€” A comma-separated list of hostnames, host IP addresses, special patterns, or wildcards which identify the hosts affected by the rule. The client list also accepts operators listed in <a class="xref" href="sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers_Configuration_Files.html#sect-Security_Guide-Formatting_Access_Rules-Operators" title="2.5.2.1.4. Operadores">SecciÃ³nÂ 2.5.2.1.4, â€œOperadoresâ€</a> to allow greater flexibility.
					</div></li><li><div class="para">
						<em class="replaceable"><code><option></code></em> â€” An optional action or colon-separated list of actions performed when the rule is triggered. Option fields support expansions, launch shell commands, allow or deny access, and alter logging behavior.
					</div></li></ul></div><div class="note"><h2>Note</h2><div class="para">
					More information on the specialist terms above can be found elsewhere in this Guide:
				</div><div class="itemizedlist"><ul><li><div class="para">
							<a class="xref" href="sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers_Configuration_Files.html#sect-Security_Guide-Formatting_Access_Rules-Wildcards" title="2.5.2.1.1. Wildcards">SecciÃ³nÂ 2.5.2.1.1, â€œWildcardsâ€</a>
						</div></li><li><div class="para">
							<a class="xref" href="sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers_Configuration_Files.html#sect-Security_Guide-Formatting_Access_Rules-Patterns" title="2.5.2.1.2. Patrones">SecciÃ³nÂ 2.5.2.1.2, â€œPatronesâ€</a>
						</div></li><li><div class="para">
							<a class="xref" href="sect-Security_Guide-Option_Fields-Expansions.html" title="2.5.2.2.4. Expansions">SecciÃ³nÂ 2.5.2.2.4, â€œExpansionsâ€</a>
						</div></li><li><div class="para">
							<a class="xref" href="sect-Security_Guide-TCP_Wrappers_Configuration_Files-Option_Fields.html" title="2.5.2.2. Option Fields">SecciÃ³nÂ 2.5.2.2, â€œOption Fieldsâ€</a>
						</div></li></ul></div></div><div class="para">
				The following is a basic sample hosts access rule:
			</div><pre class="screen">vsftpd : .ejemplo.com
</pre><div class="para">
				This rule instructs TCP Wrappers to watch for connections to the FTP daemon (<code class="systemitem">vsftpd</code>) from any host in the <code class="systemitem">example.com</code> domain. If this rule appears in <code class="filename">hosts.allow</code>, the connection is accepted. If this rule appears in <code class="filename">hosts.deny</code>, the connection is rejected.
			</div><div class="para">
				The next sample hosts access rule is more complex and uses two option fields:
			</div><pre class="screen">sshd : .example.com  \ : spawn /bin/echo `/bin/date` access denied>>/var/log/sshd.log \ : deny
</pre><div class="para">
				Note that each option field is preceded by the backslash (\). Use of the backslash prevents failure of the rule due to length.
			</div><div class="para">
				This sample rule states that if a connection to the SSH daemon (<code class="systemitem">sshd</code>) is attempted from a host in the <code class="systemitem">example.com</code> domain, execute the <code class="command">echo</code> command to append the attempt to a special log file, and deny the connection. Because the optional <code class="command">deny</code> directive is used, this line denies access even if it appears in the <code class="filename">hosts.allow</code> file. Refer to <a class="xref" href="sect-Security_Guide-TCP_Wrappers_Configuration_Files-Option_Fields.html" title="2.5.2.2. Option Fields">SecciÃ³nÂ 2.5.2.2, â€œOption Fieldsâ€</a> for a more detailed look at available options.
			</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h5 class="title" id="sect-Security_Guide-Formatting_Access_Rules-Wildcards">2.5.2.1.1. Wildcards</h5></div></div></div><div class="para">
					Wildcards allow TCP Wrappers to more easily match groups of daemons or hosts. They are used most frequently in the client list field of access rules.
				</div><div class="para">
					The following wildcards are available:
				</div><div class="itemizedlist"><ul><li><div class="para">
							<code class="option">ALL</code> â€” Matches everything. It can be used for both the daemon list and the client list.
						</div></li><li><div class="para">
							<code class="option">LOCAL</code> â€” Matches any host that does not contain a period (.), such as localhost.
						</div></li><li><div class="para">
							<code class="option">KNOWN</code> â€” Matches any host where the hostname and host address are known or where the user is known.
						</div></li><li><div class="para">
							<code class="option">UNKNOWN</code> â€” Matches any host where the hostname or host address are unknown or where the user is unknown.
						</div></li><li><div class="para">
							<code class="option">PARANOID</code> â€” Matches any host where the hostname does not match the host address.
						</div></li></ul></div><div class="important"><h2>Important</h2><div class="para">
						The <code class="option">KNOWN</code>, <code class="option">UNKNOWN</code>, and <code class="option">PARANOID</code> wildcards should be used with care, because they rely on functioning DNS server for correct operation. Any disruption to name resolution may prevent legitimate users from gaining access to a service.
					</div></div></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h5 class="title" id="sect-Security_Guide-Formatting_Access_Rules-Patterns">2.5.2.1.2. Patrones</h5></div></div></div><div class="para">
					Patterns can be used in the client field of access rules to more precisely specify groups of client hosts.
				</div><div class="para">
					The following is a list of common patterns for entries in the client field:
				</div><div class="itemizedlist"><ul><li><div class="para">
							<span class="emphasis"><em>Hostname beginning with a period (.)</em></span> â€” Placing a period at the beginning of a hostname matches all hosts sharing the listed components of the name. The following example applies to any host within the <code class="systemitem">example.com</code> domain:
						</div><pre class="screen">ALL : .ejemplo.com
</pre></li><li><div class="para">
							<span class="emphasis"><em>IP address ending with a period (.)</em></span> â€” Placing a period at the end of an IP address matches all hosts sharing the initial numeric groups of an IP address. The following example applies to any host within the <code class="systemitem">192.168.x.x</code> network:
						</div><pre class="screen">ALL : 192.168.
</pre></li><li><div class="para">
							<span class="emphasis"><em>IP address/netmask pair</em></span> â€” Netmask expressions can also be used as a pattern to control access to a particular group of IP addresses. The following example applies to any host with an address range of <code class="systemitem">192.168.0.0</code> through <code class="systemitem">192.168.1.255</code>:
						</div><pre class="screen">ALL : 192.168.0.0/255.255.254.0
</pre><div class="important"><h2>Important</h2><div class="para">
								When working in the IPv4 address space, the address/prefix length (<em class="firstterm">prefixlen</em>) pair declarations (<abbr class="abbrev">CIDR</abbr> notation) are not supported. Only IPv6 rules can use this format.
							</div></div></li><li><div class="para">
							<span class="emphasis"><em>[IPv6 address]/prefixlen pair</em></span> â€” [net]/prefixlen pairs can also be used as a pattern to control access to a particular group of IPv6 addresses. The following example would apply to any host with an address range of <code class="systemitem">3ffe:505:2:1::</code> through <code class="systemitem">3ffe:505:2:1:ffff:ffff:ffff:ffff</code>:
						</div><pre class="screen">ALL : [3ffe:505:2:1::]/64
</pre></li><li><div class="para">
							<span class="emphasis"><em>The asterisk (*)</em></span> â€” Asterisks can be used to match entire groups of hostnames or IP addresses, as long as they are not mixed in a client list containing other types of patterns. The following example would apply to any host within the <code class="systemitem">example.com</code> domain:
						</div><pre class="screen">ALL : *.ejemplo.com
</pre></li><li><div class="para">
							<span class="emphasis"><em>The slash (/)</em></span> â€” If a client list begins with a slash, it is treated as a file name. This is useful if rules specifying large numbers of hosts are necessary. The following example refers TCP Wrappers to the <code class="filename">/etc/telnet.hosts</code> file for all Telnet connections:
						</div><pre class="screen">in.telnetd : /etc/telnet.hosts
</pre></li></ul></div><div class="para">
					Other, lesser used, patterns are also accepted by TCP Wrappers. Refer to the <code class="filename">hosts_access</code> man 5 page for more information.
				</div><div class="warning"><h2>Warning</h2><div class="para">
						Be very careful when using hostnames and domain names. Attackers can use a variety of tricks to circumvent accurate name resolution. In addition, disruption to DNS service prevents even authorized users from using network services. It is, therefore, best to use IP addresses whenever possible.
					</div></div></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h5 class="title" id="sect-Security_Guide-Formatting_Access_Rules-Portmap_and_TCP_Wrappers">2.5.2.1.3. Portmap and TCP Wrappers</h5></div></div></div><div class="para">
					<code class="command">Portmap</code>'s implementation of TCP Wrappers does not support host look-ups, which means <code class="command">portmap</code> can not use hostnames to identify hosts. Consequently, access control rules for portmap in <code class="filename">hosts.allow</code> or <code class="filename">hosts.deny</code> must use IP addresses, or the keyword <code class="option">ALL</code>, for specifying hosts.
				</div><div class="para">
					Changes to <code class="command">portmap</code> access control rules may not take effect immediately. You may need to restart the <code class="command">portmap</code> service.
				</div><div class="para">
					Widely used services, such as NIS and NFS, depend on <code class="command">portmap</code> to operate, so be aware of these limitations.
				</div></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h5 class="title" id="sect-Security_Guide-Formatting_Access_Rules-Operators">2.5.2.1.4. Operadores</h5></div></div></div><div class="para">
					At present, access control rules accept one operator, <code class="option">EXCEPT</code>. It can be used in both the daemon list and the client list of a rule.
				</div><div class="para">
					The <code class="option">EXCEPT</code> operator allows specific exceptions to broader matches within the same rule.
				</div><div class="para">
					In the following example from a <code class="filename">hosts.allow</code> file, all <code class="systemitem">example.com</code> hosts are allowed to connect to all services except <code class="systemitem">cracker.example.com</code>:
				</div><pre class="screen">ALL: .example.com EXCEPT cracker.example.com
</pre><div class="para">
					In another example from a <code class="filename">hosts.allow</code> file, clients from the <code class="systemitem">192.168.0.<em class="replaceable"><code>x</code></em></code> network can use all services except for FTP:
				</div><pre class="screen">ALL EXCEPT vsftpd: 192.168.0.
</pre><div class="note"><h2>Note</h2><div class="para">
						Organizationally, it is often easier to avoid using <code class="option">EXCEPT</code> operators. This allows other administrators to quickly scan the appropriate files to see what hosts are allowed or denied access to services, without having to sort through <code class="option">EXCEPT</code> operators.
					</div></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-TCP_Wrappers_and_xinetd.html"><strong>Anterior</strong>2.5. TCP Wrappers and xinetd</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-TCP_Wrappers_Configuration_Files-Option_Fields.html"><strong>Siguiente</strong>2.5.2.2. Option Fields</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.5.3. xinetd</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-TCP_Wrappers_and_xinetd.html" title="2.5. TCP Wrappers and xinetd" /><link rel="prev" href="sect-Security_Guide-Option_Fields-Expansions.html" title="2.5.2.2.4. Expansions" /><link rel="next" href="sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd_Configuration_Files.html" title="2.5.4. xinetd Configuration Files" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img
  src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Option_Fields-Expansions.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd_Configuration_Files.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd">2.5.3. xinetd</h3></div></div></div><div class="para">
			The <code class="systemitem">xinetd</code> daemon is a TCP-wrapped <em class="firstterm">super service</em> which controls access to a subset of popular network services, including FTP, IMAP, and Telnet. It also provides service-specific configuration options for access control, enhanced logging, binding, redirection, and resource utilization control.
		</div><div class="para">
			When a client attempts to connect to a network service controlled by <code class="systemitem">xinetd</code>, the super service receives the request and checks for any TCP Wrappers access control rules.
		</div><div class="para">
			If access is allowed, <code class="systemitem">xinetd</code> verifies that the connection is allowed under its own access rules for that service. It also checks that the service can have more resources allotted to it and that it is not in breach of any defined rules.
		</div><div class="para">
			If all these conditions are met (that is, access is allowed to the service; the service has not reached its resource limit; and the service is not in breach of any defined rule), <code class="systemitem">xinetd</code> then starts an instance of the requested service and passes control of the connection to it. After the connection has been established, <code class="systemitem">xinetd</code> takes no further part in the communication between the client and the server.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Option_Fields-Expansions.html"><strong>Anterior</strong>2.5.2.2.4. Expansions</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd_Configuration_Files.html"><strong>Siguiente</strong>2.5.4. xinetd Configuration Files</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd_Configuration_Files.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.5.4. xinetd Configuration Files</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-TCP_Wrappers_and_xinetd.html" title="2.5. TCP Wrappers and xinetd" /><link rel="prev" href="sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd.html" title="2.5.3. xinetd" /><link rel="next" href="sect-Security_Guide-xinetd_Configuration_Files-The_etcxinetd.d_Directory.html" title="2.5.4.2. El directorio /etc/xinetd.d/" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs
 .fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-xinetd_Configuration_Files-The_etcxinetd.d_Directory.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd_Configuration_Files">2.5.4. xinetd Configuration Files</h3></div></div></div><div class="para">
			The configuration files for <code class="systemitem">xinetd</code> are as follows:
		</div><div class="itemizedlist"><ul><li><div class="para">
					<code class="filename">/etc/xinetd.conf</code> â€” The global <code class="systemitem">xinetd</code> configuration file.
				</div></li><li><div class="para">
					<code class="filename">/etc/xinetd.d/</code> â€” The directory containing all service-specific files.
				</div></li></ul></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-xinetd_Configuration_Files-The_etcxinetd.conf_File">2.5.4.1. El Archivo /etc/xinetd.conf</h4></div></div></div><div class="para">
				The <code class="filename">/etc/xinetd.conf</code> file contains general configuration settings which affect every service under <code class="systemitem">xinetd</code>'s control. It is read when the <code class="systemitem">xinetd</code> service is first started, so for configuration changes to take effect, you need to restart the <code class="systemitem">xinetd</code> service. The following is a sample <code class="filename">/etc/xinetd.conf</code> file:
			</div><pre class="screen">defaults
{
         instances               = 60        
         log_type                = SYSLOG        authpriv
         log_on_success          = HOST PID
         log_on_failure          = HOST
         cps                     = 25 30
}
includedir /etc/xinetd.d
</pre><div class="para">
				These lines control the following aspects of <code class="systemitem">xinetd</code>:
			</div><div class="itemizedlist"><ul><li><div class="para">
						<code class="option">instances</code> â€” Specifies the maximum number of simultaneous requests that <code class="systemitem">xinetd</code> can process.
					</div></li><li><div class="para">
						<code class="option">log_type</code> â€” Configures <code class="systemitem">xinetd</code> to use the <code class="command">authpriv</code> log facility, which writes log entries to the <code class="filename">/var/log/secure</code> file. Adding a directive such as <code class="option">FILE /var/log/xinetdlog</code> would create a custom log file called <code class="filename">xinetdlog</code> in the <code class="filename">/var/log/</code> directory.
					</div></li><li><div class="para">
						<code class="option">log_on_success</code> â€” Configures <code class="systemitem">xinetd</code> to log successful connection attempts. By default, the remote host's IP address and the process ID of the server processing the request are recorded.
					</div></li><li><div class="para">
						<code class="option">log_on_failure</code> â€” Configures <code class="systemitem">xinetd</code> to log failed connection attempts or if the connection was denied.
					</div></li><li><div class="para">
						<code class="option">cps</code> â€” Configures <code class="systemitem">xinetd</code> to allow no more than 25 connections per second to any given service. If this limit is exceeded, the service is retired for 30 seconds.
					</div></li><li><div class="para">
						<code class="option">includedir</code> <code class="filename">/etc/xinetd.d/</code> â€” Includes options declared in the service-specific configuration files located in the <code class="filename">/etc/xinetd.d/</code> directory. Refer to <a class="xref" href="sect-Security_Guide-xinetd_Configuration_Files-The_etcxinetd.d_Directory.html" title="2.5.4.2. El directorio /etc/xinetd.d/">SecciÃ³nÂ 2.5.4.2, â€œEl directorio /etc/xinetd.d/â€</a> for more information.
					</div></li></ul></div><div class="note"><h2>Note</h2><div class="para">
					Often, both the <code class="option">log_on_success</code> and <code class="option">log_on_failure</code> settings in <code class="filename">/etc/xinetd.conf</code> are further modified in the service-specific configuration files. More information may therefore appear in a given service's log file than the <code class="filename">/etc/xinetd.conf</code> file may indicate. Refer to <a class="xref" href="sect-Security_Guide-xinetd_Configuration_Files-Altering_xinetd_Configuration_Files.html#sect-Security_Guide-Altering_xinetd_Configuration_Files-Logging_Options" title="2.5.4.3.1. Logging Options">SecciÃ³nÂ 2.5.4.3.1, â€œLogging Optionsâ€</a> for further information.
				</div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd.html"><strong>Anterior</strong>2.5.3. xinetd</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-xinetd_Configuration_Files-The_etcxinetd.d_Directory.html"><strong>Siguiente</strong>2.5.4.2. El directorio /etc/xinetd.d/</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-TCP_Wrappers_and_xinetd.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.5. TCP Wrappers and xinetd</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="chap-Security_Guide-Securing_Your_Network.html" title="CapÃtulo 2. Securing Your Network" /><link rel="prev" href="sect-Security_Guide-Additional_Resources-Useful_PAM_Websites.html" title="2.4.8.2. Useful PAM Websites" /><link rel="next" href="sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers_Configuration_Files.html" title="2.5.2. TCP Wrappers Configuration Files" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a c
 lass="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Additional_Resources-Useful_PAM_Websites.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers_Configuration_Files.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h2 class="title" id="sect-Security_Guide-TCP_Wrappers_and_xinetd">2.5. TCP Wrappers and xinetd</h2></div></div></div><div class="para">
		Controlling access to network services is one of the most important security tasks facing a server administrator. Fedora provides several tools for this purpose. For example, an <code class="command">iptables</code>-based firewall filters out unwelcome network packets within the kernel's network stack. For network services that utilize it, <em class="firstterm">TCP Wrappers</em> add an additional layer of protection by defining which hosts are or are not allowed to connect to "<span class="emphasis"><em>wrapped</em></span>" network services. One such wrapped network service is the <code class="systemitem">xinetd</code> <span class="emphasis"><em>super server</em></span>. This service is called a super server because it controls connections to a subset of network services and further refines access control.
	</div><div class="para">
		<a class="xref" href="sect-Security_Guide-TCP_Wrappers_and_xinetd.html#figu-Security_Guide-TCP_Wrappers_and_xinetd-Access_Control_to_Network_Services" title="Figura 2.9. Access Control to Network Services">FiguraÂ 2.9, â€œAccess Control to Network Servicesâ€</a> is a basic illustration of how these tools work together to protect network services.
	</div><div class="figure" id="figu-Security_Guide-TCP_Wrappers_and_xinetd-Access_Control_to_Network_Services"><div class="figure-contents"><div class="mediaobject"><img src="images/tcp_wrap_diagram.png" alt="Access Control to Network Services" /><div class="longdesc"><div class="para">
					Exhibit A: Access Control to Network Services Flowchart
				</div></div></div></div><h6>Figura 2.9. Access Control to Network Services</h6></div><br class="figure-break" /><div class="para">
		This chapter focuses on the role of TCP Wrappers and <code class="systemitem">xinetd</code> in controlling access to network services and reviews how these tools can be used to enhance both logging and utilization management. Refer to <a class="xref" href="sect-Security_Guide-IPTables.html" title="2.9. IPTables">SecciÃ³nÂ 2.9, â€œIPTablesâ€</a> for information about using firewalls with <code class="command">iptables</code>.
	</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers">2.5.1. TCP Wrappers</h3></div></div></div><div class="para">
			The TCP Wrappers package (<code class="filename">tcp_wrappers</code>) is installed by default and provides host-based access control to network services. The most important component within the package is the <code class="filename">/usr/lib/libwrap.a</code> library. In general terms, a TCP-wrapped service is one that has been compiled against the <code class="filename">libwrap.a</code> library.
		</div><div class="para">
			When a connection attempt is made to a TCP-wrapped service, the service first references the host's access files (<code class="filename">/etc/hosts.allow</code> and <code class="filename">/etc/hosts.deny</code>) to determine whether or not the client is allowed to connect. In most cases, it then uses the syslog daemon (<code class="systemitem">syslogd</code>) to write the name of the requesting client and the requested service to <code class="filename">/var/log/secure</code> or <code class="filename">/var/log/messages</code>.
		</div><div class="para">
			If a client is allowed to connect, TCP Wrappers release control of the connection to the requested service and take no further part in the communication between the client and the server.
		</div><div class="para">
			In addition to access control and logging, TCP Wrappers can execute commands to interact with the client before denying or releasing control of the connection to the requested network service.
		</div><div class="para">
			Because TCP Wrappers are a valuable addition to any server administrator's arsenal of security tools, most network services within Fedora are linked to the <code class="filename">libwrap.a</code> library. Some such applications include <code class="systemitem">/usr/sbin/sshd</code>, <code class="command">/usr/sbin/sendmail</code>, and <code class="systemitem">/usr/sbin/xinetd</code>.
		</div><div class="note"><h2>Note</h2><div class="para">
				To determine if a network service binary is linked to <code class="filename">libwrap.a</code>, type the following command as the root user:
			</div><pre class="screen">ldd <nombre-binario> | grep libwrap
</pre><div class="para">
				Replace <em class="replaceable"><code><binary-name></code></em> with the name of the network service binary.
			</div><div class="para">
				If the command returns straight to the prompt with no output, then the network service is <span class="emphasis"><em>not</em></span> linked to <code class="filename">libwrap.a</code>.
			</div><div class="para">
				The following example indicates that <code class="systemitem">/usr/sbin/sshd</code> is linked to <code class="filename">libwrap.a</code>:
			</div><pre class="screen">[root at myServer ~]# ldd /usr/sbin/sshd | grep libwrap
        libwrap.so.0 => /lib/libwrap.so.0 (0x00655000)
[root at myServer ~]#
</pre></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-TCP_Wrappers-Advantages_of_TCP_Wrappers">2.5.1.1. Advantages of TCP Wrappers</h4></div></div></div><div class="para">
				TCP Wrappers provide the following advantages over other network service control techniques:
			</div><div class="itemizedlist"><ul><li><div class="para">
						<span class="emphasis"><em>Transparency to both the client and the wrapped network service</em></span> â€” Both the connecting client and the wrapped network service are unaware that TCP Wrappers are in use. Legitimate users are logged and connected to the requested service while connections from banned clients fail.
					</div></li><li><div class="para">
						<span class="emphasis"><em>Centralized management of multiple protocols</em></span> â€” TCP Wrappers operate separately from the network services they protect, allowing many server applications to share a common set of access control configuration files, making for simpler management.
					</div></li></ul></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Additional_Resources-Useful_PAM_Websites.html"><strong>Anterior</strong>2.4.8.2. Useful PAM Websites</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers_Configuration_Files.html"><strong>Siguiente</strong>2.5.2. TCP Wrappers Configuration Files</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Threats_to_Server_Security-Inattentive_Administration.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.3.3.3. Inattentive Administration</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Server_Security.html" title="1.3.3. Threats to Server Security" /><link rel="prev" href="sect-Security_Guide-Threats_to_Server_Security-Unpatched_Services.html" title="1.3.3.2. Unpatched Services" /><link rel="next" href="sect-Security_Guide-Threats_to_Server_Security-Inherently_Insecure_Services.html" title="1.3.3.4. Inherently Insecure Services" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/ima
 ge_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Threats_to_Server_Security-Unpatched_Services.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Threats_to_Server_Security-Inherently_Insecure_Services.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Threats_to_Server_Security-Inattentive_Administration">1.3.3.3. Inattentive Administration</h4></div></div></div><div class="para">
				Administrators who fail to patch their systems are one of the greatest threats to server security. According to the <em class="firstterm">SysAdmin, Audit, Network, Security Institute</em> (<em class="firstterm">SANS</em>), the primary cause of computer security vulnerability is to "assign untrained people to maintain security and provide neither the training nor the time to make it possible to do the job."<sup>[<a id="id2897327" href="#ftn.id2897327" class="footnote">10</a>]</sup> This applies as much to inexperienced administrators as it does to overconfident or amotivated administrators.
			</div><div class="para">
				Some administrators fail to patch their servers and workstations, while others fail to watch log messages from the system kernel or network traffic. Another common error is when default passwords or keys to services are left unchanged. For example, some databases have default administration passwords because the database developers assume that the system administrator changes these passwords immediately after installation. If a database administrator fails to change this password, even an inexperienced cracker can use a widely-known default password to gain administrative privileges to the database. These are only a few examples of how inattentive administration can lead to compromised servers.
			</div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id2897327" href="#id2897327" class="para">10</a>] </sup>
					http://www.sans.org/resources/errors.php
				</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Threats_to_Server_Security-Unpatched_Services.html"><strong>Anterior</strong>1.3.3.2. Unpatched Services</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Threats_to_Server_Security-Inherently_Insecure_Services.html"><strong>Siguiente</strong>1.3.3.4. Inherently Insecure Services</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Threats_to_Server_Security-Inherently_Insecure_Services.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.3.3.4. Inherently Insecure Services</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Server_Security.html" title="1.3.3. Threats to Server Security" /><link rel="prev" href="sect-Security_Guide-Threats_to_Server_Security-Inattentive_Administration.html" title="1.3.3.3. Inattentive Administration" /><link rel="next" href="sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Workstation_and_Home_PC_Security.html" title="1.3.4. Threats to Workstation and Home PC Security" /></head><body class=""><p id="title"><a class="left" href="http://www.fedor
 aproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Threats_to_Server_Security-Inattentive_Administration.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Workstation_and_Home_PC_Security.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Threats_to_Server_Security-Inherently_Insecure_Services">1.3.3.4. Inherently Insecure Services</h4></div></div></div><div class="para">
				Even the most vigilant organization can fall victim to vulnerabilities if the network services they choose are inherently insecure. For instance, there are many services developed under the assumption that they are used over trusted networks; however, this assumption fails as soon as the service becomes available over the Internet â€” which is itself inherently untrusted.
			</div><div class="para">
				One category of insecure network services are those that require unencrypted usernames and passwords for authentication. Telnet and FTP are two such services. If packet sniffing software is monitoring traffic between the remote user and such a service usernames and passwords can be easily intercepted.
			</div><div class="para">
				Inherently, such services can also more easily fall prey to what the security industry terms the <em class="firstterm">man-in-the-middle</em> attack. In this type of attack, a cracker redirects network traffic by tricking a cracked name server on the network to point to his machine instead of the intended server. Once someone opens a remote session to the server, the attacker's machine acts as an invisible conduit, sitting quietly between the remote service and the unsuspecting user capturing information. In this way a cracker can gather administrative passwords and raw data without the server or the user realizing it.
			</div><div class="para">
				Another category of insecure services include network file systems and information services such as NFS or NIS, which are developed explicitly for LAN usage but are, unfortunately, extended to include WANs (for remote users). NFS does not, by default, have any authentication or security mechanisms configured to prevent a cracker from mounting the NFS share and accessing anything contained therein. NIS, as well, has vital information that must be known by every computer on a network, including passwords and file permissions, within a plain text ASCII or DBM (ASCII-derived) database. A cracker who gains access to this database can then access every user account on a network, including the administrator's account.
			</div><div class="para">
				By default, Fedora is released with all such services turned off. However, since administrators often find themselves forced to use these services, careful configuration is critical. Refer to <a class="xref" href="sect-Security_Guide-Server_Security.html" title="2.2. Server Security">SecciÃ³nÂ 2.2, â€œServer Securityâ€</a> for more information about setting up services in a safe manner.
			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Threats_to_Server_Security-Inattentive_Administration.html"><strong>Anterior</strong>1.3.3.3. Inattentive Administration</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Workstation_and_Home_PC_Security.html"><strong>Siguiente</strong>1.3.4. Threats to Workstation and Home PC Security</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Threats_to_Server_Security-Unpatched_Services.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.3.3.2. Unpatched Services</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Server_Security.html" title="1.3.3. Threats to Server Security" /><link rel="prev" href="sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Server_Security.html" title="1.3.3. Threats to Server Security" /><link rel="next" href="sect-Security_Guide-Threats_to_Server_Security-Inattentive_Administration.html" title="1.3.3.3. Inattentive Administration" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/image
 s/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Server_Security.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Threats_to_Server_Security-Inattentive_Administration.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Threats_to_Server_Security-Unpatched_Services">1.3.3.2. Unpatched Services</h4></div></div></div><div class="para">
				Most server applications that are included in a default installation are solid, thoroughly tested pieces of software. Having been in use in production environments for many years, their code has been thoroughly refined and many of the bugs have been found and fixed.
			</div><div class="para">
				However, there is no such thing as perfect software and there is always room for further refinement. Moreover, newer software is often not as rigorously tested as one might expect, because of its recent arrival to production environments or because it may not be as popular as other server software.
			</div><div class="para">
				Developers and system administrators often find exploitable bugs in server applications and publish the information on bug tracking and security-related websites such as the Bugtraq mailing list (<a href="http://www.securityfocus.com">http://www.securityfocus.com</a>) or the Computer Emergency Response Team (CERT) website (<a href="http://www.cert.org">http://www.cert.org</a>). Although these mechanisms are an effective way of alerting the community to security vulnerabilities, it is up to system administrators to patch their systems promptly. This is particularly true because crackers have access to these same vulnerability tracking services and will use the information to crack unpatched systems whenever they can. Good system administration requires vigilance, constant bug tracking, and proper system maintenance to ensure a more secure computing environment.
			</div><div class="para">
				Refer to <a class="xref" href="sect-Security_Guide-Security_Updates.html" title="1.5. Actualizaciones de Seguridad">SecciÃ³nÂ 1.5, â€œActualizaciones de Seguridadâ€</a> for more information about keeping a system up-to-date.
			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Server_Security.html"><strong>Anterior</strong>1.3.3. Threats to Server Security</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Threats_to_Server_Security-Inattentive_Administration.html"><strong>Siguiente</strong>1.3.3.3. Inattentive Administration</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Threats_to_Workstation_and_Home_PC_Security-Vulnerable_Client_Applications.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.3.4.2. Vulnerable Client Applications</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Workstation_and_Home_PC_Security.html" title="1.3.4. Threats to Workstation and Home PC Security" /><link rel="prev" href="sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Workstation_and_Home_PC_Security.html" title="1.3.4. Threats to Workstation and Home PC Security" /><link rel="next" href="sect-Security_Guide-Common_Exploits_and_Attacks.html" title="1.4. Ataques y Aprovechadas ComÃºnes" /></head><body class=""><p id="title"><a class="left" href="http:
 //www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Workstation_and_Home_PC_Security.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Common_Exploits_and_Attacks.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Threats_to_Workstation_and_Home_PC_Security-Vulnerable_Client_Applications">1.3.4.2. Vulnerable Client Applications</h4></div></div></div><div class="para">
				Although an administrator may have a fully secure and patched server, that does not mean remote users are secure when accessing it. For instance, if the server offers Telnet or FTP services over a public network, an attacker can capture the plain text usernames and passwords as they pass over the network, and then use the account information to access the remote user's workstation.
			</div><div class="para">
				Even when using secure protocols, such as SSH, a remote user may be vulnerable to certain attacks if they do not keep their client applications updated. For instance, v.1 SSH clients are vulnerable to an X-forwarding attack from malicious SSH servers. Once connected to the server, the attacker can quietly capture any keystrokes and mouse clicks made by the client over the network. This problem was fixed in the v.2 SSH protocol, but it is up to the user to keep track of what applications have such vulnerabilities and update them as necessary.
			</div><div class="para">
				<a class="xref" href="chap-Security_Guide-Securing_Your_Network.html#sect-Security_Guide-Workstation_Security" title="2.1. Workstation Security">SecciÃ³nÂ 2.1, â€œWorkstation Securityâ€</a> discusses in more detail what steps administrators and home users should take to limit the vulnerability of computer workstations.
			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Workstation_and_Home_PC_Security.html"><strong>Anterior</strong>1.3.4. Threats to Workstation and Home PC Security</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Common_Exploits_and_Attacks.html"><strong>Siguiente</strong>1.4. Ataques y Aprovechadas ComÃºnes</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Updating_Packages-Applying_the_Changes.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.5.4. Applying the Changes</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Security_Updates.html" title="1.5. Actualizaciones de Seguridad" /><link rel="prev" href="sect-Security_Guide-Updating_Packages-Installing_Signed_Packages.html" title="1.5.3. Installing Signed Packages" /><link rel="next" href="chap-Security_Guide-Securing_Your_Network.html" title="CapÃtulo 2. Securing Your Network" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedorap
 roject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Updating_Packages-Installing_Signed_Packages.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="chap-Security_Guide-Securing_Your_Network.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Updating_Packages-Applying_the_Changes">1.5.4. Applying the Changes</h3></div></div></div><div class="para">
			After downloading and installing security errata and updates, it is important to halt usage of the older software and begin using the new software. How this is done depends on the type of software that has been updated. The following list itemizes the general categories of software and provides instructions for using the updated versions after a package upgrade.
		</div><div class="note"><h2>Note</h2><div class="para">
				In general, rebooting the system is the surest way to ensure that the latest version of a software package is used; however, this option is not always required, or available to the system administrator.
			</div></div><div class="variablelist"><dl><dt><span class="term">Aplicaciones</span></dt><dd><div class="para">
						User-space applications are any programs that can be initiated by a system user. Typically, such applications are used only when a user, script, or automated task utility launches them and they do not persist for long periods of time.
					</div><div class="para">
						Once such a user-space application is updated, halt any instances of the application on the system and launch the program again to use the updated version.
					</div></dd><dt><span class="term">Kernel</span></dt><dd><div class="para">
						The kernel is the core software component for the Fedora operating system. It manages access to memory, the processor, and peripherals as well as schedules all tasks.
					</div><div class="para">
						Because of its central role, the kernel cannot be restarted without also stopping the computer. Therefore, an updated version of the kernel cannot be used until the system is rebooted.
					</div></dd><dt><span class="term">Shared Libraries</span></dt><dd><div class="para">
						Shared libraries are units of code, such as <code class="filename">glibc</code>, which are used by a number of applications and services. Applications utilizing a shared library typically load the shared code when the application is initialized, so any applications using the updated library must be halted and relaunched.
					</div><div class="para">
						To determine which running applications link against a particular library, use the <code class="command">lsof</code> command as in the following example:
					</div><pre class="screen"><code class="command">lsof /lib/libwrap.so*</code>
</pre><div class="para">
						This command returns a list of all the running programs which use TCP wrappers for host access control. Therefore, any program listed must be halted and relaunched if the <code class="filename">tcp_wrappers</code> package is updated.
					</div></dd><dt><span class="term">Servicios SysV</span></dt><dd><div class="para">
						SysV services are persistent server programs launched during the boot process. Examples of SysV services include <code class="command">sshd</code>, <code class="command">vsftpd</code>, and <code class="command">xinetd</code>.
					</div><div class="para">
						Because these programs usually persist in memory as long as the machine is booted, each updated SysV service must be halted and relaunched after the package is upgraded. This can be done using the <span class="application"><strong>Services Configuration Tool</strong></span> or by logging into a root shell prompt and issuing the <code class="command">/sbin/service</code> command as in the following example:
					</div><pre class="screen"><code class="command">/sbin/service <em class="replaceable"><code><nombre-servicio></code></em> restart</code>
</pre><div class="para">
						In the previous example, replace <em class="replaceable"><code><service-name></code></em> with the name of the service, such as <code class="command">sshd</code>.
					</div></dd><dt><span class="term">Servicios <code class="command">xinetd</code></span></dt><dd><div class="para">
						Services controlled by the <code class="command">xinetd</code> super service only run when a there is an active connection. Examples of services controlled by <code class="command">xinetd</code> include Telnet, IMAP, and POP3.
					</div><div class="para">
						Because new instances of these services are launched by <code class="command">xinetd</code> each time a new request is received, connections that occur after an upgrade are handled by the updated software. However, if there are active connections at the time the <code class="command">xinetd</code> controlled service is upgraded, they are serviced by the older version of the software.
					</div><div class="para">
						To kill off older instances of a particular <code class="command">xinetd</code> controlled service, upgrade the package for the service then halt all processes currently running. To determine if the process is running, use the <code class="command">ps</code> command and then use the <code class="command">kill</code> or <code class="command">killall</code> command to halt current instances of the service.
					</div><div class="para">
						For example, if security errata <code class="filename">imap</code> packages are released, upgrade the packages, then type the following command as root into a shell prompt:
					</div><pre class="screen"><code class="command">ps -aux | grep imap</code>
</pre><div class="para">
						This command returns all active IMAP sessions. Individual sessions can then be terminated by issuing the following command:
					</div><pre class="screen"><code class="command">kill <em class="replaceable"><code><PID></code></em></code>
</pre><div class="para">
						If this fails to terminate the session, use the following command instead:
					</div><pre class="screen"><code class="command">kill -9 <em class="replaceable"><code><PID></code></em></code>
</pre><div class="para">
						In the previous examples, replace <em class="replaceable"><code><PID></code></em> with the process identification number (found in the second column of the <code class="command">ps</code> command) for an IMAP session.
					</div><div class="para">
						To kill all active IMAP sessions, issue the following command:
					</div><pre class="screen"><code class="command">killall imapd</code>
</pre></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Updating_Packages-Installing_Signed_Packages.html"><strong>Anterior</strong>1.5.3. Installing Signed Packages</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="chap-Security_Guide-Securing_Your_Network.html"><strong>Siguiente</strong>CapÃtulo 2. Securing Your Network</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Updating_Packages-Installing_Signed_Packages.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.5.3. Installing Signed Packages</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Security_Updates.html" title="1.5. Actualizaciones de Seguridad" /><link rel="prev" href="sect-Security_Guide-Updating_Packages-Verifying_Signed_Packages.html" title="1.5.2. Verifying Signed Packages" /><link rel="next" href="sect-Security_Guide-Updating_Packages-Applying_the_Changes.html" title="1.5.4. Applying the Changes" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http:
 //docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Updating_Packages-Verifying_Signed_Packages.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Updating_Packages-Applying_the_Changes.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Updating_Packages-Installing_Signed_Packages">1.5.3. Installing Signed Packages</h3></div></div></div><div class="para">
			Installation for most packages can be done safely (except kernel packages) by issuing the following command:
		</div><pre class="screen"><code class="command">rpm -Uvh /tmp/updates/*.rpm</code>
</pre><div class="para">
			For kernel packages use the following command:
		</div><pre class="screen"><code class="command">rpm -ivh /tmp/updates/<em class="replaceable"><code><kernel-package></code></em></code>
</pre><div class="para">
			Replace <em class="replaceable"><code><kernel-package></code></em> in the previous example with the name of the kernel RPM.
		</div><div class="para">
			Once the machine has been safely rebooted using the new kernel, the old kernel may be removed using the following command:
		</div><pre class="screen"><code class="command">rpm -e <em class="replaceable"><code><old-kernel-package></code></em></code>
</pre><div class="para">
			Replace <em class="replaceable"><code><old-kernel-package></code></em> in the previous example with the name of the older kernel RPM.
		</div><div class="note"><h2>Note</h2><div class="para">
				It is not a requirement that the old kernel be removed. The default boot loader, GRUB, allows for multiple kernels to be installed, then chosen from a menu at boot time.
			</div></div><div class="important"><h2>Important</h2><div class="para">
				Before installing any security errata, be sure to read any special instructions contained in the errata report and execute them accordingly. Refer to <a class="xref" href="sect-Security_Guide-Updating_Packages-Applying_the_Changes.html" title="1.5.4. Applying the Changes">SecciÃ³nÂ 1.5.4, â€œApplying the Changesâ€</a> for general instructions about applying the changes made by an errata update.
			</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Updating_Packages-Verifying_Signed_Packages.html"><strong>Anterior</strong>1.5.2. Verifying Signed Packages</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Updating_Packages-Applying_the_Changes.html"><strong>Siguiente</strong>1.5.4. Applying the Changes</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Updating_Packages-Verifying_Signed_Packages.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.5.2. Verifying Signed Packages</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Security_Updates.html" title="1.5. Actualizaciones de Seguridad" /><link rel="prev" href="sect-Security_Guide-Security_Updates.html" title="1.5. Actualizaciones de Seguridad" /><link rel="next" href="sect-Security_Guide-Updating_Packages-Installing_Signed_Packages.html" title="1.5.3. Installing Signed Packages" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedorapr
 oject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Security_Updates.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Updating_Packages-Installing_Signed_Packages.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Updating_Packages-Verifying_Signed_Packages">1.5.2. Verifying Signed Packages</h3></div></div></div><div class="para">
			All Fedora packages are signed with the Fedora <em class="firstterm">GPG</em> key. GPG stands for GNU Privacy Guard, or GnuPG, a free software package used for ensuring the authenticity of distributed files. For example, a private key (secret key) locks the package while the public key unlocks and verifies the package. If the public key distributed by Fedora does not match the private key during RPM verification, the package may have been altered and therefore cannot be trusted.
		</div><div class="para">
			The RPM utility within Fedora automatically tries to verify the GPG signature of an RPM package before installing it. If the Fedora GPG key is not installed, install it from a secure, static location, such as an Fedora installation CD-ROM or DVD.
		</div><div class="para">
			Assuming the disc is mounted in <code class="filename">/mnt/cdrom</code>, use the following command to import it into the <em class="firstterm">keyring</em> (a database of trusted keys on the system):
		</div><pre class="screen"><code class="command">rpm --import /mnt/cdrom/RPM-GPG-KEY</code>
</pre><div class="para">
			To display a list of all keys installed for RPM verification, execute the following command:
		</div><pre class="screen"><code class="command">rpm -qa gpg-pubkey*</code>
</pre><div class="para">
			The output will look similar to the following:
		</div><pre class="screen"><code class="computeroutput">gpg-pubkey-db42a60e-37ea5438</code>
</pre><div class="para">
			To display details about a specific key, use the <code class="command">rpm -qi</code> command followed by the output from the previous command, as in this example:
		</div><pre class="screen"><code class="command">rpm -qi gpg-pubkey-db42a60e-37ea5438</code>
</pre><div class="para">
			It is extremely important to verify the signature of the RPM files before installing them to ensure that they have not been altered from the original source of the packages. To verify all the downloaded packages at once, issue the following command:
		</div><pre class="screen"><code class="command">rpm -K /tmp/updates/*.rpm</code>
</pre><div class="para">
			For each package, if the GPG key verifies successfully, the command returns <code class="computeroutput">gpg OK</code>. If it doesn't, make sure you are using the correct Fedora public key, as well as verifying the source of the content. Packages that do not pass GPG verifications should not be installed, as they may have been altered by a third party.
		</div><div class="para">
			After verifying the GPG key and downloading all the packages associated with the errata report, install the packages as root at a shell prompt.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Security_Updates.html"><strong>Anterior</strong>1.5. Actualizaciones de Seguridad</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Updating_Packages-Installing_Signed_Packages.html"><strong>Siguiente</strong>1.5.3. Installing Signed Packages</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Using_IPTables-Basic_Firewall_Policies.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.3.2. PolÃticas BÃ¡sicas del Cortafuego</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Firewalls-Using_IPTables.html" title="2.8.3. Uso de IPTables" /><link rel="prev" href="sect-Security_Guide-Firewalls-Using_IPTables.html" title="2.8.3. Uso de IPTables" /><link rel="next" href="sect-Security_Guide-Using_IPTables-Saving_and_Restoring_IPTables_Rules.html" title="2.8.3.3. Guardando y Restaurando las Reglas de IPTables" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="
 right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Firewalls-Using_IPTables.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Using_IPTables-Saving_and_Restoring_IPTables_Rules.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Using_IPTables-Basic_Firewall_Policies">2.8.3.2. PolÃticas BÃ¡sicas del Cortafuego</h4></div></div></div><div class="para">
				El establecimiento de polÃticas bÃ¡sicas de cortafuego crea la base para construir reglas definidas por el usuario mÃ¡s detalladas.
			</div><div class="para">
				Cada cadena de <code class="command">iptables</code> se compone de una polÃtica predeterminada, y cero o mÃ¡s reglas que funcionan en conjunto con la polÃtica predeterminada para definir el conjunto de reglas del cortafuego.
			</div><div class="para">
				La polÃtica establecida por defecto para una cadena puede ser ACEPTAR o ABANDONAR. Los administradores de sistemas orientados por la seguridad implementan una polÃtica por defecto de ABANDONAR, y solo permiten unos pocos paquetes especÃficos, luego de ser analizados uno por uno. Por ejemplo, las siguientes polÃticas bloquean todos los paquetes que lleguen a o que partan desde una puerta de enlace:
			</div><pre class="screen">[root at miServidor ~ ] # iptables -P INPUT DROP
[root at miServidor ~ ] # iptables -P OUTPUT DROP
</pre><div class="para">
				Es tambiÃ©n algo recomendado que a cualquier <em class="firstterm">paquete reenviado</em> â€” trÃ¡fico de red que es enrutado desde el cortafuegos hacia su nodo de destino â€” tambiÃ©n le sea negada la entrada, para poder asÃ restringir las posibles exposiciones inadvertidas de clientes internos a Internet. Para hacerlo, utilice la siguiente regla:
			</div><pre class="screen">[root at miServidor ~ ] # iptables -P FORWARD DROP
</pre><div class="para">
				Cuando haya establecido las polÃticas por defecto para cada cadena, puede crear y guardar las reglas siguientes para su red y requerimientos de seguridad particulares.
			</div><div class="para">
				Las siguientes secciones describen cÃ³mo guardar las reglas iptables y delinea algunas de las reglas que puede implementar cuando construya su cortafuego con iptables.
			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Firewalls-Using_IPTables.html"><strong>Anterior</strong>2.8.3. Uso de IPTables</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Using_IPTables-Saving_and_Restoring_IPTables_Rules.html"><strong>Siguiente</strong>2.8.3.3. Guardando y Restaurando las Reglas de IP...</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Using_IPTables-Saving_and_Restoring_IPTables_Rules.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.3.3. Guardando y Restaurando las Reglas de IPTables</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Firewalls-Using_IPTables.html" title="2.8.3. Uso de IPTables" /><link rel="prev" href="sect-Security_Guide-Using_IPTables-Basic_Firewall_Policies.html" title="2.8.3.2. PolÃticas BÃ¡sicas del Cortafuego" /><link rel="next" href="sect-Security_Guide-Firewalls-Common_IPTables_Filtering.html" title="2.8.4. Filtrado ComÃºn de IPTalbes" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a
 ><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Using_IPTables-Basic_Firewall_Policies.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Firewalls-Common_IPTables_Filtering.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Using_IPTables-Saving_and_Restoring_IPTables_Rules">2.8.3.3. Guardando y Restaurando las Reglas de IPTables</h4></div></div></div><div class="para">
				Los cambios en <code class="command">iptables</code> son transitorios; si el sistema es reiniciado o si el servicio de <code class="command">iptables</code> es reiniciado, las reglas son automÃ¡ticamente eliminadas y reseteadas. Para guardar las reglas de modo que sean cargadas cuando el servicio <code class="command">iptables</code> sea iniciado, utilice el siguiente comando:
			</div><pre class="screen">[root at miServidor ~ ] # service iptables save
</pre><div class="para">
				Las reglas se guardan en el archivo <code class="filename">/etc/sysconfig/iptables</code> y se aplican cada vez que el servicio o la computadora se reinician.
			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Using_IPTables-Basic_Firewall_Policies.html"><strong>Anterior</strong>2.8.3.2. PolÃticas BÃ¡sicas del Cortafuego</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Firewalls-Common_IPTables_Filtering.html"><strong>Siguiente</strong>2.8.4. Filtrado ComÃºn de IPTalbes</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Virtual_Private_Networks_VPNs-Creating_an_IPsec_Connection.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.7.4. Creating an IPsec Connection</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Virtual_Private_Networks_VPNs.html" title="2.7. Virtual Private Networks (VPNs)" /><link rel="prev" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec.html" title="2.7.3. IPsec" /><link rel="next" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Installation.html" title="2.7.5. IPsec Installation" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://
 docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Installation.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Virtual_Private_Networks_VPNs-Creating_an_IPsec_Connection">2.7.4. Creating an <abbr class="abbrev">IPsec</abbr> Connection</h3></div></div></div><div class="para">
			An <abbr class="abbrev">IPsec</abbr> connection is split into two logical phases. In phase 1, an <abbr class="abbrev">IPsec</abbr> node initializes the connection with the remote node or network. The remote node or network checks the requesting node's credentials and both parties negotiate the authentication method for the connection.
		</div><div class="para">
			On Fedora systems, an <abbr class="abbrev">IPsec</abbr> connection uses the <em class="firstterm">pre-shared key</em> method of <abbr class="abbrev">IPsec</abbr> node authentication. In a pre-shared key <abbr class="abbrev">IPsec</abbr> connection, both hosts must use the same key in order to move to Phase 2 of the <abbr class="abbrev">IPsec</abbr> connection.
		</div><div class="para">
			Phase 2 of the <abbr class="abbrev">IPsec</abbr> connection is where the <em class="firstterm">Security Association</em> (<acronym class="acronym">SA</acronym>) is created between <abbr class="abbrev">IPsec</abbr> nodes. This phase establishes an <abbr class="abbrev">SA</abbr> database with configuration information, such as the encryption method, secret session key exchange parameters, and more. This phase manages the actual <abbr class="abbrev">IPsec</abbr> connection between remote nodes and networks.
		</div><div class="para">
			The Fedora implementation of <abbr class="abbrev">IPsec</abbr> uses IKE for sharing keys between hosts across the Internet. The <code class="command">racoon</code> keying daemon handles the IKE key distribution and exchange. Refer to the <code class="command">racoon</code> man page for more information about this daemon.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec.html"><strong>Anterior</strong>2.7.3. IPsec</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Installation.html"><strong>Siguiente</strong>2.7.5. IPsec Installation</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.7.3. IPsec</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Virtual_Private_Networks_VPNs.html" title="2.7. Virtual Private Networks (VPNs)" /><link rel="prev" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-VPNs_and_PROD.html" title="2.7.2. VPNs and Fedora" /><link rel="next" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-Creating_an_IPsec_Connection.html" title="2.7.4. Creating an IPsec Connection" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right
 " href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-VPNs_and_PROD.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-Creating_an_IPsec_Connection.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec">2.7.3. IPsec</h3></div></div></div><div class="para">
			Fedora supports <abbr class="abbrev">IPsec</abbr> for connecting remote hosts and networks to each other using a secure tunnel on a common carrier network such as the Internet. <abbr class="abbrev">IPsec</abbr> can be implemented using a host-to-host (one computer workstation to another) or network-to-network (one <acronym class="acronym">LAN</acronym>/<acronym class="acronym">WAN</acronym> to another) configuration.
		</div><div class="para">
			The <abbr class="abbrev">IPsec</abbr> implementation in Fedora uses <em class="firstterm">Internet Key Exchange</em> (<em class="firstterm">IKE</em>), a protocol implemented by the Internet Engineering Task Force (<acronym class="acronym">IETF</acronym>), used for mutual authentication and secure associations between connecting systems.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-VPNs_and_PROD.html"><strong>Anterior</strong>2.7.2. VPNs and Fedora</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-Creating_an_IPsec_Connection.html"><strong>Siguiente</strong>2.7.4. Creating an IPsec Connection</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Host_to_Host_Configuration.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.7.6. IPsec Host-to-Host Configuration</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Virtual_Private_Networks_VPNs.html" title="2.7. Virtual Private Networks (VPNs)" /><link rel="prev" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Installation.html" title="2.7.5. IPsec Installation" /><link rel="next" href="sect-Security_Guide-IPsec_Host_to_Host_Configuration-Manual_IPsec_Host_to_Host_Configuration.html" title="2.7.6.2. Manual IPsec Host-to-Host Configuration" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/i
 mages/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Installation.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-IPsec_Host_to_Host_Configuration-Manual_IPsec_Host_to_Host_Configuration.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Host_to_Host_Configuration">2.7.6. IPsec Host-to-Host Configuration</h3></div></div></div><div class="para">
			IPsec can be configured to connect one desktop or workstation (host) to another using a host-to-host connection. This type of connection uses the network to which each host is connected to create a secure tunnel between each host. The requirements of a host-to-host connection are minimal, as is the configuration of <abbr class="abbrev">IPsec</abbr> on each host. The hosts need only a dedicated connection to a carrier network (such as the Internet) and Fedora to create the <abbr class="abbrev">IPsec</abbr> connection.
		</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-IPsec_Host_to_Host_Configuration-Host_to_Host_Connection">2.7.6.1. Host-to-Host Connection</h4></div></div></div><div class="para">
				A host-to-host <abbr class="abbrev">IPsec</abbr> connection is an encrypted connection between two systems, both running <abbr class="abbrev">IPsec</abbr> with the same authentication key. With the <abbr class="abbrev">IPsec</abbr> connection active, any network traffic between the two hosts is encrypted.
			</div><div class="para">
				To configure a host-to-host <abbr class="abbrev">IPsec</abbr> connection, use the following steps for each host:
			</div><div class="note"><h2>Note</h2><div class="para">
					You should perform the following procedures on the actual machine that you are configuring. Avoid attempting to configure and establish <abbr class="abbrev">IPsec</abbr> connections remotely.
				</div></div><div class="orderedlist"><ol><li><div class="para">
						In a command shell, type <code class="command">system-config-network</code> to start the <span class="application"><strong>Network Administration Tool</strong></span>.
					</div></li><li><div class="para">
						On the <span class="guilabel"><strong>IPsec</strong></span> tab, click <span class="guibutton"><strong>New</strong></span> to start the <abbr class="abbrev">IPsec</abbr> configuration wizard.
					</div></li><li><div class="para">
						Click <span class="guibutton"><strong>Forward</strong></span> to start configuring a host-to-host <abbr class="abbrev">IPsec</abbr> connection.
					</div></li><li><div class="para">
						Enter a unique name for the connection, for example, <strong class="userinput"><code>ipsec0</code></strong>. If required, select the check box to automatically activate the connection when the computer starts. Click <span class="guibutton"><strong>Forward</strong></span> to continue.
					</div></li><li><div class="para">
						Select <span class="guilabel"><strong>Host to Host encryption</strong></span> as the connection type, and then click <span class="guibutton"><strong>Forward</strong></span>.
					</div></li><li><div class="para">
						Select the type of encryption to use: manual or automatic.
					</div><div class="para">
						If you select manual encryption, an encryption key must be provided later in the process. If you select automatic encryption, the <code class="command">racoon</code> daemon manages the encryption key. The <code class="filename">ipsec-tools</code> package must be installed if you want to use automatic encryption.
					</div><div class="para">
						Click <span class="guibutton"><strong>Forward</strong></span> to continue.
					</div></li><li><div class="para">
						Enter the IP address of the remote host.
					</div><div class="para">
						To determine the IP address of the remote host, use the following command <span class="emphasis"><em>on the remote host</em></span>:
					</div><pre class="screen">[root at myServer ~] # /sbin/ifconfig <em class="replaceable"><code><device></code></em>
</pre><div class="para">
						where <em class="replaceable"><code><device></code></em> is the Ethernet device that you want to use for the <abbr class="abbrev">VPN</abbr> connection.
					</div><div class="para">
						If only one Ethernet card exists in the system, the device name is typically eth0. The following example shows the relevant information from this command (note that this is an example output only):
					</div><pre class="screen">eth0      Link encap:Ethernet  HWaddr 00:0C:6E:E8:98:1D
          inet addr:172.16.44.192  Bcast:172.16.45.255  Mask:255.255.254.0
</pre><div class="para">
						The IP address is the number following the <code class="computeroutput">inet addr:</code> label.
					</div><div class="note"><h2>Note</h2><div class="para">
							For host-to-host connections, both hosts should have a public, routable address. Alternatively, both hosts can have a private, non-routable address (for example, from the 10.x.x.x or 192.168.x.x ranges) as long as they are on the sam LAN.
						</div><div class="para">
							If the hosts are on different LANs, or one has a public address while the other has a private address, refer to <a class="xref" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Network_to_Network_Configuration.html" title="2.7.7. IPsec Network-to-Network Configuration">SecciÃ³nÂ 2.7.7, â€œIPsec Network-to-Network Configurationâ€</a>.
						</div></div><div class="para">
						Click <span class="guibutton"><strong>Forward</strong></span> to continue.
					</div></li><li><div class="para">
						If manual encryption was selected in step <a class="xref" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Host_to_Host_Configuration.html#list-Security_Guide-list-Security_Guide-list-Security_Guide-st-host-encrypt-type">6</a>, specify the encryption key to use, or click <span class="guibutton"><strong>Generate</strong></span> to create one.
					</div><div class="orderedlist"><ol><li><div class="para">
								Specify an authentication key or click <span class="guibutton"><strong>Generate</strong></span> to generate one. It can be any combination of numbers and letters.
							</div></li><li><div class="para">
								Click <span class="guibutton"><strong>Forward</strong></span> to continue.
							</div></li></ol></div></li><li><div class="para">
						Verify the information on the <span class="guilabel"><strong>IPsec â€” Summary</strong></span> page, and then click <span class="guibutton"><strong>Apply</strong></span>.
					</div></li><li><div class="para">
						Click <span class="guimenu"><strong>File</strong></span> => <span class="guimenuitem"><strong>Save</strong></span> to save the configuration.
					</div><div class="para">
						You may need to restart the network for the changes to take effect. To restart the network, use the following command:
					</div><pre class="screen">[root at myServer ~]# service network restart
</pre></li><li><div class="para">
						Select the <abbr class="abbrev">IPsec</abbr> connection from the list and click the <span class="guibutton"><strong>Activate</strong></span> button.
					</div></li><li><div class="para">
						Repeat the entire procedure for the other host. It is essential that the same keys from step <a class="xref" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Host_to_Host_Configuration.html#list-Security_Guide-list-Security_Guide-list-Security_Guide-st-host-to-host-keys">8</a> be used on the other hosts. Otherwise, <abbr class="abbrev">IPsec</abbr> will not work.
					</div></li></ol></div><div class="para">
				After configuring the <abbr class="abbrev">IPsec</abbr> connection, it appears in the <abbr class="abbrev">IPsec</abbr> list as shown in <a class="xref" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Host_to_Host_Configuration.html#figu-Security_Guide-Host_to_Host_Connection-IPsec_Connection" title="Figura 2.10. ConexiÃ³n IPsec">FiguraÂ 2.10, â€œConexiÃ³n IPsecâ€</a>.
			</div><div class="figure" id="figu-Security_Guide-Host_to_Host_Connection-IPsec_Connection"><div class="figure-contents"><div class="mediaobject"><img src="images/fed-ipsec_host2host.png" alt="ConexiÃ³n IPsec" /><div class="longdesc"><div class="para">
							ConexiÃ³n IPsec
						</div></div></div></div><h6>Figura 2.10. ConexiÃ³n IPsec</h6></div><br class="figure-break" /><div class="para">
				The following files are created when the <abbr class="abbrev">IPsec</abbr> connection is configured:
			</div><div class="itemizedlist"><ul><li><div class="para">
						<code class="filename">/etc/sysconfig/network-scripts/ifcfg-<em class="replaceable"><code><nickname></code></em></code>
					</div></li><li><div class="para">
						<code class="filename">/etc/sysconfig/network-scripts/keys-<em class="replaceable"><code><nickname></code></em></code>
					</div></li><li><div class="para">
						<code class="filename">/etc/racoon/<em class="replaceable"><code><ip-remota></code></em>.conf</code>
					</div></li><li><div class="para">
						<code class="filename">/etc/racoon/psk.txt</code>
					</div></li></ul></div><div class="para">
				If automatic encryption is selected, <code class="filename">/etc/racoon/racoon.conf</code> is also created.
			</div><div class="para">
				When the interface is up, <code class="filename">/etc/racoon/racoon.conf</code> is modified to include <code class="filename"><em class="replaceable"><code><remote-ip></code></em>.conf</code>.
			</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Installation.html"><strong>Anterior</strong>2.7.5. IPsec Installation</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-IPsec_Host_to_Host_Configuration-Manual_IPsec_Host_to_Host_Configuration.html"><strong>Siguiente</strong>2.7.6.2. Manual IPsec Host-to-Host Configuration</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Installation.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.7.5. IPsec Installation</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Virtual_Private_Networks_VPNs.html" title="2.7. Virtual Private Networks (VPNs)" /><link rel="prev" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-Creating_an_IPsec_Connection.html" title="2.7.4. Creating an IPsec Connection" /><link rel="next" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Host_to_Host_Configuration.html" title="2.7.6. IPsec Host-to-Host Configuration" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_l
 eft.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-Creating_an_IPsec_Connection.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Host_to_Host_Configuration.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Installation">2.7.5. IPsec Installation</h3></div></div></div><div class="para">
			Implementing <abbr class="abbrev">IPsec</abbr> requires that the <code class="filename">ipsec-tools</code> RPM package be installed on all <abbr class="abbrev">IPsec</abbr> hosts (if using a host-to-host configuration) or routers (if using a network-to-network configuration). The RPM package contains essential libraries, daemons, and configuration files for setting up the <abbr class="abbrev">IPsec</abbr> connection, including:
		</div><div class="itemizedlist"><ul><li><div class="para">
					<code class="command">/sbin/setkey</code> â€” manipulates the key management and security attributes of <abbr class="abbrev">IPsec</abbr> in the kernel. This executable is controlled by the <code class="command">racoon</code> key management daemon. Refer to the <code class="command">setkey</code>(8) man page for more information.
				</div></li><li><div class="para">
					<code class="command">/usr/sbin/racoon</code> â€” the IKE key management daemon, used to manage and control security associations and key sharing between IPsec-connected systems.
				</div></li><li><div class="para">
					<code class="filename">/etc/racoon/racoon.conf</code> â€” the <code class="command">racoon</code> daemon configuration file used to configure various aspects of the <abbr class="abbrev">IPsec</abbr> connection, including authentication methods and encryption algorithms used in the connection. Refer to the <code class="filename">racoon.conf</code>(5) man page for a complete listing of available directives.
				</div></li></ul></div><div class="para">
			To configure <abbr class="abbrev">IPsec</abbr> on Fedora, you can use the <span class="application"><strong>Network Administration Tool</strong></span>, or manually edit the networking and <abbr class="abbrev">IPsec</abbr> configuration files.
		</div><div class="itemizedlist"><ul><li><div class="para">
					To connect two network-connected hosts via IPsec, refer to <a class="xref" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Host_to_Host_Configuration.html" title="2.7.6. IPsec Host-to-Host Configuration">SecciÃ³nÂ 2.7.6, â€œIPsec Host-to-Host Configurationâ€</a>.
				</div></li><li><div class="para">
					To connect one <acronym class="acronym">LAN</acronym>/<acronym class="acronym">WAN</acronym> to another via IPsec, refer to <a class="xref" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Network_to_Network_Configuration.html" title="2.7.7. IPsec Network-to-Network Configuration">SecciÃ³nÂ 2.7.7, â€œIPsec Network-to-Network Configurationâ€</a>.
				</div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-Creating_an_IPsec_Connection.html"><strong>Anterior</strong>2.7.4. Creating an IPsec Connection</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Host_to_Host_Configuration.html"><strong>Siguiente</strong>2.7.6. IPsec Host-to-Host Configuration</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Network_to_Network_Configuration.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.7.7. IPsec Network-to-Network Configuration</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Virtual_Private_Networks_VPNs.html" title="2.7. Virtual Private Networks (VPNs)" /><link rel="prev" href="sect-Security_Guide-IPsec_Host_to_Host_Configuration-Manual_IPsec_Host_to_Host_Configuration.html" title="2.7.6.2. Manual IPsec Host-to-Host Configuration" /><link rel="next" href="sect-Security_Guide-IPsec_Network_to_Network_Configuration-Manual_IPsec_Network_to_Network_Configuration.html" title="2.7.7.2. Manual IPsec Network-to-Network Configuration" /></head><body class=""><p id="title"><a clas
 s="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-IPsec_Host_to_Host_Configuration-Manual_IPsec_Host_to_Host_Configuration.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-IPsec_Network_to_Network_Configuration-Manual_IPsec_Network_to_Network_Configuration.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Network_to_Network_Configuration">2.7.7. IPsec Network-to-Network Configuration</h3></div></div></div><div class="para">
			IPsec can also be configured to connect an entire network (such as a <acronym class="acronym">LAN</acronym> or <acronym class="acronym">WAN</acronym>) to a remote network using a network-to-network connection. A network-to-network connection requires the setup of <abbr class="abbrev">IPsec</abbr> routers on each side of the connecting networks to transparently process and route information from one node on a <acronym class="acronym">LAN</acronym> to a node on a remote <acronym class="acronym">LAN</acronym>. <a class="xref" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Network_to_Network_Configuration.html#figu-Security_Guide-IPsec_Network_to_Network_Configuration-A_network_to_network_IPsec_tunneled_connection" title="Figura 2.11. A network-to-network IPsec tunneled connection">FiguraÂ 2.11, â€œA network-to-network IPsec tunneled connectionâ€</a> shows a network-to-network <abbr class="abbrev">IPsec</abbr> tunneled connection.
		</div><div class="figure" id="figu-Security_Guide-IPsec_Network_to_Network_Configuration-A_network_to_network_IPsec_tunneled_connection"><div class="figure-contents"><div class="mediaobject"><img src="images/n-t-n-ipsec-diagram.png" alt="A network-to-network IPsec tunneled connection" /><div class="longdesc"><div class="para">
						A network-to-network <abbr class="abbrev">IPsec</abbr> tunneled connection
					</div></div></div></div><h6>Figura 2.11. A network-to-network <abbr class="abbrev">IPsec</abbr> tunneled connection</h6></div><br class="figure-break" /><div class="para">
			This diagram shows two separate <acronym class="acronym">LAN</acronym>s separated by the Internet. These <acronym class="acronym">LAN</acronym>s use <abbr class="abbrev">IPsec</abbr> routers to authenticate and initiate a connection using a secure tunnel through the Internet. Packets that are intercepted in transit would require brute-force decryption in order to crack the cipher protecting the packets between these <acronym class="acronym">LAN</acronym>s. The process of communicating from one node in the 192.168.1.0/24 IP range to another in the 192.168.2.0/24 range is completely transparent to the nodes as the processing, encryption/decryption, and routing of the <abbr class="abbrev">IPsec</abbr> packets are completely handled by the <abbr class="abbrev">IPsec</abbr> router.
		</div><div class="para">
			The information needed for a network-to-network connection include:
		</div><div class="itemizedlist"><ul><li><div class="para">
					The externally-accessible IP addresses of the dedicated <abbr class="abbrev">IPsec</abbr> routers
				</div></li><li><div class="para">
					The network address ranges of the <acronym class="acronym">LAN</acronym>/<acronym class="acronym">WAN</acronym> served by the <abbr class="abbrev">IPsec</abbr> routers (such as 192.168.1.0/24 or 10.0.1.0/24)
				</div></li><li><div class="para">
					The IP addresses of the gateway devices that route the data from the network nodes to the Internet
				</div></li><li><div class="para">
					A unique name, for example, <code class="computeroutput">ipsec1</code>. This is used to identify the <abbr class="abbrev">IPsec</abbr> connection and to distinguish it from other devices or connections.
				</div></li><li><div class="para">
					A fixed encryption key or one automatically generated by <code class="command">racoon</code>
				</div></li><li><div class="para">
					A pre-shared authentication key that is used during the initial stage of the connection and to exchange encryption keys during the session.
				</div></li></ul></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-IPsec_Network_to_Network_Configuration-Network_to_Network_VPN_Connection">2.7.7.1. Network-to-Network (<abbr class="abbrev">VPN</abbr>) Connection</h4></div></div></div><div class="para">
				A network-to-network <abbr class="abbrev">IPsec</abbr> connection uses two <abbr class="abbrev">IPsec</abbr> routers, one for each network, through which the network traffic for the private subnets is routed.
			</div><div class="para">
				For example, as shown in <a class="xref" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Network_to_Network_Configuration.html#figu-Security_Guide-Network_to_Network_VPN_Connection-Network_to_Network_IPsec" title="Figura 2.12. Network-to-Network IPsec">FiguraÂ 2.12, â€œNetwork-to-Network IPsecâ€</a>, if the 192.168.1.0/24 private network sends network traffic to the 192.168.2.0/24 private network, the packets go through gateway0, to ipsec0, through the Internet, to ipsec1, to gateway1, and to the 192.168.2.0/24 subnet.
			</div><div class="para">
				<abbr class="abbrev">IPsec</abbr> routers require publicly addressable IP addresses and a second Ethernet device connected to their respective private networks. Traffic only travels through an <abbr class="abbrev">IPsec</abbr> router if it is intended for another <abbr class="abbrev">IPsec</abbr> router with which it has an encrypted connection.
			</div><div class="figure" id="figu-Security_Guide-Network_to_Network_VPN_Connection-Network_to_Network_IPsec"><div class="figure-contents"><div class="mediaobject"><img src="images/n-t-n-ipsec-diagram.png" alt="Network-to-Network IPsec" /><div class="longdesc"><div class="para">
							Network-to-Network IPsec
						</div></div></div></div><h6>Figura 2.12. Network-to-Network IPsec</h6></div><br class="figure-break" /><div class="para">
				Alternate network configuration options include a firewall between each IP router and the Internet, and an intranet firewall between each <abbr class="abbrev">IPsec</abbr> router and subnet gateway. The <abbr class="abbrev">IPsec</abbr> router and the gateway for the subnet can be one system with two Ethernet devices: one with a public IP address that acts as the <abbr class="abbrev">IPsec</abbr> router; and one with a private IP address that acts as the gateway for the private subnet. Each <abbr class="abbrev">IPsec</abbr> router can use the gateway for its private network or a public gateway to send the packets to the other <abbr class="abbrev">IPsec</abbr> router.
			</div><div class="para">
				Use the following procedure to configure a network-to-network <abbr class="abbrev">IPsec</abbr> connection:
			</div><div class="orderedlist"><ol><li><div class="para">
						In a command shell, type <code class="command">system-config-network</code> to start the <span class="application"><strong>Network Administration Tool</strong></span>.
					</div></li><li><div class="para">
						On the <span class="guilabel"><strong>IPsec</strong></span> tab, click <span class="guibutton"><strong>New</strong></span> to start the <abbr class="abbrev">IPsec</abbr> configuration wizard.
					</div></li><li><div class="para">
						Click <span class="guibutton"><strong>Forward</strong></span> to start configuring a network-to-network <abbr class="abbrev">IPsec</abbr> connection.
					</div></li><li><div class="para">
						Enter a unique nickname for the connection, for example, <strong class="userinput"><code>ipsec0</code></strong>. If required, select the check box to automatically activate the connection when the computer starts. Click <span class="guibutton"><strong>Forward</strong></span> to continue.
					</div></li><li><div class="para">
						Select <span class="guilabel"><strong>Network to Network encryption (VPN)</strong></span> as the connection type, and then click <span class="guibutton"><strong>Forward</strong></span>.
					</div></li><li><div class="para">
						Select the type of encryption to use: manual or automatic.
					</div><div class="para">
						If you select manual encryption, an encryption key must be provided later in the process. If you select automatic encryption, the <code class="command">racoon</code> daemon manages the encryption key. The <code class="filename">ipsec-tools</code> package must be installed if you want to use automatic encryption.
					</div><div class="para">
						Click <span class="guibutton"><strong>Forward</strong></span> to continue.
					</div></li><li><div class="para">
						On the <span class="guilabel"><strong>Local Network</strong></span> page, enter the following information:
					</div><div class="itemizedlist"><ul><li><div class="para">
								<span class="guilabel"><strong>Local Network Address</strong></span> â€” The IP address of the device on the <abbr class="abbrev">IPsec</abbr> router connected to the private network.
							</div></li><li><div class="para">
								<span class="guilabel"><strong>Local Subnet Mask</strong></span> â€” The subnet mask of the local network IP address.
							</div></li><li><div class="para">
								<span class="guilabel"><strong>Local Network Gateway</strong></span> â€” The gateway for the private subnet.
							</div></li></ul></div><div class="para">
						Click <span class="guibutton"><strong>Forward</strong></span> to continue.
					</div><div class="figure" id="figu-Security_Guide-Network_to_Network_VPN_Connection-Local_Network_Information"><div class="figure-contents"><div class="mediaobject"><img src="images/fed-ipsec_n_to_n_local.png" alt="InformaciÃ³n de Red Local" /><div class="longdesc"><div class="para">
									InformaciÃ³n de Red Local
								</div></div></div></div><h6>Figura 2.13. InformaciÃ³n de Red Local</h6></div><br class="figure-break" /></li><li><div class="para">
						On the <span class="guilabel"><strong>Remote Network</strong></span> page, enter the following information:
					</div><div class="itemizedlist"><ul><li><div class="para">
								<span class="guilabel"><strong>Remote IP Address</strong></span> â€” The publicly addressable IP address of the <abbr class="abbrev">IPsec</abbr> router for the <span class="emphasis"><em>other</em></span> private network. In our example, for ipsec0, enter the publicly addressable IP address of ipsec1, and vice versa.
							</div></li><li><div class="para">
								<span class="guilabel"><strong>Remote Network Address</strong></span> â€” The network address of the private subnet behind the <span class="emphasis"><em>other</em></span> <abbr class="abbrev">IPsec</abbr> router. In our example, enter <strong class="userinput"><code>192.168.1.0</code></strong> if configuring ipsec1, and enter <strong class="userinput"><code>192.168.2.0</code></strong> if configuring ipsec0.
							</div></li><li><div class="para">
								<span class="guilabel"><strong>Remote Subnet Mask</strong></span> â€” The subnet mask of the remote IP address.
							</div></li><li><div class="para">
								<span class="guilabel"><strong>Remote Network Gateway</strong></span> â€” The IP address of the gateway for the remote network address.
							</div></li><li><div class="para">
								If manual encryption was selected in step <a class="xref" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Network_to_Network_Configuration.html#list-Security_Guide-list-Security_Guide-list-Security_Guide-st-host-encrypt-type-n">6</a>, specify the encryption key to use or click <span class="guibutton"><strong>Generate</strong></span> to create one.
							</div><div class="para">
								Specify an authentication key or click <span class="guibutton"><strong>Generate</strong></span> to generate one. This key can be any combination of numbers and letters.
							</div></li></ul></div><div class="para">
						Click <span class="guibutton"><strong>Forward</strong></span> to continue.
					</div><div class="figure" id="figu-Security_Guide-Network_to_Network_VPN_Connection-Remote_Network_Information"><div class="figure-contents"><div class="mediaobject"><img src="images/fed-ipsec_n_to_n_remote.png" alt="InformaciÃ³n de Red Remota" /><div class="longdesc"><div class="para">
									InformaciÃ³n de Red Remota
								</div></div></div></div><h6>Figura 2.14. InformaciÃ³n de Red Remota</h6></div><br class="figure-break" /></li><li><div class="para">
						Verify the information on the <span class="guilabel"><strong>IPsec â€” Summary</strong></span> page, and then click <span class="guibutton"><strong>Apply</strong></span>.
					</div></li><li><div class="para">
						Select <span class="guimenu"><strong>File</strong></span> => <span class="guimenuitem"><strong>Save</strong></span> to save the configuration.
					</div></li><li><div class="para">
						Select the <abbr class="abbrev">IPsec</abbr> connection from the list, and then click <span class="guibutton"><strong>Activate</strong></span> to activate the connection.
					</div></li><li><div class="para">
						Habilitando reenvÃo IP:
					</div><div class="orderedlist"><ol><li><div class="para">
								Edit <code class="filename">/etc/sysctl.conf</code> and set <code class="computeroutput">net.ipv4.ip_forward</code> to <strong class="userinput"><code>1</code></strong>.
							</div></li><li><div class="para">
								Use el siguiente comando para habilitar los cambios:
							</div><pre class="screen">[root at myServer ~]# /sbin/sysctl -p /etc/sysctl.conf
</pre></li></ol></div></li></ol></div><div class="para">
				The network script to activate the <abbr class="abbrev">IPsec</abbr> connection automatically creates network routes to send packets through the <abbr class="abbrev">IPsec</abbr> router if necessary.
			</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-IPsec_Host_to_Host_Configuration-Manual_IPsec_Host_to_Host_Configuration.html"><strong>Anterior</strong>2.7.6.2. Manual IPsec Host-to-Host Configuration</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-IPsec_Network_to_Network_Configuration-Manual_IPsec_Network_to_Network_Configuration.html"><strong>Siguiente</strong>2.7.7.2. Manual IPsec Network-to-Network Configur...</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Virtual_Private_Networks_VPNs-Starting_and_Stopping_an_IPsec_Connection.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.7.8. Starting and Stopping an IPsec Connection</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Virtual_Private_Networks_VPNs.html" title="2.7. Virtual Private Networks (VPNs)" /><link rel="prev" href="sect-Security_Guide-IPsec_Network_to_Network_Configuration-Manual_IPsec_Network_to_Network_Configuration.html" title="2.7.7.2. Manual IPsec Network-to-Network Configuration" /><link rel="next" href="sect-Security_Guide-Firewalls.html" title="2.8. Firewalls" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" a
 lt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-IPsec_Network_to_Network_Configuration-Manual_IPsec_Network_to_Network_Configuration.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Firewalls.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Virtual_Private_Networks_VPNs-Starting_and_Stopping_an_IPsec_Connection">2.7.8. Starting and Stopping an <abbr class="abbrev">IPsec</abbr> Connection</h3></div></div></div><div class="para">
			If the <abbr class="abbrev">IPsec</abbr> connection was not configured to activate on boot, you can control it from the command line.
		</div><div class="para">
			To start the connection, use the following command on each host for host-to-host IPsec, or each <abbr class="abbrev">IPsec</abbr> router for network-to-network IPsec:
		</div><pre class="screen">[root at myServer ~] # /sbin/ifup <em class="replaceable"><code><nickname></code></em>
</pre><div class="para">
			where <em class="replaceable"><code><nickname></code></em> is the nickname configured earlier, such as <code class="computeroutput">ipsec0</code>.
		</div><div class="para">
			Para detener la conexiÃ³n, use el siguiente comando:
		</div><pre class="screen">[root at myServer ~] # /sbin/ifdown <em class="replaceable"><code><nickname></code></em>
</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-IPsec_Network_to_Network_Configuration-Manual_IPsec_Network_to_Network_Configuration.html"><strong>Anterior</strong>2.7.7.2. Manual IPsec Network-to-Network Configur...</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Firewalls.html"><strong>Siguiente</strong>2.8. Firewalls</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Virtual_Private_Networks_VPNs-VPNs_and_PROD.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.7.2. VPNs and Fedora</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Virtual_Private_Networks_VPNs.html" title="2.7. Virtual Private Networks (VPNs)" /><link rel="prev" href="sect-Security_Guide-Virtual_Private_Networks_VPNs.html" title="2.7. Virtual Private Networks (VPNs)" /><link rel="next" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec.html" title="2.7.3. IPsec" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.or
 g"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Virtual_Private_Networks_VPNs.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Virtual_Private_Networks_VPNs-VPNs_and_PROD">2.7.2. VPNs and Fedora</h3></div></div></div><div class="para">
			Fedora provides various options in terms of implementing a software solution to securely connect to a <acronym class="acronym">WAN</acronym>. <em class="firstterm">Internet Protocol Security</em> (<acronym class="acronym">IPsec</acronym>) is the supported <abbr class="abbrev">VPN</abbr> implementation for Fedora, and sufficiently addresses the usability needs of organizations with branch offices or remote users.
		</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Virtual_Private_Networks_VPNs.html"><strong>Anterior</strong>2.7. Virtual Private Networks (VPNs)</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec.html"><strong>Siguiente</strong>2.7.3. IPsec</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Virtual_Private_Networks_VPNs.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.7. Virtual Private Networks (VPNs)</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="chap-Security_Guide-Securing_Your_Network.html" title="CapÃtulo 2. Securing Your Network" /><link rel="prev" href="sect-Security_Guide-Additional_Resources-Useful_Kerberos_Websites.html" title="2.6.10.2. Useful Kerberos Websites" /><link rel="next" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-VPNs_and_PROD.html" title="2.7.2. VPNs and Fedora" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right
 " href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Additional_Resources-Useful_Kerberos_Websites.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-VPNs_and_PROD.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h2 class="title" id="sect-Security_Guide-Virtual_Private_Networks_VPNs">2.7. Virtual Private Networks (VPNs)</h2></div></div></div><div class="para">
		Organizations with several satellite offices often connect to each other with dedicated lines for efficiency and protection of sensitive data in transit. For example, many businesses use frame relay or <em class="firstterm">Asynchronous Transfer Mode</em> (<acronym class="acronym">ATM</acronym>) lines as an end-to-end networking solution to link one office with others. This can be an expensive proposition, especially for small to medium sized businesses (<acronym class="acronym">SMB</acronym>s) that want to expand without paying the high costs associated with enterprise-level, dedicated digital circuits.
	</div><div class="para">
		To address this need, <em class="firstterm">Virtual Private Networks</em> (<abbr class="abbrev">VPN</abbr>s) were developed. Following the same functional principles as dedicated circuits, <abbr class="abbrev">VPN</abbr>s allow for secured digital communication between two parties (or networks), creating a <em class="firstterm">Wide Area Network</em> (<acronym class="acronym">WAN</acronym>) from existing <em class="firstterm">Local Area Networks</em> (<acronym class="acronym">LAN</acronym>s). Where it differs from frame relay or ATM is in its transport medium. <abbr class="abbrev">VPN</abbr>s transmit over IP using datagrams as the transport layer, making it a secure conduit through the Internet to an intended destination. Most free software <abbr class="abbrev">VPN</abbr> implementations incorporate open standard encryption methods to further mask data in transit.
	</div><div class="para">
		Some organizations employ hardware <abbr class="abbrev">VPN</abbr> solutions to augment security, while others use software or protocol-based implementations. Several vendors provide hardware <abbr class="abbrev">VPN</abbr> solutions, such as Cisco, Nortel, IBM, and Checkpoint. There is a free software-based <abbr class="abbrev">VPN</abbr> solution for Linux called FreeS/Wan that utilizes a standardized <em class="firstterm">Internet Protocol Security</em> (<abbr class="abbrev">IPsec</abbr>) implementation. These <abbr class="abbrev">VPN</abbr> solutions, irrespective of whether they are hardware or software based, act as specialized routers that exist between the IP connection from one office to another.
	</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Virtual_Private_Networks_VPNs-How_Does_a_VPN_Work">2.7.1. How Does a VPN Work?</h3></div></div></div><div class="para">
			When a packet is transmitted from a client, it sends it through the <abbr class="abbrev">VPN</abbr> router or gateway, which adds an <em class="firstterm">Authentication Header</em> (<abbr class="abbrev">AH</abbr>) for routing and authentication. The data is then encrypted and, finally, enclosed with an <em class="firstterm">Encapsulating Security Payload</em> (<abbr class="abbrev">ESP</abbr>). This latter constitutes the decryption and handling instructions.
		</div><div class="para">
			The receiving <abbr class="abbrev">VPN</abbr> router strips the header information, decrypts the data, and routes it to its intended destination (either a workstation or other node on a network). Using a network-to-network connection, the receiving node on the local network receives the packets already decrypted and ready for processing. The encryption/decryption process in a network-to-network <abbr class="abbrev">VPN</abbr> connection is transparent to a local node.
		</div><div class="para">
			With such a heightened level of security, an attacker must not only intercept a packet, but decrypt the packet as well. Intruders who employ a man-in-the-middle attack between a server and client must also have access to at least one of the private keys for authenticating sessions. Because they employ several layers of authentication and encryption, <abbr class="abbrev">VPN</abbr>s are a secure and effective means of connecting multiple remote nodes to act as a unified intranet.
		</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Additional_Resources-Useful_Kerberos_Websites.html"><strong>Anterior</strong>2.6.10.2. Useful Kerberos Websites</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-VPNs_and_PROD.html"><strong>Siguiente</strong>2.7.2. VPNs and Fedora</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Vulnerability_Assessment-Defining_Assessment_and_Testing.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.2.2. Definiendo EvaluaciÃ³n y Pruebas</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Vulnerability_Assessment.html" title="1.2. Vulnerability Assessment" /><link rel="prev" href="sect-Security_Guide-Vulnerability_Assessment.html" title="1.2. Vulnerability Assessment" /><link rel="next" href="sect-Security_Guide-Vulnerability_Assessment-Evaluating_the_Tools.html" title="1.2.3. Herramientas de EvaluaciÃ³n" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="htt
 p://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Vulnerability_Assessment.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Vulnerability_Assessment-Evaluating_the_Tools.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Vulnerability_Assessment-Defining_Assessment_and_Testing">1.2.2. Definiendo EvaluaciÃ³n y Pruebas</h3></div></div></div><div class="para">
			Vulnerability assessments may be broken down into one of two types: <em class="firstterm">Outside looking in</em> and <em class="firstterm">inside looking around</em>.
		</div><div class="para">
			When performing an outside looking in vulnerability assessment, you are attempting to compromise your systems from the outside. Being external to your company provides you with the cracker's viewpoint. You see what a cracker sees â€” publicly-routable IP addresses, systems on your <em class="firstterm">DMZ</em>, external interfaces of your firewall, and more. DMZ stands for "demilitarized zone", which corresponds to a computer or small subnetwork that sits between a trusted internal network, such as a corporate private LAN, and an untrusted external network, such as the public Internet. Typically, the DMZ contains devices accessible to Internet traffic, such as Web (HTTP ) servers, FTP servers, SMTP (e-mail) servers and DNS servers.
		</div><div class="para">
			When you perform an inside looking around vulnerability assessment, you are somewhat at an advantage since you are internal and your status is elevated to trusted. This is the viewpoint you and your co-workers have once logged on to your systems. You see print servers, file servers, databases, and other resources.
		</div><div class="para">
			There are striking distinctions between these two types of vulnerability assessments. Being internal to your company gives you elevated privileges more so than any outsider. Still today in most organizations, security is configured in such a manner as to keep intruders out. Very little is done to secure the internals of the organization (such as departmental firewalls, user-level access controls, authentication procedures for internal resources, and more). Typically, there are many more resources when looking around inside as most systems are internal to a company. Once you set yourself outside of the company, you immediately are given an untrusted status. The systems and resources available to you externally are usually very limited.
		</div><div class="para">
			Consider the difference between vulnerability assessments and <em class="firstterm">penetration tests</em>. Think of a vulnerability assessment as the first step to a penetration test. The information gleaned from the assessment is used for testing. Whereas the assessment is undertaken to check for holes and potential vulnerabilities, the penetration testing actually attempts to exploit the findings.
		</div><div class="para">
			Assessing network infrastructure is a dynamic process. Security, both information and physical, is dynamic. Performing an assessment shows an overview, which can turn up false positives and false negatives.
		</div><div class="para">
			Security administrators are only as good as the tools they use and the knowledge they retain. Take any of the assessment tools currently available, run them against your system, and it is almost a guarantee that there are some false positives. Whether by program fault or user error, the result is the same. The tool may find vulnerabilities which in reality do not exist (false positive); or, even worse, the tool may not find vulnerabilities that actually do exist (false negative).
		</div><div class="para">
			Now that the difference between a vulnerability assessment and a penetration test is defined, take the findings of the assessment and review them carefully before conducting a penetration test as part of your new best practices approach.
		</div><div class="warning"><h2>Warning</h2><div class="para">
				Attempting to exploit vulnerabilities on production resources can have adverse effects to the productivity and efficiency of your systems and network.
			</div></div><div class="para">
			En la lista siguiente se examinan algunos de los beneficios de llevar a cabo evaluaciones de vulnerabilidad.
		</div><div class="itemizedlist"><ul><li><div class="para">
					Cree un enfoque proactivo sobre la seguridad de la informaciÃ³n
				</div></li><li><div class="para">
					Finds potential exploits before crackers find them
				</div></li><li><div class="para">
					Resultados en los sistemas que se mantiene actualizados y parcheados
				</div></li><li><div class="para">
					Promover el crecimiento y las ayudas en el desarrollo de la especializaciÃ³n de personal
				</div></li><li><div class="para">
					Abates financial loss and negative publicity
				</div></li></ul></div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Defining_Assessment_and_Testing-Establishing_a_Methodology">1.2.2.1. Estableciendo una MetodologÃa</h4></div></div></div><div class="para">
				To aid in the selection of tools for a vulnerability assessment, it is helpful to establish a vulnerability assessment methodology. Unfortunately, there is no predefined or industry approved methodology at this time; however, common sense and best practices can act as a sufficient guide.
			</div><div class="para">
				<span class="emphasis"><em>What is the target? Are we looking at one server, or are we looking at our entire network and everything within the network? Are we external or internal to the company?</em></span> The answers to these questions are important as they help determine not only which tools to select but also the manner in which they are used.
			</div><div class="para">
				To learn more about establishing methodologies, refer to the following websites:
			</div><div class="itemizedlist"><ul><li><div class="para">
						<a href="http://www.isecom.org/osstmm/">http://www.isecom.org/osstmm/</a> <em class="citetitle">The Open Source Security Testing Methodology Manual</em> (OSSTMM)
					</div></li><li><div class="para">
						<a href="http://www.owasp.org/">http://www.owasp.org/</a> <em class="citetitle">The Open Web Application Security Project</em>
					</div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Vulnerability_Assessment.html"><strong>Anterior</strong>1.2. Vulnerability Assessment</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Vulnerability_Assessment-Evaluating_the_Tools.html"><strong>Siguiente</strong>1.2.3. Herramientas de EvaluaciÃ³n</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Vulnerability_Assessment-Evaluating_the_Tools.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.2.3. Herramientas de EvaluaciÃ³n</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-Vulnerability_Assessment.html" title="1.2. Vulnerability Assessment" /><link rel="prev" href="sect-Security_Guide-Vulnerability_Assessment-Defining_Assessment_and_Testing.html" title="1.2.2. Definiendo EvaluaciÃ³n y Pruebas" /><link rel="next" href="sect-Security_Guide-Evaluating_the_Tools-Nessus.html" title="1.2.3.2. Nessus" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="htt
 p://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Vulnerability_Assessment-Defining_Assessment_and_Testing.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Evaluating_the_Tools-Nessus.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Vulnerability_Assessment-Evaluating_the_Tools">1.2.3. Herramientas de EvaluaciÃ³n</h3></div></div></div><div class="para">
			An assessment can start by using some form of an information gathering tool. When assessing the entire network, map the layout first to find the hosts that are running. Once located, examine each host individually. Focusing on these hosts requires another set of tools. Knowing which tools to use may be the most crucial step in finding vulnerabilities.
		</div><div class="para">
			Just as in any aspect of everyday life, there are many different tools that perform the same job. This concept applies to performing vulnerability assessments as well. There are tools specific to operating systems, applications, and even networks (based on the protocols used). Some tools are free; others are not. Some tools are intuitive and easy to use, while others are cryptic and poorly documented but have features that other tools do not.
		</div><div class="para">
			Finding the right tools may be a daunting task and in the end, experience counts. If possible, set up a test lab and try out as many tools as you can, noting the strengths and weaknesses of each. Review the README file or man page for the tool. Additionally, look to the Internet for more information, such as articles, step-by-step guides, or even mailing lists specific to a tool.
		</div><div class="para">
			The tools discussed below are just a small sampling of the available tools.
		</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-Evaluating_the_Tools-Scanning_Hosts_with_Nmap">1.2.3.1. Escaneando Equipos con Nmap</h4></div></div></div><div class="para">
				Nmap is a popular tool included in Fedora that can be used to determine the layout of a network. Nmap has been available for many years and is probably the most often used tool when gathering information. An excellent man page is included that provides a detailed description of its options and usage. Administrators can use Nmap on a network to find host systems and open ports on those systems.
			</div><div class="para">
				Nmap is a competent first step in vulnerability assessment. You can map out all the hosts within your network and even pass an option that allows Nmap to attempt to identify the operating system running on a particular host. Nmap is a good foundation for establishing a policy of using secure services and stopping unused services.
			</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h5 class="title" id="sect-Security_Guide-Scanning_Hosts_with_Nmap-Using_Nmap">1.2.3.1.1. Usando Nmap</h5></div></div></div><div class="para">
					Nmap can be run from a shell prompt by typing the <code class="command">nmap</code> command followed by the hostname or IP address of the machine to scan.
				</div><pre class="screen"><code class="command">nmap foo.example.com</code>
</pre><div class="para">
					The results of the scan (which could take up to a few minutes, depending on where the host is located) should look similar to the following:
				</div><pre class="screen">Starting Nmap 4.68 ( http://nmap.org )
Interesting ports on foo.example.com:
Not shown: 1710 filtered ports
PORT    STATE  SERVICE
22/tcp  open   ssh
53/tcp  open   domain
70/tcp  closed gopher
80/tcp  open   http
113/tcp closed auth
</pre><div class="para">
					Nmap tests the most common network communication ports for listening or waiting services. This knowledge can be helpful to an administrator who wants to close down unnecessary or unused services.
				</div><div class="para">
					For more information about using Nmap, refer to the official homepage at the following URL:
				</div><div class="para">
					<a href="http://www.insecure.org/">http://www.insecure.org/</a>
				</div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Vulnerability_Assessment-Defining_Assessment_and_Testing.html"><strong>Anterior</strong>1.2.2. Definiendo EvaluaciÃ³n y Pruebas</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Evaluating_the_Tools-Nessus.html"><strong>Siguiente</strong>1.2.3.2. Nessus</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-Vulnerability_Assessment.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.2. Vulnerability Assessment</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="chap-Security_Guide-Security_Overview.html" title="CapÃtulo 1. Security Overview" /><link rel="prev" href="chap-Security_Guide-Security_Overview.html" title="CapÃtulo 1. Security Overview" /><link rel="next" href="sect-Security_Guide-Vulnerability_Assessment-Defining_Assessment_and_Testing.html" title="1.2.2. Definiendo EvaluaciÃ³n y Pruebas" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://do
 cs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security_Guide-Security_Overview.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Vulnerability_Assessment-Defining_Assessment_and_Testing.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h2 class="title" id="sect-Security_Guide-Vulnerability_Assessment">1.2. Vulnerability Assessment</h2></div></div></div><div class="para">
		Given time, resources, and motivation, a cracker can break into nearly any system. At the end of the day, all of the security procedures and technologies currently available cannot guarantee that any systems are completely safe from intrusion. Routers help secure gateways to the Internet. Firewalls help secure the edge of the network. Virtual Private Networks safely pass data in an encrypted stream. Intrusion detection systems warn you of malicious activity. However, the success of each of these technologies is dependent upon a number of variables, including:
	</div><div class="itemizedlist"><ul><li><div class="para">
				The expertise of the staff responsible for configuring, monitoring, and maintaining the technologies.
			</div></li><li><div class="para">
				The ability to patch and update services and kernels quickly and efficiently.
			</div></li><li><div class="para">
				The ability of those responsible to keep constant vigilance over the network.
			</div></li></ul></div><div class="para">
		Given the dynamic state of data systems and technologies, securing corporate resources can be quite complex. Due to this complexity, it is often difficult to find expert resources for all of your systems. While it is possible to have personnel knowledgeable in many areas of information security at a high level, it is difficult to retain staff who are experts in more than a few subject areas. This is mainly because each subject area of information security requires constant attention and focus. Information security does not stand still.
	</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h3 class="title" id="sect-Security_Guide-Vulnerability_Assessment-Thinking_Like_the_Enemy">1.2.1. Pensado como el Enemigo</h3></div></div></div><div class="para">
			Suppose that you administer an enterprise network. Such networks are commonly comprised of operating systems, applications, servers, network monitors, firewalls, intrusion detection systems, and more. Now imagine trying to keep current with each of these. Given the complexity of today's software and networking environments, exploits and bugs are a certainty. Keeping current with patches and updates for an entire network can prove to be a daunting task in a large organization with heterogeneous systems.
		</div><div class="para">
			Combine the expertise requirements with the task of keeping current, and it is inevitable that adverse incidents occur, systems are breached, data is corrupted, and service is interrupted.
		</div><div class="para">
			To augment security technologies and aid in protecting systems, networks, and data, you must think like a cracker and gauge the security of your systems by checking for weaknesses. Preventative vulnerability assessments against your own systems and network resources can reveal potential issues that can be addressed before a cracker exploits it.
		</div><div class="para">
			A vulnerability assessment is an internal audit of your network and system security; the results of which indicate the confidentiality, integrity, and availability of your network (as explained in <a class="xref" href="chap-Security_Guide-Security_Overview.html#sect-Security_Guide-What_is_Computer_Security-Standardizing_Security" title="1.1.1.3. Standardizing Security">SecciÃ³nÂ 1.1.1.3, â€œStandardizing Securityâ€</a>). Typically, vulnerability assessment starts with a reconnaissance phase, during which important data regarding the target systems and resources is gathered. This phase leads to the system readiness phase, whereby the target is essentially checked for all known vulnerabilities. The readiness phase culminates in the reporting phase, where the findings are classified into categories of high, medium, and low risk; and methods for improving the security (or mitigating the risk of vulnerability) of the target are discussed.
		</div><div class="para">
			If you were to perform a vulnerability assessment of your home, you would likely check each door to your home to see if they are closed and locked. You would also check every window, making sure that they closed completely and latch correctly. This same concept applies to systems, networks, and electronic data. Malicious users are the thieves and vandals of your data. Focus on their tools, mentality, and motivations, and you can then react swiftly to their actions.
		</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security_Guide-Security_Overview.html"><strong>Anterior</strong>CapÃtulo 1. Security Overview</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Vulnerability_Assessment-Defining_Assessment_and_Testing.html"><strong>Siguiente</strong>1.2.2. Definiendo EvaluaciÃ³n y Pruebas</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-xinetd_Configuration_Files-Altering_xinetd_Configuration_Files.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.5.4.3. Altering xinetd Configuration Files</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd_Configuration_Files.html" title="2.5.4. xinetd Configuration Files" /><link rel="prev" href="sect-Security_Guide-xinetd_Configuration_Files-The_etcxinetd.d_Directory.html" title="2.5.4.2. El directorio /etc/xinetd.d/" /><link rel="next" href="sect-Security_Guide-Altering_xinetd_Configuration_Files-Access_Control_Options.html" title="2.5.4.3.2. Access Control Options" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common
 _Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-xinetd_Configuration_Files-The_etcxinetd.d_Directory.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Altering_xinetd_Configuration_Files-Access_Control_Options.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-xinetd_Configuration_Files-Altering_xinetd_Configuration_Files">2.5.4.3. Altering xinetd Configuration Files</h4></div></div></div><div class="para">
				A range of directives is available for services protected by <code class="systemitem">xinetd</code>. This section highlights some of the more commonly used options.
			</div><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h5 class="title" id="sect-Security_Guide-Altering_xinetd_Configuration_Files-Logging_Options">2.5.4.3.1. Logging Options</h5></div></div></div><div class="para">
					The following logging options are available for both <code class="filename">/etc/xinetd.conf</code> and the service-specific configuration files within the <code class="filename">/etc/xinetd.d/</code> directory.
				</div><div class="para">
					The following is a list of some of the more commonly used logging options:
				</div><div class="itemizedlist"><ul><li><div class="para">
							<code class="option">ATTEMPT</code> â€” Logs the fact that a failed attempt was made (<code class="option">log_on_failure</code>).
						</div></li><li><div class="para">
							<code class="option">DURATION</code> â€” Logs the length of time the service is used by a remote system (<code class="option">log_on_success</code>).
						</div></li><li><div class="para">
							<code class="option">EXIT</code> â€” Logs the exit status or termination signal of the service (<code class="option">log_on_success</code>).
						</div></li><li><div class="para">
							<code class="option">HOST</code> â€” Logs the remote host's IP address (<code class="option">log_on_failure</code> and <code class="option">log_on_success</code>).
						</div></li><li><div class="para">
							<code class="option">PID</code> â€” Logs the process ID of the server receiving the request (<code class="option">log_on_success</code>).
						</div></li><li><div class="para">
							<code class="option">USERID</code> â€” Logs the remote user using the method defined in RFC 1413 for all multi-threaded stream services (<code class="option">log_on_failure</code> and<code class="option">log_on_success</code>).
						</div></li></ul></div><div class="para">
					For a complete list of logging options, refer to the <code class="filename">xinetd.conf</code> man page.
				</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-xinetd_Configuration_Files-The_etcxinetd.d_Directory.html"><strong>Anterior</strong>2.5.4.2. El directorio /etc/xinetd.d/</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Altering_xinetd_Configuration_Files-Access_Control_Options.html"><strong>Siguiente</strong>2.5.4.3.2. Access Control Options</a></li></ul></body></html>

--- NEW FILE sect-Security_Guide-xinetd_Configuration_Files-The_etcxinetd.d_Directory.html ---
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.5.4.2. El directorio /etc/xinetd.d/</title><link rel="stylesheet" href="./Common_Content/css/default.css" type="text/css" /><meta name="generator" content="publican" /><meta name="package" content="fedora-security-guide-es-ES-1.0-Security Guide" /><link rel="home" href="index.html" title="security-guide" /><link rel="up" href="sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd_Configuration_Files.html" title="2.5.4. xinetd Configuration Files" /><link rel="prev" href="sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd_Configuration_Files.html" title="2.5.4. xinetd Configuration Files" /><link rel="next" href="sect-Security_Guide-xinetd_Configuration_Files-Altering_xinetd_Configuration_Files.html" title="2.5.4.3. Altering xinetd Configuration Files" /></head><body class=""><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Comm
 on_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd_Configuration_Files.html"><strong>Anterior</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-xinetd_Configuration_Files-Altering_xinetd_Configuration_Files.html"><strong>Siguiente</strong></a></li></ul><div class="section" lang="es-ES" xml:lang="es-ES"><div class="titlepage"><div><div><h4 class="title" id="sect-Security_Guide-xinetd_Configuration_Files-The_etcxinetd.d_Directory">2.5.4.2. El directorio /etc/xinetd.d/</h4></div></div></div><div class="para">
				The <code class="filename">/etc/xinetd.d/</code> directory contains the configuration files for each service managed by <code class="systemitem">xinetd</code> and the names of the files correlate to the service. As with <code class="filename">xinetd.conf</code>, this directory is read only when the <code class="systemitem">xinetd</code> service is started. For any changes to take effect, the administrator must restart the <code class="systemitem">xinetd</code> service.
			</div><div class="para">
				The format of files in the <code class="filename">/etc/xinetd.d/</code> directory use the same conventions as <code class="filename">/etc/xinetd.conf</code>. The primary reason the configuration for each service is stored in a separate file is to make customization easier and less likely to affect other services.
			</div><div class="para">
				To gain an understanding of how these files are structured, consider the <code class="filename">/etc/xinetd.d/krb5-telnet</code> file:
			</div><pre class="screen">service telnet
{
         flags           = REUSE
         socket_type     = stream
         wait            = no
         user            = root
         server          = /usr/kerberos/sbin/telnetd
         log_on_failure  += USERID
         disable         = yes
}
</pre><div class="para">
				These lines control various aspects of the <code class="command">telnet</code> service:
			</div><div class="itemizedlist"><ul><li><div class="para">
						<code class="option">service</code> â€” Specifies the service name, usually one of those listed in the <code class="filename">/etc/services</code> file.
					</div></li><li><div class="para">
						<code class="option">flags</code> â€” Sets any of a number of attributes for the connection. <code class="option">REUSE</code> instructs <code class="systemitem">xinetd</code> to reuse the socket for a Telnet connection.
					</div><div class="note"><h2>Note</h2><div class="para">
							The <code class="option">REUSE</code> flag is deprecated. All services now implicitly use the <code class="option">REUSE</code> flag.
						</div></div></li><li><div class="para">
						<code class="option">socket_type</code> â€” Sets the network socket type to <code class="option">stream</code>.
					</div></li><li><div class="para">
						<code class="option">wait</code> â€” Specifies whether the service is single-threaded (<code class="option">yes</code>) or multi-threaded (<code class="option">no</code>).
					</div></li><li><div class="para">
						<code class="option">user</code> â€” Specifies which user ID the process runs under.
					</div></li><li><div class="para">
						<code class="option">server</code> â€” Specifies which binary executable to launch.
					</div></li><li><div class="para">
						<code class="option">log_on_failure</code> â€” Specifies logging parameters for <code class="option">log_on_failure</code> in addition to those already defined in <code class="filename">xinetd.conf</code>.
					</div></li><li><div class="para">
						<code class="option">disable</code> â€” Specifies whether the service is disabled (<code class="option">yes</code>) or enabled (<code class="option">no</code>).
					</div></li></ul></div><div class="para">
				Refer to the <code class="filename">xinetd.conf</code> man page for more information about these options and their usage.
			</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd_Configuration_Files.html"><strong>Anterior</strong>2.5.4. xinetd Configuration Files</a></li><li class="up"><a accesskey="u" href="#"><strong>Subir</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Inicio</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-xinetd_Configuration_Files-Altering_xinetd_Configuration_Files.html"><strong>Siguiente</strong>2.5.4.3. Altering xinetd Configuration Files</a></li></ul></body></html>