[web] Added languages en-US nl-NL it-IT es-ES
Eric Christensen
sparks at fedoraproject.org
Fri Jul 23 14:27:40 UTC 2010
commit 428cff5b6552bcb7c78159b91c6b93a4929f635e
Author: Eric H Christensen <eric at christensenplace.us>
Date: Fri Jul 23 10:26:07 2010 -0400
Added languages en-US nl-NL it-IT es-ES
fedoradocs.db | Bin 352256 -> 352256 bytes
public_html/Sitemap | 8 +-
.../Fedora-13-Security_Guide-en-US.epub | Bin 765669 -> 766974 bytes
.../Security_Guide/Common_Content/css/common.css | 48 +-
.../13/html-single/Security_Guide/index.html | 1286 +++++++++-----------
.../Security_Guide/Common_Content/css/common.css | 48 +-
...ide-Encryption-Data_in_Motion-Secure_Shell.html | 2 +-
...on-Data_in_Motion-Virtual_Private_Networks.html | 2 +-
.../Security_Guide-Encryption-Data_in_Motion.html | 2 +-
...tecting_Data_at_Rest-File_Based_Encryption.html | 2 +-
.../13/html/Security_Guide/We_Need_Feedback.html | 2 +-
.../Fedora/13/html/Security_Guide/apas02.html | 42 +-
.../Fedora/13/html/Security_Guide/apas02s02.html | 6 +-
.../Fedora/13/html/Security_Guide/apas02s03.html | 6 +-
.../Fedora/13/html/Security_Guide/apas02s04.html | 6 +-
.../Fedora/13/html/Security_Guide/apas02s05.html | 6 +-
.../Fedora/13/html/Security_Guide/apas02s06.html | 6 +-
.../appe-Publican-Revision_History.html | 2 +-
.../chap-Security_Guide-Encryption.html | 4 +-
.../chap-Security_Guide-Encryption_Standards.html | 40 +-
...General_Principles_of_Information_Security.html | 4 +-
.../chap-Security_Guide-References.html | 2 +-
.../chap-Security_Guide-Secure_Installation.html | 4 +-
.../chap-Security_Guide-Securing_Your_Network.html | 134 +--
.../chap-Security_Guide-Security_Overview.html | 56 +-
.../chap-Security_Guide-Software_Maintenance.html | 4 +-
.../en-US/Fedora/13/html/Security_Guide/index.html | 6 +-
.../pref-Security_Guide-Preface.html | 14 +-
...y_Guide-Additional_Resources-Related_Books.html | 2 +-
...Additional_Resources-Related_Documentation.html | 2 +-
...itional_Resources-Useful_Firewall_Websites.html | 2 +-
...tional_Resources-Useful_IP_Tables_Websites.html | 2 +-
...itional_Resources-Useful_Kerberos_Websites.html | 2 +-
...e-Additional_Resources-Useful_PAM_Websites.html | 2 +-
...nal_Resources-Useful_TCP_Wrappers_Websites.html | 2 +-
...Configuration_Files-Access_Control_Options.html | 11 +-
...tion_Files-Binding_and_Redirection_Options.html | 5 +-
...guration_Files-Resource_Management_Options.html | 2 +-
...ulnerabilities-Threats_to_Network_Security.html | 8 +-
...Vulnerabilities-Threats_to_Server_Security.html | 4 +-
...hreats_to_Workstation_and_Home_PC_Security.html | 4 +-
...curity_Guide-Attackers_and_Vulnerabilities.html | 6 +-
...figuration-Activating_the_IPTables_Service.html | 8 +-
...ration-Enabling_and_Disabling_the_Firewall.html | 2 +-
...e-Basic_Firewall_Configuration-Other_Ports.html | 2 +-
...Firewall_Configuration-Saving_the_Settings.html | 2 +-
...ic_Firewall_Configuration-Trusted_Services.html | 2 +-
...mmand_Options_for_IPTables-Command_Options.html | 5 +-
...ptions_for_IPTables-IPTables_Match_Options.html | 11 +-
...ns_for_IPTables-IPTables_Parameter_Options.html | 2 +-
...mmand_Options_for_IPTables-Listing_Options.html | 2 +-
...ommand_Options_for_IPTables-Target_Options.html | 2 +-
...Security_Guide-Common_Exploits_and_Attacks.html | 4 +-
...crypted_Archives-Installation-Instructions.html | 2 +-
...on-7_Zip_Encrypted_Archives-Things_of_note.html | 2 +-
..._Zip_Encrypted_Archives-Usage_Instructions.html | 2 +-
..._Guide-Encryption-7_Zip_Encrypted_Archives.html | 4 +-
...otecting_Data_at_Rest-Full_Disk_Encryption.html | 2 +-
...tion-Using_GPG-About_Public_Key_Encryption.html | 2 +-
...ryption-Using_GPG-Creating_GPG_Keys_in_KDE.html | 3 +-
...yption-Using_GPG-Creating_GPG_Keys_in_KDE1.html | 2 +-
...Encryption-Using_GPG-Using_GPG_with_Alpine.html | 3 +-
..._GPG_with_Evolution-Signing_and_Encrypting.html | 2 +-
...ing_GPG-Using_GPG_with_Evolution-Verifying.html | 2 +-
...ryption-Using_GPG-Using_GPG_with_Evolution.html | 2 +-
...ption-Using_GPG-Using_GPG_with_Thunderbird.html | 4 +-
.../sect-Security_Guide-Encryption-Using_GPG.html | 4 +-
...g_the_Tools-Anticipating_Your_Future_Needs.html | 2 +-
...Security_Guide-Evaluating_the_Tools-Nessus.html | 2 +-
...-Security_Guide-Evaluating_the_Tools-Nikto.html | 2 +-
...uide-Evaluating_the_Tools-VLAD_the_Scanner.html | 2 +-
...de-FORWARD_and_NAT_Rules-DMZs_and_IPTables.html | 5 +-
...ity_Guide-FORWARD_and_NAT_Rules-Prerouting.html | 8 +-
...urity_Guide-Firewalls-Additional_Resources.html | 4 +-
...ide-Firewalls-Basic_Firewall_Configuration.html | 7 +-
..._Guide-Firewalls-Common_IPTables_Filtering.html | 14 +-
...rity_Guide-Firewalls-FORWARD_and_NAT_Rules.html | 20 +-
...Firewalls-IPTables_and_Connection_Tracking.html | 5 +-
.../sect-Security_Guide-Firewalls-IPv6.html | 5 +-
...alicious_Software_and_Spoofed_IP_Addresses.html | 8 +-
...ct-Security_Guide-Firewalls-Using_IPTables.html | 13 +-
.../sect-Security_Guide-Firewalls.html | 8 +-
...curity_Guide-IPTables-Additional_Resources.html | 4 +-
...uide-IPTables-Command_Options_for_IPTables.html | 7 +-
...ty_Guide-IPTables-IPTables_Control_Scripts.html | 7 +-
...-Security_Guide-IPTables-IPTables_and_IPv6.html | 2 +-
...urity_Guide-IPTables-Saving_IPTables_Rules.html | 8 +-
.../sect-Security_Guide-IPTables.html | 4 +-
...ch_Options-Additional_Match_Option_Modules.html | 2 +-
...Guide-IPTables_Match_Options-ICMP_Protocol.html | 2 +-
..._Guide-IPTables_Match_Options-UDP_Protocol.html | 2 +-
...on-Manual_IPsec_Host_to_Host_Configuration.html | 25 +-
...ual_IPsec_Network_to_Network_Configuration.html | 32 +-
...curity_Guide-Kerberos-Additional_Resources.html | 4 +-
...e-Kerberos-Configuring_a_Kerberos_5_Client.html | 8 +-
...e-Kerberos-Configuring_a_Kerberos_5_Server.html | 14 +-
...ity_Guide-Kerberos-Domain_to_Realm_Mapping.html | 6 +-
...Security_Guide-Kerberos-How_Kerberos_Works.html | 2 +-
...curity_Guide-Kerberos-Kerberos_Terminology.html | 2 +-
...t-Security_Guide-Kerberos-Kerberos_and_PAM.html | 2 +-
...eros-Setting_Up_Cross_Realm_Authentication.html | 10 +-
...y_Guide-Kerberos-Setting_Up_Secondary_KDCs.html | 14 +-
.../sect-Security_Guide-Kerberos.html | 12 +-
...ide-LUKS_Disk_Encryption-Links_of_Interest.html | 2 +-
...ting_Directories-Step_by_Step_Instructions.html | 2 +-
...irectories-What_you_have_just_accomplished.html | 2 +-
...Encryption-Manually_Encrypting_Directories.html | 2 +-
.../sect-Security_Guide-LUKS_Disk_Encryption.html | 4 +-
...ecurity_Guide-Option_Fields-Access_Control.html | 5 +-
...ct-Security_Guide-Option_Fields-Expansions.html | 8 +-
...ecurity_Guide-Option_Fields-Shell_Commands.html | 8 +-
...PAM_Configuration_File_Format-Control_Flag.html | 2 +-
...Configuration_File_Format-Module_Arguments.html | 5 +-
...-PAM_Configuration_File_Format-Module_Name.html | 2 +-
...al_Caching-Common_pam_timestamp_Directives.html | 2 +-
...AM_and_Device_Ownership-Application_Access.html | 2 +-
...ntication_Modules_PAM-Additional_Resources.html | 4 +-
...ntication_Modules_PAM-Creating_PAM_Modules.html | 2 +-
..._Modules_PAM-PAM_Configuration_File_Format.html | 15 +-
...cation_Modules_PAM-PAM_Configuration_Files.html | 4 +-
...-PAM_and_Administrative_Credential_Caching.html | 11 +-
...ation_Modules_PAM-PAM_and_Device_Ownership.html | 10 +-
...Modules_PAM-Sample_PAM_Configuration_Files.html | 5 +-
...Guide-Pluggable_Authentication_Modules_PAM.html | 4 +-
...allation-Utilize_LUKS_Partition_Encryption.html | 2 +-
...curity_Guide-Securing_FTP-Anonymous_Access.html | 16 +-
...ing_FTP-Use_TCP_Wrappers_To_Control_Access.html | 2 +-
...-Security_Guide-Securing_FTP-User_Accounts.html | 5 +-
...Guide-Securing_NFS-Beware_of_Syntax_Errors.html | 11 +-
...g_NFS-Do_Not_Use_the_no_root_squash_Option.html | 2 +-
...de-Securing_NFS-NFS_Firewall_Configuration.html | 2 +-
...Assign_Static_Ports_and_Use_iptables_Rules.html | 8 +-
...Securing_NIS-Edit_the_varypsecurenets_File.html | 5 +-
...e-Securing_NIS-Use_Kerberos_Authentication.html | 2 +-
...Password_like_NIS_Domain_Name_and_Hostname.html | 8 +-
...ring_Portmap-Protect_portmap_With_iptables.html | 8 +-
...ty_Guide-Securing_Sendmail-Mail_only_Users.html | 2 +-
...y_Guide-Securing_Sendmail-NFS_and_Sendmail.html | 2 +-
.../sect-Security_Guide-Security_Updates.html | 4 +-
...ecurity_Guide-Server_Security-Securing_FTP.html | 13 +-
...ecurity_Guide-Server_Security-Securing_NFS.html | 4 +-
...ecurity_Guide-Server_Security-Securing_NIS.html | 4 +-
...ity_Guide-Server_Security-Securing_Portmap.html | 4 +-
...ty_Guide-Server_Security-Securing_Sendmail.html | 4 +-
...r_Security-Securing_the_Apache_HTTP_Server.html | 9 +-
...curity-Verifying_Which_Ports_Are_Listening.html | 23 +-
.../sect-Security_Guide-Server_Security.html | 37 +-
...onfiguring_Firefox_to_use_Kerberos_for_SSO.html | 19 +-
...O-Getting_Started_with_your_new_Smart_Card.html | 10 +-
...ign_on_SSO-How_Smart_Card_Enrollment_Works.html | 4 +-
...gle_Sign_on_SSO-How_Smart_Card_Login_Works.html | 4 +-
.../sect-Security_Guide-Single_Sign_on_SSO.html | 10 +-
...gned_Packages_from_Well_Known_Repositories.html | 2 +-
...curity_Updates-Adjusting_Automatic_Updates.html | 2 +-
...enance-Plan_and_Configure_Security_Updates.html | 2 +-
...Wrappers_Configuration_Files-Option_Fields.html | 10 +-
...P_Wrappers_and_xinetd-Additional_Resources.html | 4 +-
...nd_xinetd-TCP_Wrappers_Configuration_Files.html | 46 +-
...urity_Guide-TCP_Wrappers_and_xinetd-xinetd.html | 2 +-
...pers_and_xinetd-xinetd_Configuration_Files.html | 7 +-
...ect-Security_Guide-TCP_Wrappers_and_xinetd.html | 12 +-
...Server_Security-Inattentive_Administration.html | 6 +-
...rver_Security-Inherently_Insecure_Services.html | 2 +-
...eats_to_Server_Security-Unpatched_Services.html | 2 +-
...PC_Security-Vulnerable_Client_Applications.html | 2 +-
...ide-Updating_Packages-Applying_the_Changes.html | 20 +-
...dating_Packages-Installing_Signed_Packages.html | 11 +-
...pdating_Packages-Verifying_Signed_Packages.html | 17 +-
...ide-Using_IPTables-Basic_Firewall_Policies.html | 8 +-
...Tables-Saving_and_Restoring_IPTables_Rules.html | 5 +-
...Networks_VPNs-Creating_an_IPsec_Connection.html | 2 +-
..._Guide-Virtual_Private_Networks_VPNs-IPsec.html | 2 +-
...orks_VPNs-IPsec_Host_to_Host_Configuration.html | 15 +-
...l_Private_Networks_VPNs-IPsec_Installation.html | 2 +-
...PNs-IPsec_Network_to_Network_Configuration.html | 15 +-
...-Starting_and_Stopping_an_IPsec_Connection.html | 8 +-
...irtual_Private_Networks_VPNs-VPNs_and_PROD.html | 2 +-
...curity_Guide-Virtual_Private_Networks_VPNs.html | 4 +-
...Assessment-Defining_Assessment_and_Testing.html | 4 +-
...nerability_Assessment-Evaluating_the_Tools.html | 12 +-
...ct-Security_Guide-Vulnerability_Assessment.html | 4 +-
..._Files-Altering_xinetd_Configuration_Files.html | 4 +-
...figuration_Files-The_etcxinetd.d_Directory.html | 5 +-
.../Fedora-13-Security_Guide-en-US.pdf | Bin 1446953 -> 1450073 bytes
184 files changed, 1162 insertions(+), 1550 deletions(-)
---
diff --git a/fedoradocs.db b/fedoradocs.db
index 44c0aec..78016df 100644
Binary files a/fedoradocs.db and b/fedoradocs.db differ
diff --git a/public_html/Sitemap b/public_html/Sitemap
index 06b8bd5..93ed4f4 100644
--- a/public_html/Sitemap
+++ b/public_html/Sitemap
@@ -1538,25 +1538,25 @@
</url>
<url>
<loc>http://docs.fedoraproject.org/en-US/Fedora/13/epub/Security_Guide/Fedora-13-Security_Guide-en-US.epub</loc>
- <lastmod>2010-05-22</lastmod>
+ <lastmod>2010-07-23</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>
<url>
<loc>http://docs.fedoraproject.org/en-US/Fedora/13/html/Security_Guide/index.html</loc>
- <lastmod>2010-05-22</lastmod>
+ <lastmod>2010-07-23</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>
<url>
<loc>http://docs.fedoraproject.org/en-US/Fedora/13/html-single/Security_Guide/index.html</loc>
- <lastmod>2010-05-22</lastmod>
+ <lastmod>2010-07-23</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>
<url>
<loc>http://docs.fedoraproject.org/en-US/Fedora/13/pdf/Security_Guide/Fedora-13-Security_Guide-en-US.pdf</loc>
- <lastmod>2010-05-22</lastmod>
+ <lastmod>2010-07-23</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>
diff --git a/public_html/en-US/Fedora/13/epub/Security_Guide/Fedora-13-Security_Guide-en-US.epub b/public_html/en-US/Fedora/13/epub/Security_Guide/Fedora-13-Security_Guide-en-US.epub
index 182ce5c..fe05f19 100644
Binary files a/public_html/en-US/Fedora/13/epub/Security_Guide/Fedora-13-Security_Guide-en-US.epub and b/public_html/en-US/Fedora/13/epub/Security_Guide/Fedora-13-Security_Guide-en-US.epub differ
diff --git a/public_html/en-US/Fedora/13/html-single/Security_Guide/Common_Content/css/common.css b/public_html/en-US/Fedora/13/html-single/Security_Guide/Common_Content/css/common.css
index e1f4d9f..a196f22 100644
--- a/public_html/en-US/Fedora/13/html-single/Security_Guide/Common_Content/css/common.css
+++ b/public_html/en-US/Fedora/13/html-single/Security_Guide/Common_Content/css/common.css
@@ -50,7 +50,8 @@ body.desktop .book > .toc {
line-height:1.35em;
}
-.toc .chapter, .toc .appendix, .toc .glossary {
+.toc .glossary,
+.toc .chapter, .toc .appendix {
margin-top:1em;
}
@@ -59,7 +60,8 @@ body.desktop .book > .toc {
display:block;
}
-span.appendix, span.glossary {
+span.glossary,
+span.appendix {
display:block;
margin-top:0.5em;
}
@@ -346,7 +348,6 @@ a.version:focus, a.version:hover {
clear:both;
}
-
/*revision history*/
.revhistory {
display:block;
@@ -362,34 +363,24 @@ a.version:focus, a.version:hover {
}
.revhistory td {
- text-align:right;
+ text-align :left;
padding:0em;
border: none;
border-top: 1px solid #fff;
+ font-weight: bold;
}
-
-.revhistory tr td:first-child {
- text-align:left;
+.revhistory .simplelist td {
+ font-weight: normal;
}
-.revhistory tr td p, .revhistory tr td div.para {
- text-align:left;
- font-weight:bold;
- display:block;
- margin:0em;
- padding:0em;
- padding-bottom:0.7em;
- border-bottom:1px solid #eee;
+.revhistory .simplelist {
+ margin-bottom: 1.5em;
+ margin-left: 1em;
}
.revhistory table th {
- background-color:transparent;
- color:#336699;
- font-size:2em;
- padding: 1em 0em;
- border: none;
- border-bottom:1px solid #eee;
+ display: none;
}
@@ -901,6 +892,10 @@ th, td {
border: 1px solid #000;
}
+.simplelist th, .simplelist td {
+ border: none;
+}
+
table table td {
border-bottom:1px dotted #aaa;
background-color:white;
@@ -964,6 +959,10 @@ span.chapter {
margin-top:0.5em;
}
+table.simplelist td, .calloutlist table td {
+ border-style: none;
+}
+
/*Breadcrumbs*/
#breadcrumbs ul li.first:before {
content:" ";
@@ -1007,7 +1006,8 @@ span.chapter {
margin-bottom:1em;
}
-.glossary dt, .index dt {
+.glossary dt,
+.index dt {
color:#444;
padding-top:.5em;
}
@@ -1375,10 +1375,6 @@ pre {
border-radius: 15px;
}
-.term{
- color:#336699;
-}
-
.package, .citetitle {
font-style: italic;
}
diff --git a/public_html/en-US/Fedora/13/html-single/Security_Guide/index.html b/public_html/en-US/Fedora/13/html-single/Security_Guide/index.html
index 20128d9..9bb79f1 100644
--- a/public_html/en-US/Fedora/13/html-single/Security_Guide/index.html
+++ b/public_html/en-US/Fedora/13/html-single/Security_Guide/index.html
@@ -1,9 +1,9 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Security Guide</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><meta name="description" content="The Fedora Security Guide is designed to assist users of Fedora in learning the processes and practices of securing workstations and servers against local and remote intrusion, exploitation, and malicious activity. Focused on Fedora Linux but detailing concepts and techniques valid for all Linux systems, the Fedora 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 too
ls, systems running Linux can be both fully functional and secured from most common intrusion and exploit methods." /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><div xml:lang="en-US" class="book" title="Security Guide" lang="en-US"><div class="titlepage"><div><div class="producttitle" font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><span class="productname">Fedora</span> <span class="productnumber">13</span></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" f
ont-size="12pt" text-align="center"><h1 id="id4999114" class="title">Security Guide</h1></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h2 class="subtitle">A Guide to Securing Fedora Linux</h2></div><p class="edition">Edition 13.0</p><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h3 class="corpauthor">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Security Guide</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><meta name="description" content="The Fedora Security Guide is designed to assist users of Fedora in learning the processes and practices of securing workstations and servers against local and remote intrusion, exploitation, and malicious activity. Focused on Fedora Linux but detailing concepts and techniques valid for all Linux systems, the Fedora 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 tool
s, systems running Linux can be both fully functional and secured from most common intrusion and exploit methods." /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><div xml:lang="en-US" class="book" title="Security Guide" id="id4512724" lang="en-US"><div class="titlepage"><div><div class="producttitle" font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><span class="productname">Fedora</span> <span class="productnumber">13</span></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-w
eight="bold" font-size="12pt" text-align="center"><h1 id="id4512724" class="title">Security Guide</h1></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h2 class="subtitle">A Guide to Securing Fedora Linux</h2></div><p class="edition">Edition 13.0</p><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h3 class="corpauthor">
<span class="inlinemediaobject"><object data="Common_Content/images/title_logo.svg" type="image/svg+xml"> Logo</object></span>
- </h3></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div xml:lang="en-US" class="authorgroup" lang="en-US"><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 class="author"><h3 class="author"><span class="firstname">Adam</span> <span class="surname">Ligas</span></h3><div class="affiliation"><span class="orgname">Fedora Project</span></div><code class="email"><a class="email" href="mailto:adam at physco.com">adam at physco.com</a></code></div></div></div><h
r /><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div id="id3281572" class="legalnotice"><h1 class="legalnotice">Legal Notice</h1><div class="para">
+ </h3></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div xml:lang="en-US" class="authorgroup" lang="en-US"><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 class="author"><h3 class="author"><span class="firstname">Adam</span> <span class="surname">Ligas</span></h3><div class="affiliation"><span class="orgname">Fedora Project</span></div><code class="email"><a class="email" href="mailto:adam at physco.com">adam at physco.com</a></code></div></div></div><h
r /><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div id="id2734794" class="legalnotice"><h1 class="legalnotice">Legal Notice</h1><div class="para">
Copyright <span class="trademark"></span>© 2010 Red Hat, Inc.
</div><div class="para">
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at <a href="http://creativecommons.org/licenses/by-sa/3.0/">http://creativecommons.org/licenses/by-sa/3.0/</a>. The original authors of this document, and Red Hat, designate the Fedora Project as the "Attribution Party" for purposes of CC-BY-SA. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
@@ -23,11 +23,11 @@
All other trademarks are the property of their respective owners.
</div></div></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div class="abstract" title="Abstract"><h6>Abstract</h6><div class="para">
The Fedora Security Guide is designed to assist users of Fedora in learning the processes and practices of securing workstations and servers against local and remote intrusion, exploitation, and malicious activity. Focused on Fedora Linux but detailing concepts and techniques valid for all Linux systems, the Fedora 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">Preface</a></span></dt><dd><dl><dt><span class="section"><a href="#id3212091">1. Document Conventions</a></span></dt><dd><dl><dt><span class="section"><a href="#id3210480">1.1. Typographic Conventions</a></span></dt><dt><span class="section"><a href="#id3395706">1.2. Pull-quote Conventions</a></span></dt><dt><span class="section"><a href="#id4396729">1.3. Notes and Warnings</a></span></dt></dl></dd><dt><span class="section"><a href="#We_Need_Feedback">2. We Need Feedback!</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Security_Guide-Security_Overview">1. Security Overview</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Introduction_to_Security">1.1. Introduction to Security</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Introduction_to_Security-What_is_Computer_Security">1
.1.1. What is Computer Security?</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Introduction_to_Security-SELinux">1.1.2. SELinux</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Introduction_to_Security-Security_Controls">1.1.3. Security Controls</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Introduction_to_Security-Conclusion">1.1.4. Conclusion</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Vulnerability_Assessment">1.2. Vulnerability Assessment</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Vulnerability_Assessment-Thinking_Like_the_Enemy">1.2.1. Thinking Like the Enemy</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Vulnerability_Assessment-Defining_Assessment_and_Testing">1.2.2. Defining Assessment and Testing</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Vulnerability_Assessment-Evaluatin
g_the_Tools">1.2.3. Evaluating the Tools</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Attackers_and_Vulnerabilities">1.3. Attackers and Vulnerabilities</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Attackers_and_Vulnerabilities-A_Quick_History_of_Hackers">1.3.1. A Quick History of Hackers</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Network_Security">1.3.2. Threats to Network Security</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Server_Security">1.3.3. Threats to Server Security</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Workstation_and_Home_PC_Security">1.3.4. Threats to Workstation and Home PC Security</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Common_Exploits_and_Atta
cks">1.4. Common Exploits and Attacks</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Security_Updates">1.5. Security Updates</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Security_Updates-Updating_Packages">1.5.1. Updating Packages</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Updating_Packages-Verifying_Signed_Packages">1.5.2. Verifying Signed Packages</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Updating_Packages-Installing_Signed_Packages">1.5.3. Installing Signed Packages</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Updating_Packages-Applying_the_Changes">1.5.4. Applying the Changes</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#chap-Security_Guide-Securing_Your_Network">2. Securing Your Network</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Workstation_Security">2.1. Workstation Secu
rity</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Workstation_Security-Evaluating_Workstation_Security">2.1.1. Evaluating Workstation Security</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Workstation_Security-BIOS_and_Boot_Loader_Security">2.1.2. BIOS and Boot Loader Security</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Workstation_Security-Password_Security">2.1.3. Password Security</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Workstation_Security-Administrative_Controls">2.1.4. Administrative Controls</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Workstation_Security-Available_Network_Services">2.1.5. Available Network Services</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Workstation_Security-Personal_Firewalls">2.1.6. Personal Firewalls</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Works
tation_Security-Security_Enhanced_Communication_Tools">2.1.7. Security Enhanced Communication Tools</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Server_Security">2.2. Server Security</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Server_Security-Securing_Services_With_TCP_Wrappers_and_xinetd">2.2.1. Securing Services With TCP Wrappers and xinetd</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Server_Security-Securing_Portmap">2.2.2. Securing Portmap</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Server_Security-Securing_NIS">2.2.3. Securing NIS</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Server_Security-Securing_NFS">2.2.4. Securing NFS</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Server_Security-Securing_the_Apache_HTTP_Server">2.2.5. Securing the Apache HTTP Server</a></span></dt><dt><span class="section"><a
href="#sect-Security_Guide-Server_Security-Securing_FTP">2.2.6. Securing FTP</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Server_Security-Securing_Sendmail">2.2.7. Securing Sendmail</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Server_Security-Verifying_Which_Ports_Are_Listening">2.2.8. Verifying Which Ports Are Listening</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Single_Sign_on_SSO">2.3. Single Sign-on (SSO)</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Single_Sign_on_SSO-Introduction">2.3.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Single_Sign_on_SSO-Getting_Started_with_your_new_Smart_Card">2.3.2. Getting Started with your new Smart Card</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Enrollment_Works">2.3.3. How Smart Card Enrollment Works</a></span></
dt><dt><span class="section"><a href="#sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Login_Works">2.3.4. How Smart Card Login Works</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Single_Sign_on_SSO-Configuring_Firefox_to_use_Kerberos_for_SSO">2.3.5. Configuring Firefox to use Kerberos for SSO</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Pluggable_Authentication_Modules_PAM">2.4. Pluggable Authentication Modules (PAM)</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Advantages_of_PAM">2.4.1. Advantages of PAM</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_Files">2.4.2. PAM Configuration Files</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_File_Format">2.4.3. PAM Configuration File Format<
/a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Sample_PAM_Configuration_Files">2.4.4. Sample PAM Configuration Files</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Creating_PAM_Modules">2.4.5. Creating PAM Modules</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Administrative_Credential_Caching">2.4.6. PAM and Administrative Credential Caching</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Device_Ownership">2.4.7. PAM and Device Ownership</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Additional_Resources">2.4.8. Additional Resources</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-TCP_Wrappers_and_xinetd">2.5. TCP Wrappers and x
inetd</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers">2.5.1. TCP Wrappers</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers_Configuration_Files">2.5.2. TCP Wrappers Configuration Files</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd">2.5.3. xinetd</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd_Configuration_Files">2.5.4. xinetd Configuration Files</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-TCP_Wrappers_and_xinetd-Additional_Resources">2.5.5. Additional Resources</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Kerberos">2.6. Kerberos</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-What_is_Kerberos">2.6.1. What is Kerberos?</a></span></dt><dt><sp
an class="section"><a href="#sect-Security_Guide-Kerberos-Kerberos_Terminology">2.6.2. Kerberos Terminology</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-How_Kerberos_Works">2.6.3. How Kerberos Works</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-Kerberos_and_PAM">2.6.4. Kerberos and PAM</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Server">2.6.5. Configuring a Kerberos 5 Server</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Client">2.6.6. Configuring a Kerberos 5 Client</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-Domain_to_Realm_Mapping">2.6.7. Domain-to-Realm Mapping</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-Setting_Up_Secondary_KDCs">2.6.8. Setting Up Secondary KDCs</a></span></dt><dt><span class="section"><a href="#se
ct-Security_Guide-Kerberos-Setting_Up_Cross_Realm_Authentication">2.6.9. Setting Up Cross Realm Authentication</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-Additional_Resources">2.6.10. Additional Resources</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Virtual_Private_Networks_VPNs">2.7. Virtual Private Networks (VPNs)</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Virtual_Private_Networks_VPNs-How_Does_a_VPN_Work">2.7.1. How Does a VPN Work?</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Virtual_Private_Networks_VPNs-VPNs_and_PROD">2.7.2. VPNs and Fedora</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec">2.7.3. IPsec</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Virtual_Private_Networks_VPNs-Creating_an_IPsec_Connection">2.7.4. Creating an <abbr class="abbrev">IPsec</ab
br> Connection</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Installation">2.7.5. IPsec Installation</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Host_to_Host_Configuration">2.7.6. IPsec Host-to-Host Configuration</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Network_to_Network_Configuration">2.7.7. IPsec Network-to-Network Configuration</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Virtual_Private_Networks_VPNs-Starting_and_Stopping_an_IPsec_Connection">2.7.8. Starting and Stopping an <abbr class="abbrev">IPsec</abbr> Connection</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Firewalls">2.8. Firewalls</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Firewalls-Netfilter_and_IPTables">2.8.1. Netfilter and IPT
ables</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Firewalls-Basic_Firewall_Configuration">2.8.2. Basic Firewall Configuration</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Firewalls-Using_IPTables">2.8.3. Using IPTables</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Firewalls-Common_IPTables_Filtering">2.8.4. Common IPTables Filtering</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Firewalls-FORWARD_and_NAT_Rules">2.8.5. <code class="computeroutput">FORWARD</code> and <acronym class="acronym">NAT</acronym> Rules</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Firewalls-Malicious_Software_and_Spoofed_IP_Addresses">2.8.6. Malicious Software and Spoofed IP Addresses</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Firewalls-IPTables_and_Connection_Tracking">2.8.7. IPTables and Connection Tracking</a></span></dt><dt><span class="section"
><a href="#sect-Security_Guide-Firewalls-IPv6">2.8.8. IPv6</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Firewalls-Additional_Resources">2.8.9. Additional Resources</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-IPTables">2.9. IPTables</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-IPTables-Packet_Filtering">2.9.1. Packet Filtering</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-IPTables-Command_Options_for_IPTables">2.9.2. Command Options for IPTables</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-IPTables-Saving_IPTables_Rules">2.9.3. Saving IPTables Rules</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-IPTables-IPTables_Control_Scripts">2.9.4. IPTables Control Scripts</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-IPTables-IPTables_and_IPv6">2.9.5. IPTables and IPv6</a></span></dt><dt><span
class="section"><a href="#sect-Security_Guide-IPTables-Additional_Resources">2.9.6. Additional Resources</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#chap-Security_Guide-Encryption">3. Encryption</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Encryption-Data_at_Rest">3.1. Data at Rest</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Encryption-Protecting_Data_at_Rest-Full_Disk_Encryption">3.2. Full Disk Encryption</a></span></dt><dt><span class="section"><a href="#Security_Guide-Encryption-Protecting_Data_at_Rest-File_Based_Encryption">3.3. File Based Encryption</a></span></dt><dt><span class="section"><a href="#Security_Guide-Encryption-Data_in_Motion">3.4. Data in Motion</a></span></dt><dt><span class="section"><a href="#Security_Guide-Encryption-Data_in_Motion-Virtual_Private_Networks">3.5. Virtual Private Networks</a></span></dt><dt><span class="section"><a href="#Security_Guide-Encryption-D
ata_in_Motion-Secure_Shell">3.6. Secure Shell</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-LUKS_Disk_Encryption">3.7. LUKS Disk Encryption</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-LUKS_Disk_Encryption-LUKS_Implementation_in_Fedora">3.7.1. LUKS Implementation in Fedora</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories">3.7.2. Manually Encrypting Directories</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-Step_by_Step_Instructions">3.7.3. Step-by-Step Instructions</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-What_you_have_just_accomplished">3.7.4. What you have just accomplished.</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-LUKS_Disk_Encryption-Links_of_Interest">
3.7.5. Links of Interest</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives">3.8. 7-Zip Encrypted Archives</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Installation">3.8.1. 7-Zip Installation in Fedora</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Installation-Instructions">3.8.2. Step-by-Step Installation Instructions</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Usage_Instructions">3.8.3. Step-by-Step Usage Instructions</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Things_of_note">3.8.4. Things of note</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Encryption-Using_GPG">3.9. Using GNU Privacy Guard (GnuPG)</a></span></dt><dd><
dl><dt><span class="section"><a href="#sect-Security_Guide-Encryption-Using_GPG-Keys_in_GNOME">3.9.1. Generating GPG Keys in GNOME</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE1">3.9.2. Generating GPG Keys in KDE</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE">3.9.3. Generating GPG Keys Using the Command Line</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Alpine">3.9.4. Using GPG with Alpine</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution">3.9.5. Using GPG with Evolution</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Thunderbird">3.9.6. Using GPG with Thunderbird</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Encryption-Using_G
PG-About_Public_Key_Encryption">3.9.7. About Public Key Encryption</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#chap-Security_Guide-General_Principles_of_Information_Security">4. General Principles of Information Security</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-General_Principles_of_Information_Security-Tips_Guides_and_Tools">4.1. Tips, Guides, and Tools</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Security_Guide-Secure_Installation">5. Secure Installation</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Secure_Installation-Disk_Partitions">5.1. Disk Partitions</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Secure_Installation-Utilize_LUKS_Partition_Encryption">5.2. Utilize LUKS Partition Encryption</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Security_Guide-Software_Maintenance">6. Software Maintenance</a></span></d
t><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Software_Maintenance-Install_Minimal_Software">6.1. Install Minimal Software</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates">6.2. Plan and Configure Security Updates</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates-Adjusting_Automatic_Updates">6.3. Adjusting Automatic Updates</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Software_Maintenance-Install_Signed_Packages_from_Well_Known_Repositories">6.4. Install Signed Packages from Well Known Repositories</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Security_Guide-References">7. References</a></span></dt><dt><span class="appendix"><a href="#chap-Security_Guide-Encryption_Standards">A. Encryption Standards</a></span></dt><dd><dl><dt><span class="section"><a href=
"#id3170015">A.1. Synchronous Encryption</a></span></dt><dd><dl><dt><span class="section"><a href="#id4431743">A.1.1. Advanced Encryption Standard - AES</a></span></dt><dt><span class="section"><a href="#id3399350">A.1.2. Data Encryption Standard - DES</a></span></dt></dl></dd><dt><span class="section"><a href="#id3264168">A.2. Public-key Encryption</a></span></dt><dd><dl><dt><span class="section"><a href="#id3488782">A.2.1. Diffie-Hellman</a></span></dt><dt><span class="section"><a href="#id3374442">A.2.2. RSA</a></span></dt><dt><span class="section"><a href="#id3236285">A.2.3. DSA</a></span></dt><dt><span class="section"><a href="#id3324079">A.2.4. SSL/TLS</a></span></dt><dt><span class="section"><a href="#id3489826">A.2.5. Cramer-Shoup Cryptosystem</a></span></dt><dt><span class="section"><a href="#id3511325">A.2.6. ElGamal Encryption</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="#appe-Publican-Revision_History">B. Revision History</a></span></dt
></dl></div><div xml:lang="en-US" class="preface" title="Preface" id="pref-Security_Guide-Preface" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Preface</h1></div></div></div><div xml:lang="en-US" class="section" title="1. Document Conventions" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id3212091">1. Document Conventions</h2></div></div></div><div class="para">
+ </div></div></div></div><hr /></div><div class="toc"><dl><dt><span class="preface"><a href="#pref-Security_Guide-Preface">Preface</a></span></dt><dd><dl><dt><span class="section"><a href="#id2912980">1. Document Conventions</a></span></dt><dd><dl><dt><span class="section"><a href="#id2753333">1.1. Typographic Conventions</a></span></dt><dt><span class="section"><a href="#id2773234">1.2. Pull-quote Conventions</a></span></dt><dt><span class="section"><a href="#id2734741">1.3. Notes and Warnings</a></span></dt></dl></dd><dt><span class="section"><a href="#We_Need_Feedback">2. We Need Feedback!</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Security_Guide-Security_Overview">1. Security Overview</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Introduction_to_Security">1.1. Introduction to Security</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Introduction_to_Security-What_is_Computer_Security">1
.1.1. What is Computer Security?</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Introduction_to_Security-SELinux">1.1.2. SELinux</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Introduction_to_Security-Security_Controls">1.1.3. Security Controls</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Introduction_to_Security-Conclusion">1.1.4. Conclusion</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Vulnerability_Assessment">1.2. Vulnerability Assessment</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Vulnerability_Assessment-Thinking_Like_the_Enemy">1.2.1. Thinking Like the Enemy</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Vulnerability_Assessment-Defining_Assessment_and_Testing">1.2.2. Defining Assessment and Testing</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Vulnerability_Assessment-Evaluatin
g_the_Tools">1.2.3. Evaluating the Tools</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Attackers_and_Vulnerabilities">1.3. Attackers and Vulnerabilities</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Attackers_and_Vulnerabilities-A_Quick_History_of_Hackers">1.3.1. A Quick History of Hackers</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Network_Security">1.3.2. Threats to Network Security</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Server_Security">1.3.3. Threats to Server Security</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Workstation_and_Home_PC_Security">1.3.4. Threats to Workstation and Home PC Security</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Common_Exploits_and_Atta
cks">1.4. Common Exploits and Attacks</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Security_Updates">1.5. Security Updates</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Security_Updates-Updating_Packages">1.5.1. Updating Packages</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Updating_Packages-Verifying_Signed_Packages">1.5.2. Verifying Signed Packages</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Updating_Packages-Installing_Signed_Packages">1.5.3. Installing Signed Packages</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Updating_Packages-Applying_the_Changes">1.5.4. Applying the Changes</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#chap-Security_Guide-Securing_Your_Network">2. Securing Your Network</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Workstation_Security">2.1. Workstation Secu
rity</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Workstation_Security-Evaluating_Workstation_Security">2.1.1. Evaluating Workstation Security</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Workstation_Security-BIOS_and_Boot_Loader_Security">2.1.2. BIOS and Boot Loader Security</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Workstation_Security-Password_Security">2.1.3. Password Security</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Workstation_Security-Administrative_Controls">2.1.4. Administrative Controls</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Workstation_Security-Available_Network_Services">2.1.5. Available Network Services</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Workstation_Security-Personal_Firewalls">2.1.6. Personal Firewalls</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Works
tation_Security-Security_Enhanced_Communication_Tools">2.1.7. Security Enhanced Communication Tools</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Server_Security">2.2. Server Security</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Server_Security-Securing_Services_With_TCP_Wrappers_and_xinetd">2.2.1. Securing Services With TCP Wrappers and xinetd</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Server_Security-Securing_Portmap">2.2.2. Securing Portmap</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Server_Security-Securing_NIS">2.2.3. Securing NIS</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Server_Security-Securing_NFS">2.2.4. Securing NFS</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Server_Security-Securing_the_Apache_HTTP_Server">2.2.5. Securing the Apache HTTP Server</a></span></dt><dt><span class="section"><a
href="#sect-Security_Guide-Server_Security-Securing_FTP">2.2.6. Securing FTP</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Server_Security-Securing_Sendmail">2.2.7. Securing Sendmail</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Server_Security-Verifying_Which_Ports_Are_Listening">2.2.8. Verifying Which Ports Are Listening</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Single_Sign_on_SSO">2.3. Single Sign-on (SSO)</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Single_Sign_on_SSO-Introduction">2.3.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Single_Sign_on_SSO-Getting_Started_with_your_new_Smart_Card">2.3.2. Getting Started with your new Smart Card</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Enrollment_Works">2.3.3. How Smart Card Enrollment Works</a></span></
dt><dt><span class="section"><a href="#sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Login_Works">2.3.4. How Smart Card Login Works</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Single_Sign_on_SSO-Configuring_Firefox_to_use_Kerberos_for_SSO">2.3.5. Configuring Firefox to use Kerberos for SSO</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Pluggable_Authentication_Modules_PAM">2.4. Pluggable Authentication Modules (PAM)</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Advantages_of_PAM">2.4.1. Advantages of PAM</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_Files">2.4.2. PAM Configuration Files</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_File_Format">2.4.3. PAM Configuration File Format<
/a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Sample_PAM_Configuration_Files">2.4.4. Sample PAM Configuration Files</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Creating_PAM_Modules">2.4.5. Creating PAM Modules</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Administrative_Credential_Caching">2.4.6. PAM and Administrative Credential Caching</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Device_Ownership">2.4.7. PAM and Device Ownership</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Additional_Resources">2.4.8. Additional Resources</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-TCP_Wrappers_and_xinetd">2.5. TCP Wrappers and x
inetd</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers">2.5.1. TCP Wrappers</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers_Configuration_Files">2.5.2. TCP Wrappers Configuration Files</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd">2.5.3. xinetd</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd_Configuration_Files">2.5.4. xinetd Configuration Files</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-TCP_Wrappers_and_xinetd-Additional_Resources">2.5.5. Additional Resources</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Kerberos">2.6. Kerberos</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-What_is_Kerberos">2.6.1. What is Kerberos?</a></span></dt><dt><sp
an class="section"><a href="#sect-Security_Guide-Kerberos-Kerberos_Terminology">2.6.2. Kerberos Terminology</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-How_Kerberos_Works">2.6.3. How Kerberos Works</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-Kerberos_and_PAM">2.6.4. Kerberos and PAM</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Server">2.6.5. Configuring a Kerberos 5 Server</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Client">2.6.6. Configuring a Kerberos 5 Client</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-Domain_to_Realm_Mapping">2.6.7. Domain-to-Realm Mapping</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-Setting_Up_Secondary_KDCs">2.6.8. Setting Up Secondary KDCs</a></span></dt><dt><span class="section"><a href="#se
ct-Security_Guide-Kerberos-Setting_Up_Cross_Realm_Authentication">2.6.9. Setting Up Cross Realm Authentication</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-Additional_Resources">2.6.10. Additional Resources</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Virtual_Private_Networks_VPNs">2.7. Virtual Private Networks (VPNs)</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Virtual_Private_Networks_VPNs-How_Does_a_VPN_Work">2.7.1. How Does a VPN Work?</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Virtual_Private_Networks_VPNs-VPNs_and_PROD">2.7.2. VPNs and Fedora</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec">2.7.3. IPsec</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Virtual_Private_Networks_VPNs-Creating_an_IPsec_Connection">2.7.4. Creating an <abbr class="abbrev">IPsec</ab
br> Connection</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Installation">2.7.5. IPsec Installation</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Host_to_Host_Configuration">2.7.6. IPsec Host-to-Host Configuration</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Network_to_Network_Configuration">2.7.7. IPsec Network-to-Network Configuration</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Virtual_Private_Networks_VPNs-Starting_and_Stopping_an_IPsec_Connection">2.7.8. Starting and Stopping an <abbr class="abbrev">IPsec</abbr> Connection</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Firewalls">2.8. Firewalls</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Firewalls-Netfilter_and_IPTables">2.8.1. Netfilter and IPT
ables</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Firewalls-Basic_Firewall_Configuration">2.8.2. Basic Firewall Configuration</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Firewalls-Using_IPTables">2.8.3. Using IPTables</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Firewalls-Common_IPTables_Filtering">2.8.4. Common IPTables Filtering</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Firewalls-FORWARD_and_NAT_Rules">2.8.5. <code class="computeroutput">FORWARD</code> and <acronym class="acronym">NAT</acronym> Rules</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Firewalls-Malicious_Software_and_Spoofed_IP_Addresses">2.8.6. Malicious Software and Spoofed IP Addresses</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Firewalls-IPTables_and_Connection_Tracking">2.8.7. IPTables and Connection Tracking</a></span></dt><dt><span class="section"
><a href="#sect-Security_Guide-Firewalls-IPv6">2.8.8. IPv6</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Firewalls-Additional_Resources">2.8.9. Additional Resources</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-IPTables">2.9. IPTables</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-IPTables-Packet_Filtering">2.9.1. Packet Filtering</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-IPTables-Command_Options_for_IPTables">2.9.2. Command Options for IPTables</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-IPTables-Saving_IPTables_Rules">2.9.3. Saving IPTables Rules</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-IPTables-IPTables_Control_Scripts">2.9.4. IPTables Control Scripts</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-IPTables-IPTables_and_IPv6">2.9.5. IPTables and IPv6</a></span></dt><dt><span
class="section"><a href="#sect-Security_Guide-IPTables-Additional_Resources">2.9.6. Additional Resources</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#chap-Security_Guide-Encryption">3. Encryption</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Encryption-Data_at_Rest">3.1. Data at Rest</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Encryption-Protecting_Data_at_Rest-Full_Disk_Encryption">3.2. Full Disk Encryption</a></span></dt><dt><span class="section"><a href="#Security_Guide-Encryption-Protecting_Data_at_Rest-File_Based_Encryption">3.3. File Based Encryption</a></span></dt><dt><span class="section"><a href="#Security_Guide-Encryption-Data_in_Motion">3.4. Data in Motion</a></span></dt><dt><span class="section"><a href="#Security_Guide-Encryption-Data_in_Motion-Virtual_Private_Networks">3.5. Virtual Private Networks</a></span></dt><dt><span class="section"><a href="#Security_Guide-Encryption-D
ata_in_Motion-Secure_Shell">3.6. Secure Shell</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-LUKS_Disk_Encryption">3.7. LUKS Disk Encryption</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-LUKS_Disk_Encryption-LUKS_Implementation_in_Fedora">3.7.1. LUKS Implementation in Fedora</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories">3.7.2. Manually Encrypting Directories</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-Step_by_Step_Instructions">3.7.3. Step-by-Step Instructions</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-What_you_have_just_accomplished">3.7.4. What you have just accomplished.</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-LUKS_Disk_Encryption-Links_of_Interest">
3.7.5. Links of Interest</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives">3.8. 7-Zip Encrypted Archives</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Installation">3.8.1. 7-Zip Installation in Fedora</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Installation-Instructions">3.8.2. Step-by-Step Installation Instructions</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Usage_Instructions">3.8.3. Step-by-Step Usage Instructions</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Things_of_note">3.8.4. Things of note</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Encryption-Using_GPG">3.9. Using GNU Privacy Guard (GnuPG)</a></span></dt><dd><
dl><dt><span class="section"><a href="#sect-Security_Guide-Encryption-Using_GPG-Keys_in_GNOME">3.9.1. Generating GPG Keys in GNOME</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE1">3.9.2. Generating GPG Keys in KDE</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE">3.9.3. Generating GPG Keys Using the Command Line</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Alpine">3.9.4. Using GPG with Alpine</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution">3.9.5. Using GPG with Evolution</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Thunderbird">3.9.6. Using GPG with Thunderbird</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Encryption-Using_G
PG-About_Public_Key_Encryption">3.9.7. About Public Key Encryption</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#chap-Security_Guide-General_Principles_of_Information_Security">4. General Principles of Information Security</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-General_Principles_of_Information_Security-Tips_Guides_and_Tools">4.1. Tips, Guides, and Tools</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Security_Guide-Secure_Installation">5. Secure Installation</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Secure_Installation-Disk_Partitions">5.1. Disk Partitions</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Secure_Installation-Utilize_LUKS_Partition_Encryption">5.2. Utilize LUKS Partition Encryption</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Security_Guide-Software_Maintenance">6. Software Maintenance</a></span></d
t><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Software_Maintenance-Install_Minimal_Software">6.1. Install Minimal Software</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates">6.2. Plan and Configure Security Updates</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates-Adjusting_Automatic_Updates">6.3. Adjusting Automatic Updates</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Software_Maintenance-Install_Signed_Packages_from_Well_Known_Repositories">6.4. Install Signed Packages from Well Known Repositories</a></span></dt></dl></dd><dt><span class="chapter"><a href="#chap-Security_Guide-References">7. References</a></span></dt><dt><span class="appendix"><a href="#chap-Security_Guide-Encryption_Standards">A. Encryption Standards</a></span></dt><dd><dl><dt><span class="section"><a href=
"#id2669437">A.1. Synchronous Encryption</a></span></dt><dd><dl><dt><span class="section"><a href="#id2932167">A.1.1. Advanced Encryption Standard - AES</a></span></dt><dt><span class="section"><a href="#id2691199">A.1.2. Data Encryption Standard - DES</a></span></dt></dl></dd><dt><span class="section"><a href="#id3921677">A.2. Public-key Encryption</a></span></dt><dd><dl><dt><span class="section"><a href="#id2654989">A.2.1. Diffie-Hellman</a></span></dt><dt><span class="section"><a href="#id2623554">A.2.2. RSA</a></span></dt><dt><span class="section"><a href="#id2623563">A.2.3. DSA</a></span></dt><dt><span class="section"><a href="#id2800052">A.2.4. SSL/TLS</a></span></dt><dt><span class="section"><a href="#id3026488">A.2.5. Cramer-Shoup Cryptosystem</a></span></dt><dt><span class="section"><a href="#id2658576">A.2.6. ElGamal Encryption</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="#appe-Publican-Revision_History">B. Revision History</a></span></dt
></dl></div><div xml:lang="en-US" class="preface" title="Preface" id="pref-Security_Guide-Preface" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Preface</h1></div></div></div><div xml:lang="en-US" class="section" title="1. Document Conventions" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id2912980">1. Document Conventions</h2></div></div></div><div class="para">
This manual uses several conventions to highlight certain words and phrases and draw attention to specific pieces of information.
</div><div class="para">
In PDF and paper editions, this manual uses typefaces drawn from the <a href="https://fedorahosted.org/liberation-fonts/">Liberation Fonts</a> set. The Liberation Fonts set is also used in HTML editions if the set is installed on your system. If not, alternative but equivalent typefaces are displayed. Note: Red Hat Enterprise Linux 5 and later includes the Liberation Fonts set by default.
- </div><div class="section" title="1.1. Typographic Conventions"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id3210480">1.1. Typographic Conventions</h3></div></div></div><div class="para">
+ </div><div class="section" title="1.1. Typographic Conventions"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id2753333">1.1. Typographic Conventions</h3></div></div></div><div class="para">
Four typographic conventions are used to call attention to specific words and phrases. These conventions, and the circumstances they apply to, are as follows.
</div><div class="para">
<code class="literal">Mono-spaced Bold</code>
@@ -75,14 +75,12 @@
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">
Publican is a <em class="firstterm">DocBook</em> publishing system.
- </div></blockquote></div></div><div class="section" title="1.2. Pull-quote Conventions"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id3395706">1.2. Pull-quote Conventions</h3></div></div></div><div class="para">
+ </div></blockquote></div></div><div class="section" title="1.2. Pull-quote Conventions"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id2773234">1.2. Pull-quote Conventions</h3></div></div></div><div class="para">
Terminal output and source code listings are set off visually from the surrounding text.
</div><div class="para">
Output sent to a terminal is set in <code class="computeroutput">mono-spaced roman</code> and presented thus:
</div><pre class="screen">books Desktop documentation drafts mss photos stuff svn
-books_tests Desktop1 downloads images notes scripts svgs
-
-</pre><div class="para">
+books_tests Desktop1 downloads images notes scripts svgs</pre><div class="para">
Source-code listings are also set in <code class="computeroutput">mono-spaced roman</code> but add syntax highlighting as follows:
</div><pre class="programlisting">package org.<span class="perl_Function">jboss</span>.<span class="perl_Function">book</span>.<span class="perl_Function">jca</span>.<span class="perl_Function">ex1</span>;
@@ -102,9 +100,7 @@ books_tests Desktop1 downloads images notes scripts svgs
System.<span class="perl_Function">out</span>.<span class="perl_Function">println</span>(<span class="perl_String">"Echo.echo('Hello') = "</span> + echo.<span class="perl_Function">echo</span>(<span class="perl_String">"Hello"</span>));
}
-}
-
-</pre></div><div class="section" title="1.3. Notes and Warnings"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id4396729">1.3. Notes and Warnings</h3></div></div></div><div class="para">
+}</pre></div><div class="section" title="1.3. Notes and Warnings"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id2734741">1.3. Notes and Warnings</h3></div></div></div><div class="para">
Finally, we use three visual styles to draw attention to information that might otherwise be overlooked.
</div><div class="note"><h2>Note</h2><div class="para">
Notes are tips, shortcuts or alternative approaches to the task at hand. Ignoring a note should have no negative consequences, but you might miss out on a trick that makes your life easier.
@@ -112,7 +108,7 @@ books_tests Desktop1 downloads images notes scripts svgs
Important boxes detail things that are easily missed: configuration changes that only apply to the current session, or services that need restarting before an update will apply. Ignoring a box labeled 'Important' won't cause data loss but may cause irritation and frustration.
</div></div><div class="warning"><h2>Warning</h2><div class="para">
Warnings should not be ignored. Ignoring warnings will most likely cause data loss.
- </div></div></div></div><div xml:lang="en-US" class="section" title="2. We Need Feedback!" id="We_Need_Feedback" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2. We Need Feedback!</h2></div></div></div><div class="para">
+ </div></div></div></div><div xml:lang="en-US" class="section" title="2. We Need Feedback!" id="We_Need_Feedback" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="We_Need_Feedback">2. We Need Feedback!</h2></div></div></div><div class="para">
More information about the Linux Security Guide project can be found at <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</a>. Please select the proper component for this guide.
@@ -120,30 +116,30 @@ books_tests Desktop1 downloads images notes scripts svgs
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 postmortem — <span class="emphasis"><em>after</em></span> 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 xml:lang="en-US" class="section" title="1.1. Introduction to Security" id="sect-Security_Guide-Introduction_to_Security" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">1.1. Introduction to Security</h2></div></div></div><div class="section" title="1.1.1. What is Computer Security?" id="sect-Security_Guide-Introduction_to_Security-What_is_Computer_Security"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">1.1.1. What is Computer Security?</h3></div></div></div><div class="para">
+ </div><div xml:lang="en-US" class="section" title="1.1. Introduction to Security" id="sect-Security_Guide-Introduction_to_Security" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sect-Security_Guide-Introduction_to_Security">1.1. Introduction to Security</h2></div></div></div><div class="section" title="1.1.1. What is Computer Security?" id="sect-Security_Guide-Introduction_to_Security-What_is_Computer_Security"><div class="titlepage"><div><div keep-together.within-column="always"><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" title="1.1.1.1. How did Computer Security Come about?" id="sect-Security_Guide-What_is_Computer_Security-How_did_Computer_Security_Come_about"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">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="id3702342" href="#ftn.id3702342" class="footnote">1</a>]</sup>and the Vladimir Levin <sup>[<a id="id3139738" href="#ftn.id3139738" 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="section" title="1.1.1.1. How did Computer Security Come about?" id="sect-Security_Guide-What_is_Computer_Security-How_did_Computer_Security_Come_about"><div class="titlepage"><div><div keep-together.within-column="always"><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="id2789710" href="#ftn.id2789710" class="footnote">1</a>]</sup>and the Vladimir Levin <sup>[<a id="id2987442" href="#ftn.id2987442" 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" title="1.1.1.2. Security Today" id="sect-Security_Guide-What_is_Computer_Security-Security_Today"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">1.1.1.2. Security Today</h4></div></div></div><div class="para">
+ </div></div><div class="section" title="1.1.1.2. Security Today" id="sect-Security_Guide-What_is_Computer_Security-Security_Today"><div class="titlepage"><div><div keep-together.within-column="always"><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="id3298422" href="#ftn.id3298422" class="footnote">3</a>]</sup>
+ 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="id2757494" href="#ftn.id2757494" 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="id3356325" href="#ftn.id3356325" class="footnote">4</a>]</sup>
+ 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="id2659578" href="#ftn.id2659578" class="footnote">4</a>]</sup>
</div><div class="para">
- Currently, an estimated 1.8 billion people use or have used the Internet worldwide.<sup>[<a id="id3175233" href="#ftn.id3175233" class="footnote">5</a>]</sup> At the same time:
+ Currently, an estimated 1.8 billion people use or have used the Internet worldwide.<sup>[<a id="id2901813" href="#ftn.id2901813" class="footnote">5</a>]</sup> At the same time:
</div><div class="itemizedlist"><ul><li class="listitem"><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="id4384302" href="#ftn.id4384302" class="footnote">6</a>]</sup>
+ 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="id2642354" href="#ftn.id2642354" class="footnote">6</a>]</sup>
</div></li><li class="listitem"><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="id3374746" href="#ftn.id3374746" class="footnote">7</a>]</sup>
+ 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="id3008146" href="#ftn.id3008146" class="footnote">7</a>]</sup>
</div></li><li class="listitem"><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="id3310449" href="#ftn.id3310449" class="footnote">8</a>]</sup>
+ 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="id2912597" href="#ftn.id2912597" 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="id3410877" href="#ftn.id3410877" class="footnote">9</a>]</sup>, undertaken by <span class="emphasis"><em>CIO Magazine</em></span>, some points are:
+ From a 2008 global survey of business and technology executives "The Global State of Information Security"<sup>[<a id="id3917573" href="#ftn.id3917573" class="footnote">9</a>]</sup>, undertaken by <span class="emphasis"><em>CIO Magazine</em></span>, some points are:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
Just 43% of respondents audit or monitor user compliance with security policies
</div></li><li class="listitem"><div class="para">
@@ -158,7 +154,7 @@ books_tests Desktop1 downloads images notes scripts svgs
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" title="1.1.1.3. Standardizing Security" id="sect-Security_Guide-What_is_Computer_Security-Standardizing_Security"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">1.1.1.3. Standardizing Security</h4></div></div></div><div class="para">
+ </div></div><div class="section" title="1.1.1.3. Standardizing Security" id="sect-Security_Guide-What_is_Computer_Security-Standardizing_Security"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><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.
@@ -166,9 +162,9 @@ books_tests Desktop1 downloads images notes scripts svgs
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 class="listitem"><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" title="1.1.2. SELinux" id="sect-Security_Guide-Introduction_to_Security-SELinux"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">1.1.2. SELinux</h3></div></div></div><div class="para">
+ </div></li></ul></div></div></div><div class="section" title="1.1.2. SELinux" id="sect-Security_Guide-Introduction_to_Security-SELinux"><div class="titlepage"><div><div keep-together.within-column="always"><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/">http://docs.fedoraproject.org/</a>. For more information on configuring and running services in Fedora that are protected by SELinux, refer to the SELinux Managing Confined Services Guide available at <a href="http://docs.fedoraproject.org">http://docs.fedoraproject.org/</a>. Other available resources for SELinux are listed in <a class="xref" href="#chap-Security_Guide-References" title="Chapter 7. References">Chapter 7, <i>References</i></a>.
- </div></div><div class="section" title="1.1.3. Security Controls" id="sect-Security_Guide-Introduction_to_Security-Security_Controls"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">1.1.3. Security Controls</h3></div></div></div><div class="para">
+ </div></div><div class="section" title="1.1.3. Security Controls" id="sect-Security_Guide-Introduction_to_Security-Security_Controls"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><div class="para">
Physical
@@ -178,7 +174,7 @@ books_tests Desktop1 downloads images notes scripts svgs
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" title="1.1.3.1. Physical Controls" id="sect-Security_Guide-Security_Controls-Physical_Controls"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">1.1.3.1. Physical Controls</h4></div></div></div><div class="para">
+ </div><div class="section" title="1.1.3.1. Physical Controls" id="sect-Security_Guide-Security_Controls-Physical_Controls"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><div class="para">
Closed-circuit surveillance cameras
@@ -192,7 +188,7 @@ books_tests Desktop1 downloads images notes scripts svgs
Locked and dead-bolted steel doors
</div></li><li class="listitem"><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" title="1.1.3.2. Technical Controls" id="sect-Security_Guide-Security_Controls-Technical_Controls"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">1.1.3.2. Technical Controls</h4></div></div></div><div class="para">
+ </div></li></ul></div></div><div class="section" title="1.1.3.2. Technical Controls" id="sect-Security_Guide-Security_Controls-Technical_Controls"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><div class="para">
Encryption
@@ -204,7 +200,7 @@ books_tests Desktop1 downloads images notes scripts svgs
Access control lists (ACLs)
</div></li><li class="listitem"><div class="para">
File integrity auditing software
- </div></li></ul></div></div><div class="section" title="1.1.3.3. Administrative Controls" id="sect-Security_Guide-Security_Controls-Administrative_Controls"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">1.1.3.3. Administrative Controls</h4></div></div></div><div class="para">
+ </div></li></ul></div></div><div class="section" title="1.1.3.3. Administrative Controls" id="sect-Security_Guide-Security_Controls-Administrative_Controls"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><div class="para">
Training and awareness
@@ -214,9 +210,9 @@ books_tests Desktop1 downloads images notes scripts svgs
Personnel recruitment and separation strategies
</div></li><li class="listitem"><div class="para">
Personnel registration and accounting
- </div></li></ul></div></div></div><div class="section" title="1.1.4. Conclusion" id="sect-Security_Guide-Introduction_to_Security-Conclusion"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">1.1.4. Conclusion</h3></div></div></div><div class="para">
+ </div></li></ul></div></div></div><div class="section" title="1.1.4. Conclusion" id="sect-Security_Guide-Introduction_to_Security-Conclusion"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Introduction_to_Security-Conclusion">1.1.4. Conclusion</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 xml:lang="en-US" class="section" title="1.2. Vulnerability Assessment" id="sect-Security_Guide-Vulnerability_Assessment" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">1.2. Vulnerability Assessment</h2></div></div></div><div class="para">
+ </div></div></div><div xml:lang="en-US" class="section" title="1.2. Vulnerability Assessment" id="sect-Security_Guide-Vulnerability_Assessment" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><div class="para">
The expertise of the staff responsible for configuring, monitoring, and maintaining the technologies.
@@ -226,7 +222,7 @@ books_tests Desktop1 downloads images notes scripts svgs
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" title="1.2.1. Thinking Like the Enemy" id="sect-Security_Guide-Vulnerability_Assessment-Thinking_Like_the_Enemy"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">1.2.1. Thinking Like the Enemy</h3></div></div></div><div class="para">
+ </div><div class="section" title="1.2.1. Thinking Like the Enemy" id="sect-Security_Guide-Vulnerability_Assessment-Thinking_Like_the_Enemy"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Vulnerability_Assessment-Thinking_Like_the_Enemy">1.2.1. Thinking Like the Enemy</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.
@@ -236,7 +232,7 @@ books_tests Desktop1 downloads images notes scripts svgs
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="#sect-Security_Guide-What_is_Computer_Security-Standardizing_Security" title="1.1.1.3. Standardizing Security">Section 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 class="section" title="1.2.2. Defining Assessment and Testing" id="sect-Security_Guide-Vulnerability_Assessment-Defining_Assessment_and_Testing"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">1.2.2. Defining Assessment and Testing</h3></div></div></div><div class="para">
+ </div></div><div class="section" title="1.2.2. Defining Assessment and Testing" id="sect-Security_Guide-Vulnerability_Assessment-Defining_Assessment_and_Testing"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Vulnerability_Assessment-Defining_Assessment_and_Testing">1.2.2. Defining Assessment and Testing</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.
@@ -266,7 +262,7 @@ books_tests Desktop1 downloads images notes scripts svgs
Promotes growth and aids in developing staff expertise
</div></li><li class="listitem"><div class="para">
Abates financial loss and negative publicity
- </div></li></ul></div><div class="section" title="1.2.2.1. Establishing a Methodology" id="sect-Security_Guide-Defining_Assessment_and_Testing-Establishing_a_Methodology"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">1.2.2.1. Establishing a Methodology</h4></div></div></div><div class="para">
+ </div></li></ul></div><div class="section" title="1.2.2.1. Establishing a Methodology" id="sect-Security_Guide-Defining_Assessment_and_Testing-Establishing_a_Methodology"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Defining_Assessment_and_Testing-Establishing_a_Methodology">1.2.2.1. Establishing a Methodology</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.
@@ -276,7 +272,7 @@ books_tests Desktop1 downloads images notes scripts svgs
<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 class="listitem"><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><div class="section" title="1.2.3. Evaluating the Tools" id="sect-Security_Guide-Vulnerability_Assessment-Evaluating_the_Tools"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">1.2.3. Evaluating the Tools</h3></div></div></div><div class="para">
+ </div></li></ul></div></div></div><div class="section" title="1.2.3. Evaluating the Tools" id="sect-Security_Guide-Vulnerability_Assessment-Evaluating_the_Tools"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Vulnerability_Assessment-Evaluating_the_Tools">1.2.3. Evaluating the Tools</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.
@@ -284,14 +280,13 @@ books_tests Desktop1 downloads images notes scripts svgs
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" title="1.2.3.1. Scanning Hosts with Nmap" id="sect-Security_Guide-Evaluating_the_Tools-Scanning_Hosts_with_Nmap"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">1.2.3.1. Scanning Hosts with Nmap</h4></div></div></div><div class="para">
+ </div><div class="section" title="1.2.3.1. Scanning Hosts with Nmap" id="sect-Security_Guide-Evaluating_the_Tools-Scanning_Hosts_with_Nmap"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Evaluating_the_Tools-Scanning_Hosts_with_Nmap">1.2.3.1. Scanning Hosts with 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" title="1.2.3.1.1. Using Nmap" id="sect-Security_Guide-Scanning_Hosts_with_Nmap-Using_Nmap"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">1.2.3.1.1. Using Nmap</h5></div></div></div><div class="para">
+ </div><div class="section" title="1.2.3.1.1. Using Nmap" id="sect-Security_Guide-Scanning_Hosts_with_Nmap-Using_Nmap"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-Security_Guide-Scanning_Hosts_with_Nmap-Using_Nmap">1.2.3.1.1. Using 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">
+ </div><pre class="screen"><code class="command">nmap foo.example.com</code></pre><div class="para">
The results of a basic scan (which could take up to a few minutes, depending on where the host is located and other network conditions) should look similar to the following:
</div><pre class="screen">
Starting Nmap 4.68 ( http://nmap.org )
@@ -302,14 +297,13 @@ PORT STATE SERVICE
53/tcp open domain
70/tcp closed gopher
80/tcp open http
-113/tcp closed auth
-</pre><div class="para">
+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 class="section" title="1.2.3.2. Nessus" id="sect-Security_Guide-Evaluating_the_Tools-Nessus"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">1.2.3.2. Nessus</h4></div></div></div><div class="para">
+ </div></div></div><div class="section" title="1.2.3.2. Nessus" id="sect-Security_Guide-Evaluating_the_Tools-Nessus"><div class="titlepage"><div><div keep-together.within-column="always"><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">
The Nessus client and server software is included in Fedora repositories but requires a subscription to use. It has been included in this document as a reference to users who may be interested in using this popular application.
@@ -317,13 +311,13 @@ PORT STATE SERVICE
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><div class="section" title="1.2.3.3. Nikto" id="sect-Security_Guide-Evaluating_the_Tools-Nikto"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">1.2.3.3. Nikto</h4></div></div></div><div class="para">
+ </div></div><div class="section" title="1.2.3.3. Nikto" id="sect-Security_Guide-Evaluating_the_Tools-Nikto"><div class="titlepage"><div><div keep-together.within-column="always"><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="para">
More information about Nikto can be found at the following URL:
</div><div class="para">
<a href="http://www.cirt.net/code/nikto.shtml">http://www.cirt.net/code/nikto.shtml</a>
- </div></div><div class="section" title="1.2.3.4. VLAD the Scanner" id="sect-Security_Guide-Evaluating_the_Tools-VLAD_the_Scanner"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">1.2.3.4. VLAD the Scanner</h4></div></div></div><div class="para">
+ </div></div><div class="section" title="1.2.3.4. VLAD the Scanner" id="sect-Security_Guide-Evaluating_the_Tools-VLAD_the_Scanner"><div class="titlepage"><div><div keep-together.within-column="always"><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.
@@ -331,17 +325,17 @@ PORT STATE SERVICE
More information about VLAD can be found on the RAZOR team website at the following URL:
</div><div class="para">
<a href="http://www.bindview.com/Support/Razor/Utilities/">http://www.bindview.com/Support/Razor/Utilities/</a>
- </div></div><div class="section" title="1.2.3.5. Anticipating Your Future Needs" id="sect-Security_Guide-Evaluating_the_Tools-Anticipating_Your_Future_Needs"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">1.2.3.5. Anticipating Your Future Needs</h4></div></div></div><div class="para">
+ </div></div><div class="section" title="1.2.3.5. Anticipating Your Future Needs" id="sect-Security_Guide-Evaluating_the_Tools-Anticipating_Your_Future_Needs"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Evaluating_the_Tools-Anticipating_Your_Future_Needs">1.2.3.5. Anticipating Your Future Needs</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></div></div><div xml:lang="en-US" class="section" title="1.3. Attackers and Vulnerabilities" id="sect-Security_Guide-Attackers_and_Vulnerabilities" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">1.3. Attackers and Vulnerabilities</h2></div></div></div><div class="para">
+ </div></div></div></div><div xml:lang="en-US" class="section" title="1.3. Attackers and Vulnerabilities" id="sect-Security_Guide-Attackers_and_Vulnerabilities" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><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" title="1.3.1. A Quick History of Hackers" id="sect-Security_Guide-Attackers_and_Vulnerabilities-A_Quick_History_of_Hackers"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">1.3.1. A Quick History of Hackers</h3></div></div></div><div class="para">
+ </div><div class="section" title="1.3.1. A Quick History of Hackers" id="sect-Security_Guide-Attackers_and_Vulnerabilities-A_Quick_History_of_Hackers"><div class="titlepage"><div><div keep-together.within-column="always"><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" title="1.3.1.1. Shades of Gray" id="sect-Security_Guide-A_Quick_History_of_Hackers-Shades_of_Gray"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">1.3.1.1. Shades of Gray</h4></div></div></div><div class="para">
+ </div><div class="section" title="1.3.1.1. Shades of Gray" id="sect-Security_Guide-A_Quick_History_of_Hackers-Shades_of_Gray"><div class="titlepage"><div><div keep-together.within-column="always"><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.
@@ -353,21 +347,21 @@ PORT STATE SERVICE
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 class="section" title="1.3.2. Threats to Network Security" id="sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Network_Security"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">1.3.2. Threats to Network Security</h3></div></div></div><div class="para">
+ </div></div></div><div class="section" title="1.3.2. Threats to Network Security" id="sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Network_Security"><div class="titlepage"><div><div keep-together.within-column="always"><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" title="1.3.2.1. Insecure Architectures" id="sect-Security_Guide-Threats_to_Network_Security-Insecure_Architectures"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">1.3.2.1. Insecure Architectures</h4></div></div></div><div class="para">
+ </div><div class="section" title="1.3.2.1. Insecure Architectures" id="sect-Security_Guide-Threats_to_Network_Security-Insecure_Architectures"><div class="titlepage"><div><div keep-together.within-column="always"><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" title="1.3.2.1.1. Broadcast Networks" id="sect-Security_Guide-Insecure_Architectures-Broadcast_Networks"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">1.3.2.1.1. Broadcast Networks</h5></div></div></div><div class="para">
+ </div><div class="section" title="1.3.2.1.1. Broadcast Networks" id="sect-Security_Guide-Insecure_Architectures-Broadcast_Networks"><div class="titlepage"><div><div keep-together.within-column="always"><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" title="1.3.2.1.2. Centralized Servers" id="sect-Security_Guide-Insecure_Architectures-Centralized_Servers"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">1.3.2.1.2. Centralized Servers</h5></div></div></div><div class="para">
+ </div></div><div class="section" title="1.3.2.1.2. Centralized Servers" id="sect-Security_Guide-Insecure_Architectures-Centralized_Servers"><div class="titlepage"><div><div keep-together.within-column="always"><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><div class="section" title="1.3.3. Threats to Server Security" id="sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Server_Security"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">1.3.3. Threats to Server Security</h3></div></div></div><div class="para">
+ </div></div></div></div><div class="section" title="1.3.3. Threats to Server Security" id="sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Server_Security"><div class="titlepage"><div><div keep-together.within-column="always"><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" title="1.3.3.1. Unused Services and Open Ports" id="sect-Security_Guide-Threats_to_Server_Security-Unused_Services_and_Open_Ports"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">1.3.3.1. Unused Services and Open Ports</h4></div></div></div><div class="para">
+ </div><div class="section" title="1.3.3.1. Unused Services and Open Ports" id="sect-Security_Guide-Threats_to_Server_Security-Unused_Services_and_Open_Ports"><div class="titlepage"><div><div keep-together.within-column="always"><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" title="2.2. Server Security">Section 2.2, “Server Securityâ€</a> for information on closing ports and disabling unused services.
- </div></div><div class="section" title="1.3.3.2. Unpatched Services" id="sect-Security_Guide-Threats_to_Server_Security-Unpatched_Services"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">1.3.3.2. Unpatched Services</h4></div></div></div><div class="para">
+ </div></div><div class="section" title="1.3.3.2. Unpatched Services" id="sect-Security_Guide-Threats_to_Server_Security-Unpatched_Services"><div class="titlepage"><div><div keep-together.within-column="always"><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.
@@ -375,11 +369,11 @@ PORT STATE SERVICE
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" title="1.5. Security Updates">Section 1.5, “Security Updatesâ€</a> for more information about keeping a system up-to-date.
- </div></div><div class="section" title="1.3.3.3. Inattentive Administration" id="sect-Security_Guide-Threats_to_Server_Security-Inattentive_Administration"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">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="id3354839" href="#ftn.id3354839" class="footnote">10</a>]</sup> This applies as much to inexperienced administrators as it does to overconfident or amotivated administrators.
+ </div></div><div class="section" title="1.3.3.3. Inattentive Administration" id="sect-Security_Guide-Threats_to_Server_Security-Inattentive_Administration"><div class="titlepage"><div><div keep-together.within-column="always"><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="id2780094" href="#ftn.id2780094" 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><div class="section" title="1.3.3.4. Inherently Insecure Services" id="sect-Security_Guide-Threats_to_Server_Security-Inherently_Insecure_Services"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">1.3.3.4. Inherently Insecure Services</h4></div></div></div><div class="para">
+ </div></div><div class="section" title="1.3.3.4. Inherently Insecure Services" id="sect-Security_Guide-Threats_to_Server_Security-Inherently_Insecure_Services"><div class="titlepage"><div><div keep-together.within-column="always"><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.
@@ -389,19 +383,19 @@ PORT STATE SERVICE
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" title="2.2. Server Security">Section 2.2, “Server Securityâ€</a> for more information about setting up services in a safe manner.
- </div></div></div><div class="section" title="1.3.4. Threats to Workstation and Home PC Security" id="sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Workstation_and_Home_PC_Security"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">1.3.4. Threats to Workstation and Home PC Security</h3></div></div></div><div class="para">
+ </div></div></div><div class="section" title="1.3.4. Threats to Workstation and Home PC Security" id="sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Workstation_and_Home_PC_Security"><div class="titlepage"><div><div keep-together.within-column="always"><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" title="1.3.4.1. Bad Passwords" id="sect-Security_Guide-Threats_to_Workstation_and_Home_PC_Security-Bad_Passwords"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">1.3.4.1. Bad Passwords</h4></div></div></div><div class="para">
+ </div><div class="section" title="1.3.4.1. Bad Passwords" id="sect-Security_Guide-Threats_to_Workstation_and_Home_PC_Security-Bad_Passwords"><div class="titlepage"><div><div keep-together.within-column="always"><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="#sect-Security_Guide-Workstation_Security-Password_Security" title="2.1.3. Password Security">Section 2.1.3, “Password Securityâ€</a>.
- </div></div><div class="section" title="1.3.4.2. Vulnerable Client Applications" id="sect-Security_Guide-Threats_to_Workstation_and_Home_PC_Security-Vulnerable_Client_Applications"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">1.3.4.2. Vulnerable Client Applications</h4></div></div></div><div class="para">
+ </div></div><div class="section" title="1.3.4.2. Vulnerable Client Applications" id="sect-Security_Guide-Threats_to_Workstation_and_Home_PC_Security-Vulnerable_Client_Applications"><div class="titlepage"><div><div keep-together.within-column="always"><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="#sect-Security_Guide-Workstation_Security" title="2.1. Workstation Security">Section 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></div></div><div xml:lang="en-US" class="section" title="1.4. Common Exploits and Attacks" id="sect-Security_Guide-Common_Exploits_and_Attacks" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">1.4. Common Exploits and Attacks</h2></div></div></div><div class="para">
+ </div></div></div></div><div xml:lang="en-US" class="section" title="1.4. Common Exploits and Attacks" id="sect-Security_Guide-Common_Exploits_and_Attacks" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sect-Security_Guide-Common_Exploits_and_Attacks">1.4. Common Exploits and Attacks</h2></div></div></div><div class="para">
<a class="xref" href="#tabl-Security_Guide-Common_Exploits_and_Attacks-Common_Exploits" title="Table 1.1. Common Exploits">Table 1.1, “Common Exploitsâ€</a> details some of the most common exploits and entry points used by intruders to access organizational network resources. Key to these common exploits are the explanations of how they are performed and how administrators can properly safeguard their network against such attacks.
- </div><div class="table"><div class="table-contents"><table summary="Common Exploits" border="1"><colgroup><col width="20%" /><col width="40%" /><col width="40%" /></colgroup><thead><tr><th>
+ </div><div class="table" title="Table 1.1. Common Exploits" id="tabl-Security_Guide-Common_Exploits_and_Attacks-Common_Exploits"><div class="table-contents"><table summary="Common Exploits" border="1"><colgroup><col width="20%" /><col width="40%" /><col width="40%" /></colgroup><thead><tr><th>
Exploit
</th><th>
Description
@@ -456,55 +450,47 @@ PORT STATE SERVICE
</td><td>
<table border="0" summary="Simple list" class="simplelist"><tr><td> The most reported DoS case in the US occurred in 2000. Several highly-trafficked commercial and government sites were rendered unavailable by a coordinated ping flood attack using several compromised systems with high bandwidth connections acting as <em class="firstterm">zombies</em>, or redirected broadcast nodes. </td></tr><tr><td> Source packets are usually forged (as well as rebroadcasted), making investigation as to the true source of the attack difficult. </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>Table 1.1. Common Exploits</h6></div><br class="table-break" /></div><div xml:lang="en-US" class="section" title="1.5. Security Updates" id="sect-Security_Guide-Security_Updates" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">1.5. Security Updates</h2></div></div></div><div class="para">
+ </td></tr></tbody></table></div><h6>Table 1.1. Common Exploits</h6></div><br class="table-break" /></div><div xml:lang="en-US" class="section" title="1.5. Security Updates" id="sect-Security_Guide-Security_Updates" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sect-Security_Guide-Security_Updates">1.5. Security Updates</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" title="1.5.1. Updating Packages" id="sect-Security_Guide-Security_Updates-Updating_Packages"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">1.5.1. Updating Packages</h3></div></div></div><div class="para">
+ </div><div class="section" title="1.5.1. Updating Packages" id="sect-Security_Guide-Security_Updates-Updating_Packages"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="section" title="1.5.2. Verifying Signed Packages" id="sect-Security_Guide-Updating_Packages-Verifying_Signed_Packages"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">1.5.2. Verifying Signed Packages</h3></div></div></div><div class="para">
+ </div></div></div><div class="section" title="1.5.2. Verifying Signed Packages" id="sect-Security_Guide-Updating_Packages-Verifying_Signed_Packages"><div class="titlepage"><div><div keep-together.within-column="always"><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">
+ </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">
+ </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">
+ </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">
+ </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">
+ </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><div class="section" title="1.5.3. Installing Signed Packages" id="sect-Security_Guide-Updating_Packages-Installing_Signed_Packages"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">1.5.3. Installing Signed Packages</h3></div></div></div><div class="para">
+ </div></div><div class="section" title="1.5.3. Installing Signed Packages" id="sect-Security_Guide-Updating_Packages-Installing_Signed_Packages"><div class="titlepage"><div><div keep-together.within-column="always"><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">
+ </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">
+ </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">
+ </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" title="1.5.4. Applying the Changes">Section 1.5.4, “Applying the Changesâ€</a> for general instructions about applying the changes made by an errata update.
- </div></div></div><div class="section" title="1.5.4. Applying the Changes" id="sect-Security_Guide-Updating_Packages-Applying_the_Changes"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">1.5.4. Applying the Changes</h3></div></div></div><div class="para">
+ </div></div></div><div class="section" title="1.5.4. Applying the Changes" id="sect-Security_Guide-Updating_Packages-Applying_the_Changes"><div class="titlepage"><div><div keep-together.within-column="always"><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.
@@ -520,15 +506,13 @@ PORT STATE SERVICE
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">
+ </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">SysV Services</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><service-name></code></em> restart</code>
-</pre><div class="para">
+ </div><pre class="screen"><code class="command">/sbin/service <em class="replaceable"><code><service-name></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"><code class="command">xinetd</code> Services</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.
@@ -538,41 +522,37 @@ PORT STATE SERVICE
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">
+ </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">
+ </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">
+ </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></div><div class="footnotes"><br /><hr width="100" align="left" /><div class="footnote"><p><sup>[<a id="ftn.id3702342" href="#id3702342" class="para">1</a>] </sup>
+ </div><pre class="screen"><code class="command">killall imapd</code></pre></dd></dl></div></div></div><div class="footnotes"><br /><hr width="100" align="left" /><div class="footnote"><p><sup>[<a id="ftn.id2789710" href="#id2789710" 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.id3139738" href="#id3139738" class="para">2</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id2987442" href="#id2987442" class="para">2</a>] </sup>
http://www.livinginternet.com/i/ia_hackers_levin.htm
- </p></div><div class="footnote"><p><sup>[<a id="ftn.id3298422" href="#id3298422" class="para">3</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id2757494" href="#id2757494" 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.id3356325" href="#id3356325" class="para">4</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id2659578" href="#id2659578" class="para">4</a>] </sup>
http://www.healthcareitnews.com/story.cms?id=9408
- </p></div><div class="footnote"><p><sup>[<a id="ftn.id3175233" href="#id3175233" class="para">5</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id2901813" href="#id2901813" class="para">5</a>] </sup>
http://www.internetworldstats.com/stats.htm
- </p></div><div class="footnote"><p><sup>[<a id="ftn.id4384302" href="#id4384302" class="para">6</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id2642354" href="#id2642354" class="para">6</a>] </sup>
http://www.cert.org
- </p></div><div class="footnote"><p><sup>[<a id="ftn.id3374746" href="#id3374746" class="para">7</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id3008146" href="#id3008146" class="para">7</a>] </sup>
http://www.cert.org/stats/fullstats.html
- </p></div><div class="footnote"><p><sup>[<a id="ftn.id3310449" href="#id3310449" class="para">8</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id2912597" href="#id2912597" class="para">8</a>] </sup>
http://www.newsfactor.com/perl/story/16407.html
- </p></div><div class="footnote"><p><sup>[<a id="ftn.id3410877" href="#id3410877" class="para">9</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id3917573" href="#id3917573" class="para">9</a>] </sup>
http://www.csoonline.com/article/454939/The_Global_State_of_Information_Security_
- </p></div><div class="footnote"><p><sup>[<a id="ftn.id3354839" href="#id3354839" class="para">10</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id2780094" href="#id2780094" class="para">10</a>] </sup>
http://www.sans.org/resources/errors.php
- </p></div></div></div><div xml:lang="en-US" class="chapter" title="Chapter 2. Securing Your Network" id="chap-Security_Guide-Securing_Your_Network" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 2. Securing Your Network</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Security_Guide-Workstation_Security">2.1. Workstation Security</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Workstation_Security-Evaluating_Workstation_Security">2.1.1. Evaluating Workstation Security</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Workstation_Security-BIOS_and_Boot_Loader_Security">2.1.2. BIOS and Boot Loader Security</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Workstation_Security-Password_Security">2.1.3. Password Security</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Workstation_Security-Administrative_Controls">2.1.
4. Administrative Controls</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Workstation_Security-Available_Network_Services">2.1.5. Available Network Services</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Workstation_Security-Personal_Firewalls">2.1.6. Personal Firewalls</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Workstation_Security-Security_Enhanced_Communication_Tools">2.1.7. Security Enhanced Communication Tools</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Server_Security">2.2. Server Security</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Server_Security-Securing_Services_With_TCP_Wrappers_and_xinetd">2.2.1. Securing Services With TCP Wrappers and xinetd</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Server_Security-Securing_Portmap">2.2.2. Securing Portmap</a></span></dt><dt><span class="section"><a href=
"#sect-Security_Guide-Server_Security-Securing_NIS">2.2.3. Securing NIS</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Server_Security-Securing_NFS">2.2.4. Securing NFS</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Server_Security-Securing_the_Apache_HTTP_Server">2.2.5. Securing the Apache HTTP Server</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Server_Security-Securing_FTP">2.2.6. Securing FTP</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Server_Security-Securing_Sendmail">2.2.7. Securing Sendmail</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Server_Security-Verifying_Which_Ports_Are_Listening">2.2.8. Verifying Which Ports Are Listening</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Single_Sign_on_SSO">2.3. Single Sign-on (SSO)</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Single_Sign_
on_SSO-Introduction">2.3.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Single_Sign_on_SSO-Getting_Started_with_your_new_Smart_Card">2.3.2. Getting Started with your new Smart Card</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Enrollment_Works">2.3.3. How Smart Card Enrollment Works</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Login_Works">2.3.4. How Smart Card Login Works</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Single_Sign_on_SSO-Configuring_Firefox_to_use_Kerberos_for_SSO">2.3.5. Configuring Firefox to use Kerberos for SSO</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Pluggable_Authentication_Modules_PAM">2.4. Pluggable Authentication Modules (PAM)</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Pluggable_Authentication_M
odules_PAM-Advantages_of_PAM">2.4.1. Advantages of PAM</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_Files">2.4.2. PAM Configuration Files</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_File_Format">2.4.3. PAM Configuration File Format</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Sample_PAM_Configuration_Files">2.4.4. Sample PAM Configuration Files</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Creating_PAM_Modules">2.4.5. Creating PAM Modules</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Administrative_Credential_Caching">2.4.6. PAM and Administrative Credential Caching</a></span></dt><dt><span class="section"><a href="#sect-Se
curity_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Device_Ownership">2.4.7. PAM and Device Ownership</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Additional_Resources">2.4.8. Additional Resources</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-TCP_Wrappers_and_xinetd">2.5. TCP Wrappers and xinetd</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers">2.5.1. TCP Wrappers</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers_Configuration_Files">2.5.2. TCP Wrappers Configuration Files</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd">2.5.3. xinetd</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd_Configuration_Files">2.5.4. xinetd Configuration Files</a></spa
n></dt><dt><span class="section"><a href="#sect-Security_Guide-TCP_Wrappers_and_xinetd-Additional_Resources">2.5.5. Additional Resources</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Kerberos">2.6. Kerberos</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-What_is_Kerberos">2.6.1. What is Kerberos?</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-Kerberos_Terminology">2.6.2. Kerberos Terminology</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-How_Kerberos_Works">2.6.3. How Kerberos Works</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-Kerberos_and_PAM">2.6.4. Kerberos and PAM</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Server">2.6.5. Configuring a Kerberos 5 Server</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-Config
uring_a_Kerberos_5_Client">2.6.6. Configuring a Kerberos 5 Client</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-Domain_to_Realm_Mapping">2.6.7. Domain-to-Realm Mapping</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-Setting_Up_Secondary_KDCs">2.6.8. Setting Up Secondary KDCs</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-Setting_Up_Cross_Realm_Authentication">2.6.9. Setting Up Cross Realm Authentication</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-Additional_Resources">2.6.10. Additional Resources</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Virtual_Private_Networks_VPNs">2.7. Virtual Private Networks (VPNs)</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Virtual_Private_Networks_VPNs-How_Does_a_VPN_Work">2.7.1. How Does a VPN Work?</a></span></dt><dt><span class="section"><a h
ref="#sect-Security_Guide-Virtual_Private_Networks_VPNs-VPNs_and_PROD">2.7.2. VPNs and Fedora</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec">2.7.3. IPsec</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Virtual_Private_Networks_VPNs-Creating_an_IPsec_Connection">2.7.4. Creating an <abbr class="abbrev">IPsec</abbr> Connection</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Installation">2.7.5. IPsec Installation</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Host_to_Host_Configuration">2.7.6. IPsec Host-to-Host Configuration</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Network_to_Network_Configuration">2.7.7. IPsec Network-to-Network Configuration</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide
-Virtual_Private_Networks_VPNs-Starting_and_Stopping_an_IPsec_Connection">2.7.8. Starting and Stopping an <abbr class="abbrev">IPsec</abbr> Connection</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Firewalls">2.8. Firewalls</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Firewalls-Netfilter_and_IPTables">2.8.1. Netfilter and IPTables</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Firewalls-Basic_Firewall_Configuration">2.8.2. Basic Firewall Configuration</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Firewalls-Using_IPTables">2.8.3. Using IPTables</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Firewalls-Common_IPTables_Filtering">2.8.4. Common IPTables Filtering</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Firewalls-FORWARD_and_NAT_Rules">2.8.5. <code class="computeroutput">FORWARD</code> and <acronym class="acrony
m">NAT</acronym> Rules</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Firewalls-Malicious_Software_and_Spoofed_IP_Addresses">2.8.6. Malicious Software and Spoofed IP Addresses</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Firewalls-IPTables_and_Connection_Tracking">2.8.7. IPTables and Connection Tracking</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Firewalls-IPv6">2.8.8. IPv6</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Firewalls-Additional_Resources">2.8.9. Additional Resources</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-IPTables">2.9. IPTables</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-IPTables-Packet_Filtering">2.9.1. Packet Filtering</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-IPTables-Command_Options_for_IPTables">2.9.2. Command Options for IPTables</a></span></dt><dt><spa
n class="section"><a href="#sect-Security_Guide-IPTables-Saving_IPTables_Rules">2.9.3. Saving IPTables Rules</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-IPTables-IPTables_Control_Scripts">2.9.4. IPTables Control Scripts</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-IPTables-IPTables_and_IPv6">2.9.5. IPTables and IPv6</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-IPTables-Additional_Resources">2.9.6. Additional Resources</a></span></dt></dl></dd></dl></div><div xml:lang="en-US" class="section" title="2.1. Workstation Security" id="sect-Security_Guide-Workstation_Security" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.1. Workstation Security</h2></div></div></div><div class="para">
+ </p></div></div></div><div xml:lang="en-US" class="chapter" title="Chapter 2. Securing Your Network" id="chap-Security_Guide-Securing_Your_Network" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 2. Securing Your Network</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Security_Guide-Workstation_Security">2.1. Workstation Security</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Workstation_Security-Evaluating_Workstation_Security">2.1.1. Evaluating Workstation Security</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Workstation_Security-BIOS_and_Boot_Loader_Security">2.1.2. BIOS and Boot Loader Security</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Workstation_Security-Password_Security">2.1.3. Password Security</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Workstation_Security-Administrative_Controls">2.1.
4. Administrative Controls</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Workstation_Security-Available_Network_Services">2.1.5. Available Network Services</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Workstation_Security-Personal_Firewalls">2.1.6. Personal Firewalls</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Workstation_Security-Security_Enhanced_Communication_Tools">2.1.7. Security Enhanced Communication Tools</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Server_Security">2.2. Server Security</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Server_Security-Securing_Services_With_TCP_Wrappers_and_xinetd">2.2.1. Securing Services With TCP Wrappers and xinetd</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Server_Security-Securing_Portmap">2.2.2. Securing Portmap</a></span></dt><dt><span class="section"><a href=
"#sect-Security_Guide-Server_Security-Securing_NIS">2.2.3. Securing NIS</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Server_Security-Securing_NFS">2.2.4. Securing NFS</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Server_Security-Securing_the_Apache_HTTP_Server">2.2.5. Securing the Apache HTTP Server</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Server_Security-Securing_FTP">2.2.6. Securing FTP</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Server_Security-Securing_Sendmail">2.2.7. Securing Sendmail</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Server_Security-Verifying_Which_Ports_Are_Listening">2.2.8. Verifying Which Ports Are Listening</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Single_Sign_on_SSO">2.3. Single Sign-on (SSO)</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Single_Sign_
on_SSO-Introduction">2.3.1. Introduction</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Single_Sign_on_SSO-Getting_Started_with_your_new_Smart_Card">2.3.2. Getting Started with your new Smart Card</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Enrollment_Works">2.3.3. How Smart Card Enrollment Works</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Login_Works">2.3.4. How Smart Card Login Works</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Single_Sign_on_SSO-Configuring_Firefox_to_use_Kerberos_for_SSO">2.3.5. Configuring Firefox to use Kerberos for SSO</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Pluggable_Authentication_Modules_PAM">2.4. Pluggable Authentication Modules (PAM)</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Pluggable_Authentication_M
odules_PAM-Advantages_of_PAM">2.4.1. Advantages of PAM</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_Files">2.4.2. PAM Configuration Files</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_File_Format">2.4.3. PAM Configuration File Format</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Sample_PAM_Configuration_Files">2.4.4. Sample PAM Configuration Files</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Creating_PAM_Modules">2.4.5. Creating PAM Modules</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Administrative_Credential_Caching">2.4.6. PAM and Administrative Credential Caching</a></span></dt><dt><span class="section"><a href="#sect-Se
curity_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Device_Ownership">2.4.7. PAM and Device Ownership</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Additional_Resources">2.4.8. Additional Resources</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-TCP_Wrappers_and_xinetd">2.5. TCP Wrappers and xinetd</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers">2.5.1. TCP Wrappers</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers_Configuration_Files">2.5.2. TCP Wrappers Configuration Files</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd">2.5.3. xinetd</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd_Configuration_Files">2.5.4. xinetd Configuration Files</a></spa
n></dt><dt><span class="section"><a href="#sect-Security_Guide-TCP_Wrappers_and_xinetd-Additional_Resources">2.5.5. Additional Resources</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Kerberos">2.6. Kerberos</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-What_is_Kerberos">2.6.1. What is Kerberos?</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-Kerberos_Terminology">2.6.2. Kerberos Terminology</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-How_Kerberos_Works">2.6.3. How Kerberos Works</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-Kerberos_and_PAM">2.6.4. Kerberos and PAM</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Server">2.6.5. Configuring a Kerberos 5 Server</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-Config
uring_a_Kerberos_5_Client">2.6.6. Configuring a Kerberos 5 Client</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-Domain_to_Realm_Mapping">2.6.7. Domain-to-Realm Mapping</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-Setting_Up_Secondary_KDCs">2.6.8. Setting Up Secondary KDCs</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-Setting_Up_Cross_Realm_Authentication">2.6.9. Setting Up Cross Realm Authentication</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Kerberos-Additional_Resources">2.6.10. Additional Resources</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Virtual_Private_Networks_VPNs">2.7. Virtual Private Networks (VPNs)</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Virtual_Private_Networks_VPNs-How_Does_a_VPN_Work">2.7.1. How Does a VPN Work?</a></span></dt><dt><span class="section"><a h
ref="#sect-Security_Guide-Virtual_Private_Networks_VPNs-VPNs_and_PROD">2.7.2. VPNs and Fedora</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec">2.7.3. IPsec</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Virtual_Private_Networks_VPNs-Creating_an_IPsec_Connection">2.7.4. Creating an <abbr class="abbrev">IPsec</abbr> Connection</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Installation">2.7.5. IPsec Installation</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Host_to_Host_Configuration">2.7.6. IPsec Host-to-Host Configuration</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Network_to_Network_Configuration">2.7.7. IPsec Network-to-Network Configuration</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide
-Virtual_Private_Networks_VPNs-Starting_and_Stopping_an_IPsec_Connection">2.7.8. Starting and Stopping an <abbr class="abbrev">IPsec</abbr> Connection</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Firewalls">2.8. Firewalls</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Firewalls-Netfilter_and_IPTables">2.8.1. Netfilter and IPTables</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Firewalls-Basic_Firewall_Configuration">2.8.2. Basic Firewall Configuration</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Firewalls-Using_IPTables">2.8.3. Using IPTables</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Firewalls-Common_IPTables_Filtering">2.8.4. Common IPTables Filtering</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Firewalls-FORWARD_and_NAT_Rules">2.8.5. <code class="computeroutput">FORWARD</code> and <acronym class="acrony
m">NAT</acronym> Rules</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Firewalls-Malicious_Software_and_Spoofed_IP_Addresses">2.8.6. Malicious Software and Spoofed IP Addresses</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Firewalls-IPTables_and_Connection_Tracking">2.8.7. IPTables and Connection Tracking</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Firewalls-IPv6">2.8.8. IPv6</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Firewalls-Additional_Resources">2.8.9. Additional Resources</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-IPTables">2.9. IPTables</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-IPTables-Packet_Filtering">2.9.1. Packet Filtering</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-IPTables-Command_Options_for_IPTables">2.9.2. Command Options for IPTables</a></span></dt><dt><spa
n class="section"><a href="#sect-Security_Guide-IPTables-Saving_IPTables_Rules">2.9.3. Saving IPTables Rules</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-IPTables-IPTables_Control_Scripts">2.9.4. IPTables Control Scripts</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-IPTables-IPTables_and_IPv6">2.9.5. IPTables and IPv6</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-IPTables-Additional_Resources">2.9.6. Additional Resources</a></span></dt></dl></dd></dl></div><div xml:lang="en-US" class="section" title="2.1. Workstation Security" id="sect-Security_Guide-Workstation_Security" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sect-Security_Guide-Workstation_Security">2.1. Workstation 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" title="2.1.1. Evaluating Workstation Security" id="sect-Security_Guide-Workstation_Security-Evaluating_Workstation_Security"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.1.1. Evaluating Workstation Security</h3></div></div></div><div class="para">
+ </div><div class="section" title="2.1.1. Evaluating Workstation Security" id="sect-Security_Guide-Workstation_Security-Evaluating_Workstation_Security"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><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?
@@ -586,14 +566,14 @@ PORT STATE SERVICE
<span class="emphasis"><em>Personal Firewalls</em></span> — What type of firewall, if any, is necessary?
</div></li><li class="listitem"><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" title="2.1.2. BIOS and Boot Loader Security" id="sect-Security_Guide-Workstation_Security-BIOS_and_Boot_Loader_Security"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.1.2. BIOS and Boot Loader Security</h3></div></div></div><div class="para">
+ </div></li></ul></div></div><div class="section" title="2.1.2. BIOS and Boot Loader Security" id="sect-Security_Guide-Workstation_Security-BIOS_and_Boot_Loader_Security"><div class="titlepage"><div><div keep-together.within-column="always"><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" title="2.1.2.1. BIOS Passwords" id="sect-Security_Guide-BIOS_and_Boot_Loader_Security-BIOS_Passwords"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.1.2.1. BIOS Passwords</h4></div></div></div><div class="para">
- The two primary reasons for password protecting the BIOS of a computer are<sup>[<a id="id3210155" href="#ftn.id3210155" class="footnote">11</a>]</sup>:
+ </div><div class="section" title="2.1.2.1. BIOS Passwords" id="sect-Security_Guide-BIOS_and_Boot_Loader_Security-BIOS_Passwords"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-BIOS_and_Boot_Loader_Security-BIOS_Passwords">2.1.2.1. BIOS Passwords</h4></div></div></div><div class="para">
+ The two primary reasons for password protecting the BIOS of a computer are<sup>[<a id="id2898454" href="#ftn.id2898454" class="footnote">11</a>]</sup>:
</div><div class="orderedlist"><ol><li class="listitem"><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 class="listitem"><div class="para">
@@ -602,11 +582,11 @@ PORT STATE SERVICE
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" title="2.1.2.1.1. Securing Non-x86 Platforms" id="sect-Security_Guide-BIOS_Passwords-Securing_Non_x86_Platforms"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.1.2.1.1. Securing Non-x86 Platforms</h5></div></div></div><div class="para">
+ </div><div class="section" title="2.1.2.1.1. Securing Non-x86 Platforms" id="sect-Security_Guide-BIOS_Passwords-Securing_Non_x86_Platforms"><div class="titlepage"><div><div keep-together.within-column="always"><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" title="2.1.2.2. Boot Loader Passwords" id="sect-Security_Guide-BIOS_and_Boot_Loader_Security-Boot_Loader_Passwords"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.1.2.2. Boot Loader Passwords</h4></div></div></div><div class="para">
+ </div></div></div><div class="section" title="2.1.2.2. Boot Loader Passwords" id="sect-Security_Guide-BIOS_and_Boot_Loader_Security-Boot_Loader_Passwords"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><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.
@@ -616,16 +596,14 @@ PORT STATE SERVICE
<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" title="2.1.2.2.1. Password Protecting GRUB" id="sect-Security_Guide-Boot_Loader_Passwords-Password_Protecting_GRUB"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.1.2.2.1. Password Protecting GRUB</h5></div></div></div><div class="para">
+ </div><div class="section" title="2.1.2.2.1. Password Protecting GRUB" id="sect-Security_Guide-Boot_Loader_Passwords-Password_Protecting_GRUB"><div class="titlepage"><div><div keep-together.within-column="always"><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="#sect-Security_Guide-BIOS_and_Boot_Loader_Security-Boot_Loader_Passwords" title="2.1.2.2. Boot Loader Passwords">Section 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">
+ </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="id4010587" href="#ftn.id4010587" class="footnote">12</a>]</sup>.
+ </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="id2924302" href="#ftn.id2924302" 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">
@@ -634,15 +612,13 @@ PORT STATE SERVICE
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">
+ </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" title="2.1.3. Password Security" id="sect-Security_Guide-Workstation_Security-Password_Security"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.1.3. Password Security</h3></div></div></div><div class="para">
+ </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" title="2.1.3. Password Security" id="sect-Security_Guide-Workstation_Security-Password_Security"><div class="titlepage"><div><div keep-together.within-column="always"><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.
@@ -656,7 +632,7 @@ PORT STATE SERVICE
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" title="2.1.3.1. Creating Strong Passwords" id="sect-Security_Guide-Password_Security-Creating_Strong_Passwords"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.1.3.1. Creating Strong Passwords</h4></div></div></div><div class="para">
+ </div><div class="section" title="2.1.3.1. Creating Strong Passwords" id="sect-Security_Guide-Password_Security-Creating_Strong_Passwords"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><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.
@@ -738,7 +714,7 @@ PORT STATE SERVICE
<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" title="2.1.3.1.1. Secure Password Creation Methodology" id="sect-Security_Guide-Creating_Strong_Passwords-Secure_Password_Creation_Methodology"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.1.3.1.1. Secure Password Creation Methodology</h5></div></div></div><div class="para">
+ </div><div class="section" title="2.1.3.1.1. Secure Password Creation Methodology" id="sect-Security_Guide-Creating_Strong_Passwords-Secure_Password_Creation_Methodology"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-Security_Guide-Creating_Strong_Passwords-Secure_Password_Creation_Methodology">2.1.3.1.1. Secure Password Creation Methodology</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 class="listitem"><div class="para">
Think of an easily-remembered phrase, such as:
@@ -760,13 +736,13 @@ PORT STATE SERVICE
<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" title="2.1.3.2. Creating User Passwords Within an Organization" id="sect-Security_Guide-Password_Security-Creating_User_Passwords_Within_an_Organization"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.1.3.2. Creating User Passwords Within an Organization</h4></div></div></div><div class="para">
+ </div></div></div><div class="section" title="2.1.3.2. Creating User Passwords Within an Organization" id="sect-Security_Guide-Password_Security-Creating_User_Passwords_Within_an_Organization"><div class="titlepage"><div><div keep-together.within-column="always"><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" title="2.1.3.2.1. Forcing Strong Passwords" id="sect-Security_Guide-Creating_User_Passwords_Within_an_Organization-Forcing_Strong_Passwords"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.1.3.2.1. Forcing Strong Passwords</h5></div></div></div><div class="para">
+ </div><div class="section" title="2.1.3.2.1. Forcing Strong Passwords" id="sect-Security_Guide-Creating_User_Passwords_Within_an_Organization-Forcing_Strong_Passwords"><div class="titlepage"><div><div keep-together.within-column="always"><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/mo
dules.html</a>. For more information about PAM, refer to <a class="xref" href="#sect-Security_Guide-Pluggable_Authentication_Modules_PAM" title="2.4. Pluggable Authentication Modules (PAM)">Section 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.
@@ -780,21 +756,19 @@ PORT STATE SERVICE
<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" title="2.1.3.2.2. Passphrases" id="sect-Security_Guide-Passphrases"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.1.3.2.2. Passphrases</h5></div></div></div><div class="para">
+ </div></div></div><div class="section" title="2.1.3.2.2. Passphrases" id="sect-Security_Guide-Passphrases"><div class="titlepage"><div><div keep-together.within-column="always"><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. 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" title="2.1.3.2.3. Password Aging" id="sect-Security_Guide-Creating_User_Passwords_Within_an_Organization-Password_Aging"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.1.3.2.3. Password Aging</h5></div></div></div><div class="para">
+ </div></div><div class="section" title="2.1.3.2.3. Password Aging" id="sect-Security_Guide-Creating_User_Passwords_Within_an_Organization-Password_Aging"><div class="titlepage"><div><div keep-together.within-column="always"><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">
+ </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">
+ </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 myServer ~]# chage davido
Changing the aging information for davido
@@ -805,8 +779,7 @@ 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 myServer ~]#
-</pre><div class="para">
+[root at myServer ~]#</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.
@@ -820,16 +793,15 @@ Account Expiration Date (YYYY-MM-DD) [1969-12-31]:
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 class="step" title="Step 5"><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"><div class="figure-contents"><div class="mediaobject"><img src="images/fed-user_pass_info.png" width="444" alt="Specifying password aging options" /><div class="longdesc"><div class="para">
+ </div></li></ol></div><div class="figure" title="Figure 2.1. Specifying password aging options" 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" width="444" 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>Figure 2.1. Specifying password aging options</h6></div><br class="figure-break" /></div></div></div><div class="section" title="2.1.4. Administrative Controls" id="sect-Security_Guide-Workstation_Security-Administrative_Controls"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.1.4. Administrative Controls</h3></div></div></div><div class="para">
+ </div></div></div></div><h6>Figure 2.1. Specifying password aging options</h6></div><br class="figure-break" /></div></div></div><div class="section" title="2.1.4. Administrative Controls" id="sect-Security_Guide-Workstation_Security-Administrative_Controls"><div class="titlepage"><div><div keep-together.within-column="always"><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">
+ </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" title="2.4. Pluggable Authentication Modules (PAM)">Section 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" title="2.1.4.1. Allowing Root Access" id="sect-Security_Guide-Administrative_Controls-Allowing_Root_Access"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.1.4.1. Allowing Root Access</h4></div></div></div><div class="para">
+ </div><div class="section" title="2.1.4.1. Allowing Root Access" id="sect-Security_Guide-Administrative_Controls-Allowing_Root_Access"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Administrative_Controls-Allowing_Root_Access">2.1.4.1. Allowing Root Access</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:
@@ -839,11 +811,11 @@ Account Expiration Date (YYYY-MM-DD) [1969-12-31]:
<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 class="listitem"><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" title="2.1.4.2. Disallowing Root Access" id="sect-Security_Guide-Administrative_Controls-Disallowing_Root_Access"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.1.4.2. Disallowing Root Access</h4></div></div></div><div class="para">
+ </div></li></ul></div></div><div class="section" title="2.1.4.2. Disallowing Root Access" id="sect-Security_Guide-Administrative_Controls-Disallowing_Root_Access"><div class="titlepage"><div><div keep-together.within-column="always"><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="#sect-Security_Guide-BIOS_and_Boot_Loader_Security-Boot_Loader_Passwords" title="2.1.2.2. Boot Loader Passwords">Section 2.1.2.2, “Boot Loader Passwordsâ€</a> for more information on this topic.)
</div><div class="para">
<a class="xref" href="#tabl-Security_Guide-Disallowing_Root_Access-Methods_of_Disabling_the_Root_Account" title="Table 2.1. Methods of Disabling the Root Account">Table 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"><div class="table-contents"><table summary="Methods of Disabling the Root Account" border="1"><colgroup><col width="12%" /><col width="29%" /><col width="29%" /><col width="29%" /></colgroup><thead><tr><th>
+ </div><div class="table" title="Table 2.1. Methods of Disabling the Root Account" 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 width="12%" /><col width="29%" /><col width="29%" /><col width="29%" /></colgroup><thead><tr><th>
Method
</th><th>
Description
@@ -884,55 +856,49 @@ Account Expiration Date (YYYY-MM-DD) [1969-12-31]:
</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="id3361611" href="#ftn.id3361611" class="footnote">a</a>]</sup>
+ 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="id3417915" href="#ftn.id3417915" class="footnote">a</a>]</sup>
</td><td>
<table border="0" summary="Simple list" class="simplelist"><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 border="0" summary="Simple list" class="simplelist"><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.id3361611" href="#id3361611" class="para">a</a>] </sup>
+ </td></tr></tbody><tbody class="footnotes"><tr><td colspan="4"><div class="footnote"><p><sup>[<a id="ftn.id3417915" href="#id3417915" class="para">a</a>] </sup>
Refer to <a class="xref" href="#sect-Security_Guide-Disallowing_Root_Access-Disabling_Root_Using_PAM" title="2.1.4.2.4. Disabling Root Using PAM">Section 2.1.4.2.4, “Disabling Root Using PAMâ€</a> for details.
- </p></div></td></tr></tbody></table></div><h6>Table 2.1. Methods of Disabling the Root Account</h6></div><br class="table-break" /><div class="section" title="2.1.4.2.1. Disabling the Root Shell" id="sect-Security_Guide-Disallowing_Root_Access-Disabling_the_Root_Shell"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.1.4.2.1. Disabling the Root Shell</h5></div></div></div><div class="para">
+ </p></div></td></tr></tbody></table></div><h6>Table 2.1. Methods of Disabling the Root Account</h6></div><br class="table-break" /><div class="section" title="2.1.4.2.1. Disabling the Root Shell" id="sect-Security_Guide-Disallowing_Root_Access-Disabling_the_Root_Shell"><div class="titlepage"><div><div keep-together.within-column="always"><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" title="2.1.4.2.2. Disabling Root Logins" id="sect-Security_Guide-Disallowing_Root_Access-Disabling_Root_Logins"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.1.4.2.2. Disabling Root Logins</h5></div></div></div><div class="para">
+ </div></div></div><div class="section" title="2.1.4.2.2. Disabling Root Logins" id="sect-Security_Guide-Disallowing_Root_Access-Disabling_Root_Logins"><div class="titlepage"><div><div keep-together.within-column="always"><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">
+ </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" title="2.1.4.2.3. Disabling Root SSH Logins" id="sect-Security_Guide-Disallowing_Root_Access-Disabling_Root_SSH_Logins"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.1.4.2.3. Disabling Root SSH Logins</h5></div></div></div><div class="para">
+ </div></div></div><div class="section" title="2.1.4.2.3. Disabling Root SSH Logins" id="sect-Security_Guide-Disallowing_Root_Access-Disabling_Root_SSH_Logins"><div class="titlepage"><div><div keep-together.within-column="always"><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">
+ </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">
+ </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" title="2.1.4.2.4. Disabling Root Using PAM" id="sect-Security_Guide-Disallowing_Root_Access-Disabling_Root_Using_PAM"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.1.4.2.4. Disabling Root Using PAM</h5></div></div></div><div class="para">
+ </div><pre class="screen"><code class="computeroutput">kill -HUP `cat /var/run/sshd.pid`</code></pre></div><div class="section" title="2.1.4.2.4. Disabling Root Using PAM" id="sect-Security_Guide-Disallowing_Root_Access-Disabling_Root_Using_PAM"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-Security_Guide-Disallowing_Root_Access-Disabling_Root_Using_PAM">2.1.4.2.4. Disabling Root Using 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">
+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" title="2.4. Pluggable Authentication Modules (PAM)">Section 2.4, “Pluggable Authentication Modules (PAM)â€</a>.
- </div></div></div><div class="section" title="2.1.4.3. Limiting Root Access" id="sect-Security_Guide-Administrative_Controls-Limiting_Root_Access"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.1.4.3. Limiting Root Access</h4></div></div></div><div class="para">
+ </div></div></div><div class="section" title="2.1.4.3. Limiting Root Access" id="sect-Security_Guide-Administrative_Controls-Limiting_Root_Access"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Administrative_Controls-Limiting_Root_Access">2.1.4.3. Limiting Root Access</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" title="2.1.4.3.1. The su Command" id="sect-Security_Guide-Limiting_Root_Access-The_su_Command"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.1.4.3.1. The <code class="command">su</code> Command</h5></div></div></div><div class="para">
+ </div><div class="section" title="2.1.4.3.1. The su Command" id="sect-Security_Guide-Limiting_Root_Access-The_su_Command"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-Security_Guide-Limiting_Root_Access-The_su_Command">2.1.4.3.1. The <code class="command">su</code> Command</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="id3702298" href="#ftn.id3702298" 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.
+ 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="id2718397" href="#ftn.id2718397" 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><username></code></em></code>
-</pre><div class="para">
+ </div><pre class="screen"><code class="command">usermod -G wheel <em class="replaceable"><code><username></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.
@@ -946,19 +912,17 @@ sense=deny file=/etc/vsftpd.ftpusers onerr=succeed
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="#figu-Security_Guide-The_su_Command-Adding_users_to_the_wheel_group." title="Figure 2.2. Adding users to the "wheel" group.">Figure 2.2, “Adding users to the "wheel" group.â€</a>.
</div></li><li class="step" title="Step 5"><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">
+ </div><pre class="screen">auth required /lib/security/$ISA/pam_wheel.so use_uid</pre><div class="para">
This change means that only members of the administrative group <code class="computeroutput">wheel</code> can use this program.
- </div></li></ol></div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/fed-user_pass_groups.png" width="444" alt="Adding users to the "wheel" group." /><div class="longdesc"><div class="para">
+ </div></li></ol></div><div class="figure" title="Figure 2.2. Adding users to the "wheel" group." 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" width="444" alt="Adding users to the "wheel" group." /><div class="longdesc"><div class="para">
<span class="guilabel"><strong>Groups</strong></span> pane illustration
</div></div></div></div><h6>Figure 2.2. Adding users to the "wheel" group.</h6></div><br class="figure-break" /><div class="note"><h2>Note</h2><div class="para">
The root user is part of the <code class="computeroutput">wheel</code> group by default.
- </div></div></div><div class="section" title="2.1.4.3.2. The sudo Command" id="sect-Security_Guide-Limiting_Root_Access-The_sudo_Command"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.1.4.3.2. The <code class="command">sudo</code> Command</h5></div></div></div><div class="para">
+ </div></div></div><div class="section" title="2.1.4.3.2. The sudo Command" id="sect-Security_Guide-Limiting_Root_Access-The_sudo_Command"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-Security_Guide-Limiting_Root_Access-The_sudo_Command">2.1.4.3.2. The <code class="command">sudo</code> Command</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">
The basic format of the <code class="command">sudo</code> command is as follows:
- </div><pre class="screen"><code class="command">sudo <em class="replaceable"><code><command></code></em></code>
-</pre><div class="para">
+ </div><pre class="screen"><code class="command">sudo <em class="replaceable"><code><command></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>.
@@ -972,21 +936,19 @@ sense=deny file=/etc/vsftpd.ftpusers onerr=succeed
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">
+ </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">
+ </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" title="2.1.5. Available Network Services" id="sect-Security_Guide-Workstation_Security-Available_Network_Services"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.1.5. Available Network Services</h3></div></div></div><div class="para">
+ </div></div></div></div><div class="section" title="2.1.5. Available Network Services" id="sect-Security_Guide-Workstation_Security-Available_Network_Services"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Workstation_Security-Available_Network_Services">2.1.5. Available Network Services</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" title="2.1.5.1. Risks To Services" id="sect-Security_Guide-Available_Network_Services-Risks_To_Services"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.1.5.1. Risks To Services</h4></div></div></div><div class="para">
+ </div><div class="section" title="2.1.5.1. Risks To Services" id="sect-Security_Guide-Available_Network_Services-Risks_To_Services"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Available_Network_Services-Risks_To_Services">2.1.5.1. Risks To Services</h4></div></div></div><div class="para">
Network services can pose many risks for Linux systems. Below is a list of some of the primary issues:
</div><div class="itemizedlist"><ul><li class="listitem"><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.
@@ -1002,7 +964,7 @@ sense=deny file=/etc/vsftpd.ftpusers onerr=succeed
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">
To limit exposure to attacks over the network, all services that are unused should be turned off.
- </div></div></div><div class="section" title="2.1.5.2. Identifying and Configuring Services" id="sect-Security_Guide-Available_Network_Services-Identifying_and_Configuring_Services"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.1.5.2. Identifying and Configuring Services</h4></div></div></div><div class="para">
+ </div></div></div><div class="section" title="2.1.5.2. Identifying and Configuring Services" id="sect-Security_Guide-Available_Network_Services-Identifying_and_Configuring_Services"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Available_Network_Services-Identifying_and_Configuring_Services">2.1.5.2. Identifying and Configuring Services</h4></div></div></div><div class="para">
To enhance security, most network services installed with Fedora are turned off by default. There are, however, some notable exceptions:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="command">cupsd</code> — The default print server for Fedora.
@@ -1016,13 +978,13 @@ sense=deny file=/etc/vsftpd.ftpusers onerr=succeed
<code class="command">sshd</code> — The OpenSSH server, which is a secure replacement for 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"><div class="figure-contents"><div class="mediaobject"><img src="images/fed-service_config.png" width="444" alt="Services Configuration Tool" /><div class="longdesc"><div class="para">
+ </div><div class="figure" title="Figure 2.3. Services Configuration Tool" 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" width="444" alt="Services Configuration Tool" /><div class="longdesc"><div class="para">
<span class="application"><strong>Services Configuration Tool</strong></span> illustration
</div></div></div></div><h6>Figure 2.3. <span class="application">Services Configuration Tool</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="#figu-Security_Guide-Identifying_and_Configuring_Services-Services_Configuration_Tool" title="Figure 2.3. Services Configuration Tool">Figure 2.3, “<span class="application">Services Configuration Tool</span>â€</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" title="2.2.8. Verifying Which Ports Are Listening">Section 2.2.8, “Verifying Which Ports Are Listeningâ€</a> for more information.
- </div></div><div class="section" title="2.1.5.3. Insecure Services" id="sect-Security_Guide-Available_Network_Services-Insecure_Services"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.1.5.3. Insecure Services</h4></div></div></div><div class="para">
+ </div></div><div class="section" title="2.1.5.3. Insecure Services" id="sect-Security_Guide-Available_Network_Services-Insecure_Services"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Available_Network_Services-Insecure_Services">2.1.5.3. Insecure Services</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" title="1.5. Security Updates">Section 1.5, “Security Updatesâ€</a> for more information.
</div><div class="para">
Some network protocols are inherently more insecure than others. These include any services that:
@@ -1068,7 +1030,7 @@ sense=deny file=/etc/vsftpd.ftpusers onerr=succeed
More information on securing network services is available in <a class="xref" href="#sect-Security_Guide-Server_Security" title="2.2. Server Security">Section 2.2, “Server Securityâ€</a>.
</div><div class="para">
The next section discusses tools available to set up a simple firewall.
- </div></div></div><div class="section" title="2.1.6. Personal Firewalls" id="sect-Security_Guide-Workstation_Security-Personal_Firewalls"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.1.6. Personal Firewalls</h3></div></div></div><div class="para">
+ </div></div></div><div class="section" title="2.1.6. Personal Firewalls" id="sect-Security_Guide-Workstation_Security-Personal_Firewalls"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Workstation_Security-Personal_Firewalls">2.1.6. Personal Firewalls</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.
@@ -1080,7 +1042,7 @@ sense=deny file=/etc/vsftpd.ftpusers onerr=succeed
Refer to <a class="xref" href="#sect-Security_Guide-Firewalls-Basic_Firewall_Configuration" title="2.8.2. Basic Firewall Configuration">Section 2.8.2, “Basic Firewall Configurationâ€</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" title="2.8. Firewalls">Section 2.8, “Firewallsâ€</a> for more information. Refer to <a class="xref" href="#sect-Security_Guide-IPTables" title="2.9. IPTables">Section 2.9, “IPTablesâ€</a> for a comprehensive guide to the <code class="command">iptables</code> command.
- </div></div><div class="section" title="2.1.7. Security Enhanced Communication Tools" id="sect-Security_Guide-Workstation_Security-Security_Enhanced_Communication_Tools"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.1.7. Security Enhanced Communication Tools</h3></div></div></div><div class="para">
+ </div></div><div class="section" title="2.1.7. Security Enhanced Communication Tools" id="sect-Security_Guide-Workstation_Security-Security_Enhanced_Communication_Tools"><div class="titlepage"><div><div keep-together.within-column="always"><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.
@@ -1102,7 +1064,7 @@ sense=deny file=/etc/vsftpd.ftpusers onerr=succeed
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" title="1.5. Security Updates">Section 1.5, “Security Updatesâ€</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 xml:lang="en-US" class="section" title="2.2. Server Security" id="sect-Security_Guide-Server_Security" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.2. Server Security</h2></div></div></div><div class="para">
+ </div></div></div><div xml:lang="en-US" class="section" title="2.2. Server Security" id="sect-Security_Guide-Server_Security" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><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:
@@ -1114,7 +1076,7 @@ sense=deny file=/etc/vsftpd.ftpusers onerr=succeed
Serve only one type of network service per machine whenever possible.
</div></li><li class="listitem"><div class="para">
Monitor all servers carefully for suspicious activity.
- </div></li></ul></div><div class="section" title="2.2.1. Securing Services With TCP Wrappers and xinetd" id="sect-Security_Guide-Server_Security-Securing_Services_With_TCP_Wrappers_and_xinetd"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.2.1. Securing Services With TCP Wrappers and xinetd</h3></div></div></div><div class="para">
+ </div></li></ul></div><div class="section" title="2.2.1. Securing Services With TCP Wrappers and xinetd" id="sect-Security_Guide-Server_Security-Securing_Services_With_TCP_Wrappers_and_xinetd"><div class="titlepage"><div><div keep-together.within-column="always"><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.
@@ -1122,58 +1084,51 @@ sense=deny file=/etc/vsftpd.ftpusers onerr=succeed
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" title="2.8. Firewalls">Section 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" title="2.2.1.1. Enhancing Security With TCP Wrappers" id="sect-Security_Guide-Securing_Services_With_TCP_Wrappers_and_xinetd-Enhancing_Security_With_TCP_Wrappers"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.1.1. Enhancing Security With TCP Wrappers</h4></div></div></div><div class="para">
+ </div><div class="section" title="2.2.1.1. Enhancing Security With TCP Wrappers" id="sect-Security_Guide-Securing_Services_With_TCP_Wrappers_and_xinetd-Enhancing_Security_With_TCP_Wrappers"><div class="titlepage"><div><div keep-together.within-column="always"><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" title="2.2.1.1.1. TCP Wrappers and Connection Banners" id="sect-Security_Guide-Enhancing_Security_With_TCP_Wrappers-TCP_Wrappers_and_Connection_Banners"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.2.1.1.1. TCP Wrappers and Connection Banners</h5></div></div></div><div class="para">
+ </div><div class="section" title="2.2.1.1.1. TCP Wrappers and Connection Banners" id="sect-Security_Guide-Enhancing_Security_With_TCP_Wrappers-TCP_Wrappers_and_Connection_Banners"><div class="titlepage"><div><div keep-together.within-column="always"><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">
+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" title="2.2.1.1.2. TCP Wrappers and Attack Warnings" id="sect-Security_Guide-Enhancing_Security_With_TCP_Wrappers-TCP_Wrappers_and_Attack_Warnings"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.2.1.1.2. TCP Wrappers and Attack Warnings</h5></div></div></div><div class="para">
+ </div><pre class="screen"><code class="command"> vsftpd : ALL : banners /etc/banners/ </code></pre></div><div class="section" title="2.2.1.1.2. TCP Wrappers and Attack Warnings" id="sect-Security_Guide-Enhancing_Security_With_TCP_Wrappers-TCP_Wrappers_and_Attack_Warnings"><div class="titlepage"><div><div keep-together.within-column="always"><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">
+ </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" title="2.2.1.1.3. TCP Wrappers and Enhanced Logging" id="sect-Security_Guide-Enhancing_Security_With_TCP_Wrappers-TCP_Wrappers_and_Enhanced_Logging"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.2.1.1.3. TCP Wrappers and Enhanced Logging</h5></div></div></div><div class="para">
+ </div></div></div><div class="section" title="2.2.1.1.3. TCP Wrappers and Enhanced Logging" id="sect-Security_Guide-Enhancing_Security_With_TCP_Wrappers-TCP_Wrappers_and_Enhanced_Logging"><div class="titlepage"><div><div keep-together.within-column="always"><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">
+ </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" title="2.2.1.2. Enhancing Security With xinetd" id="sect-Security_Guide-Securing_Services_With_TCP_Wrappers_and_xinetd-Enhancing_Security_With_xinetd"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.1.2. Enhancing Security With xinetd</h4></div></div></div><div class="para">
+ </div></div></div><div class="section" title="2.2.1.2. Enhancing Security With xinetd" id="sect-Security_Guide-Securing_Services_With_TCP_Wrappers_and_xinetd-Enhancing_Security_With_xinetd"><div class="titlepage"><div><div keep-together.within-column="always"><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" title="2.2.1.2.1. Setting a Trap" id="sect-Security_Guide-Enhancing_Security_With_xinetd-Setting_a_Trap"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.2.1.2.1. Setting a Trap</h5></div></div></div><div class="para">
+ </div><div class="section" title="2.2.1.2.1. Setting a Trap" id="sect-Security_Guide-Enhancing_Security_With_xinetd-Setting_a_Trap"><div class="titlepage"><div><div keep-together.within-column="always"><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">
+ </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">
+ </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">
+ </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:
@@ -1181,7 +1136,7 @@ sense=deny file=/etc/vsftpd.ftpusers onerr=succeed
It does not work against stealth scans.
</div></li><li class="listitem"><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" title="2.2.1.2.2. Controlling Server Resources" id="sect-Security_Guide-Enhancing_Security_With_xinetd-Controlling_Server_Resources"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.2.1.2.2. Controlling Server Resources</h5></div></div></div><div class="para">
+ </div></li></ul></div></div><div class="section" title="2.2.1.2.2. Controlling Server Resources" id="sect-Security_Guide-Enhancing_Security_With_xinetd-Controlling_Server_Resources"><div class="titlepage"><div><div keep-together.within-column="always"><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:
@@ -1201,28 +1156,26 @@ sense=deny file=/etc/vsftpd.ftpusers onerr=succeed
<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 class="section" title="2.2.2. Securing Portmap" id="sect-Security_Guide-Server_Security-Securing_Portmap"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.2.2. Securing Portmap</h3></div></div></div><div class="para">
+ </div></div></div></div><div class="section" title="2.2.2. Securing Portmap" id="sect-Security_Guide-Server_Security-Securing_Portmap"><div class="titlepage"><div><div keep-together.within-column="always"><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" title="2.2.2.1. Protect portmap With TCP Wrappers" id="sect-Security_Guide-Securing_Portmap-Protect_portmap_With_TCP_Wrappers"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.2.1. Protect portmap With TCP Wrappers</h4></div></div></div><div class="para">
+ </div><div class="section" title="2.2.2.1. Protect portmap With TCP Wrappers" id="sect-Security_Guide-Securing_Portmap-Protect_portmap_With_TCP_Wrappers"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="section" title="2.2.2.2. Protect portmap With iptables" id="sect-Security_Guide-Securing_Portmap-Protect_portmap_With_iptables"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.2.2. Protect portmap With iptables</h4></div></div></div><div class="para">
+ </div></div><div class="section" title="2.2.2.2. Protect portmap With iptables" id="sect-Security_Guide-Securing_Portmap-Protect_portmap_With_iptables"><div class="titlepage"><div><div keep-together.within-column="always"><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">
+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">
+ </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" title="2.8. Firewalls">Section 2.8, “Firewallsâ€</a> for more information about implementing firewalls with iptables commands.
- </div></div></div></div><div class="section" title="2.2.3. Securing NIS" id="sect-Security_Guide-Server_Security-Securing_NIS"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.2.3. Securing NIS</h3></div></div></div><div class="para">
+ </div></div></div></div><div class="section" title="2.2.3. Securing NIS" id="sect-Security_Guide-Server_Security-Securing_NIS"><div class="titlepage"><div><div keep-together.within-column="always"><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:
@@ -1238,66 +1191,58 @@ iptables -A INPUT -p tcp -s 127.0.0.1 --dport 111 -j ACCEPT
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" title="2.2.2. Securing Portmap">Section 2.2.2, “Securing Portmapâ€</a>, then address the following issues, such as network planning.
- </div><div class="section" title="2.2.3.1. Carefully Plan the Network" id="sect-Security_Guide-Securing_NIS-Carefully_Plan_the_Network"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.3.1. Carefully Plan the Network</h4></div></div></div><div class="para">
+ </div><div class="section" title="2.2.3.1. Carefully Plan the Network" id="sect-Security_Guide-Securing_NIS-Carefully_Plan_the_Network"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="section" title="2.2.3.2. Use a Password-like NIS Domain Name and Hostname" id="sect-Security_Guide-Securing_NIS-Use_a_Password_like_NIS_Domain_Name_and_Hostname"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.3.2. Use a Password-like NIS Domain Name and Hostname</h4></div></div></div><div class="para">
+ </div></div><div class="section" title="2.2.3.2. Use a Password-like NIS Domain Name and Hostname" id="sect-Security_Guide-Securing_NIS-Use_a_Password_like_NIS_Domain_Name_and_Hostname"><div class="titlepage"><div><div keep-together.within-column="always"><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">
+ </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">
+ </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><div class="section" title="2.2.3.3. Edit the /var/yp/securenets File" id="sect-Security_Guide-Securing_NIS-Edit_the_varypsecurenets_File"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.3.3. Edit the <code class="filename">/var/yp/securenets</code> File</h4></div></div></div><div class="para">
+ </div></div><div class="section" title="2.2.3.3. Edit the /var/yp/securenets File" id="sect-Security_Guide-Securing_NIS-Edit_the_varypsecurenets_File"><div class="titlepage"><div><div keep-together.within-column="always"><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">
+ </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><div class="section" title="2.2.3.4. Assign Static Ports and Use iptables Rules" id="sect-Security_Guide-Securing_NIS-Assign_Static_Ports_and_Use_iptables_Rules"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.3.4. Assign Static Ports and Use iptables Rules</h4></div></div></div><div class="para">
+ </div></div><div class="section" title="2.2.3.4. Assign Static Ports and Use iptables Rules" id="sect-Security_Guide-Securing_NIS-Assign_Static_Ports_and_Use_iptables_Rules"><div class="titlepage"><div><div keep-together.within-column="always"><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">
+ </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">
+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" title="2.8. Firewalls">Section 2.8, “Firewallsâ€</a> for more information about implementing firewalls with iptables commands.
- </div></div></div><div class="section" title="2.2.3.5. Use Kerberos Authentication" id="sect-Security_Guide-Securing_NIS-Use_Kerberos_Authentication"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.3.5. Use Kerberos Authentication</h4></div></div></div><div class="para">
+ </div></div></div><div class="section" title="2.2.3.5. Use Kerberos Authentication" id="sect-Security_Guide-Securing_NIS-Use_Kerberos_Authentication"><div class="titlepage"><div><div keep-together.within-column="always"><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" title="2.6. Kerberos">Section 2.6, “Kerberosâ€</a> for more information about Kerberos.
- </div></div></div><div class="section" title="2.2.4. Securing NFS" id="sect-Security_Guide-Server_Security-Securing_NFS"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.2.4. Securing NFS</h3></div></div></div><div class="important"><h2>Important</h2><div class="para">
+ </div></div></div><div class="section" title="2.2.4. Securing NFS" id="sect-Security_Guide-Server_Security-Securing_NFS"><div class="titlepage"><div><div keep-together.within-column="always"><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" title="2.2.2. Securing Portmap">Section 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" title="2.2.4.1. Carefully Plan the Network" id="sect-Security_Guide-Securing_NFS-Carefully_Plan_the_Network"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.4.1. Carefully Plan the Network</h4></div></div></div><div class="para">
+ </div></div><div class="section" title="2.2.4.1. Carefully Plan the Network" id="sect-Security_Guide-Securing_NFS-Carefully_Plan_the_Network"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="section" title="2.2.4.2. Beware of Syntax Errors" id="sect-Security_Guide-Securing_NFS-Beware_of_Syntax_Errors"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.4.2. Beware of Syntax Errors</h4></div></div></div><div class="para">
+ </div></div><div class="section" title="2.2.4.2. Beware of Syntax Errors" id="sect-Security_Guide-Securing_NFS-Beware_of_Syntax_Errors"><div class="titlepage"><div><div keep-together.within-column="always"><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">
+ </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">
+ </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><div class="section" title="2.2.4.3. Do Not Use the no_root_squash Option" id="sect-Security_Guide-Securing_NFS-Do_Not_Use_the_no_root_squash_Option"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.4.3. Do Not Use the <code class="command">no_root_squash</code> Option</h4></div></div></div><div class="para">
+ </div><pre class="screen">showmount -e <em class="replaceable"><code><hostname></code></em></pre></div><div class="section" title="2.2.4.3. Do Not Use the no_root_squash Option" id="sect-Security_Guide-Securing_NFS-Do_Not_Use_the_no_root_squash_Option"><div class="titlepage"><div><div keep-together.within-column="always"><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><div class="section" title="2.2.4.4. NFS Firewall Configuration" id="sect-Security_Guide-Securing_NFS-NFS_Firewall_Configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.4.4. NFS Firewall Configuration</h4></div></div></div><div class="para">
+ </div></div><div class="section" title="2.2.4.4. NFS Firewall Configuration" id="sect-Security_Guide-Securing_NFS-NFS_Firewall_Configuration"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><div class="para">
<code class="command">MOUNTD_PORT</code> — TCP and UDP port for mountd (rpc.mountd)
@@ -1311,13 +1256,11 @@ iptables -A INPUT -p ALL -s! 192.168.0.0/24 --dport 835 -j DROP
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></div><div class="section" title="2.2.5. Securing the Apache HTTP Server" id="sect-Security_Guide-Server_Security-Securing_the_Apache_HTTP_Server"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.2.5. Securing the Apache HTTP Server</h3></div></div></div><div class="para">
+ </div></div></div><div class="section" title="2.2.5. Securing the Apache HTTP Server" id="sect-Security_Guide-Server_Security-Securing_the_Apache_HTTP_Server"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><pre class="screen">chown root <em class="replaceable"><code><directory_name></code></em>
-</pre></li><li class="listitem"><pre class="screen">chmod 755 <em class="replaceable"><code><directory_name></code></em>
-</pre></li></ol></div><div class="para">
+ </div><div class="orderedlist"><ol><li class="listitem"><pre class="screen">chown root <em class="replaceable"><code><directory_name></code></em></pre></li><li class="listitem"><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>.
@@ -1326,12 +1269,11 @@ iptables -A INPUT -p ALL -s! 192.168.0.0/24 --dport 835 -j DROP
</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><pre class="screen">UserDir enabled
-UserDir disabled root
-</pre><div class="para">
+UserDir disabled root</pre><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>Important</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><div class="section" title="2.2.6. Securing FTP" id="sect-Security_Guide-Server_Security-Securing_FTP"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.2.6. Securing FTP</h3></div></div></div><div class="para">
+ </div></div></div><div class="section" title="2.2.6. Securing FTP" id="sect-Security_Guide-Server_Security-Securing_FTP"><div class="titlepage"><div><div keep-together.within-column="always"><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 provides three FTP servers.
@@ -1343,24 +1285,21 @@ UserDir disabled root
<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" title="2.2.6.1. FTP Greeting Banner" id="sect-Security_Guide-Securing_FTP-FTP_Greeting_Banner"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.6.1. FTP Greeting Banner</h4></div></div></div><div class="para">
+ </div><div class="section" title="2.2.6.1. FTP Greeting Banner" id="sect-Security_Guide-Securing_FTP-FTP_Greeting_Banner"><div class="titlepage"><div><div keep-together.within-column="always"><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">
+ </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">
+ </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-Enhancing_Security_With_TCP_Wrappers-TCP_Wrappers_and_Connection_Banners" title="2.2.1.1.1. TCP Wrappers and Connection Banners">Section 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">
+ </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-Enhancing_Security_With_TCP_Wrappers-TCP_Wrappers_and_Connection_Banners" title="2.2.1.1.1. TCP Wrappers and Connection Banners">Section 2.2.1.1.1, “TCP Wrappers and Connection Bannersâ€</a>.
- </div></div><div class="section" title="2.2.6.2. Anonymous Access" id="sect-Security_Guide-Securing_FTP-Anonymous_Access"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.6.2. Anonymous Access</h4></div></div></div><div class="para">
+ </div></div><div class="section" title="2.2.6.2. Anonymous Access" id="sect-Security_Guide-Securing_FTP-Anonymous_Access"><div class="titlepage"><div><div keep-together.within-column="always"><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.
@@ -1368,40 +1307,35 @@ UserDir disabled root
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" title="2.2.6.2.1. Anonymous Upload" id="sect-Security_Guide-Anonymous_Access-Anonymous_Upload"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.2.6.2.1. Anonymous Upload</h5></div></div></div><div class="para">
+ </div></div><div class="section" title="2.2.6.2.1. Anonymous Upload" id="sect-Security_Guide-Anonymous_Access-Anonymous_Upload"><div class="titlepage"><div><div keep-together.within-column="always"><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/upload
-</pre><div class="para">
+ </div><pre class="screen">mkdir /var/ftp/pub/upload</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/upload
-</pre><div class="para">
+ </div><pre class="screen">chmod 730 /var/ftp/pub/upload</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 upload
-</pre><div class="warning"><h2>Warning</h2><div class="para">
+ </div><pre class="screen">drwx-wx--- 2 root ftp 4096 Feb 13 20:05 upload</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><div class="section" title="2.2.6.3. User Accounts" id="sect-Security_Guide-Securing_FTP-User_Accounts"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.6.3. User Accounts</h4></div></div></div><div class="para">
+ </div><pre class="screen">anon_upload_enable=YES</pre></div></div><div class="section" title="2.2.6.3. User Accounts" id="sect-Security_Guide-Securing_FTP-User_Accounts"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Securing_FTP-User_Accounts">2.2.6.3. User Accounts</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" title="2.2.6.3.1. Restricting User Accounts" id="sect-Security_Guide-User_Accounts-Restricting_User_Accounts"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.2.6.3.1. Restricting User Accounts</h5></div></div></div><div class="para">
+ </div><pre class="screen">local_enable=NO</pre><div class="section" title="2.2.6.3.1. Restricting User Accounts" id="sect-Security_Guide-User_Accounts-Restricting_User_Accounts"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-Security_Guide-User_Accounts-Restricting_User_Accounts">2.2.6.3.1. Restricting User Accounts</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="#sect-Security_Guide-Disallowing_Root_Access-Disabling_Root_Using_PAM" title="2.1.4.2.4. Disabling Root Using PAM">Section 2.1.4.2.4, “Disabling Root Using 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><div class="section" title="2.2.6.4. Use TCP Wrappers To Control Access" id="sect-Security_Guide-Securing_FTP-Use_TCP_Wrappers_To_Control_Access"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.6.4. Use TCP Wrappers To Control Access</h4></div></div></div><div class="para">
+ </div></div></div><div class="section" title="2.2.6.4. Use TCP Wrappers To Control Access" id="sect-Security_Guide-Securing_FTP-Use_TCP_Wrappers_To_Control_Access"><div class="titlepage"><div><div keep-together.within-column="always"><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-Securing_Services_With_TCP_Wrappers_and_xinetd-Enhancing_Security_With_TCP_Wrappers" title="2.2.1.1. Enhancing Security With TCP Wrappers">Section 2.2.1.1, “Enhancing Security With TCP Wrappersâ€</a>.
- </div></div></div><div class="section" title="2.2.7. Securing Sendmail" id="sect-Security_Guide-Server_Security-Securing_Sendmail"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.2.7. Securing Sendmail</h3></div></div></div><div class="para">
+ </div></div></div><div class="section" title="2.2.7. Securing Sendmail" id="sect-Security_Guide-Server_Security-Securing_Sendmail"><div class="titlepage"><div><div keep-together.within-column="always"><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" title="2.2.7.1. Limiting a Denial of Service Attack" id="sect-Security_Guide-Securing_Sendmail-Limiting_a_Denial_of_Service_Attack"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.7.1. Limiting a Denial of Service Attack</h4></div></div></div><div class="para">
+ </div><div class="section" title="2.2.7.1. Limiting a Denial of Service Attack" id="sect-Security_Guide-Securing_Sendmail-Limiting_a_Denial_of_Service_Attack"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><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.
@@ -1413,15 +1347,15 @@ UserDir disabled root
<code class="command">confMAX_HEADERS_LENGTH</code> — The maximum acceptable size (in bytes) for a message header.
</div></li><li class="listitem"><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 class="section" title="2.2.7.2. NFS and Sendmail" id="sect-Security_Guide-Securing_Sendmail-NFS_and_Sendmail"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.7.2. NFS and Sendmail</h4></div></div></div><div class="para">
+ </div></li></ul></div></div><div class="section" title="2.2.7.2. NFS and Sendmail" id="sect-Security_Guide-Securing_Sendmail-NFS_and_Sendmail"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Securing_Sendmail-NFS_and_Sendmail">2.2.7.2. NFS and 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><div class="section" title="2.2.7.3. Mail-only Users" id="sect-Security_Guide-Securing_Sendmail-Mail_only_Users"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.7.3. Mail-only Users</h4></div></div></div><div class="para">
+ </div></div></div><div class="section" title="2.2.7.3. Mail-only Users" id="sect-Security_Guide-Securing_Sendmail-Mail_only_Users"><div class="titlepage"><div><div keep-together.within-column="always"><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></div><div class="section" title="2.2.8. Verifying Which Ports Are Listening" id="sect-Security_Guide-Server_Security-Verifying_Which_Ports_Are_Listening"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.2.8. Verifying Which Ports Are Listening</h3></div></div></div><div class="para">
+ </div></div></div><div class="section" title="2.2.8. Verifying Which Ports Are Listening" id="sect-Security_Guide-Server_Security-Verifying_Which_Ports_Are_Listening"><div class="titlepage"><div><div keep-together.within-column="always"><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.
@@ -1429,8 +1363,7 @@ UserDir disabled root
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">
+ </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):
@@ -1450,36 +1383,30 @@ 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">
+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">
+ </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">
+ </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">
+ </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">
+ </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">
+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></div><div xml:lang="en-US" class="section" title="2.3. Single Sign-on (SSO)" id="sect-Security_Guide-Single_Sign_on_SSO" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.3. Single Sign-on (SSO)</h2></div></div></div><div class="section" title="2.3.1. Introduction" id="sect-Security_Guide-Single_Sign_on_SSO-Introduction"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.3.1. Introduction</h3></div></div></div><div class="para">
+ </div></div></div><div xml:lang="en-US" class="section" title="2.3. Single Sign-on (SSO)" id="sect-Security_Guide-Single_Sign_on_SSO" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sect-Security_Guide-Single_Sign_on_SSO">2.3. Single Sign-on (SSO)</h2></div></div></div><div class="section" title="2.3.1. Introduction" id="sect-Security_Guide-Single_Sign_on_SSO-Introduction"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Single_Sign_on_SSO-Introduction">2.3.1. Introduction</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" title="2.3.1.1. Supported Applications" id="sect-Security_Guide-Introduction-Supported_Applications"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.3.1.1. Supported Applications</h4></div></div></div><div class="para">
+ </div><div class="section" title="2.3.1.1. Supported Applications" id="sect-Security_Guide-Introduction-Supported_Applications"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Introduction-Supported_Applications">2.3.1.1. Supported Applications</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 class="listitem"><div class="para">
Login
@@ -1487,19 +1414,19 @@ ypbind 657 0 7u IPv4 1319 TCP *:834 (LISTE
Screensaver
</div></li><li class="listitem"><div class="para">
Firefox and Thunderbird
- </div></li></ul></div></div><div class="section" title="2.3.1.2. Supported Authentication Mechanisms" id="sect-Security_Guide-Introduction-Supported_Authentication_Mechanisms"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.3.1.2. Supported Authentication Mechanisms</h4></div></div></div><div class="para">
+ </div></li></ul></div></div><div class="section" title="2.3.1.2. Supported Authentication Mechanisms" id="sect-Security_Guide-Introduction-Supported_Authentication_Mechanisms"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><div class="para">
Kerberos name/password login
</div></li><li class="listitem"><div class="para">
Smart card/PIN login
- </div></li></ul></div></div><div class="section" title="2.3.1.3. Supported Smart Cards" id="sect-Security_Guide-Introduction-Supported_Smart_Cards"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.3.1.3. Supported Smart Cards</h4></div></div></div><div class="para">
+ </div></li></ul></div></div><div class="section" title="2.3.1.3. Supported Smart Cards" id="sect-Security_Guide-Introduction-Supported_Smart_Cards"><div class="titlepage"><div><div keep-together.within-column="always"><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" title="2.3.1.4. Advantages of Fedora Single Sign-on" id="sect-Security_Guide-Introduction-Advantages_of_PROD_Single_Sign_on"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.3.1.4. Advantages of Fedora Single Sign-on</h4></div></div></div><div class="para">
+ </div></div><div class="section" title="2.3.1.4. Advantages of Fedora Single Sign-on" id="sect-Security_Guide-Introduction-Advantages_of_PROD_Single_Sign_on"><div class="titlepage"><div><div keep-together.within-column="always"><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:
@@ -1509,7 +1436,7 @@ ypbind 657 0 7u IPv4 1319 TCP *:834 (LISTE
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 class="listitem"><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 class="section" title="2.3.2. Getting Started with your new Smart Card" id="sect-Security_Guide-Single_Sign_on_SSO-Getting_Started_with_your_new_Smart_Card"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.3.2. Getting Started with your new Smart Card</h3></div></div></div><div class="para">
+ </div></li></ul></div></div></div><div class="section" title="2.3.2. Getting Started with your new Smart Card" id="sect-Security_Guide-Single_Sign_on_SSO-Getting_Started_with_your_new_Smart_Card"><div class="titlepage"><div><div keep-together.within-column="always"><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.
@@ -1519,8 +1446,7 @@ ypbind 657 0 7u IPv4 1319 TCP *:834 (LISTE
Make sure you have the <code class="filename">nss-tools</code> package loaded.
</div></li><li class="step" title="Step 3"><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 class="step" title="Step 4"><div class="para">
+ </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 class="step" title="Step 4"><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 class="step" title="Step 5"><div class="para">
Enable Smart Card Login Support
@@ -1570,12 +1496,11 @@ ypbind 657 0 7u IPv4 1319 TCP *:834 (LISTE
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 class="step" title="Step 9"><div class="para">
Logout
- </div></li></ol></div><div class="section" title="2.3.2.1. Troubleshooting" id="sect-Security_Guide-Getting_Started_with_your_new_Smart_Card-Troubleshooting"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.3.2.1. Troubleshooting</h4></div></div></div><div class="para">
+ </div></li></ol></div><div class="section" title="2.3.2.1. Troubleshooting" id="sect-Security_Guide-Getting_Started_with_your_new_Smart_Card-Troubleshooting"><div class="titlepage"><div><div keep-together.within-column="always"><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">
+ </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><div class="section" title="2.3.3. How Smart Card Enrollment Works" id="sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Enrollment_Works"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.3.3. How Smart Card Enrollment Works</h3></div></div></div><div class="para">
+ </div></div></div><div class="section" title="2.3.3. How Smart Card Enrollment Works" id="sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Enrollment_Works"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><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>).
@@ -1583,9 +1508,9 @@ ypbind 657 0 7u IPv4 1319 TCP *:834 (LISTE
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 class="listitem"><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"><div class="figure-contents"><div class="mediaobject"><img src="images/SCLoginEnrollment.png" width="444" alt="How Smart Card Enrollment Works" /><div class="longdesc"><div class="para">
+ </div></li></ol></div><div class="figure" title="Figure 2.4. How Smart Card Enrollment Works" 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" width="444" alt="How Smart Card Enrollment Works" /><div class="longdesc"><div class="para">
How Smart Card Enrollment Works.
- </div></div></div></div><h6>Figure 2.4. How Smart Card Enrollment Works</h6></div><br class="figure-break" /></div><div class="section" title="2.3.4. How Smart Card Login Works" id="sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Login_Works"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.3.4. How Smart Card Login Works</h3></div></div></div><div class="para">
+ </div></div></div></div><h6>Figure 2.4. How Smart Card Enrollment Works</h6></div><br class="figure-break" /></div><div class="section" title="2.3.4. How Smart Card Login Works" id="sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Login_Works"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><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.
@@ -1593,13 +1518,13 @@ ypbind 657 0 7u IPv4 1319 TCP *:834 (LISTE
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 class="listitem"><div class="para">
This is validated against the KDC and login granted.
- </div></li></ol></div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/SCLogin.png" width="444" alt="How Smart Card Login Works" /><div class="longdesc"><div class="para">
+ </div></li></ol></div><div class="figure" title="Figure 2.5. How Smart Card Login Works" 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" width="444" alt="How Smart Card Login Works" /><div class="longdesc"><div class="para">
How Smart Card Login Works.
</div></div></div></div><h6>Figure 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" title="2.6. Kerberos">Section 2.6, “Kerberosâ€</a> and <a class="xref" href="#sect-Security_Guide-Pluggable_Authentication_Modules_PAM" title="2.4. Pluggable Authentication Modules (PAM)">Section 2.4, “Pluggable Authentication Modules (PAM)â€</a> for more information on Kerberos and <acronym class="acronym">PAM</acronym>.
- </div></div><div class="section" title="2.3.5. Configuring Firefox to use Kerberos for SSO" id="sect-Security_Guide-Single_Sign_on_SSO-Configuring_Firefox_to_use_Kerberos_for_SSO"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.3.5. Configuring Firefox to use Kerberos for SSO</h3></div></div></div><div class="para">
+ </div></div><div class="section" title="2.3.5. Configuring Firefox to use Kerberos for SSO" id="sect-Security_Guide-Single_Sign_on_SSO-Configuring_Firefox_to_use_Kerberos_for_SSO"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><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.
@@ -1618,7 +1543,7 @@ ypbind 657 0 7u IPv4 1319 TCP *:834 (LISTE
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"><div class="figure-contents"><div class="mediaobject"><img src="images/fed-firefox_kerberos_SSO.png" width="444" alt="Configuring Firefox for SSO with Kerberos" /><div class="longdesc"><div class="para">
+ </div></li></ol></div><div class="figure" title="Figure 2.6. Configuring Firefox for SSO with Kerberos" 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" width="444" 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>Figure 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:
@@ -1634,34 +1559,29 @@ Valid starting Expires Service principal
renew until 10/26/06 23:47:54
Kerberos 4 ticket cache: /tmp/tkt10920
-klist: You have no tickets cached
-</pre><div class="section" title="2.3.5.1. Troubleshooting" id="sect-Security_Guide-Configuring_Firefox_to_use_Kerberos_for_SSO-Troubleshooting"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.3.5.1. Troubleshooting</h4></div></div></div><div class="para">
+klist: You have no tickets cached</pre><div class="section" title="2.3.5.1. Troubleshooting" id="sect-Security_Guide-Configuring_Firefox_to_use_Kerberos_for_SSO-Troubleshooting"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><div class="para">
Close all instances of Firefox.
</div></li><li class="listitem"><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 class="listitem"><div class="para">
+export NSPR_LOG_FILE=/tmp/moz.log</pre></li><li class="listitem"><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">
+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">
+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">
+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></div><div xml:lang="en-US" class="section" title="2.4. Pluggable Authentication Modules (PAM)" id="sect-Security_Guide-Pluggable_Authentication_Modules_PAM" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.4. Pluggable Authentication Modules (PAM)</h2></div></div></div><div class="para">
+ </div></div></div></div><div xml:lang="en-US" class="section" title="2.4. Pluggable Authentication Modules (PAM)" id="sect-Security_Guide-Pluggable_Authentication_Modules_PAM" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sect-Security_Guide-Pluggable_Authentication_Modules_PAM">2.4. Pluggable Authentication Modules (PAM)</h2></div></div></div><div class="para">
Programs that grant users access to a system use <em class="firstterm">authentication</em> to verify each other's identity (that is, to establish that a user is who they say they are).
</div><div class="para">
Historically, each program had its own way of authenticating users. In Fedora, many programs are configured to use a centralized authentication mechanism called <em class="firstterm">Pluggable Authentication Modules</em> (<acronym class="acronym">PAM</acronym>).
@@ -1669,7 +1589,7 @@ example.com = EXAMPLE.COM
PAM uses a pluggable, modular architecture, which affords the system administrator a great deal of flexibility in setting authentication policies for the system.
</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" title="2.4.3. PAM Configuration File Format">Section 2.4.3, “PAM Configuration File Formatâ€</a> for more information.
- </div><div class="section" title="2.4.1. Advantages of PAM" id="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Advantages_of_PAM"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.4.1. Advantages of PAM</h3></div></div></div><div class="para">
+ </div><div class="section" title="2.4.1. Advantages of PAM" id="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Advantages_of_PAM"><div class="titlepage"><div><div keep-together.within-column="always"><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 offers the following advantages:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
a common authentication scheme that can be used with a wide variety of applications.
@@ -1677,18 +1597,17 @@ example.com = EXAMPLE.COM
significant flexibility and control over authentication for both system administrators and application developers.
</div></li><li class="listitem"><div class="para">
a single, fully-documented library which allows developers to write programs without having to create their own authentication schemes.
- </div></li></ul></div></div><div class="section" title="2.4.2. PAM Configuration Files" id="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_Files"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.4.2. PAM Configuration Files</h3></div></div></div><div class="para">
+ </div></li></ul></div></div><div class="section" title="2.4.2. PAM Configuration Files" id="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_Files"><div class="titlepage"><div><div keep-together.within-column="always"><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">
The <code class="filename">/etc/pam.d/</code> directory contains the PAM configuration files for each PAM-aware application. In earlier versions of PAM, the <code class="filename">/etc/pam.conf</code> file was used, but this file is now deprecated and is only used if the <code class="filename">/etc/pam.d/</code> directory does not exist.
- </div><div class="section" title="2.4.2.1. PAM Service Files" id="sect-Security_Guide-PAM_Configuration_Files-PAM_Service_Files"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.4.2.1. PAM Service Files</h4></div></div></div><div class="para">
+ </div><div class="section" title="2.4.2.1. PAM Service Files" id="sect-Security_Guide-PAM_Configuration_Files-PAM_Service_Files"><div class="titlepage"><div><div keep-together.within-column="always"><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">
Each PAM-aware application or <em class="firstterm">service</em> has a file in the <code class="filename">/etc/pam.d/</code> directory. Each file in this directory has the same name as the service to which it controls access.
</div><div class="para">
The PAM-aware program is responsible for defining its service name and installing its own PAM configuration file in the <code class="filename">/etc/pam.d/</code> directory. For example, the <code class="command">login</code> program defines its service name as <code class="command">login</code> and installs the <code class="filename">/etc/pam.d/login</code> PAM configuration file.
- </div></div></div><div class="section" title="2.4.3. PAM Configuration File Format" id="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_File_Format"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.4.3. PAM Configuration File Format</h3></div></div></div><div class="para">
+ </div></div></div><div class="section" title="2.4.3. PAM Configuration File Format" id="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_File_Format"><div class="titlepage"><div><div keep-together.within-column="always"><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">
Each PAM configuration file contains a group of directives formatted as follows:
- </div><pre class="screen"><em class="replaceable"><code><module interface></code></em> <em class="replaceable"><code><control flag></code></em> <em class="replaceable"><code><module name></code></em> <em class="replaceable"><code><module arguments></code></em>
-</pre><div class="para">
+ </div><pre class="screen"><em class="replaceable"><code><module interface></code></em> <em class="replaceable"><code><control flag></code></em> <em class="replaceable"><code><module name></code></em> <em class="replaceable"><code><module arguments></code></em></pre><div class="para">
Each of these elements is explained in the following sections.
- </div><div class="section" title="2.4.3.1. Module Interface" id="sect-Security_Guide-PAM_Configuration_File_Format-Module_Interface"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.4.3.1. Module Interface</h4></div></div></div><div class="para">
+ </div><div class="section" title="2.4.3.1. Module Interface" id="sect-Security_Guide-PAM_Configuration_File_Format-Module_Interface"><div class="titlepage"><div><div keep-together.within-column="always"><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">
Four types of PAM module interface are currently available. Each of these corresponds to a different aspect of the authorization process:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="command">auth</code> — This module interface authenticates use. For example, it requests and verifies the validity of a password. Modules with this interface can also set credentials, such as group memberships or Kerberos tickets.
@@ -1702,10 +1621,9 @@ example.com = EXAMPLE.COM
An individual module can provide any or all module interfaces. For instance, <code class="filename">pam_unix.so</code> provides all four module interfaces.
</div></div><div class="para">
In a PAM configuration file, the module interface is the first field defined. For example, a typical line in a configuration may look like this:
- </div><pre class="screen">auth required pam_unix.so
-</pre><div class="para">
+ </div><pre class="screen">auth required pam_unix.so</pre><div class="para">
This instructs PAM to use the <code class="filename">pam_unix.so</code> module's <code class="command">auth</code> interface.
- </div><div class="section" title="2.4.3.1.1. Stacking Module Interfaces" id="sect-Security_Guide-Module_Interface-Stacking_Module_Interfaces"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.4.3.1.1. Stacking Module Interfaces</h5></div></div></div><div class="para">
+ </div><div class="section" title="2.4.3.1.1. Stacking Module Interfaces" id="sect-Security_Guide-Module_Interface-Stacking_Module_Interfaces"><div class="titlepage"><div><div keep-together.within-column="always"><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" title="2.4.3.2. Control Flag">Section 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">
Stacking makes it easy for an administrator to require specific conditions to exist before allowing the user to authenticate. For example, the <code class="command">reboot</code> command normally uses several stacked modules, as seen in its PAM configuration file:
@@ -1714,8 +1632,7 @@ example.com = EXAMPLE.COM
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 class="listitem"><div class="para">
+account required pam_permit.so</pre><div class="itemizedlist"><ul><li class="listitem"><div class="para">
The first line is a comment and is not processed.
</div></li><li class="listitem"><div class="para">
<code class="command">auth sufficient pam_rootok.so</code> — This line uses the <code class="filename">pam_rootok.so</code> module to check whether the current user is root, by verifying that their UID is 0. If this test succeeds, no other modules are consulted and the command is executed. If this test fails, the next module is consulted.
@@ -1725,7 +1642,7 @@ account required pam_permit.so
<code class="command">#auth include system-auth</code> — This line is commented and is not processed.
</div></li><li class="listitem"><div class="para">
<code class="command">account required pam_permit.so</code> — This line uses the <code class="filename">pam_permit.so</code> module to allow the root user or anyone logged in at the console to reboot the system.
- </div></li></ul></div></div></div><div class="section" title="2.4.3.2. Control Flag" id="sect-Security_Guide-PAM_Configuration_File_Format-Control_Flag"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.4.3.2. Control Flag</h4></div></div></div><div class="para">
+ </div></li></ul></div></div></div><div class="section" title="2.4.3.2. Control Flag" id="sect-Security_Guide-PAM_Configuration_File_Format-Control_Flag"><div class="titlepage"><div><div keep-together.within-column="always"><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">
All PAM modules generate a success or failure result when called. Control flags tell PAM what do with the result. Modules can be stacked in a particular order, and the control flags determine how important the success or failure of a particular module is to the overall goal of authenticating the user to the service.
</div><div class="para">
There are four predefined control flags:
@@ -1743,18 +1660,17 @@ account required pam_permit.so
A newer control flag syntax that allows for more precise control is now available for 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><div class="section" title="2.4.3.3. Module Name" id="sect-Security_Guide-PAM_Configuration_File_Format-Module_Name"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.4.3.3. Module Name</h4></div></div></div><div class="para">
+ </div></div><div class="section" title="2.4.3.3. Module Name" id="sect-Security_Guide-PAM_Configuration_File_Format-Module_Name"><div class="titlepage"><div><div keep-together.within-column="always"><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><div class="section" title="2.4.3.4. Module Arguments" id="sect-Security_Guide-PAM_Configuration_File_Format-Module_Arguments"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.4.3.4. Module Arguments</h4></div></div></div><div class="para">
+ </div></div><div class="section" title="2.4.3.4. Module Arguments" id="sect-Security_Guide-PAM_Configuration_File_Format-Module_Arguments"><div class="titlepage"><div><div keep-together.within-column="always"><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 uses <em class="firstterm">arguments</em> to pass information to a pluggable module during authentication for some modules.
</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">
The following is a typical <code class="filename">pam_userdb.so</code> line in a PAM configuration. The <em class="replaceable"><code><path-to-file></code></em> is the full path to the Berkeley DB database file:
- </div><pre class="screen">auth required pam_userdb.so db=<em class="replaceable"><code><path-to-file></code></em>
-</pre><div class="para">
+ </div><pre class="screen">auth required pam_userdb.so db=<em class="replaceable"><code><path-to-file></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></div><div class="section" title="2.4.4. Sample PAM Configuration Files" id="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Sample_PAM_Configuration_Files"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.4.4. Sample PAM Configuration Files</h3></div></div></div><div class="para">
+ </div></div></div><div class="section" title="2.4.4. Sample PAM Configuration Files" id="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Sample_PAM_Configuration_Files"><div class="titlepage"><div><div keep-together.within-column="always"><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">
The following is a sample PAM application configuration file:
</div><pre class="screen">#%PAM-1.0
auth required pam_securetty.so
@@ -1763,8 +1679,7 @@ 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 class="listitem"><div class="para">
+session required pam_unix.so</pre><div class="itemizedlist"><ul><li class="listitem"><div class="para">
The first line is a comment, indicated by the hash mark (<code class="command">#</code>) at the beginning of the line.
</div></li><li class="listitem"><div class="para">
Lines two through four stack three modules for login authentication.
@@ -1796,7 +1711,7 @@ session required pam_unix.so
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 class="listitem"><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><div class="section" title="2.4.5. Creating PAM Modules" id="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Creating_PAM_Modules"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.4.5. Creating PAM Modules</h3></div></div></div><div class="para">
+ </div></li></ul></div></div><div class="section" title="2.4.5. Creating PAM Modules" id="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Creating_PAM_Modules"><div class="titlepage"><div><div keep-together.within-column="always"><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.
@@ -1804,7 +1719,7 @@ session required pam_unix.so
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><div class="section" title="2.4.6. PAM and Administrative Credential Caching" id="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Administrative_Credential_Caching"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.4.6. PAM and Administrative Credential Caching</h3></div></div></div><div class="para">
+ </div></div><div class="section" title="2.4.6. PAM and Administrative Credential Caching" id="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Administrative_Credential_Caching"><div class="titlepage"><div><div keep-together.within-column="always"><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.
@@ -1812,11 +1727,11 @@ session required pam_unix.so
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"><div class="figure-contents"><div class="mediaobject"><img src="images/authicon.png" alt="The Authentication Icon" /><div class="longdesc"><div class="para">
+ </div><div class="figure" title="Figure 2.7. The Authentication Icon" 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>Figure 2.7. The Authentication Icon</h6></div><br class="figure-break" /><div class="section" title="2.4.6.1. Removing the Timestamp File" id="sect-Security_Guide-PAM_and_Administrative_Credential_Caching-Removing_the_Timestamp_File"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.4.6.1. Removing the Timestamp File</h4></div></div></div><div class="para">
+ </div></div></div></div><h6>Figure 2.7. The Authentication Icon</h6></div><br class="figure-break" /><div class="section" title="2.4.6.1. Removing the Timestamp File" id="sect-Security_Guide-PAM_and_Administrative_Credential_Caching-Removing_the_Timestamp_File"><div class="titlepage"><div><div keep-together.within-column="always"><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"><div class="figure-contents"><div class="mediaobject"><img src="images/auth-panel.png" width="444" alt="Dismiss Authentication Dialog" /><div class="longdesc"><div class="para">
+ </div><div class="figure" title="Figure 2.8. Dismiss Authentication Dialog" id="figu-Security_Guide-Removing_the_Timestamp_File-Dismiss_Authentication_Dialog"><div class="figure-contents"><div class="mediaobject"><img src="images/auth-panel.png" width="444" alt="Dismiss Authentication Dialog" /><div class="longdesc"><div class="para">
Illustration of the authentication dismissal dialog box.
</div></div></div></div><h6>Figure 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:
@@ -1828,12 +1743,11 @@ session required pam_unix.so
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 class="listitem"><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">
+ </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 class="section" title="2.4.6.2. Common pam_timestamp Directives" id="sect-Security_Guide-PAM_and_Administrative_Credential_Caching-Common_pam_timestamp_Directives"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.4.6.2. Common pam_timestamp Directives</h4></div></div></div><div class="para">
+ </div></div><div class="section" title="2.4.6.2. Common pam_timestamp Directives" id="sect-Security_Guide-PAM_and_Administrative_Credential_Caching-Common_pam_timestamp_Directives"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><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).
@@ -1841,9 +1755,9 @@ session required pam_unix.so
<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-Additional_Resources-Installed_Firewall_Documentation" title="2.8.9.1. Installed Firewall Documentation">Section 2.8.9.1, “Installed Firewall Documentationâ€</a> for more information about controlling the <code class="filename">pam_timestamp.so</code> module.
- </div></div></div><div class="section" title="2.4.7. PAM and Device Ownership" id="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Device_Ownership"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.4.7. PAM and Device Ownership</h3></div></div></div><div class="para">
+ </div></div></div><div class="section" title="2.4.7. PAM and Device Ownership" id="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Device_Ownership"><div class="titlepage"><div><div keep-together.within-column="always"><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" title="2.4.7.1. Device Ownership" id="sect-Security_Guide-PAM_and_Device_Ownership-Device_Ownership"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.4.7.1. Device Ownership</h4></div></div></div><div class="para">
+ </div><div class="section" title="2.4.7.1. Device Ownership" id="sect-Security_Guide-PAM_and_Device_Ownership-Device_Ownership"><div class="titlepage"><div><div keep-together.within-column="always"><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.
@@ -1862,13 +1776,11 @@ session required pam_unix.so
</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">
+<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 class="section" title="2.4.7.2. Application Access" id="sect-Security_Guide-PAM_and_Device_Ownership-Application_Access"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.4.7.2. Application Access</h4></div></div></div><div class="para">
+ </div><pre class="screen"><console>=tty[0-9][0-9]* vc/[0-9][0-9]*</pre></div></div><div class="section" title="2.4.7.2. Application Access" id="sect-Security_Guide-PAM_and_Device_Ownership-Application_Access"><div class="titlepage"><div><div keep-together.within-column="always"><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>.
@@ -1886,9 +1798,9 @@ session required pam_unix.so
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-Additional_Resources-Installed_Firewall_Documentation" title="2.8.9.1. Installed Firewall Documentation">Section 2.8.9.1, “Installed Firewall Documentationâ€</a> for more information.
- </div></div></div><div class="section" title="2.4.8. Additional Resources" id="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Additional_Resources"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.4.8. Additional Resources</h3></div></div></div><div class="para">
+ </div></div></div><div class="section" title="2.4.8. Additional Resources" id="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Additional_Resources"><div class="titlepage"><div><div keep-together.within-column="always"><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" title="2.4.8.1. Installed PAM Documentation" id="sect-Security_Guide-Additional_Resources-Installed_PAM_Documentation"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.4.8.1. Installed PAM Documentation</h4></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ </div><div class="section" title="2.4.8.1. Installed PAM Documentation" id="sect-Security_Guide-Additional_Resources-Installed_PAM_Documentation"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><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 class="listitem"><div class="para">
<code class="command">pam</code> — Good introductory information on PAM, including the structure and purpose of the PAM configuration files.
@@ -1906,19 +1818,19 @@ session required pam_unix.so
<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 class="listitem"><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 class="section" title="2.4.8.2. Useful PAM Websites" id="sect-Security_Guide-Additional_Resources-Useful_PAM_Websites"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.4.8.2. Useful PAM Websites</h4></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ </div></li></ul></div></div><div class="section" title="2.4.8.2. Useful PAM Websites" id="sect-Security_Guide-Additional_Resources-Useful_PAM_Websites"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><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></div></div><div xml:lang="en-US" class="section" title="2.5. TCP Wrappers and xinetd" id="sect-Security_Guide-TCP_Wrappers_and_xinetd" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.5. TCP Wrappers and xinetd</h2></div></div></div><div class="para">
+ </div></div></li></ul></div></div></div></div><div xml:lang="en-US" class="section" title="2.5. TCP Wrappers and xinetd" id="sect-Security_Guide-TCP_Wrappers_and_xinetd" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><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="#figu-Security_Guide-TCP_Wrappers_and_xinetd-Access_Control_to_Network_Services" title="Figure 2.9. Access Control to Network Services">Figure 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"><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">
+ </div><div class="figure" title="Figure 2.9. Access Control to Network Services" 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>Figure 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" title="2.9. IPTables">Section 2.9, “IPTablesâ€</a> for information about using firewalls with <code class="command">iptables</code>.
- </div><div class="section" title="2.5.1. TCP Wrappers" id="sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.5.1. TCP Wrappers</h3></div></div></div><div class="para">
+ </div><div class="section" title="2.5.1. TCP Wrappers" id="sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers"><div class="titlepage"><div><div keep-together.within-column="always"><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>.
@@ -1930,8 +1842,7 @@ session required pam_unix.so
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 <binary-name> | grep libwrap
-</pre><div class="para">
+ </div><pre class="screen">ldd <binary-name> | 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>.
@@ -1939,14 +1850,13 @@ session required pam_unix.so
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" title="2.5.1.1. Advantages of TCP Wrappers" id="sect-Security_Guide-TCP_Wrappers-Advantages_of_TCP_Wrappers"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.5.1.1. Advantages of TCP Wrappers</h4></div></div></div><div class="para">
+[root at myServer ~]#</pre></div><div class="section" title="2.5.1.1. Advantages of TCP Wrappers" id="sect-Security_Guide-TCP_Wrappers-Advantages_of_TCP_Wrappers"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><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 class="listitem"><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 class="section" title="2.5.2. TCP Wrappers Configuration Files" id="sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers_Configuration_Files"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.5.2. TCP Wrappers Configuration Files</h3></div></div></div><div class="para">
+ </div></li></ul></div></div></div><div class="section" title="2.5.2. TCP Wrappers Configuration Files" id="sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers_Configuration_Files"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><div class="para">
<code class="filename">/etc/hosts.allow</code>
@@ -1970,13 +1880,11 @@ session required pam_unix.so
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" title="2.5.2.1. Formatting Access Rules" id="sect-Security_Guide-TCP_Wrappers_Configuration_Files-Formatting_Access_Rules"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.5.2.1. Formatting Access Rules</h4></div></div></div><div class="para">
+ </div><pre class="screen">warning: /etc/hosts.allow, line 20: missing newline or line too long</pre></div><div class="section" title="2.5.2.1. Formatting Access Rules" id="sect-Security_Guide-TCP_Wrappers_Configuration_Files-Formatting_Access_Rules"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><div class="para">
+ </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 class="listitem"><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-Formatting_Access_Rules-Operators" title="2.5.2.1.4. Operators">Section 2.5.2.1.4, “Operatorsâ€</a>) to allow greater flexibility.
</div></li><li class="listitem"><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-Formatting_Access_Rules-Operators" title="2.5.2.1.4. Operators">Section 2.5.2.1.4, “Operatorsâ€</a> to allow greater flexibility.
@@ -1994,17 +1902,15 @@ session required pam_unix.so
<a class="xref" href="#sect-Security_Guide-TCP_Wrappers_Configuration_Files-Option_Fields" title="2.5.2.2. Option Fields">Section 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 : .example.com
-</pre><div class="para">
+ </div><pre class="screen">vsftpd : .example.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">
+ </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" title="2.5.2.2. Option Fields">Section 2.5.2.2, “Option Fieldsâ€</a> for a more detailed look at available options.
- </div><div class="section" title="2.5.2.1.1. Wildcards" id="sect-Security_Guide-Formatting_Access_Rules-Wildcards"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.5.2.1.1. Wildcards</h5></div></div></div><div class="para">
+ </div><div class="section" title="2.5.2.1.1. Wildcards" id="sect-Security_Guide-Formatting_Access_Rules-Wildcards"><div class="titlepage"><div><div keep-together.within-column="always"><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:
@@ -2020,73 +1926,62 @@ session required pam_unix.so
<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" title="2.5.2.1.2. Patterns" id="sect-Security_Guide-Formatting_Access_Rules-Patterns"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.5.2.1.2. Patterns</h5></div></div></div><div class="para">
+ </div></div></div><div class="section" title="2.5.2.1.2. Patterns" id="sect-Security_Guide-Formatting_Access_Rules-Patterns"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-Security_Guide-Formatting_Access_Rules-Patterns">2.5.2.1.2. Patterns</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 class="listitem"><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 : .example.com
-</pre></li><li class="listitem"><div class="para">
+ </div><pre class="screen">ALL : .example.com</pre></li><li class="listitem"><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 class="listitem"><div class="para">
+ </div><pre class="screen">ALL : 192.168.</pre></li><li class="listitem"><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">
+ </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 class="listitem"><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 class="listitem"><div class="para">
+ </div><pre class="screen">ALL : [3ffe:505:2:1::]/64</pre></li><li class="listitem"><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 : *.example.com
-</pre></li><li class="listitem"><div class="para">
+ </div><pre class="screen">ALL : *.example.com</pre></li><li class="listitem"><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">
+ </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" title="2.5.2.1.3. Portmap and TCP Wrappers" id="sect-Security_Guide-Formatting_Access_Rules-Portmap_and_TCP_Wrappers"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.5.2.1.3. Portmap and TCP Wrappers</h5></div></div></div><div class="para">
+ </div></div></div><div class="section" title="2.5.2.1.3. Portmap and TCP Wrappers" id="sect-Security_Guide-Formatting_Access_Rules-Portmap_and_TCP_Wrappers"><div class="titlepage"><div><div keep-together.within-column="always"><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" title="2.5.2.1.4. Operators" id="sect-Security_Guide-Formatting_Access_Rules-Operators"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.5.2.1.4. Operators</h5></div></div></div><div class="para">
+ </div></div><div class="section" title="2.5.2.1.4. Operators" id="sect-Security_Guide-Formatting_Access_Rules-Operators"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-Security_Guide-Formatting_Access_Rules-Operators">2.5.2.1.4. Operators</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">
+ </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">
+ </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 class="section" title="2.5.2.2. Option Fields" id="sect-Security_Guide-TCP_Wrappers_Configuration_Files-Option_Fields"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.5.2.2. Option Fields</h4></div></div></div><div class="para">
+ </div></div></div></div><div class="section" title="2.5.2.2. Option Fields" id="sect-Security_Guide-TCP_Wrappers_Configuration_Files-Option_Fields"><div class="titlepage"><div><div keep-together.within-column="always"><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" title="2.5.2.2.1. Logging" id="sect-Security_Guide-Option_Fields-Logging"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.5.2.2.1. Logging</h5></div></div></div><div class="para">
+ </div><div class="section" title="2.5.2.2.1. Logging" id="sect-Security_Guide-Option_Fields-Logging"><div class="titlepage"><div><div keep-together.within-column="always"><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">
+ </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">
+ </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 class="section" title="2.5.2.2.2. Access Control" id="sect-Security_Guide-Option_Fields-Access_Control"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.5.2.2.2. Access Control</h5></div></div></div><div class="para">
+ </div></div></div><div class="section" title="2.5.2.2.2. Access Control" id="sect-Security_Guide-Option_Fields-Access_Control"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-Security_Guide-Option_Fields-Access_Control">2.5.2.2.2. Access Control</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">
+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><div class="section" title="2.5.2.2.3. Shell Commands" id="sect-Security_Guide-Option_Fields-Shell_Commands"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.5.2.2.3. Shell Commands</h5></div></div></div><div class="para">
+ </div></div><div class="section" title="2.5.2.2.3. Shell Commands" id="sect-Security_Guide-Option_Fields-Shell_Commands"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><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.
@@ -2094,16 +1989,14 @@ sshd : client-2.example.com : deny
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 class="listitem"><div class="para">
+ : allow</pre></li><li class="listitem"><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">
+ : 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><div class="section" title="2.5.2.2.4. Expansions" id="sect-Security_Guide-Option_Fields-Expansions"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.5.2.2.4. Expansions</h5></div></div></div><div class="para">
+ </div></div><div class="section" title="2.5.2.2.4. Expansions" id="sect-Security_Guide-Option_Fields-Expansions"><div class="titlepage"><div><div keep-together.within-column="always"><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:
@@ -2135,16 +2028,14 @@ sshd : client-2.example.com : deny
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">
+ : 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">
+: 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" title="2.5.5. Additional Resources">Section 2.5.5, “Additional Resourcesâ€</a> for more information about TCP Wrappers.
- </div></div></div></div><div class="section" title="2.5.3. xinetd" id="sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.5.3. xinetd</h3></div></div></div><div class="para">
+ </div></div></div></div><div class="section" title="2.5.3. xinetd" id="sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd"><div class="titlepage"><div><div keep-together.within-column="always"><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.
@@ -2152,13 +2043,13 @@ sshd : client-2.example.com : deny
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><div class="section" title="2.5.4. xinetd Configuration Files" id="sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd_Configuration_Files"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.5.4. xinetd Configuration Files</h3></div></div></div><div class="para">
+ </div></div><div class="section" title="2.5.4. xinetd Configuration Files" id="sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd_Configuration_Files"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><div class="para">
<code class="filename">/etc/xinetd.conf</code> — The global <code class="systemitem">xinetd</code> configuration file.
</div></li><li class="listitem"><div class="para">
<code class="filename">/etc/xinetd.d/</code> — The directory containing all service-specific files.
- </div></li></ul></div><div class="section" title="2.5.4.1. The /etc/xinetd.conf File" id="sect-Security_Guide-xinetd_Configuration_Files-The_etcxinetd.conf_File"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.5.4.1. The /etc/xinetd.conf File</h4></div></div></div><div class="para">
+ </div></li></ul></div><div class="section" title="2.5.4.1. The /etc/xinetd.conf File" id="sect-Security_Guide-xinetd_Configuration_Files-The_etcxinetd.conf_File"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-xinetd_Configuration_Files-The_etcxinetd.conf_File">2.5.4.1. The /etc/xinetd.conf File</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
{
@@ -2168,8 +2059,7 @@ sshd : client-2.example.com : deny
log_on_failure = HOST
cps = 25 30
}
-includedir /etc/xinetd.d
-</pre><div class="para">
+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 class="listitem"><div class="para">
<code class="option">instances</code> — Specifies the maximum number of simultaneous requests that <code class="systemitem">xinetd</code> can process.
@@ -2185,7 +2075,7 @@ includedir /etc/xinetd.d
<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" title="2.5.4.2. The /etc/xinetd.d/ Directory">Section 2.5.4.2, “The /etc/xinetd.d/ Directoryâ€</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-Altering_xinetd_Configuration_Files-Logging_Options" title="2.5.4.3.1. Logging Options">Section 2.5.4.3.1, “Logging Optionsâ€</a> for further information.
- </div></div></div><div class="section" title="2.5.4.2. The /etc/xinetd.d/ Directory" id="sect-Security_Guide-xinetd_Configuration_Files-The_etcxinetd.d_Directory"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.5.4.2. The /etc/xinetd.d/ Directory</h4></div></div></div><div class="para">
+ </div></div></div><div class="section" title="2.5.4.2. The /etc/xinetd.d/ Directory" id="sect-Security_Guide-xinetd_Configuration_Files-The_etcxinetd.d_Directory"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-xinetd_Configuration_Files-The_etcxinetd.d_Directory">2.5.4.2. The /etc/xinetd.d/ Directory</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.
@@ -2200,8 +2090,7 @@ includedir /etc/xinetd.d
server = /usr/kerberos/sbin/telnetd
log_on_failure += USERID
disable = yes
-}
-</pre><div class="para">
+}</pre><div class="para">
These lines control various aspects of the <code class="command">telnet</code> service:
</div><div class="itemizedlist"><ul><li class="listitem"><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.
@@ -2223,9 +2112,9 @@ includedir /etc/xinetd.d
<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><div class="section" title="2.5.4.3. Altering xinetd Configuration Files" id="sect-Security_Guide-xinetd_Configuration_Files-Altering_xinetd_Configuration_Files"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.5.4.3. Altering xinetd Configuration Files</h4></div></div></div><div class="para">
+ </div></div><div class="section" title="2.5.4.3. Altering xinetd Configuration Files" id="sect-Security_Guide-xinetd_Configuration_Files-Altering_xinetd_Configuration_Files"><div class="titlepage"><div><div keep-together.within-column="always"><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" title="2.5.4.3.1. Logging Options" id="sect-Security_Guide-Altering_xinetd_Configuration_Files-Logging_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.5.4.3.1. Logging Options</h5></div></div></div><div class="para">
+ </div><div class="section" title="2.5.4.3.1. Logging Options" id="sect-Security_Guide-Altering_xinetd_Configuration_Files-Logging_Options"><div class="titlepage"><div><div keep-together.within-column="always"><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:
@@ -2243,7 +2132,7 @@ includedir /etc/xinetd.d
<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 class="section" title="2.5.4.3.2. Access Control Options" id="sect-Security_Guide-Altering_xinetd_Configuration_Files-Access_Control_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.5.4.3.2. Access Control Options</h5></div></div></div><div class="para">
+ </div></div><div class="section" title="2.5.4.3.2. Access Control Options" id="sect-Security_Guide-Altering_xinetd_Configuration_Files-Access_Control_Options"><div class="titlepage"><div><div keep-together.within-column="always"><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" title="2.5.2. TCP Wrappers Configuration Files">Section 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.
@@ -2277,16 +2166,13 @@ includedir /etc/xinetd.d
no_access = 172.16.45.0/24
log_on_success += PID HOST EXIT
access_times = 09:45-16:15
-}
-</pre><div class="para">
+}</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">
+ </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">
+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:
@@ -2296,7 +2182,7 @@ Sep 7 14:58:33 localhost xinetd[5283]: EXIT: telnet status=0 pid=5285 duration=
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><div class="section" title="2.5.4.3.3. Binding and Redirection Options" id="sect-Security_Guide-Altering_xinetd_Configuration_Files-Binding_and_Redirection_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.5.4.3.3. Binding and Redirection Options</h5></div></div></div><div class="para">
+ </div></div></div><div class="section" title="2.5.4.3.3. Binding and Redirection Options" id="sect-Security_Guide-Altering_xinetd_Configuration_Files-Binding_and_Redirection_Options"><div class="titlepage"><div><div keep-together.within-column="always"><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.
@@ -2319,12 +2205,11 @@ Sep 7 14:58:33 localhost xinetd[5283]: EXIT: telnet status=0 pid=5285 duration=
log_on_failure += USERID
bind = 123.123.123.123
redirect = 10.0.1.13 23
-}
-</pre><div class="para">
+}</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><div class="section" title="2.5.4.3.4. Resource Management Options" id="sect-Security_Guide-Altering_xinetd_Configuration_Files-Resource_Management_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.5.4.3.4. Resource Management Options</h5></div></div></div><div class="para">
+ </div></div><div class="section" title="2.5.4.3.4. Resource Management Options" id="sect-Security_Guide-Altering_xinetd_Configuration_Files-Resource_Management_Options"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><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.
@@ -2336,9 +2221,9 @@ Sep 7 14:58:33 localhost xinetd[5283]: EXIT: telnet status=0 pid=5285 duration=
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></div></div><div class="section" title="2.5.5. Additional Resources" id="sect-Security_Guide-TCP_Wrappers_and_xinetd-Additional_Resources"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.5.5. Additional Resources</h3></div></div></div><div class="para">
+ </div></div></div></div><div class="section" title="2.5.5. Additional Resources" id="sect-Security_Guide-TCP_Wrappers_and_xinetd-Additional_Resources"><div class="titlepage"><div><div keep-together.within-column="always"><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" title="2.5.5.1. Installed TCP Wrappers Documentation" id="sect-Security_Guide-Additional_Resources-Installed_TCP_Wrappers_Documentation"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.5.5.1. Installed TCP Wrappers Documentation</h4></div></div></div><div class="para">
+ </div><div class="section" title="2.5.5.1. Installed TCP Wrappers Documentation" id="sect-Security_Guide-Additional_Resources-Installed_TCP_Wrappers_Documentation"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><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.
@@ -2354,29 +2239,29 @@ Sep 7 14:58:33 localhost xinetd[5283]: EXIT: telnet status=0 pid=5285 duration=
<code class="command">man hosts_options</code> — The man page for the TCP Wrappers options fields.
</div></li><li class="listitem"><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 class="section" title="2.5.5.2. Useful TCP Wrappers Websites" id="sect-Security_Guide-Additional_Resources-Useful_TCP_Wrappers_Websites"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.5.5.2. Useful TCP Wrappers Websites</h4></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ </div></li></ul></div></dd></dl></div></li></ul></div></div><div class="section" title="2.5.5.2. Useful TCP Wrappers Websites" id="sect-Security_Guide-Additional_Resources-Useful_TCP_Wrappers_Websites"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><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 class="listitem"><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><div class="section" title="2.5.5.3. Related Books" id="sect-Security_Guide-Additional_Resources-Related_Books"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.5.5.3. Related Books</h4></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ </div></li></ul></div></div><div class="section" title="2.5.5.3. Related Books" id="sect-Security_Guide-Additional_Resources-Related_Books"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><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></div></div><div xml:lang="en-US" class="section" title="2.6. Kerberos" id="sect-Security_Guide-Kerberos" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.6. Kerberos</h2></div></div></div><div class="para">
+ </div></li></ul></div></div></div></div><div xml:lang="en-US" class="section" title="2.6. Kerberos" id="sect-Security_Guide-Kerberos" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sect-Security_Guide-Kerberos">2.6. Kerberos</h2></div></div></div><div class="para">
System security and integrity within a network can be unwieldy. It can occupy the time of several administrators just to keep track of what services are being run on a network and the manner in which these services are used.
</div><div class="para">
Further, authenticating users to network services can prove dangerous when the method used by the protocol is inherently insecure, as evidenced by the transfer of unencrypted passwords over a network using the traditional FTP and Telnet protocols.
</div><div class="para">
Kerberos is a way to eliminate the need for protocols that allow unsafe methods of authentication, thereby enhancing overall network security.
- </div><div class="section" title="2.6.1. What is Kerberos?" id="sect-Security_Guide-Kerberos-What_is_Kerberos"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.6.1. What is Kerberos?</h3></div></div></div><div class="para">
- Kerberos is a network authentication protocol created by MIT, and uses symmetric-key cryptography<sup>[<a id="id3440357" href="#ftn.id3440357" class="footnote">14</a>]</sup> to authenticate users to network services, which means passwords are never actually sent over the network.
+ </div><div class="section" title="2.6.1. What is Kerberos?" id="sect-Security_Guide-Kerberos-What_is_Kerberos"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Kerberos-What_is_Kerberos">2.6.1. What is Kerberos?</h3></div></div></div><div class="para">
+ Kerberos is a network authentication protocol created by MIT, and uses symmetric-key cryptography<sup>[<a id="id2824038" href="#ftn.id2824038" class="footnote">14</a>]</sup> to authenticate users to network services, which means passwords are never actually sent over the network.
</div><div class="para">
Consequently, when users authenticate to network services using Kerberos, unauthorized users attempting to gather passwords by monitoring network traffic are effectively thwarted.
- </div><div class="section" title="2.6.1.1. Advantages of Kerberos" id="sect-Security_Guide-What_is_Kerberos-Advantages_of_Kerberos"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.6.1.1. Advantages of Kerberos</h4></div></div></div><div class="para">
+ </div><div class="section" title="2.6.1.1. Advantages of Kerberos" id="sect-Security_Guide-What_is_Kerberos-Advantages_of_Kerberos"><div class="titlepage"><div><div keep-together.within-column="always"><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">
Most conventional network services use password-based authentication schemes. Such schemes require a user to authenticate to a given network server by supplying their username and password. Unfortunately, the transmission of authentication information for many services is unencrypted. For such a scheme to be secure, the network has to be inaccessible to outsiders, and all computers and users on the network must be trusted and trustworthy.
</div><div class="para">
Even if this is the case, a network that is connected to the Internet can no longer be assumed to be secure. Any attacker who gains access to the network can use a simple packet analyzer, also known as a packet sniffer, to intercept usernames and passwords, compromising user accounts and the integrity of the entire security infrastructure.
</div><div class="para">
The primary design goal of Kerberos is to eliminate the transmission of unencrypted passwords across the network. If used properly, Kerberos effectively eliminates the threat that packet sniffers would otherwise pose on a network.
- </div></div><div class="section" title="2.6.1.2. Disadvantages of Kerberos" id="sect-Security_Guide-What_is_Kerberos-Disadvantages_of_Kerberos"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.6.1.2. Disadvantages of Kerberos</h4></div></div></div><div class="para">
+ </div></div><div class="section" title="2.6.1.2. Disadvantages of Kerberos" id="sect-Security_Guide-What_is_Kerberos-Disadvantages_of_Kerberos"><div class="titlepage"><div><div keep-together.within-column="always"><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">
Although Kerberos removes a common and severe security threat, it may be difficult to implement for a variety of reasons:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
Migrating user passwords from a standard UNIX password database, such as <code class="filename">/etc/passwd</code> or <code class="filename">/etc/shadow</code>, to a Kerberos password database can be tedious, as there is no automated mechanism to perform this task. Refer to Question 2.23 in the online Kerberos FAQ:
@@ -2390,7 +2275,7 @@ Sep 7 14:58:33 localhost xinetd[5283]: EXIT: telnet status=0 pid=5285 duration=
For an application to use Kerberos, its source must be modified to make the appropriate calls into the Kerberos libraries. Applications modified in this way are considered to be <em class="firstterm">Kerberos-aware</em>, or <em class="firstterm">kerberized</em>. For some applications, this can be quite problematic due to the size of the application or its design. For other incompatible applications, changes must be made to the way in which the server and client communicate. Again, this may require extensive programming. Closed-source applications that do not have Kerberos support by default are often the most problematic.
</div></li><li class="listitem"><div class="para">
Kerberos is an all-or-nothing solution. If Kerberos is used on the network, any unencrypted passwords transferred to a non-Kerberos aware service is at risk. Thus, the network gains no benefit from the use of Kerberos. To secure a network with Kerberos, one must either use Kerberos-aware versions of <span class="emphasis"><em>all</em></span> client/server applications that transmit passwords unencrypted, or not use <span class="emphasis"><em>any</em></span> such client/server applications at all.
- </div></li></ul></div></div></div><div class="section" title="2.6.2. Kerberos Terminology" id="sect-Security_Guide-Kerberos-Kerberos_Terminology"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.6.2. Kerberos Terminology</h3></div></div></div><div class="para">
+ </div></li></ul></div></div></div><div class="section" title="2.6.2. Kerberos Terminology" id="sect-Security_Guide-Kerberos-Kerberos_Terminology"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Kerberos-Kerberos_Terminology">2.6.2. Kerberos Terminology</h3></div></div></div><div class="para">
Kerberos has its own terminology to define various aspects of the service. Before learning how Kerberos works, it is important to learn the following terms.
</div><div class="variablelist"><dl><dt><span class="term">authentication server (AS)</span></dt><dd><div class="para">
A server that issues tickets for a desired service which are in turn given to users for access to the service. The AS responds to requests from clients who do not have or do not send credentials with a request. It is usually used to gain access to the ticket-granting server (TGS) service by issuing a ticket-granting ticket (TGT). The AS usually runs on the same host as the key distribution center (KDC).
@@ -2432,7 +2317,7 @@ Sep 7 14:58:33 localhost xinetd[5283]: EXIT: telnet status=0 pid=5285 duration=
A special ticket that allows the client to obtain additional tickets without applying for them from the KDC.
</div></dd><dt><span class="term">unencrypted password</span></dt><dd><div class="para">
A plain text, human-readable password.
- </div></dd></dl></div></div><div class="section" title="2.6.3. How Kerberos Works" id="sect-Security_Guide-Kerberos-How_Kerberos_Works"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.6.3. How Kerberos Works</h3></div></div></div><div class="para">
+ </div></dd></dl></div></div><div class="section" title="2.6.3. How Kerberos Works" id="sect-Security_Guide-Kerberos-How_Kerberos_Works"><div class="titlepage"><div><div keep-together.within-column="always"><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 differs from username/password authentication methods. Instead of authenticating each user to each network service, Kerberos uses symmetric encryption and a trusted third party (a KDC), to authenticate users to a suite of network services. When a user authenticates to the KDC, the KDC sends a ticket specific to that session back to the user's machine, and any Kerberos-aware services look for the ticket on the user's machine rather than requiring the user to authenticate using a password.
</div><div class="para">
When a user on a Kerberos-aware network logs in to their workstation, their principal is sent to the KDC as part of a request for a TGT from the Authentication Server. This request can be sent by the log-in program so that it is transparent to the user, or can be sent by the <code class="command">kinit</code> program after the user logs in.
@@ -2460,11 +2345,11 @@ Sep 7 14:58:33 localhost xinetd[5283]: EXIT: telnet status=0 pid=5285 duration=
You should ensure that the DNS entries and hosts on the network are all properly configured. Refer to the <em class="citetitle">Kerberos V5 System Administrator's Guide</em> in <code class="filename">/usr/share/doc/krb5-server-<em class="replaceable"><code><version-number></code></em></code> for more information (where <em class="replaceable"><code><version-number></code></em> is the version number of the <code class="filename">krb5-server</code> package installed on your system).
</div></li></ul></div>
- </div></div></div><div class="section" title="2.6.4. Kerberos and PAM" id="sect-Security_Guide-Kerberos-Kerberos_and_PAM"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.6.4. Kerberos and PAM</h3></div></div></div><div class="para">
+ </div></div></div><div class="section" title="2.6.4. Kerberos and PAM" id="sect-Security_Guide-Kerberos-Kerberos_and_PAM"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Kerberos-Kerberos_and_PAM">2.6.4. Kerberos and PAM</h3></div></div></div><div class="para">
Kerberos-aware services do not currently make use of Pluggable Authentication Modules (PAM) — these services bypass PAM completely. However, applications that use PAM can make use of Kerberos for authentication if the <code class="filename">pam_krb5</code> module (provided in the <code class="filename">pam_krb5</code> package) is installed. The <code class="filename">pam_krb5</code> package contains sample configuration files that allow services such as <code class="command">login</code> and <code class="command">gdm</code> to authenticate users as well as obtain initial credentials using their passwords. If access to network servers is always performed using Kerberos-aware services or services that use GSS-API, such as IMAP, the network can be considered reasonably safe.
</div><div class="important"><h2>Important</h2><div class="para">
Administrators should be careful not to allow users to authenticate to most network services using Kerberos passwords. Many protocols used by these services do not encrypt the password before sending it over the network, destroying the benefits of the Kerberos system. For example, users should not be allowed to authenticate to Telnet services with the same password they use for Kerberos authentication.
- </div></div></div><div class="section" title="2.6.5. Configuring a Kerberos 5 Server" id="sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Server"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.6.5. Configuring a Kerberos 5 Server</h3></div></div></div><div class="para">
+ </div></div></div><div class="section" title="2.6.5. Configuring a Kerberos 5 Server" id="sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Server"><div class="titlepage"><div><div keep-together.within-column="always"><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">
When setting up Kerberos, install the KDC first. If it is necessary to set up slave servers, install the master first.
</div><div class="para">
To configure the first Kerberos KDC, follow these steps:
@@ -2478,13 +2363,11 @@ Sep 7 14:58:33 localhost xinetd[5283]: EXIT: telnet status=0 pid=5285 duration=
Edit the <code class="filename">/etc/krb5.conf</code> and <code class="filename">/var/kerberos/krb5kdc/kdc.conf</code> configuration files to reflect the realm name and domain-to-realm mappings. A simple realm can be constructed by replacing instances of <em class="replaceable"><code>EXAMPLE.COM</code></em> and <em class="replaceable"><code>example.com</code></em> with the correct domain name — being certain to keep uppercase and lowercase names in the correct format — and by changing the KDC from <em class="replaceable"><code>kerberos.example.com</code></em> to the name of the Kerberos server. By convention, all realm names are uppercase and all DNS hostnames and domain names are lowercase. For full details about the formats of these configuration files, refer to their respective man pages.
</div></li><li class="step" title="Step 4"><div class="para">
Create the database using the <code class="command">kdb5_util</code> utility from a shell prompt:
- </div><pre class="screen">/usr/kerberos/sbin/kdb5_util create -s
-</pre><div class="para">
+ </div><pre class="screen">/usr/kerberos/sbin/kdb5_util create -s</pre><div class="para">
The <code class="command">create</code> command creates the database that stores keys for the Kerberos realm. The <code class="command">-s</code> switch forces creation of a <em class="firstterm">stash</em> file in which the master server key is stored. If no stash file is present from which to read the key, the Kerberos server (<code class="command">krb5kdc</code>) prompts the user for the master server password (which can be used to regenerate the key) every time it starts.
</div></li><li class="step" title="Step 5"><div class="para">
Edit the <code class="filename">/var/kerberos/krb5kdc/kadm5.acl</code> file. This file is used by <code class="command">kadmind</code> to determine which principals have administrative access to the Kerberos database and their level of access. Most organizations can get by with a single line:
- </div><pre class="screen">*/admin at EXAMPLE.COMÂ Â *
-</pre><div class="para">
+ </div><pre class="screen">*/admin at EXAMPLE.COMÂ Â *</pre><div class="para">
Most users are represented in the database by a single principal (with a <span class="emphasis"><em>NULL</em></span>, or empty, instance, such as <span class="emphasis"><em>joe at EXAMPLE.COM</em></span>). In this configuration, users with a second principal with an instance of <span class="emphasis"><em>admin</em></span> (for example, <span class="emphasis"><em>joe/admin at EXAMPLE.COM</em></span>) are able to wield full power over the realm's Kerberos database.
</div><div class="para">
After <code class="command">kadmind</code> has been started on the server, any user can access its services by running <code class="command">kadmin</code> on any of the clients or servers in the realm. However, only users listed in the <code class="filename">kadm5.acl</code> file can modify the database in any way, except for changing their own passwords.
@@ -2492,13 +2375,11 @@ Sep 7 14:58:33 localhost xinetd[5283]: EXIT: telnet status=0 pid=5285 duration=
The <code class="command">kadmin</code> utility communicates with the <code class="command">kadmind</code> server over the network, and uses Kerberos to handle authentication. Consequently, the first principal must already exist before connecting to the server over the network to administer it. Create the first principal with the <code class="command">kadmin.local</code> command, which is specifically designed to be used on the same host as the KDC and does not use Kerberos for authentication.
</div></div><div class="para">
Type the following <code class="command">kadmin.local</code> command at the KDC terminal to create the first principal:
- </div><pre class="screen">/usr/kerberos/sbin/kadmin.local -q "addprinc <em class="replaceable"><code>username</code></em>/admin"
-</pre></li><li class="step" title="Step 6"><div class="para">
+ </div><pre class="screen">/usr/kerberos/sbin/kadmin.local -q "addprinc <em class="replaceable"><code>username</code></em>/admin"</pre></li><li class="step" title="Step 6"><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 class="step" title="Step 7"><div class="para">
+/sbin/service krb524 start</pre></li><li class="step" title="Step 7"><div class="para">
Add principals for the users using the <code class="command">addprinc</code> command within <code class="command">kadmin</code>. <code class="command">kadmin</code> and <code class="command">kadmin.local</code> are command line interfaces to the KDC. As such, many commands — such as <code class="command">addprinc</code> — are available after launching the <code class="command">kadmin</code> program. Refer to the <code class="command">kadmin</code> man page for more information.
</div></li><li class="step" title="Step 8"><div class="para">
Verify that the KDC is issuing tickets. First, run <code class="command">kinit</code> to obtain a ticket and store it in a credential cache file. Next, use <code class="command">klist</code> to view the list of credentials in the cache and use <code class="command">kdestroy</code> to destroy the cache and the credentials it contains.
@@ -2506,7 +2387,7 @@ Sep 7 14:58:33 localhost xinetd[5283]: EXIT: telnet status=0 pid=5285 duration=
By default, <code class="command">kinit</code> attempts to authenticate using the same system login username (not the Kerberos server). If that username does not correspond to a principal in the Kerberos database, <code class="command">kinit</code> issues an error message. If that happens, supply <code class="command">kinit</code> with the name of the correct principal as an argument on the command line (<code class="command">kinit <em class="replaceable"><code><principal></code></em></code>).
</div></div></li></ol></div><div class="para">
Once these steps are completed, the Kerberos server should be up and running.
- </div></div><div class="section" title="2.6.6. Configuring a Kerberos 5 Client" id="sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Client"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.6.6. Configuring a Kerberos 5 Client</h3></div></div></div><div class="para">
+ </div></div><div class="section" title="2.6.6. Configuring a Kerberos 5 Client" id="sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Client"><div class="titlepage"><div><div keep-together.within-column="always"><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">
Setting up a Kerberos 5 client is less involved than setting up a server. At a minimum, install the client packages and provide each client with a valid <code class="filename">krb5.conf</code> configuration file. While <code class="command">ssh</code> and <code class="command">slogin</code> are the preferred method of remotely logging in to client systems, Kerberized versions of <code class="command">rsh</code> and <code class="command">rlogin</code> are still available, though deploying them requires that a few more configuration changes be made.
</div><div class="procedure"><ol class="1"><li class="step" title="Step 1"><div class="para">
Be sure that time synchronization is in place between the Kerberos client and the KDC. Refer to <a class="xref" href="#sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Server" title="2.6.5. Configuring a Kerberos 5 Server">Section 2.6.5, “Configuring a Kerberos 5 Serverâ€</a> for more information. In addition, verify that DNS is working properly on the Kerberos client before configuring the Kerberos client programs.
@@ -2516,11 +2397,9 @@ Sep 7 14:58:33 localhost xinetd[5283]: EXIT: telnet status=0 pid=5285 duration=
Before a workstation in the realm can use Kerberos to authenticate users who connect using <code class="command">ssh</code> or Kerberized <code class="command">rsh</code> or <code class="command">rlogin</code>, it must have its own host principal in the Kerberos database. The <code class="command">sshd</code>, <code class="command">kshd</code>, and <code class="command">klogind</code> server programs all need access to the keys for the <span class="emphasis"><em>host</em></span> service's principal. Additionally, in order to use the kerberized <code class="command">rsh</code> and <code class="command">rlogin</code> services, that workstation must have the <code class="filename">xinetd</code> package installed.
</div><div class="para">
Using <code class="command">kadmin</code>, add a host principal for the workstation on the KDC. The instance in this case is the hostname of the workstation. Use the <code class="command">-randkey</code> option for the <code class="command">kadmin</code>'s <code class="command">addprinc</code> command to create the principal and assign it a random key:
- </div><pre class="screen">addprinc -randkey host/<em class="replaceable"><code>blah.example.com</code></em>
-</pre><div class="para">
+ </div><pre class="screen">addprinc -randkey host/<em class="replaceable"><code>blah.example.com</code></em></pre><div class="para">
Now that the principal has been created, keys can be extracted for the workstation by running <code class="command">kadmin</code> <span class="emphasis"><em>on the workstation itself</em></span>, and using the <code class="command">ktadd</code> command within <code class="command">kadmin</code>:
- </div><pre class="screen">ktadd -k /etc/krb5.keytab host/<em class="replaceable"><code>blah.example.com</code></em>
-</pre></li><li class="step" title="Step 4"><div class="para">
+ </div><pre class="screen">ktadd -k /etc/krb5.keytab host/<em class="replaceable"><code>blah.example.com</code></em></pre></li><li class="step" title="Step 4"><div class="para">
To use other kerberized network services, they must first be started. Below is a list of some common kerberized services and instructions about enabling them:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="command">ssh</code> — OpenSSH uses GSS-API to authenticate users to servers if the client's and server's configuration both have <code class="option">GSSAPIAuthentication</code> enabled. If the client also has <code class="option">GSSAPIDelegateCredentials</code> enabled, the user's credentials are made available on the remote system.
@@ -2536,22 +2415,20 @@ Sep 7 14:58:33 localhost xinetd[5283]: EXIT: telnet status=0 pid=5285 duration=
An alternative to <code class="filename">cyrus-imap</code> can be found in the <code class="command">dovecot</code> package, which is also included in Fedora. This package contains an IMAP server but does not, to date, support GSS-API and Kerberos.
</div></li><li class="listitem"><div class="para">
CVS — To use a kerberized CVS server, <code class="command">gserver</code> uses a principal with a root of <code class="computeroutput">cvs</code> and is otherwise identical to the CVS <code class="command">pserver</code>.
- </div></li></ul></div></li></ol></div></div><div class="section" title="2.6.7. Domain-to-Realm Mapping" id="sect-Security_Guide-Kerberos-Domain_to_Realm_Mapping"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.6.7. Domain-to-Realm Mapping</h3></div></div></div><div class="para">
+ </div></li></ul></div></li></ol></div></div><div class="section" title="2.6.7. Domain-to-Realm Mapping" id="sect-Security_Guide-Kerberos-Domain_to_Realm_Mapping"><div class="titlepage"><div><div keep-together.within-column="always"><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">
When a client attempts to access a service running on a particular server, it knows the name of the service (<span class="emphasis"><em>host</em></span>) and the name of the server (<span class="emphasis"><em>foo.example.com</em></span>), but because more than one realm may be deployed on your network, it must guess at the name of the realm in which the service resides.
</div><div class="para">
By default, the name of the realm is taken to be the DNS domain name of the server, upper-cased.
</div><div class="literallayout"><p>foo.example.org → EXAMPLE.ORG<br />
foo.example.com → EXAMPLE.COM<br />
foo.hq.example.com → HQ.EXAMPLE.COM<br />
-<br />
</p></div><div class="para">
In some configurations, this will be sufficient, but in others, the realm name which is derived will be the name of a non-existant realm. In these cases, the mapping from the server's DNS domain name to the name of its realm must be specified in the <span class="emphasis"><em>domain_realm</em></span> section of the client system's <code class="filename">krb5.conf</code>. For example:
</div><pre class="screen">[domain_realm]
.example.com = EXAMPLE.COM
-example.com = EXAMPLE.COM
-</pre><div class="para">
+example.com = EXAMPLE.COM</pre><div class="para">
The above configuration specifies two mappings. The first mapping specifies that any system in the "example.com" DNS domain belongs to the <span class="emphasis"><em>EXAMPLE.COM</em></span> realm. The second specifies that a system with the exact name "example.com" is also in the realm. (The distinction between a domain and a specific host is marked by the presence or lack of an initial ".".) The mapping can also be stored directly in DNS.
- </div></div><div class="section" title="2.6.8. Setting Up Secondary KDCs" id="sect-Security_Guide-Kerberos-Setting_Up_Secondary_KDCs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.6.8. Setting Up Secondary KDCs</h3></div></div></div><div class="para">
+ </div></div><div class="section" title="2.6.8. Setting Up Secondary KDCs" id="sect-Security_Guide-Kerberos-Setting_Up_Secondary_KDCs"><div class="titlepage"><div><div keep-together.within-column="always"><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">
For a number of reasons, you may choose to run multiple KDCs for a given realm. In this scenario, one KDC (the <span class="emphasis"><em>master KDC</em></span>) keeps a writable copy of the realm database and runs <code class="command">kadmind</code> (it is also your realm's <span class="emphasis"><em>admin server</em></span>), and one or more KDCs (<span class="emphasis"><em>slave KDCs</em></span>) keep read-only copies of the database and run <code class="command">kpropd</code>.
</div><div class="para">
The master-slave propagation procedure entails the master KDC dumping its database to a temporary dump file and then transmitting that file to each of its slaves, which then overwrite their previously-received read-only copies of the database with the contents of the dump file.
@@ -2577,8 +2454,7 @@ Entry for principal host/masterkdc.example.com with kvno 3, encryption type DES
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">
+<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>
@@ -2600,29 +2476,25 @@ Entry for principal host/slavekdc.example.com with kvno 3, encryption type DES w
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">
+<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 host/masterkdc.example.com at EXAMPLE.COM > /var/kerberos/krb5kdc/kpropd.acl</code></strong></code><br />
-</p></div><div class="para">
+ </div><div class="literallayout"><p> <code class="computeroutput"><code class="prompt">#</code> <strong class="userinput"><code>echo host/masterkdc.example.com at EXAMPLE.COM > /var/kerberos/krb5kdc/kpropd.acl</code></strong></code></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">
Ensure that the slave KDC's firewall allows the master KDC to contact it using TCP on port 754 (<span class="emphasis"><em>krb5_prop</em></span>), and start the <code class="command">kprop</code> service. Then, double-check that the <code class="command">kadmin</code> service is <span class="emphasis"><em>disabled</em></span>.
</div><div class="para">
Now perform a manual database propagation test by dumping the realm database, on the master KDC, to the default data file which the <code class="command">kprop</code> command will read (<code class="filename">/var/kerberos/krb5kdc/slave_datatrans</code>), and then use the <code class="command">kprop</code> command to transmit its contents to the slave KDC.
- </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">
+ </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></p></div><div class="para">
Using <code class="command">kinit</code>, verify that a client system whose <code class="filename">krb5.conf</code> lists only the slave KDC in its list of KDCs for your realm is now correctly able to obtain initial credentials from the slave KDC.
</div><div class="para">
That done, simply create a script which dumps the realm database and runs the <code class="command">kprop</code> command to transmit the database to each slave KDC in turn, and configure the <code class="command">cron</code> service to run the script periodically.
- </div></div><div class="section" title="2.6.9. Setting Up Cross Realm Authentication" id="sect-Security_Guide-Kerberos-Setting_Up_Cross_Realm_Authentication"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.6.9. Setting Up Cross Realm Authentication</h3></div></div></div><div class="para">
+ </div></div><div class="section" title="2.6.9. Setting Up Cross Realm Authentication" id="sect-Security_Guide-Kerberos-Setting_Up_Cross_Realm_Authentication"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Kerberos-Setting_Up_Cross_Realm_Authentication">2.6.9. Setting Up Cross Realm Authentication</h3></div></div></div><div class="para">
<span class="emphasis"><em>Cross-realm authentication</em></span> is the term which is used to describe situations in which clients (typically users) of one realm use Kerberos to authenticate to services (typically server processes running on a particular server system) which belong to a realm other than their own.
</div><div class="para">
For the simplest case, in order for a client of a realm named <code class="literal">A.EXAMPLE.COM</code> to access a service in the <code class="literal">B.EXAMPLE.COM</code> realm, both realms must share a key for a principal named <code class="literal">krbtgt/B.EXAMPLE.COM at A.EXAMPLE.COM</code>, and both keys must have the same key version number associated with them.
</div><div class="para">
To accomplish this, select a very strong password or passphrase, and create an entry for the principal in both realms using 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"><code>kadmin -r B.EXAMPLE.COM</code></strong></code> <code class="computeroutput"><code class="prompt">kadmin:</code> <strong class="userinput"><code>add_principal krbtgt/B.EXA
MPLE.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">
+ </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"><code>kadmin -r B.EXAMPLE.COM</code></strong></code> <code class="computeroutput"><code class="prompt">kadmin:</code> <strong class="userinput"><code>add_principal krbtgt/B.EXA
MPLE.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></p></div><div class="para">
Use the <code class="command">get_principal</code> command to verify that both entries have matching key version numbers (<code class="literal">kvno</code> values) and encryption types.
</div><div class="important"><h2>Dumping the Database Doesn't Do It</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.
@@ -2636,8 +2508,7 @@ Entry for principal host/slavekdc.example.com with kvno 3, encryption type DES c
Now you face the more conventional problems: the client's system must be configured so that it can properly deduce the realm to which a particular service belongs, and it must be able to determine how to obtain credentials for services in that realm.
</div><div class="para">
First things first: the principal name for a service provided from a specific server system in a given realm typically looks like this:
- </div><div class="literallayout"><p>service/server.example.com at EXAMPLE.COM<br />
-</p></div><div class="para">
+ </div><div class="literallayout"><p>service/server.example.com at EXAMPLE.COM</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>).
@@ -2692,7 +2563,6 @@ Entry for principal host/slavekdc.example.com with kvno 3, encryption type DES c
D.EXAMPLE.COMÂ =Â C.EXAMPLE.COM<br />
}<br />
<br />
-<br />
</p></div><div class="para">
In this example, clients in the <code class="literal">A.EXAMPLE.COM</code> realm can obtain cross-realm credentials for <code class="literal">B.EXAMPLE.COM</code> directly from the <code class="literal">A.EXAMPLE.COM</code> KDC.
</div><div class="para">
@@ -2705,10 +2575,9 @@ Entry for principal host/slavekdc.example.com with kvno 3, encryption type DES c
Clients in the <code class="literal">A.EXAMPLE.COM</code> realm can obtain cross-realm credentials from <code class="literal">B.EXAMPLE.COM</code> realm directly. Without the "." indicating this, the client would instead attempt to use a hierarchical path, in this case:
</div><div class="literallayout"><p> A.EXAMPLE.COM → EXAMPLE.COM → B.EXAMPLE.COM<br />
<br />
-<br />
-</p></div></div></div><div class="section" title="2.6.10. Additional Resources" id="sect-Security_Guide-Kerberos-Additional_Resources"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.6.10. Additional Resources</h3></div></div></div><div class="para">
+</p></div></div></div><div class="section" title="2.6.10. Additional Resources" id="sect-Security_Guide-Kerberos-Additional_Resources"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Kerberos-Additional_Resources">2.6.10. Additional Resources</h3></div></div></div><div class="para">
For more information about Kerberos, refer to the following resources.
- </div><div class="section" title="2.6.10.1. Installed Kerberos Documentation" id="sect-Security_Guide-Additional_Resources-Installed_Kerberos_Documentation"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.6.10.1. Installed Kerberos Documentation</h4></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ </div><div class="section" title="2.6.10.1. Installed Kerberos Documentation" id="sect-Security_Guide-Additional_Resources-Installed_Kerberos_Documentation"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><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 class="listitem"><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).
@@ -2734,7 +2603,7 @@ Entry for principal host/slavekdc.example.com with kvno 3, encryption type DES c
<code class="command">man krb5.conf</code> — Describes the format and options available within the configuration file for the Kerberos V5 library.
</div></li><li class="listitem"><div class="para">
<code class="command">man kdc.conf</code> — Describes the format and options available within the configuration file for the Kerberos V5 AS and KDC.
- </div></li></ul></div></dd></dl></div></li></ul></div></div><div class="section" title="2.6.10.2. Useful Kerberos Websites" id="sect-Security_Guide-Additional_Resources-Useful_Kerberos_Websites"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.6.10.2. Useful Kerberos Websites</h4></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ </div></li></ul></div></dd></dl></div></li></ul></div></div><div class="section" title="2.6.10.2. Useful Kerberos Websites" id="sect-Security_Guide-Additional_Resources-Useful_Kerberos_Websites"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><div class="para">
<a href="http://web.mit.edu/kerberos/www/">http://web.mit.edu/kerberos/www/</a> — <em class="citetitle">Kerberos: The Network Authentication Protocol</em> webpage from MIT.
</div></li><li class="listitem"><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> — The Kerberos Frequently Asked Questions (FAQ).
@@ -2746,25 +2615,25 @@ Entry for principal host/slavekdc.example.com with kvno 3, encryption type DES c
<a href="http://www.ornl.gov/~jar/HowToKerb.html">http://www.ornl.gov/~jar/HowToKerb.html</a> — <em class="citetitle">How to Kerberize your site</em> is a good reference for kerberizing a network.
</div></li><li class="listitem"><div class="para">
<a href="http://www.networkcomputing.com/netdesign/kerb1.html">http://www.networkcomputing.com/netdesign/kerb1.html</a> — <em class="citetitle">Kerberos Network Design Manual</em> is a thorough overview of the Kerberos system.
- </div></li></ul></div></div></div></div><div xml:lang="en-US" class="section" title="2.7. Virtual Private Networks (VPNs)" id="sect-Security_Guide-Virtual_Private_Networks_VPNs" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.7. Virtual Private Networks (VPNs)</h2></div></div></div><div class="para">
+ </div></li></ul></div></div></div></div><div xml:lang="en-US" class="section" title="2.7. Virtual Private Networks (VPNs)" id="sect-Security_Guide-Virtual_Private_Networks_VPNs" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><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" title="2.7.1. How Does a VPN Work?" id="sect-Security_Guide-Virtual_Private_Networks_VPNs-How_Does_a_VPN_Work"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.7.1. How Does a VPN Work?</h3></div></div></div><div class="para">
+ </div><div class="section" title="2.7.1. How Does a VPN Work?" id="sect-Security_Guide-Virtual_Private_Networks_VPNs-How_Does_a_VPN_Work"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="section" title="2.7.2. VPNs and Fedora" id="sect-Security_Guide-Virtual_Private_Networks_VPNs-VPNs_and_PROD"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.7.2. VPNs and Fedora</h3></div></div></div><div class="para">
+ </div></div><div class="section" title="2.7.2. VPNs and Fedora" id="sect-Security_Guide-Virtual_Private_Networks_VPNs-VPNs_and_PROD"><div class="titlepage"><div><div keep-together.within-column="always"><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><div class="section" title="2.7.3. IPsec" id="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.7.3. IPsec</h3></div></div></div><div class="para">
+ </div></div><div class="section" title="2.7.3. IPsec" id="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec"><div class="titlepage"><div><div keep-together.within-column="always"><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><div class="section" title="2.7.4. Creating an IPsec Connection" id="sect-Security_Guide-Virtual_Private_Networks_VPNs-Creating_an_IPsec_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.7.4. Creating an <abbr class="abbrev">IPsec</abbr> Connection</h3></div></div></div><div class="para">
+ </div></div><div class="section" title="2.7.4. Creating an IPsec Connection" id="sect-Security_Guide-Virtual_Private_Networks_VPNs-Creating_an_IPsec_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><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.
@@ -2772,7 +2641,7 @@ Entry for principal host/slavekdc.example.com with kvno 3, encryption type DES c
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><div class="section" title="2.7.5. IPsec Installation" id="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Installation"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.7.5. IPsec Installation</h3></div></div></div><div class="para">
+ </div></div><div class="section" title="2.7.5. IPsec Installation" id="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Installation"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><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.
@@ -2786,9 +2655,9 @@ Entry for principal host/slavekdc.example.com with kvno 3, encryption type DES c
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" title="2.7.6. IPsec Host-to-Host Configuration">Section 2.7.6, “IPsec Host-to-Host Configurationâ€</a>.
</div></li><li class="listitem"><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" title="2.7.7. IPsec Network-to-Network Configuration">Section 2.7.7, “IPsec Network-to-Network Configurationâ€</a>.
- </div></li></ul></div></div><div class="section" title="2.7.6. IPsec Host-to-Host Configuration" id="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Host_to_Host_Configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.7.6. IPsec Host-to-Host Configuration</h3></div></div></div><div class="para">
+ </div></li></ul></div></div><div class="section" title="2.7.6. IPsec Host-to-Host Configuration" id="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Host_to_Host_Configuration"><div class="titlepage"><div><div keep-together.within-column="always"><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" title="2.7.6.1. Host-to-Host Connection" id="sect-Security_Guide-IPsec_Host_to_Host_Configuration-Host_to_Host_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.7.6.1. Host-to-Host Connection</h4></div></div></div><div class="para">
+ </div><div class="section" title="2.7.6.1. Host-to-Host Connection" id="sect-Security_Guide-IPsec_Host_to_Host_Configuration-Host_to_Host_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><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:
@@ -2814,14 +2683,12 @@ Entry for principal host/slavekdc.example.com with kvno 3, encryption type DES c
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">
+ </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">
+ 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 same LAN.
@@ -2841,14 +2708,13 @@ Entry for principal host/slavekdc.example.com with kvno 3, encryption type DES c
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 class="listitem"><div class="para">
+ </div><pre class="screen">[root at myServer ~]# service network restart</pre></li><li class="listitem"><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 class="listitem"><div class="para">
Repeat the entire procedure for the other host. It is essential that the same keys from step <a class="xref" href="#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="#figu-Security_Guide-Host_to_Host_Connection-IPsec_Connection" title="Figure 2.10. IPsec Connection">Figure 2.10, “IPsec Connectionâ€</a>.
- </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/fed-ipsec_host2host.png" width="444" alt="IPsec Connection" /><div class="longdesc"><div class="para">
+ </div><div class="figure" title="Figure 2.10. IPsec Connection" id="figu-Security_Guide-Host_to_Host_Connection-IPsec_Connection"><div class="figure-contents"><div class="mediaobject"><img src="images/fed-ipsec_host2host.png" width="444" alt="IPsec Connection" /><div class="longdesc"><div class="para">
IPsec Connection
</div></div></div></div><h6>Figure 2.10. IPsec Connection</h6></div><br class="figure-break" /><div class="para">
The following files are created when the <abbr class="abbrev">IPsec</abbr> connection is configured:
@@ -2864,7 +2730,7 @@ Entry for principal host/slavekdc.example.com with kvno 3, encryption type DES c
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 class="section" title="2.7.6.2. Manual IPsec Host-to-Host Configuration" id="sect-Security_Guide-IPsec_Host_to_Host_Configuration-Manual_IPsec_Host_to_Host_Configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.7.6.2. Manual <abbr class="abbrev">IPsec</abbr> Host-to-Host Configuration</h4></div></div></div><div class="para">
+ </div></div><div class="section" title="2.7.6.2. Manual IPsec Host-to-Host Configuration" id="sect-Security_Guide-IPsec_Host_to_Host_Configuration-Manual_IPsec_Host_to_Host_Configuration"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><div class="para">
The IP address of each host
@@ -2884,16 +2750,13 @@ Entry for principal host/slavekdc.example.com with kvno 3, encryption type DES c
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">
+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">
+ </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">
+ </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.
@@ -2906,8 +2769,7 @@ IKE_METHOD=PSK
authentication_method pre_shared_key;
dh_group 2 ;
}
-}
-</pre><div class="para">
+}</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.
@@ -2923,7 +2785,7 @@ IKE_METHOD=PSK
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" title="2.7.6.2.1. The Racoon Configuration File" id="sect-Security_Guide-Manual_IPsec_Host_to_Host_Configuration-The_Racoon_Configuration_File"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.7.6.2.1. The Racoon Configuration File</h5></div></div></div><div class="para">
+ </div></dd></dl></div><div class="section" title="2.7.6.2.1. The Racoon Configuration File" id="sect-Security_Guide-Manual_IPsec_Host_to_Host_Configuration-The_Racoon_Configuration_File"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-Security_Guide-Manual_IPsec_Host_to_Host_Configuration-The_Racoon_Configuration_File">2.7.6.2.1. The Racoon Configuration File</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.
@@ -2940,8 +2802,7 @@ sainfo anonymous
authentication_algorithm hmac_sha1, hmac_md5 ;
compression_algorithm deflate ;
}
-include "/etc/racoon/X.X.X.X.conf";
-</pre><div class="para">
+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.
@@ -2957,17 +2818,15 @@ include "/etc/racoon/X.X.X.X.conf";
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">
+ </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></div><div class="section" title="2.7.7. IPsec Network-to-Network Configuration" id="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Network_to_Network_Configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.7.7. IPsec Network-to-Network Configuration</h3></div></div></div><div class="para">
+IP 172.16.45.107 > 172.16.44.192: AH(spi=0x0954ccb6,seq=0xbb): ESP(spi=0x0c9f2164,seq=0xbb)</pre></div></div></div><div class="section" title="2.7.7. IPsec Network-to-Network Configuration" id="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Network_to_Network_Configuration"><div class="titlepage"><div><div keep-together.within-column="always"><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="#figu-Security_Guide-IPsec_Network_to_Network_Configuration-A_network_to_network_IPsec_tunneled_connection" title="Figure 2.11. A network-to-network IPsec tunneled connection">Figure 2.11, “A network-to-network <abbr class="abbrev">IPsec</abbr> tunneled connectionâ€</a> shows a network-to-network <abbr class="abbrev">IPsec</abbr> tunneled connection.
- </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/n-t-n-ipsec-diagram.png" width="444" alt="A network-to-network IPsec tunneled connection" /><div class="longdesc"><div class="para">
+ </div><div class="figure" title="Figure 2.11. A network-to-network IPsec tunneled connection" 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" width="444" 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>Figure 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.
@@ -2985,13 +2844,13 @@ IP 172.16.45.107 > 172.16.44.192: AH(spi=0x0954ccb6,seq=0xbb): ESP(spi=0x0c9f
A fixed encryption key or one automatically generated by <code class="command">racoon</code>
</div></li><li class="listitem"><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" title="2.7.7.1. Network-to-Network (VPN) Connection" id="sect-Security_Guide-IPsec_Network_to_Network_Configuration-Network_to_Network_VPN_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.7.7.1. Network-to-Network (<abbr class="abbrev">VPN</abbr>) Connection</h4></div></div></div><div class="para">
+ </div></li></ul></div><div class="section" title="2.7.7.1. Network-to-Network (VPN) Connection" id="sect-Security_Guide-IPsec_Network_to_Network_Configuration-Network_to_Network_VPN_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><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="#figu-Security_Guide-Network_to_Network_VPN_Connection-Network_to_Network_IPsec" title="Figure 2.12. Network-to-Network IPsec">Figure 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"><div class="figure-contents"><div class="mediaobject"><img src="images/n-t-n-ipsec-diagram.png" width="444" alt="Network-to-Network IPsec" /><div class="longdesc"><div class="para">
+ </div><div class="figure" title="Figure 2.12. Network-to-Network IPsec" 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" width="444" alt="Network-to-Network IPsec" /><div class="longdesc"><div class="para">
Network-to-Network IPsec
</div></div></div></div><h6>Figure 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.
@@ -3023,7 +2882,7 @@ IP 172.16.45.107 > 172.16.44.192: AH(spi=0x0954ccb6,seq=0xbb): ESP(spi=0x0c9f
<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"><div class="figure-contents"><div class="mediaobject"><img src="images/fed-ipsec_n_to_n_local.png" width="444" alt="Local Network Information" /><div class="longdesc"><div class="para">
+ </div><div class="figure" title="Figure 2.13. Local Network Information" 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" width="444" alt="Local Network Information" /><div class="longdesc"><div class="para">
Local Network Information
</div></div></div></div><h6>Figure 2.13. Local Network Information</h6></div><br class="figure-break" /></li><li class="listitem"><div class="para">
On the <span class="guilabel"><strong>Remote Network</strong></span> page, enter the following information:
@@ -3041,7 +2900,7 @@ IP 172.16.45.107 > 172.16.44.192: AH(spi=0x0954ccb6,seq=0xbb): ESP(spi=0x0c9f
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"><div class="figure-contents"><div class="mediaobject"><img src="images/fed-ipsec_n_to_n_remote.png" width="444" alt="Remote Network Information" /><div class="longdesc"><div class="para">
+ </div><div class="figure" title="Figure 2.14. Remote Network Information" 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" width="444" alt="Remote Network Information" /><div class="longdesc"><div class="para">
Remote Network Information
</div></div></div></div><h6>Figure 2.14. Remote Network Information</h6></div><br class="figure-break" /></li><li class="listitem"><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>.
@@ -3055,10 +2914,9 @@ IP 172.16.45.107 > 172.16.44.192: AH(spi=0x0954ccb6,seq=0xbb): ESP(spi=0x0c9f
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 class="listitem"><div class="para">
Use the following command to enable the change:
- </div><pre class="screen">[root at myServer ~]# /sbin/sysctl -p /etc/sysctl.conf
-</pre></li></ol></div></li></ol></div><div class="para">
+ </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 class="section" title="2.7.7.2. Manual IPsec Network-to-Network Configuration" id="sect-Security_Guide-IPsec_Network_to_Network_Configuration-Manual_IPsec_Network_to_Network_Configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.7.7.2. Manual <abbr class="abbrev">IPsec</abbr> Network-to-Network Configuration</h4></div></div></div><div class="para">
+ </div></div><div class="section" title="2.7.7.2. Manual IPsec Network-to-Network Configuration" id="sect-Security_Guide-IPsec_Network_to_Network_Configuration-Manual_IPsec_Network_to_Network_Configuration"><div class="titlepage"><div><div keep-together.within-column="always"><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="para">
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>.
@@ -3071,8 +2929,7 @@ 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">
+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">
Specifies the type of connection.
@@ -3092,11 +2949,9 @@ DST=<em class="replaceable"><code>X.X.X.X</code></em>
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">
+ </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">
+ </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.
@@ -3114,8 +2969,7 @@ sainfo anonymous
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">
+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;
@@ -3126,45 +2980,37 @@ include "/etc/racoon/<em class="replaceable"><code>X.X.X.X</code></em>.conf"
authentication_method pre_shared_key;
dh_group 2 ;
}
-}
-</pre><div class="para">
+}</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 class="listitem"><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 class="listitem"><div class="para">
Use the following command to enable the change:
- </div><pre class="screen">[root at myServer ~] # sysctl -p /etc/sysctl.conf
-</pre></li></ol></div><div class="para">
+ </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">
+ </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">
+ </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">
+ </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></div><div class="section" title="2.7.8. Starting and Stopping an IPsec Connection" id="sect-Security_Guide-Virtual_Private_Networks_VPNs-Starting_and_Stopping_an_IPsec_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.7.8. Starting and Stopping an <abbr class="abbrev">IPsec</abbr> Connection</h3></div></div></div><div class="para">
+ (ipip-proto-4)</pre></div></div><div class="section" title="2.7.8. Starting and Stopping an IPsec Connection" id="sect-Security_Guide-Virtual_Private_Networks_VPNs-Starting_and_Stopping_an_IPsec_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><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">
+ </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">
To stop the connection, use the following command:
- </div><pre class="screen">[root at myServer ~] # /sbin/ifdown <em class="replaceable"><code><nickname></code></em>
-</pre></div></div><div xml:lang="en-US" class="section" title="2.8. Firewalls" id="sect-Security_Guide-Firewalls" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.8. Firewalls</h2></div></div></div><div class="para">
+ </div><pre class="screen">[root at myServer ~] # /sbin/ifdown <em class="replaceable"><code><nickname></code></em></pre></div></div><div xml:lang="en-US" class="section" title="2.8. Firewalls" id="sect-Security_Guide-Firewalls" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sect-Security_Guide-Firewalls">2.8. Firewalls</h2></div></div></div><div class="para">
Information security is commonly thought of as a process and not a product. However, standard security implementations usually employ some form of dedicated mechanism to control access privileges and restrict network resources to users who are authorized, identifiable, and traceable. Fedora includes several tools to assist administrators and security engineers with network-level access control issues.
</div><div class="para">
Firewalls are one of the core components of a network security implementation. Several vendors market firewall solutions catering to all levels of the marketplace: from home users protecting one PC to data center solutions safeguarding vital enterprise information. Firewalls can be stand-alone hardware solutions, such as firewall appliances by Cisco, Nokia, and Sonicwall. Vendors such as Checkpoint, McAfee, and Symantec have also developed proprietary software firewall solutions for home and business markets.
</div><div class="para">
Apart from the differences between hardware and software firewalls, there are also differences in the way firewalls function that separate one solution from another. <a class="xref" href="#tabl-Security_Guide-Firewalls-Firewall_Types" title="Table 2.2. Firewall Types">Table 2.2, “Firewall Typesâ€</a> details three common types of firewalls and how they function:
- </div><div class="table"><div class="table-contents"><table summary="Firewall Types" border="1"><colgroup><col width="10%" /><col width="30%" /><col width="30%" /><col width="30%" /></colgroup><thead><tr><th>
+ </div><div class="table" title="Table 2.2. Firewall Types" id="tabl-Security_Guide-Firewalls-Firewall_Types"><div class="table-contents"><table summary="Firewall Types" border="1"><colgroup><col width="10%" /><col width="30%" /><col width="30%" /><col width="30%" /></colgroup><thead><tr><th>
Method
</th><th>
Description
@@ -3202,30 +3048,29 @@ include "/etc/racoon/<em class="replaceable"><code>X.X.X.X</code></em>.conf"
</td><td>
<table border="0" summary="Simple list" class="simplelist"><tr><td> · Proxies are often application-specific (HTTP, Telnet, etc.), or protocol-restricted (most proxies work with TCP-connected services only) </td></tr><tr><td> · Application services cannot run behind a proxy, so your application servers must use a separate form of network security </td></tr><tr><td> · Proxies can become a network bottleneck, as all requests and transmissions are passed through one source rather than directly from a client to a remote service </td></tr></table>
- </td></tr></tbody></table></div><h6>Table 2.2. Firewall Types</h6></div><br class="table-break" /><div class="section" title="2.8.1. Netfilter and IPTables" id="sect-Security_Guide-Firewalls-Netfilter_and_IPTables"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.8.1. Netfilter and IPTables</h3></div></div></div><div class="para">
+ </td></tr></tbody></table></div><h6>Table 2.2. Firewall Types</h6></div><br class="table-break" /><div class="section" title="2.8.1. Netfilter and IPTables" id="sect-Security_Guide-Firewalls-Netfilter_and_IPTables"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Firewalls-Netfilter_and_IPTables">2.8.1. Netfilter and IPTables</h3></div></div></div><div class="para">
The Linux kernel features a powerful networking subsystem called <em class="firstterm">Netfilter</em>. The Netfilter subsystem provides stateful or stateless packet filtering as well as NAT and IP masquerading services. Netfilter also has the ability to <em class="firstterm">mangle</em> IP header information for advanced routing and connection state management. Netfilter is controlled using the <code class="command">iptables</code> tool.
- </div><div class="section" title="2.8.1.1. IPTables Overview" id="sect-Security_Guide-Netfilter_and_IPTables-IPTables_Overview"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.8.1.1. IPTables Overview</h4></div></div></div><div class="para">
+ </div><div class="section" title="2.8.1.1. IPTables Overview" id="sect-Security_Guide-Netfilter_and_IPTables-IPTables_Overview"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Netfilter_and_IPTables-IPTables_Overview">2.8.1.1. IPTables Overview</h4></div></div></div><div class="para">
The power and flexibility of Netfilter is implemented using the <code class="command">iptables</code> administration tool, a command line tool similar in syntax to its predecessor, <code class="command">ipchains</code>, which Netfilter/iptables replaced in the Linux kernel 2.4 and above.
</div><div class="para">
<code class="command">iptables</code> uses the Netfilter subsystem to enhance network connection, inspection, and processing. <code class="command">iptables</code> features advanced logging, pre- and post-routing actions, network address translation, and port forwarding, all in one command line interface.
</div><div class="para">
This section provides an overview of <code class="command">iptables</code>. For more detailed information, refer to <a class="xref" href="#sect-Security_Guide-IPTables" title="2.9. IPTables">Section 2.9, “IPTablesâ€</a>.
- </div></div></div><div class="section" title="2.8.2. Basic Firewall Configuration" id="sect-Security_Guide-Firewalls-Basic_Firewall_Configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.8.2. Basic Firewall Configuration</h3></div></div></div><div class="para">
+ </div></div></div><div class="section" title="2.8.2. Basic Firewall Configuration" id="sect-Security_Guide-Firewalls-Basic_Firewall_Configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Firewalls-Basic_Firewall_Configuration">2.8.2. Basic Firewall Configuration</h3></div></div></div><div class="para">
Just as a firewall in a building attempts to prevent a fire from spreading, a computer firewall attempts to prevent malicious software from spreading to your computer. It also helps to prevent unauthorized users from accessing your computer.
</div><div class="para">
In a default Fedora installation, a firewall exists between your computer or network and any untrusted networks, for example the Internet. It determines which services on your computer remote users can access. A properly configured firewall can greatly increase the security of your system. It is recommended that you configure a firewall for any Fedora system with an Internet connection.
- </div><div class="section" title="2.8.2.1. Firewall Configuration Tool" id="sect-Security_Guide-Basic_Firewall_Configuration-RHSECLEVELTOOL"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.8.2.1. <span class="application"><strong>Firewall Configuration Tool</strong></span></h4></div></div></div><div class="para">
+ </div><div class="section" title="2.8.2.1. Firewall Configuration Tool" id="sect-Security_Guide-Basic_Firewall_Configuration-RHSECLEVELTOOL"><div class="titlepage"><div><div keep-together.within-column="always"><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">
During the <span class="guilabel"><strong>Firewall Configuration</strong></span> screen of the Fedora installation, you were given the option to enable a basic firewall as well as to allow specific devices, incoming services, and ports.
</div><div class="para">
After installation, you can change this preference by using the <span class="application"><strong>Firewall Configuration Tool</strong></span>.
</div><div class="para">
To start this application, use the following command:
- </div><pre class="screen">[root at myServer ~] # system-config-firewall
-</pre><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/fed-firewall_config.png" width="444" alt="Firewall Configuration Tool" /><div class="longdesc"><div class="para">
+ </div><pre class="screen">[root at myServer ~] # system-config-firewall</pre><div class="figure" title="Figure 2.15. Firewall Configuration Tool" id="figu-Security_Guide-RHSECLEVELTOOL-RHSECLEVELTOOL"><div class="figure-contents"><div class="mediaobject"><img src="images/fed-firewall_config.png" width="444" alt="Firewall Configuration Tool" /><div class="longdesc"><div class="para">
Security Level Configuration
</div></div></div></div><h6>Figure 2.15. <span class="application">Firewall Configuration Tool</span></h6></div><br class="figure-break" /><div class="note"><h2>Note</h2><div class="para">
The <span class="application"><strong>Firewall Configuration Tool</strong></span> only configures a basic firewall. If the system needs more complex rules, refer to <a class="xref" href="#sect-Security_Guide-IPTables" title="2.9. IPTables">Section 2.9, “IPTablesâ€</a> for details on configuring specific <code class="command">iptables</code> rules.
- </div></div></div><div class="section" title="2.8.2.2. Enabling and Disabling the Firewall" id="sect-Security_Guide-Basic_Firewall_Configuration-Enabling_and_Disabling_the_Firewall"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.8.2.2. Enabling and Disabling the Firewall</h4></div></div></div><div class="para">
+ </div></div></div><div class="section" title="2.8.2.2. Enabling and Disabling the Firewall" id="sect-Security_Guide-Basic_Firewall_Configuration-Enabling_and_Disabling_the_Firewall"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Basic_Firewall_Configuration-Enabling_and_Disabling_the_Firewall">2.8.2.2. Enabling and Disabling the Firewall</h4></div></div></div><div class="para">
Select one of the following options for the firewall:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<span class="guilabel"><strong>Disabled</strong></span> — Disabling the firewall provides complete access to your system and does no security checking. This should only be selected if you are running on a trusted network (not the Internet) or need to configure a custom firewall using the iptables command line tool.
@@ -3235,7 +3080,7 @@ include "/etc/racoon/<em class="replaceable"><code>X.X.X.X</code></em>.conf"
<span class="guilabel"><strong>Enabled</strong></span> — This option configures the system to reject incoming connections that are not in response to outbound requests, such as DNS replies or DHCP requests. If access to services running on this machine is needed, you can choose to allow specific services through the firewall.
</div><div class="para">
If you are connecting your system to the Internet, but do not plan to run a server, this is the safest choice.
- </div></li></ul></div></div><div class="section" title="2.8.2.3. Trusted Services" id="sect-Security_Guide-Basic_Firewall_Configuration-Trusted_Services"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.8.2.3. Trusted Services</h4></div></div></div><div class="para">
+ </div></li></ul></div></div><div class="section" title="2.8.2.3. Trusted Services" id="sect-Security_Guide-Basic_Firewall_Configuration-Trusted_Services"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Basic_Firewall_Configuration-Trusted_Services">2.8.2.3. Trusted Services</h4></div></div></div><div class="para">
Enabling options in the <span class="guilabel"><strong>Trusted services</strong></span> list allows the specified service to pass through the firewall.
</div><div class="variablelist"><dl><dt><span class="term"><span class="guilabel"><strong>WWW (HTTP)</strong></span></span></dt><dd><div class="para">
The HTTP protocol is used by Apache (and by other Web servers) to serve web pages. If you plan on making your Web server publicly available, select this check box. This option is not required for viewing pages locally or for developing web pages. This service requires that the <code class="filename">httpd</code> package be installed.
@@ -3253,36 +3098,31 @@ include "/etc/racoon/<em class="replaceable"><code>X.X.X.X</code></em>.conf"
The Network File System (NFS) is a file sharing protocol commonly used on *NIX systems. Version 4 of this protocol is more secure than its predecessors. If you want to share files or directories on your system with other network users, select this check box.
</div></dd><dt><span class="term"><span class="guilabel"><strong>Samba</strong></span></span></dt><dd><div class="para">
Samba is an implementation of Microsoft's proprietary SMB networking protocol. If you need to share files, directories, or locally-connected printers with Microsoft Windows machines, select this check box.
- </div></dd></dl></div></div><div class="section" title="2.8.2.4. Other Ports" id="sect-Security_Guide-Basic_Firewall_Configuration-Other_Ports"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.8.2.4. Other Ports</h4></div></div></div><div class="para">
+ </div></dd></dl></div></div><div class="section" title="2.8.2.4. Other Ports" id="sect-Security_Guide-Basic_Firewall_Configuration-Other_Ports"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Basic_Firewall_Configuration-Other_Ports">2.8.2.4. Other Ports</h4></div></div></div><div class="para">
The <span class="application"><strong>Firewall Configuration Tool</strong></span> includes an <span class="guilabel"><strong>Other ports</strong></span> section for specifying custom IP ports as being trusted by <code class="command">iptables</code>. For example, to allow IRC and Internet printing protocol (IPP) to pass through the firewall, add the following to the <span class="guilabel"><strong>Other ports</strong></span> section:
</div><div class="para">
<code class="computeroutput">194:tcp,631:tcp</code>
- </div></div><div class="section" title="2.8.2.5. Saving the Settings" id="sect-Security_Guide-Basic_Firewall_Configuration-Saving_the_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.8.2.5. Saving the Settings</h4></div></div></div><div class="para">
+ </div></div><div class="section" title="2.8.2.5. Saving the Settings" id="sect-Security_Guide-Basic_Firewall_Configuration-Saving_the_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Basic_Firewall_Configuration-Saving_the_Settings">2.8.2.5. Saving the Settings</h4></div></div></div><div class="para">
Click <span class="guibutton"><strong>OK</strong></span> to save the changes and enable or disable the firewall. If <span class="guilabel"><strong>Enable firewall</strong></span> was selected, the options selected are translated to <code class="command">iptables</code> commands and written to the <code class="filename">/etc/sysconfig/iptables</code> file. The <code class="command">iptables</code> service is also started so that the firewall is activated immediately after saving the selected options. If <span class="guilabel"><strong>Disable firewall</strong></span> was selected, the <code class="filename">/etc/sysconfig/iptables</code> file is removed and the <code class="command">iptables</code> service is stopped immediately.
</div><div class="para">
The selected options are also written to the <code class="filename">/etc/sysconfig/system-config-securitylevel</code> file so that the settings can be restored the next time the application is started. Do not edit this file by hand.
</div><div class="para">
Even though the firewall is activated immediately, the <code class="command">iptables</code> service is not configured to start automatically at boot time. Refer to <a class="xref" href="#sect-Security_Guide-Basic_Firewall_Configuration-Activating_the_IPTables_Service" title="2.8.2.6. Activating the IPTables Service">Section 2.8.2.6, “Activating the IPTables Serviceâ€</a> for more information.
- </div></div><div class="section" title="2.8.2.6. Activating the IPTables Service" id="sect-Security_Guide-Basic_Firewall_Configuration-Activating_the_IPTables_Service"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.8.2.6. Activating the IPTables Service</h4></div></div></div><div class="para">
+ </div></div><div class="section" title="2.8.2.6. Activating the IPTables Service" id="sect-Security_Guide-Basic_Firewall_Configuration-Activating_the_IPTables_Service"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Basic_Firewall_Configuration-Activating_the_IPTables_Service">2.8.2.6. Activating the IPTables Service</h4></div></div></div><div class="para">
The firewall rules are only active if the <code class="command">iptables</code> service is running. To manually start the service, use the following command:
- </div><pre class="screen">[root at myServer ~] # service iptables restart
-</pre><div class="para">
+ </div><pre class="screen">[root at myServer ~] # service iptables restart</pre><div class="para">
To ensure that <code class="command">iptables</code> starts when the system is booted, use the following command:
- </div><pre class="screen">[root at myServer ~] # chkconfig --level 345 iptables on
-</pre></div></div><div class="section" title="2.8.3. Using IPTables" id="sect-Security_Guide-Firewalls-Using_IPTables"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.8.3. Using IPTables</h3></div></div></div><div class="para">
+ </div><pre class="screen">[root at myServer ~] # chkconfig --level 345 iptables on</pre></div></div><div class="section" title="2.8.3. Using IPTables" id="sect-Security_Guide-Firewalls-Using_IPTables"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Firewalls-Using_IPTables">2.8.3. Using IPTables</h3></div></div></div><div class="para">
The first step in using <code class="command">iptables</code> is to start the <code class="command">iptables</code> service. Use the following command to start the <code class="command">iptables</code> service:
- </div><pre class="screen">[root at myServer ~] # service iptables start
-</pre><div class="note"><h2>Note</h2><div class="para">
+ </div><pre class="screen">[root at myServer ~] # service iptables start</pre><div class="note"><h2>Note</h2><div class="para">
The <code class="command">ip6tables</code> service can be turned off if you intend to use the <code class="command">iptables</code> service only. If you deactivate the <code class="command">ip6tables</code> service, remember to deactivate the IPv6 network also. Never leave a network device active without the matching firewall.
</div></div><div class="para">
To force <code class="command">iptables</code> to start by default when the system is booted, use the following command:
- </div><pre class="screen">[root at myServer ~] # chkconfig --level 345 iptables on
-</pre><div class="para">
+ </div><pre class="screen">[root at myServer ~] # chkconfig --level 345 iptables on</pre><div class="para">
This forces <code class="command">iptables</code> to start whenever the system is booted into runlevel 3, 4, or 5.
- </div><div class="section" title="2.8.3.1. IPTables Command Syntax" id="sect-Security_Guide-Using_IPTables-IPTables_Command_Syntax"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.8.3.1. IPTables Command Syntax</h4></div></div></div><div class="para">
+ </div><div class="section" title="2.8.3.1. IPTables Command Syntax" id="sect-Security_Guide-Using_IPTables-IPTables_Command_Syntax"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Using_IPTables-IPTables_Command_Syntax">2.8.3.1. IPTables Command Syntax</h4></div></div></div><div class="para">
The following sample <code class="command">iptables</code> command illustrates the basic command syntax:
- </div><pre class="screen">[root at myServer ~ ] # iptables -A <em class="replaceable"><code><chain></code></em> -j <em class="replaceable"><code><target></code></em>
-</pre><div class="para">
+ </div><pre class="screen">[root at myServer ~ ] # iptables -A <em class="replaceable"><code><chain></code></em> -j <em class="replaceable"><code><target></code></em></pre><div class="para">
The <code class="option">-A</code> option specifies that the rule be appended to <em class="firstterm"><chain></em>. Each chain is comprised of one or more <em class="firstterm">rules</em>, and is therefore also known as a <em class="firstterm">ruleset</em>.
</div><div class="para">
The three built-in chains are INPUT, OUTPUT, and FORWARD. These chains are permanent and cannot be deleted. The chain specifies the point at which a packet is manipulated.
@@ -3290,27 +3130,24 @@ include "/etc/racoon/<em class="replaceable"><code>X.X.X.X</code></em>.conf"
The <code class="option">-j <em class="replaceable"><code><target></code></em></code> option specifies the target of the rule; i.e., what to do if the packet matches the rule. Examples of built-in targets are ACCEPT, DROP, and REJECT.
</div><div class="para">
Refer to the <code class="command">iptables</code> man page for more information on the available chains, options, and targets.
- </div></div><div class="section" title="2.8.3.2. Basic Firewall Policies" id="sect-Security_Guide-Using_IPTables-Basic_Firewall_Policies"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.8.3.2. Basic Firewall Policies</h4></div></div></div><div class="para">
+ </div></div><div class="section" title="2.8.3.2. Basic Firewall Policies" id="sect-Security_Guide-Using_IPTables-Basic_Firewall_Policies"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Using_IPTables-Basic_Firewall_Policies">2.8.3.2. Basic Firewall Policies</h4></div></div></div><div class="para">
Establishing basic firewall policies creates a foundation for building more detailed, user-defined rules.
</div><div class="para">
Each <code class="command">iptables</code> chain is comprised of a default policy, and zero or more rules which work in concert with the default policy to define the overall ruleset for the firewall.
</div><div class="para">
The default policy for a chain can be either DROP or ACCEPT. Security-minded administrators typically implement a default policy of DROP, and only allow specific packets on a case-by-case basis. For example, the following policies block all incoming and outgoing packets on a network gateway:
</div><pre class="screen">[root at myServer ~ ] # iptables -P INPUT DROP
-[root at myServer ~ ] # iptables -P OUTPUT DROP
-</pre><div class="para">
+[root at myServer ~ ] # iptables -P OUTPUT DROP</pre><div class="para">
It is also recommended that any <em class="firstterm">forwarded packets</em> — network traffic that is to be routed from the firewall to its destination node — be denied as well, to restrict internal clients from inadvertent exposure to the Internet. To do this, use the following rule:
- </div><pre class="screen">[root at myServer ~ ] # iptables -P FORWARD DROP
-</pre><div class="para">
+ </div><pre class="screen">[root at myServer ~ ] # iptables -P FORWARD DROP</pre><div class="para">
When you have established the default policies for each chain, you can create and save further rules for your particular network and security requirements.
</div><div class="para">
The following sections describe how to save iptables rules and outline some of the rules you might implement in the course of building your iptables firewall.
- </div></div><div class="section" title="2.8.3.3. Saving and Restoring IPTables Rules" id="sect-Security_Guide-Using_IPTables-Saving_and_Restoring_IPTables_Rules"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.8.3.3. Saving and Restoring IPTables Rules</h4></div></div></div><div class="para">
+ </div></div><div class="section" title="2.8.3.3. Saving and Restoring IPTables Rules" id="sect-Security_Guide-Using_IPTables-Saving_and_Restoring_IPTables_Rules"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Using_IPTables-Saving_and_Restoring_IPTables_Rules">2.8.3.3. Saving and Restoring IPTables Rules</h4></div></div></div><div class="para">
Changes to <code class="command">iptables</code> are transitory; if the system is rebooted or if the <code class="command">iptables</code> service is restarted, the rules are automatically flushed and reset. To save the rules so that they are loaded when the <code class="command">iptables</code> service is started, use the following command:
- </div><pre class="screen">[root at myServer ~ ] # service iptables save
-</pre><div class="para">
+ </div><pre class="screen">[root at myServer ~ ] # service iptables save</pre><div class="para">
The rules are stored in the file <code class="filename">/etc/sysconfig/iptables</code> and are applied whenever the service is started or the machine is rebooted.
- </div></div></div><div class="section" title="2.8.4. Common IPTables Filtering" id="sect-Security_Guide-Firewalls-Common_IPTables_Filtering"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.8.4. Common IPTables Filtering</h3></div></div></div><div class="para">
+ </div></div></div><div class="section" title="2.8.4. Common IPTables Filtering" id="sect-Security_Guide-Firewalls-Common_IPTables_Filtering"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Firewalls-Common_IPTables_Filtering">2.8.4. Common IPTables Filtering</h3></div></div></div><div class="para">
Preventing remote attackers from accessing a LAN is one of the most important aspects of network security. The integrity of a LAN should be protected from malicious remote users through the use of stringent firewall rules.
</div><div class="para">
However, with a default policy set to block all incoming, outgoing, and forwarded packets, it is impossible for the firewall/gateway and internal LAN users to communicate with each other or with external resources.
@@ -3318,11 +3155,9 @@ include "/etc/racoon/<em class="replaceable"><code>X.X.X.X</code></em>.conf"
To allow users to perform network-related functions and to use networking applications, administrators must open certain ports for communication.
</div><div class="para">
For example, to allow access to port 80 <span class="emphasis"><em>on the firewall</em></span>, append the following rule:
- </div><pre class="screen">[root at myServer ~ ] # iptables -A INPUT -p tcp -m tcp --dport 80 -j ACCEPT
-</pre><div class="para">
+ </div><pre class="screen">[root at myServer ~ ] # iptables -A INPUT -p tcp -m tcp --dport 80 -j ACCEPT</pre><div class="para">
This allows users to browse websites that communicate using the standard port 80. To allow access to secure websites (for example, https://www.example.com/), you also need to provide access to port 443, as follows:
- </div><pre class="screen">[root at myServer ~ ] # iptables -A INPUT -p tcp -m tcp --dport 443 -j ACCEPT
-</pre><div class="important"><h2>Important</h2><div class="para">
+ </div><pre class="screen">[root at myServer ~ ] # iptables -A INPUT -p tcp -m tcp --dport 443 -j ACCEPT</pre><div class="important"><h2>Important</h2><div class="para">
When creating an <code class="command">iptables</code> ruleset, order is important.
</div><div class="para">
If a rule specifies that any packets from the 192.168.100.0/24 subnet be dropped, and this is followed by a rule that allows packets from 192.168.100.13 (which is within the dropped subnet), then the second rule is ignored.
@@ -3330,8 +3165,7 @@ include "/etc/racoon/<em class="replaceable"><code>X.X.X.X</code></em>.conf"
The rule to allow packets from 192.168.100.13 must precede the rule that drops the remainder of the subnet.
</div><div class="para">
To insert a rule in a specific location in an existing chain, use the <code class="option">-I</code> option. For example:
- </div><pre class="screen">[root at myServer ~ ] # iptables -I INPUT 1 -i lo -p all -j ACCEPT
-</pre><div class="para">
+ </div><pre class="screen">[root at myServer ~ ] # iptables -I INPUT 1 -i lo -p all -j ACCEPT</pre><div class="para">
This rule is inserted as the first rule in the INPUT chain to allow local loopback device traffic.
</div></div><div class="para">
There may be times when you require remote access to the LAN. Secure services, for example SSH, can be used for encrypted remote connection to LAN services.
@@ -3340,10 +3174,9 @@ include "/etc/racoon/<em class="replaceable"><code>X.X.X.X</code></em>.conf"
</div><div class="para">
For remote users with broadband connections, however, special cases can be made. You can configure <code class="command">iptables</code> to accept connections from remote SSH clients. For example, the following rules allow remote SSH access:
</div><pre class="screen">[root at myServer ~ ] # iptables -A INPUT -p tcp --dport 22 -j ACCEPT
-[root at myServer ~ ] # iptables -A OUTPUT -p tcp --sport 22 -j ACCEPT
-</pre><div class="para">
+[root at myServer ~ ] # iptables -A OUTPUT -p tcp --sport 22 -j ACCEPT</pre><div class="para">
These rules allow incoming and outbound access for an individual system, such as a single PC directly connected to the Internet or a firewall/gateway. However, they do not allow nodes behind the firewall/gateway to access these services. To allow LAN access to these services, you can use <em class="firstterm">Network Address Translation</em> (<acronym class="acronym">NAT</acronym>) with <code class="command">iptables</code> filtering rules.
- </div></div><div class="section" title="2.8.5. FORWARD and NAT Rules" id="sect-Security_Guide-Firewalls-FORWARD_and_NAT_Rules"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.8.5. <code class="computeroutput">FORWARD</code> and <acronym class="acronym">NAT</acronym> Rules</h3></div></div></div><div class="para">
+ </div></div><div class="section" title="2.8.5. FORWARD and NAT Rules" id="sect-Security_Guide-Firewalls-FORWARD_and_NAT_Rules"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Firewalls-FORWARD_and_NAT_Rules">2.8.5. <code class="computeroutput">FORWARD</code> and <acronym class="acronym">NAT</acronym> Rules</h3></div></div></div><div class="para">
Most ISPs provide only a limited number of publicly routable IP addresses to the organizations they serve.
</div><div class="para">
Administrators must, therefore, find alternative ways to share access to Internet services without giving public IP addresses to every node on the LAN. Using private IP addresses is the most common way of allowing all nodes on a LAN to properly access internal and external network services.
@@ -3356,56 +3189,47 @@ include "/etc/racoon/<em class="replaceable"><code>X.X.X.X</code></em>.conf"
</div><div class="para">
The <code class="computeroutput">FORWARD</code> chain allows an administrator to control where packets can be routed within a LAN. For example, to allow forwarding for the entire LAN (assuming the firewall/gateway is assigned an internal IP address on eth1), use the following rules:
</div><pre class="screen">[root at myServer ~ ] # iptables -A FORWARD -i eth1 -j ACCEPT
-[root at myServer ~ ] # iptables -A FORWARD -o eth1 -j ACCEPT
-</pre><div class="para">
+[root at myServer ~ ] # iptables -A FORWARD -o eth1 -j ACCEPT</pre><div class="para">
This rule gives systems behind the firewall/gateway access to the internal network. The gateway routes packets from one LAN node to its intended destination node, passing all packets through its <code class="filename">eth1</code> device.
</div><div class="note"><h2>Note</h2><div class="para">
By default, the IPv4 policy in Fedora kernels disables support for IP forwarding. This prevents machines that run Fedora from functioning as dedicated edge routers. To enable IP forwarding, use the following command:
- </div><pre class="screen">[root at myServer ~ ] # sysctl -w net.ipv4.ip_forward=1
-</pre><div class="para">
+ </div><pre class="screen">[root at myServer ~ ] # sysctl -w net.ipv4.ip_forward=1</pre><div class="para">
This configuration change is only valid for the current session; it does not persist beyond a reboot or network service restart. To permanently set IP forwarding, edit the <code class="filename">/etc/sysctl.conf</code> file as follows:
</div><div class="para">
Locate the following line:
- </div><pre class="screen">net.ipv4.ip_forward = 0
-</pre><div class="para">
+ </div><pre class="screen">net.ipv4.ip_forward = 0</pre><div class="para">
Edit it to read as follows:
- </div><pre class="screen">net.ipv4.ip_forward = 1
-</pre><div class="para">
+ </div><pre class="screen">net.ipv4.ip_forward = 1</pre><div class="para">
Use the following command to enable the change to the <code class="filename">sysctl.conf</code> file:
- </div><pre class="screen">[root at myServer ~ ] # sysctl -p /etc/sysctl.conf
-</pre></div><div class="section" title="2.8.5.1. Postrouting and IP Masquerading" id="sect-Security_Guide-FORWARD_and_NAT_Rules-Postrouting_and_IP_Masquerading"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.8.5.1. Postrouting and IP Masquerading</h4></div></div></div><div class="para">
+ </div><pre class="screen">[root at myServer ~ ] # sysctl -p /etc/sysctl.conf</pre></div><div class="section" title="2.8.5.1. Postrouting and IP Masquerading" id="sect-Security_Guide-FORWARD_and_NAT_Rules-Postrouting_and_IP_Masquerading"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-FORWARD_and_NAT_Rules-Postrouting_and_IP_Masquerading">2.8.5.1. Postrouting and IP Masquerading</h4></div></div></div><div class="para">
Accepting forwarded packets via the firewall's internal IP device allows LAN nodes to communicate with each other; however they still cannot communicate externally to the Internet.
</div><div class="para">
To allow LAN nodes with private IP addresses to communicate with external public networks, configure the firewall for <em class="firstterm">IP masquerading</em>, which masks requests from LAN nodes with the IP address of the firewall's external device (in this case, eth0):
- </div><pre class="screen">[root at myServer ~ ] # iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
-</pre><div class="para">
+ </div><pre class="screen">[root at myServer ~ ] # iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE</pre><div class="para">
This rule uses the NAT packet matching table (<code class="option">-t nat</code>) and specifies the built-in POSTROUTING chain for NAT (<code class="option">-A POSTROUTING</code>) on the firewall's external networking device (<code class="option">-o eth0</code>).
</div><div class="para">
POSTROUTING allows packets to be altered as they are leaving the firewall's external device.
</div><div class="para">
The <code class="option">-j MASQUERADE</code> target is specified to mask the private IP address of a node with the external IP address of the firewall/gateway.
- </div></div><div class="section" title="2.8.5.2. Prerouting" id="sect-Security_Guide-FORWARD_and_NAT_Rules-Prerouting"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.8.5.2. Prerouting</h4></div></div></div><div class="para">
+ </div></div><div class="section" title="2.8.5.2. Prerouting" id="sect-Security_Guide-FORWARD_and_NAT_Rules-Prerouting"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-FORWARD_and_NAT_Rules-Prerouting">2.8.5.2. Prerouting</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">
For example, if you want to forward incoming HTTP requests to your dedicated Apache HTTP Server at 172.31.0.23, use the following command:
- </div><pre class="screen">[root at myServer ~ ] # iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 80 -j DNAT --to 172.31.0.23:80
-</pre><div class="para">
+ </div><pre class="screen">[root at myServer ~ ] # iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 80 -j DNAT --to 172.31.0.23:80</pre><div class="para">
This rule specifies that the <acronym class="acronym">nat</acronym> table use the built-in PREROUTING chain to forward incoming HTTP requests exclusively to the listed destination IP address of 172.31.0.23.
</div><div class="note"><h2>Note</h2><div class="para">
If you have a default policy of DROP in your FORWARD chain, you must append a rule to forward all incoming HTTP requests so that destination NAT routing is possible. To do this, use the following command:
- </div><pre class="screen">[root at myServer ~ ] # iptables -A FORWARD -i eth0 -p tcp --dport 80 -d 172.31.0.23 -j ACCEPT
-</pre><div class="para">
+ </div><pre class="screen">[root at myServer ~ ] # iptables -A FORWARD -i eth0 -p tcp --dport 80 -d 172.31.0.23 -j ACCEPT</pre><div class="para">
This rule forwards all incoming HTTP requests from the firewall to the intended destination; the Apache HTTP Server behind the firewall.
- </div></div></div><div class="section" title="2.8.5.3. DMZs and IPTables" id="sect-Security_Guide-FORWARD_and_NAT_Rules-DMZs_and_IPTables"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.8.5.3. DMZs and IPTables</h4></div></div></div><div class="para">
+ </div></div></div><div class="section" title="2.8.5.3. DMZs and IPTables" id="sect-Security_Guide-FORWARD_and_NAT_Rules-DMZs_and_IPTables"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-FORWARD_and_NAT_Rules-DMZs_and_IPTables">2.8.5.3. DMZs and IPTables</h4></div></div></div><div class="para">
You can create <code class="command">iptables</code> rules to route traffic to certain machines, such as a dedicated HTTP or FTP server, in a <em class="firstterm">demilitarized zone</em> (<acronym class="acronym">DMZ</acronym>). A <acronym class="acronym">DMZ</acronym> is a special local subnetwork dedicated to providing services on a public carrier, such as the Internet.
</div><div class="para">
For example, to set a rule for routing incoming HTTP requests to a dedicated HTTP server at 10.0.4.2 (outside of the 192.168.1.0/24 range of the LAN), NAT uses the <code class="computeroutput">PREROUTING</code> table to forward the packets to the appropriate destination:
- </div><pre class="screen">[root at myServer ~ ] # iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 80 -j DNAT --to-destination 10.0.4.2:80
-</pre><div class="para">
+ </div><pre class="screen">[root at myServer ~ ] # 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">
If the HTTP server is configured to accept secure connections, then port 443 must be forwarded as well.
- </div></div></div><div class="section" title="2.8.6. Malicious Software and Spoofed IP Addresses" id="sect-Security_Guide-Firewalls-Malicious_Software_and_Spoofed_IP_Addresses"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.8.6. Malicious Software and Spoofed IP Addresses</h3></div></div></div><div class="para">
+ </div></div></div><div class="section" title="2.8.6. Malicious Software and Spoofed IP Addresses" id="sect-Security_Guide-Firewalls-Malicious_Software_and_Spoofed_IP_Addresses"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Firewalls-Malicious_Software_and_Spoofed_IP_Addresses">2.8.6. Malicious Software and Spoofed IP Addresses</h3></div></div></div><div class="para">
More elaborate rules can be created that control access to specific subnets, or even specific nodes, within a LAN. You can also restrict certain dubious applications or programs such as trojans, worms, and other client/server viruses from contacting their server.
</div><div class="para">
For example, some trojans scan networks for services on ports from 31337 to 31340 (called the <span class="emphasis"><em>elite</em></span> ports in cracking terminology).
@@ -3414,21 +3238,19 @@ include "/etc/racoon/<em class="replaceable"><code>X.X.X.X</code></em>.conf"
</div><div class="para">
The following rules drop all TCP traffic that attempts to use port 31337:
</div><pre class="screen">[root at myServer ~ ] # iptables -A OUTPUT -o eth0 -p tcp --dport 31337 --sport 31337 -j DROP
-[root at myServer ~ ] # iptables -A FORWARD -o eth0 -p tcp --dport 31337 --sport 31337 -j DROP
-</pre><div class="para">
+[root at myServer ~ ] # iptables -A FORWARD -o eth0 -p tcp --dport 31337 --sport 31337 -j DROP</pre><div class="para">
You can also block outside connections that attempt to spoof private IP address ranges to infiltrate your LAN.
</div><div class="para">
For example, if your LAN uses the 192.168.1.0/24 range, you can design a rule that instructs the Internet-facing network device (for example, eth0) to drop any packets to that device with an address in your LAN IP range.
</div><div class="para">
Because it is recommended to reject forwarded packets as a default policy, any other spoofed IP address to the external-facing device (eth0) is rejected automatically.
- </div><pre class="screen">[root at myServer ~ ] # iptables -A FORWARD -s 192.168.1.0/24 -i eth0 -j DROP
-</pre><div class="note"><h2>Note</h2><div class="para">
+ </div><pre class="screen">[root at myServer ~ ] # iptables -A FORWARD -s 192.168.1.0/24 -i eth0 -j DROP</pre><div class="note"><h2>Note</h2><div class="para">
There is a distinction between the <code class="computeroutput">DROP</code> and <code class="computeroutput">REJECT</code> targets when dealing with <span class="emphasis"><em>appended</em></span> rules.
</div><div class="para">
The <code class="computeroutput">REJECT</code> target denies access and returns a <code class="computeroutput">connection refused</code> error to users who attempt to connect to the service. The <code class="computeroutput">DROP</code> target, as the name implies, drops the packet without any warning.
</div><div class="para">
Administrators can use their own discretion when using these targets. However, to avoid user confusion and attempts to continue connecting, the <code class="computeroutput">REJECT</code> target is recommended.
- </div></div></div><div class="section" title="2.8.7. IPTables and Connection Tracking" id="sect-Security_Guide-Firewalls-IPTables_and_Connection_Tracking"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.8.7. IPTables and Connection Tracking</h3></div></div></div><div class="para">
+ </div></div></div><div class="section" title="2.8.7. IPTables and Connection Tracking" id="sect-Security_Guide-Firewalls-IPTables_and_Connection_Tracking"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Firewalls-IPTables_and_Connection_Tracking">2.8.7. IPTables and Connection Tracking</h3></div></div></div><div class="para">
You can inspect and restrict connections to services based on their <em class="firstterm">connection state.</em> A module within <code class="command">iptables</code> uses a method called <em class="firstterm">connection tracking</em> to store information about incoming connections. You can allow or deny access based on the following connection states:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="option">NEW</code> — A packet requesting a new connection, such as an HTTP request.
@@ -3440,33 +3262,31 @@ include "/etc/racoon/<em class="replaceable"><code>X.X.X.X</code></em>.conf"
<code class="option">INVALID</code> — A packet that is not part of any connections in the connection tracking table.
</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 myServer ~ ] # iptables -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT
-</pre></div><div class="section" title="2.8.8. IPv6" id="sect-Security_Guide-Firewalls-IPv6"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.8.8. IPv6</h3></div></div></div><div class="para">
+ </div><pre class="screen">[root at myServer ~ ] # iptables -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT</pre></div><div class="section" title="2.8.8. IPv6" id="sect-Security_Guide-Firewalls-IPv6"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Firewalls-IPv6">2.8.8. IPv6</h3></div></div></div><div class="para">
The introduction of the next-generation Internet Protocol, called IPv6, expands beyond the 32-bit address limit of IPv4 (or IP). IPv6 supports 128-bit addresses, and carrier networks that are IPv6 aware are therefore able to address a larger number of routable addresses than 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 12, both IPv4 and IPv6 services are enabled by default.
</div><div class="para">
The <code class="command">ip6tables</code> command syntax is identical to <code class="command">iptables</code> in every aspect except that it supports 128-bit addresses. For example, use the following command to enable SSH connections on an IPv6-aware network server:
- </div><pre class="screen">[root at myServer ~ ] # ip6tables -A INPUT -i eth0 -p tcp -s 3ffe:ffff:100::1/128 --dport 22 -j ACCEPT
-</pre><div class="para">
+ </div><pre class="screen">[root at myServer ~ ] # ip6tables -A INPUT -i eth0 -p tcp -s 3ffe:ffff:100::1/128 --dport 22 -j ACCEPT</pre><div class="para">
For more information about IPv6 networking, refer to the IPv6 Information Page at <a href="http://www.ipv6.org/">http://www.ipv6.org/</a>.
- </div></div><div class="section" title="2.8.9. Additional Resources" id="sect-Security_Guide-Firewalls-Additional_Resources"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.8.9. Additional Resources</h3></div></div></div><div class="para">
+ </div></div><div class="section" title="2.8.9. Additional Resources" id="sect-Security_Guide-Firewalls-Additional_Resources"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Firewalls-Additional_Resources">2.8.9. Additional Resources</h3></div></div></div><div class="para">
There are several aspects to firewalls and the Linux Netfilter subsystem that could not be covered in this chapter. For more information, refer to the following resources.
- </div><div class="section" title="2.8.9.1. Installed Firewall Documentation" id="sect-Security_Guide-Additional_Resources-Installed_Firewall_Documentation"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.8.9.1. Installed Firewall Documentation</h4></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ </div><div class="section" title="2.8.9.1. Installed Firewall Documentation" id="sect-Security_Guide-Additional_Resources-Installed_Firewall_Documentation"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Additional_Resources-Installed_Firewall_Documentation">2.8.9.1. Installed Firewall Documentation</h4></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
Refer to <a class="xref" href="#sect-Security_Guide-IPTables" title="2.9. IPTables">Section 2.9, “IPTablesâ€</a> for more detailed information on the <code class="command">iptables</code> command, including definitions for many command options.
</div></li><li class="listitem"><div class="para">
The <code class="command">iptables</code> man page contains a brief summary of the various options.
- </div></li></ul></div></div><div class="section" title="2.8.9.2. Useful Firewall Websites" id="sect-Security_Guide-Additional_Resources-Useful_Firewall_Websites"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.8.9.2. Useful Firewall Websites</h4></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ </div></li></ul></div></div><div class="section" title="2.8.9.2. Useful Firewall Websites" id="sect-Security_Guide-Additional_Resources-Useful_Firewall_Websites"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Additional_Resources-Useful_Firewall_Websites">2.8.9.2. Useful Firewall Websites</h4></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<a href="http://www.netfilter.org/">http://www.netfilter.org/</a> — The official homepage of the Netfilter and <code class="command">iptables</code> project.
</div></li><li class="listitem"><div class="para">
<a href="http://www.tldp.org/">http://www.tldp.org/</a> — The Linux Documentation Project contains several useful guides relating to firewall creation and administration.
</div></li><li class="listitem"><div class="para">
<a href="http://www.iana.org/assignments/port-numbers">http://www.iana.org/assignments/port-numbers</a> — The official list of registered and common service ports as assigned by the Internet Assigned Numbers Authority.
- </div></li></ul></div></div><div class="section" title="2.8.9.3. Related Documentation" id="sect-Security_Guide-Additional_Resources-Related_Documentation"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.8.9.3. Related Documentation</h4></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ </div></li></ul></div></div><div class="section" title="2.8.9.3. Related Documentation" id="sect-Security_Guide-Additional_Resources-Related_Documentation"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Additional_Resources-Related_Documentation">2.8.9.3. Related Documentation</h4></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<em class="citetitle">Red Hat Linux Firewalls</em>, by Bill McCarty; Red Hat Press — a comprehensive reference to building network and server firewalls using open source packet filtering technology such as Netfilter and <code class="command">iptables</code>. It includes topics that cover analyzing firewall logs, developing firewall rules, and customizing your firewall using various graphical tools.
</div></li><li class="listitem"><div class="para">
<em class="citetitle">Linux Firewalls</em>, by Robert Ziegler; New Riders Press — contains a wealth of information on building firewalls using both 2.2 kernel <code class="command">ipchains</code> as well as Netfilter and <code class="command">iptables</code>. Additional security topics such as remote access issues and intrusion detection systems are also covered.
- </div></li></ul></div></div></div></div><div xml:lang="en-US" class="section" title="2.9. IPTables" id="sect-Security_Guide-IPTables" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.9. IPTables</h2></div></div></div><div class="para">
+ </div></li></ul></div></div></div></div><div xml:lang="en-US" class="section" title="2.9. IPTables" id="sect-Security_Guide-IPTables" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sect-Security_Guide-IPTables">2.9. IPTables</h2></div></div></div><div class="para">
Included with Fedora are advanced tools for network <em class="firstterm">packet filtering</em> — the process of controlling network packets as they enter, move through, and exit the network stack within the kernel. Kernel versions prior to 2.4 relied on <code class="command">ipchains</code> for packet filtering and used lists of rules applied to packets at each step of the filtering process. The 2.4 kernel introduced <code class="command">iptables</code> (also called <em class="firstterm">netfilter</em>), which is similar to <code class="command">ipchains</code> but greatly expands the scope and control available for filtering network packets.
</div><div class="para">
This chapter focuses on packet filtering basics, explains various options available with <code class="command">iptables</code> commands, and explains how filtering rules can be preserved between system reboots.
@@ -3476,7 +3296,7 @@ include "/etc/racoon/<em class="replaceable"><code>X.X.X.X</code></em>.conf"
The default firewall mechanism in the 2.4 and later kernels is <code class="command">iptables</code>, but <code class="command">iptables</code> cannot be used if <code class="command">ipchains</code> is already running. If <code class="command">ipchains</code> is present at boot time, the kernel issues an error and fails to start <code class="command">iptables</code>.
</div><div class="para">
The functionality of <code class="command">ipchains</code> is not affected by these errors.
- </div></div><div class="section" title="2.9.1. Packet Filtering" id="sect-Security_Guide-IPTables-Packet_Filtering"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.9.1. Packet Filtering</h3></div></div></div><div class="para">
+ </div></div><div class="section" title="2.9.1. Packet Filtering" id="sect-Security_Guide-IPTables-Packet_Filtering"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-IPTables-Packet_Filtering">2.9.1. Packet Filtering</h3></div></div></div><div class="para">
The Linux kernel uses the <span class="application"><strong>Netfilter</strong></span> facility to filter packets, allowing some of them to be received by or pass through the system while stopping others. This facility is built in to the Linux kernel, and has three built-in <em class="firstterm">tables</em> or <em class="firstterm">rules lists</em>, as follows:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="option">filter</code> — The default table for handling network packets.
@@ -3526,7 +3346,7 @@ include "/etc/racoon/<em class="replaceable"><code>X.X.X.X</code></em>.conf"
Every chain has a default policy to <code class="command">ACCEPT</code>, <code class="command">DROP</code>, <code class="command">REJECT</code>, or <code class="command">QUEUE</code>. If none of the rules in the chain apply to the packet, then the packet is dealt with in accordance with the default policy.
</div><div class="para">
The <code class="command">iptables</code> command configures these tables, as well as sets up new tables if necessary.
- </div></div><div class="section" title="2.9.2. Command Options for IPTables" id="sect-Security_Guide-IPTables-Command_Options_for_IPTables"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.9.2. Command Options for IPTables</h3></div></div></div><div class="para">
+ </div></div><div class="section" title="2.9.2. Command Options for IPTables" id="sect-Security_Guide-IPTables-Command_Options_for_IPTables"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-IPTables-Command_Options_for_IPTables">2.9.2. Command Options for IPTables</h3></div></div></div><div class="para">
Rules for filtering packets are created using the <code class="command">iptables</code> command. The following aspects of the packet are most often used as criteria:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<span class="emphasis"><em>Packet Type</em></span> — Specifies the type of packets the command filters.
@@ -3538,10 +3358,9 @@ include "/etc/racoon/<em class="replaceable"><code>X.X.X.X</code></em>.conf"
Refer to <a class="xref" href="#sect-Security_Guide-Command_Options_for_IPTables-IPTables_Match_Options" title="2.9.2.4. IPTables Match Options">Section 2.9.2.4, “IPTables Match Optionsâ€</a> and <a class="xref" href="#sect-Security_Guide-Command_Options_for_IPTables-Target_Options" title="2.9.2.5. Target Options">Section 2.9.2.5, “Target Optionsâ€</a> for more information about specific options that address these aspects of a packet.
</div><div class="para">
The options used with specific <code class="command">iptables</code> rules must be grouped logically, based on the purpose and conditions of the overall rule, for the rule to be valid. The remainder of this section explains commonly-used options for the <code class="command">iptables</code> command.
- </div><div class="section" title="2.9.2.1. Structure of IPTables Command Options" id="sect-Security_Guide-Command_Options_for_IPTables-Structure_of_IPTables_Command_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.9.2.1. Structure of IPTables Command Options</h4></div></div></div><div class="para">
+ </div><div class="section" title="2.9.2.1. Structure of IPTables Command Options" id="sect-Security_Guide-Command_Options_for_IPTables-Structure_of_IPTables_Command_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Command_Options_for_IPTables-Structure_of_IPTables_Command_Options">2.9.2.1. Structure of IPTables Command Options</h4></div></div></div><div class="para">
Many <code class="command">iptables</code> commands have the following structure:
- </div><pre class="screen"><code class="computeroutput"> iptables [-t <em class="replaceable"><code><table-name></code></em>] <em class="replaceable"><code><command></code></em> <em class="replaceable"><code><chain-name></code></em> \ <em class="replaceable"><code><parameter-1></code></em> <em class="replaceable"><code><option-1></code></em> \ <em class="replaceable"><code><parameter-n></code></em> <em class="replaceable"><code><option-n></code></em></code>
-</pre><div class="para">
+ </div><pre class="screen"><code class="computeroutput"> iptables [-t <em class="replaceable"><code><table-name></code></em>] <em class="replaceable"><code><command></code></em> <em class="replaceable"><code><chain-name></code></em> \ <em class="replaceable"><code><parameter-1></code></em> <em class="replaceable"><code><option-1></code></em> \ <em class="replaceable"><code><parameter-n></code></em> <em class="replaceable"><code><option-n></code></em></code></pre><div class="para">
<em class="replaceable"><code><table-name></code></em> — Specifies which table the rule applies to. If omitted, the <code class="option">filter</code> table is used.
</div><div class="para">
<em class="replaceable"><code><command></code></em> — Specifies the action to perform, such as appending or deleting a rule.
@@ -3559,7 +3378,7 @@ include "/etc/racoon/<em class="replaceable"><code>X.X.X.X</code></em>.conf"
In contrast, a command that adds a rule which filters packets from a particular subnet using a variety of specific parameters and options can be rather long. When constructing <code class="command">iptables</code> commands, it is important to remember that some parameters and options require further parameters and options to construct a valid rule. This can produce a cascading effect, with the further parameters requiring yet more parameters. Until every parameter and option that requires another set of options is satisfied, the rule is not valid.
</div><div class="para">
Type <code class="command">iptables -h</code> to view a comprehensive list of <code class="command">iptables</code> command structures.
- </div></div><div class="section" title="2.9.2.2. Command Options" id="sect-Security_Guide-Command_Options_for_IPTables-Command_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.9.2.2. Command Options</h4></div></div></div><div class="para">
+ </div></div><div class="section" title="2.9.2.2. Command Options" id="sect-Security_Guide-Command_Options_for_IPTables-Command_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Command_Options_for_IPTables-Command_Options">2.9.2.2. Command Options</h4></div></div></div><div class="para">
Command options instruct <code class="command">iptables</code> to perform a specific action. Only one command option is allowed per <code class="command">iptables</code> command. With the exception of the help command, all commands are written in upper-case characters.
</div><div class="para">
The <code class="command">iptables</code> commands are as follows:
@@ -3585,8 +3404,7 @@ include "/etc/racoon/<em class="replaceable"><code>X.X.X.X</code></em>.conf"
This is especially important when adding rules using the <code class="option">-I</code> with an integer argument. If you specify an existing number when adding a rule to a chain, <code class="command">iptables</code> adds the new rule <span class="emphasis"><em>before</em></span> (or above) the existing rule.
</div></div></li><li class="listitem"><div class="para">
<code class="option">-L</code> — Lists all of the rules in the chain specified after the command. To list all rules in all chains in the default <code class="option">filter</code> table, do not specify a chain or table. Otherwise, the following syntax should be used to list the rules in a specific chain in a particular table:
- </div><pre class="screen"><code class="computeroutput"> iptables -L <em class="replaceable"><code><chain-name></code></em> -t <em class="replaceable"><code><table-name></code></em></code>
-</pre><div class="para">
+ </div><pre class="screen"><code class="computeroutput"> iptables -L <em class="replaceable"><code><chain-name></code></em> -t <em class="replaceable"><code><table-name></code></em></code></pre><div class="para">
Additional options for the <code class="option">-L</code> command option, which provide rule numbers and allow more verbose rule descriptions, are described in <a class="xref" href="#sect-Security_Guide-Command_Options_for_IPTables-Listing_Options" title="2.9.2.6. Listing Options">Section 2.9.2.6, “Listing Optionsâ€</a>.
</div></li><li class="listitem"><div class="para">
<code class="option">-N</code> — Creates a new chain with a user-specified name. The chain name must be unique, otherwise an error message is displayed.
@@ -3598,7 +3416,7 @@ include "/etc/racoon/<em class="replaceable"><code>X.X.X.X</code></em>.conf"
<code class="option">-X</code> — Deletes a user-specified chain. You cannot delete a built-in chain.
</div></li><li class="listitem"><div class="para">
<code class="option">-Z</code> — Sets the byte and packet counters in all chains for a table to zero.
- </div></li></ul></div></div><div class="section" title="2.9.2.3. IPTables Parameter Options" id="sect-Security_Guide-Command_Options_for_IPTables-IPTables_Parameter_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.9.2.3. IPTables Parameter Options</h4></div></div></div><div class="para">
+ </div></li></ul></div></div><div class="section" title="2.9.2.3. IPTables Parameter Options" id="sect-Security_Guide-Command_Options_for_IPTables-IPTables_Parameter_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Command_Options_for_IPTables-IPTables_Parameter_Options">2.9.2.3. IPTables Parameter Options</h4></div></div></div><div class="para">
Certain <code class="command">iptables</code> commands, including those used to add, append, delete, insert, or replace rules within a particular chain, require various parameters to construct a packet filtering rule.
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="option">-c</code> — Resets the counters for a particular rule. This parameter accepts the <code class="option">PKTS</code> and <code class="option">BYTES</code> options to specify which counter to reset.
@@ -3644,21 +3462,18 @@ include "/etc/racoon/<em class="replaceable"><code>X.X.X.X</code></em>.conf"
The "<code class="option">all</code>" protocol means the rule applies to every supported protocol. If no protocol is listed with this rule, it defaults to "<code class="option">all</code>".
</div></li><li class="listitem"><div class="para">
<code class="option">-s</code> — Sets the source for a particular packet using the same syntax as the destination (<code class="option">-d</code>) parameter.
- </div></li></ul></div></div><div class="section" title="2.9.2.4. IPTables Match Options" id="sect-Security_Guide-Command_Options_for_IPTables-IPTables_Match_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.9.2.4. IPTables Match Options</h4></div></div></div><div class="para">
+ </div></li></ul></div></div><div class="section" title="2.9.2.4. IPTables Match Options" id="sect-Security_Guide-Command_Options_for_IPTables-IPTables_Match_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Command_Options_for_IPTables-IPTables_Match_Options">2.9.2.4. IPTables Match Options</h4></div></div></div><div class="para">
Different network protocols provide specialized matching options which can be configured to match a particular packet using that protocol. However, the protocol must first be specified in the <code class="command">iptables</code> command. For example, <code class="option">-p <em class="replaceable"><code><protocol-name></code></em></code> enables options for the specified protocol. Note that you can also use the protocol ID, instead of the protocol name. Refer to the following examples, each of which have the same effect:
- </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">
+ </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">
Service definitions are provided in the <code class="filename">/etc/services</code> file. For readability, it is recommended that you use the service names rather than the port numbers.
</div><div class="warning"><h2>Warning</h2><div class="para">
Secure the <code class="filename">/etc/services</code> file to prevent unauthorized editing. If this file is editable, crackers can use it to enable ports on your machine you have otherwise closed. To secure this file, type the following commands as 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">
+[root at myServer ~]# chattr +i /etc/services</pre><div class="para">
This prevents the file from being renamed, deleted or having links made to it.
- </div></div><div class="section" title="2.9.2.4.1. TCP Protocol" id="sect-Security_Guide-IPTables_Match_Options-TCP_Protocol"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.9.2.4.1. TCP Protocol</h5></div></div></div><div class="para">
+ </div></div><div class="section" title="2.9.2.4.1. TCP Protocol" id="sect-Security_Guide-IPTables_Match_Options-TCP_Protocol"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-Security_Guide-IPTables_Match_Options-TCP_Protocol">2.9.2.4.1. TCP Protocol</h5></div></div></div><div class="para">
These match options are available for the TCP protocol (<code class="option">-p tcp</code>):
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="option">--dport</code> — Sets the destination port for the packet.
@@ -3708,7 +3523,7 @@ include "/etc/racoon/<em class="replaceable"><code>X.X.X.X</code></em>.conf"
Use the exclamation point character (<code class="option">!</code>) after the <code class="option">--tcp-flags</code> to reverse the effect of the match option.
</div></li><li class="listitem"><div class="para">
<code class="option">--tcp-option</code> — Attempts to match with TCP-specific options that can be set within a particular packet. This match option can also be reversed with the exclamation point character (<code class="option">!</code>).
- </div></li></ul></div></div><div class="section" title="2.9.2.4.2. UDP Protocol" id="sect-Security_Guide-IPTables_Match_Options-UDP_Protocol"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.9.2.4.2. UDP Protocol</h5></div></div></div><div class="para">
+ </div></li></ul></div></div><div class="section" title="2.9.2.4.2. UDP Protocol" id="sect-Security_Guide-IPTables_Match_Options-UDP_Protocol"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-Security_Guide-IPTables_Match_Options-UDP_Protocol">2.9.2.4.2. UDP Protocol</h5></div></div></div><div class="para">
These match options are available for the UDP protocol (<code class="option">-p udp</code>):
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="option">--dport</code> — Specifies the destination port of the UDP packet, using the service name, port number, or range of port numbers. The <code class="option">--destination-port</code> match option is synonymous with <code class="option">--dport</code>.
@@ -3716,11 +3531,11 @@ include "/etc/racoon/<em class="replaceable"><code>X.X.X.X</code></em>.conf"
<code class="option">--sport</code> — Specifies the source port of the UDP packet, using the service name, port number, or range of port numbers. The <code class="option">--source-port</code> match option is synonymous with <code class="option">--sport</code>.
</div></li></ul></div><div class="para">
For the <code class="option">--dport</code> and <code class="option">--sport</code> options, to specify a range of port numbers, separate the two numbers with a colon (:). For example: <code class="option">-p tcp --dport 3000:3200</code>. The largest acceptable valid range is 0:65535.
- </div></div><div class="section" title="2.9.2.4.3. ICMP Protocol" id="sect-Security_Guide-IPTables_Match_Options-ICMP_Protocol"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.9.2.4.3. ICMP Protocol</h5></div></div></div><div class="para">
+ </div></div><div class="section" title="2.9.2.4.3. ICMP Protocol" id="sect-Security_Guide-IPTables_Match_Options-ICMP_Protocol"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-Security_Guide-IPTables_Match_Options-ICMP_Protocol">2.9.2.4.3. ICMP Protocol</h5></div></div></div><div class="para">
The following match options are available for the Internet Control Message Protocol (ICMP) (<code class="option">-p icmp</code>):
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="option">--icmp-type</code> — Sets the name or number of the ICMP type to match with the rule. A list of valid ICMP names can be retrieved by typing the <code class="command">iptables -p icmp -h</code> command.
- </div></li></ul></div></div><div class="section" title="2.9.2.4.4. Additional Match Option Modules" id="sect-Security_Guide-IPTables_Match_Options-Additional_Match_Option_Modules"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.9.2.4.4. Additional Match Option Modules</h5></div></div></div><div class="para">
+ </div></li></ul></div></div><div class="section" title="2.9.2.4.4. Additional Match Option Modules" id="sect-Security_Guide-IPTables_Match_Options-Additional_Match_Option_Modules"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-Security_Guide-IPTables_Match_Options-Additional_Match_Option_Modules">2.9.2.4.4. Additional Match Option Modules</h5></div></div></div><div class="para">
Additional match options are available through modules loaded by the <code class="command">iptables</code> command.
</div><div class="para">
To use a match option module, load the module by name using the <code class="option">-m <em class="replaceable"><code><module-name></code></em></code>, where <em class="replaceable"><code><module-name></code></em> is the name of the module.
@@ -3772,7 +3587,7 @@ include "/etc/racoon/<em class="replaceable"><code>X.X.X.X</code></em>.conf"
<code class="option">--mac-source</code> — Matches a MAC address of the network interface card that sent the packet. To exclude a MAC address from a rule, place an exclamation point character (<code class="option">!</code>) after the <code class="option">--mac-source</code> match option.
</div></li></ul></div></li></ul></div><div class="para">
Refer to the <code class="command">iptables</code> man page for more match options available through modules.
- </div></div></div><div class="section" title="2.9.2.5. Target Options" id="sect-Security_Guide-Command_Options_for_IPTables-Target_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.9.2.5. Target Options</h4></div></div></div><div class="para">
+ </div></div></div><div class="section" title="2.9.2.5. Target Options" id="sect-Security_Guide-Command_Options_for_IPTables-Target_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Command_Options_for_IPTables-Target_Options">2.9.2.5. Target Options</h4></div></div></div><div class="para">
When a packet has matched a particular rule, the rule can direct the packet to a number of different targets which determine the appropriate action. Each chain has a default target, which is used if none of the rules on that chain match a packet or if none of the rules which match the packet specify a target.
</div><div class="para">
The following are the standard targets:
@@ -3812,7 +3627,7 @@ include "/etc/racoon/<em class="replaceable"><code>X.X.X.X</code></em>.conf"
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><div class="section" title="2.9.2.6. Listing Options" id="sect-Security_Guide-Command_Options_for_IPTables-Listing_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.9.2.6. Listing Options</h4></div></div></div><div class="para">
+ </div></div><div class="section" title="2.9.2.6. Listing Options" id="sect-Security_Guide-Command_Options_for_IPTables-Listing_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Command_Options_for_IPTables-Listing_Options">2.9.2.6. Listing Options</h4></div></div></div><div class="para">
The default list command, <code class="command">iptables -L [<chain-name>]</code>, provides a very basic overview of the default filter table's current chains. Additional options provide more information:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="option">-v</code> — Displays verbose output, such as the number of packets and bytes each chain has processed, the number of packets and bytes each rule has matched, and which interfaces apply to a particular rule.
@@ -3824,10 +3639,9 @@ include "/etc/racoon/<em class="replaceable"><code>X.X.X.X</code></em>.conf"
<code class="option">--line-numbers</code> — Lists rules in each chain next to their numeric order in the chain. This option is useful when attempting to delete the specific rule in a chain or to locate where to insert a rule within a chain.
</div></li><li class="listitem"><div class="para">
<code class="option">-t <table-name></code> — Specifies a table name. If omitted, defaults to the filter table.
- </div></li></ul></div></div></div><div class="section" title="2.9.3. Saving IPTables Rules" id="sect-Security_Guide-IPTables-Saving_IPTables_Rules"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.9.3. Saving IPTables Rules</h3></div></div></div><div class="para">
+ </div></li></ul></div></div></div><div class="section" title="2.9.3. Saving IPTables Rules" id="sect-Security_Guide-IPTables-Saving_IPTables_Rules"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-IPTables-Saving_IPTables_Rules">2.9.3. Saving IPTables Rules</h3></div></div></div><div class="para">
Rules created with the <code class="command">iptables</code> command are stored in memory. If the system is restarted before saving the <code class="command">iptables</code> rule set, all rules are lost. For netfilter rules to persist through a system reboot, they need to be saved. To save netfilter rules, type the following command as root:
- </div><pre class="screen"><code class="command"> /sbin/service iptables save </code>
-</pre><div class="para">
+ </div><pre class="screen"><code class="command"> /sbin/service iptables save </code></pre><div class="para">
This executes the <code class="command">iptables</code> init script, which runs the <code class="command">/sbin/iptables-save</code> program and writes the current <code class="command">iptables</code> configuration to <code class="filename">/etc/sysconfig/iptables</code>. The existing <code class="filename">/etc/sysconfig/iptables</code> file is saved as <code class="filename">/etc/sysconfig/iptables.save</code>.
</div><div class="para">
The next time the system boots, the <code class="command">iptables</code> init script reapplies the rules saved in <code class="filename">/etc/sysconfig/iptables</code> by using the <code class="command">/sbin/iptables-restore</code> command.
@@ -3835,12 +3649,11 @@ include "/etc/racoon/<em class="replaceable"><code>X.X.X.X</code></em>.conf"
While it is always a good idea to test a new <code class="command">iptables</code> rule before committing it to the <code class="filename">/etc/sysconfig/iptables</code> file, it is possible to copy <code class="command">iptables</code> rules into this file from another system's version of this file. This provides a quick way to distribute sets of <code class="command">iptables</code> rules to multiple machines.
</div><div class="para">
You can also save the iptables rules to a separate file for distribution, backup or other purposes. To save your iptables rules, type the following command as 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">
+ </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">
If distributing the <code class="filename">/etc/sysconfig/iptables</code> file to other machines, type <code class="command">/sbin/service iptables restart</code> for the new rules to take effect.
</div></div><div class="note"><h2>Note</h2><div class="para">
Note the difference between the <code class="command">iptables</code> <span class="emphasis"><em>command</em></span> (<code class="command">/sbin/iptables</code>), which is used to manipulate the tables and chains that constitute the <code class="command">iptables</code> functionality, and the <code class="command">iptables</code> <span class="emphasis"><em>service</em></span> (<code class="command">/sbin/iptables service</code>), which is used to enable and disable the <code class="command">iptables</code> service itself.
- </div></div></div><div class="section" title="2.9.4. IPTables Control Scripts" id="sect-Security_Guide-IPTables-IPTables_Control_Scripts"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.9.4. IPTables Control Scripts</h3></div></div></div><div class="para">
+ </div></div></div><div class="section" title="2.9.4. IPTables Control Scripts" id="sect-Security_Guide-IPTables-IPTables_Control_Scripts"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-IPTables-IPTables_Control_Scripts">2.9.4. IPTables Control Scripts</h3></div></div></div><div class="para">
There are two basic methods for controlling <code class="command">iptables</code> in Fedora:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<span class="application"><strong>Firewall Configuration Tool</strong></span> (<code class="command">system-config-securitylevel</code>) — A graphical interface for creating, activating, and saving basic firewall rules. Refer to <a class="xref" href="#sect-Security_Guide-Firewalls-Basic_Firewall_Configuration" title="2.8.2. Basic Firewall Configuration">Section 2.8.2, “Basic Firewall Configurationâ€</a> for more information.
@@ -3848,8 +3661,7 @@ include "/etc/racoon/<em class="replaceable"><code>X.X.X.X</code></em>.conf"
<code class="command">/sbin/service iptables <em class="replaceable"><code><option></code></em></code> — Used to manipulate various functions of <code class="command">iptables</code> using its initscript. The following options are available:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="command">start</code> — If a firewall is configured (that is, <code class="filename">/etc/sysconfig/iptables</code> exists), all running <code class="command">iptables</code> are stopped completely and then started using the <code class="command">/sbin/iptables-restore</code> command. This option only works if the <code class="command">ipchains</code> kernel module is not loaded. To check if this module is loaded, type the following command as root:
- </div><pre class="screen"><code class="command"> [root at MyServer ~]# lsmod | grep ipchains </code>
-</pre><div class="para">
+ </div><pre class="screen"><code class="command"> [root at MyServer ~]# lsmod | grep ipchains </code></pre><div class="para">
If this command returns no output, it means the module is not loaded. If necessary, use the <code class="command">/sbin/rmmod</code> command to remove the module.
</div></li><li class="listitem"><div class="para">
<code class="command">stop</code> — If a firewall is running, the firewall rules in memory are flushed, and all iptables modules and helpers are unloaded.
@@ -3875,7 +3687,7 @@ include "/etc/racoon/<em class="replaceable"><code>X.X.X.X</code></em>.conf"
<code class="command">save</code> — Saves firewall rules to <code class="filename">/etc/sysconfig/iptables</code> using <code class="command">iptables-save</code>. Refer to <a class="xref" href="#sect-Security_Guide-IPTables-Saving_IPTables_Rules" title="2.9.3. Saving IPTables Rules">Section 2.9.3, “Saving IPTables Rulesâ€</a> for more information.
</div></li></ul></div></li></ul></div><div class="note"><h2>Note</h2><div class="para">
To use the same initscript commands to control netfilter for IPv6, substitute <code class="command">ip6tables</code> for <code class="command">iptables</code> in the <code class="command">/sbin/service</code> commands listed in this section. For more information about IPv6 and netfilter, refer to <a class="xref" href="#sect-Security_Guide-IPTables-IPTables_and_IPv6" title="2.9.5. IPTables and IPv6">Section 2.9.5, “IPTables and IPv6â€</a>.
- </div></div><div class="section" title="2.9.4.1. IPTables Control Scripts Configuration File" id="sect-Security_Guide-IPTables_Control_Scripts-IPTables_Control_Scripts_Configuration_File"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.9.4.1. IPTables Control Scripts Configuration File</h4></div></div></div><div class="para">
+ </div></div><div class="section" title="2.9.4.1. IPTables Control Scripts Configuration File" id="sect-Security_Guide-IPTables_Control_Scripts-IPTables_Control_Scripts_Configuration_File"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-IPTables_Control_Scripts-IPTables_Control_Scripts_Configuration_File">2.9.4.1. IPTables Control Scripts Configuration File</h4></div></div></div><div class="para">
The behavior of the <code class="command">iptables</code> initscripts is controlled by the <code class="filename">/etc/sysconfig/iptables-config</code> configuration file. The following is a list of directives contained in this file:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="command">IPTABLES_MODULES</code> — Specifies a space-separated list of additional <code class="command">iptables</code> modules to load when a firewall is activated. These can include connection tracking and NAT helpers.
@@ -3909,7 +3721,7 @@ include "/etc/racoon/<em class="replaceable"><code>X.X.X.X</code></em>.conf"
<code class="command">yes</code> — The default value. Returns only IP addresses within a status output.
</div></li><li class="listitem"><div class="para">
<code class="command">no</code> — Returns domain or hostnames within a status output.
- </div></li></ul></div></li></ul></div></div></div><div class="section" title="2.9.5. IPTables and IPv6" id="sect-Security_Guide-IPTables-IPTables_and_IPv6"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.9.5. IPTables and IPv6</h3></div></div></div><div class="para">
+ </div></li></ul></div></li></ul></div></div></div><div class="section" title="2.9.5. IPTables and IPv6" id="sect-Security_Guide-IPTables-IPTables_and_IPv6"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-IPTables-IPTables_and_IPv6">2.9.5. IPTables and IPv6</h3></div></div></div><div class="para">
If the <code class="filename">iptables-ipv6</code> package is installed, netfilter in Fedora can filter the next-generation IPv6 Internet protocol. The command used to manipulate the IPv6 netfilter is <code class="command">ip6tables</code>.
</div><div class="para">
Most directives for this command are identical to those used for <code class="command">iptables</code>, except the <code class="command">nat</code> table is not yet supported. This means that it is not yet possible to perform IPv6 network address translation tasks, such as masquerading and port forwarding.
@@ -3919,53 +3731,53 @@ include "/etc/racoon/<em class="replaceable"><code>X.X.X.X</code></em>.conf"
Configuration options for the <code class="command">ip6tables</code> init script are stored in <code class="filename">/etc/sysconfig/ip6tables-config</code>, and the names for each directive vary slightly from their <code class="command">iptables</code> counterparts.
</div><div class="para">
For example, the <code class="filename">iptables-config</code> directive <code class="command">IPTABLES_MODULES</code>:the equivalent in the <code class="filename">ip6tables-config</code> file is <code class="command">IP6TABLES_MODULES</code>.
- </div></div><div class="section" title="2.9.6. Additional Resources" id="sect-Security_Guide-IPTables-Additional_Resources"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.9.6. Additional Resources</h3></div></div></div><div class="para">
+ </div></div><div class="section" title="2.9.6. Additional Resources" id="sect-Security_Guide-IPTables-Additional_Resources"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-IPTables-Additional_Resources">2.9.6. Additional Resources</h3></div></div></div><div class="para">
Refer to the following sources for additional information on packet filtering with <code class="command">iptables</code>.
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<a class="xref" href="#sect-Security_Guide-Firewalls" title="2.8. Firewalls">Section 2.8, “Firewallsâ€</a> — Contains a chapter about the role of firewalls within an overall security strategy as well as strategies for constructing firewall rules.
- </div></li></ul></div><div class="section" title="2.9.6.1. Installed IP Tables Documentation" id="sect-Security_Guide-Additional_Resources-Installed_IP_Tables_Documentation"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.9.6.1. Installed IP Tables Documentation</h4></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ </div></li></ul></div><div class="section" title="2.9.6.1. Installed IP Tables Documentation" id="sect-Security_Guide-Additional_Resources-Installed_IP_Tables_Documentation"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Additional_Resources-Installed_IP_Tables_Documentation">2.9.6.1. Installed IP Tables Documentation</h4></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="command">man iptables</code> — Contains a description of <code class="command">iptables</code> as well as a comprehensive list of targets, options, and match extensions.
- </div></li></ul></div></div><div class="section" title="2.9.6.2. Useful IP Tables Websites" id="sect-Security_Guide-Additional_Resources-Useful_IP_Tables_Websites"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.9.6.2. Useful IP Tables Websites</h4></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ </div></li></ul></div></div><div class="section" title="2.9.6.2. Useful IP Tables Websites" id="sect-Security_Guide-Additional_Resources-Useful_IP_Tables_Websites"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Additional_Resources-Useful_IP_Tables_Websites">2.9.6.2. Useful IP Tables Websites</h4></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<a href="http://www.netfilter.org/">http://www.netfilter.org/</a> — The home of the netfilter/iptables project. Contains assorted information about <code class="command">iptables</code>, including a FAQ addressing specific problems and various helpful guides by Rusty Russell, the Linux IP firewall maintainer. The HOWTO documents on the site cover subjects such as basic networking concepts, kernel packet filtering, and NAT configurations.
</div></li><li class="listitem"><div class="para">
<a href="http://www.linuxnewbie.org/nhf/Security/IPtables_Basics.html">http://www.linuxnewbie.org/nhf/Security/IPtables_Basics.html</a> — An introduction to the way packets move through the Linux kernel, plus an introduction to constructing basic <code class="command">iptables</code> commands.
- </div></li></ul></div></div></div></div><div class="footnotes"><br /><hr width="100" align="left" /><div class="footnote"><p><sup>[<a id="ftn.id3210155" href="#id3210155" class="para">11</a>] </sup>
+ </div></li></ul></div></div></div></div><div class="footnotes"><br /><hr width="100" align="left" /><div class="footnote"><p><sup>[<a id="ftn.id2898454" href="#id2898454" 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.id4010587" href="#id4010587" class="para">12</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id2924302" href="#id2924302" 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.id3702298" href="#id3702298" class="para">13</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id2718397" href="#id2718397" class="para">13</a>] </sup>
This access is still subject to the restrictions imposed by SELinux, if it is enabled.
- </p></div><div class="footnote"><p><sup>[<a id="ftn.id3440357" href="#id3440357" class="para">14</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id2824038" href="#id2824038" class="para">14</a>] </sup>
A system where both the client and the server share a common key that is used to encrypt and decrypt network communication.
</p></div></div></div><div xml:lang="en-US" class="chapter" title="Chapter 3. Encryption" id="chap-Security_Guide-Encryption" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 3. Encryption</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Security_Guide-Encryption-Data_at_Rest">3.1. Data at Rest</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Encryption-Protecting_Data_at_Rest-Full_Disk_Encryption">3.2. Full Disk Encryption</a></span></dt><dt><span class="section"><a href="#Security_Guide-Encryption-Protecting_Data_at_Rest-File_Based_Encryption">3.3. File Based Encryption</a></span></dt><dt><span class="section"><a href="#Security_Guide-Encryption-Data_in_Motion">3.4. Data in Motion</a></span></dt><dt><span class="section"><a href="#Security_Guide-Encryption-Data_in_Motion-Virtual_Private_Networks">3.5. Virtual Private Networks</a></span></dt><dt><span class="section"><a href="#Security_Gu
ide-Encryption-Data_in_Motion-Secure_Shell">3.6. Secure Shell</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-LUKS_Disk_Encryption">3.7. LUKS Disk Encryption</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-LUKS_Disk_Encryption-LUKS_Implementation_in_Fedora">3.7.1. LUKS Implementation in Fedora</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories">3.7.2. Manually Encrypting Directories</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-Step_by_Step_Instructions">3.7.3. Step-by-Step Instructions</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-What_you_have_just_accomplished">3.7.4. What you have just accomplished.</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-LUKS_Disk_Encryption-Lin
ks_of_Interest">3.7.5. Links of Interest</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives">3.8. 7-Zip Encrypted Archives</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Installation">3.8.1. 7-Zip Installation in Fedora</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Installation-Instructions">3.8.2. Step-by-Step Installation Instructions</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Usage_Instructions">3.8.3. Step-by-Step Usage Instructions</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Things_of_note">3.8.4. Things of note</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Security_Guide-Encryption-Using_GPG">3.9. Using GNU Privacy Guard (GnuPG)</a><
/span></dt><dd><dl><dt><span class="section"><a href="#sect-Security_Guide-Encryption-Using_GPG-Keys_in_GNOME">3.9.1. Generating GPG Keys in GNOME</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE1">3.9.2. Generating GPG Keys in KDE</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE">3.9.3. Generating GPG Keys Using the Command Line</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Alpine">3.9.4. Using GPG with Alpine</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution">3.9.5. Using GPG with Evolution</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Thunderbird">3.9.6. Using GPG with Thunderbird</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-En
cryption-Using_GPG-About_Public_Key_Encryption">3.9.7. About Public Key Encryption</a></span></dt></dl></dd></dl></div><div class="para">
There are two main types of data that must be protected: data at rest and data in motion. These different types of data are protected in similar ways using similar technology but the implementations can be completely different. No single protective implementation can prevent all possible methods of compromise as the same information may be at rest and in motion at different points in time.
- </div><div class="section" title="3.1. Data at Rest" id="sect-Security_Guide-Encryption-Data_at_Rest"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">3.1. Data at Rest</h2></div></div></div><div class="para">
+ </div><div class="section" title="3.1. Data at Rest" id="sect-Security_Guide-Encryption-Data_at_Rest"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sect-Security_Guide-Encryption-Data_at_Rest">3.1. Data at Rest</h2></div></div></div><div class="para">
Data at rest is data that is stored on a hard drive, tape, CD, DVD, disk, or other media. This information's biggest threat comes from being physically stolen. Laptops in airports, CDs going through the mail, and backup tapes that get left in the wrong places are all examples of events where data can be compromised through theft. If the data was encrypted on the media then you wouldn't have to worry as much about the data being compromised.
- </div></div><div class="section" title="3.2. Full Disk Encryption" id="sect-Security_Guide-Encryption-Protecting_Data_at_Rest-Full_Disk_Encryption"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">3.2. Full Disk Encryption</h2></div></div></div><div class="para">
+ </div></div><div class="section" title="3.2. Full Disk Encryption" id="sect-Security_Guide-Encryption-Protecting_Data_at_Rest-Full_Disk_Encryption"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sect-Security_Guide-Encryption-Protecting_Data_at_Rest-Full_Disk_Encryption">3.2. Full Disk Encryption</h2></div></div></div><div class="para">
Full disk or partition encryption is one of the best ways of protecting your data. Not only is each file protected but also the temporary storage that may contain parts of these files is also protected. Full disk encryption will protect all of your files so you don't have to worry about selecting what you want to protect and possibly missing a file.
</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">
Full disk encryption solutions like LUKS only protect the data when your computer is off. Once the computer is on and LUKS has decrypted the disk, the files on that disk are available to anyone who would normally have access to them. To protect your files when the computer is on, use full disk encryption in combination with another solution such as file based encryption. Also remember to lock your computer whenever you are away from it. A passphrase protected screen saver set to activate after a few minutes of inactivity is a good way to keep intruders out.
- </div></div><div class="section" title="3.3. File Based Encryption" id="Security_Guide-Encryption-Protecting_Data_at_Rest-File_Based_Encryption"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">3.3. File Based Encryption</h2></div></div></div><div class="para">
+ </div></div><div class="section" title="3.3. File Based Encryption" id="Security_Guide-Encryption-Protecting_Data_at_Rest-File_Based_Encryption"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="Security_Guide-Encryption-Protecting_Data_at_Rest-File_Based_Encryption">3.3. File Based Encryption</h2></div></div></div><div class="para">
GnuPG (GPG) is an open source version of PGP that allows you to sign and/or encrypt a file or an email message. This is useful to maintain integrity of the message or file and also protects the confidentiality of the information contained within the file or email. In the case of email, GPG provides dual protection. Not only can it provide Data at Rest protection but also Data In Motion protection once the message has been sent across the network.
</div><div class="para">
File based encryption is intended to protect a file after it has left your computer, such as when you send a CD through the mail. Some file based encryption solutions will leave remnants of the encrypted files that an attacker who has physical access to your computer can recover under some circumstances. To protect the contents of those files from attackers who may have access to your computer, use file based encryption combined with another solution such as full disk encryption.
- </div></div><div class="section" title="3.4. Data in Motion" id="Security_Guide-Encryption-Data_in_Motion"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">3.4. Data in Motion</h2></div></div></div><div class="para">
+ </div></div><div class="section" title="3.4. Data in Motion" id="Security_Guide-Encryption-Data_in_Motion"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="Security_Guide-Encryption-Data_in_Motion">3.4. Data in Motion</h2></div></div></div><div class="para">
Data in motion is data that is being transmitted over a network. The biggest threats to data in motion are interception and alteration. Your user name and password should never be transmitted over a network without protection as it could be intercepted and used by someone else to impersonate you or gain access to sensitive information. Other private information such as bank account information should also be protected when transmitted across a network. If the network session was encrypted then you would not have to worry as much about the data being compromised while it is being transmitted.
</div><div class="para">
Data in motion is particularly vulnerable to attackers because the attacker does not have to be near the computer in which the data is being stored rather they only have to be somewhere along the path. Encryption tunnels can protect data along the path of communications.
- </div></div><div class="section" title="3.5. Virtual Private Networks" id="Security_Guide-Encryption-Data_in_Motion-Virtual_Private_Networks"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">3.5. Virtual Private Networks</h2></div></div></div><div class="para">
+ </div></div><div class="section" title="3.5. Virtual Private Networks" id="Security_Guide-Encryption-Data_in_Motion-Virtual_Private_Networks"><div class="titlepage"><div><div keep-together.within-column="always"><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">
Virtual Private Networks (VPN) provide encrypted tunnels between computers or networks of computers across all ports. With a VPN in place, all network traffic from the client is forwarded to the server through the encrypted tunnel. This means that the client is logically on the same network as the server it is connected to via the VPN. VPNs are very common and are simple to use and setup.
- </div></div><div class="section" title="3.6. Secure Shell" id="Security_Guide-Encryption-Data_in_Motion-Secure_Shell"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">3.6. Secure Shell</h2></div></div></div><div class="para">
+ </div></div><div class="section" title="3.6. Secure Shell" id="Security_Guide-Encryption-Data_in_Motion-Secure_Shell"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="Security_Guide-Encryption-Data_in_Motion-Secure_Shell">3.6. Secure Shell</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><div xml:lang="en-US" class="section" title="3.7. LUKS Disk Encryption" id="sect-Security_Guide-LUKS_Disk_Encryption" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">3.7. LUKS Disk Encryption</h2></div></div></div><div class="para">
+ </div></div><div xml:lang="en-US" class="section" title="3.7. LUKS Disk Encryption" id="sect-Security_Guide-LUKS_Disk_Encryption" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sect-Security_Guide-LUKS_Disk_Encryption">3.7. LUKS Disk Encryption</h2></div></div></div><div class="para">
Linux Unified Key Setup-on-disk-format (or LUKS) allows you to encrypt partitions on your Linux computer. This is particularly important when it comes to mobile computers and removable media. LUKS allows multiple user keys to decrypt a master key which is used for the bulk encryption of the partition.
- </div><div class="section" title="3.7.1. LUKS Implementation in Fedora" id="sect-Security_Guide-LUKS_Disk_Encryption-LUKS_Implementation_in_Fedora"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.7.1. LUKS Implementation in Fedora</h3></div></div></div><div class="para">
+ </div><div class="section" title="3.7.1. LUKS Implementation in Fedora" id="sect-Security_Guide-LUKS_Disk_Encryption-LUKS_Implementation_in_Fedora"><div class="titlepage"><div><div keep-together.within-column="always"><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:
@@ -3979,13 +3791,13 @@ include "/etc/racoon/<em class="replaceable"><code>X.X.X.X</code></em>.conf"
cast5 - <a href="http://www.ietf.org/rfc/rfc2144.txt">RFC 2144</a>
</div></li><li class="listitem"><div class="para">
cast6 - <a href="http://www.ietf.org/rfc/rfc2612.txt">RFC 2612</a>
- </div></li></ul></div></div><div class="section" title="3.7.2. Manually Encrypting Directories" id="sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.7.2. Manually Encrypting Directories</h3></div></div></div><div class="warning"><h2>Warning</h2><div class="para">
+ </div></li></ul></div></div><div class="section" title="3.7.2. Manually Encrypting Directories" id="sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories"><div class="titlepage"><div><div keep-together.within-column="always"><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">
If you are running a version of Fedora prior to Fedora 9 and want to encrypt a partition, or you want to encrypt a partition after the installation of the current version of Fedora, the following directions are for you. The below example demonstrates encrypting your /home partition but any partition can be used.
</div><div class="para">
The following procedure will wipe all your existing data, so be sure to have a tested backup before you start. This also requires you to have a separate partition for /home (in my case that is /dev/VG00/LV_home). All the following must be done as root. Any of these steps failing means you must not continue until the step succeeded.
- </div></div><div class="section" title="3.7.3. Step-by-Step Instructions" id="sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-Step_by_Step_Instructions"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.7.3. Step-by-Step Instructions</h3></div></div></div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ </div></div><div class="section" title="3.7.3. Step-by-Step Instructions" id="sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-Step_by_Step_Instructions"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><div class="para">
enter runlevel 1: <code class="code">telinit 1</code>
</div></li><li class="listitem"><div class="para">
unmount your existing /home: <code class="code"> umount /home</code>
@@ -4023,25 +3835,25 @@ include "/etc/racoon/<em class="replaceable"><code>X.X.X.X</code></em>.conf"
The entry in /etc/crypttab makes your computer ask your <code class="code">luks</code> passphrase on boot
</div></li><li class="listitem"><div class="para">
Login as root and restore your backup
- </div></li></ol></div></div><div class="section" title="3.7.4. What you have just accomplished." id="sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-What_you_have_just_accomplished"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.7.4. What you have just accomplished.</h3></div></div></div><div class="para">
+ </div></li></ol></div></div><div class="section" title="3.7.4. What you have just accomplished." id="sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-What_you_have_just_accomplished"><div class="titlepage"><div><div keep-together.within-column="always"><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">
Congratulations, you now have an encrypted partition for all of your data to safely rest while the computer is off.
- </div></div><div class="section" title="3.7.5. Links of Interest" id="sect-Security_Guide-LUKS_Disk_Encryption-Links_of_Interest"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.7.5. Links of Interest</h3></div></div></div><div class="para">
+ </div></div><div class="section" title="3.7.5. Links of Interest" id="sect-Security_Guide-LUKS_Disk_Encryption-Links_of_Interest"><div class="titlepage"><div><div keep-together.within-column="always"><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">
For additional information on LUKS or encrypting hard drives under Fedora please visit one of the following links:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<a href="http://clemens.endorphin.org/LUKS/">LUKS - Linux Unified Key Setup</a>
</div></li><li class="listitem"><div class="para">
<a href="https://bugzilla.redhat.com/attachment.cgi?id=161912">HOWTO: Creating an encrypted Physical Volume (PV) using a second hard drive, pvmove, and a Fedora LiveCD</a>
- </div></li></ul></div></div></div><div xml:lang="en-US" class="section" title="3.8. 7-Zip Encrypted Archives" id="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">3.8. 7-Zip Encrypted Archives</h2></div></div></div><div class="para">
+ </div></li></ul></div></div></div><div xml:lang="en-US" class="section" title="3.8. 7-Zip Encrypted Archives" id="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><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" title="3.8.1. 7-Zip Installation in Fedora" id="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Installation"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.8.1. 7-Zip Installation in Fedora</h3></div></div></div><div class="para">
+ </div><div class="section" title="3.8.1. 7-Zip Installation in Fedora" id="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Installation"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="section" title="3.8.2. Step-by-Step Installation Instructions" id="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Installation-Instructions"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.8.2. Step-by-Step Installation Instructions</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ </div></div><div class="section" title="3.8.2. Step-by-Step Installation Instructions" id="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Installation-Instructions"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><div class="para">
Open a Terminal: <code class="code">Click ''Applications'' -> ''System Tools'' -> ''Terminal''</code>
</div></li><li class="listitem"><div class="para">
Install 7-Zip with sudo access: <code class="code">sudo yum install p7zip</code>
</div></li><li class="listitem"><div class="para">
Close the Terminal: <code class="code">exit</code>
- </div></li></ul></div></div><div class="section" title="3.8.3. Step-by-Step Usage Instructions" id="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Usage_Instructions"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.8.3. Step-by-Step Usage Instructions</h3></div></div></div><div class="para">
+ </div></li></ul></div></div><div class="section" title="3.8.3. Step-by-Step Usage Instructions" id="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Usage_Instructions"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><div class="para">
Open a Terminal:<code class="code">Click ''Applications'' -> ''System Tools'' -> ''Terminal''</code>
@@ -4065,15 +3877,15 @@ include "/etc/racoon/<em class="replaceable"><code>X.X.X.X</code></em>.conf"
Delete the test archive and test extraction: <code class="code">rm -r newplace</code>
</div></li><li class="listitem"><div class="para">
Close the Terminal: <code class="code">exit</code>
- </div></li></ul></div></div><div class="section" title="3.8.4. Things of note" id="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Things_of_note"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.8.4. Things of note</h3></div></div></div><div class="para">
+ </div></li></ul></div></div><div class="section" title="3.8.4. Things of note" id="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Things_of_note"><div class="titlepage"><div><div keep-together.within-column="always"><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></div><div xml:lang="en-US" class="section" title="3.9. Using GNU Privacy Guard (GnuPG)" id="sect-Security_Guide-Encryption-Using_GPG" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">3.9. Using GNU Privacy Guard (GnuPG)</h2></div></div></div><div class="para">
+ </div></div></div><div xml:lang="en-US" class="section" title="3.9. Using GNU Privacy Guard (GnuPG)" id="sect-Security_Guide-Encryption-Using_GPG" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sect-Security_Guide-Encryption-Using_GPG">3.9. Using GNU Privacy Guard (GnuPG)</h2></div></div></div><div class="para">
<span class="application"><strong>GnuPG</strong></span> (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="para">
GPG can also be used to sign and/or encrypt files kept on your computer or on a network drive. This can add additional protection in preventing a file from being altered or read by unauthorized people.
</div><div class="para">
To utilize GPG for authentication or encrytion of email you must first generate your public and private keys. After generating the keys you will have to setup your email client to utilize them.
- </div><div class="section" title="3.9.1. Generating GPG Keys in GNOME" id="sect-Security_Guide-Encryption-Using_GPG-Keys_in_GNOME"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.9.1. Generating GPG Keys in GNOME</h3></div></div></div><div class="para">
+ </div><div class="section" title="3.9.1. Generating GPG Keys in GNOME" id="sect-Security_Guide-Encryption-Using_GPG-Keys_in_GNOME"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Encryption-Using_GPG-Keys_in_GNOME">3.9.1. Generating 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 <span class="package">Seahorse</span> 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 <span class="package">Seahorse</span> 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.
@@ -4081,13 +3893,13 @@ include "/etc/racoon/<em class="replaceable"><code>X.X.X.X</code></em>.conf"
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 class="section" title="3.9.2. Generating GPG Keys in KDE" id="sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE1"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.9.2. Generating GPG Keys in KDE</h3></div></div></div><div class="para">
+ </div></div><div class="section" title="3.9.2. Generating GPG Keys in KDE" id="sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE1"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE1">3.9.2. Generating 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><div class="section" title="3.9.3. Generating GPG Keys Using the Command Line" id="sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.9.3. Generating GPG Keys Using the Command Line</h3></div></div></div><div class="para">
+ </div></div><div class="section" title="3.9.3. Generating GPG Keys Using the Command Line" id="sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE">3.9.3. Generating 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.
@@ -4119,14 +3931,13 @@ include "/etc/racoon/<em class="replaceable"><code>X.X.X.X</code></em>.conf"
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><div class="section" title="3.9.4. Using GPG with Alpine" id="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Alpine"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.9.4. Using GPG with Alpine</h3></div></div></div><div class="para">
+ </div></div></div><div class="section" title="3.9.4. Using GPG with Alpine" id="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Alpine"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Alpine">3.9.4. Using GPG with Alpine</h3></div></div></div><div class="para">
If you are using the email client <span class="package">Alpine</span> or <span class="package">Pine</span> then you will also need to download and install <span class="package">ez-pine-gpg</span>. This software is currently available from <a href="http://business-php.com/opensource/ez-pine-gpg/">http://business-php.com/opensource/ez-pine-gpg/</a>. Once you have installed ez-pine-gpg you will need to modify your <code class="code">~/.pinerc</code> file. You need to:
</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
/home/username/bin should be replaced with the installation path that you specified.
@@ -4144,20 +3955,19 @@ display-filters=_LEADING("-----BEGIN PGP")_ /home/max/bin/ez-pine-gpg-incoming
sending-filters=/home/max/bin/ez-pine-gpg-sign _INCLUDEALLHDRS_,
/home/username/bin/ez-pine-gpg-encrypt _RECIPIENTS_ gpg-identifier,
/home/username/bin/ez-pine-gpg-sign-and-encrypt _INCLUDEALLHDRS_ _RECIPIENTS_ gpg-identifier
-
-</pre></div><div class="section" title="3.9.5. Using GPG with Evolution" id="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.9.5. Using GPG with Evolution</h3></div></div></div><div class="section" title="3.9.5.1. Configuring GPG for use with Evolution" id="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution-Configuring"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">3.9.5.1. Configuring GPG for use with Evolution</h4></div></div></div><div class="para">
+</pre></div><div class="section" title="3.9.5. Using GPG with Evolution" id="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution">3.9.5. Using GPG with Evolution</h3></div></div></div><div class="section" title="3.9.5.1. Configuring GPG for use with Evolution" id="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution-Configuring"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution-Configuring">3.9.5.1. Configuring GPG for use with Evolution</h4></div></div></div><div class="para">
To configure GPG for use in <span class="application"><strong>Evolution</strong></span> select from the <span class="application"><strong>Evolution</strong></span> Main Menu, select Tools, Settings... In the left pane, select Mail Accounts. In the right pane, select the email account you use for Fedora Project correspondence. Then select the Edit button. The <span class="application"><strong>Evolution</strong></span> Account Editor dialog appears. Select the Security tab.
</div><div class="para">
In the PGP/GPG Key ID field, enter the GPG key ID matching this account's email address. If you are not sure what your key ID is, use this command: <code class="code">gpg --fingerprint EMAIL_ADDRESS</code>. The key ID is the same as the last eight characters (4 bytes) of the key fingerprint. It is a good idea to click the option Always encrypt to myself when sending encrypted mail. You may also want to select Always sign outgoing messages when using this account.
</div><div class="note"><h2>Notice</h2><div class="para">
If you do not mark public keys as trusted in your keyring, you will not be able to encrypt email to their owners unless you select the option Always trust keys in my keyring when encrypting. You will instead receive a dialog indicating that a trust check has failed.
- </div></div></div><div class="section" title="3.9.5.2. Verifying email with Evolution" id="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution-Verifying"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">3.9.5.2. Verifying email with Evolution</h4></div></div></div><div class="para">
+ </div></div></div><div class="section" title="3.9.5.2. Verifying email with Evolution" id="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution-Verifying"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution-Verifying">3.9.5.2. Verifying email with Evolution</h4></div></div></div><div class="para">
Evolution will automatically check any incoming GPG-signed messages for validity. If Evolution cannot GPG verify a message due to a missing public key (or tampering), it will end with a red banner. If the message is verified but you have not signed the key either locally or globally, the banner will be yellow. If the message is verified and you have signed the key, the banner will be green. When you click the seal icon, Evolution displays a dialog with more security information about the signature. To add a public key to your keyring, use the search function along with the key owner's email address: <code class="code">gpg --keyserver pgp.mit.edu --search email address</code>. To import the correct key, you may need to match the key ID with the information provided by Evolution.
- </div></div><div class="section" title="3.9.5.3. Signing and Encrypting email with Evolution" id="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution-Signing_and_Encrypting"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">3.9.5.3. Signing and Encrypting email with Evolution</h4></div></div></div><div class="para">
+ </div></div><div class="section" title="3.9.5.3. Signing and Encrypting email with Evolution" id="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution-Signing_and_Encrypting"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution-Signing_and_Encrypting">3.9.5.3. Signing and Encrypting email with Evolution</h4></div></div></div><div class="para">
Signing email allows the recipients to verify that the email actually came from you. The FDP (and the whole of the Fedora Project) encourage you to sign email to other participants, including on Fedora mailing lists. Encrypting email allows only your recipients to read your email. Please do not send encrypted email over the Fedora mailing lists, since almost no one will be able to read it.
</div><div class="para">
While composing your email, choose the Security menu, and then select PGP Sign to sign your message. To encrypt your message, select PGP Encrypt. You may sign an encrypted message as well, which is good practice. When you send the message, Evolution will ask you to enter your GPG key passphrase. (After three unsuccessful attempts Evolution generates an error.) If you select the option Remember this password for the remainder of this session, you will not need to use your passphrase again to sign or decrypt, unless you quit and restart Evolution.
- </div></div></div><div class="section" title="3.9.6. Using GPG with Thunderbird" id="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Thunderbird"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.9.6. Using GPG with Thunderbird</h3></div></div></div><div class="para">
+ </div></div></div><div class="section" title="3.9.6. Using GPG with Thunderbird" id="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Thunderbird"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Thunderbird">3.9.6. Using GPG with Thunderbird</h3></div></div></div><div class="para">
Fedora Core includes Mozilla Thunderbird in the thunderbird package, and the mozilla-mail package for the Mozilla Suite email application. Thunderbird is the recommended Mozilla email application. This appears on your desktop as Applications > Internet > Thunderbird Email.
</div><div class="para">
Mozilla products support extensions, plugins that add new features to the main application. The Enigmail extensions provide GPG support to email products from Mozilla. Versions of Enigmail exist for both Mozilla Thunderbird, and the Mozilla Suite (Seamonkey). Netscape software from AOL is based on the Mozilla products, and may also use this extension.
@@ -4169,9 +3979,9 @@ sending-filters=/home/max/bin/ez-pine-gpg-sign _INCLUDEALLHDRS_,
The homepage for Enigmail is: <a href="http://enigmail.mozdev.org/download.html">http://enigmail.mozdev.org/download.html</a>.
</div><div class="para">
This page provides screenshots of Enigmail and GPG in action: <a href="http://enigmail.mozdev.org/screenshots.html">http://enigmail.mozdev.org/screenshots.html</a>.
- </div><div class="section" title="3.9.6.1. Installing Enigmail" id="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Thunderbird-Installing_Enigmail"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">3.9.6.1. Installing Enigmail</h4></div></div></div><div class="para">
+ </div><div class="section" title="3.9.6.1. Installing Enigmail" id="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Thunderbird-Installing_Enigmail"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Thunderbird-Installing_Enigmail">3.9.6.1. Installing Enigmail</h4></div></div></div><div class="para">
Enigmail is now available in fedora repository. It can be installed by typing: <code class="code">yum install thunderbird-enigmail</code> at a command line. Alternatively, you can install <span class="package">thunderbird-enigmail</span> using by going to <code class="code">System -> Administration -> Add/Remove Software</code>.
- </div></div></div><div class="section" title="3.9.7. About Public Key Encryption" id="sect-Security_Guide-Encryption-Using_GPG-About_Public_Key_Encryption"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.9.7. About Public Key Encryption</h3></div></div></div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ </div></div></div><div class="section" title="3.9.7. About Public Key Encryption" id="sect-Security_Guide-Encryption-Using_GPG-About_Public_Key_Encryption"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Encryption-Using_GPG-About_Public_Key_Encryption">3.9.7. About Public Key Encryption</h3></div></div></div><div class="orderedlist"><ol><li class="listitem"><div class="para">
<a href="http://en.wikipedia.org/wiki/Public-key_cryptography">Wikipedia - Public Key Cryptography</a>
</div></li><li class="listitem"><div class="para">
<a href="http://computer.howstuffworks.com/encryption.htm">HowStuffWorks - Encryption</a>
@@ -4191,7 +4001,7 @@ sending-filters=/home/max/bin/ez-pine-gpg-sign _INCLUDEALLHDRS_,
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 class="listitem"><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" title="4.1. Tips, Guides, and Tools" id="sect-Security_Guide-General_Principles_of_Information_Security-Tips_Guides_and_Tools"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.1. Tips, Guides, and Tools</h2></div></div></div><div class="para">
+ </div></li></ul></div><div class="section" title="4.1. Tips, Guides, and Tools" id="sect-Security_Guide-General_Principles_of_Information_Security-Tips_Guides_and_Tools"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sect-Security_Guide-General_Principles_of_Information_Security-Tips_Guides_and_Tools">4.1. Tips, Guides, and Tools</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 class="listitem"><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>
@@ -4205,7 +4015,7 @@ sending-filters=/home/max/bin/ez-pine-gpg-sign _INCLUDEALLHDRS_,
Also, DISA has made available <a href="http://iase.disa.mil/stigs/SRR/unix.html">UNIX SPR scripts</a> that allow administrators to check specific settings on systems. These scripts provide XML-formatted reports listing any known vulnerable settings.
</div></div></div><div xml:lang="en-US" class="chapter" title="Chapter 5. Secure Installation" id="chap-Security_Guide-Secure_Installation" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 5. Secure Installation</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Security_Guide-Secure_Installation-Disk_Partitions">5.1. Disk Partitions</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Secure_Installation-Utilize_LUKS_Partition_Encryption">5.2. Utilize LUKS Partition Encryption</a></span></dt></dl></div><div class="para">
Security begins with the first time you put that CD or DVD into your disk drive to install Fedora. Configuring your system securely from the beginning makes it easier to implement additional security settings later.
- </div><div class="section" title="5.1. Disk Partitions" id="sect-Security_Guide-Secure_Installation-Disk_Partitions"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.1. Disk Partitions</h2></div></div></div><div class="para">
+ </div><div class="section" title="5.1. Disk Partitions" id="sect-Security_Guide-Secure_Installation-Disk_Partitions"><div class="titlepage"><div><div keep-together.within-column="always"><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.
@@ -4213,23 +4023,23 @@ sending-filters=/home/max/bin/ez-pine-gpg-sign _INCLUDEALLHDRS_,
/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 class="section" title="5.2. Utilize LUKS Partition Encryption" id="sect-Security_Guide-Secure_Installation-Utilize_LUKS_Partition_Encryption"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.2. Utilize LUKS Partition Encryption</h2></div></div></div><div class="para">
+ </div></div><div class="section" title="5.2. Utilize LUKS Partition Encryption" id="sect-Security_Guide-Secure_Installation-Utilize_LUKS_Partition_Encryption"><div class="titlepage"><div><div keep-together.within-column="always"><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></div><div xml:lang="en-US" class="chapter" title="Chapter 6. Software Maintenance" id="chap-Security_Guide-Software_Maintenance" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 6. Software Maintenance</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Security_Guide-Software_Maintenance-Install_Minimal_Software">6.1. Install Minimal Software</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates">6.2. Plan and Configure Security Updates</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates-Adjusting_Automatic_Updates">6.3. Adjusting Automatic Updates</a></span></dt><dt><span class="section"><a href="#sect-Security_Guide-Software_Maintenance-Install_Signed_Packages_from_Well_Known_Repositories">6.4. Install Signed Packages from Well Known Repositories</a></
span></dt></dl></div><div class="para">
Software maintenance is extremely important to maintaining a secure system. It is vital to patch software as soon as it becomes available in order to prevent attackers from using known holes to infiltrate your system.
- </div><div class="section" title="6.1. Install Minimal Software" id="sect-Security_Guide-Software_Maintenance-Install_Minimal_Software"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.1. Install Minimal Software</h2></div></div></div><div class="para">
+ </div><div class="section" title="6.1. Install Minimal Software" id="sect-Security_Guide-Software_Maintenance-Install_Minimal_Software"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sect-Security_Guide-Software_Maintenance-Install_Minimal_Software">6.1. Install Minimal Software</h2></div></div></div><div class="para">
It is best practice to install only the packages you will use because each piece of software on your computer could possibly contain a vulnerability. If you are installing from the DVD media take the opportunity to select exactly what packages you want to install during the installation. When you find you need another package, you can always add it to the system later.
- </div></div><div class="section" title="6.2. Plan and Configure Security Updates" id="sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.2. Plan and Configure Security Updates</h2></div></div></div><div class="para">
+ </div></div><div class="section" title="6.2. Plan and Configure Security Updates" id="sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates"><div class="titlepage"><div><div keep-together.within-column="always"><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><div class="section" title="6.3. Adjusting Automatic Updates" id="sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates-Adjusting_Automatic_Updates"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.3. Adjusting Automatic Updates</h2></div></div></div><div class="para">
+ </div></div><div class="section" title="6.3. Adjusting Automatic Updates" id="sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates-Adjusting_Automatic_Updates"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates-Adjusting_Automatic_Updates">6.3. Adjusting Automatic Updates</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 -> Software Updates</code>. In KDE it is located at: <code class="code">Applications -> Settings -> Software Updates</code>.
- </div></div><div class="section" title="6.4. Install Signed Packages from Well Known Repositories" id="sect-Security_Guide-Software_Maintenance-Install_Signed_Packages_from_Well_Known_Repositories"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.4. Install Signed Packages from Well Known Repositories</h2></div></div></div><div class="para">
+ </div></div><div class="section" title="6.4. Install Signed Packages from Well Known Repositories" id="sect-Security_Guide-Software_Maintenance-Install_Signed_Packages_from_Well_Known_Repositories"><div class="titlepage"><div><div keep-together.within-column="always"><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.
@@ -4276,44 +4086,44 @@ sending-filters=/home/max/bin/ez-pine-gpg-sign _INCLUDEALLHDRS_,
</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><div xml:lang="en-US" class="appendix" title="Appendix A. Encryption Standards" id="chap-Security_Guide-Encryption_Standards" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Encryption Standards</h1></div></div></div><div class="para">
- </div><div class="section" title="A.1. Synchronous Encryption"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id3170015">A.1. Synchronous Encryption</h2></div></div></div><div class="para">
- </div><div class="section" title="A.1.1. Advanced Encryption Standard - AES"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id4431743">A.1.1. Advanced Encryption Standard - AES</h3></div></div></div><div class="para">
- In cryptography, the Advanced Encryption Standard (AES) is an encryption standard adopted by the U.S. government. The standard comprises three block ciphers, AES-128, AES-192 and AES-256, adopted from a larger collection originally published as Rijndael. Each AES cipher has a 128-bit block size, with key sizes of 128, 192 and 256 bits, respectively. The AES ciphers have been analyzed extensively and are now used worldwide, as was the case with its predecessor, the Data Encryption Standard (DES).<sup>[<a id="id3278393" href="#ftn.id3278393" class="footnote">15</a>]</sup>
- </div><div class="section" title="A.1.1.1. AES Uses"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="id3322677">A.1.1.1. AES Uses</h4></div></div></div><div class="para">
- </div></div><div class="section" title="A.1.1.2. AES History"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="id3171471">A.1.1.2. AES History</h4></div></div></div><div class="para">
- AES was announced by National Institute of Standards and Technology (NIST) as U.S. FIPS PUB 197 (FIPS 197) on November 26, 2001 after a 5-year standardization process in which fifteen competing designs were presented and evaluated before Rijndael was selected as the most suitable (see Advanced Encryption Standard process for more details). It became effective as a standard May 26, 2002. It is available in many different encryption packages. AES is the first publicly accessible and open cipher approved by the NSA for top secret information (see Security of AES, below).<sup>[<a id="id3320599" href="#ftn.id3320599" class="footnote">16</a>]</sup>
+ </div><div class="section" title="A.1. Synchronous Encryption"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id2669437">A.1. Synchronous Encryption</h2></div></div></div><div class="para">
+ </div><div class="section" title="A.1.1. Advanced Encryption Standard - AES"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id2932167">A.1.1. Advanced Encryption Standard - AES</h3></div></div></div><div class="para">
+ In cryptography, the Advanced Encryption Standard (AES) is an encryption standard adopted by the U.S. government. The standard comprises three block ciphers, AES-128, AES-192 and AES-256, adopted from a larger collection originally published as Rijndael. Each AES cipher has a 128-bit block size, with key sizes of 128, 192 and 256 bits, respectively. The AES ciphers have been analyzed extensively and are now used worldwide, as was the case with its predecessor, the Data Encryption Standard (DES).<sup>[<a id="id3816293" href="#ftn.id3816293" class="footnote">15</a>]</sup>
+ </div><div class="section" title="A.1.1.1. AES Uses"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="id4514510">A.1.1.1. AES Uses</h4></div></div></div><div class="para">
+ </div></div><div class="section" title="A.1.1.2. AES History"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="id3003846">A.1.1.2. AES History</h4></div></div></div><div class="para">
+ AES was announced by National Institute of Standards and Technology (NIST) as U.S. FIPS PUB 197 (FIPS 197) on November 26, 2001 after a 5-year standardization process in which fifteen competing designs were presented and evaluated before Rijndael was selected as the most suitable (see Advanced Encryption Standard process for more details). It became effective as a standard May 26, 2002. It is available in many different encryption packages. AES is the first publicly accessible and open cipher approved by the NSA for top secret information (see Security of AES, below).<sup>[<a id="id2765309" href="#ftn.id2765309" class="footnote">16</a>]</sup>
</div><div class="para">
- The Rijndael cipher was developed by two Belgian cryptographers, Joan Daemen and Vincent Rijmen, and submitted by them to the AES selection process. Rijndael (pronounced [rÉ›indaËl]) is a portmanteau of the names of the two inventors.<sup>[<a id="id3501231" href="#ftn.id3501231" class="footnote">17</a>]</sup>
- </div></div></div><div class="section" title="A.1.2. Data Encryption Standard - DES"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id3399350">A.1.2. Data Encryption Standard - DES</h3></div></div></div><div class="para">
- The Data Encryption Standard (DES) is a block cipher (a form of shared secret encryption) that was selected by the National Bureau of Standards as an official Federal Information Processing Standard (FIPS) for the United States in 1976 and which has subsequently enjoyed widespread use internationally. It is based on a symmetric-key algorithm that uses a 56-bit key. The algorithm was initially controversial with classified design elements, a relatively short key length, and suspicions about a National Security Agency (NSA) backdoor. DES consequently came under intense academic scrutiny which motivated the modern understanding of block ciphers and their cryptanalysis.<sup>[<a id="id3374705" href="#ftn.id3374705" class="footnote">18</a>]</sup>
- </div><div class="section" title="A.1.2.1. DES Uses"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="id3383069">A.1.2.1. DES Uses</h4></div></div></div><div class="para">
- </div></div><div class="section" title="A.1.2.2. DES History"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="id3137354">A.1.2.2. DES History</h4></div></div></div><div class="para">
- DES is now considered to be insecure for many applications. This is chiefly due to the 56-bit key size being too small; in January, 1999, distributed.net and the Electronic Frontier Foundation collaborated to publicly break a DES key in 22 hours and 15 minutes (see chronology). There are also some analytical results which demonstrate theoretical weaknesses in the cipher, although they are unfeasible to mount in practice. The algorithm is believed to be practically secure in the form of Triple DES, although there are theoretical attacks. In recent years, the cipher has been superseded by the Advanced Encryption Standard (AES).<sup>[<a id="id3108307" href="#ftn.id3108307" class="footnote">19</a>]</sup>
+ The Rijndael cipher was developed by two Belgian cryptographers, Joan Daemen and Vincent Rijmen, and submitted by them to the AES selection process. Rijndael (pronounced [rÉ›indaËl]) is a portmanteau of the names of the two inventors.<sup>[<a id="id2776491" href="#ftn.id2776491" class="footnote">17</a>]</sup>
+ </div></div></div><div class="section" title="A.1.2. Data Encryption Standard - DES"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id2691199">A.1.2. Data Encryption Standard - DES</h3></div></div></div><div class="para">
+ The Data Encryption Standard (DES) is a block cipher (a form of shared secret encryption) that was selected by the National Bureau of Standards as an official Federal Information Processing Standard (FIPS) for the United States in 1976 and which has subsequently enjoyed widespread use internationally. It is based on a symmetric-key algorithm that uses a 56-bit key. The algorithm was initially controversial with classified design elements, a relatively short key length, and suspicions about a National Security Agency (NSA) backdoor. DES consequently came under intense academic scrutiny which motivated the modern understanding of block ciphers and their cryptanalysis.<sup>[<a id="id4477371" href="#ftn.id4477371" class="footnote">18</a>]</sup>
+ </div><div class="section" title="A.1.2.1. DES Uses"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="id2918924">A.1.2.1. DES Uses</h4></div></div></div><div class="para">
+ </div></div><div class="section" title="A.1.2.2. DES History"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="id2693303">A.1.2.2. DES History</h4></div></div></div><div class="para">
+ DES is now considered to be insecure for many applications. This is chiefly due to the 56-bit key size being too small; in January, 1999, distributed.net and the Electronic Frontier Foundation collaborated to publicly break a DES key in 22 hours and 15 minutes (see chronology). There are also some analytical results which demonstrate theoretical weaknesses in the cipher, although they are unfeasible to mount in practice. The algorithm is believed to be practically secure in the form of Triple DES, although there are theoretical attacks. In recent years, the cipher has been superseded by the Advanced Encryption Standard (AES).<sup>[<a id="id2646526" href="#ftn.id2646526" class="footnote">19</a>]</sup>
</div><div class="para">
- In some documentation, a distinction is made between DES as a standard and DES the algorithm which is referred to as the DEA (the Data Encryption Algorithm). When spoken, "DES" is either spelled out as an abbreviation (/ËŒdiËËŒiËˈɛs/), or pronounced as a one-syllable acronym (/ˈdÉ›z/).<sup>[<a id="id3406913" href="#ftn.id3406913" class="footnote">20</a>]</sup>
- </div></div></div></div><div class="section" title="A.2. Public-key Encryption"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id3264168">A.2. Public-key Encryption</h2></div></div></div><div class="para">
- Public-key cryptography is a cryptographic approach, employed by many cryptographic algorithms and cryptosystems, whose distinguishing characteristic is the use of asymmetric key algorithms instead of or in addition to symmetric key algorithms. Using the techniques of public key-private key cryptography, many methods of protecting communications or authenticating messages formerly unknown have become practical. They do not require a secure initial exchange of one or more secret keys as is required when using symmetric key algorithms. It can also be used to create digital signatures.<sup>[<a id="id3142852" href="#ftn.id3142852" class="footnote">21</a>]</sup>
+ In some documentation, a distinction is made between DES as a standard and DES the algorithm which is referred to as the DEA (the Data Encryption Algorithm). When spoken, "DES" is either spelled out as an abbreviation (/ËŒdiËËŒiËˈɛs/), or pronounced as a one-syllable acronym (/ˈdÉ›z/).<sup>[<a id="id2799939" href="#ftn.id2799939" class="footnote">20</a>]</sup>
+ </div></div></div></div><div class="section" title="A.2. Public-key Encryption"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id3921677">A.2. Public-key Encryption</h2></div></div></div><div class="para">
+ Public-key cryptography is a cryptographic approach, employed by many cryptographic algorithms and cryptosystems, whose distinguishing characteristic is the use of asymmetric key algorithms instead of or in addition to symmetric key algorithms. Using the techniques of public key-private key cryptography, many methods of protecting communications or authenticating messages formerly unknown have become practical. They do not require a secure initial exchange of one or more secret keys as is required when using symmetric key algorithms. It can also be used to create digital signatures.<sup>[<a id="id3921686" href="#ftn.id3921686" class="footnote">21</a>]</sup>
</div><div class="para">
- Public key cryptography is a fundamental and widely used technology around the world, and is the approach which underlies such Internet standards as Transport Layer Security (TLS) (successor to SSL), PGP and GPG.<sup>[<a id="id3471522" href="#ftn.id3471522" class="footnote">22</a>]</sup>
+ Public key cryptography is a fundamental and widely used technology around the world, and is the approach which underlies such Internet standards as Transport Layer Security (TLS) (successor to SSL), PGP and GPG.<sup>[<a id="id3254619" href="#ftn.id3254619" class="footnote">22</a>]</sup>
</div><div class="para">
- The distinguishing technique used in public key cryptography is the use of asymmetric key algorithms, where the key used to encrypt a message is not the same as the key used to decrypt it. Each user has a pair of cryptographic keys — a public key and a private key. The private key is kept secret, whilst the public key may be widely distributed. Messages are encrypted with the recipient's public key and can only be decrypted with the corresponding private key. The keys are related mathematically, but the private key cannot be feasibly (ie, in actual or projected practice) derived from the public key. It was the discovery of such algorithms which revolutionized the practice of cryptography beginning in the middle 1970s.<sup>[<a id="id3428053" href="#ftn.id3428053" class="footnote">23</a>]</sup>
+ The distinguishing technique used in public key cryptography is the use of asymmetric key algorithms, where the key used to encrypt a message is not the same as the key used to decrypt it. Each user has a pair of cryptographic keys — a public key and a private key. The private key is kept secret, whilst the public key may be widely distributed. Messages are encrypted with the recipient's public key and can only be decrypted with the corresponding private key. The keys are related mathematically, but the private key cannot be feasibly (ie, in actual or projected practice) derived from the public key. It was the discovery of such algorithms which revolutionized the practice of cryptography beginning in the middle 1970s.<sup>[<a id="id2971746" href="#ftn.id2971746" class="footnote">23</a>]</sup>
</div><div class="para">
- In contrast, Symmetric-key algorithms, variations of which have been used for some thousands of years, use a single secret key shared by sender and receiver (which must also be kept private, thus accounting for the ambiguity of the common terminology) for both encryption and decryption. To use a symmetric encryption scheme, the sender and receiver must securely share a key in advance.<sup>[<a id="id3140920" href="#ftn.id3140920" class="footnote">24</a>]</sup>
+ In contrast, Symmetric-key algorithms, variations of which have been used for some thousands of years, use a single secret key shared by sender and receiver (which must also be kept private, thus accounting for the ambiguity of the common terminology) for both encryption and decryption. To use a symmetric encryption scheme, the sender and receiver must securely share a key in advance.<sup>[<a id="id2836332" href="#ftn.id2836332" class="footnote">24</a>]</sup>
</div><div class="para">
- Because symmetric key algorithms are nearly always much less computationally intensive, it is common to exchange a key using a key-exchange algorithm and transmit data using that key and a symmetric key algorithm. PGP, and the SSL/TLS family of schemes do this, for instance, and are called hybrid cryptosystems in consequence.<sup>[<a id="id3266464" href="#ftn.id3266464" class="footnote">25</a>]</sup>
- </div><div class="section" title="A.2.1. Diffie-Hellman"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id3488782">A.2.1. Diffie-Hellman</h3></div></div></div><div class="para">
- Diffie–Hellman key exchange (D–H) is a cryptographic protocol that allows two parties that have no prior knowledge of each other to jointly establish a shared secret key over an insecure communications channel. This key can then be used to encrypt subsequent communications using a symmetric key cipher.<sup>[<a id="id3123933" href="#ftn.id3123933" class="footnote">26</a>]</sup>
- </div><div class="section" title="A.2.1.1. Diffie-Hellman History"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="id3123950">A.2.1.1. Diffie-Hellman History</h4></div></div></div><div class="para">
- The scheme was first published by Whitfield Diffie and Martin Hellman in 1976, although it later emerged that it had been separately invented a few years earlier within GCHQ, the British signals intelligence agency, by Malcolm J. Williamson but was kept classified. In 2002, Hellman suggested the algorithm be called Diffie–Hellman–Merkle key exchange in recognition of Ralph Merkle's contribution to the invention of public-key cryptography (Hellman, 2002).<sup>[<a id="id3337749" href="#ftn.id3337749" class="footnote">27</a>]</sup>
+ Because symmetric key algorithms are nearly always much less computationally intensive, it is common to exchange a key using a key-exchange algorithm and transmit data using that key and a symmetric key algorithm. PGP, and the SSL/TLS family of schemes do this, for instance, and are called hybrid cryptosystems in consequence.<sup>[<a id="id2961938" href="#ftn.id2961938" class="footnote">25</a>]</sup>
+ </div><div class="section" title="A.2.1. Diffie-Hellman"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id2654989">A.2.1. Diffie-Hellman</h3></div></div></div><div class="para">
+ Diffie–Hellman key exchange (D–H) is a cryptographic protocol that allows two parties that have no prior knowledge of each other to jointly establish a shared secret key over an insecure communications channel. This key can then be used to encrypt subsequent communications using a symmetric key cipher.<sup>[<a id="id2974776" href="#ftn.id2974776" class="footnote">26</a>]</sup>
+ </div><div class="section" title="A.2.1.1. Diffie-Hellman History"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="id2783490">A.2.1.1. Diffie-Hellman History</h4></div></div></div><div class="para">
+ The scheme was first published by Whitfield Diffie and Martin Hellman in 1976, although it later emerged that it had been separately invented a few years earlier within GCHQ, the British signals intelligence agency, by Malcolm J. Williamson but was kept classified. In 2002, Hellman suggested the algorithm be called Diffie–Hellman–Merkle key exchange in recognition of Ralph Merkle's contribution to the invention of public-key cryptography (Hellman, 2002).<sup>[<a id="id2783506" href="#ftn.id2783506" class="footnote">27</a>]</sup>
</div><div class="para">
- Although Diffie–Hellman key agreement itself is an anonymous (non-authenticated) key-agreement protocol, it provides the basis for a variety of authenticated protocols, and is used to provide perfect forward secrecy in Transport Layer Security's ephemeral modes (referred to as EDH or DHE depending on the cipher suite).<sup>[<a id="id3489855" href="#ftn.id3489855" class="footnote">28</a>]</sup>
+ Although Diffie–Hellman key agreement itself is an anonymous (non-authenticated) key-agreement protocol, it provides the basis for a variety of authenticated protocols, and is used to provide perfect forward secrecy in Transport Layer Security's ephemeral modes (referred to as EDH or DHE depending on the cipher suite).<sup>[<a id="id2653644" href="#ftn.id2653644" class="footnote">28</a>]</sup>
</div><div class="para">
- U.S. Patent 4,200,770, now expired, describes the algorithm and credits Hellman, Diffie, and Merkle as inventors.<sup>[<a id="id3295112" href="#ftn.id3295112" class="footnote">29</a>]</sup>
- </div></div></div><div class="section" title="A.2.2. RSA"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id3374442">A.2.2. RSA</h3></div></div></div><div class="para">
- In cryptography, RSA (which stands for Rivest, Shamir and Adleman who first publicly described it; see below) is an algorithm for public-key cryptography. It is the first algorithm known to be suitable for signing as well as encryption, and was one of the first great advances in public key cryptography. RSA is widely used in electronic commerce protocols, and is believed to be secure given sufficiently long keys and the use of up-to-date implementations.<sup>[<a id="id3236267" href="#ftn.id3236267" class="footnote">30</a>]</sup>
- </div></div><div class="section" title="A.2.3. DSA"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id3236285">A.2.3. DSA</h3></div></div></div><div class="para">
- The Digital Signature Algorithm (DSA) is a United States Federal Government standard or FIPS for digital signatures. It was proposed by the National Institute of Standards and Technology (NIST) in August 1991 for use in their Digital Signature Standard (DSS), specified in FIPS 186, adopted in 1993. A minor revision was issued in 1996 as FIPS 186-1. The standard was expanded further in 2000 as FIPS 186-2 and again in 2009 as FIPS 186-3.<sup>[<a id="id4228822" href="#ftn.id4228822" class="footnote">31</a>]</sup>
- </div></div><div class="section" title="A.2.4. SSL/TLS"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id3324079">A.2.4. SSL/TLS</h3></div></div></div><div class="para">
+ U.S. Patent 4,200,770, now expired, describes the algorithm and credits Hellman, Diffie, and Merkle as inventors.<sup>[<a id="id2949689" href="#ftn.id2949689" class="footnote">29</a>]</sup>
+ </div></div></div><div class="section" title="A.2.2. RSA"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id2623554">A.2.2. RSA</h3></div></div></div><div class="para">
+ In cryptography, RSA (which stands for Rivest, Shamir and Adleman who first publicly described it; see below) is an algorithm for public-key cryptography. It is the first algorithm known to be suitable for signing as well as encryption, and was one of the first great advances in public key cryptography. RSA is widely used in electronic commerce protocols, and is believed to be secure given sufficiently long keys and the use of up-to-date implementations.<sup>[<a id="id2696090" href="#ftn.id2696090" class="footnote">30</a>]</sup>
+ </div></div><div class="section" title="A.2.3. DSA"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id2623563">A.2.3. DSA</h3></div></div></div><div class="para">
+ The Digital Signature Algorithm (DSA) is a United States Federal Government standard or FIPS for digital signatures. It was proposed by the National Institute of Standards and Technology (NIST) in August 1991 for use in their Digital Signature Standard (DSS), specified in FIPS 186, adopted in 1993. A minor revision was issued in 1996 as FIPS 186-1. The standard was expanded further in 2000 as FIPS 186-2 and again in 2009 as FIPS 186-3.<sup>[<a id="id2896234" href="#ftn.id2896234" class="footnote">31</a>]</sup>
+ </div></div><div class="section" title="A.2.4. SSL/TLS"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id2800052">A.2.4. SSL/TLS</h3></div></div></div><div class="para">
Transport Layer Security (TLS) and its predecessor, Secure Socket Layer (SSL), are cryptographic protocols that provide security for communications over networks such as the Internet. TLS and SSL encrypt the segments of network connections at the Transport Layer end-to-end. Several versions of the protocols are in widespread use in applications like web browsing, electronic mail, Internet faxing, instant messaging and voice-over-IP (VoIP). TLS is an IETF standards track protocol, last updated in RFC 5246, that was based on the earlier SSL specifications developed by Netscape Corporation.
</div><div class="para">
The TLS protocol allows client/server applications to communicate across a network in a way designed to prevent eavesdropping and tampering. TLS provides endpoint authentication and communications confidentiality over the Internet using cryptography. TLS provides RSA security with 1024 and 2048 bit strengths.
@@ -4324,50 +4134,50 @@ sending-filters=/home/max/bin/ez-pine-gpg-sign _INCLUDEALLHDRS_,
</div><div class="para">
Typically, the key information and certificates necessary for TLS are handled in the form of X.509 certificates, which define required fields and data formats.
</div><div class="para">
- SSL operates in modular fashion. It is extensible by design, with support for forward and backward compatibility and negotiation between peers.<sup>[<a id="id3380143" href="#ftn.id3380143" class="footnote">32</a>]</sup>
- </div></div><div class="section" title="A.2.5. Cramer-Shoup Cryptosystem"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id3489826">A.2.5. Cramer-Shoup Cryptosystem</h3></div></div></div><div class="para">
- The Cramer–Shoup system is an asymmetric key encryption algorithm, and was the first efficient scheme proven to be secure against adaptive chosen ciphertext attack using standard cryptographic assumptions. Its security is based on the computational intractability (widely assumed, but not proved) of the decisional Diffie–Hellman assumption. Developed by Ronald Cramer and Victor Shoup in 1998, it is an extension of the Elgamal cryptosystem. In contrast to Elgamal, which is extremely malleable, Cramer–Shoup adds additional elements to ensure non-malleability even against a resourceful attacker. This non-malleability is achieved through the use of a collision-resistant hash function and additional computations, resulting in a ciphertext which is twice as large as in Elgamal.<sup>[<a id="id3489835" href="#ftn.id3489835" class="footnote">33</a>]</sup>
- </div></div><div class="section" title="A.2.6. ElGamal Encryption"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id3511325">A.2.6. ElGamal Encryption</h3></div></div></div><div class="para">
- In cryptography, the ElGamal encryption system is an asymmetric key encryption algorithm for public-key cryptography which is based on the Diffie-Hellman key agreement. It was described by Taher Elgamal in 1985.[1] ElGamal encryption is used in the free GNU Privacy Guard software, recent versions of PGP, and other cryptosystems. The Digital Signature Algorithm is a variant of the ElGamal signature scheme, which should not be confused with ElGamal encryption.<sup>[<a id="id3511342" href="#ftn.id3511342" class="footnote">34</a>]</sup>
- </div></div></div><div class="footnotes"><br /><hr width="100" align="left" /><div class="footnote"><p><sup>[<a id="ftn.id3278393" href="#id3278393" class="para">15</a>] </sup>
+ SSL operates in modular fashion. It is extensible by design, with support for forward and backward compatibility and negotiation between peers.<sup>[<a id="id2766576" href="#ftn.id2766576" class="footnote">32</a>]</sup>
+ </div></div><div class="section" title="A.2.5. Cramer-Shoup Cryptosystem"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id3026488">A.2.5. Cramer-Shoup Cryptosystem</h3></div></div></div><div class="para">
+ The Cramer–Shoup system is an asymmetric key encryption algorithm, and was the first efficient scheme proven to be secure against adaptive chosen ciphertext attack using standard cryptographic assumptions. Its security is based on the computational intractability (widely assumed, but not proved) of the decisional Diffie–Hellman assumption. Developed by Ronald Cramer and Victor Shoup in 1998, it is an extension of the Elgamal cryptosystem. In contrast to Elgamal, which is extremely malleable, Cramer–Shoup adds additional elements to ensure non-malleability even against a resourceful attacker. This non-malleability is achieved through the use of a collision-resistant hash function and additional computations, resulting in a ciphertext which is twice as large as in Elgamal.<sup>[<a id="id3026496" href="#ftn.id3026496" class="footnote">33</a>]</sup>
+ </div></div><div class="section" title="A.2.6. ElGamal Encryption"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id2658576">A.2.6. ElGamal Encryption</h3></div></div></div><div class="para">
+ In cryptography, the ElGamal encryption system is an asymmetric key encryption algorithm for public-key cryptography which is based on the Diffie-Hellman key agreement. It was described by Taher Elgamal in 1985.[1] ElGamal encryption is used in the free GNU Privacy Guard software, recent versions of PGP, and other cryptosystems. The Digital Signature Algorithm is a variant of the ElGamal signature scheme, which should not be confused with ElGamal encryption.<sup>[<a id="id2658592" href="#ftn.id2658592" class="footnote">34</a>]</sup>
+ </div></div></div><div class="footnotes"><br /><hr width="100" align="left" /><div class="footnote"><p><sup>[<a id="ftn.id3816293" href="#id3816293" class="para">15</a>] </sup>
"Advanced Encryption Standard." <span class="emphasis"><em>Wikipedia.</em></span> 14 November 2009 <a href="http://en.wikipedia.org/wiki/Advanced_Encryption_Standard">http://en.wikipedia.org/wiki/Advanced_Encryption_Standard</a>
- </p></div><div class="footnote"><p><sup>[<a id="ftn.id3320599" href="#id3320599" class="para">16</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id2765309" href="#id2765309" class="para">16</a>] </sup>
"Advanced Encryption Standard." <span class="emphasis"><em>Wikipedia.</em></span> 14 November 2009 <a href="http://en.wikipedia.org/wiki/Advanced_Encryption_Standard">http://en.wikipedia.org/wiki/Advanced_Encryption_Standard</a>
- </p></div><div class="footnote"><p><sup>[<a id="ftn.id3501231" href="#id3501231" class="para">17</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id2776491" href="#id2776491" class="para">17</a>] </sup>
"Advanced Encryption Standard." <span class="emphasis"><em>Wikipedia.</em></span> 14 November 2009 <a href="http://en.wikipedia.org/wiki/Advanced_Encryption_Standard">http://en.wikipedia.org/wiki/Advanced_Encryption_Standard</a>
- </p></div><div class="footnote"><p><sup>[<a id="ftn.id3374705" href="#id3374705" class="para">18</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id4477371" href="#id4477371" class="para">18</a>] </sup>
"Data Encryption Standard." <span class="emphasis"><em>Wikipedia.</em></span> 14 November 2009 <a href="http://en.wikipedia.org/wiki/Data_Encryption_Standard">http://en.wikipedia.org/wiki/Data_Encryption_Standard</a>
- </p></div><div class="footnote"><p><sup>[<a id="ftn.id3108307" href="#id3108307" class="para">19</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id2646526" href="#id2646526" class="para">19</a>] </sup>
"Data Encryption Standard." <span class="emphasis"><em>Wikipedia.</em></span> 14 November 2009 <a href="http://en.wikipedia.org/wiki/Data_Encryption_Standard">http://en.wikipedia.org/wiki/Data_Encryption_Standard</a>
- </p></div><div class="footnote"><p><sup>[<a id="ftn.id3406913" href="#id3406913" class="para">20</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id2799939" href="#id2799939" class="para">20</a>] </sup>
"Data Encryption Standard." <span class="emphasis"><em>Wikipedia.</em></span> 14 November 2009 <a href="http://en.wikipedia.org/wiki/Data_Encryption_Standard">http://en.wikipedia.org/wiki/Data_Encryption_Standard</a>
- </p></div><div class="footnote"><p><sup>[<a id="ftn.id3142852" href="#id3142852" class="para">21</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id3921686" href="#id3921686" class="para">21</a>] </sup>
"Public-key Encryption." <span class="emphasis"><em>Wikipedia.</em></span> 14 November 2009 <a href="http://en.wikipedia.org/wiki/Public-key_cryptography">http://en.wikipedia.org/wiki/Public-key_cryptography</a>
- </p></div><div class="footnote"><p><sup>[<a id="ftn.id3471522" href="#id3471522" class="para">22</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id3254619" href="#id3254619" class="para">22</a>] </sup>
"Public-key Encryption." <span class="emphasis"><em>Wikipedia.</em></span> 14 November 2009 <a href="http://en.wikipedia.org/wiki/Public-key_cryptography">http://en.wikipedia.org/wiki/Public-key_cryptography</a>
- </p></div><div class="footnote"><p><sup>[<a id="ftn.id3428053" href="#id3428053" class="para">23</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id2971746" href="#id2971746" class="para">23</a>] </sup>
"Public-key Encryption." <span class="emphasis"><em>Wikipedia.</em></span> 14 November 2009 <a href="http://en.wikipedia.org/wiki/Public-key_cryptography">http://en.wikipedia.org/wiki/Public-key_cryptography</a>
- </p></div><div class="footnote"><p><sup>[<a id="ftn.id3140920" href="#id3140920" class="para">24</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id2836332" href="#id2836332" class="para">24</a>] </sup>
"Public-key Encryption." <span class="emphasis"><em>Wikipedia.</em></span> 14 November 2009 <a href="http://en.wikipedia.org/wiki/Public-key_cryptography">http://en.wikipedia.org/wiki/Public-key_cryptography</a>
- </p></div><div class="footnote"><p><sup>[<a id="ftn.id3266464" href="#id3266464" class="para">25</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id2961938" href="#id2961938" class="para">25</a>] </sup>
"Public-key Encryption." <span class="emphasis"><em>Wikipedia.</em></span> 14 November 2009 <a href="http://en.wikipedia.org/wiki/Public-key_cryptography">http://en.wikipedia.org/wiki/Public-key_cryptography</a>
- </p></div><div class="footnote"><p><sup>[<a id="ftn.id3123933" href="#id3123933" class="para">26</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id2974776" href="#id2974776" class="para">26</a>] </sup>
"Diffie-Hellman." <span class="emphasis"><em>Wikipedia.</em></span> 14 November 2009 <a href="http://en.wikipedia.org/wiki/Diffie-Hellman">http://en.wikipedia.org/wiki/Diffie-Hellman</a>
- </p></div><div class="footnote"><p><sup>[<a id="ftn.id3337749" href="#id3337749" class="para">27</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id2783506" href="#id2783506" class="para">27</a>] </sup>
"Diffie-Hellman." <span class="emphasis"><em>Wikipedia.</em></span> 14 November 2009 <a href="http://en.wikipedia.org/wiki/Diffie-Hellman">http://en.wikipedia.org/wiki/Diffie-Hellman</a>
- </p></div><div class="footnote"><p><sup>[<a id="ftn.id3489855" href="#id3489855" class="para">28</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id2653644" href="#id2653644" class="para">28</a>] </sup>
"Diffie-Hellman." <span class="emphasis"><em>Wikipedia.</em></span> 14 November 2009 <a href="http://en.wikipedia.org/wiki/Diffie-Hellman">http://en.wikipedia.org/wiki/Diffie-Hellman</a>
- </p></div><div class="footnote"><p><sup>[<a id="ftn.id3295112" href="#id3295112" class="para">29</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id2949689" href="#id2949689" class="para">29</a>] </sup>
"Diffie-Hellman." <span class="emphasis"><em>Wikipedia.</em></span> 14 November 2009 <a href="http://en.wikipedia.org/wiki/Diffie-Hellman">http://en.wikipedia.org/wiki/Diffie-Hellman</a>
- </p></div><div class="footnote"><p><sup>[<a id="ftn.id3236267" href="#id3236267" class="para">30</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id2696090" href="#id2696090" class="para">30</a>] </sup>
"RSA" <span class="emphasis"><em>Wikipedia</em></span> 14 April 2010 <a href="http://en.wikipedia.org/wiki/RSA">http://en.wikipedia.org/wiki/RSA</a>
- </p></div><div class="footnote"><p><sup>[<a id="ftn.id4228822" href="#id4228822" class="para">31</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id2896234" href="#id2896234" class="para">31</a>] </sup>
"Digital Signature Algorithm" <span class="emphasis"><em>Wikipedia</em></span> 14 April 2010 <a href="http://en.wikipedia.org/wiki/Digital_Signature_Algorithm">http://en.wikipedia.org/wiki/Digital_Signature_Algorithm</a>
- </p></div><div class="footnote"><p><sup>[<a id="ftn.id3380143" href="#id3380143" class="para">32</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id2766576" href="#id2766576" class="para">32</a>] </sup>
"Transport Layer Security" <span class="emphasis"><em>Wikipedia</em></span> 14 April 2010 <a href="http://en.wikipedia.org/wiki/Transport_Layer_Security">http://en.wikipedia.org/wiki/Transport_Layer_Security</a>
- </p></div><div class="footnote"><p><sup>[<a id="ftn.id3489835" href="#id3489835" class="para">33</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id3026496" href="#id3026496" class="para">33</a>] </sup>
"Cramer–Shoup cryptosystem" <span class="emphasis"><em>Wikipedia</em></span> 14 April 2010 <a href="http://en.wikipedia.org/wiki/Cramer-Shoup_cryptosystem">http://en.wikipedia.org/wiki/Cramer-Shoup_cryptosystem</a>
- </p></div><div class="footnote"><p><sup>[<a id="ftn.id3511342" href="#id3511342" class="para">34</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id2658592" href="#id2658592" class="para">34</a>] </sup>
"ElGamal encryption" <span class="emphasis"><em>Wikipedia</em></span> 14 April 2010 <a href="http://en.wikipedia.org/wiki/ElGamal_encryption">http://en.wikipedia.org/wiki/ElGamal_encryption</a>
</p></div></div></div><div xml:lang="en-US" class="appendix" title="Appendix B. Revision History" id="appe-Publican-Revision_History" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Revision History</h1></div></div></div><div class="para">
<div class="revhistory"><table border="0" width="100%" summary="Revision history"><tr><th align="left" valign="top" colspan="3"><b>Revision History</b></th></tr><tr><td align="left">Revision 13.0-8</td><td align="left">Wed Jun 9 2010</td><td align="left"><span class="author"><span class="firstname">Eric</span> <span class="surname">Christensen</span></span></td></tr><tr><td align="left" colspan="3">
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/Common_Content/css/common.css b/public_html/en-US/Fedora/13/html/Security_Guide/Common_Content/css/common.css
index e1f4d9f..a196f22 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/Common_Content/css/common.css
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/Common_Content/css/common.css
@@ -50,7 +50,8 @@ body.desktop .book > .toc {
line-height:1.35em;
}
-.toc .chapter, .toc .appendix, .toc .glossary {
+.toc .glossary,
+.toc .chapter, .toc .appendix {
margin-top:1em;
}
@@ -59,7 +60,8 @@ body.desktop .book > .toc {
display:block;
}
-span.appendix, span.glossary {
+span.glossary,
+span.appendix {
display:block;
margin-top:0.5em;
}
@@ -346,7 +348,6 @@ a.version:focus, a.version:hover {
clear:both;
}
-
/*revision history*/
.revhistory {
display:block;
@@ -362,34 +363,24 @@ a.version:focus, a.version:hover {
}
.revhistory td {
- text-align:right;
+ text-align :left;
padding:0em;
border: none;
border-top: 1px solid #fff;
+ font-weight: bold;
}
-
-.revhistory tr td:first-child {
- text-align:left;
+.revhistory .simplelist td {
+ font-weight: normal;
}
-.revhistory tr td p, .revhistory tr td div.para {
- text-align:left;
- font-weight:bold;
- display:block;
- margin:0em;
- padding:0em;
- padding-bottom:0.7em;
- border-bottom:1px solid #eee;
+.revhistory .simplelist {
+ margin-bottom: 1.5em;
+ margin-left: 1em;
}
.revhistory table th {
- background-color:transparent;
- color:#336699;
- font-size:2em;
- padding: 1em 0em;
- border: none;
- border-bottom:1px solid #eee;
+ display: none;
}
@@ -901,6 +892,10 @@ th, td {
border: 1px solid #000;
}
+.simplelist th, .simplelist td {
+ border: none;
+}
+
table table td {
border-bottom:1px dotted #aaa;
background-color:white;
@@ -964,6 +959,10 @@ span.chapter {
margin-top:0.5em;
}
+table.simplelist td, .calloutlist table td {
+ border-style: none;
+}
+
/*Breadcrumbs*/
#breadcrumbs ul li.first:before {
content:" ";
@@ -1007,7 +1006,8 @@ span.chapter {
margin-bottom:1em;
}
-.glossary dt, .index dt {
+.glossary dt,
+.index dt {
color:#444;
padding-top:.5em;
}
@@ -1375,10 +1375,6 @@ pre {
border-radius: 15px;
}
-.term{
- color:#336699;
-}
-
.package, .citetitle {
font-style: italic;
}
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/Security_Guide-Encryption-Data_in_Motion-Secure_Shell.html b/public_html/en-US/Fedora/13/html/Security_Guide/Security_Guide-Encryption-Data_in_Motion-Secure_Shell.html
index 788f94f..e168ed3 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/Security_Guide-Encryption-Data_in_Motion-Secure_Shell.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/Security_Guide-Encryption-Data_in_Motion-Secure_Shell.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.6. Secure Shell</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="chap-Security_Guide-Encryption.html" title="Chapter 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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it
upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="Security_Guide-Encryption-Data_in_Motion-Virtual_Private_Networks.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-LUKS_Disk_Encryption.html"><strong>Next</strong></a></li></ul><div class="section" title="3.6. Secure Shell" id="Security_Guide-Encryption-Data_in_Motion-Secure_Shell"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">3.6. Secure Shell</h2></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.6. Secure Shell</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="chap-Security_Guide-Encryption.html" title="Chapter 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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it
upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="Security_Guide-Encryption-Data_in_Motion-Virtual_Private_Networks.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-LUKS_Disk_Encryption.html"><strong>Next</strong></a></li></ul><div class="section" title="3.6. Secure Shell" id="Security_Guide-Encryption-Data_in_Motion-Secure_Shell"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="Security_Guide-Encryption-Data_in_Motion-Secure_Shell">3.6. Secure Shell</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.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/Security_Guide-Encryption-Data_in_Motion-Virtual_Private_Networks.html b/public_html/en-US/Fedora/13/html/Security_Guide/Security_Guide-Encryption-Data_in_Motion-Virtual_Private_Networks.html
index 73debf2..42bacdf 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/Security_Guide-Encryption-Data_in_Motion-Virtual_Private_Networks.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/Security_Guide-Encryption-Data_in_Motion-Virtual_Private_Networks.html
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="chap-Security_Guide-Encryption.html" title="Chapter 3. Encryption" /><link rel="prev" href="Security_Guide-Encryption-Data_in_Motion.html" title="3.4. Data in Motion" /><link rel="next" href="Security_Guide-Encryption-Data_in_Motion-Secure_Shell.html" title="3.6. Secure Shell" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your brow
ser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="Security_Guide-Encryption-Data_in_Motion.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="Security_Guide-Encryption-Data_in_Motion-Secure_Shell.html"><strong>Next</strong></a></li></ul><div class="section" title="3.5. Virtual Private Networks" id="Security_Guide-Encryption-Data_in_Motion-Virtual_Private_Networks"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">3.5. Virtual Private Networks</h2></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.5. Virtual Private Networks</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="chap-Security_Guide-Encryption.html" title="Chapter 3. Encryption" /><link rel="prev" href="Security_Guide-Encryption-Data_in_Motion.html" title="3.4. Data in Motion" /><link rel="next" href="Security_Guide-Encryption-Data_in_Motion-Secure_Shell.html" title="3.6. Secure Shell" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your brows
er or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="Security_Guide-Encryption-Data_in_Motion.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="Security_Guide-Encryption-Data_in_Motion-Secure_Shell.html"><strong>Next</strong></a></li></ul><div class="section" title="3.5. Virtual Private Networks" id="Security_Guide-Encryption-Data_in_Motion-Virtual_Private_Networks"><div class="titlepage"><div><div keep-together.within-column="always"><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">
Virtual Private Networks (VPN) provide encrypted tunnels between computers or networks of computers across all ports. With a VPN in place, all network traffic from the client is forwarded to the server through the encrypted tunnel. This means that the client is logically on the same network as the server it is connected to via the VPN. VPNs are very common and are simple to use and setup.
</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="Security_Guide-Encryption-Data_in_Motion.html"><strong>Prev</strong>3.4. Data in Motion</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="Security_Guide-Encryption-Data_in_Motion-Secure_Shell.html"><strong>Next</strong>3.6. Secure Shell</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/Security_Guide-Encryption-Data_in_Motion.html b/public_html/en-US/Fedora/13/html/Security_Guide/Security_Guide-Encryption-Data_in_Motion.html
index 75ef4c8..05bc94d 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/Security_Guide-Encryption-Data_in_Motion.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/Security_Guide-Encryption-Data_in_Motion.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.4. Data in Motion</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="chap-Security_Guide-Encryption.html" title="Chapter 3. Encryption" /><link rel="prev" href="Security_Guide-Encryption-Protecting_Data_at_Rest-File_Based_Encryption.html" title="3.3. File Based Encryption" /><link rel="next" href="Security_Guide-Encryption-Data_in_Motion-Virtual_Private_Networks.html" title="3.5. Virtual Private Networks" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.h
tml">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="Security_Guide-Encryption-Protecting_Data_at_Rest-File_Based_Encryption.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="Security_Guide-Encryption-Data_in_Motion-Virtual_Private_Networks.html"><strong>Next</strong></a></li></ul><div class="section" title="3.4. Data in Motion" id="Security_Guide-Encryption-Data_in_Motion"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">3.4. Data in Motion</h2></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.4. Data in Motion</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="chap-Security_Guide-Encryption.html" title="Chapter 3. Encryption" /><link rel="prev" href="Security_Guide-Encryption-Protecting_Data_at_Rest-File_Based_Encryption.html" title="3.3. File Based Encryption" /><link rel="next" href="Security_Guide-Encryption-Data_in_Motion-Virtual_Private_Networks.html" title="3.5. Virtual Private Networks" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.ht
ml">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="Security_Guide-Encryption-Protecting_Data_at_Rest-File_Based_Encryption.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="Security_Guide-Encryption-Data_in_Motion-Virtual_Private_Networks.html"><strong>Next</strong></a></li></ul><div class="section" title="3.4. Data in Motion" id="Security_Guide-Encryption-Data_in_Motion"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="Security_Guide-Encryption-Data_in_Motion">3.4. Data in Motion</h2></div></div></div><div class="para">
Data in motion is data that is being transmitted over a network. The biggest threats to data in motion are interception and alteration. Your user name and password should never be transmitted over a network without protection as it could be intercepted and used by someone else to impersonate you or gain access to sensitive information. Other private information such as bank account information should also be protected when transmitted across a network. If the network session was encrypted then you would not have to worry as much about the data being compromised while it is being transmitted.
</div><div class="para">
Data in motion is particularly vulnerable to attackers because the attacker does not have to be near the computer in which the data is being stored rather they only have to be somewhere along the path. Encryption tunnels can protect data along the path of communications.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/Security_Guide-Encryption-Protecting_Data_at_Rest-File_Based_Encryption.html b/public_html/en-US/Fedora/13/html/Security_Guide/Security_Guide-Encryption-Protecting_Data_at_Rest-File_Based_Encryption.html
index 160fc9e..e82f621 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/Security_Guide-Encryption-Protecting_Data_at_Rest-File_Based_Encryption.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/Security_Guide-Encryption-Protecting_Data_at_Rest-File_Based_Encryption.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.3. File Based Encryption</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="chap-Security_Guide-Encryption.html" title="Chapter 3. Encryption" /><link rel="prev" href="sect-Security_Guide-Encryption-Protecting_Data_at_Rest-Full_Disk_Encryption.html" title="3.2. Full Disk Encryption" /><link rel="next" href="Security_Guide-Encryption-Data_in_Motion.html" title="3.4. Data in Motion" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, t
o view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Encryption-Protecting_Data_at_Rest-Full_Disk_Encryption.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="Security_Guide-Encryption-Data_in_Motion.html"><strong>Next</strong></a></li></ul><div class="section" title="3.3. File Based Encryption" id="Security_Guide-Encryption-Protecting_Data_at_Rest-File_Based_Encryption"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">3.3. File Based Encryption</h2></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.3. File Based Encryption</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="chap-Security_Guide-Encryption.html" title="Chapter 3. Encryption" /><link rel="prev" href="sect-Security_Guide-Encryption-Protecting_Data_at_Rest-Full_Disk_Encryption.html" title="3.2. Full Disk Encryption" /><link rel="next" href="Security_Guide-Encryption-Data_in_Motion.html" title="3.4. Data in Motion" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to
view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Encryption-Protecting_Data_at_Rest-Full_Disk_Encryption.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="Security_Guide-Encryption-Data_in_Motion.html"><strong>Next</strong></a></li></ul><div class="section" title="3.3. File Based Encryption" id="Security_Guide-Encryption-Protecting_Data_at_Rest-File_Based_Encryption"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="Security_Guide-Encryption-Protecting_Data_at_Rest-File_Based_Encryption">3.3. File Based Encryption</h2></div></div></
div><div class="para">
GnuPG (GPG) is an open source version of PGP that allows you to sign and/or encrypt a file or an email message. This is useful to maintain integrity of the message or file and also protects the confidentiality of the information contained within the file or email. In the case of email, GPG provides dual protection. Not only can it provide Data at Rest protection but also Data In Motion protection once the message has been sent across the network.
</div><div class="para">
File based encryption is intended to protect a file after it has left your computer, such as when you send a CD through the mail. Some file based encryption solutions will leave remnants of the encrypted files that an attacker who has physical access to your computer can recover under some circumstances. To protect the contents of those files from attackers who may have access to your computer, use file based encryption combined with another solution such as full disk encryption.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/We_Need_Feedback.html b/public_html/en-US/Fedora/13/html/Security_Guide/We_Need_Feedback.html
index 19718ff..42d27ce 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/We_Need_Feedback.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/We_Need_Feedback.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2. We Need Feedback!</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="pref-Security_Guide-Preface.html" title="Preface" /><link rel="prev" href="pref-Security_Guide-Preface.html" title="Preface" /><link rel="next" href="chap-Security_Guide-Security_Overview.html" title="Chapter 1. Security Overview" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title">
<a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="pref-Security_Guide-Preface.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Security_Guide-Security_Overview.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" title="2. We Need Feedback!" id="We_Need_Feedback" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2. We Need Feedback!</h2></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2. We Need Feedback!</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="pref-Security_Guide-Preface.html" title="Preface" /><link rel="prev" href="pref-Security_Guide-Preface.html" title="Preface" /><link rel="next" href="chap-Security_Guide-Security_Overview.html" title="Chapter 1. Security Overview" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><
a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="pref-Security_Guide-Preface.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Security_Guide-Security_Overview.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" title="2. We Need Feedback!" id="We_Need_Feedback" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="We_Need_Feedback">2. We Need Feedback!</h2></div></div></div><div class="para">
More information about the Linux Security Guide project can be found at <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</a>. Please select the proper component for this guide.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/apas02.html b/public_html/en-US/Fedora/13/html/Security_Guide/apas02.html
index f1be569..142b32a 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/apas02.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/apas02.html
@@ -1,39 +1,39 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>A.2. Public-key Encryption</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="chap-Security_Guide-Encryption_Standards.html" title="Appendix A. Encryption Standards" /><link rel="prev" href="chap-Security_Guide-Encryption_Standards.html" title="Appendix A. Encryption Standards" /><link rel="next" href="apas02s02.html" title="A.2.2. RSA" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable ifram
e display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security_Guide-Encryption_Standards.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="apas02s02.html"><strong>Next</strong></a></li></ul><div class="section" title="A.2. Public-key Encryption"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id3175945">A.2. Public-key Encryption</h2></div></div></div><div class="para">
- Public-key cryptography is a cryptographic approach, employed by many cryptographic algorithms and cryptosystems, whose distinguishing characteristic is the use of asymmetric key algorithms instead of or in addition to symmetric key algorithms. Using the techniques of public key-private key cryptography, many methods of protecting communications or authenticating messages formerly unknown have become practical. They do not require a secure initial exchange of one or more secret keys as is required when using symmetric key algorithms. It can also be used to create digital signatures.<sup>[<a id="id3175954" href="#ftn.id3175954" class="footnote">21</a>]</sup>
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>A.2. Public-key Encryption</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="chap-Security_Guide-Encryption_Standards.html" title="Appendix A. Encryption Standards" /><link rel="prev" href="chap-Security_Guide-Encryption_Standards.html" title="Appendix A. Encryption Standards" /><link rel="next" href="apas02s02.html" title="A.2.2. RSA" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security_Guide-Encryption_Standards.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="apas02s02.html"><strong>Next</strong></a></li></ul><div class="section" title="A.2. Public-key Encryption"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id2648790">A.2. Public-key Encryption</h2></div></div></div><div class="para">
+ Public-key cryptography is a cryptographic approach, employed by many cryptographic algorithms and cryptosystems, whose distinguishing characteristic is the use of asymmetric key algorithms instead of or in addition to symmetric key algorithms. Using the techniques of public key-private key cryptography, many methods of protecting communications or authenticating messages formerly unknown have become practical. They do not require a secure initial exchange of one or more secret keys as is required when using symmetric key algorithms. It can also be used to create digital signatures.<sup>[<a id="id2648799" href="#ftn.id2648799" class="footnote">21</a>]</sup>
</div><div class="para">
- Public key cryptography is a fundamental and widely used technology around the world, and is the approach which underlies such Internet standards as Transport Layer Security (TLS) (successor to SSL), PGP and GPG.<sup>[<a id="id3448985" href="#ftn.id3448985" class="footnote">22</a>]</sup>
+ Public key cryptography is a fundamental and widely used technology around the world, and is the approach which underlies such Internet standards as Transport Layer Security (TLS) (successor to SSL), PGP and GPG.<sup>[<a id="id2994219" href="#ftn.id2994219" class="footnote">22</a>]</sup>
</div><div class="para">
- The distinguishing technique used in public key cryptography is the use of asymmetric key algorithms, where the key used to encrypt a message is not the same as the key used to decrypt it. Each user has a pair of cryptographic keys — a public key and a private key. The private key is kept secret, whilst the public key may be widely distributed. Messages are encrypted with the recipient's public key and can only be decrypted with the corresponding private key. The keys are related mathematically, but the private key cannot be feasibly (ie, in actual or projected practice) derived from the public key. It was the discovery of such algorithms which revolutionized the practice of cryptography beginning in the middle 1970s.<sup>[<a id="id3270172" href="#ftn.id3270172" class="footnote">23</a>]</sup>
+ The distinguishing technique used in public key cryptography is the use of asymmetric key algorithms, where the key used to encrypt a message is not the same as the key used to decrypt it. Each user has a pair of cryptographic keys — a public key and a private key. The private key is kept secret, whilst the public key may be widely distributed. Messages are encrypted with the recipient's public key and can only be decrypted with the corresponding private key. The keys are related mathematically, but the private key cannot be feasibly (ie, in actual or projected practice) derived from the public key. It was the discovery of such algorithms which revolutionized the practice of cryptography beginning in the middle 1970s.<sup>[<a id="id2772142" href="#ftn.id2772142" class="footnote">23</a>]</sup>
</div><div class="para">
- In contrast, Symmetric-key algorithms, variations of which have been used for some thousands of years, use a single secret key shared by sender and receiver (which must also be kept private, thus accounting for the ambiguity of the common terminology) for both encryption and decryption. To use a symmetric encryption scheme, the sender and receiver must securely share a key in advance.<sup>[<a id="id3178130" href="#ftn.id3178130" class="footnote">24</a>]</sup>
+ In contrast, Symmetric-key algorithms, variations of which have been used for some thousands of years, use a single secret key shared by sender and receiver (which must also be kept private, thus accounting for the ambiguity of the common terminology) for both encryption and decryption. To use a symmetric encryption scheme, the sender and receiver must securely share a key in advance.<sup>[<a id="id2726852" href="#ftn.id2726852" class="footnote">24</a>]</sup>
</div><div class="para">
- Because symmetric key algorithms are nearly always much less computationally intensive, it is common to exchange a key using a key-exchange algorithm and transmit data using that key and a symmetric key algorithm. PGP, and the SSL/TLS family of schemes do this, for instance, and are called hybrid cryptosystems in consequence.<sup>[<a id="id3371733" href="#ftn.id3371733" class="footnote">25</a>]</sup>
- </div><div class="section" title="A.2.1. Diffie-Hellman"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id3371753">A.2.1. Diffie-Hellman</h3></div></div></div><div class="para">
- Diffie–Hellman key exchange (D–H) is a cryptographic protocol that allows two parties that have no prior knowledge of each other to jointly establish a shared secret key over an insecure communications channel. This key can then be used to encrypt subsequent communications using a symmetric key cipher.<sup>[<a id="id3148637" href="#ftn.id3148637" class="footnote">26</a>]</sup>
- </div><div class="section" title="A.2.1.1. Diffie-Hellman History"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="id3148655">A.2.1.1. Diffie-Hellman History</h4></div></div></div><div class="para">
- The scheme was first published by Whitfield Diffie and Martin Hellman in 1976, although it later emerged that it had been separately invented a few years earlier within GCHQ, the British signals intelligence agency, by Malcolm J. Williamson but was kept classified. In 2002, Hellman suggested the algorithm be called Diffie–Hellman–Merkle key exchange in recognition of Ralph Merkle's contribution to the invention of public-key cryptography (Hellman, 2002).<sup>[<a id="id3148671" href="#ftn.id3148671" class="footnote">27</a>]</sup>
+ Because symmetric key algorithms are nearly always much less computationally intensive, it is common to exchange a key using a key-exchange algorithm and transmit data using that key and a symmetric key algorithm. PGP, and the SSL/TLS family of schemes do this, for instance, and are called hybrid cryptosystems in consequence.<sup>[<a id="id2684063" href="#ftn.id2684063" class="footnote">25</a>]</sup>
+ </div><div class="section" title="A.2.1. Diffie-Hellman"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id2684083">A.2.1. Diffie-Hellman</h3></div></div></div><div class="para">
+ Diffie–Hellman key exchange (D–H) is a cryptographic protocol that allows two parties that have no prior knowledge of each other to jointly establish a shared secret key over an insecure communications channel. This key can then be used to encrypt subsequent communications using a symmetric key cipher.<sup>[<a id="id2842738" href="#ftn.id2842738" class="footnote">26</a>]</sup>
+ </div><div class="section" title="A.2.1.1. Diffie-Hellman History"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="id2842756">A.2.1.1. Diffie-Hellman History</h4></div></div></div><div class="para">
+ The scheme was first published by Whitfield Diffie and Martin Hellman in 1976, although it later emerged that it had been separately invented a few years earlier within GCHQ, the British signals intelligence agency, by Malcolm J. Williamson but was kept classified. In 2002, Hellman suggested the algorithm be called Diffie–Hellman–Merkle key exchange in recognition of Ralph Merkle's contribution to the invention of public-key cryptography (Hellman, 2002).<sup>[<a id="id2852596" href="#ftn.id2852596" class="footnote">27</a>]</sup>
</div><div class="para">
- Although Diffie–Hellman key agreement itself is an anonymous (non-authenticated) key-agreement protocol, it provides the basis for a variety of authenticated protocols, and is used to provide perfect forward secrecy in Transport Layer Security's ephemeral modes (referred to as EDH or DHE depending on the cipher suite).<sup>[<a id="id3314638" href="#ftn.id3314638" class="footnote">28</a>]</sup>
+ Although Diffie–Hellman key agreement itself is an anonymous (non-authenticated) key-agreement protocol, it provides the basis for a variety of authenticated protocols, and is used to provide perfect forward secrecy in Transport Layer Security's ephemeral modes (referred to as EDH or DHE depending on the cipher suite).<sup>[<a id="id2852622" href="#ftn.id2852622" class="footnote">28</a>]</sup>
</div><div class="para">
- U.S. Patent 4,200,770, now expired, describes the algorithm and credits Hellman, Diffie, and Merkle as inventors.<sup>[<a id="id3226903" href="#ftn.id3226903" class="footnote">29</a>]</sup>
- </div></div></div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id3175954" href="#id3175954" class="para">21</a>] </sup>
+ U.S. Patent 4,200,770, now expired, describes the algorithm and credits Hellman, Diffie, and Merkle as inventors.<sup>[<a id="id2969161" href="#ftn.id2969161" class="footnote">29</a>]</sup>
+ </div></div></div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id2648799" href="#id2648799" class="para">21</a>] </sup>
"Public-key Encryption." <span class="emphasis"><em>Wikipedia.</em></span> 14 November 2009 <a href="http://en.wikipedia.org/wiki/Public-key_cryptography">http://en.wikipedia.org/wiki/Public-key_cryptography</a>
- </p></div><div class="footnote"><p><sup>[<a id="ftn.id3448985" href="#id3448985" class="para">22</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id2994219" href="#id2994219" class="para">22</a>] </sup>
"Public-key Encryption." <span class="emphasis"><em>Wikipedia.</em></span> 14 November 2009 <a href="http://en.wikipedia.org/wiki/Public-key_cryptography">http://en.wikipedia.org/wiki/Public-key_cryptography</a>
- </p></div><div class="footnote"><p><sup>[<a id="ftn.id3270172" href="#id3270172" class="para">23</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id2772142" href="#id2772142" class="para">23</a>] </sup>
"Public-key Encryption." <span class="emphasis"><em>Wikipedia.</em></span> 14 November 2009 <a href="http://en.wikipedia.org/wiki/Public-key_cryptography">http://en.wikipedia.org/wiki/Public-key_cryptography</a>
- </p></div><div class="footnote"><p><sup>[<a id="ftn.id3178130" href="#id3178130" class="para">24</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id2726852" href="#id2726852" class="para">24</a>] </sup>
"Public-key Encryption." <span class="emphasis"><em>Wikipedia.</em></span> 14 November 2009 <a href="http://en.wikipedia.org/wiki/Public-key_cryptography">http://en.wikipedia.org/wiki/Public-key_cryptography</a>
- </p></div><div class="footnote"><p><sup>[<a id="ftn.id3371733" href="#id3371733" class="para">25</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id2684063" href="#id2684063" class="para">25</a>] </sup>
"Public-key Encryption." <span class="emphasis"><em>Wikipedia.</em></span> 14 November 2009 <a href="http://en.wikipedia.org/wiki/Public-key_cryptography">http://en.wikipedia.org/wiki/Public-key_cryptography</a>
- </p></div><div class="footnote"><p><sup>[<a id="ftn.id3148637" href="#id3148637" class="para">26</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id2842738" href="#id2842738" class="para">26</a>] </sup>
"Diffie-Hellman." <span class="emphasis"><em>Wikipedia.</em></span> 14 November 2009 <a href="http://en.wikipedia.org/wiki/Diffie-Hellman">http://en.wikipedia.org/wiki/Diffie-Hellman</a>
- </p></div><div class="footnote"><p><sup>[<a id="ftn.id3148671" href="#id3148671" class="para">27</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id2852596" href="#id2852596" class="para">27</a>] </sup>
"Diffie-Hellman." <span class="emphasis"><em>Wikipedia.</em></span> 14 November 2009 <a href="http://en.wikipedia.org/wiki/Diffie-Hellman">http://en.wikipedia.org/wiki/Diffie-Hellman</a>
- </p></div><div class="footnote"><p><sup>[<a id="ftn.id3314638" href="#id3314638" class="para">28</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id2852622" href="#id2852622" class="para">28</a>] </sup>
"Diffie-Hellman." <span class="emphasis"><em>Wikipedia.</em></span> 14 November 2009 <a href="http://en.wikipedia.org/wiki/Diffie-Hellman">http://en.wikipedia.org/wiki/Diffie-Hellman</a>
- </p></div><div class="footnote"><p><sup>[<a id="ftn.id3226903" href="#id3226903" class="para">29</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id2969161" href="#id2969161" class="para">29</a>] </sup>
"Diffie-Hellman." <span class="emphasis"><em>Wikipedia.</em></span> 14 November 2009 <a href="http://en.wikipedia.org/wiki/Diffie-Hellman">http://en.wikipedia.org/wiki/Diffie-Hellman</a>
</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security_Guide-Encryption_Standards.html"><strong>Prev</strong>Appendix A. Encryption Standards</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="apas02s02.html"><strong>Next</strong>A.2.2. RSA</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/apas02s02.html b/public_html/en-US/Fedora/13/html/Security_Guide/apas02s02.html
index 3aa031c..a1a6cd0 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/apas02s02.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/apas02s02.html
@@ -1,7 +1,7 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>A.2.2. RSA</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="apas02.html" title="A.2. Public-key Encryption" /><link rel="prev" href="apas02.html" title="A.2. Public-key Encryption" /><link rel="next" href="apas02s03.html" title="A.2.3. DSA" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img sr
c="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="apas02.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="apas02s03.html"><strong>Next</strong></a></li></ul><div class="section" title="A.2.2. RSA"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id3226924">A.2.2. RSA</h3></div></div></div><div class="para">
- In cryptography, RSA (which stands for Rivest, Shamir and Adleman who first publicly described it; see below) is an algorithm for public-key cryptography. It is the first algorithm known to be suitable for signing as well as encryption, and was one of the first great advances in public key cryptography. RSA is widely used in electronic commerce protocols, and is believed to be secure given sufficiently long keys and the use of up-to-date implementations.<sup>[<a id="id3316060" href="#ftn.id3316060" class="footnote">30</a>]</sup>
- </div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id3316060" href="#id3316060" class="para">30</a>] </sup>
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>A.2.2. RSA</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="apas02.html" title="A.2. Public-key Encryption" /><link rel="prev" href="apas02.html" title="A.2. Public-key Encryption" /><link rel="next" href="apas02s03.html" title="A.2.3. DSA" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src
="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="apas02.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="apas02s03.html"><strong>Next</strong></a></li></ul><div class="section" title="A.2.2. RSA"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id2969181">A.2.2. RSA</h3></div></div></div><div class="para">
+ In cryptography, RSA (which stands for Rivest, Shamir and Adleman who first publicly described it; see below) is an algorithm for public-key cryptography. It is the first algorithm known to be suitable for signing as well as encryption, and was one of the first great advances in public key cryptography. RSA is widely used in electronic commerce protocols, and is believed to be secure given sufficiently long keys and the use of up-to-date implementations.<sup>[<a id="id2712877" href="#ftn.id2712877" class="footnote">30</a>]</sup>
+ </div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id2712877" href="#id2712877" class="para">30</a>] </sup>
"RSA" <span class="emphasis"><em>Wikipedia</em></span> 14 April 2010 <a href="http://en.wikipedia.org/wiki/RSA">http://en.wikipedia.org/wiki/RSA</a>
</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apas02.html"><strong>Prev</strong>A.2. Public-key Encryption</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="apas02s03.html"><strong>Next</strong>A.2.3. DSA</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/apas02s03.html b/public_html/en-US/Fedora/13/html/Security_Guide/apas02s03.html
index 4472d2d..3a3083b 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/apas02s03.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/apas02s03.html
@@ -1,7 +1,7 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>A.2.3. DSA</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="apas02.html" title="A.2. Public-key Encryption" /><link rel="prev" href="apas02s02.html" title="A.2.2. RSA" /><link rel="next" href="apas02s04.html" title="A.2.4. SSL/TLS" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common
_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="apas02s02.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="apas02s04.html"><strong>Next</strong></a></li></ul><div class="section" title="A.2.3. DSA"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id3316078">A.2.3. DSA</h3></div></div></div><div class="para">
- The Digital Signature Algorithm (DSA) is a United States Federal Government standard or FIPS for digital signatures. It was proposed by the National Institute of Standards and Technology (NIST) in August 1991 for use in their Digital Signature Standard (DSS), specified in FIPS 186, adopted in 1993. A minor revision was issued in 1996 as FIPS 186-1. The standard was expanded further in 2000 as FIPS 186-2 and again in 2009 as FIPS 186-3.<sup>[<a id="id3316094" href="#ftn.id3316094" class="footnote">31</a>]</sup>
- </div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id3316094" href="#id3316094" class="para">31</a>] </sup>
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>A.2.3. DSA</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="apas02.html" title="A.2. Public-key Encryption" /><link rel="prev" href="apas02s02.html" title="A.2.2. RSA" /><link rel="next" href="apas02s04.html" title="A.2.4. SSL/TLS" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_
Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="apas02s02.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="apas02s04.html"><strong>Next</strong></a></li></ul><div class="section" title="A.2.3. DSA"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id2712895">A.2.3. DSA</h3></div></div></div><div class="para">
+ The Digital Signature Algorithm (DSA) is a United States Federal Government standard or FIPS for digital signatures. It was proposed by the National Institute of Standards and Technology (NIST) in August 1991 for use in their Digital Signature Standard (DSS), specified in FIPS 186, adopted in 1993. A minor revision was issued in 1996 as FIPS 186-1. The standard was expanded further in 2000 as FIPS 186-2 and again in 2009 as FIPS 186-3.<sup>[<a id="id2774345" href="#ftn.id2774345" class="footnote">31</a>]</sup>
+ </div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id2774345" href="#id2774345" class="para">31</a>] </sup>
"Digital Signature Algorithm" <span class="emphasis"><em>Wikipedia</em></span> 14 April 2010 <a href="http://en.wikipedia.org/wiki/Digital_Signature_Algorithm">http://en.wikipedia.org/wiki/Digital_Signature_Algorithm</a>
</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apas02s02.html"><strong>Prev</strong>A.2.2. RSA</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="apas02s04.html"><strong>Next</strong>A.2.4. SSL/TLS</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/apas02s04.html b/public_html/en-US/Fedora/13/html/Security_Guide/apas02s04.html
index b95a289..b0f42a6 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/apas02s04.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/apas02s04.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>A.2.4. SSL/TLS</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="apas02.html" title="A.2. Public-key Encryption" /><link rel="prev" href="apas02s03.html" title="A.2.3. DSA" /><link rel="next" href="apas02s05.html" title="A.2.5. Cramer-Shoup Cryptosystem" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject
.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="apas02s03.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="apas02s05.html"><strong>Next</strong></a></li></ul><div class="section" title="A.2.4. SSL/TLS"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id3235283">A.2.4. SSL/TLS</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>A.2.4. SSL/TLS</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="apas02.html" title="A.2. Public-key Encryption" /><link rel="prev" href="apas02s03.html" title="A.2.3. DSA" /><link rel="next" href="apas02s05.html" title="A.2.5. Cramer-Shoup Cryptosystem" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.
org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="apas02s03.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="apas02s05.html"><strong>Next</strong></a></li></ul><div class="section" title="A.2.4. SSL/TLS"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id2774364">A.2.4. SSL/TLS</h3></div></div></div><div class="para">
Transport Layer Security (TLS) and its predecessor, Secure Socket Layer (SSL), are cryptographic protocols that provide security for communications over networks such as the Internet. TLS and SSL encrypt the segments of network connections at the Transport Layer end-to-end. Several versions of the protocols are in widespread use in applications like web browsing, electronic mail, Internet faxing, instant messaging and voice-over-IP (VoIP). TLS is an IETF standards track protocol, last updated in RFC 5246, that was based on the earlier SSL specifications developed by Netscape Corporation.
</div><div class="para">
The TLS protocol allows client/server applications to communicate across a network in a way designed to prevent eavesdropping and tampering. TLS provides endpoint authentication and communications confidentiality over the Internet using cryptography. TLS provides RSA security with 1024 and 2048 bit strengths.
@@ -11,7 +11,7 @@
</div><div class="para">
Typically, the key information and certificates necessary for TLS are handled in the form of X.509 certificates, which define required fields and data formats.
</div><div class="para">
- SSL operates in modular fashion. It is extensible by design, with support for forward and backward compatibility and negotiation between peers.<sup>[<a id="id3323694" href="#ftn.id3323694" class="footnote">32</a>]</sup>
- </div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id3323694" href="#id3323694" class="para">32</a>] </sup>
+ SSL operates in modular fashion. It is extensible by design, with support for forward and backward compatibility and negotiation between peers.<sup>[<a id="id3915647" href="#ftn.id3915647" class="footnote">32</a>]</sup>
+ </div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id3915647" href="#id3915647" class="para">32</a>] </sup>
"Transport Layer Security" <span class="emphasis"><em>Wikipedia</em></span> 14 April 2010 <a href="http://en.wikipedia.org/wiki/Transport_Layer_Security">http://en.wikipedia.org/wiki/Transport_Layer_Security</a>
</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apas02s03.html"><strong>Prev</strong>A.2.3. DSA</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="apas02s05.html"><strong>Next</strong>A.2.5. Cramer-Shoup Cryptosystem</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/apas02s05.html b/public_html/en-US/Fedora/13/html/Security_Guide/apas02s05.html
index 042dca1..4369680 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/apas02s05.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/apas02s05.html
@@ -1,7 +1,7 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>A.2.5. Cramer-Shoup Cryptosystem</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="apas02.html" title="A.2. Public-key Encryption" /><link rel="prev" href="apas02s04.html" title="A.2.4. SSL/TLS" /><link rel="next" href="apas02s06.html" title="A.2.6. ElGamal Encryption" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://ww
w.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="apas02s04.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="apas02s06.html"><strong>Next</strong></a></li></ul><div class="section" title="A.2.5. Cramer-Shoup Cryptosystem"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id3316796">A.2.5. Cramer-Shoup Cryptosystem</h3></div></div></div><div class="para">
- The Cramer–Shoup system is an asymmetric key encryption algorithm, and was the first efficient scheme proven to be secure against adaptive chosen ciphertext attack using standard cryptographic assumptions. Its security is based on the computational intractability (widely assumed, but not proved) of the decisional Diffie–Hellman assumption. Developed by Ronald Cramer and Victor Shoup in 1998, it is an extension of the Elgamal cryptosystem. In contrast to Elgamal, which is extremely malleable, Cramer–Shoup adds additional elements to ensure non-malleability even against a resourceful attacker. This non-malleability is achieved through the use of a collision-resistant hash function and additional computations, resulting in a ciphertext which is twice as large as in Elgamal.<sup>[<a id="id3404964" href="#ftn.id3404964" class="footnote">33</a>]</sup>
- </div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id3404964" href="#id3404964" class="para">33</a>] </sup>
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>A.2.5. Cramer-Shoup Cryptosystem</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="apas02.html" title="A.2. Public-key Encryption" /><link rel="prev" href="apas02s04.html" title="A.2.4. SSL/TLS" /><link rel="next" href="apas02s06.html" title="A.2.6. ElGamal Encryption" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www
.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="apas02s04.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="apas02s06.html"><strong>Next</strong></a></li></ul><div class="section" title="A.2.5. Cramer-Shoup Cryptosystem"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id3915666">A.2.5. Cramer-Shoup Cryptosystem</h3></div></div></div><div class="para">
+ The Cramer–Shoup system is an asymmetric key encryption algorithm, and was the first efficient scheme proven to be secure against adaptive chosen ciphertext attack using standard cryptographic assumptions. Its security is based on the computational intractability (widely assumed, but not proved) of the decisional Diffie–Hellman assumption. Developed by Ronald Cramer and Victor Shoup in 1998, it is an extension of the Elgamal cryptosystem. In contrast to Elgamal, which is extremely malleable, Cramer–Shoup adds additional elements to ensure non-malleability even against a resourceful attacker. This non-malleability is achieved through the use of a collision-resistant hash function and additional computations, resulting in a ciphertext which is twice as large as in Elgamal.<sup>[<a id="id3915675" href="#ftn.id3915675" class="footnote">33</a>]</sup>
+ </div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id3915675" href="#id3915675" class="para">33</a>] </sup>
"Cramer–Shoup cryptosystem" <span class="emphasis"><em>Wikipedia</em></span> 14 April 2010 <a href="http://en.wikipedia.org/wiki/Cramer-Shoup_cryptosystem">http://en.wikipedia.org/wiki/Cramer-Shoup_cryptosystem</a>
</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apas02s04.html"><strong>Prev</strong>A.2.4. SSL/TLS</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="apas02s06.html"><strong>Next</strong>A.2.6. ElGamal Encryption</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/apas02s06.html b/public_html/en-US/Fedora/13/html/Security_Guide/apas02s06.html
index 2c311db..5dcc44f 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/apas02s06.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/apas02s06.html
@@ -1,7 +1,7 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>A.2.6. ElGamal Encryption</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="apas02.html" title="A.2. Public-key Encryption" /><link rel="prev" href="apas02s05.html" title="A.2.5. Cramer-Shoup Cryptosystem" /><link rel="next" href="appe-Publican-Revision_History.html" title="Appendix B. Revision History" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="ti
tle"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="apas02s05.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="appe-Publican-Revision_History.html"><strong>Next</strong></a></li></ul><div class="section" title="A.2.6. ElGamal Encryption"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id3404983">A.2.6. ElGamal Encryption</h3></div></div></div><div class="para">
- In cryptography, the ElGamal encryption system is an asymmetric key encryption algorithm for public-key cryptography which is based on the Diffie-Hellman key agreement. It was described by Taher Elgamal in 1985.[1] ElGamal encryption is used in the free GNU Privacy Guard software, recent versions of PGP, and other cryptosystems. The Digital Signature Algorithm is a variant of the ElGamal signature scheme, which should not be confused with ElGamal encryption.<sup>[<a id="id3405000" href="#ftn.id3405000" class="footnote">34</a>]</sup>
- </div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id3405000" href="#id3405000" class="para">34</a>] </sup>
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>A.2.6. ElGamal Encryption</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="apas02.html" title="A.2. Public-key Encryption" /><link rel="prev" href="apas02s05.html" title="A.2.5. Cramer-Shoup Cryptosystem" /><link rel="next" href="appe-Publican-Revision_History.html" title="Appendix B. Revision History" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="tit
le"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="apas02s05.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="appe-Publican-Revision_History.html"><strong>Next</strong></a></li></ul><div class="section" title="A.2.6. ElGamal Encryption"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id2926050">A.2.6. ElGamal Encryption</h3></div></div></div><div class="para">
+ In cryptography, the ElGamal encryption system is an asymmetric key encryption algorithm for public-key cryptography which is based on the Diffie-Hellman key agreement. It was described by Taher Elgamal in 1985.[1] ElGamal encryption is used in the free GNU Privacy Guard software, recent versions of PGP, and other cryptosystems. The Digital Signature Algorithm is a variant of the ElGamal signature scheme, which should not be confused with ElGamal encryption.<sup>[<a id="id2917808" href="#ftn.id2917808" class="footnote">34</a>]</sup>
+ </div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id2917808" href="#id2917808" class="para">34</a>] </sup>
"ElGamal encryption" <span class="emphasis"><em>Wikipedia</em></span> 14 April 2010 <a href="http://en.wikipedia.org/wiki/ElGamal_encryption">http://en.wikipedia.org/wiki/ElGamal_encryption</a>
</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="apas02s05.html"><strong>Prev</strong>A.2.5. Cramer-Shoup Cryptosystem</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="appe-Publican-Revision_History.html"><strong>Next</strong>Appendix B. Revision History</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/appe-Publican-Revision_History.html b/public_html/en-US/Fedora/13/html/Security_Guide/appe-Publican-Revision_History.html
index d303097..9c06c83 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/appe-Publican-Revision_History.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/appe-Publican-Revision_History.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Appendix B. Revision History</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="index.html" title="Security Guide" /><link rel="prev" href="apas02s06.html" title="A.2.6. ElGamal Encryption" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product
Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="apas02s06.html"><strong>Prev</strong></a></li><li class="next"></li></ul><div xml:lang="en-US" class="appendix" title="Appendix B. Revision History" id="appe-Publican-Revision_History" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Revision History</h1></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Appendix B. Revision History</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="index.html" title="Security Guide" /><link rel="prev" href="apas02s06.html" title="A.2.6. ElGamal Encryption" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product 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="apas02s06.html"><strong>Prev</strong></a></li><li class="next"></li></ul><div xml:lang="en-US" class="appendix" title="Appendix B. Revision History" id="appe-Publican-Revision_History" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Revision History</h1></div></div></div><div class="para">
<div class="revhistory"><table border="0" width="100%" summary="Revision history"><tr><th align="left" valign="top" colspan="3"><b>Revision History</b></th></tr><tr><td align="left">Revision 13.0-8</td><td align="left">Wed Jun 9 2010</td><td align="left"><span class="author"><span class="firstname">Eric</span> <span class="surname">Christensen</span></span></td></tr><tr><td align="left" colspan="3">
<table border="0" summary="Simple list" class="simplelist"><tr><td>Removed FireGPG text as that project has been retired.</td></tr></table>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/chap-Security_Guide-Encryption.html b/public_html/en-US/Fedora/13/html/Security_Guide/chap-Security_Guide-Encryption.html
index c5b189e..f5705b7 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/chap-Security_Guide-Encryption.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/chap-Security_Guide-Encryption.html
@@ -1,7 +1,7 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 3. Encryption</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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.6.2. Useful IP Tables Websites" /><link rel="next" href="sect-Security_Guide-Encryption-Protecting_Data_at_Rest-Full_Disk_Encryption.html" title="3.2. Full Disk Encryption" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe
, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Additional_Resources-Useful_IP_Tables_Websites.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-Protecting_Data_at_Rest-Full_Disk_Encryption.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 3. Encryption" id="chap-Security_Guide-Encryption" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 3. Encryption</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Security_Guide-Encryption.html#sect-Se
curity_Guide-Encryption-Data_at_Rest">3.1. Data at Rest</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Encryption-Protecting_Data_at_Rest-Full_Disk_Encryption.html">3.2. Full Disk Encryption</a></span></dt><dt><span class="section"><a href="Security_Guide-Encryption-Protecting_Data_at_Rest-File_Based_Encryption.html">3.3. File Based Encryption</a></span></dt><dt><span class="section"><a href="Security_Guide-Encryption-Data_in_Motion.html">3.4. Data in Motion</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. Secure Shell</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.h
tml#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. Generating 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. Generating 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. Generating GPG Keys Using the Command Line</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Alpine.html">3.9.4. Using GPG with Alpine</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution.html">3.9.5. Using GPG with Evolution</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Thunderbird.html">3.9.6. Using GPG with Thunderbird</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Encryption-Using_GPG-About_Public_Key_Encryption.html">3.9.7. About Public Key
Encryption</a></span></dt></dl></dd></dl></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 3. Encryption</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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.6.2. Useful IP Tables Websites" /><link rel="next" href="sect-Security_Guide-Encryption-Protecting_Data_at_Rest-Full_Disk_Encryption.html" title="3.2. Full Disk Encryption" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe,
to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Additional_Resources-Useful_IP_Tables_Websites.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-Protecting_Data_at_Rest-Full_Disk_Encryption.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 3. Encryption" id="chap-Security_Guide-Encryption" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 3. Encryption</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Security_Guide-Encryption.html#sect-Sec
urity_Guide-Encryption-Data_at_Rest">3.1. Data at Rest</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Encryption-Protecting_Data_at_Rest-Full_Disk_Encryption.html">3.2. Full Disk Encryption</a></span></dt><dt><span class="section"><a href="Security_Guide-Encryption-Protecting_Data_at_Rest-File_Based_Encryption.html">3.3. File Based Encryption</a></span></dt><dt><span class="section"><a href="Security_Guide-Encryption-Data_in_Motion.html">3.4. Data in Motion</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. Secure Shell</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.ht
ml#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. Generating 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. Generating 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. Generating GPG Keys Using the Command Line</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Alpine.html">3.9.4. Using GPG with Alpine</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution.html">3.9.5. Using GPG with Evolution</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Thunderbird.html">3.9.6. Using GPG with Thunderbird</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Encryption-Using_GPG-About_Public_Key_Encryption.html">3.9.7. About Public Key
Encryption</a></span></dt></dl></dd></dl></div><div class="para">
There are two main types of data that must be protected: data at rest and data in motion. These different types of data are protected in similar ways using similar technology but the implementations can be completely different. No single protective implementation can prevent all possible methods of compromise as the same information may be at rest and in motion at different points in time.
- </div><div class="section" title="3.1. Data at Rest" id="sect-Security_Guide-Encryption-Data_at_Rest"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">3.1. Data at Rest</h2></div></div></div><div class="para">
+ </div><div class="section" title="3.1. Data at Rest" id="sect-Security_Guide-Encryption-Data_at_Rest"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sect-Security_Guide-Encryption-Data_at_Rest">3.1. Data at Rest</h2></div></div></div><div class="para">
Data at rest is data that is stored on a hard drive, tape, CD, DVD, disk, or other media. This information's biggest threat comes from being physically stolen. Laptops in airports, CDs going through the mail, and backup tapes that get left in the wrong places are all examples of events where data can be compromised through theft. If the data was encrypted on the media then you wouldn't have to worry as much about the data being compromised.
</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Additional_Resources-Useful_IP_Tables_Websites.html"><strong>Prev</strong>2.9.6.2. Useful IP Tables Websites</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-Protecting_Data_at_Rest-Full_Disk_Encryption.html"><strong>Next</strong>3.2. Full Disk Encryption</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/chap-Security_Guide-Encryption_Standards.html b/public_html/en-US/Fedora/13/html/Security_Guide/chap-Security_Guide-Encryption_Standards.html
index 2f7a001..0eefa0d 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/chap-Security_Guide-Encryption_Standards.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/chap-Security_Guide-Encryption_Standards.html
@@ -1,31 +1,31 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Appendix A. Encryption Standards</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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-References.html" title="Chapter 7. References" /><link rel="next" href="apas02.html" title="A.2. Public-key Encryption" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" h
ref="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-References.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="apas02.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="appendix" title="Appendix A. Encryption Standards" id="chap-Security_Guide-Encryption_Standards" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Encryption Standards</h1></div></div></div><div class="para">
- </div><div class="section" title="A.1. Synchronous Encryption"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id3430291">A.1. Synchronous Encryption</h2></div></div></div><div class="para">
- </div><div class="section" title="A.1.1. Advanced Encryption Standard - AES"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id3302598">A.1.1. Advanced Encryption Standard - AES</h3></div></div></div><div class="para">
- In cryptography, the Advanced Encryption Standard (AES) is an encryption standard adopted by the U.S. government. The standard comprises three block ciphers, AES-128, AES-192 and AES-256, adopted from a larger collection originally published as Rijndael. Each AES cipher has a 128-bit block size, with key sizes of 128, 192 and 256 bits, respectively. The AES ciphers have been analyzed extensively and are now used worldwide, as was the case with its predecessor, the Data Encryption Standard (DES).<sup>[<a id="id4402321" href="#ftn.id4402321" class="footnote">15</a>]</sup>
- </div><div class="section" title="A.1.1.1. AES Uses"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="id3362725">A.1.1.1. AES Uses</h4></div></div></div><div class="para">
- </div></div><div class="section" title="A.1.1.2. AES History"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="id3330867">A.1.1.2. AES History</h4></div></div></div><div class="para">
- AES was announced by National Institute of Standards and Technology (NIST) as U.S. FIPS PUB 197 (FIPS 197) on November 26, 2001 after a 5-year standardization process in which fifteen competing designs were presented and evaluated before Rijndael was selected as the most suitable (see Advanced Encryption Standard process for more details). It became effective as a standard May 26, 2002. It is available in many different encryption packages. AES is the first publicly accessible and open cipher approved by the NSA for top secret information (see Security of AES, below).<sup>[<a id="id3466628" href="#ftn.id3466628" class="footnote">16</a>]</sup>
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Appendix A. Encryption Standards</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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-References.html" title="Chapter 7. References" /><link rel="next" href="apas02.html" title="A.2. Public-key Encryption" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" hr
ef="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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-References.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="apas02.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="appendix" title="Appendix A. Encryption Standards" id="chap-Security_Guide-Encryption_Standards" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Encryption Standards</h1></div></div></div><div class="para">
+ </div><div class="section" title="A.1. Synchronous Encryption"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id2872303">A.1. Synchronous Encryption</h2></div></div></div><div class="para">
+ </div><div class="section" title="A.1.1. Advanced Encryption Standard - AES"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id2644834">A.1.1. Advanced Encryption Standard - AES</h3></div></div></div><div class="para">
+ In cryptography, the Advanced Encryption Standard (AES) is an encryption standard adopted by the U.S. government. The standard comprises three block ciphers, AES-128, AES-192 and AES-256, adopted from a larger collection originally published as Rijndael. Each AES cipher has a 128-bit block size, with key sizes of 128, 192 and 256 bits, respectively. The AES ciphers have been analyzed extensively and are now used worldwide, as was the case with its predecessor, the Data Encryption Standard (DES).<sup>[<a id="id2758744" href="#ftn.id2758744" class="footnote">15</a>]</sup>
+ </div><div class="section" title="A.1.1.1. AES Uses"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="id2822587">A.1.1.1. AES Uses</h4></div></div></div><div class="para">
+ </div></div><div class="section" title="A.1.1.2. AES History"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="id2684588">A.1.1.2. AES History</h4></div></div></div><div class="para">
+ AES was announced by National Institute of Standards and Technology (NIST) as U.S. FIPS PUB 197 (FIPS 197) on November 26, 2001 after a 5-year standardization process in which fifteen competing designs were presented and evaluated before Rijndael was selected as the most suitable (see Advanced Encryption Standard process for more details). It became effective as a standard May 26, 2002. It is available in many different encryption packages. AES is the first publicly accessible and open cipher approved by the NSA for top secret information (see Security of AES, below).<sup>[<a id="id2993158" href="#ftn.id2993158" class="footnote">16</a>]</sup>
</div><div class="para">
- The Rijndael cipher was developed by two Belgian cryptographers, Joan Daemen and Vincent Rijmen, and submitted by them to the AES selection process. Rijndael (pronounced [rÉ›indaËl]) is a portmanteau of the names of the two inventors.<sup>[<a id="id3132579" href="#ftn.id3132579" class="footnote">17</a>]</sup>
- </div></div></div><div class="section" title="A.1.2. Data Encryption Standard - DES"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id3049809">A.1.2. Data Encryption Standard - DES</h3></div></div></div><div class="para">
- The Data Encryption Standard (DES) is a block cipher (a form of shared secret encryption) that was selected by the National Bureau of Standards as an official Federal Information Processing Standard (FIPS) for the United States in 1976 and which has subsequently enjoyed widespread use internationally. It is based on a symmetric-key algorithm that uses a 56-bit key. The algorithm was initially controversial with classified design elements, a relatively short key length, and suspicions about a National Security Agency (NSA) backdoor. DES consequently came under intense academic scrutiny which motivated the modern understanding of block ciphers and their cryptanalysis.<sup>[<a id="id3272416" href="#ftn.id3272416" class="footnote">18</a>]</sup>
- </div><div class="section" title="A.1.2.1. DES Uses"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="id4400532">A.1.2.1. DES Uses</h4></div></div></div><div class="para">
- </div></div><div class="section" title="A.1.2.2. DES History"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="id3503457">A.1.2.2. DES History</h4></div></div></div><div class="para">
- DES is now considered to be insecure for many applications. This is chiefly due to the 56-bit key size being too small; in January, 1999, distributed.net and the Electronic Frontier Foundation collaborated to publicly break a DES key in 22 hours and 15 minutes (see chronology). There are also some analytical results which demonstrate theoretical weaknesses in the cipher, although they are unfeasible to mount in practice. The algorithm is believed to be practically secure in the form of Triple DES, although there are theoretical attacks. In recent years, the cipher has been superseded by the Advanced Encryption Standard (AES).<sup>[<a id="id3259210" href="#ftn.id3259210" class="footnote">19</a>]</sup>
+ The Rijndael cipher was developed by two Belgian cryptographers, Joan Daemen and Vincent Rijmen, and submitted by them to the AES selection process. Rijndael (pronounced [rÉ›indaËl]) is a portmanteau of the names of the two inventors.<sup>[<a id="id2657664" href="#ftn.id2657664" class="footnote">17</a>]</sup>
+ </div></div></div><div class="section" title="A.1.2. Data Encryption Standard - DES"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id2721588">A.1.2. Data Encryption Standard - DES</h3></div></div></div><div class="para">
+ The Data Encryption Standard (DES) is a block cipher (a form of shared secret encryption) that was selected by the National Bureau of Standards as an official Federal Information Processing Standard (FIPS) for the United States in 1976 and which has subsequently enjoyed widespread use internationally. It is based on a symmetric-key algorithm that uses a 56-bit key. The algorithm was initially controversial with classified design elements, a relatively short key length, and suspicions about a National Security Agency (NSA) backdoor. DES consequently came under intense academic scrutiny which motivated the modern understanding of block ciphers and their cryptanalysis.<sup>[<a id="id2921548" href="#ftn.id2921548" class="footnote">18</a>]</sup>
+ </div><div class="section" title="A.1.2.1. DES Uses"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="id2868551">A.1.2.1. DES Uses</h4></div></div></div><div class="para">
+ </div></div><div class="section" title="A.1.2.2. DES History"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="id2698706">A.1.2.2. DES History</h4></div></div></div><div class="para">
+ DES is now considered to be insecure for many applications. This is chiefly due to the 56-bit key size being too small; in January, 1999, distributed.net and the Electronic Frontier Foundation collaborated to publicly break a DES key in 22 hours and 15 minutes (see chronology). There are also some analytical results which demonstrate theoretical weaknesses in the cipher, although they are unfeasible to mount in practice. The algorithm is believed to be practically secure in the form of Triple DES, although there are theoretical attacks. In recent years, the cipher has been superseded by the Advanced Encryption Standard (AES).<sup>[<a id="id3003419" href="#ftn.id3003419" class="footnote">19</a>]</sup>
</div><div class="para">
- In some documentation, a distinction is made between DES as a standard and DES the algorithm which is referred to as the DEA (the Data Encryption Algorithm). When spoken, "DES" is either spelled out as an abbreviation (/ËŒdiËËŒiËˈɛs/), or pronounced as a one-syllable acronym (/ˈdÉ›z/).<sup>[<a id="id3185367" href="#ftn.id3185367" class="footnote">20</a>]</sup>
- </div></div></div></div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id4402321" href="#id4402321" class="para">15</a>] </sup>
+ In some documentation, a distinction is made between DES as a standard and DES the algorithm which is referred to as the DEA (the Data Encryption Algorithm). When spoken, "DES" is either spelled out as an abbreviation (/ËŒdiËËŒiËˈɛs/), or pronounced as a one-syllable acronym (/ˈdÉ›z/).<sup>[<a id="id2842147" href="#ftn.id2842147" class="footnote">20</a>]</sup>
+ </div></div></div></div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id2758744" href="#id2758744" class="para">15</a>] </sup>
"Advanced Encryption Standard." <span class="emphasis"><em>Wikipedia.</em></span> 14 November 2009 <a href="http://en.wikipedia.org/wiki/Advanced_Encryption_Standard">http://en.wikipedia.org/wiki/Advanced_Encryption_Standard</a>
- </p></div><div class="footnote"><p><sup>[<a id="ftn.id3466628" href="#id3466628" class="para">16</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id2993158" href="#id2993158" class="para">16</a>] </sup>
"Advanced Encryption Standard." <span class="emphasis"><em>Wikipedia.</em></span> 14 November 2009 <a href="http://en.wikipedia.org/wiki/Advanced_Encryption_Standard">http://en.wikipedia.org/wiki/Advanced_Encryption_Standard</a>
- </p></div><div class="footnote"><p><sup>[<a id="ftn.id3132579" href="#id3132579" class="para">17</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id2657664" href="#id2657664" class="para">17</a>] </sup>
"Advanced Encryption Standard." <span class="emphasis"><em>Wikipedia.</em></span> 14 November 2009 <a href="http://en.wikipedia.org/wiki/Advanced_Encryption_Standard">http://en.wikipedia.org/wiki/Advanced_Encryption_Standard</a>
- </p></div><div class="footnote"><p><sup>[<a id="ftn.id3272416" href="#id3272416" class="para">18</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id2921548" href="#id2921548" class="para">18</a>] </sup>
"Data Encryption Standard." <span class="emphasis"><em>Wikipedia.</em></span> 14 November 2009 <a href="http://en.wikipedia.org/wiki/Data_Encryption_Standard">http://en.wikipedia.org/wiki/Data_Encryption_Standard</a>
- </p></div><div class="footnote"><p><sup>[<a id="ftn.id3259210" href="#id3259210" class="para">19</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id3003419" href="#id3003419" class="para">19</a>] </sup>
"Data Encryption Standard." <span class="emphasis"><em>Wikipedia.</em></span> 14 November 2009 <a href="http://en.wikipedia.org/wiki/Data_Encryption_Standard">http://en.wikipedia.org/wiki/Data_Encryption_Standard</a>
- </p></div><div class="footnote"><p><sup>[<a id="ftn.id3185367" href="#id3185367" class="para">20</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id2842147" href="#id2842147" class="para">20</a>] </sup>
"Data Encryption Standard." <span class="emphasis"><em>Wikipedia.</em></span> 14 November 2009 <a href="http://en.wikipedia.org/wiki/Data_Encryption_Standard">http://en.wikipedia.org/wiki/Data_Encryption_Standard</a>
</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security_Guide-References.html"><strong>Prev</strong>Chapter 7. References</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="apas02.html"><strong>Next</strong>A.2. Public-key Encryption</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/chap-Security_Guide-General_Principles_of_Information_Security.html b/public_html/en-US/Fedora/13/html/Security_Guide/chap-Security_Guide-General_Principles_of_Information_Security.html
index 7254bb9..acf7509 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/chap-Security_Guide-General_Principles_of_Information_Security.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/chap-Security_Guide-General_Principles_of_Information_Security.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 4. General Principles of Information Security</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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.7. About Public Key Encryption" /><link rel="next" href="chap-Security_Guide-Secure_Installation.html" title="Chapter 5. Secure Installation" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an if
rame, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Encryption-Using_GPG-About_Public_Key_Encryption.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Security_Guide-Secure_Installation.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 4. General Principles of Information Security" id="chap-Security_Guide-General_Principles_of_Information_Security" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 4. General Principles of Information Security</h2></div></div></div><div class="toc"><dl><dt><span cl
ass="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. Tips, Guides, and Tools</a></span></dt></dl></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 4. General Principles of Information Security</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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.7. About Public Key Encryption" /><link rel="next" href="chap-Security_Guide-Secure_Installation.html" title="Chapter 5. Secure Installation" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an ifr
ame, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Encryption-Using_GPG-About_Public_Key_Encryption.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Security_Guide-Secure_Installation.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 4. General Principles of Information Security" id="chap-Security_Guide-General_Principles_of_Information_Security" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 4. General Principles of Information Security</h2></div></div></div><div class="toc"><dl><dt><span cla
ss="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. Tips, Guides, and Tools</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 class="listitem"><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.
@@ -16,7 +16,7 @@
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 class="listitem"><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" title="4.1. Tips, Guides, and Tools" id="sect-Security_Guide-General_Principles_of_Information_Security-Tips_Guides_and_Tools"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.1. Tips, Guides, and Tools</h2></div></div></div><div class="para">
+ </div></li></ul></div><div class="section" title="4.1. Tips, Guides, and Tools" id="sect-Security_Guide-General_Principles_of_Information_Security-Tips_Guides_and_Tools"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sect-Security_Guide-General_Principles_of_Information_Security-Tips_Guides_and_Tools">4.1. Tips, Guides, and Tools</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 class="listitem"><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>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/chap-Security_Guide-References.html b/public_html/en-US/Fedora/13/html/Security_Guide/chap-Security_Guide-References.html
index e98ef2b..2ee5d63 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/chap-Security_Guide-References.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/chap-Security_Guide-References.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 7. References</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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" /><link rel="next" href="chap-Security_Guide-Encryption_Standards.html" title="Appendix A. Encryption Standards" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.
html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Software_Maintenance-Install_Signed_Packages_from_Well_Known_Repositories.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Security_Guide-Encryption_Standards.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 7. References" id="chap-Security_Guide-References" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 7. References</h2></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 7. References</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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" /><link rel="next" href="chap-Security_Guide-Encryption_Standards.html" title="Appendix A. Encryption Standards" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.h
tml">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Software_Maintenance-Install_Signed_Packages_from_Well_Known_Repositories.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Security_Guide-Encryption_Standards.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 7. References" id="chap-Security_Guide-References" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 7. References</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" title="Books" id="vari-Security_Guide-References-Books"><h6>Books</h6><dl><dt><span class="term">SELinux by Example</span></dt><dd><div class="para">
Mayer, MacMillan, and Caplan
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/chap-Security_Guide-Secure_Installation.html b/public_html/en-US/Fedora/13/html/Security_Guide/chap-Security_Guide-Secure_Installation.html
index 7c1897c..c59288f 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/chap-Security_Guide-Secure_Installation.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/chap-Security_Guide-Secure_Installation.html
@@ -1,8 +1,8 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 5. Secure Installation</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="Chapter 4. General Principles of Information Security" /><link rel="next" href="sect-Security_Guide-Secure_Installation-Utilize_LUKS_Partition_Encryption.html" title="5.2. Utilize LUKS Partition Encryption" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../
../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security_Guide-General_Principles_of_Information_Security.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Secure_Installation-Utilize_LUKS_Partition_Encryption.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 5. Secure Installation" id="chap-Security_Guide-Secure_Installation" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 5. Secure Installation</h2></div></div></div><div class="toc"><dl><dt><span class="sect
ion"><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></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 5. Secure Installation</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="Chapter 4. General Principles of Information Security" /><link rel="next" href="sect-Security_Guide-Secure_Installation-Utilize_LUKS_Partition_Encryption.html" title="5.2. Utilize LUKS Partition Encryption" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../.
./../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security_Guide-General_Principles_of_Information_Security.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Secure_Installation-Utilize_LUKS_Partition_Encryption.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 5. Secure Installation" id="chap-Security_Guide-Secure_Installation" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 5. Secure Installation</h2></div></div></div><div class="toc"><dl><dt><span class="secti
on"><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></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" title="5.1. Disk Partitions" id="sect-Security_Guide-Secure_Installation-Disk_Partitions"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.1. Disk Partitions</h2></div></div></div><div class="para">
+ </div><div class="section" title="5.1. Disk Partitions" id="sect-Security_Guide-Secure_Installation-Disk_Partitions"><div class="titlepage"><div><div keep-together.within-column="always"><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.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/chap-Security_Guide-Securing_Your_Network.html b/public_html/en-US/Fedora/13/html/Security_Guide/chap-Security_Guide-Securing_Your_Network.html
index 5756e91..a92641f 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/chap-Security_Guide-Securing_Your_Network.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/chap-Security_Guide-Securing_Your_Network.html
@@ -1,8 +1,8 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 2. Securing Your Network</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable ifram
e display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Updating_Packages-Applying_the_Changes.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Server_Security.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 2. Securing Your Network" id="chap-Security_Guide-Securing_Your_Network" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 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 S
ecurity</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_Network.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. Availabl
e Network Services</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. Personal Firewalls</a></span></dt><dt><span class="section"><a href="chap-Security_Guide-Securing_Your_Network.html#sect-Security_Guide-Workstation_Security-Security_Enhanced_Communication_Tools">2.1.7. Security Enhanced Communication Tools</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Security_Guide-Server_Security.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-S
erver_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. Introduction</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="section"><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 cla
ss="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_a
nd_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_Guid
e-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-Additional_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. What is 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_a
nd_PAM.html">2.6.4. Kerberos and 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. Setting Up Cross Realm Authentication</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 Does 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 <abbr class="abbrev">IPsec</abbr> 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-Secu
rity_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 <abbr class="abbrev">IPsec</abbr> 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 and IPTables</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Firewalls-Basic_Firewall_Configuration.html">2.8.2. Basic Firewall Configuration</a></span></dt
><dt><span class="section"><a href="sect-Security_Guide-Firewalls-Using_IPTables.html">2.8.3. Using IPTables</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Firewalls-Common_IPTables_Filtering.html">2.8.4. Common IPTables Filtering</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Firewalls-FORWARD_and_NAT_Rules.html">2.8.5. <code class="computeroutput">FORWARD</code> and <acronym class="acronym">NAT</acronym> Rules</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Firewalls-Malicious_Software_and_Spoofed_IP_Addresses.html">2.8.6. Malicious Software and Spoofed IP Addresses</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Firewalls-IPTables_and_Connection_Tracking.html">2.8.7. IPTables and Connection Tracking</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-Addi
tional_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. Packet Filtering</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-IPTables-Command_Options_for_IPTables.html">2.9.2. Command Options for IPTables</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-IPTables-Saving_IPTables_Rules.html">2.9.3. Saving IPTables Rules</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-IPTables-IPTables_Control_Scripts.html">2.9.4. IPTables Control Scripts</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-IPTables-IPTables_and_IPv6.html">2.9.5. IPTables and IPv6</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-IPTables-Additional_Resources.html">2.9.
6. Additional Resources</a></span></dt></dl></dd></dl></div><div xml:lang="en-US" class="section" title="2.1. Workstation Security" id="sect-Security_Guide-Workstation_Security" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.1. Workstation Security</h2></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 2. Securing Your Network</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe
display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Updating_Packages-Applying_the_Changes.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Server_Security.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 2. Securing Your Network" id="chap-Security_Guide-Securing_Your_Network" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 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 Se
curity</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_Network.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. Available
Network Services</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. Personal Firewalls</a></span></dt><dt><span class="section"><a href="chap-Security_Guide-Securing_Your_Network.html#sect-Security_Guide-Workstation_Security-Security_Enhanced_Communication_Tools">2.1.7. Security Enhanced Communication Tools</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Security_Guide-Server_Security.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-Se
rver_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_S
ign_on_SSO.html#sect-Security_Guide-Single_Sign_on_SSO-Introduction">2.3.1. Introduction</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="section"><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 clas
s="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_an
d_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-Additional_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. What is 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_an
d_PAM.html">2.6.4. Kerberos and 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. Setting Up Cross Realm Authentication</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 Does 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 <abbr class="abbrev">IPsec</abbr> 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-Secur
ity_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 <abbr class="abbrev">IPsec</abbr> 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 and IPTables</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Firewalls-Basic_Firewall_Configuration.html">2.8.2. Basic Firewall Configuration</a></span></dt>
<dt><span class="section"><a href="sect-Security_Guide-Firewalls-Using_IPTables.html">2.8.3. Using IPTables</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Firewalls-Common_IPTables_Filtering.html">2.8.4. Common IPTables Filtering</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Firewalls-FORWARD_and_NAT_Rules.html">2.8.5. <code class="computeroutput">FORWARD</code> and <acronym class="acronym">NAT</acronym> Rules</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Firewalls-Malicious_Software_and_Spoofed_IP_Addresses.html">2.8.6. Malicious Software and Spoofed IP Addresses</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Firewalls-IPTables_and_Connection_Tracking.html">2.8.7. IPTables and Connection Tracking</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-Addit
ional_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. Packet Filtering</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-IPTables-Command_Options_for_IPTables.html">2.9.2. Command Options for IPTables</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-IPTables-Saving_IPTables_Rules.html">2.9.3. Saving IPTables Rules</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-IPTables-IPTables_Control_Scripts.html">2.9.4. IPTables Control Scripts</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-IPTables-IPTables_and_IPv6.html">2.9.5. IPTables and IPv6</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-IPTables-Additional_Resources.html">2.9.6
. Additional Resources</a></span></dt></dl></dd></dl></div><div xml:lang="en-US" class="section" title="2.1. Workstation Security" id="sect-Security_Guide-Workstation_Security" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sect-Security_Guide-Workstation_Security">2.1. Workstation 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" title="2.1.1. Evaluating Workstation Security" id="sect-Security_Guide-Workstation_Security-Evaluating_Workstation_Security"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.1.1. Evaluating Workstation Security</h3></div></div></div><div class="para">
+ </div><div class="section" title="2.1.1. Evaluating Workstation Security" id="sect-Security_Guide-Workstation_Security-Evaluating_Workstation_Security"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><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?
@@ -16,14 +16,14 @@
<span class="emphasis"><em>Personal Firewalls</em></span> — What type of firewall, if any, is necessary?
</div></li><li class="listitem"><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" title="2.1.2. BIOS and Boot Loader Security" id="sect-Security_Guide-Workstation_Security-BIOS_and_Boot_Loader_Security"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.1.2. BIOS and Boot Loader Security</h3></div></div></div><div class="para">
+ </div></li></ul></div></div><div class="section" title="2.1.2. BIOS and Boot Loader Security" id="sect-Security_Guide-Workstation_Security-BIOS_and_Boot_Loader_Security"><div class="titlepage"><div><div keep-together.within-column="always"><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" title="2.1.2.1. BIOS Passwords" id="sect-Security_Guide-BIOS_and_Boot_Loader_Security-BIOS_Passwords"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.1.2.1. BIOS Passwords</h4></div></div></div><div class="para">
- The two primary reasons for password protecting the BIOS of a computer are<sup>[<a id="id3151297" href="#ftn.id3151297" class="footnote">11</a>]</sup>:
+ </div><div class="section" title="2.1.2.1. BIOS Passwords" id="sect-Security_Guide-BIOS_and_Boot_Loader_Security-BIOS_Passwords"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-BIOS_and_Boot_Loader_Security-BIOS_Passwords">2.1.2.1. BIOS Passwords</h4></div></div></div><div class="para">
+ The two primary reasons for password protecting the BIOS of a computer are<sup>[<a id="id2724355" href="#ftn.id2724355" class="footnote">11</a>]</sup>:
</div><div class="orderedlist"><ol><li class="listitem"><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 class="listitem"><div class="para">
@@ -32,11 +32,11 @@
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" title="2.1.2.1.1. Securing Non-x86 Platforms" id="sect-Security_Guide-BIOS_Passwords-Securing_Non_x86_Platforms"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.1.2.1.1. Securing Non-x86 Platforms</h5></div></div></div><div class="para">
+ </div><div class="section" title="2.1.2.1.1. Securing Non-x86 Platforms" id="sect-Security_Guide-BIOS_Passwords-Securing_Non_x86_Platforms"><div class="titlepage"><div><div keep-together.within-column="always"><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" title="2.1.2.2. Boot Loader Passwords" id="sect-Security_Guide-BIOS_and_Boot_Loader_Security-Boot_Loader_Passwords"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.1.2.2. Boot Loader Passwords</h4></div></div></div><div class="para">
+ </div></div></div><div class="section" title="2.1.2.2. Boot Loader Passwords" id="sect-Security_Guide-BIOS_and_Boot_Loader_Security-Boot_Loader_Passwords"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><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.
@@ -46,16 +46,14 @@
<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" title="2.1.2.2.1. Password Protecting GRUB" id="sect-Security_Guide-Boot_Loader_Passwords-Password_Protecting_GRUB"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.1.2.2.1. Password Protecting GRUB</h5></div></div></div><div class="para">
+ </div><div class="section" title="2.1.2.2.1. Password Protecting GRUB" id="sect-Security_Guide-Boot_Loader_Passwords-Password_Protecting_GRUB"><div class="titlepage"><div><div keep-together.within-column="always"><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">Section 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">
+ </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="id3312778" href="#ftn.id3312778" class="footnote">12</a>]</sup>.
+ </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="id2650084" href="#ftn.id2650084" 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">
@@ -64,15 +62,13 @@
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">
+ </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" title="2.1.3. Password Security" id="sect-Security_Guide-Workstation_Security-Password_Security"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.1.3. Password Security</h3></div></div></div><div class="para">
+ </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" title="2.1.3. Password Security" id="sect-Security_Guide-Workstation_Security-Password_Security"><div class="titlepage"><div><div keep-together.within-column="always"><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.
@@ -86,7 +82,7 @@
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" title="2.1.3.1. Creating Strong Passwords" id="sect-Security_Guide-Password_Security-Creating_Strong_Passwords"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.1.3.1. Creating Strong Passwords</h4></div></div></div><div class="para">
+ </div><div class="section" title="2.1.3.1. Creating Strong Passwords" id="sect-Security_Guide-Password_Security-Creating_Strong_Passwords"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><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.
@@ -168,7 +164,7 @@
<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" title="2.1.3.1.1. Secure Password Creation Methodology" id="sect-Security_Guide-Creating_Strong_Passwords-Secure_Password_Creation_Methodology"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.1.3.1.1. Secure Password Creation Methodology</h5></div></div></div><div class="para">
+ </div><div class="section" title="2.1.3.1.1. Secure Password Creation Methodology" id="sect-Security_Guide-Creating_Strong_Passwords-Secure_Password_Creation_Methodology"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-Security_Guide-Creating_Strong_Passwords-Secure_Password_Creation_Methodology">2.1.3.1.1. Secure Password Creation Methodology</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 class="listitem"><div class="para">
Think of an easily-remembered phrase, such as:
@@ -190,13 +186,13 @@
<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" title="2.1.3.2. Creating User Passwords Within an Organization" id="sect-Security_Guide-Password_Security-Creating_User_Passwords_Within_an_Organization"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.1.3.2. Creating User Passwords Within an Organization</h4></div></div></div><div class="para">
+ </div></div></div><div class="section" title="2.1.3.2. Creating User Passwords Within an Organization" id="sect-Security_Guide-Password_Security-Creating_User_Passwords_Within_an_Organization"><div class="titlepage"><div><div keep-together.within-column="always"><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" title="2.1.3.2.1. Forcing Strong Passwords" id="sect-Security_Guide-Creating_User_Passwords_Within_an_Organization-Forcing_Strong_Passwords"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.1.3.2.1. Forcing Strong Passwords</h5></div></div></div><div class="para">
+ </div><div class="section" title="2.1.3.2.1. Forcing Strong Passwords" id="sect-Security_Guide-Creating_User_Passwords_Within_an_Organization-Forcing_Strong_Passwords"><div class="titlepage"><div><div keep-together.within-column="always"><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/mo
dules.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)">Section 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.
@@ -210,21 +206,19 @@
<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" title="2.1.3.2.2. Passphrases" id="sect-Security_Guide-Passphrases"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.1.3.2.2. Passphrases</h5></div></div></div><div class="para">
+ </div></div></div><div class="section" title="2.1.3.2.2. Passphrases" id="sect-Security_Guide-Passphrases"><div class="titlepage"><div><div keep-together.within-column="always"><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. 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" title="2.1.3.2.3. Password Aging" id="sect-Security_Guide-Creating_User_Passwords_Within_an_Organization-Password_Aging"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.1.3.2.3. Password Aging</h5></div></div></div><div class="para">
+ </div></div><div class="section" title="2.1.3.2.3. Password Aging" id="sect-Security_Guide-Creating_User_Passwords_Within_an_Organization-Password_Aging"><div class="titlepage"><div><div keep-together.within-column="always"><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">
+ </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">
+ </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 myServer ~]# chage davido
Changing the aging information for davido
@@ -235,8 +229,7 @@ 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 myServer ~]#
-</pre><div class="para">
+[root at myServer ~]#</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.
@@ -250,16 +243,15 @@ Account Expiration Date (YYYY-MM-DD) [1969-12-31]:
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 class="step" title="Step 5"><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"><div class="figure-contents"><div class="mediaobject"><img src="images/fed-user_pass_info.png" width="444" alt="Specifying password aging options" /><div class="longdesc"><div class="para">
+ </div></li></ol></div><div class="figure" title="Figure 2.1. Specifying password aging options" 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" width="444" 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>Figure 2.1. Specifying password aging options</h6></div><br class="figure-break" /></div></div></div><div class="section" title="2.1.4. Administrative Controls" id="sect-Security_Guide-Workstation_Security-Administrative_Controls"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.1.4. Administrative Controls</h3></div></div></div><div class="para">
+ </div></div></div></div><h6>Figure 2.1. Specifying password aging options</h6></div><br class="figure-break" /></div></div></div><div class="section" title="2.1.4. Administrative Controls" id="sect-Security_Guide-Workstation_Security-Administrative_Controls"><div class="titlepage"><div><div keep-together.within-column="always"><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">
+ </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)">Section 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 user
s on their network should receive.
- </div><div class="section" title="2.1.4.1. Allowing Root Access" id="sect-Security_Guide-Administrative_Controls-Allowing_Root_Access"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.1.4.1. Allowing Root Access</h4></div></div></div><div class="para">
+ </div><div class="section" title="2.1.4.1. Allowing Root Access" id="sect-Security_Guide-Administrative_Controls-Allowing_Root_Access"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Administrative_Controls-Allowing_Root_Access">2.1.4.1. Allowing Root Access</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:
@@ -269,11 +261,11 @@ Account Expiration Date (YYYY-MM-DD) [1969-12-31]:
<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 class="listitem"><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" title="2.1.4.2. Disallowing Root Access" id="sect-Security_Guide-Administrative_Controls-Disallowing_Root_Access"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.1.4.2. Disallowing Root Access</h4></div></div></div><div class="para">
+ </div></li></ul></div></div><div class="section" title="2.1.4.2. Disallowing Root Access" id="sect-Security_Guide-Administrative_Controls-Disallowing_Root_Access"><div class="titlepage"><div><div keep-together.within-column="always"><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">Section 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="Table 2.1. Methods of Disabling the Root Account">Table 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"><div class="table-contents"><table summary="Methods of Disabling the Root Account" border="1"><colgroup><col width="12%" /><col width="29%" /><col width="29%" /><col width="29%" /></colgroup><thead><tr><th>
+ </div><div class="table" title="Table 2.1. Methods of Disabling the Root Account" 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 width="12%" /><col width="29%" /><col width="29%" /><col width="29%" /></colgroup><thead><tr><th>
Method
</th><th>
Description
@@ -314,55 +306,49 @@ Account Expiration Date (YYYY-MM-DD) [1969-12-31]:
</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="id3374456" href="#ftn.id3374456" class="footnote">a</a>]</sup>
+ 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="id2888345" href="#ftn.id2888345" class="footnote">a</a>]</sup>
</td><td>
<table border="0" summary="Simple list" class="simplelist"><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 border="0" summary="Simple list" class="simplelist"><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.id3374456" href="#id3374456" class="para">a</a>] </sup>
+ </td></tr></tbody><tbody class="footnotes"><tr><td colspan="4"><div class="footnote"><p><sup>[<a id="ftn.id2888345" href="#id2888345" 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. Disabling Root Using PAM">Section 2.1.4.2.4, “Disabling Root Using PAMâ€</a> for details.
- </p></div></td></tr></tbody></table></div><h6>Table 2.1. Methods of Disabling the Root Account</h6></div><br class="table-break" /><div class="section" title="2.1.4.2.1. Disabling the Root Shell" id="sect-Security_Guide-Disallowing_Root_Access-Disabling_the_Root_Shell"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.1.4.2.1. Disabling the Root Shell</h5></div></div></div><div class="para">
+ </p></div></td></tr></tbody></table></div><h6>Table 2.1. Methods of Disabling the Root Account</h6></div><br class="table-break" /><div class="section" title="2.1.4.2.1. Disabling the Root Shell" id="sect-Security_Guide-Disallowing_Root_Access-Disabling_the_Root_Shell"><div class="titlepage"><div><div keep-together.within-column="always"><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" title="2.1.4.2.2. Disabling Root Logins" id="sect-Security_Guide-Disallowing_Root_Access-Disabling_Root_Logins"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.1.4.2.2. Disabling Root Logins</h5></div></div></div><div class="para">
+ </div></div></div><div class="section" title="2.1.4.2.2. Disabling Root Logins" id="sect-Security_Guide-Disallowing_Root_Access-Disabling_Root_Logins"><div class="titlepage"><div><div keep-together.within-column="always"><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">
+ </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" title="2.1.4.2.3. Disabling Root SSH Logins" id="sect-Security_Guide-Disallowing_Root_Access-Disabling_Root_SSH_Logins"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.1.4.2.3. Disabling Root SSH Logins</h5></div></div></div><div class="para">
+ </div></div></div><div class="section" title="2.1.4.2.3. Disabling Root SSH Logins" id="sect-Security_Guide-Disallowing_Root_Access-Disabling_Root_SSH_Logins"><div class="titlepage"><div><div keep-together.within-column="always"><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">
+ </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">
+ </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" title="2.1.4.2.4. Disabling Root Using PAM" id="sect-Security_Guide-Disallowing_Root_Access-Disabling_Root_Using_PAM"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.1.4.2.4. Disabling Root Using PAM</h5></div></div></div><div class="para">
+ </div><pre class="screen"><code class="computeroutput">kill -HUP `cat /var/run/sshd.pid`</code></pre></div><div class="section" title="2.1.4.2.4. Disabling Root Using PAM" id="sect-Security_Guide-Disallowing_Root_Access-Disabling_Root_Using_PAM"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-Security_Guide-Disallowing_Root_Access-Disabling_Root_Using_PAM">2.1.4.2.4. Disabling Root Using 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">
+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)">Section 2.4, “Pluggable Authentication Modules (PAM)â€</a>.
- </div></div></div><div class="section" title="2.1.4.3. Limiting Root Access" id="sect-Security_Guide-Administrative_Controls-Limiting_Root_Access"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.1.4.3. Limiting Root Access</h4></div></div></div><div class="para">
+ </div></div></div><div class="section" title="2.1.4.3. Limiting Root Access" id="sect-Security_Guide-Administrative_Controls-Limiting_Root_Access"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Administrative_Controls-Limiting_Root_Access">2.1.4.3. Limiting Root Access</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" title="2.1.4.3.1. The su Command" id="sect-Security_Guide-Limiting_Root_Access-The_su_Command"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.1.4.3.1. The <code class="command">su</code> Command</h5></div></div></div><div class="para">
+ </div><div class="section" title="2.1.4.3.1. The su Command" id="sect-Security_Guide-Limiting_Root_Access-The_su_Command"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-Security_Guide-Limiting_Root_Access-The_su_Command">2.1.4.3.1. The <code class="command">su</code> Command</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="id3176012" href="#ftn.id3176012" 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.
+ 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="id2881253" href="#ftn.id2881253" 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><username></code></em></code>
-</pre><div class="para">
+ </div><pre class="screen"><code class="command">usermod -G wheel <em class="replaceable"><code><username></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.
@@ -376,19 +362,17 @@ sense=deny file=/etc/vsftpd.ftpusers onerr=succeed
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="Figure 2.2. Adding users to the "wheel" group.">Figure 2.2, “Adding users to the "wheel" group.â€</a>.
</div></li><li class="step" title="Step 5"><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">
+ </div><pre class="screen">auth required /lib/security/$ISA/pam_wheel.so use_uid</pre><div class="para">
This change means that only members of the administrative group <code class="computeroutput">wheel</code> can use this program.
- </div></li></ol></div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/fed-user_pass_groups.png" width="444" alt="Adding users to the "wheel" group." /><div class="longdesc"><div class="para">
+ </div></li></ol></div><div class="figure" title="Figure 2.2. Adding users to the "wheel" group." 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" width="444" alt="Adding users to the "wheel" group." /><div class="longdesc"><div class="para">
<span class="guilabel"><strong>Groups</strong></span> pane illustration
</div></div></div></div><h6>Figure 2.2. Adding users to the "wheel" group.</h6></div><br class="figure-break" /><div class="note"><h2>Note</h2><div class="para">
The root user is part of the <code class="computeroutput">wheel</code> group by default.
- </div></div></div><div class="section" title="2.1.4.3.2. The sudo Command" id="sect-Security_Guide-Limiting_Root_Access-The_sudo_Command"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.1.4.3.2. The <code class="command">sudo</code> Command</h5></div></div></div><div class="para">
+ </div></div></div><div class="section" title="2.1.4.3.2. The sudo Command" id="sect-Security_Guide-Limiting_Root_Access-The_sudo_Command"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-Security_Guide-Limiting_Root_Access-The_sudo_Command">2.1.4.3.2. The <code class="command">sudo</code> Command</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">
The basic format of the <code class="command">sudo</code> command is as follows:
- </div><pre class="screen"><code class="command">sudo <em class="replaceable"><code><command></code></em></code>
-</pre><div class="para">
+ </div><pre class="screen"><code class="command">sudo <em class="replaceable"><code><command></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>.
@@ -402,21 +386,19 @@ sense=deny file=/etc/vsftpd.ftpusers onerr=succeed
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">
+ </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">
+ </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" title="2.1.5. Available Network Services" id="sect-Security_Guide-Workstation_Security-Available_Network_Services"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.1.5. Available Network Services</h3></div></div></div><div class="para">
+ </div></div></div></div><div class="section" title="2.1.5. Available Network Services" id="sect-Security_Guide-Workstation_Security-Available_Network_Services"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Workstation_Security-Available_Network_Services">2.1.5. Available Network Services</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" title="2.1.5.1. Risks To Services" id="sect-Security_Guide-Available_Network_Services-Risks_To_Services"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.1.5.1. Risks To Services</h4></div></div></div><div class="para">
+ </div><div class="section" title="2.1.5.1. Risks To Services" id="sect-Security_Guide-Available_Network_Services-Risks_To_Services"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Available_Network_Services-Risks_To_Services">2.1.5.1. Risks To Services</h4></div></div></div><div class="para">
Network services can pose many risks for Linux systems. Below is a list of some of the primary issues:
</div><div class="itemizedlist"><ul><li class="listitem"><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.
@@ -432,7 +414,7 @@ sense=deny file=/etc/vsftpd.ftpusers onerr=succeed
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">
To limit exposure to attacks over the network, all services that are unused should be turned off.
- </div></div></div><div class="section" title="2.1.5.2. Identifying and Configuring Services" id="sect-Security_Guide-Available_Network_Services-Identifying_and_Configuring_Services"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.1.5.2. Identifying and Configuring Services</h4></div></div></div><div class="para">
+ </div></div></div><div class="section" title="2.1.5.2. Identifying and Configuring Services" id="sect-Security_Guide-Available_Network_Services-Identifying_and_Configuring_Services"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Available_Network_Services-Identifying_and_Configuring_Services">2.1.5.2. Identifying and Configuring Services</h4></div></div></div><div class="para">
To enhance security, most network services installed with Fedora are turned off by default. There are, however, some notable exceptions:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="command">cupsd</code> — The default print server for Fedora.
@@ -446,13 +428,13 @@ sense=deny file=/etc/vsftpd.ftpusers onerr=succeed
<code class="command">sshd</code> — The OpenSSH server, which is a secure replacement for 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"><div class="figure-contents"><div class="mediaobject"><img src="images/fed-service_config.png" width="444" alt="Services Configuration Tool" /><div class="longdesc"><div class="para">
+ </div><div class="figure" title="Figure 2.3. Services Configuration Tool" 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" width="444" alt="Services Configuration Tool" /><div class="longdesc"><div class="para">
<span class="application"><strong>Services Configuration Tool</strong></span> illustration
</div></div></div></div><h6>Figure 2.3. <span class="application">Services Configuration Tool</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="Figure 2.3. Services Configuration Tool">Figure 2.3, “<span class="application">Services Configuration Tool</span>â€</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">Section 2.2.8, “Verifying Which Ports Are Listeningâ€</a> for more information.
- </div></div><div class="section" title="2.1.5.3. Insecure Services" id="sect-Security_Guide-Available_Network_Services-Insecure_Services"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.1.5.3. Insecure Services</h4></div></div></div><div class="para">
+ </div></div><div class="section" title="2.1.5.3. Insecure Services" id="sect-Security_Guide-Available_Network_Services-Insecure_Services"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Available_Network_Services-Insecure_Services">2.1.5.3. Insecure Services</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. Security Updates">Section 1.5, “Security Updatesâ€</a> for more information.
</div><div class="para">
Some network protocols are inherently more insecure than others. These include any services that:
@@ -498,7 +480,7 @@ sense=deny file=/etc/vsftpd.ftpusers onerr=succeed
More information on securing network services is available in <a class="xref" href="sect-Security_Guide-Server_Security.html" title="2.2. Server Security">Section 2.2, “Server Securityâ€</a>.
</div><div class="para">
The next section discusses tools available to set up a simple firewall.
- </div></div></div><div class="section" title="2.1.6. Personal Firewalls" id="sect-Security_Guide-Workstation_Security-Personal_Firewalls"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.1.6. Personal Firewalls</h3></div></div></div><div class="para">
+ </div></div></div><div class="section" title="2.1.6. Personal Firewalls" id="sect-Security_Guide-Workstation_Security-Personal_Firewalls"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Workstation_Security-Personal_Firewalls">2.1.6. Personal Firewalls</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.
@@ -510,7 +492,7 @@ sense=deny file=/etc/vsftpd.ftpusers onerr=succeed
Refer to <a class="xref" href="sect-Security_Guide-Firewalls-Basic_Firewall_Configuration.html" title="2.8.2. Basic Firewall Configuration">Section 2.8.2, “Basic Firewall Configurationâ€</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">Section 2.8, “Firewallsâ€</a> for more information. Refer to <a class="xref" href="sect-Security_Guide-IPTables.html" title="2.9. IPTables">Section 2.9, “IPTablesâ€</a> for a comprehensive guide to the <code class="command">iptables</code> command.
- </div></div><div class="section" title="2.1.7. Security Enhanced Communication Tools" id="sect-Security_Guide-Workstation_Security-Security_Enhanced_Communication_Tools"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.1.7. Security Enhanced Communication Tools</h3></div></div></div><div class="para">
+ </div></div><div class="section" title="2.1.7. Security Enhanced Communication Tools" id="sect-Security_Guide-Workstation_Security-Security_Enhanced_Communication_Tools"><div class="titlepage"><div><div keep-together.within-column="always"><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.
@@ -532,10 +514,10 @@ sense=deny file=/etc/vsftpd.ftpusers onerr=succeed
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. Security Updates">Section 1.5, “Security Updatesâ€</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.id3151297" href="#id3151297" class="para">11</a>] </sup>
+ </div></div></div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id2724355" href="#id2724355" 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.id3312778" href="#id3312778" class="para">12</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id2650084" href="#id2650084" 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.id3176012" href="#id3176012" class="para">13</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id2881253" href="#id2881253" 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>Prev</strong>1.5.4. Applying the Changes</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Server_Security.html"><strong>Next</strong>2.2. Server Security</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/chap-Security_Guide-Security_Overview.html b/public_html/en-US/Fedora/13/html/Security_Guide/chap-Security_Guide-Security_Overview.html
index 7bca94e..9d3daf2 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/chap-Security_Guide-Security_Overview.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/chap-Security_Guide-Security_Overview.html
@@ -1,33 +1,33 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 1. Security Overview</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. We Need Feedback!" /><link rel="next" href="sect-Security_Guide-Vulnerability_Assessment.html" title="1.2. Vulnerability Assessment" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="tit
le"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="We_Need_Feedback.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Vulnerability_Assessment.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 1. Security Overview" id="chap-Security_Guide-Security_Overview" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 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-Secur
ity_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. Conclusion</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. Thinking Lik
e the Enemy</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Vulnerability_Assessment-Defining_Assessment_and_Testing.html">1.2.2. Defining Assessment and Testing</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Vulnerability_Assessment-Evaluating_the_Tools.html">1.2.3. Evaluating the Tools</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. Common Exploits and Attacks</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Security_Updates.html">1.5. Security Updates</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. Install
ing 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">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 1. Security Overview</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. We Need Feedback!" /><link rel="next" href="sect-Security_Guide-Vulnerability_Assessment.html" title="1.2. Vulnerability Assessment" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="titl
e"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Vulnerability_Assessment.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 1. Security Overview" id="chap-Security_Guide-Security_Overview" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 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-Securi
ty_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. Conclusion</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. Thinking Like
the Enemy</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Vulnerability_Assessment-Defining_Assessment_and_Testing.html">1.2.2. Defining Assessment and Testing</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Vulnerability_Assessment-Evaluating_the_Tools.html">1.2.3. Evaluating the Tools</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. Common Exploits and Attacks</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Security_Updates.html">1.5. Security Updates</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. Installi
ng 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 postmortem — <span class="emphasis"><em>after</em></span> 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 xml:lang="en-US" class="section" title="1.1. Introduction to Security" id="sect-Security_Guide-Introduction_to_Security" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">1.1. Introduction to Security</h2></div></div></div><div class="section" title="1.1.1. What is Computer Security?" id="sect-Security_Guide-Introduction_to_Security-What_is_Computer_Security"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">1.1.1. What is Computer Security?</h3></div></div></div><div class="para">
+ </div><div xml:lang="en-US" class="section" title="1.1. Introduction to Security" id="sect-Security_Guide-Introduction_to_Security" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sect-Security_Guide-Introduction_to_Security">1.1. Introduction to Security</h2></div></div></div><div class="section" title="1.1.1. What is Computer Security?" id="sect-Security_Guide-Introduction_to_Security-What_is_Computer_Security"><div class="titlepage"><div><div keep-together.within-column="always"><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" title="1.1.1.1. How did Computer Security Come about?" id="sect-Security_Guide-What_is_Computer_Security-How_did_Computer_Security_Come_about"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">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="id3163660" href="#ftn.id3163660" class="footnote">1</a>]</sup>and the Vladimir Levin <sup>[<a id="id3175539" href="#ftn.id3175539" 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="section" title="1.1.1.1. How did Computer Security Come about?" id="sect-Security_Guide-What_is_Computer_Security-How_did_Computer_Security_Come_about"><div class="titlepage"><div><div keep-together.within-column="always"><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="id3905951" href="#ftn.id3905951" class="footnote">1</a>]</sup>and the Vladimir Levin <sup>[<a id="id2865703" href="#ftn.id2865703" 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" title="1.1.1.2. Security Today" id="sect-Security_Guide-What_is_Computer_Security-Security_Today"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">1.1.1.2. Security Today</h4></div></div></div><div class="para">
+ </div></div><div class="section" title="1.1.1.2. Security Today" id="sect-Security_Guide-What_is_Computer_Security-Security_Today"><div class="titlepage"><div><div keep-together.within-column="always"><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="id3265129" href="#ftn.id3265129" class="footnote">3</a>]</sup>
+ 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="id3022373" href="#ftn.id3022373" 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="id3135785" href="#ftn.id3135785" class="footnote">4</a>]</sup>
+ 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="id2888425" href="#ftn.id2888425" class="footnote">4</a>]</sup>
</div><div class="para">
- Currently, an estimated 1.8 billion people use or have used the Internet worldwide.<sup>[<a id="id3180511" href="#ftn.id3180511" class="footnote">5</a>]</sup> At the same time:
+ Currently, an estimated 1.8 billion people use or have used the Internet worldwide.<sup>[<a id="id2976013" href="#ftn.id2976013" class="footnote">5</a>]</sup> At the same time:
</div><div class="itemizedlist"><ul><li class="listitem"><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="id3440772" href="#ftn.id3440772" class="footnote">6</a>]</sup>
+ 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="id2828262" href="#ftn.id2828262" class="footnote">6</a>]</sup>
</div></li><li class="listitem"><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="id3344650" href="#ftn.id3344650" class="footnote">7</a>]</sup>
+ 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="id2800274" href="#ftn.id2800274" class="footnote">7</a>]</sup>
</div></li><li class="listitem"><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="id3361297" href="#ftn.id3361297" class="footnote">8</a>]</sup>
+ 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="id2844014" href="#ftn.id2844014" 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="id3218416" href="#ftn.id3218416" class="footnote">9</a>]</sup>, undertaken by <span class="emphasis"><em>CIO Magazine</em></span>, some points are:
+ From a 2008 global survey of business and technology executives "The Global State of Information Security"<sup>[<a id="id2798519" href="#ftn.id2798519" class="footnote">9</a>]</sup>, undertaken by <span class="emphasis"><em>CIO Magazine</em></span>, some points are:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
Just 43% of respondents audit or monitor user compliance with security policies
</div></li><li class="listitem"><div class="para">
@@ -42,7 +42,7 @@
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" title="1.1.1.3. Standardizing Security" id="sect-Security_Guide-What_is_Computer_Security-Standardizing_Security"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">1.1.1.3. Standardizing Security</h4></div></div></div><div class="para">
+ </div></div><div class="section" title="1.1.1.3. Standardizing Security" id="sect-Security_Guide-What_is_Computer_Security-Standardizing_Security"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><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.
@@ -50,9 +50,9 @@
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 class="listitem"><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" title="1.1.2. SELinux" id="sect-Security_Guide-Introduction_to_Security-SELinux"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">1.1.2. SELinux</h3></div></div></div><div class="para">
+ </div></li></ul></div></div></div><div class="section" title="1.1.2. SELinux" id="sect-Security_Guide-Introduction_to_Security-SELinux"><div class="titlepage"><div><div keep-together.within-column="always"><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/">http://docs.fedoraproject.org/</a>. For more information on configuring and running services in Fedora that are protected by SELinux, refer to the SELinux Managing Confined Services Guide available at <a href="http://docs.fedoraproject.org">http://docs.fedoraproject.org/</a>. Other available resources for SELinux are listed in <a class="xref" href="chap-Security_Guide-References.html" title="Chapter 7. References">Chapter 7, <i>References</i></a>.
- </div></div><div class="section" title="1.1.3. Security Controls" id="sect-Security_Guide-Introduction_to_Security-Security_Controls"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">1.1.3. Security Controls</h3></div></div></div><div class="para">
+ </div></div><div class="section" title="1.1.3. Security Controls" id="sect-Security_Guide-Introduction_to_Security-Security_Controls"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><div class="para">
Physical
@@ -62,7 +62,7 @@
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" title="1.1.3.1. Physical Controls" id="sect-Security_Guide-Security_Controls-Physical_Controls"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">1.1.3.1. Physical Controls</h4></div></div></div><div class="para">
+ </div><div class="section" title="1.1.3.1. Physical Controls" id="sect-Security_Guide-Security_Controls-Physical_Controls"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><div class="para">
Closed-circuit surveillance cameras
@@ -76,7 +76,7 @@
Locked and dead-bolted steel doors
</div></li><li class="listitem"><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" title="1.1.3.2. Technical Controls" id="sect-Security_Guide-Security_Controls-Technical_Controls"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">1.1.3.2. Technical Controls</h4></div></div></div><div class="para">
+ </div></li></ul></div></div><div class="section" title="1.1.3.2. Technical Controls" id="sect-Security_Guide-Security_Controls-Technical_Controls"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><div class="para">
Encryption
@@ -88,7 +88,7 @@
Access control lists (ACLs)
</div></li><li class="listitem"><div class="para">
File integrity auditing software
- </div></li></ul></div></div><div class="section" title="1.1.3.3. Administrative Controls" id="sect-Security_Guide-Security_Controls-Administrative_Controls"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">1.1.3.3. Administrative Controls</h4></div></div></div><div class="para">
+ </div></li></ul></div></div><div class="section" title="1.1.3.3. Administrative Controls" id="sect-Security_Guide-Security_Controls-Administrative_Controls"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><div class="para">
Training and awareness
@@ -98,24 +98,24 @@
Personnel recruitment and separation strategies
</div></li><li class="listitem"><div class="para">
Personnel registration and accounting
- </div></li></ul></div></div></div><div class="section" title="1.1.4. Conclusion" id="sect-Security_Guide-Introduction_to_Security-Conclusion"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">1.1.4. Conclusion</h3></div></div></div><div class="para">
+ </div></li></ul></div></div></div><div class="section" title="1.1.4. Conclusion" id="sect-Security_Guide-Introduction_to_Security-Conclusion"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Introduction_to_Security-Conclusion">1.1.4. Conclusion</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.id3163660" href="#id3163660" class="para">1</a>] </sup>
+ </div></div></div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id3905951" href="#id3905951" 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.id3175539" href="#id3175539" class="para">2</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id2865703" href="#id2865703" class="para">2</a>] </sup>
http://www.livinginternet.com/i/ia_hackers_levin.htm
- </p></div><div class="footnote"><p><sup>[<a id="ftn.id3265129" href="#id3265129" class="para">3</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id3022373" href="#id3022373" 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.id3135785" href="#id3135785" class="para">4</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id2888425" href="#id2888425" class="para">4</a>] </sup>
http://www.healthcareitnews.com/story.cms?id=9408
- </p></div><div class="footnote"><p><sup>[<a id="ftn.id3180511" href="#id3180511" class="para">5</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id2976013" href="#id2976013" class="para">5</a>] </sup>
http://www.internetworldstats.com/stats.htm
- </p></div><div class="footnote"><p><sup>[<a id="ftn.id3440772" href="#id3440772" class="para">6</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id2828262" href="#id2828262" class="para">6</a>] </sup>
http://www.cert.org
- </p></div><div class="footnote"><p><sup>[<a id="ftn.id3344650" href="#id3344650" class="para">7</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id2800274" href="#id2800274" class="para">7</a>] </sup>
http://www.cert.org/stats/fullstats.html
- </p></div><div class="footnote"><p><sup>[<a id="ftn.id3361297" href="#id3361297" class="para">8</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id2844014" href="#id2844014" class="para">8</a>] </sup>
http://www.newsfactor.com/perl/story/16407.html
- </p></div><div class="footnote"><p><sup>[<a id="ftn.id3218416" href="#id3218416" class="para">9</a>] </sup>
+ </p></div><div class="footnote"><p><sup>[<a id="ftn.id2798519" href="#id2798519" 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>Prev</strong>2. We Need Feedback!</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Vulnerability_Assessment.html"><strong>Next</strong>1.2. Vulnerability Assessment</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/chap-Security_Guide-Software_Maintenance.html b/public_html/en-US/Fedora/13/html/Security_Guide/chap-Security_Guide-Software_Maintenance.html
index 059cbe5..b2b3188 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/chap-Security_Guide-Software_Maintenance.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/chap-Security_Guide-Software_Maintenance.html
@@ -1,7 +1,7 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 6. Software Maintenance</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="..
/../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Secure_Installation-Utilize_LUKS_Partition_Encryption.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 6. Software Maintenance" id="chap-Security_Guide-Software_Maintenance" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 6. Software Maintenance</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.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. Adjusting Automatic Updates</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">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 6. Software Maintenance</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../
../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Secure_Installation-Utilize_LUKS_Partition_Encryption.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 6. Software Maintenance" id="chap-Security_Guide-Software_Maintenance" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 6. Software Maintenance</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.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. Adjusting Automatic Updates</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" title="6.1. Install Minimal Software" id="sect-Security_Guide-Software_Maintenance-Install_Minimal_Software"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.1. Install Minimal Software</h2></div></div></div><div class="para">
+ </div><div class="section" title="6.1. Install Minimal Software" id="sect-Security_Guide-Software_Maintenance-Install_Minimal_Software"><div class="titlepage"><div><div keep-together.within-column="always"><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>Prev</strong>5.2. Utilize LUKS Partition Encryption</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates.html"><strong>Next</strong>6.2. Plan and Configure Security Updates</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/index.html b/public_html/en-US/Fedora/13/html/Security_Guide/index.html
index c91a22b..1442afe 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/index.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/index.html
@@ -1,9 +1,9 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Security Guide</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><meta name="description" content="The Fedora Security Guide is designed to assist users of Fedora in learning the processes and practices of securing workstations and servers against local and remote intrusion, exploitation, and malicious activity. Focused on Fedora Linux but detailing concepts and techniques valid for all Linux systems, the Fedora 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 too
ls, 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" /><link rel="next" href="pref-Security_Guide-Preface.html" title="Preface" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"></li><li class="next"><a accesskey="n" href="pref-Security_Guide-Preface.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="book" title="Security Guide" lang="en-US"><div class="titlepa
ge"><div><div class="producttitle" font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><span class="productname">Fedora</span> <span class="productnumber">13</span></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h1 id="id4431348" class="title">Security Guide</h1></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h2 class="subtitle">A Guide to Securing Fedora Linux</h2></div><p class="edition">Edition 13.0</p><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h3 class="corpauthor">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Security Guide</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><meta name="description" content="The Fedora Security Guide is designed to assist users of Fedora in learning the processes and practices of securing workstations and servers against local and remote intrusion, exploitation, and malicious activity. Focused on Fedora Linux but detailing concepts and techniques valid for all Linux systems, the Fedora 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 tool
s, 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" /><link rel="next" href="pref-Security_Guide-Preface.html" title="Preface" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"></li><li class="next"><a accesskey="n" href="pref-Security_Guide-Preface.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="book" title="Security Guide" id="id3921079" lang="en-US"><div
class="titlepage"><div><div class="producttitle" font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><span class="productname">Fedora</span> <span class="productnumber">13</span></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h1 id="id3921079" class="title">Security Guide</h1></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h2 class="subtitle">A Guide to Securing Fedora Linux</h2></div><p class="edition">Edition 13.0</p><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h3 class="corpauthor">
<span class="inlinemediaobject"><object data="Common_Content/images/title_logo.svg" type="image/svg+xml"> Logo</object></span>
- </h3></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div xml:lang="en-US" class="authorgroup" lang="en-US"><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 class="author"><h3 class="author"><span class="firstname">Adam</span> <span class="surname">Ligas</span></h3><div class="affiliation"><span class="orgname">Fedora Project</span></div><code class="email"><a class="email" href="mailto:adam at physco.com">adam at physco.com</a></code></div></div></div><h
r /><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div id="id3050099" class="legalnotice"><h1 class="legalnotice">Legal Notice</h1><div class="para">
+ </h3></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div xml:lang="en-US" class="authorgroup" lang="en-US"><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 class="author"><h3 class="author"><span class="firstname">Adam</span> <span class="surname">Ligas</span></h3><div class="affiliation"><span class="orgname">Fedora Project</span></div><code class="email"><a class="email" href="mailto:adam at physco.com">adam at physco.com</a></code></div></div></div><h
r /><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div id="id2929174" class="legalnotice"><h1 class="legalnotice">Legal Notice</h1><div class="para">
Copyright <span class="trademark"></span>© 2010 Red Hat, Inc.
</div><div class="para">
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at <a href="http://creativecommons.org/licenses/by-sa/3.0/">http://creativecommons.org/licenses/by-sa/3.0/</a>. The original authors of this document, and Red Hat, designate the Fedora Project as the "Attribution Party" for purposes of CC-BY-SA. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
@@ -23,4 +23,4 @@
All other trademarks are the property of their respective owners.
</div></div></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div class="abstract" title="Abstract"><h6>Abstract</h6><div class="para">
The Fedora Security Guide is designed to assist users of Fedora in learning the processes and practices of securing workstations and servers against local and remote intrusion, exploitation, and malicious activity. Focused on Fedora Linux but detailing concepts and techniques valid for all Linux systems, the Fedora 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">Preface</a></span></dt><dd><dl><dt><span class="section"><a href="pref-Security_Guide-Preface.html#id2866553">1. Document Conventions</a></span></dt><dd><dl><dt><span class="section"><a href="pref-Security_Guide-Preface.html#id4401948">1.1. Typographic Conventions</a></span></dt><dt><span class="section"><a href="pref-Security_Guide-Preface.html#id3478227">1.2. Pull-quote Conventions</a></span></dt><dt><span class="section"><a href="pref-Security_Guide-Preface.html#id3136613">1.3. Notes and Warnings</a></span></dt></dl></dd><dt><span class="section"><a href="We_Need_Feedback.html">2. We Need Feedback!</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-Security_Guide-Security_Overview.html#sect-Security_Guide-Introd
uction_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. Conclusion</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-V
ulnerability_Assessment.html#sect-Security_Guide-Vulnerability_Assessment-Thinking_Like_the_Enemy">1.2.1. Thinking Like the Enemy</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Vulnerability_Assessment-Defining_Assessment_and_Testing.html">1.2.2. Defining Assessment and Testing</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Vulnerability_Assessment-Evaluating_the_Tools.html">1.2.3. Evaluating the Tools</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 S
ecurity</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. Common Exploits and Attacks</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Security_Updates.html">1.5. Security Updates</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><d
t><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_Network.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. Available Network Services</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. Personal Firewalls</a></span></dt><dt><span class="section"><a href="chap-Security_Guide-Securing_Your_Network.html#sect-Security_Guide-Workstation_Security-Security_Enhanced_Communication_Tools">2.1.7. Security Enha
nced 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-Sec
urity_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. Introduction</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="section"><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 hre
f="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-Additional_Resources.html">2.5.5. Additional Resources</a></span></dt></dl></dd><dt><span cl
ass="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. What is 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 and 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="s
ect-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. Setting Up Cross Realm Authentication</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 Does a VPN Work?</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Virtual_Private_Ne
tworks_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 <abbr class="abbrev">IPsec</abbr> 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_Net
works_VPNs-Starting_and_Stopping_an_IPsec_Connection.html">2.7.8. Starting and Stopping an <abbr class="abbrev">IPsec</abbr> 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 and IPTables</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Firewalls-Basic_Firewall_Configuration.html">2.8.2. Basic Firewall Configuration</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Firewalls-Using_IPTables.html">2.8.3. Using IPTables</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Firewalls-Common_IPTables_Filtering.html">2.8.4. Common IPTables Filtering</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Firewalls-FORWARD_and_NAT_Rules.html">2.8.5. <code class="computeroutput">FO
RWARD</code> and <acronym class="acronym">NAT</acronym> Rules</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Firewalls-Malicious_Software_and_Spoofed_IP_Addresses.html">2.8.6. Malicious Software and Spoofed IP Addresses</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Firewalls-IPTables_and_Connection_Tracking.html">2.8.7. IPTables and Connection Tracking</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. Packet Filtering</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-IPTable
s-Command_Options_for_IPTables.html">2.9.2. Command Options for IPTables</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-IPTables-Saving_IPTables_Rules.html">2.9.3. Saving IPTables Rules</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-IPTables-IPTables_Control_Scripts.html">2.9.4. IPTables Control Scripts</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-IPTables-IPTables_and_IPv6.html">2.9.5. IPTables and IPv6</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-IPTables-Additional_Resources.html">2.9.6. 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. Data at Rest</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Encryption-Protecting_Data_a
t_Rest-Full_Disk_Encryption.html">3.2. Full Disk Encryption</a></span></dt><dt><span class="section"><a href="Security_Guide-Encryption-Protecting_Data_at_Rest-File_Based_Encryption.html">3.3. File Based Encryption</a></span></dt><dt><span class="section"><a href="Security_Guide-Encryption-Data_in_Motion.html">3.4. Data in Motion</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. Secure Shell</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. 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-Instal
lation">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. Generating GPG Keys in GNOME</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Encryption-Using_GPG-Creating_GP
G_Keys_in_KDE1.html">3.9.2. Generating 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. Generating GPG Keys Using the Command Line</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Alpine.html">3.9.4. Using GPG with Alpine</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution.html">3.9.5. Using GPG with Evolution</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Thunderbird.html">3.9.6. Using GPG with Thunderbird</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Encryption-Using_GPG-About_Public_Key_Encryption.html">3.9.7. 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.
General Principles of Information Security</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_Guides_and_Tools">4.1. Tips, Guides, and Tools</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. Software Maintenance</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Security_Guide-Software_Maintena
nce.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.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. Adjusting Automatic Updates</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. References</a></span></dt><dt><span class="appendix"><a href="chap-Security_Guide-Encryption_Standards.html">A. Encryption Standards</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Security_Gu
ide-Encryption_Standards.html#id3430291">A.1. Synchronous Encryption</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Security_Guide-Encryption_Standards.html#id3302598">A.1.1. Advanced Encryption Standard - AES</a></span></dt><dt><span class="section"><a href="chap-Security_Guide-Encryption_Standards.html#id3049809">A.1.2. Data Encryption Standard - DES</a></span></dt></dl></dd><dt><span class="section"><a href="apas02.html">A.2. Public-key Encryption</a></span></dt><dd><dl><dt><span class="section"><a href="apas02.html#id3371753">A.2.1. Diffie-Hellman</a></span></dt><dt><span class="section"><a href="apas02s02.html">A.2.2. RSA</a></span></dt><dt><span class="section"><a href="apas02s03.html">A.2.3. DSA</a></span></dt><dt><span class="section"><a href="apas02s04.html">A.2.4. SSL/TLS</a></span></dt><dt><span class="section"><a href="apas02s05.html">A.2.5. Cramer-Shoup Cryptosystem</a></span></dt><dt><span class="section"><a href="apas02s06.html">A.2.6. ElGamal
Encryption</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="appe-Publican-Revision_History.html">B. Revision History</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>Next</strong>Preface</a></li></ul></body></html>
+ </div></div></div></div><hr /></div><div class="toc"><dl><dt><span class="preface"><a href="pref-Security_Guide-Preface.html">Preface</a></span></dt><dd><dl><dt><span class="section"><a href="pref-Security_Guide-Preface.html#id2851385">1. Document Conventions</a></span></dt><dd><dl><dt><span class="section"><a href="pref-Security_Guide-Preface.html#id2829053">1.1. Typographic Conventions</a></span></dt><dt><span class="section"><a href="pref-Security_Guide-Preface.html#id2817419">1.2. Pull-quote Conventions</a></span></dt><dt><span class="section"><a href="pref-Security_Guide-Preface.html#id2963957">1.3. Notes and Warnings</a></span></dt></dl></dd><dt><span class="section"><a href="We_Need_Feedback.html">2. We Need Feedback!</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-Security_Guide-Security_Overview.html#sect-Security_Guide-Introd
uction_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. Conclusion</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-V
ulnerability_Assessment.html#sect-Security_Guide-Vulnerability_Assessment-Thinking_Like_the_Enemy">1.2.1. Thinking Like the Enemy</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Vulnerability_Assessment-Defining_Assessment_and_Testing.html">1.2.2. Defining Assessment and Testing</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Vulnerability_Assessment-Evaluating_the_Tools.html">1.2.3. Evaluating the Tools</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 S
ecurity</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. Common Exploits and Attacks</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Security_Updates.html">1.5. Security Updates</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><d
t><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_Network.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. Available Network Services</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. Personal Firewalls</a></span></dt><dt><span class="section"><a href="chap-Security_Guide-Securing_Your_Network.html#sect-Security_Guide-Workstation_Security-Security_Enhanced_Communication_Tools">2.1.7. Security Enha
nced 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-Sec
urity_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. Introduction</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="section"><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 hre
f="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-Additional_Resources.html">2.5.5. Additional Resources</a></span></dt></dl></dd><dt><span cl
ass="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. What is 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 and 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="s
ect-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. Setting Up Cross Realm Authentication</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 Does a VPN Work?</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Virtual_Private_Ne
tworks_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 <abbr class="abbrev">IPsec</abbr> 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_Net
works_VPNs-Starting_and_Stopping_an_IPsec_Connection.html">2.7.8. Starting and Stopping an <abbr class="abbrev">IPsec</abbr> 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 and IPTables</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Firewalls-Basic_Firewall_Configuration.html">2.8.2. Basic Firewall Configuration</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Firewalls-Using_IPTables.html">2.8.3. Using IPTables</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Firewalls-Common_IPTables_Filtering.html">2.8.4. Common IPTables Filtering</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Firewalls-FORWARD_and_NAT_Rules.html">2.8.5. <code class="computeroutput">FO
RWARD</code> and <acronym class="acronym">NAT</acronym> Rules</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Firewalls-Malicious_Software_and_Spoofed_IP_Addresses.html">2.8.6. Malicious Software and Spoofed IP Addresses</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Firewalls-IPTables_and_Connection_Tracking.html">2.8.7. IPTables and Connection Tracking</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. Packet Filtering</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-IPTable
s-Command_Options_for_IPTables.html">2.9.2. Command Options for IPTables</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-IPTables-Saving_IPTables_Rules.html">2.9.3. Saving IPTables Rules</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-IPTables-IPTables_Control_Scripts.html">2.9.4. IPTables Control Scripts</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-IPTables-IPTables_and_IPv6.html">2.9.5. IPTables and IPv6</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-IPTables-Additional_Resources.html">2.9.6. 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. Data at Rest</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Encryption-Protecting_Data_a
t_Rest-Full_Disk_Encryption.html">3.2. Full Disk Encryption</a></span></dt><dt><span class="section"><a href="Security_Guide-Encryption-Protecting_Data_at_Rest-File_Based_Encryption.html">3.3. File Based Encryption</a></span></dt><dt><span class="section"><a href="Security_Guide-Encryption-Data_in_Motion.html">3.4. Data in Motion</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. Secure Shell</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. 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-Instal
lation">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. Generating GPG Keys in GNOME</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Encryption-Using_GPG-Creating_GP
G_Keys_in_KDE1.html">3.9.2. Generating 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. Generating GPG Keys Using the Command Line</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Alpine.html">3.9.4. Using GPG with Alpine</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution.html">3.9.5. Using GPG with Evolution</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Thunderbird.html">3.9.6. Using GPG with Thunderbird</a></span></dt><dt><span class="section"><a href="sect-Security_Guide-Encryption-Using_GPG-About_Public_Key_Encryption.html">3.9.7. 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.
General Principles of Information Security</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_Guides_and_Tools">4.1. Tips, Guides, and Tools</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. Software Maintenance</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Security_Guide-Software_Maintena
nce.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.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. Adjusting Automatic Updates</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. References</a></span></dt><dt><span class="appendix"><a href="chap-Security_Guide-Encryption_Standards.html">A. Encryption Standards</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Security_Gu
ide-Encryption_Standards.html#id2872303">A.1. Synchronous Encryption</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Security_Guide-Encryption_Standards.html#id2644834">A.1.1. Advanced Encryption Standard - AES</a></span></dt><dt><span class="section"><a href="chap-Security_Guide-Encryption_Standards.html#id2721588">A.1.2. Data Encryption Standard - DES</a></span></dt></dl></dd><dt><span class="section"><a href="apas02.html">A.2. Public-key Encryption</a></span></dt><dd><dl><dt><span class="section"><a href="apas02.html#id2684083">A.2.1. Diffie-Hellman</a></span></dt><dt><span class="section"><a href="apas02s02.html">A.2.2. RSA</a></span></dt><dt><span class="section"><a href="apas02s03.html">A.2.3. DSA</a></span></dt><dt><span class="section"><a href="apas02s04.html">A.2.4. SSL/TLS</a></span></dt><dt><span class="section"><a href="apas02s05.html">A.2.5. Cramer-Shoup Cryptosystem</a></span></dt><dt><span class="section"><a href="apas02s06.html">A.2.6. ElGamal
Encryption</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="appe-Publican-Revision_History.html">B. Revision History</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>Next</strong>Preface</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/pref-Security_Guide-Preface.html b/public_html/en-US/Fedora/13/html/Security_Guide/pref-Security_Guide-Preface.html
index b1a0412..04c0f37 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/pref-Security_Guide-Preface.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/pref-Security_Guide-Preface.html
@@ -1,10 +1,10 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Preface</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. We Need Feedback!" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Conte
nt/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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>Prev</strong></a></li><li class="next"><a accesskey="n" href="We_Need_Feedback.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="preface" title="Preface" id="pref-Security_Guide-Preface" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Preface</h1></div></div></div><div xml:lang="en-US" class="section" title="1. Document Conventions" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id2866553">1. Document Conventions</h2></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Preface</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. We Need Feedback!" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_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="index.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="We_Need_Feedback.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="preface" title="Preface" id="pref-Security_Guide-Preface" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Preface</h1></div></div></div><div xml:lang="en-US" class="section" title="1. Document Conventions" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id2851385">1. Document Conventions</h2></div></div></div><div class="para">
This manual uses several conventions to highlight certain words and phrases and draw attention to specific pieces of information.
</div><div class="para">
In PDF and paper editions, this manual uses typefaces drawn from the <a href="https://fedorahosted.org/liberation-fonts/">Liberation Fonts</a> set. The Liberation Fonts set is also used in HTML editions if the set is installed on your system. If not, alternative but equivalent typefaces are displayed. Note: Red Hat Enterprise Linux 5 and later includes the Liberation Fonts set by default.
- </div><div class="section" title="1.1. Typographic Conventions"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id4401948">1.1. Typographic Conventions</h3></div></div></div><div class="para">
+ </div><div class="section" title="1.1. Typographic Conventions"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id2829053">1.1. Typographic Conventions</h3></div></div></div><div class="para">
Four typographic conventions are used to call attention to specific words and phrases. These conventions, and the circumstances they apply to, are as follows.
</div><div class="para">
<code class="literal">Mono-spaced Bold</code>
@@ -52,14 +52,12 @@
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">
Publican is a <em class="firstterm">DocBook</em> publishing system.
- </div></blockquote></div></div><div class="section" title="1.2. Pull-quote Conventions"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id3478227">1.2. Pull-quote Conventions</h3></div></div></div><div class="para">
+ </div></blockquote></div></div><div class="section" title="1.2. Pull-quote Conventions"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id2817419">1.2. Pull-quote Conventions</h3></div></div></div><div class="para">
Terminal output and source code listings are set off visually from the surrounding text.
</div><div class="para">
Output sent to a terminal is set in <code class="computeroutput">mono-spaced roman</code> and presented thus:
</div><pre class="screen">books Desktop documentation drafts mss photos stuff svn
-books_tests Desktop1 downloads images notes scripts svgs
-
-</pre><div class="para">
+books_tests Desktop1 downloads images notes scripts svgs</pre><div class="para">
Source-code listings are also set in <code class="computeroutput">mono-spaced roman</code> but add syntax highlighting as follows:
</div><pre class="programlisting">package org.<span class="perl_Function">jboss</span>.<span class="perl_Function">book</span>.<span class="perl_Function">jca</span>.<span class="perl_Function">ex1</span>;
@@ -79,9 +77,7 @@ books_tests Desktop1 downloads images notes scripts svgs
System.<span class="perl_Function">out</span>.<span class="perl_Function">println</span>(<span class="perl_String">"Echo.echo('Hello') = "</span> + echo.<span class="perl_Function">echo</span>(<span class="perl_String">"Hello"</span>));
}
-}
-
-</pre></div><div class="section" title="1.3. Notes and Warnings"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id3136613">1.3. Notes and Warnings</h3></div></div></div><div class="para">
+}</pre></div><div class="section" title="1.3. Notes and Warnings"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id2963957">1.3. Notes and Warnings</h3></div></div></div><div class="para">
Finally, we use three visual styles to draw attention to information that might otherwise be overlooked.
</div><div class="note"><h2>Note</h2><div class="para">
Notes are tips, shortcuts or alternative approaches to the task at hand. Ignoring a note should have no negative consequences, but you might miss out on a trick that makes your life easier.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Additional_Resources-Related_Books.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Additional_Resources-Related_Books.html
index 691d7a8..496fdd7 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Additional_Resources-Related_Books.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Additional_Resources-Related_Books.html
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.htm
l">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Additional_Resources-Useful_TCP_Wrappers_Websites.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Kerberos.html"><strong>Next</strong></a></li></ul><div class="section" title="2.5.5.3. Related Books" id="sect-Security_Guide-Additional_Resources-Related_Books"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.5.5.3. Related Books</h4></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.5.5.3. Related Books</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html
">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Additional_Resources-Useful_TCP_Wrappers_Websites.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Kerberos.html"><strong>Next</strong></a></li></ul><div class="section" title="2.5.5.3. Related Books" id="sect-Security_Guide-Additional_Resources-Related_Books"><div class="titlepage"><div><div keep-together.within-column="always"><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
class="listitem"><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>Prev</strong>2.5.5.2. Useful TCP Wrappers Websites</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Kerberos.html"><strong>Next</strong>2.6. Kerberos</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Additional_Resources-Related_Documentation.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Additional_Resources-Related_Documentation.html
index 0439b95..a9be778 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Additional_Resources-Related_Documentation.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Additional_Resources-Related_Documentation.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.9.3. Related Documentation</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Useful Firewall Websites" /><link rel="next" href="sect-Security_Guide-IPTables.html" title="2.9. IPTables" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an
iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Additional_Resources-Useful_Firewall_Websites.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-IPTables.html"><strong>Next</strong></a></li></ul><div class="section" title="2.8.9.3. Related Documentation" id="sect-Security_Guide-Additional_Resources-Related_Documentation"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.8.9.3. Related Documentation</h4></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.9.3. Related Documentation</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Useful Firewall Websites" /><link rel="next" href="sect-Security_Guide-IPTables.html" title="2.9. IPTables" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an i
frame, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Additional_Resources-Useful_Firewall_Websites.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-IPTables.html"><strong>Next</strong></a></li></ul><div class="section" title="2.8.9.3. Related Documentation" id="sect-Security_Guide-Additional_Resources-Related_Documentation"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Additional_Resources-Related_Documentation">2.8.9.3. Related Documentation</h4></div></div></div><div class="itemize
dlist"><ul><li class="listitem"><div class="para">
<em class="citetitle">Red Hat Linux Firewalls</em>, by Bill McCarty; Red Hat Press — a comprehensive reference to building network and server firewalls using open source packet filtering technology such as Netfilter and <code class="command">iptables</code>. It includes topics that cover analyzing firewall logs, developing firewall rules, and customizing your firewall using various graphical tools.
</div></li><li class="listitem"><div class="para">
<em class="citetitle">Linux Firewalls</em>, by Robert Ziegler; New Riders Press — contains a wealth of information on building firewalls using both 2.2 kernel <code class="command">ipchains</code> as well as Netfilter and <code class="command">iptables</code>. Additional security topics such as remote access issues and intrusion detection systems are also covered.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Additional_Resources-Useful_Firewall_Websites.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Additional_Resources-Useful_Firewall_Websites.html
index 1c55884..9dd07bc 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Additional_Resources-Useful_Firewall_Websites.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Additional_Resources-Useful_Firewall_Websites.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.9.2. Useful Firewall Websites</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Related Documentation" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="
../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Firewalls-Additional_Resources.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Additional_Resources-Related_Documentation.html"><strong>Next</strong></a></li></ul><div class="section" title="2.8.9.2. Useful Firewall Websites" id="sect-Security_Guide-Additional_Resources-Useful_Firewall_Websites"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.8.9.2. Useful Firewall Websites</h4></div></div></div><div class="itemizedlist"
><ul><li class="listitem"><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.9.2. Useful Firewall Websites</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Related Documentation" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src=".
./../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Firewalls-Additional_Resources.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Additional_Resources-Related_Documentation.html"><strong>Next</strong></a></li></ul><div class="section" title="2.8.9.2. Useful Firewall Websites" id="sect-Security_Guide-Additional_Resources-Useful_Firewall_Websites"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Additional_Resources-Useful_Firewall_Websites">2.8.9.2. Us
eful Firewall Websites</h4></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<a href="http://www.netfilter.org/">http://www.netfilter.org/</a> — The official homepage of the Netfilter and <code class="command">iptables</code> project.
</div></li><li class="listitem"><div class="para">
<a href="http://www.tldp.org/">http://www.tldp.org/</a> — The Linux Documentation Project contains several useful guides relating to firewall creation and administration.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Additional_Resources-Useful_IP_Tables_Websites.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Additional_Resources-Useful_IP_Tables_Websites.html
index 16c282c..0375e6e 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Additional_Resources-Useful_IP_Tables_Websites.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Additional_Resources-Useful_IP_Tables_Websites.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.9.6.2. Useful IP Tables Websites</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="sect-Security_Guide-IPTables-Additional_Resources.html" title="2.9.6. Additional Resources" /><link rel="prev" href="sect-Security_Guide-IPTables-Additional_Resources.html" title="2.9.6. Additional Resources" /><link rel="next" href="chap-Security_Guide-Encryption.html" title="Chapter 3. Encryption" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe,
to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-IPTables-Additional_Resources.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Security_Guide-Encryption.html"><strong>Next</strong></a></li></ul><div class="section" title="2.9.6.2. Useful IP Tables Websites" id="sect-Security_Guide-Additional_Resources-Useful_IP_Tables_Websites"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.9.6.2. Useful IP Tables Websites</h4></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.9.6.2. Useful IP Tables Websites</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="sect-Security_Guide-IPTables-Additional_Resources.html" title="2.9.6. Additional Resources" /><link rel="prev" href="sect-Security_Guide-IPTables-Additional_Resources.html" title="2.9.6. Additional Resources" /><link rel="next" href="chap-Security_Guide-Encryption.html" title="Chapter 3. Encryption" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, t
o view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-IPTables-Additional_Resources.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Security_Guide-Encryption.html"><strong>Next</strong></a></li></ul><div class="section" title="2.9.6.2. Useful IP Tables Websites" id="sect-Security_Guide-Additional_Resources-Useful_IP_Tables_Websites"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Additional_Resources-Useful_IP_Tables_Websites">2.9.6.2. Useful IP Tables Websites</h4></div></div></div><div class="itemizedlist"
><ul><li class="listitem"><div class="para">
<a href="http://www.netfilter.org/">http://www.netfilter.org/</a> — The home of the netfilter/iptables project. Contains assorted information about <code class="command">iptables</code>, including a FAQ addressing specific problems and various helpful guides by Rusty Russell, the Linux IP firewall maintainer. The HOWTO documents on the site cover subjects such as basic networking concepts, kernel packet filtering, and NAT configurations.
</div></li><li class="listitem"><div class="para">
<a href="http://www.linuxnewbie.org/nhf/Security/IPtables_Basics.html">http://www.linuxnewbie.org/nhf/Security/IPtables_Basics.html</a> — An introduction to the way packets move through the Linux kernel, plus an introduction to constructing basic <code class="command">iptables</code> commands.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Additional_Resources-Useful_Kerberos_Websites.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Additional_Resources-Useful_Kerberos_Websites.html
index c28e576..f742497 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Additional_Resources-Useful_Kerberos_Websites.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Additional_Resources-Useful_Kerberos_Websites.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.6.10.2. Useful Kerberos Websites</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../
../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Kerberos-Additional_Resources.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Virtual_Private_Networks_VPNs.html"><strong>Next</strong></a></li></ul><div class="section" title="2.6.10.2. Useful Kerberos Websites" id="sect-Security_Guide-Additional_Resources-Useful_Kerberos_Websites"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.6.10.2. Useful Kerberos Websites</h4></div></div></div><div class="itemizedlist"><ul><li class="li
stitem"><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.6.10.2. Useful Kerberos Websites</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../.
./../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Kerberos-Additional_Resources.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Virtual_Private_Networks_VPNs.html"><strong>Next</strong></a></li></ul><div class="section" title="2.6.10.2. Useful Kerberos Websites" id="sect-Security_Guide-Additional_Resources-Useful_Kerberos_Websites"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Additional_Resources-Useful_Kerberos_Websites">2.6.10.2. Useful Kerberos Webs
ites</h4></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<a href="http://web.mit.edu/kerberos/www/">http://web.mit.edu/kerberos/www/</a> — <em class="citetitle">Kerberos: The Network Authentication Protocol</em> webpage from MIT.
</div></li><li class="listitem"><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> — The Kerberos Frequently Asked Questions (FAQ).
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Additional_Resources-Useful_PAM_Websites.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Additional_Resources-Useful_PAM_Websites.html
index 1797663..2fa0aad 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Additional_Resources-Useful_PAM_Websites.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Additional_Resources-Useful_PAM_Websites.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.4.8.2. Useful PAM Websites</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id=
"tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Additional_Resources.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-TCP_Wrappers_and_xinetd.html"><strong>Next</strong></a></li></ul><div class="section" title="2.4.8.2. Useful PAM Websites" id="sect-Security_Guide-Additional_Resources-Useful_PAM_Websites"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.4.8.2. Useful PAM Websites</h4></div></div></div><div
class="itemizedlist"><ul><li class="listitem"><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.4.8.2. Useful PAM Websites</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="
tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Additional_Resources.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-TCP_Wrappers_and_xinetd.html"><strong>Next</strong></a></li></ul><div class="section" title="2.4.8.2. Useful PAM Websites" id="sect-Security_Guide-Additional_Resources-Useful_PAM_Websites"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Additional_Resources-Useful_PAM_W
ebsites">2.4.8.2. Useful PAM Websites</h4></div></div></div><div class="itemizedlist"><ul><li class="listitem"><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.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Additional_Resources-Useful_TCP_Wrappers_Websites.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Additional_Resources-Useful_TCP_Wrappers_Websites.html
index 9f0205e..31f09de 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Additional_Resources-Useful_TCP_Wrappers_Websites.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Additional_Resources-Useful_TCP_Wrappers_Websites.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.5.5.2. Useful TCP Wrappers Websites</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" c
lass="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-TCP_Wrappers_and_xinetd-Additional_Resources.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Additional_Resources-Related_Books.html"><strong>Next</strong></a></li></ul><div class="section" title="2.5.5.2. Useful TCP Wrappers Websites" id="sect-Security_Guide-Additional_Resources-Useful_TCP_Wrappers_Websites"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.5.5.2. Useful TCP Wrappers Websites</h4></div></d
iv></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.5.5.2. Useful TCP Wrappers Websites</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" cl
ass="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-TCP_Wrappers_and_xinetd-Additional_Resources.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Additional_Resources-Related_Books.html"><strong>Next</strong></a></li></ul><div class="section" title="2.5.5.2. Useful TCP Wrappers Websites" id="sect-Security_Guide-Additional_Resources-Useful_TCP_Wrappers_Websites"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Additional_Resources-Useful_T
CP_Wrappers_Websites">2.5.5.2. Useful TCP Wrappers Websites</h4></div></div></div><div class="itemizedlist"><ul><li class="listitem"><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 class="listitem"><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.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Altering_xinetd_Configuration_Files-Access_Control_Options.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Altering_xinetd_Configuration_Files-Access_Control_Options.html
index 9689ec6..6eead2a 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Altering_xinetd_Configuration_Files-Access_Control_Options.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Altering_xinetd_Configuration_Files-Access_Control_Options.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.5.4.3.2. Access Control Options</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Bi
nding and Redirection Options" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-xinetd_Configuration_Files-Altering_xinetd_Configuration_Files.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Altering_xinetd_Configuration_Files-Binding_and_Redirection_Options.html"><strong>Next</strong></a></li></ul><div class="section" title="2.5.4.3.2. Access Control Options" id="sect-Security_Guide-Altering_xinetd_Configura
tion_Files-Access_Control_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.5.4.3.2. Access Control Options</h5></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.5.4.3.2. Access Control Options</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Bin
ding and Redirection Options" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-xinetd_Configuration_Files-Altering_xinetd_Configuration_Files.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Altering_xinetd_Configuration_Files-Binding_and_Redirection_Options.html"><strong>Next</strong></a></li></ul><div class="section" title="2.5.4.3.2. Access Control Options" id="sect-Security_Guide-Altering_xinetd_Configurat
ion_Files-Access_Control_Options"><div class="titlepage"><div><div keep-together.within-column="always"><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">Section 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.
@@ -34,16 +34,13 @@
no_access = 172.16.45.0/24
log_on_success += PID HOST EXIT
access_times = 09:45-16:15
-}
-</pre><div class="para">
+}</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">
+ </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">
+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:
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Altering_xinetd_Configuration_Files-Binding_and_Redirection_Options.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Altering_xinetd_Configuration_Files-Binding_and_Redirection_Options.html
index ff7a8ff..97865c9 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Altering_xinetd_Configuration_Files-Binding_and_Redirection_Options.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Altering_xinetd_Configuration_Files-Binding_and_Redirection_Options.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.5.4.3.3. Binding and Redirection Options</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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 Man
agement Options" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Altering_xinetd_Configuration_Files-Access_Control_Options.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Altering_xinetd_Configuration_Files-Resource_Management_Options.html"><strong>Next</strong></a></li></ul><div class="section" title="2.5.4.3.3. Binding and Redirection Options" id="sect-Security_Guide-Altering_xinetd_Configuration_Files-Bi
nding_and_Redirection_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.5.4.3.3. Binding and Redirection Options</h5></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.5.4.3.3. Binding and Redirection Options</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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 Mana
gement Options" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Altering_xinetd_Configuration_Files-Access_Control_Options.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Altering_xinetd_Configuration_Files-Resource_Management_Options.html"><strong>Next</strong></a></li></ul><div class="section" title="2.5.4.3.3. Binding and Redirection Options" id="sect-Security_Guide-Altering_xinetd_Configuration_Files-Bin
ding_and_Redirection_Options"><div class="titlepage"><div><div keep-together.within-column="always"><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.
@@ -23,8 +23,7 @@
log_on_failure += USERID
bind = 123.123.123.123
redirect = 10.0.1.13 23
-}
-</pre><div class="para">
+}</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.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Altering_xinetd_Configuration_Files-Resource_Management_Options.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Altering_xinetd_Configuration_Files-Resource_Management_Options.html
index 498aaf5..346a609 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Altering_xinetd_Configuration_Files-Resource_Management_Options.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Altering_xinetd_Configuration_Files-Resource_Management_Options.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.5.4.3.4. Resource Management Options</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Altering_xinetd_Configuration_Files-Binding_and_Redirection_Options.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-TCP_Wrappers_and_xinetd-Additional_Resources.html"><strong>Next</strong></a></li></ul><div class="section" title="2.5.4.3.4. Resource Management Options" id="sect-Security_Guide-Altering_xinetd_Configuration_Files-Resource_Management_Options"><di
v class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.5.4.3.4. Resource Management Options</h5></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.5.4.3.4. Resource Management Options</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Altering_xinetd_Configuration_Files-Binding_and_Redirection_Options.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-TCP_Wrappers_and_xinetd-Additional_Resources.html"><strong>Next</strong></a></li></ul><div class="section" title="2.5.4.3.4. Resource Management Options" id="sect-Security_Guide-Altering_xinetd_Configuration_Files-Resource_Management_Options"><div
class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><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.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Network_Security.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Network_Security.html
index 2044009..d6fede3 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Network_Security.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Network_Security.html
@@ -1,11 +1,11 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.3.2. Threats to Network Security</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe i
d="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Attackers_and_Vulnerabilities.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Server_Security.html"><strong>Next</strong></a></li></ul><div class="section" title="1.3.2. Threats to Network Security" id="sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Network_Security"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">1.3.2. Threats to Network
Security</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.3.2. Threats to Network Security</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id
="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Attackers_and_Vulnerabilities.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Server_Security.html"><strong>Next</strong></a></li></ul><div class="section" title="1.3.2. Threats to Network Security" id="sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Network_Security"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Att
ackers_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" title="1.3.2.1. Insecure Architectures" id="sect-Security_Guide-Threats_to_Network_Security-Insecure_Architectures"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">1.3.2.1. Insecure Architectures</h4></div></div></div><div class="para">
+ </div><div class="section" title="1.3.2.1. Insecure Architectures" id="sect-Security_Guide-Threats_to_Network_Security-Insecure_Architectures"><div class="titlepage"><div><div keep-together.within-column="always"><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" title="1.3.2.1.1. Broadcast Networks" id="sect-Security_Guide-Insecure_Architectures-Broadcast_Networks"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">1.3.2.1.1. Broadcast Networks</h5></div></div></div><div class="para">
+ </div><div class="section" title="1.3.2.1.1. Broadcast Networks" id="sect-Security_Guide-Insecure_Architectures-Broadcast_Networks"><div class="titlepage"><div><div keep-together.within-column="always"><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" title="1.3.2.1.2. Centralized Servers" id="sect-Security_Guide-Insecure_Architectures-Centralized_Servers"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">1.3.2.1.2. Centralized Servers</h5></div></div></div><div class="para">
+ </div></div><div class="section" title="1.3.2.1.2. Centralized Servers" id="sect-Security_Guide-Insecure_Architectures-Centralized_Servers"><div class="titlepage"><div><div keep-together.within-column="always"><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>Prev</strong>1.3. Attackers and Vulnerabilities</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Server_Security.html"><strong>Next</strong>1.3.3. Threats to Server Security</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Server_Security.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Server_Security.html
index 6e86934..4b6157c 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Server_Security.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Server_Security.html
@@ -1,8 +1,8 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"
><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Network_Security.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Threats_to_Server_Security-Unpatched_Services.html"><strong>Next</strong></a></li></ul><div class="section" title="1.3.3. Threats to Server Security" id="sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Server_Security"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">1
.3.3. Threats to Server Security</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.3.3. Threats to Server Security</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc">
<iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Network_Security.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Threats_to_Server_Security-Unpatched_Services.html"><strong>Next</strong></a></li></ul><div class="section" title="1.3.3. Threats to Server Security" id="sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Server_Security"><div class="titlepage"><div><div keep-together.within-column="always"><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" title="1.3.3.1. Unused Services and Open Ports" id="sect-Security_Guide-Threats_to_Server_Security-Unused_Services_and_Open_Ports"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">1.3.3.1. Unused Services and Open Ports</h4></div></div></div><div class="para">
+ </div><div class="section" title="1.3.3.1. Unused Services and Open Ports" id="sect-Security_Guide-Threats_to_Server_Security-Unused_Services_and_Open_Ports"><div class="titlepage"><div><div keep-together.within-column="always"><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">Section 2.2, “Server Securityâ€</a> for information on closing ports and disabling unused services.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Workstation_and_Home_PC_Security.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Workstation_and_Home_PC_Security.html
index 99cd21a..09c1c63 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Workstation_and_Home_PC_Security.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Workstation_and_Home_PC_Security.html
@@ -1,7 +1,7 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.3.4. Threats to Workstation and Home PC Security</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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" /></h
ead><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Threats_to_Server_Security-Inherently_Insecure_Services.html"><strong>Prev</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>Next</strong></a></li></ul><div class="section" title="1.3.4. Threats to Workstation and Home PC Security" id="sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Wor
kstation_and_Home_PC_Security"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">1.3.4. Threats to Workstation and Home PC Security</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.3.4. Threats to Workstation and Home PC Security</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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" /></he
ad><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Threats_to_Server_Security-Inherently_Insecure_Services.html"><strong>Prev</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>Next</strong></a></li></ul><div class="section" title="1.3.4. Threats to Workstation and Home PC Security" id="sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Work
station_and_Home_PC_Security"><div class="titlepage"><div><div keep-together.within-column="always"><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" title="1.3.4.1. Bad Passwords" id="sect-Security_Guide-Threats_to_Workstation_and_Home_PC_Security-Bad_Passwords"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">1.3.4.1. Bad Passwords</h4></div></div></div><div class="para">
+ </div><div class="section" title="1.3.4.1. Bad Passwords" id="sect-Security_Guide-Threats_to_Workstation_and_Home_PC_Security-Bad_Passwords"><div class="titlepage"><div><div keep-together.within-column="always"><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">Section 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>Prev</strong>1.3.3.4. Inherently Insecure Services</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</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>Next</strong>1.3.4.2. Vulnerable Client Applications</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Attackers_and_Vulnerabilities.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Attackers_and_Vulnerabilities.html
index 19ac3eb..23fc55f 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Attackers_and_Vulnerabilities.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Attackers_and_Vulnerabilities.html
@@ -1,14 +1,14 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.3. Attackers and Vulnerabilities</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="chap-Security_Guide-Security_Overview.html" title="Chapter 1. Security Overview" /><link rel="prev" href="sect-Security_Guide-Evaluating_the_Tools-Anticipating_Your_Future_Needs.html" title="1.2.3.5. Anticipating Your Future Needs" /><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="toc_embeded "><div id="tocdiv" class="to
c"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Evaluating_the_Tools-Anticipating_Your_Future_Needs.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Network_Security.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" title="1.3. Attackers and Vulnerabilities" id="sect-Security_Guide-Attackers_and_Vulnerabilities" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 cla
ss="title">1.3. Attackers and Vulnerabilities</h2></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.3. Attackers and Vulnerabilities</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="chap-Security_Guide-Security_Overview.html" title="Chapter 1. Security Overview" /><link rel="prev" href="sect-Security_Guide-Evaluating_the_Tools-Anticipating_Your_Future_Needs.html" title="1.2.3.5. Anticipating Your Future Needs" /><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="toc_embeded "><div id="tocdiv" class="toc
"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Evaluating_the_Tools-Anticipating_Your_Future_Needs.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Network_Security.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" title="1.3. Attackers and Vulnerabilities" id="sect-Security_Guide-Attackers_and_Vulnerabilities" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 clas
s="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" title="1.3.1. A Quick History of Hackers" id="sect-Security_Guide-Attackers_and_Vulnerabilities-A_Quick_History_of_Hackers"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">1.3.1. A Quick History of Hackers</h3></div></div></div><div class="para">
+ </div><div class="section" title="1.3.1. A Quick History of Hackers" id="sect-Security_Guide-Attackers_and_Vulnerabilities-A_Quick_History_of_Hackers"><div class="titlepage"><div><div keep-together.within-column="always"><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" title="1.3.1.1. Shades of Gray" id="sect-Security_Guide-A_Quick_History_of_Hackers-Shades_of_Gray"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">1.3.1.1. Shades of Gray</h4></div></div></div><div class="para">
+ </div><div class="section" title="1.3.1.1. Shades of Gray" id="sect-Security_Guide-A_Quick_History_of_Hackers-Shades_of_Gray"><div class="titlepage"><div><div keep-together.within-column="always"><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.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Basic_Firewall_Configuration-Activating_the_IPTables_Service.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Basic_Firewall_Configuration-Activating_the_IPTables_Service.html
index 0c90696..2c79993 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Basic_Firewall_Configuration-Activating_the_IPTables_Service.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Basic_Firewall_Configuration-Activating_the_IPTables_Service.html
@@ -1,9 +1,7 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.2.6. Activating the IPTables Service</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Basic Firewall Configuration" /><link rel="prev" href="sect-Security_Guide-Basic_Firewall_Configuration-Saving_the_Settings.html" title="2.8.2.5. Saving the Settings" /><link rel="next" href="sect-Security_Guide-Firewalls-Using_IPTables.html" title="2.8.3. Using IPTables" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" cl
ass="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Basic_Firewall_Configuration-Saving_the_Settings.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Firewalls-Using_IPTables.html"><strong>Next</strong></a></li></ul><div class="section" title="2.8.2.6. Activating the IPTables Service" id="sect-Security_Guide-Basic_Firewall_Configuration-Activating_the_IPTables_Service"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.8.2.6. Activating the IPTables Service</h4
></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.2.6. Activating the IPTables Service</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Basic Firewall Configuration" /><link rel="prev" href="sect-Security_Guide-Basic_Firewall_Configuration-Saving_the_Settings.html" title="2.8.2.5. Saving the Settings" /><link rel="next" href="sect-Security_Guide-Firewalls-Using_IPTables.html" title="2.8.3. Using IPTables" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" cla
ss="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Basic_Firewall_Configuration-Saving_the_Settings.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Firewalls-Using_IPTables.html"><strong>Next</strong></a></li></ul><div class="section" title="2.8.2.6. Activating the IPTables Service" id="sect-Security_Guide-Basic_Firewall_Configuration-Activating_the_IPTables_Service"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Basic_Firewall_Configu
ration-Activating_the_IPTables_Service">2.8.2.6. Activating the IPTables Service</h4></div></div></div><div class="para">
The firewall rules are only active if the <code class="command">iptables</code> service is running. To manually start the service, use the following command:
- </div><pre class="screen">[root at myServer ~] # service iptables restart
-</pre><div class="para">
+ </div><pre class="screen">[root at myServer ~] # service iptables restart</pre><div class="para">
To ensure that <code class="command">iptables</code> starts when the system is booted, use the following command:
- </div><pre class="screen">[root at myServer ~] # chkconfig --level 345 iptables on
-</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Basic_Firewall_Configuration-Saving_the_Settings.html"><strong>Prev</strong>2.8.2.5. Saving the Settings</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Firewalls-Using_IPTables.html"><strong>Next</strong>2.8.3. Using IPTables</a></li></ul></body></html>
+ </div><pre class="screen">[root at myServer ~] # chkconfig --level 345 iptables on</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Basic_Firewall_Configuration-Saving_the_Settings.html"><strong>Prev</strong>2.8.2.5. Saving the Settings</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Firewalls-Using_IPTables.html"><strong>Next</strong>2.8.3. Using IPTables</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Basic_Firewall_Configuration-Enabling_and_Disabling_the_Firewall.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Basic_Firewall_Configuration-Enabling_and_Disabling_the_Firewall.html
index 28c1e46..8b7db9f 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Basic_Firewall_Configuration-Enabling_and_Disabling_the_Firewall.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Basic_Firewall_Configuration-Enabling_and_Disabling_the_Firewall.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.2.2. Enabling and Disabling the Firewall</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Basic Firewall Configuration" /><link rel="prev" href="sect-Security_Guide-Firewalls-Basic_Firewall_Configuration.html" title="2.8.2. Basic Firewall Configuration" /><link rel="next" href="sect-Security_Guide-Basic_Firewall_Configuration-Trusted_Services.html" title="2.8.2.3. Trusted Services" /></head><body class="toc_embeded "><div id="tocdiv" class="toc
"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Firewalls-Basic_Firewall_Configuration.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Basic_Firewall_Configuration-Trusted_Services.html"><strong>Next</strong></a></li></ul><div class="section" title="2.8.2.2. Enabling and Disabling the Firewall" id="sect-Security_Guide-Basic_Firewall_Configuration-Enabling_and_Disabling_the_Firewall"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">
2.8.2.2. Enabling and Disabling the Firewall</h4></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.2.2. Enabling and Disabling the Firewall</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Basic Firewall Configuration" /><link rel="prev" href="sect-Security_Guide-Firewalls-Basic_Firewall_Configuration.html" title="2.8.2. Basic Firewall Configuration" /><link rel="next" href="sect-Security_Guide-Basic_Firewall_Configuration-Trusted_Services.html" title="2.8.2.3. Trusted Services" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"
><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Firewalls-Basic_Firewall_Configuration.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Basic_Firewall_Configuration-Trusted_Services.html"><strong>Next</strong></a></li></ul><div class="section" title="2.8.2.2. Enabling and Disabling the Firewall" id="sect-Security_Guide-Basic_Firewall_Configuration-Enabling_and_Disabling_the_Firewall"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" i
d="sect-Security_Guide-Basic_Firewall_Configuration-Enabling_and_Disabling_the_Firewall">2.8.2.2. Enabling and Disabling the Firewall</h4></div></div></div><div class="para">
Select one of the following options for the firewall:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<span class="guilabel"><strong>Disabled</strong></span> — Disabling the firewall provides complete access to your system and does no security checking. This should only be selected if you are running on a trusted network (not the Internet) or need to configure a custom firewall using the iptables command line tool.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Basic_Firewall_Configuration-Other_Ports.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Basic_Firewall_Configuration-Other_Ports.html
index 4c4b1e8..7cca738 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Basic_Firewall_Configuration-Other_Ports.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Basic_Firewall_Configuration-Other_Ports.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.2.4. Other Ports</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Basic Firewall Configuration" /><link rel="prev" href="sect-Security_Guide-Basic_Firewall_Configuration-Trusted_Services.html" title="2.8.2.3. Trusted Services" /><link rel="next" href="sect-Security_Guide-Basic_Firewall_Configuration-Saving_the_Settings.html" title="2.8.2.5. Saving the Settings" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocfram
e" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Basic_Firewall_Configuration-Trusted_Services.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Basic_Firewall_Configuration-Saving_the_Settings.html"><strong>Next</strong></a></li></ul><div class="section" title="2.8.2.4. Other Ports" id="sect-Security_Guide-Basic_Firewall_Configuration-Other_Ports"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.8.2.4. Other Ports</h4></div></div></div><div class="par
a">
+<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. Other Ports</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Basic Firewall Configuration" /><link rel="prev" href="sect-Security_Guide-Basic_Firewall_Configuration-Trusted_Services.html" title="2.8.2.3. Trusted Services" /><link rel="next" href="sect-Security_Guide-Basic_Firewall_Configuration-Saving_the_Settings.html" title="2.8.2.5. Saving the Settings" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe
" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Basic_Firewall_Configuration-Trusted_Services.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Basic_Firewall_Configuration-Saving_the_Settings.html"><strong>Next</strong></a></li></ul><div class="section" title="2.8.2.4. Other Ports" id="sect-Security_Guide-Basic_Firewall_Configuration-Other_Ports"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Basic_Firewall_Configuration-Other_P
orts">2.8.2.4. Other Ports</h4></div></div></div><div class="para">
The <span class="application"><strong>Firewall Configuration Tool</strong></span> includes an <span class="guilabel"><strong>Other ports</strong></span> section for specifying custom IP ports as being trusted by <code class="command">iptables</code>. For example, to allow IRC and Internet printing protocol (IPP) to pass through the firewall, add the following to the <span class="guilabel"><strong>Other ports</strong></span> section:
</div><div class="para">
<code class="computeroutput">194:tcp,631:tcp</code>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Basic_Firewall_Configuration-Saving_the_Settings.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Basic_Firewall_Configuration-Saving_the_Settings.html
index ea20536..d7bd5fd 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Basic_Firewall_Configuration-Saving_the_Settings.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Basic_Firewall_Configuration-Saving_the_Settings.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.2.5. Saving the Settings</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Basic Firewall Configuration" /><link rel="prev" href="sect-Security_Guide-Basic_Firewall_Configuration-Other_Ports.html" title="2.8.2.4. Other Ports" /><link rel="next" href="sect-Security_Guide-Basic_Firewall_Configuration-Activating_the_IPTables_Service.html" title="2.8.2.6. Activating the IPTables Service" /></head><body class="toc_embeded "><div id="tocdiv" class="to
c"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Basic_Firewall_Configuration-Other_Ports.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Basic_Firewall_Configuration-Activating_the_IPTables_Service.html"><strong>Next</strong></a></li></ul><div class="section" title="2.8.2.5. Saving the Settings" id="sect-Security_Guide-Basic_Firewall_Configuration-Saving_the_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.8.2.5. Savi
ng the Settings</h4></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.2.5. Saving the Settings</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Basic Firewall Configuration" /><link rel="prev" href="sect-Security_Guide-Basic_Firewall_Configuration-Other_Ports.html" title="2.8.2.4. Other Ports" /><link rel="next" href="sect-Security_Guide-Basic_Firewall_Configuration-Activating_the_IPTables_Service.html" title="2.8.2.6. Activating the IPTables Service" /></head><body class="toc_embeded "><div id="tocdiv" class="toc
"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Basic_Firewall_Configuration-Other_Ports.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Basic_Firewall_Configuration-Activating_the_IPTables_Service.html"><strong>Next</strong></a></li></ul><div class="section" title="2.8.2.5. Saving the Settings" id="sect-Security_Guide-Basic_Firewall_Configuration-Saving_the_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Securi
ty_Guide-Basic_Firewall_Configuration-Saving_the_Settings">2.8.2.5. Saving the Settings</h4></div></div></div><div class="para">
Click <span class="guibutton"><strong>OK</strong></span> to save the changes and enable or disable the firewall. If <span class="guilabel"><strong>Enable firewall</strong></span> was selected, the options selected are translated to <code class="command">iptables</code> commands and written to the <code class="filename">/etc/sysconfig/iptables</code> file. The <code class="command">iptables</code> service is also started so that the firewall is activated immediately after saving the selected options. If <span class="guilabel"><strong>Disable firewall</strong></span> was selected, the <code class="filename">/etc/sysconfig/iptables</code> file is removed and the <code class="command">iptables</code> service is stopped immediately.
</div><div class="para">
The selected options are also written to the <code class="filename">/etc/sysconfig/system-config-securitylevel</code> file so that the settings can be restored the next time the application is started. Do not edit this file by hand.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Basic_Firewall_Configuration-Trusted_Services.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Basic_Firewall_Configuration-Trusted_Services.html
index 8553e49..44963b3 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Basic_Firewall_Configuration-Trusted_Services.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Basic_Firewall_Configuration-Trusted_Services.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.2.3. Trusted Services</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Basic Firewall Configuration" /><link rel="prev" href="sect-Security_Guide-Basic_Firewall_Configuration-Enabling_and_Disabling_the_Firewall.html" title="2.8.2.2. Enabling and Disabling the Firewall" /><link rel="next" href="sect-Security_Guide-Basic_Firewall_Configuration-Other_Ports.html" title="2.8.2.4. Other Ports" /></head><body class="toc_embeded "><div id="tocdiv" clas
s="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Basic_Firewall_Configuration-Enabling_and_Disabling_the_Firewall.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Basic_Firewall_Configuration-Other_Ports.html"><strong>Next</strong></a></li></ul><div class="section" title="2.8.2.3. Trusted Services" id="sect-Security_Guide-Basic_Firewall_Configuration-Trusted_Services"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.8.2.3. T
rusted Services</h4></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.2.3. Trusted Services</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Basic Firewall Configuration" /><link rel="prev" href="sect-Security_Guide-Basic_Firewall_Configuration-Enabling_and_Disabling_the_Firewall.html" title="2.8.2.2. Enabling and Disabling the Firewall" /><link rel="next" href="sect-Security_Guide-Basic_Firewall_Configuration-Other_Ports.html" title="2.8.2.4. Other Ports" /></head><body class="toc_embeded "><div id="tocdiv" class
="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Basic_Firewall_Configuration-Enabling_and_Disabling_the_Firewall.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Basic_Firewall_Configuration-Other_Ports.html"><strong>Next</strong></a></li></ul><div class="section" title="2.8.2.3. Trusted Services" id="sect-Security_Guide-Basic_Firewall_Configuration-Trusted_Services"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Sec
urity_Guide-Basic_Firewall_Configuration-Trusted_Services">2.8.2.3. Trusted Services</h4></div></div></div><div class="para">
Enabling options in the <span class="guilabel"><strong>Trusted services</strong></span> list allows the specified service to pass through the firewall.
</div><div class="variablelist"><dl><dt><span class="term"><span class="guilabel"><strong>WWW (HTTP)</strong></span></span></dt><dd><div class="para">
The HTTP protocol is used by Apache (and by other Web servers) to serve web pages. If you plan on making your Web server publicly available, select this check box. This option is not required for viewing pages locally or for developing web pages. This service requires that the <code class="filename">httpd</code> package be installed.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Command_Options_for_IPTables-Command_Options.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Command_Options_for_IPTables-Command_Options.html
index 2eb8b8d..b16435e 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Command_Options_for_IPTables-Command_Options.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Command_Options_for_IPTables-Command_Options.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.9.2.2. Command Options</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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.2. Command Options for IPTables" /><link rel="prev" href="sect-Security_Guide-IPTables-Command_Options_for_IPTables.html" title="2.9.2. Command Options for IPTables" /><link rel="next" href="sect-Security_Guide-Command_Options_for_IPTables-IPTables_Parameter_Options.html" title="2.9.2.3. IPTables Parameter Options" /></head><body class="toc_embeded "><div id="tocdiv" class="toc">
<iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-IPTables-Command_Options_for_IPTables.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Command_Options_for_IPTables-IPTables_Parameter_Options.html"><strong>Next</strong></a></li></ul><div class="section" title="2.9.2.2. Command Options" id="sect-Security_Guide-Command_Options_for_IPTables-Command_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.9.2.2. Command Options</h4></d
iv></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.9.2.2. Command Options</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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.2. Command Options for IPTables" /><link rel="prev" href="sect-Security_Guide-IPTables-Command_Options_for_IPTables.html" title="2.9.2. Command Options for IPTables" /><link rel="next" href="sect-Security_Guide-Command_Options_for_IPTables-IPTables_Parameter_Options.html" title="2.9.2.3. IPTables Parameter Options" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><
iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-IPTables-Command_Options_for_IPTables.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Command_Options_for_IPTables-IPTables_Parameter_Options.html"><strong>Next</strong></a></li></ul><div class="section" title="2.9.2.2. Command Options" id="sect-Security_Guide-Command_Options_for_IPTables-Command_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Command_Op
tions_for_IPTables-Command_Options">2.9.2.2. Command Options</h4></div></div></div><div class="para">
Command options instruct <code class="command">iptables</code> to perform a specific action. Only one command option is allowed per <code class="command">iptables</code> command. With the exception of the help command, all commands are written in upper-case characters.
</div><div class="para">
The <code class="command">iptables</code> commands are as follows:
@@ -26,8 +26,7 @@
This is especially important when adding rules using the <code class="option">-I</code> with an integer argument. If you specify an existing number when adding a rule to a chain, <code class="command">iptables</code> adds the new rule <span class="emphasis"><em>before</em></span> (or above) the existing rule.
</div></div></li><li class="listitem"><div class="para">
<code class="option">-L</code> — Lists all of the rules in the chain specified after the command. To list all rules in all chains in the default <code class="option">filter</code> table, do not specify a chain or table. Otherwise, the following syntax should be used to list the rules in a specific chain in a particular table:
- </div><pre class="screen"><code class="computeroutput"> iptables -L <em class="replaceable"><code><chain-name></code></em> -t <em class="replaceable"><code><table-name></code></em></code>
-</pre><div class="para">
+ </div><pre class="screen"><code class="computeroutput"> iptables -L <em class="replaceable"><code><chain-name></code></em> -t <em class="replaceable"><code><table-name></code></em></code></pre><div class="para">
Additional options for the <code class="option">-L</code> command option, which provide rule numbers and allow more verbose rule descriptions, are described in <a class="xref" href="sect-Security_Guide-Command_Options_for_IPTables-Listing_Options.html" title="2.9.2.6. Listing Options">Section 2.9.2.6, “Listing Optionsâ€</a>.
</div></li><li class="listitem"><div class="para">
<code class="option">-N</code> — Creates a new chain with a user-specified name. The chain name must be unique, otherwise an error message is displayed.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Command_Options_for_IPTables-IPTables_Match_Options.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Command_Options_for_IPTables-IPTables_Match_Options.html
index 3d25140..4239215 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Command_Options_for_IPTables-IPTables_Match_Options.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Command_Options_for_IPTables-IPTables_Match_Options.html
@@ -1,20 +1,17 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.4. IPTables Match Options</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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.2. Command Options for IPTables" /><link rel="prev" href="sect-Security_Guide-Command_Options_for_IPTables-IPTables_Parameter_Options.html" title="2.9.2.3. IPTables Parameter Options" /><link rel="next" href="sect-Security_Guide-IPTables_Match_Options-UDP_Protocol.html" title="2.9.2.4.2. UDP Protocol" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Command_Options_for_IPTables-IPTables_Parameter_Options.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-IPTables_Match_Options-UDP_Protocol.html"><strong>Next</strong></a></li></ul><div class="section" title="2.9.2.4. IPTables Match Options" id="sect-Security_Guide-Command_Options_for_IPTables-IPTables_Match_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.9.2.4. IPTables Match Opt
ions</h4></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.9.2.4. IPTables Match Options</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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.2. Command Options for IPTables" /><link rel="prev" href="sect-Security_Guide-Command_Options_for_IPTables-IPTables_Parameter_Options.html" title="2.9.2.3. IPTables Parameter Options" /><link rel="next" href="sect-Security_Guide-IPTables_Match_Options-UDP_Protocol.html" title="2.9.2.4.2. UDP Protocol" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Command_Options_for_IPTables-IPTables_Parameter_Options.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-IPTables_Match_Options-UDP_Protocol.html"><strong>Next</strong></a></li></ul><div class="section" title="2.9.2.4. IPTables Match Options" id="sect-Security_Guide-Command_Options_for_IPTables-IPTables_Match_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Comma
nd_Options_for_IPTables-IPTables_Match_Options">2.9.2.4. IPTables Match Options</h4></div></div></div><div class="para">
Different network protocols provide specialized matching options which can be configured to match a particular packet using that protocol. However, the protocol must first be specified in the <code class="command">iptables</code> command. For example, <code class="option">-p <em class="replaceable"><code><protocol-name></code></em></code> enables options for the specified protocol. Note that you can also use the protocol ID, instead of the protocol name. Refer to the following examples, each of which have the same effect:
- </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">
+ </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">
Service definitions are provided in the <code class="filename">/etc/services</code> file. For readability, it is recommended that you use the service names rather than the port numbers.
</div><div class="warning"><h2>Warning</h2><div class="para">
Secure the <code class="filename">/etc/services</code> file to prevent unauthorized editing. If this file is editable, crackers can use it to enable ports on your machine you have otherwise closed. To secure this file, type the following commands as 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">
+[root at myServer ~]# chattr +i /etc/services</pre><div class="para">
This prevents the file from being renamed, deleted or having links made to it.
- </div></div><div class="section" title="2.9.2.4.1. TCP Protocol" id="sect-Security_Guide-IPTables_Match_Options-TCP_Protocol"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.9.2.4.1. TCP Protocol</h5></div></div></div><div class="para">
+ </div></div><div class="section" title="2.9.2.4.1. TCP Protocol" id="sect-Security_Guide-IPTables_Match_Options-TCP_Protocol"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-Security_Guide-IPTables_Match_Options-TCP_Protocol">2.9.2.4.1. TCP Protocol</h5></div></div></div><div class="para">
These match options are available for the TCP protocol (<code class="option">-p tcp</code>):
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="option">--dport</code> — Sets the destination port for the packet.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Command_Options_for_IPTables-IPTables_Parameter_Options.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Command_Options_for_IPTables-IPTables_Parameter_Options.html
index 811d419..5f6d50f 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Command_Options_for_IPTables-IPTables_Parameter_Options.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Command_Options_for_IPTables-IPTables_Parameter_Options.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.9.2.3. IPTables Parameter Options</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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.2. Command Options for IPTables" /><link rel="prev" href="sect-Security_Guide-Command_Options_for_IPTables-Command_Options.html" title="2.9.2.2. Command Options" /><link rel="next" href="sect-Security_Guide-Command_Options_for_IPTables-IPTables_Match_Options.html" title="2.9.2.4. IPTables Match Options" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><
iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Command_Options_for_IPTables-Command_Options.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Command_Options_for_IPTables-IPTables_Match_Options.html"><strong>Next</strong></a></li></ul><div class="section" title="2.9.2.3. IPTables Parameter Options" id="sect-Security_Guide-Command_Options_for_IPTables-IPTables_Parameter_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.9.2.3.Â
IPTables Parameter Options</h4></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.9.2.3. IPTables Parameter Options</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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.2. Command Options for IPTables" /><link rel="prev" href="sect-Security_Guide-Command_Options_for_IPTables-Command_Options.html" title="2.9.2.2. Command Options" /><link rel="next" href="sect-Security_Guide-Command_Options_for_IPTables-IPTables_Match_Options.html" title="2.9.2.4. IPTables Match Options" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><i
frame id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Command_Options_for_IPTables-Command_Options.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Command_Options_for_IPTables-IPTables_Match_Options.html"><strong>Next</strong></a></li></ul><div class="section" title="2.9.2.3. IPTables Parameter Options" id="sect-Security_Guide-Command_Options_for_IPTables-IPTables_Parameter_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-S
ecurity_Guide-Command_Options_for_IPTables-IPTables_Parameter_Options">2.9.2.3. IPTables Parameter Options</h4></div></div></div><div class="para">
Certain <code class="command">iptables</code> commands, including those used to add, append, delete, insert, or replace rules within a particular chain, require various parameters to construct a packet filtering rule.
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="option">-c</code> — Resets the counters for a particular rule. This parameter accepts the <code class="option">PKTS</code> and <code class="option">BYTES</code> options to specify which counter to reset.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Command_Options_for_IPTables-Listing_Options.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Command_Options_for_IPTables-Listing_Options.html
index 13664dc..d06a593 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Command_Options_for_IPTables-Listing_Options.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Command_Options_for_IPTables-Listing_Options.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.9.2.6. Listing Options</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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.2. Command Options for IPTables" /><link rel="prev" href="sect-Security_Guide-Command_Options_for_IPTables-Target_Options.html" title="2.9.2.5. Target Options" /><link rel="next" href="sect-Security_Guide-IPTables-Saving_IPTables_Rules.html" title="2.9.3. Saving IPTables Rules" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src=
"../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Command_Options_for_IPTables-Target_Options.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-IPTables-Saving_IPTables_Rules.html"><strong>Next</strong></a></li></ul><div class="section" title="2.9.2.6. Listing Options" id="sect-Security_Guide-Command_Options_for_IPTables-Listing_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.9.2.6. Listing Options</h4></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.9.2.6. Listing Options</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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.2. Command Options for IPTables" /><link rel="prev" href="sect-Security_Guide-Command_Options_for_IPTables-Target_Options.html" title="2.9.2.5. Target Options" /><link rel="next" href="sect-Security_Guide-IPTables-Saving_IPTables_Rules.html" title="2.9.3. Saving IPTables Rules" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="
../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Command_Options_for_IPTables-Target_Options.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-IPTables-Saving_IPTables_Rules.html"><strong>Next</strong></a></li></ul><div class="section" title="2.9.2.6. Listing Options" id="sect-Security_Guide-Command_Options_for_IPTables-Listing_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Command_Options_for_IPTables-Listing_Options">2.9.2.6. Listing Opt
ions</h4></div></div></div><div class="para">
The default list command, <code class="command">iptables -L [<chain-name>]</code>, provides a very basic overview of the default filter table's current chains. Additional options provide more information:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="option">-v</code> — Displays verbose output, such as the number of packets and bytes each chain has processed, the number of packets and bytes each rule has matched, and which interfaces apply to a particular rule.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Command_Options_for_IPTables-Target_Options.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Command_Options_for_IPTables-Target_Options.html
index 0b2f1d7..ba2f2f3 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Command_Options_for_IPTables-Target_Options.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Command_Options_for_IPTables-Target_Options.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.9.2.5. Target Options</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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.2. Command Options for IPTables" /><link rel="prev" href="sect-Security_Guide-IPTables_Match_Options-Additional_Match_Option_Modules.html" title="2.9.2.4.4. Additional Match Option Modules" /><link rel="next" href="sect-Security_Guide-Command_Options_for_IPTables-Listing_Options.html" title="2.9.2.6. Listing Options" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"
><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-IPTables_Match_Options-Additional_Match_Option_Modules.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Command_Options_for_IPTables-Listing_Options.html"><strong>Next</strong></a></li></ul><div class="section" title="2.9.2.5. Target Options" id="sect-Security_Guide-Command_Options_for_IPTables-Target_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.9.2.5. Target Options</h4
></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.9.2.5. Target Options</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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.2. Command Options for IPTables" /><link rel="prev" href="sect-Security_Guide-IPTables_Match_Options-Additional_Match_Option_Modules.html" title="2.9.2.4.4. Additional Match Option Modules" /><link rel="next" href="sect-Security_Guide-Command_Options_for_IPTables-Listing_Options.html" title="2.9.2.6. Listing Options" /></head><body class="toc_embeded "><div id="tocdiv" class="toc">
<iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-IPTables_Match_Options-Additional_Match_Option_Modules.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Command_Options_for_IPTables-Listing_Options.html"><strong>Next</strong></a></li></ul><div class="section" title="2.9.2.5. Target Options" id="sect-Security_Guide-Command_Options_for_IPTables-Target_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Comma
nd_Options_for_IPTables-Target_Options">2.9.2.5. Target Options</h4></div></div></div><div class="para">
When a packet has matched a particular rule, the rule can direct the packet to a number of different targets which determine the appropriate action. Each chain has a default target, which is used if none of the rules on that chain match a packet or if none of the rules which match the packet specify a target.
</div><div class="para">
The following are the standard targets:
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Common_Exploits_and_Attacks.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Common_Exploits_and_Attacks.html
index 570a290..c6f167d 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Common_Exploits_and_Attacks.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Common_Exploits_and_Attacks.html
@@ -1,8 +1,8 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. Common Exploits and Attacks</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="chap-Security_Guide-Security_Overview.html" title="Chapter 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. Security Updates" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="t
oc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Threats_to_Workstation_and_Home_PC_Security-Vulnerable_Client_Applications.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Security_Updates.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" title="1.4. Common Exploits and Attacks" id="sect-Security_Guide-Common_Exploits_and_Attacks" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">1.4. Common Exploits and Attacks</h2></div>
</div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.4. Common Exploits and Attacks</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="chap-Security_Guide-Security_Overview.html" title="Chapter 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. Security Updates" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="to
c" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Threats_to_Workstation_and_Home_PC_Security-Vulnerable_Client_Applications.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Security_Updates.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" title="1.4. Common Exploits and Attacks" id="sect-Security_Guide-Common_Exploits_and_Attacks" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sect-Security_Guide-Common_Exploits_and_A
ttacks">1.4. Common Exploits and Attacks</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="Table 1.1. Common Exploits">Table 1.1, “Common Exploitsâ€</a> details some of the most common exploits and entry points used by intruders to access organizational network resources. Key to these common exploits are the explanations of how they are performed and how administrators can properly safeguard their network against such attacks.
- </div><div class="table"><div class="table-contents"><table summary="Common Exploits" border="1"><colgroup><col width="20%" /><col width="40%" /><col width="40%" /></colgroup><thead><tr><th>
+ </div><div class="table" title="Table 1.1. Common Exploits" id="tabl-Security_Guide-Common_Exploits_and_Attacks-Common_Exploits"><div class="table-contents"><table summary="Common Exploits" border="1"><colgroup><col width="20%" /><col width="40%" /><col width="40%" /></colgroup><thead><tr><th>
Exploit
</th><th>
Description
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Installation-Instructions.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Installation-Instructions.html
index db075cd..627d39e 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Installation-Instructions.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Installation-Instructions.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.8.2. Step-by-Step Installation Instructions</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class
="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Usage_Instructions.html"><strong>Next</strong></a></li></ul><div class="section" title="3.8.2. Step-by-Step Installation Instructions" id="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Installation-Instructions"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class
="title">3.8.2. Step-by-Step Installation Instructions</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.8.2. Step-by-Step Installation Instructions</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class=
"toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Usage_Instructions.html"><strong>Next</strong></a></li></ul><div class="section" title="3.8.2. Step-by-Step Installation Instructions" id="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Installation-Instructions"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><div class="para">
Open a Terminal: <code class="code">Click ''Applications'' -> ''System Tools'' -> ''Terminal''</code>
</div></li><li class="listitem"><div class="para">
Install 7-Zip with sudo access: <code class="code">sudo yum install p7zip</code>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Things_of_note.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Things_of_note.html
index ddadcb1..49f6a9c 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Things_of_note.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Things_of_note.html
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" cla
ss="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Usage_Instructions.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-Using_GPG.html"><strong>Next</strong></a></li></ul><div class="section" title="3.8.4. Things of note" id="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Things_of_note"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.8.4. Things of note</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.8.4. Things of note</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" clas
s="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Usage_Instructions.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-Using_GPG.html"><strong>Next</strong></a></li></ul><div class="section" title="3.8.4. Things of note" id="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Things_of_note"><div class="titlepage"><div><div keep-together.within-column="always"><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><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Usage_Instructions.html"><strong>Prev</strong>3.8.3. Step-by-Step Usage Instructions</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-Using_GPG.html"><strong>Next</strong>3.9. Using GNU Privacy Guard (GnuPG)</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Usage_Instructions.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Usage_Instructions.html
index 6828af7..7c62d9f 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Usage_Instructions.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Usage_Instructions.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.8.3. Step-by-Step Usage Instructions</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id=
"tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Installation-Instructions.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Things_of_note.html"><strong>Next</strong></a></li></ul><div class="section" title="3.8.3. Step-by-Step Usage Instructions" id="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Usage_Instructions"><div class="titlepage"><div><div keep-together.within-col
umn="always"><h3 class="title">3.8.3. Step-by-Step Usage Instructions</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.8.3. Step-by-Step Usage Instructions</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="
tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Installation-Instructions.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Things_of_note.html"><strong>Next</strong></a></li></ul><div class="section" title="3.8.3. Step-by-Step Usage Instructions" id="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Usage_Instructions"><div class="titlepage"><div><div keep-together.within-colu
mn="always"><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 class="listitem"><div class="para">
Open a Terminal:<code class="code">Click ''Applications'' -> ''System Tools'' -> ''Terminal''</code>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives.html
index 563ffd7..58c3003 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives.html
@@ -1,7 +1,7 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.8. 7-Zip Encrypted Archives</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="chap-Security_Guide-Encryption.html" title="Chapter 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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="
toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-LUKS_Disk_Encryption-Links_of_Interest.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Installation-Instructions.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" title="3.8. 7-Zip Encrypted Archives" id="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">3.8. 7-Zip Encrypted Archive
s</h2></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.8. 7-Zip Encrypted Archives</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="chap-Security_Guide-Encryption.html" title="Chapter 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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="t
oc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-LUKS_Disk_Encryption-Links_of_Interest.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Installation-Instructions.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" title="3.8. 7-Zip Encrypted Archives" id="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sect-Security_Guide-Encryp
tion-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" title="3.8.1. 7-Zip Installation in Fedora" id="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Installation"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.8.1. 7-Zip Installation in Fedora</h3></div></div></div><div class="para">
+ </div><div class="section" title="3.8.1. 7-Zip Installation in Fedora" id="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Installation"><div class="titlepage"><div><div keep-together.within-column="always"><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>Prev</strong>3.7.5. Links of Interest</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Installation-Instructions.html"><strong>Next</strong>3.8.2. Step-by-Step Installation Instructions</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-Protecting_Data_at_Rest-Full_Disk_Encryption.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-Protecting_Data_at_Rest-Full_Disk_Encryption.html
index 5a74634..b9eec88 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-Protecting_Data_at_Rest-Full_Disk_Encryption.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-Protecting_Data_at_Rest-Full_Disk_Encryption.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.2. Full Disk Encryption</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="chap-Security_Guide-Encryption.html" title="Chapter 3. Encryption" /><link rel="prev" href="chap-Security_Guide-Encryption.html" title="Chapter 3. Encryption" /><link rel="next" href="Security_Guide-Encryption-Protecting_Data_at_Rest-File_Based_Encryption.html" title="3.3. File Based Encryption" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it u
pgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security_Guide-Encryption.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="Security_Guide-Encryption-Protecting_Data_at_Rest-File_Based_Encryption.html"><strong>Next</strong></a></li></ul><div class="section" title="3.2. Full Disk Encryption" id="sect-Security_Guide-Encryption-Protecting_Data_at_Rest-Full_Disk_Encryption"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">3.2. Full Disk Encryption</h2></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.2. Full Disk Encryption</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="chap-Security_Guide-Encryption.html" title="Chapter 3. Encryption" /><link rel="prev" href="chap-Security_Guide-Encryption.html" title="Chapter 3. Encryption" /><link rel="next" href="Security_Guide-Encryption-Protecting_Data_at_Rest-File_Based_Encryption.html" title="3.3. File Based Encryption" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it up
grade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security_Guide-Encryption.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="Security_Guide-Encryption-Protecting_Data_at_Rest-File_Based_Encryption.html"><strong>Next</strong></a></li></ul><div class="section" title="3.2. Full Disk Encryption" id="sect-Security_Guide-Encryption-Protecting_Data_at_Rest-Full_Disk_Encryption"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sect-Security_Guide-Encryption-Protecting_Data_at_Rest-Full_Disk_Encryption">3.2. Full Disk Encryption</h2></div></div></div><div class="par
a">
Full disk or partition encryption is one of the best ways of protecting your data. Not only is each file protected but also the temporary storage that may contain parts of these files is also protected. Full disk encryption will protect all of your files so you don't have to worry about selecting what you want to protect and possibly missing a file.
</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.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-Using_GPG-About_Public_Key_Encryption.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-Using_GPG-About_Public_Key_Encryption.html
index ebd3389..2d587f5 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-Using_GPG-About_Public_Key_Encryption.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-Using_GPG-About_Public_Key_Encryption.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.9.7. About Public Key Encryption</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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-Using_GPG_with_Thunderbird.html" title="3.9.6. Using GPG with Thunderbird" /><link rel="next" href="chap-Security_Guide-General_Principles_of_Information_Security.html" title="Chapter 4. General Principles of Information Security" /></head><body class="toc_embeded "><div id="tocdiv" clas
s="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Thunderbird.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Security_Guide-General_Principles_of_Information_Security.html"><strong>Next</strong></a></li></ul><div class="section" title="3.9.7. About Public Key Encryption" id="sect-Security_Guide-Encryption-Using_GPG-About_Public_Key_Encryption"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.9.7. About
Public Key Encryption</h3></div></div></div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.9.7. About Public Key Encryption</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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-Using_GPG_with_Thunderbird.html" title="3.9.6. Using GPG with Thunderbird" /><link rel="next" href="chap-Security_Guide-General_Principles_of_Information_Security.html" title="Chapter 4. General Principles of Information Security" /></head><body class="toc_embeded "><div id="tocdiv" class
="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Thunderbird.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Security_Guide-General_Principles_of_Information_Security.html"><strong>Next</strong></a></li></ul><div class="section" title="3.9.7. About Public Key Encryption" id="sect-Security_Guide-Encryption-Using_GPG-About_Public_Key_Encryption"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Securi
ty_Guide-Encryption-Using_GPG-About_Public_Key_Encryption">3.9.7. About Public Key Encryption</h3></div></div></div><div class="orderedlist"><ol><li class="listitem"><div class="para">
<a href="http://en.wikipedia.org/wiki/Public-key_cryptography">Wikipedia - Public Key Cryptography</a>
</div></li><li class="listitem"><div class="para">
<a href="http://computer.howstuffworks.com/encryption.htm">HowStuffWorks - Encryption</a>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE.html
index 040ebae..3b13d0a 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.9.3. Generating GPG Keys Using the Command Line</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Generating GPG Keys in KDE" /><link rel="next" href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Alpine.html" title="3.9.4. Using GPG with Alpine" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><ifr
ame id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE1.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Alpine.html"><strong>Next</strong></a></li></ul><div class="section" title="3.9.3. Generating GPG Keys Using the Command Line" id="sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.9.3. Generat
ing GPG Keys Using the Command Line</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.9.3. Generating GPG Keys Using the Command Line</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Generating GPG Keys in KDE" /><link rel="next" href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Alpine.html" title="3.9.4. Using GPG with Alpine" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><ifra
me id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE1.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Alpine.html"><strong>Next</strong></a></li></ul><div class="section" title="3.9.3. Generating GPG Keys Using the Command Line" id="sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Securit
y_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE">3.9.3. Generating 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.
@@ -32,7 +32,6 @@
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">
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE1.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE1.html
index 7d28207..ae284c5 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE1.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE1.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.9.2. Generating GPG Keys in KDE</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Generating GPG Keys Using the Command Line" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocfram
e" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Encryption-Using_GPG.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE.html"><strong>Next</strong></a></li></ul><div class="section" title="3.9.2. Generating GPG Keys in KDE" id="sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE1"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.9.2. Generating GPG Keys in KDE</h3></div></div></div><div class=
"para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.9.2. Generating GPG Keys in KDE</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Generating GPG Keys Using the Command Line" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe
" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Encryption-Using_GPG.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE.html"><strong>Next</strong></a></li></ul><div class="section" title="3.9.2. Generating GPG Keys in KDE" id="sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE1"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE
1">3.9.2. Generating 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.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Alpine.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Alpine.html
index 86d1362..22922fb 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Alpine.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Alpine.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.9.4. Using GPG with Alpine</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Generating GPG Keys Using the Command Line" /><link rel="next" href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution.html" title="3.9.5. Using GPG with Evolution" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><ifr
ame id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution.html"><strong>Next</strong></a></li></ul><div class="section" title="3.9.4. Using GPG with Alpine" id="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Alpine"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.9.4. Using GPG with Alpine</h3></d
iv></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.9.4. Using GPG with Alpine</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Generating GPG Keys Using the Command Line" /><link rel="next" href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution.html" title="3.9.5. Using GPG with Evolution" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><ifra
me id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution.html"><strong>Next</strong></a></li></ul><div class="section" title="3.9.4. Using GPG with Alpine" id="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Alpine"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Encryption-Usi
ng_GPG-Using_GPG_with_Alpine">3.9.4. Using GPG with Alpine</h3></div></div></div><div class="para">
If you are using the email client <span class="package">Alpine</span> or <span class="package">Pine</span> then you will also need to download and install <span class="package">ez-pine-gpg</span>. This software is currently available from <a href="http://business-php.com/opensource/ez-pine-gpg/">http://business-php.com/opensource/ez-pine-gpg/</a>. Once you have installed ez-pine-gpg you will need to modify your <code class="code">~/.pinerc</code> file. You need to:
</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
/home/username/bin should be replaced with the installation path that you specified.
@@ -18,5 +18,4 @@ display-filters=_LEADING("-----BEGIN PGP")_ /home/max/bin/ez-pine-gpg-incoming
sending-filters=/home/max/bin/ez-pine-gpg-sign _INCLUDEALLHDRS_,
/home/username/bin/ez-pine-gpg-encrypt _RECIPIENTS_ gpg-identifier,
/home/username/bin/ez-pine-gpg-sign-and-encrypt _INCLUDEALLHDRS_ _RECIPIENTS_ gpg-identifier
-
</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE.html"><strong>Prev</strong>3.9.3. Generating GPG Keys Using the Command Line</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution.html"><strong>Next</strong>3.9.5. Using GPG with Evolution</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution-Signing_and_Encrypting.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution-Signing_and_Encrypting.html
index 0252697..74575b9 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution-Signing_and_Encrypting.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution-Signing_and_Encrypting.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.9.5.3. Signing and Encrypting email with Evolution</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution.html" title="3.9.5. Using GPG with Evolution" /><link rel="prev" href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution-Verifying.html" title="3.9.5.2. Verifying email with Evolution" /><link rel="next" href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Thunderbird.html" title="3.9.6. Using GPG with Thunderbird" /></head><body class=
"toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution-Verifying.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Thunderbird.html"><strong>Next</strong></a></li></ul><div class="section" title="3.9.5.3. Signing and Encrypting email with Evolution" id="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution-Signing_and_Encrypting"><div class="tit
lepage"><div><div keep-together.within-column="always"><h4 class="title">3.9.5.3. Signing and Encrypting email with Evolution</h4></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.9.5.3. Signing and Encrypting email with Evolution</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution.html" title="3.9.5. Using GPG with Evolution" /><link rel="prev" href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution-Verifying.html" title="3.9.5.2. Verifying email with Evolution" /><link rel="next" href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Thunderbird.html" title="3.9.6. Using GPG with Thunderbird" /></head><body class="
toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution-Verifying.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Thunderbird.html"><strong>Next</strong></a></li></ul><div class="section" title="3.9.5.3. Signing and Encrypting email with Evolution" id="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution-Signing_and_Encrypting"><div class="titl
epage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution-Signing_and_Encrypting">3.9.5.3. Signing and Encrypting email with Evolution</h4></div></div></div><div class="para">
Signing email allows the recipients to verify that the email actually came from you. The FDP (and the whole of the Fedora Project) encourage you to sign email to other participants, including on Fedora mailing lists. Encrypting email allows only your recipients to read your email. Please do not send encrypted email over the Fedora mailing lists, since almost no one will be able to read it.
</div><div class="para">
While composing your email, choose the Security menu, and then select PGP Sign to sign your message. To encrypt your message, select PGP Encrypt. You may sign an encrypted message as well, which is good practice. When you send the message, Evolution will ask you to enter your GPG key passphrase. (After three unsuccessful attempts Evolution generates an error.) If you select the option Remember this password for the remainder of this session, you will not need to use your passphrase again to sign or decrypt, unless you quit and restart Evolution.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution-Verifying.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution-Verifying.html
index 36a3d5a..e19121b 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution-Verifying.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution-Verifying.html
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.5.2. Verifying email with Evolution</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution.html" title="3.9.5. Using GPG with Evolution" /><link rel="prev" href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution.html" title="3.9.5. Using GPG with Evolution" /><link rel="next" href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution-Signing_and_Encrypting.html" title="3.9.5.3. Signing and Encrypting email with Evolution" /></head><bo
dy class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution-Signing_and_Encrypting.html"><strong>Next</strong></a></li></ul><div class="section" title="3.9.5.2. Verifying email with Evolution" id="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution-Verifying"><div class="titlepage
"><div><div keep-together.within-column="always"><h4 class="title">3.9.5.2. Verifying email with Evolution</h4></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.9.5.2. Verifying email with Evolution</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution.html" title="3.9.5. Using GPG with Evolution" /><link rel="prev" href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution.html" title="3.9.5. Using GPG with Evolution" /><link rel="next" href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution-Signing_and_Encrypting.html" title="3.9.5.3. Signing and Encrypting email with Evolution" /></head><bod
y class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution-Signing_and_Encrypting.html"><strong>Next</strong></a></li></ul><div class="section" title="3.9.5.2. Verifying email with Evolution" id="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution-Verifying"><div class="titlepage"
><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution-Verifying">3.9.5.2. Verifying email with Evolution</h4></div></div></div><div class="para">
Evolution will automatically check any incoming GPG-signed messages for validity. If Evolution cannot GPG verify a message due to a missing public key (or tampering), it will end with a red banner. If the message is verified but you have not signed the key either locally or globally, the banner will be yellow. If the message is verified and you have signed the key, the banner will be green. When you click the seal icon, Evolution displays a dialog with more security information about the signature. To add a public key to your keyring, use the search function along with the key owner's email address: <code class="code">gpg --keyserver pgp.mit.edu --search email address</code>. To import the correct key, you may need to match the key ID with the information provided by Evolution.
</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution.html"><strong>Prev</strong>3.9.5. Using GPG with Evolution</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution-Signing_and_Encrypting.html"><strong>Next</strong>3.9.5.3. Signing and Encrypting email with Evolut...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution.html
index f49fb31..f11c1c2 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.9.5. Using GPG with Evolution</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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-Using_GPG_with_Alpine.html" title="3.9.4. Using GPG with Alpine" /><link rel="next" href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution-Verifying.html" title="3.9.5.2. Verifying email with Evolution" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Alpine.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution-Verifying.html"><strong>Next</strong></a></li></ul><div class="section" title="3.9.5. Using GPG with Evolution" id="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.9.5. Using GPG with Evol
ution</h3></div></div></div><div class="section" title="3.9.5.1. Configuring GPG for use with Evolution" id="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution-Configuring"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">3.9.5.1. Configuring GPG for use with Evolution</h4></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.9.5. Using GPG with Evolution</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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-Using_GPG_with_Alpine.html" title="3.9.4. Using GPG with Alpine" /><link rel="next" href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution-Verifying.html" title="3.9.5.2. Verifying email with Evolution" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Alpine.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution-Verifying.html"><strong>Next</strong></a></li></ul><div class="section" title="3.9.5. Using GPG with Evolution" id="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Encr
yption-Using_GPG-Using_GPG_with_Evolution">3.9.5. Using GPG with Evolution</h3></div></div></div><div class="section" title="3.9.5.1. Configuring GPG for use with Evolution" id="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution-Configuring"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution-Configuring">3.9.5.1. Configuring GPG for use with Evolution</h4></div></div></div><div class="para">
To configure GPG for use in <span class="application"><strong>Evolution</strong></span> select from the <span class="application"><strong>Evolution</strong></span> Main Menu, select Tools, Settings... In the left pane, select Mail Accounts. In the right pane, select the email account you use for Fedora Project correspondence. Then select the Edit button. The <span class="application"><strong>Evolution</strong></span> Account Editor dialog appears. Select the Security tab.
</div><div class="para">
In the PGP/GPG Key ID field, enter the GPG key ID matching this account's email address. If you are not sure what your key ID is, use this command: <code class="code">gpg --fingerprint EMAIL_ADDRESS</code>. The key ID is the same as the last eight characters (4 bytes) of the key fingerprint. It is a good idea to click the option Always encrypt to myself when sending encrypted mail. You may also want to select Always sign outgoing messages when using this account.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Thunderbird.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Thunderbird.html
index 585e0a8..f8f3c9c 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Thunderbird.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Thunderbird.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.9.6. Using GPG with Thunderbird</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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-Using_GPG_with_Evolution-Signing_and_Encrypting.html" title="3.9.5.3. Signing and Encrypting email with Evolution" /><link rel="next" href="sect-Security_Guide-Encryption-Using_GPG-About_Public_Key_Encryption.html" title="3.9.7. About Public Key Encryption" /></head><body class="toc_embede
d "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution-Signing_and_Encrypting.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-Using_GPG-About_Public_Key_Encryption.html"><strong>Next</strong></a></li></ul><div class="section" title="3.9.6. Using GPG with Thunderbird" id="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Thunderbird"><div class="titlepage"><div><div keep-together.withi
n-column="always"><h3 class="title">3.9.6. Using GPG with Thunderbird</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.9.6. Using GPG with Thunderbird</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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-Using_GPG_with_Evolution-Signing_and_Encrypting.html" title="3.9.5.3. Signing and Encrypting email with Evolution" /><link rel="next" href="sect-Security_Guide-Encryption-Using_GPG-About_Public_Key_Encryption.html" title="3.9.7. About Public Key Encryption" /></head><body class="toc_embeded
"><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution-Signing_and_Encrypting.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-Using_GPG-About_Public_Key_Encryption.html"><strong>Next</strong></a></li></ul><div class="section" title="3.9.6. Using GPG with Thunderbird" id="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Thunderbird"><div class="titlepage"><div><div keep-together.within
-column="always"><h3 class="title" id="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Thunderbird">3.9.6. Using GPG with Thunderbird</h3></div></div></div><div class="para">
Fedora Core includes Mozilla Thunderbird in the thunderbird package, and the mozilla-mail package for the Mozilla Suite email application. Thunderbird is the recommended Mozilla email application. This appears on your desktop as Applications > Internet > Thunderbird Email.
</div><div class="para">
Mozilla products support extensions, plugins that add new features to the main application. The Enigmail extensions provide GPG support to email products from Mozilla. Versions of Enigmail exist for both Mozilla Thunderbird, and the Mozilla Suite (Seamonkey). Netscape software from AOL is based on the Mozilla products, and may also use this extension.
@@ -12,6 +12,6 @@
The homepage for Enigmail is: <a href="http://enigmail.mozdev.org/download.html">http://enigmail.mozdev.org/download.html</a>.
</div><div class="para">
This page provides screenshots of Enigmail and GPG in action: <a href="http://enigmail.mozdev.org/screenshots.html">http://enigmail.mozdev.org/screenshots.html</a>.
- </div><div class="section" title="3.9.6.1. Installing Enigmail" id="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Thunderbird-Installing_Enigmail"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">3.9.6.1. Installing Enigmail</h4></div></div></div><div class="para">
+ </div><div class="section" title="3.9.6.1. Installing Enigmail" id="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Thunderbird-Installing_Enigmail"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Thunderbird-Installing_Enigmail">3.9.6.1. Installing Enigmail</h4></div></div></div><div class="para">
Enigmail is now available in fedora repository. It can be installed by typing: <code class="code">yum install thunderbird-enigmail</code> at a command line. Alternatively, you can install <span class="package">thunderbird-enigmail</span> using by going to <code class="code">System -> Administration -> Add/Remove Software</code>.
</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Encryption-Using_GPG-Using_GPG_with_Evolution-Signing_and_Encrypting.html"><strong>Prev</strong>3.9.5.3. Signing and Encrypting email with Evolut...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-Using_GPG-About_Public_Key_Encryption.html"><strong>Next</strong>3.9.7. About Public Key Encryption</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-Using_GPG.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-Using_GPG.html
index 81e7b60..1c0e318 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-Using_GPG.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Encryption-Using_GPG.html
@@ -1,12 +1,12 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.9. Using GNU Privacy Guard (GnuPG)</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="chap-Security_Guide-Encryption.html" title="Chapter 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. Generating GPG Keys in KDE" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src=".
./../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Things_of_note.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE1.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" title="3.9. Using GNU Privacy Guard (GnuPG)" id="sect-Security_Guide-Encryption-Using_GPG" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">3.9. Using GNU Privacy Guard (GnuPG)</h2></div></d
iv></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.9. Using GNU Privacy Guard (GnuPG)</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="chap-Security_Guide-Encryption.html" title="Chapter 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. Generating GPG Keys in KDE" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="..
/../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives-Things_of_note.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-Using_GPG-Creating_GPG_Keys_in_KDE1.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" title="3.9. Using GNU Privacy Guard (GnuPG)" id="sect-Security_Guide-Encryption-Using_GPG" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sect-Security_Guide-Encryption-Using_GPG">3.9.Â
Using GNU Privacy Guard (GnuPG)</h2></div></div></div><div class="para">
<span class="application"><strong>GnuPG</strong></span> (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="para">
GPG can also be used to sign and/or encrypt files kept on your computer or on a network drive. This can add additional protection in preventing a file from being altered or read by unauthorized people.
</div><div class="para">
To utilize GPG for authentication or encrytion of email you must first generate your public and private keys. After generating the keys you will have to setup your email client to utilize them.
- </div><div class="section" title="3.9.1. Generating GPG Keys in GNOME" id="sect-Security_Guide-Encryption-Using_GPG-Keys_in_GNOME"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.9.1. Generating GPG Keys in GNOME</h3></div></div></div><div class="para">
+ </div><div class="section" title="3.9.1. Generating GPG Keys in GNOME" id="sect-Security_Guide-Encryption-Using_GPG-Keys_in_GNOME"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Encryption-Using_GPG-Keys_in_GNOME">3.9.1. Generating 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 <span class="package">Seahorse</span> 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 <span class="package">Seahorse</span> 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.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Evaluating_the_Tools-Anticipating_Your_Future_Needs.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Evaluating_the_Tools-Anticipating_Your_Future_Needs.html
index b4283c5..0459a77 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Evaluating_the_Tools-Anticipating_Your_Future_Needs.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Evaluating_the_Tools-Anticipating_Your_Future_Needs.html
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. Anticipating Your Future Needs</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Evaluating the Tools" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Evaluating_the_Tools-VLAD_the_Scanner.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Attackers_and_Vulnerabilities.html"><strong>Next</strong></a></li></ul><div class="section" title="1.2.3.5. Anticipating Your Future Needs" id="sect-Security_Guide-Evaluating_the_Tools-Anticipating_Your_Future_Needs"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">1.2.3.5. Anticipating Your Future Needs</h4></div></div></
div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.2.3.5. Anticipating Your Future Needs</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Evaluating the Tools" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" c
lass="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Evaluating_the_Tools-VLAD_the_Scanner.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Attackers_and_Vulnerabilities.html"><strong>Next</strong></a></li></ul><div class="section" title="1.2.3.5. Anticipating Your Future Needs" id="sect-Security_Guide-Evaluating_the_Tools-Anticipating_Your_Future_Needs"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Evaluating_the_Tools-Anticipating_Yo
ur_Future_Needs">1.2.3.5. Anticipating Your Future Needs</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>Prev</strong>1.2.3.4. VLAD the Scanner</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Attackers_and_Vulnerabilities.html"><strong>Next</strong>1.3. Attackers and Vulnerabilities</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Evaluating_the_Tools-Nessus.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Evaluating_the_Tools-Nessus.html
index ec927b1..160af70 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Evaluating_the_Tools-Nessus.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Evaluating_the_Tools-Nessus.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.2.3.2. Nessus</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Evaluating the Tools" /><link rel="prev" href="sect-Security_Guide-Vulnerability_Assessment-Evaluating_the_Tools.html" title="1.2.3. Evaluating the Tools" /><link rel="next" href="sect-Security_Guide-Evaluating_the_Tools-Nikto.html" title="1.2.3.3. Nikto" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html
">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Vulnerability_Assessment-Evaluating_the_Tools.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Evaluating_the_Tools-Nikto.html"><strong>Next</strong></a></li></ul><div class="section" title="1.2.3.2. Nessus" id="sect-Security_Guide-Evaluating_the_Tools-Nessus"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">1.2.3.2. Nessus</h4></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.2.3.2. Nessus</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Evaluating the Tools" /><link rel="prev" href="sect-Security_Guide-Vulnerability_Assessment-Evaluating_the_Tools.html" title="1.2.3. Evaluating the Tools" /><link rel="next" href="sect-Security_Guide-Evaluating_the_Tools-Nikto.html" title="1.2.3.3. Nikto" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html"
>This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Vulnerability_Assessment-Evaluating_the_Tools.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Evaluating_the_Tools-Nikto.html"><strong>Next</strong></a></li></ul><div class="section" title="1.2.3.2. Nessus" id="sect-Security_Guide-Evaluating_the_Tools-Nessus"><div class="titlepage"><div><div keep-together.within-column="always"><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">
The Nessus client and server software is included in Fedora repositories but requires a subscription to use. It has been included in this document as a reference to users who may be interested in using this popular application.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Evaluating_the_Tools-Nikto.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Evaluating_the_Tools-Nikto.html
index af785f4..c61ec04 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Evaluating_the_Tools-Nikto.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Evaluating_the_Tools-Nikto.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.2.3.3. Nikto</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Evaluating the Tools" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is
an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Evaluating_the_Tools-Nessus.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Evaluating_the_Tools-VLAD_the_Scanner.html"><strong>Next</strong></a></li></ul><div class="section" title="1.2.3.3. Nikto" id="sect-Security_Guide-Evaluating_the_Tools-Nikto"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">1.2.3.3. Nikto</h4></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.2.3.3. Nikto</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Evaluating the Tools" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is
an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Evaluating_the_Tools-Nessus.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Evaluating_the_Tools-VLAD_the_Scanner.html"><strong>Next</strong></a></li></ul><div class="section" title="1.2.3.3. Nikto" id="sect-Security_Guide-Evaluating_the_Tools-Nikto"><div class="titlepage"><div><div keep-together.within-column="always"><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="para">
More information about Nikto can be found at the following URL:
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Evaluating_the_Tools-VLAD_the_Scanner.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Evaluating_the_Tools-VLAD_the_Scanner.html
index 72f58b8..e4b3395 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Evaluating_the_Tools-VLAD_the_Scanner.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Evaluating_the_Tools-VLAD_the_Scanner.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.2.3.4. VLAD the Scanner</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Evaluating the Tools" /><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. Anticipating Your Future Needs" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="to
c" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Evaluating_the_Tools-Nikto.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Evaluating_the_Tools-Anticipating_Your_Future_Needs.html"><strong>Next</strong></a></li></ul><div class="section" title="1.2.3.4. VLAD the Scanner" id="sect-Security_Guide-Evaluating_the_Tools-VLAD_the_Scanner"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">1.2.3.4. VLAD the Scanner</h4></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.2.3.4. VLAD the Scanner</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Evaluating the Tools" /><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. Anticipating Your Future Needs" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc
" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Evaluating_the_Tools-Nikto.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Evaluating_the_Tools-Anticipating_Your_Future_Needs.html"><strong>Next</strong></a></li></ul><div class="section" title="1.2.3.4. VLAD the Scanner" id="sect-Security_Guide-Evaluating_the_Tools-VLAD_the_Scanner"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Evaluating_the_Tools-VLAD_the_Scanner">1.2.3.4. VLAD the Scan
ner</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.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-FORWARD_and_NAT_Rules-DMZs_and_IPTables.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-FORWARD_and_NAT_Rules-DMZs_and_IPTables.html
index 1dbe9ca..1339b5b 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-FORWARD_and_NAT_Rules-DMZs_and_IPTables.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-FORWARD_and_NAT_Rules-DMZs_and_IPTables.html
@@ -1,11 +1,10 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.5.3. DMZs and IPTables</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. FORWARD and NAT Rules" /><link rel="prev" href="sect-Security_Guide-FORWARD_and_NAT_Rules-Prerouting.html" title="2.8.5.2. Prerouting" /><link rel="next" href="sect-Security_Guide-Firewalls-Malicious_Software_and_Spoofed_IP_Addresses.html" title="2.8.6. Malicious Software and Spoofed IP Addresses" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocfram
e" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-FORWARD_and_NAT_Rules-Prerouting.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Firewalls-Malicious_Software_and_Spoofed_IP_Addresses.html"><strong>Next</strong></a></li></ul><div class="section" title="2.8.5.3. DMZs and IPTables" id="sect-Security_Guide-FORWARD_and_NAT_Rules-DMZs_and_IPTables"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.8.5.3. DMZs and IPTables</h4></div></div></div><div class="
para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.5.3. DMZs and IPTables</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. FORWARD and NAT Rules" /><link rel="prev" href="sect-Security_Guide-FORWARD_and_NAT_Rules-Prerouting.html" title="2.8.5.2. Prerouting" /><link rel="next" href="sect-Security_Guide-Firewalls-Malicious_Software_and_Spoofed_IP_Addresses.html" title="2.8.6. Malicious Software and Spoofed IP Addresses" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe
" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-FORWARD_and_NAT_Rules-Prerouting.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Firewalls-Malicious_Software_and_Spoofed_IP_Addresses.html"><strong>Next</strong></a></li></ul><div class="section" title="2.8.5.3. DMZs and IPTables" id="sect-Security_Guide-FORWARD_and_NAT_Rules-DMZs_and_IPTables"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-FORWARD_and_NAT_Rules-DMZs_and_IPTables
">2.8.5.3. DMZs and IPTables</h4></div></div></div><div class="para">
You can create <code class="command">iptables</code> rules to route traffic to certain machines, such as a dedicated HTTP or FTP server, in a <em class="firstterm">demilitarized zone</em> (<acronym class="acronym">DMZ</acronym>). A <acronym class="acronym">DMZ</acronym> is a special local subnetwork dedicated to providing services on a public carrier, such as the Internet.
</div><div class="para">
For example, to set a rule for routing incoming HTTP requests to a dedicated HTTP server at 10.0.4.2 (outside of the 192.168.1.0/24 range of the LAN), NAT uses the <code class="computeroutput">PREROUTING</code> table to forward the packets to the appropriate destination:
- </div><pre class="screen">[root at myServer ~ ] # iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 80 -j DNAT --to-destination 10.0.4.2:80
-</pre><div class="para">
+ </div><pre class="screen">[root at myServer ~ ] # 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">
If the HTTP server is configured to accept secure connections, then port 443 must be forwarded as well.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-FORWARD_and_NAT_Rules-Prerouting.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-FORWARD_and_NAT_Rules-Prerouting.html
index 86617ba..7265ae7 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-FORWARD_and_NAT_Rules-Prerouting.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-FORWARD_and_NAT_Rules-Prerouting.html
@@ -1,15 +1,13 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.5.2. Prerouting</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. FORWARD and NAT Rules" /><link rel="prev" href="sect-Security_Guide-Firewalls-FORWARD_and_NAT_Rules.html" title="2.8.5. FORWARD and NAT Rules" /><link rel="next" href="sect-Security_Guide-FORWARD_and_NAT_Rules-DMZs_and_IPTables.html" title="2.8.5.3. DMZs and IPTables" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.h
tml">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Firewalls-FORWARD_and_NAT_Rules.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-FORWARD_and_NAT_Rules-DMZs_and_IPTables.html"><strong>Next</strong></a></li></ul><div class="section" title="2.8.5.2. Prerouting" id="sect-Security_Guide-FORWARD_and_NAT_Rules-Prerouting"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.8.5.2. Prerouting</h4></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.5.2. Prerouting</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. FORWARD and NAT Rules" /><link rel="prev" href="sect-Security_Guide-Firewalls-FORWARD_and_NAT_Rules.html" title="2.8.5. FORWARD and NAT Rules" /><link rel="next" href="sect-Security_Guide-FORWARD_and_NAT_Rules-DMZs_and_IPTables.html" title="2.8.5.3. DMZs and IPTables" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.ht
ml">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Firewalls-FORWARD_and_NAT_Rules.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-FORWARD_and_NAT_Rules-DMZs_and_IPTables.html"><strong>Next</strong></a></li></ul><div class="section" title="2.8.5.2. Prerouting" id="sect-Security_Guide-FORWARD_and_NAT_Rules-Prerouting"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-FORWARD_and_NAT_Rules-Prerouting">2.8.5.2. Prerouting</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">
For example, if you want to forward incoming HTTP requests to your dedicated Apache HTTP Server at 172.31.0.23, use the following command:
- </div><pre class="screen">[root at myServer ~ ] # iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 80 -j DNAT --to 172.31.0.23:80
-</pre><div class="para">
+ </div><pre class="screen">[root at myServer ~ ] # iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 80 -j DNAT --to 172.31.0.23:80</pre><div class="para">
This rule specifies that the <acronym class="acronym">nat</acronym> table use the built-in PREROUTING chain to forward incoming HTTP requests exclusively to the listed destination IP address of 172.31.0.23.
</div><div class="note"><h2>Note</h2><div class="para">
If you have a default policy of DROP in your FORWARD chain, you must append a rule to forward all incoming HTTP requests so that destination NAT routing is possible. To do this, use the following command:
- </div><pre class="screen">[root at myServer ~ ] # iptables -A FORWARD -i eth0 -p tcp --dport 80 -d 172.31.0.23 -j ACCEPT
-</pre><div class="para">
+ </div><pre class="screen">[root at myServer ~ ] # iptables -A FORWARD -i eth0 -p tcp --dport 80 -d 172.31.0.23 -j ACCEPT</pre><div class="para">
This rule forwards all incoming HTTP requests from the firewall to the intended destination; the Apache HTTP Server behind the firewall.
</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Firewalls-FORWARD_and_NAT_Rules.html"><strong>Prev</strong>2.8.5. FORWARD and NAT Rules</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-FORWARD_and_NAT_Rules-DMZs_and_IPTables.html"><strong>Next</strong>2.8.5.3. DMZs and IPTables</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Firewalls-Additional_Resources.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Firewalls-Additional_Resources.html
index d8b2400..46bedd3 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Firewalls-Additional_Resources.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Firewalls-Additional_Resources.html
@@ -1,8 +1,8 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Useful Firewall Websites" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your b
rowser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Firewalls-IPv6.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Additional_Resources-Useful_Firewall_Websites.html"><strong>Next</strong></a></li></ul><div class="section" title="2.8.9. Additional Resources" id="sect-Security_Guide-Firewalls-Additional_Resources"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.8.9. Additional Resources</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.9. Additional Resources</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Useful Firewall Websites" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your br
owser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Firewalls-IPv6.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Additional_Resources-Useful_Firewall_Websites.html"><strong>Next</strong></a></li></ul><div class="section" title="2.8.9. Additional Resources" id="sect-Security_Guide-Firewalls-Additional_Resources"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Firewalls-Additional_Resources">2.8.9. Additional Resources</h3></div></div></div><div class="para">
There are several aspects to firewalls and the Linux Netfilter subsystem that could not be covered in this chapter. For more information, refer to the following resources.
- </div><div class="section" title="2.8.9.1. Installed Firewall Documentation" id="sect-Security_Guide-Additional_Resources-Installed_Firewall_Documentation"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.8.9.1. Installed Firewall Documentation</h4></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ </div><div class="section" title="2.8.9.1. Installed Firewall Documentation" id="sect-Security_Guide-Additional_Resources-Installed_Firewall_Documentation"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Additional_Resources-Installed_Firewall_Documentation">2.8.9.1. Installed Firewall Documentation</h4></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
Refer to <a class="xref" href="sect-Security_Guide-IPTables.html" title="2.9. IPTables">Section 2.9, “IPTablesâ€</a> for more detailed information on the <code class="command">iptables</code> command, including definitions for many command options.
</div></li><li class="listitem"><div class="para">
The <code class="command">iptables</code> man page contains a brief summary of the various options.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Firewalls-Basic_Firewall_Configuration.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Firewalls-Basic_Firewall_Configuration.html
index 861a344..cff8440 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Firewalls-Basic_Firewall_Configuration.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Firewalls-Basic_Firewall_Configuration.html
@@ -1,17 +1,16 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.2. Basic Firewall Configuration</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Enabling and Disabling the Firewall" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is
an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Firewalls.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Basic_Firewall_Configuration-Enabling_and_Disabling_the_Firewall.html"><strong>Next</strong></a></li></ul><div class="section" title="2.8.2. Basic Firewall Configuration" id="sect-Security_Guide-Firewalls-Basic_Firewall_Configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.8.2. Basic Firewall Configuration</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.2. Basic Firewall Configuration</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Enabling and Disabling the Firewall" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is a
n iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Firewalls.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Basic_Firewall_Configuration-Enabling_and_Disabling_the_Firewall.html"><strong>Next</strong></a></li></ul><div class="section" title="2.8.2. Basic Firewall Configuration" id="sect-Security_Guide-Firewalls-Basic_Firewall_Configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Firewalls-Basic_Firewall_Configuration">2.8.2. Basic Firewall Configuration</h3></div></div>
</div><div class="para">
Just as a firewall in a building attempts to prevent a fire from spreading, a computer firewall attempts to prevent malicious software from spreading to your computer. It also helps to prevent unauthorized users from accessing your computer.
</div><div class="para">
In a default Fedora installation, a firewall exists between your computer or network and any untrusted networks, for example the Internet. It determines which services on your computer remote users can access. A properly configured firewall can greatly increase the security of your system. It is recommended that you configure a firewall for any Fedora system with an Internet connection.
- </div><div class="section" title="2.8.2.1. Firewall Configuration Tool" id="sect-Security_Guide-Basic_Firewall_Configuration-RHSECLEVELTOOL"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.8.2.1. <span class="application"><strong>Firewall Configuration Tool</strong></span></h4></div></div></div><div class="para">
+ </div><div class="section" title="2.8.2.1. Firewall Configuration Tool" id="sect-Security_Guide-Basic_Firewall_Configuration-RHSECLEVELTOOL"><div class="titlepage"><div><div keep-together.within-column="always"><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">
During the <span class="guilabel"><strong>Firewall Configuration</strong></span> screen of the Fedora installation, you were given the option to enable a basic firewall as well as to allow specific devices, incoming services, and ports.
</div><div class="para">
After installation, you can change this preference by using the <span class="application"><strong>Firewall Configuration Tool</strong></span>.
</div><div class="para">
To start this application, use the following command:
- </div><pre class="screen">[root at myServer ~] # system-config-firewall
-</pre><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/fed-firewall_config.png" width="444" alt="Firewall Configuration Tool" /><div class="longdesc"><div class="para">
+ </div><pre class="screen">[root at myServer ~] # system-config-firewall</pre><div class="figure" title="Figure 2.15. Firewall Configuration Tool" id="figu-Security_Guide-RHSECLEVELTOOL-RHSECLEVELTOOL"><div class="figure-contents"><div class="mediaobject"><img src="images/fed-firewall_config.png" width="444" alt="Firewall Configuration Tool" /><div class="longdesc"><div class="para">
Security Level Configuration
</div></div></div></div><h6>Figure 2.15. <span class="application">Firewall Configuration Tool</span></h6></div><br class="figure-break" /><div class="note"><h2>Note</h2><div class="para">
The <span class="application"><strong>Firewall Configuration Tool</strong></span> only configures a basic firewall. If the system needs more complex rules, refer to <a class="xref" href="sect-Security_Guide-IPTables.html" title="2.9. IPTables">Section 2.9, “IPTablesâ€</a> for details on configuring specific <code class="command">iptables</code> rules.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Firewalls-Common_IPTables_Filtering.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Firewalls-Common_IPTables_Filtering.html
index 4a4d902..1ef905e 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Firewalls-Common_IPTables_Filtering.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Firewalls-Common_IPTables_Filtering.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.4. Common IPTables Filtering</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Saving and Restoring IPTables Rules" /><link rel="next" href="sect-Security_Guide-Firewalls-FORWARD_and_NAT_Rules.html" title="2.8.5. FORWARD and NAT Rules" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../..
/toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Using_IPTables-Saving_and_Restoring_IPTables_Rules.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Firewalls-FORWARD_and_NAT_Rules.html"><strong>Next</strong></a></li></ul><div class="section" title="2.8.4. Common IPTables Filtering" id="sect-Security_Guide-Firewalls-Common_IPTables_Filtering"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.8.4. Common IPTables Filtering</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.4. Common IPTables Filtering</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Saving and Restoring IPTables Rules" /><link rel="next" href="sect-Security_Guide-Firewalls-FORWARD_and_NAT_Rules.html" title="2.8.5. FORWARD and NAT Rules" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../
toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Using_IPTables-Saving_and_Restoring_IPTables_Rules.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Firewalls-FORWARD_and_NAT_Rules.html"><strong>Next</strong></a></li></ul><div class="section" title="2.8.4. Common IPTables Filtering" id="sect-Security_Guide-Firewalls-Common_IPTables_Filtering"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Firewalls-Common_IPTables_Filtering">2.8.4. Common IPTables Filtering</
h3></div></div></div><div class="para">
Preventing remote attackers from accessing a LAN is one of the most important aspects of network security. The integrity of a LAN should be protected from malicious remote users through the use of stringent firewall rules.
</div><div class="para">
However, with a default policy set to block all incoming, outgoing, and forwarded packets, it is impossible for the firewall/gateway and internal LAN users to communicate with each other or with external resources.
@@ -8,11 +8,9 @@
To allow users to perform network-related functions and to use networking applications, administrators must open certain ports for communication.
</div><div class="para">
For example, to allow access to port 80 <span class="emphasis"><em>on the firewall</em></span>, append the following rule:
- </div><pre class="screen">[root at myServer ~ ] # iptables -A INPUT -p tcp -m tcp --dport 80 -j ACCEPT
-</pre><div class="para">
+ </div><pre class="screen">[root at myServer ~ ] # iptables -A INPUT -p tcp -m tcp --dport 80 -j ACCEPT</pre><div class="para">
This allows users to browse websites that communicate using the standard port 80. To allow access to secure websites (for example, https://www.example.com/), you also need to provide access to port 443, as follows:
- </div><pre class="screen">[root at myServer ~ ] # iptables -A INPUT -p tcp -m tcp --dport 443 -j ACCEPT
-</pre><div class="important"><h2>Important</h2><div class="para">
+ </div><pre class="screen">[root at myServer ~ ] # iptables -A INPUT -p tcp -m tcp --dport 443 -j ACCEPT</pre><div class="important"><h2>Important</h2><div class="para">
When creating an <code class="command">iptables</code> ruleset, order is important.
</div><div class="para">
If a rule specifies that any packets from the 192.168.100.0/24 subnet be dropped, and this is followed by a rule that allows packets from 192.168.100.13 (which is within the dropped subnet), then the second rule is ignored.
@@ -20,8 +18,7 @@
The rule to allow packets from 192.168.100.13 must precede the rule that drops the remainder of the subnet.
</div><div class="para">
To insert a rule in a specific location in an existing chain, use the <code class="option">-I</code> option. For example:
- </div><pre class="screen">[root at myServer ~ ] # iptables -I INPUT 1 -i lo -p all -j ACCEPT
-</pre><div class="para">
+ </div><pre class="screen">[root at myServer ~ ] # iptables -I INPUT 1 -i lo -p all -j ACCEPT</pre><div class="para">
This rule is inserted as the first rule in the INPUT chain to allow local loopback device traffic.
</div></div><div class="para">
There may be times when you require remote access to the LAN. Secure services, for example SSH, can be used for encrypted remote connection to LAN services.
@@ -30,7 +27,6 @@
</div><div class="para">
For remote users with broadband connections, however, special cases can be made. You can configure <code class="command">iptables</code> to accept connections from remote SSH clients. For example, the following rules allow remote SSH access:
</div><pre class="screen">[root at myServer ~ ] # iptables -A INPUT -p tcp --dport 22 -j ACCEPT
-[root at myServer ~ ] # iptables -A OUTPUT -p tcp --sport 22 -j ACCEPT
-</pre><div class="para">
+[root at myServer ~ ] # iptables -A OUTPUT -p tcp --sport 22 -j ACCEPT</pre><div class="para">
These rules allow incoming and outbound access for an individual system, such as a single PC directly connected to the Internet or a firewall/gateway. However, they do not allow nodes behind the firewall/gateway to access these services. To allow LAN access to these services, you can use <em class="firstterm">Network Address Translation</em> (<acronym class="acronym">NAT</acronym>) with <code class="command">iptables</code> filtering rules.
</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Using_IPTables-Saving_and_Restoring_IPTables_Rules.html"><strong>Prev</strong>2.8.3.3. Saving and Restoring IPTables Rules</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Firewalls-FORWARD_and_NAT_Rules.html"><strong>Next</strong>2.8.5. FORWARD and NAT Rules</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Firewalls-FORWARD_and_NAT_Rules.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Firewalls-FORWARD_and_NAT_Rules.html
index a5c9c58..4777559 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Firewalls-FORWARD_and_NAT_Rules.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Firewalls-FORWARD_and_NAT_Rules.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.5. FORWARD and NAT Rules</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Common IPTables Filtering" /><link rel="next" href="sect-Security_Guide-FORWARD_and_NAT_Rules-Prerouting.html" title="2.8.5.2. Prerouting" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view i
t upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Firewalls-Common_IPTables_Filtering.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-FORWARD_and_NAT_Rules-Prerouting.html"><strong>Next</strong></a></li></ul><div class="section" title="2.8.5. FORWARD and NAT Rules" id="sect-Security_Guide-Firewalls-FORWARD_and_NAT_Rules"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.8.5. <code class="computeroutput">FORWARD</code> and <acronym class="acronym">NAT</acronym> Rules</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.5. FORWARD and NAT Rules</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Common IPTables Filtering" /><link rel="next" href="sect-Security_Guide-FORWARD_and_NAT_Rules-Prerouting.html" title="2.8.5.2. Prerouting" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it
upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Firewalls-Common_IPTables_Filtering.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-FORWARD_and_NAT_Rules-Prerouting.html"><strong>Next</strong></a></li></ul><div class="section" title="2.8.5. FORWARD and NAT Rules" id="sect-Security_Guide-Firewalls-FORWARD_and_NAT_Rules"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Firewalls-FORWARD_and_NAT_Rules">2.8.5. <code class="computeroutput">FORWARD</code> and <acronym class="acronym">NAT</acronym> Rules
</h3></div></div></div><div class="para">
Most ISPs provide only a limited number of publicly routable IP addresses to the organizations they serve.
</div><div class="para">
Administrators must, therefore, find alternative ways to share access to Internet services without giving public IP addresses to every node on the LAN. Using private IP addresses is the most common way of allowing all nodes on a LAN to properly access internal and external network services.
@@ -13,29 +13,23 @@
</div><div class="para">
The <code class="computeroutput">FORWARD</code> chain allows an administrator to control where packets can be routed within a LAN. For example, to allow forwarding for the entire LAN (assuming the firewall/gateway is assigned an internal IP address on eth1), use the following rules:
</div><pre class="screen">[root at myServer ~ ] # iptables -A FORWARD -i eth1 -j ACCEPT
-[root at myServer ~ ] # iptables -A FORWARD -o eth1 -j ACCEPT
-</pre><div class="para">
+[root at myServer ~ ] # iptables -A FORWARD -o eth1 -j ACCEPT</pre><div class="para">
This rule gives systems behind the firewall/gateway access to the internal network. The gateway routes packets from one LAN node to its intended destination node, passing all packets through its <code class="filename">eth1</code> device.
</div><div class="note"><h2>Note</h2><div class="para">
By default, the IPv4 policy in Fedora kernels disables support for IP forwarding. This prevents machines that run Fedora from functioning as dedicated edge routers. To enable IP forwarding, use the following command:
- </div><pre class="screen">[root at myServer ~ ] # sysctl -w net.ipv4.ip_forward=1
-</pre><div class="para">
+ </div><pre class="screen">[root at myServer ~ ] # sysctl -w net.ipv4.ip_forward=1</pre><div class="para">
This configuration change is only valid for the current session; it does not persist beyond a reboot or network service restart. To permanently set IP forwarding, edit the <code class="filename">/etc/sysctl.conf</code> file as follows:
</div><div class="para">
Locate the following line:
- </div><pre class="screen">net.ipv4.ip_forward = 0
-</pre><div class="para">
+ </div><pre class="screen">net.ipv4.ip_forward = 0</pre><div class="para">
Edit it to read as follows:
- </div><pre class="screen">net.ipv4.ip_forward = 1
-</pre><div class="para">
+ </div><pre class="screen">net.ipv4.ip_forward = 1</pre><div class="para">
Use the following command to enable the change to the <code class="filename">sysctl.conf</code> file:
- </div><pre class="screen">[root at myServer ~ ] # sysctl -p /etc/sysctl.conf
-</pre></div><div class="section" title="2.8.5.1. Postrouting and IP Masquerading" id="sect-Security_Guide-FORWARD_and_NAT_Rules-Postrouting_and_IP_Masquerading"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.8.5.1. Postrouting and IP Masquerading</h4></div></div></div><div class="para">
+ </div><pre class="screen">[root at myServer ~ ] # sysctl -p /etc/sysctl.conf</pre></div><div class="section" title="2.8.5.1. Postrouting and IP Masquerading" id="sect-Security_Guide-FORWARD_and_NAT_Rules-Postrouting_and_IP_Masquerading"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-FORWARD_and_NAT_Rules-Postrouting_and_IP_Masquerading">2.8.5.1. Postrouting and IP Masquerading</h4></div></div></div><div class="para">
Accepting forwarded packets via the firewall's internal IP device allows LAN nodes to communicate with each other; however they still cannot communicate externally to the Internet.
</div><div class="para">
To allow LAN nodes with private IP addresses to communicate with external public networks, configure the firewall for <em class="firstterm">IP masquerading</em>, which masks requests from LAN nodes with the IP address of the firewall's external device (in this case, eth0):
- </div><pre class="screen">[root at myServer ~ ] # iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
-</pre><div class="para">
+ </div><pre class="screen">[root at myServer ~ ] # iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE</pre><div class="para">
This rule uses the NAT packet matching table (<code class="option">-t nat</code>) and specifies the built-in POSTROUTING chain for NAT (<code class="option">-A POSTROUTING</code>) on the firewall's external networking device (<code class="option">-o eth0</code>).
</div><div class="para">
POSTROUTING allows packets to be altered as they are leaving the firewall's external device.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Firewalls-IPTables_and_Connection_Tracking.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Firewalls-IPTables_and_Connection_Tracking.html
index 2ecf538..e46e237 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Firewalls-IPTables_and_Connection_Tracking.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Firewalls-IPTables_and_Connection_Tracking.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.7. IPTables and Connection Tracking</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Malicious Software and Spoofed IP Addresses" /><link rel="next" href="sect-Security_Guide-Firewalls-IPv6.html" title="2.8.8. IPv6" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is
an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Firewalls-Malicious_Software_and_Spoofed_IP_Addresses.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Firewalls-IPv6.html"><strong>Next</strong></a></li></ul><div class="section" title="2.8.7. IPTables and Connection Tracking" id="sect-Security_Guide-Firewalls-IPTables_and_Connection_Tracking"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.8.7. IPTables and Connection Tracking</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.7. IPTables and Connection Tracking</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Malicious Software and Spoofed IP Addresses" /><link rel="next" href="sect-Security_Guide-Firewalls-IPv6.html" title="2.8.8. IPv6" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is
an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Firewalls-Malicious_Software_and_Spoofed_IP_Addresses.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Firewalls-IPv6.html"><strong>Next</strong></a></li></ul><div class="section" title="2.8.7. IPTables and Connection Tracking" id="sect-Security_Guide-Firewalls-IPTables_and_Connection_Tracking"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Firewalls-IPTables_and_Connection_Tracking">2.8.7. IPTables and Connection Tracking</h3><
/div></div></div><div class="para">
You can inspect and restrict connections to services based on their <em class="firstterm">connection state.</em> A module within <code class="command">iptables</code> uses a method called <em class="firstterm">connection tracking</em> to store information about incoming connections. You can allow or deny access based on the following connection states:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="option">NEW</code> — A packet requesting a new connection, such as an HTTP request.
@@ -12,5 +12,4 @@
<code class="option">INVALID</code> — A packet that is not part of any connections in the connection tracking table.
</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 myServer ~ ] # 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>Prev</strong>2.8.6. Malicious Software and Spoofed IP Addresses</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Firewalls-IPv6.html"><strong>Next</strong>2.8.8. IPv6</a></li></ul></body></html>
+ </div><pre class="screen">[root at myServer ~ ] # 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>Prev</strong>2.8.6. Malicious Software and Spoofed IP Addresses</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Firewalls-IPv6.html"><strong>Next</strong>2.8.8. IPv6</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Firewalls-IPv6.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Firewalls-IPv6.html
index d94d331..e10179b 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Firewalls-IPv6.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Firewalls-IPv6.html
@@ -1,12 +1,11 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.8. IPv6</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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 and Connection Tracking" /><link rel="next" href="sect-Security_Guide-Firewalls-Additional_Resources.html" title="2.8.9. Additional Resources" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to vie
w it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Firewalls-IPTables_and_Connection_Tracking.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Firewalls-Additional_Resources.html"><strong>Next</strong></a></li></ul><div class="section" title="2.8.8. IPv6" id="sect-Security_Guide-Firewalls-IPv6"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.8.8. IPv6</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.8. IPv6</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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 and Connection Tracking" /><link rel="next" href="sect-Security_Guide-Firewalls-Additional_Resources.html" title="2.8.9. Additional Resources" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view
it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Firewalls-IPTables_and_Connection_Tracking.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Firewalls-Additional_Resources.html"><strong>Next</strong></a></li></ul><div class="section" title="2.8.8. IPv6" id="sect-Security_Guide-Firewalls-IPv6"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Firewalls-IPv6">2.8.8. IPv6</h3></div></div></div><div class="para">
The introduction of the next-generation Internet Protocol, called IPv6, expands beyond the 32-bit address limit of IPv4 (or IP). IPv6 supports 128-bit addresses, and carrier networks that are IPv6 aware are therefore able to address a larger number of routable addresses than 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 12, both IPv4 and IPv6 services are enabled by default.
</div><div class="para">
The <code class="command">ip6tables</code> command syntax is identical to <code class="command">iptables</code> in every aspect except that it supports 128-bit addresses. For example, use the following command to enable SSH connections on an IPv6-aware network server:
- </div><pre class="screen">[root at myServer ~ ] # ip6tables -A INPUT -i eth0 -p tcp -s 3ffe:ffff:100::1/128 --dport 22 -j ACCEPT
-</pre><div class="para">
+ </div><pre class="screen">[root at myServer ~ ] # ip6tables -A INPUT -i eth0 -p tcp -s 3ffe:ffff:100::1/128 --dport 22 -j ACCEPT</pre><div class="para">
For more information about IPv6 networking, refer to the IPv6 Information Page at <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>Prev</strong>2.8.7. IPTables and Connection Tracking</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Firewalls-Additional_Resources.html"><strong>Next</strong>2.8.9. Additional Resources</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Firewalls-Malicious_Software_and_Spoofed_IP_Addresses.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Firewalls-Malicious_Software_and_Spoofed_IP_Addresses.html
index b6a3dc6..2e941d8 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Firewalls-Malicious_Software_and_Spoofed_IP_Addresses.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Firewalls-Malicious_Software_and_Spoofed_IP_Addresses.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.6. Malicious Software and Spoofed IP Addresses</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. DMZs and IPTables" /><link rel="next" href="sect-Security_Guide-Firewalls-IPTables_and_Connection_Tracking.html" title="2.8.7. IPTables and Connection Tracking" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="
../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-FORWARD_and_NAT_Rules-DMZs_and_IPTables.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Firewalls-IPTables_and_Connection_Tracking.html"><strong>Next</strong></a></li></ul><div class="section" title="2.8.6. Malicious Software and Spoofed IP Addresses" id="sect-Security_Guide-Firewalls-Malicious_Software_and_Spoofed_IP_Addresses"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.8.6. Malicious Software and Spoofed IP Addres
ses</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.6. Malicious Software and Spoofed IP Addresses</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. DMZs and IPTables" /><link rel="next" href="sect-Security_Guide-Firewalls-IPTables_and_Connection_Tracking.html" title="2.8.7. IPTables and Connection Tracking" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src=".
./../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-FORWARD_and_NAT_Rules-DMZs_and_IPTables.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Firewalls-IPTables_and_Connection_Tracking.html"><strong>Next</strong></a></li></ul><div class="section" title="2.8.6. Malicious Software and Spoofed IP Addresses" id="sect-Security_Guide-Firewalls-Malicious_Software_and_Spoofed_IP_Addresses"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Firewalls-Malicious_Softw
are_and_Spoofed_IP_Addresses">2.8.6. Malicious Software and Spoofed IP Addresses</h3></div></div></div><div class="para">
More elaborate rules can be created that control access to specific subnets, or even specific nodes, within a LAN. You can also restrict certain dubious applications or programs such as trojans, worms, and other client/server viruses from contacting their server.
</div><div class="para">
For example, some trojans scan networks for services on ports from 31337 to 31340 (called the <span class="emphasis"><em>elite</em></span> ports in cracking terminology).
@@ -9,15 +9,13 @@
</div><div class="para">
The following rules drop all TCP traffic that attempts to use port 31337:
</div><pre class="screen">[root at myServer ~ ] # iptables -A OUTPUT -o eth0 -p tcp --dport 31337 --sport 31337 -j DROP
-[root at myServer ~ ] # iptables -A FORWARD -o eth0 -p tcp --dport 31337 --sport 31337 -j DROP
-</pre><div class="para">
+[root at myServer ~ ] # iptables -A FORWARD -o eth0 -p tcp --dport 31337 --sport 31337 -j DROP</pre><div class="para">
You can also block outside connections that attempt to spoof private IP address ranges to infiltrate your LAN.
</div><div class="para">
For example, if your LAN uses the 192.168.1.0/24 range, you can design a rule that instructs the Internet-facing network device (for example, eth0) to drop any packets to that device with an address in your LAN IP range.
</div><div class="para">
Because it is recommended to reject forwarded packets as a default policy, any other spoofed IP address to the external-facing device (eth0) is rejected automatically.
- </div><pre class="screen">[root at myServer ~ ] # iptables -A FORWARD -s 192.168.1.0/24 -i eth0 -j DROP
-</pre><div class="note"><h2>Note</h2><div class="para">
+ </div><pre class="screen">[root at myServer ~ ] # iptables -A FORWARD -s 192.168.1.0/24 -i eth0 -j DROP</pre><div class="note"><h2>Note</h2><div class="para">
There is a distinction between the <code class="computeroutput">DROP</code> and <code class="computeroutput">REJECT</code> targets when dealing with <span class="emphasis"><em>appended</em></span> rules.
</div><div class="para">
The <code class="computeroutput">REJECT</code> target denies access and returns a <code class="computeroutput">connection refused</code> error to users who attempt to connect to the service. The <code class="computeroutput">DROP</code> target, as the name implies, drops the packet without any warning.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Firewalls-Using_IPTables.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Firewalls-Using_IPTables.html
index ed6a760..64276fa 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Firewalls-Using_IPTables.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Firewalls-Using_IPTables.html
@@ -1,19 +1,16 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.3. Using IPTables</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Activating the IPTables Service" /><link rel="next" href="sect-Security_Guide-Using_IPTables-Basic_Firewall_Policies.html" title="2.8.3.2. Basic Firewall Policies" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../..
/../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Basic_Firewall_Configuration-Activating_the_IPTables_Service.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Using_IPTables-Basic_Firewall_Policies.html"><strong>Next</strong></a></li></ul><div class="section" title="2.8.3. Using IPTables" id="sect-Security_Guide-Firewalls-Using_IPTables"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.8.3. Using IPTables</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.3. Using IPTables</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Activating the IPTables Service" /><link rel="next" href="sect-Security_Guide-Using_IPTables-Basic_Firewall_Policies.html" title="2.8.3.2. Basic Firewall Policies" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../
../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Basic_Firewall_Configuration-Activating_the_IPTables_Service.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Using_IPTables-Basic_Firewall_Policies.html"><strong>Next</strong></a></li></ul><div class="section" title="2.8.3. Using IPTables" id="sect-Security_Guide-Firewalls-Using_IPTables"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Firewalls-Using_IPTables">2.8.3. Using IPTables</h3></div></div></div>
<div class="para">
The first step in using <code class="command">iptables</code> is to start the <code class="command">iptables</code> service. Use the following command to start the <code class="command">iptables</code> service:
- </div><pre class="screen">[root at myServer ~] # service iptables start
-</pre><div class="note"><h2>Note</h2><div class="para">
+ </div><pre class="screen">[root at myServer ~] # service iptables start</pre><div class="note"><h2>Note</h2><div class="para">
The <code class="command">ip6tables</code> service can be turned off if you intend to use the <code class="command">iptables</code> service only. If you deactivate the <code class="command">ip6tables</code> service, remember to deactivate the IPv6 network also. Never leave a network device active without the matching firewall.
</div></div><div class="para">
To force <code class="command">iptables</code> to start by default when the system is booted, use the following command:
- </div><pre class="screen">[root at myServer ~] # chkconfig --level 345 iptables on
-</pre><div class="para">
+ </div><pre class="screen">[root at myServer ~] # chkconfig --level 345 iptables on</pre><div class="para">
This forces <code class="command">iptables</code> to start whenever the system is booted into runlevel 3, 4, or 5.
- </div><div class="section" title="2.8.3.1. IPTables Command Syntax" id="sect-Security_Guide-Using_IPTables-IPTables_Command_Syntax"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.8.3.1. IPTables Command Syntax</h4></div></div></div><div class="para">
+ </div><div class="section" title="2.8.3.1. IPTables Command Syntax" id="sect-Security_Guide-Using_IPTables-IPTables_Command_Syntax"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Using_IPTables-IPTables_Command_Syntax">2.8.3.1. IPTables Command Syntax</h4></div></div></div><div class="para">
The following sample <code class="command">iptables</code> command illustrates the basic command syntax:
- </div><pre class="screen">[root at myServer ~ ] # iptables -A <em class="replaceable"><code><chain></code></em> -j <em class="replaceable"><code><target></code></em>
-</pre><div class="para">
+ </div><pre class="screen">[root at myServer ~ ] # iptables -A <em class="replaceable"><code><chain></code></em> -j <em class="replaceable"><code><target></code></em></pre><div class="para">
The <code class="option">-A</code> option specifies that the rule be appended to <em class="firstterm"><chain></em>. Each chain is comprised of one or more <em class="firstterm">rules</em>, and is therefore also known as a <em class="firstterm">ruleset</em>.
</div><div class="para">
The three built-in chains are INPUT, OUTPUT, and FORWARD. These chains are permanent and cannot be deleted. The chain specifies the point at which a packet is manipulated.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Firewalls.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Firewalls.html
index bb15c79..389020c 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Firewalls.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Firewalls.html
@@ -1,12 +1,12 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8. Firewalls</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="chap-Security_Guide-Securing_Your_Network.html" title="Chapter 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. Basic Firewall Configuration" /></head><body class="toc_embeded "><div id="tocdiv" class="toc
"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-Starting_and_Stopping_an_IPsec_Connection.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Firewalls-Basic_Firewall_Configuration.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" title="2.8. Firewalls" id="sect-Security_Guide-Firewalls" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.8. Firewalls</h2></div></d
iv></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8. Firewalls</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="chap-Security_Guide-Securing_Your_Network.html" title="Chapter 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. Basic Firewall Configuration" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"
><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-Starting_and_Stopping_an_IPsec_Connection.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Firewalls-Basic_Firewall_Configuration.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" title="2.8. Firewalls" id="sect-Security_Guide-Firewalls" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sect-Security_Guide-Firewa
lls">2.8. Firewalls</h2></div></div></div><div class="para">
Information security is commonly thought of as a process and not a product. However, standard security implementations usually employ some form of dedicated mechanism to control access privileges and restrict network resources to users who are authorized, identifiable, and traceable. Fedora includes several tools to assist administrators and security engineers with network-level access control issues.
</div><div class="para">
Firewalls are one of the core components of a network security implementation. Several vendors market firewall solutions catering to all levels of the marketplace: from home users protecting one PC to data center solutions safeguarding vital enterprise information. Firewalls can be stand-alone hardware solutions, such as firewall appliances by Cisco, Nokia, and Sonicwall. Vendors such as Checkpoint, McAfee, and Symantec have also developed proprietary software firewall solutions for home and business markets.
</div><div class="para">
Apart from the differences between hardware and software firewalls, there are also differences in the way firewalls function that separate one solution from another. <a class="xref" href="sect-Security_Guide-Firewalls.html#tabl-Security_Guide-Firewalls-Firewall_Types" title="Table 2.2. Firewall Types">Table 2.2, “Firewall Typesâ€</a> details three common types of firewalls and how they function:
- </div><div class="table"><div class="table-contents"><table summary="Firewall Types" border="1"><colgroup><col width="10%" /><col width="30%" /><col width="30%" /><col width="30%" /></colgroup><thead><tr><th>
+ </div><div class="table" title="Table 2.2. Firewall Types" id="tabl-Security_Guide-Firewalls-Firewall_Types"><div class="table-contents"><table summary="Firewall Types" border="1"><colgroup><col width="10%" /><col width="30%" /><col width="30%" /><col width="30%" /></colgroup><thead><tr><th>
Method
</th><th>
Description
@@ -44,9 +44,9 @@
</td><td>
<table border="0" summary="Simple list" class="simplelist"><tr><td> · Proxies are often application-specific (HTTP, Telnet, etc.), or protocol-restricted (most proxies work with TCP-connected services only) </td></tr><tr><td> · Application services cannot run behind a proxy, so your application servers must use a separate form of network security </td></tr><tr><td> · Proxies can become a network bottleneck, as all requests and transmissions are passed through one source rather than directly from a client to a remote service </td></tr></table>
- </td></tr></tbody></table></div><h6>Table 2.2. Firewall Types</h6></div><br class="table-break" /><div class="section" title="2.8.1. Netfilter and IPTables" id="sect-Security_Guide-Firewalls-Netfilter_and_IPTables"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.8.1. Netfilter and IPTables</h3></div></div></div><div class="para">
+ </td></tr></tbody></table></div><h6>Table 2.2. Firewall Types</h6></div><br class="table-break" /><div class="section" title="2.8.1. Netfilter and IPTables" id="sect-Security_Guide-Firewalls-Netfilter_and_IPTables"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Firewalls-Netfilter_and_IPTables">2.8.1. Netfilter and IPTables</h3></div></div></div><div class="para">
The Linux kernel features a powerful networking subsystem called <em class="firstterm">Netfilter</em>. The Netfilter subsystem provides stateful or stateless packet filtering as well as NAT and IP masquerading services. Netfilter also has the ability to <em class="firstterm">mangle</em> IP header information for advanced routing and connection state management. Netfilter is controlled using the <code class="command">iptables</code> tool.
- </div><div class="section" title="2.8.1.1. IPTables Overview" id="sect-Security_Guide-Netfilter_and_IPTables-IPTables_Overview"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.8.1.1. IPTables Overview</h4></div></div></div><div class="para">
+ </div><div class="section" title="2.8.1.1. IPTables Overview" id="sect-Security_Guide-Netfilter_and_IPTables-IPTables_Overview"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Netfilter_and_IPTables-IPTables_Overview">2.8.1.1. IPTables Overview</h4></div></div></div><div class="para">
The power and flexibility of Netfilter is implemented using the <code class="command">iptables</code> administration tool, a command line tool similar in syntax to its predecessor, <code class="command">ipchains</code>, which Netfilter/iptables replaced in the Linux kernel 2.4 and above.
</div><div class="para">
<code class="command">iptables</code> uses the Netfilter subsystem to enhance network connection, inspection, and processing. <code class="command">iptables</code> features advanced logging, pre- and post-routing actions, network address translation, and port forwarding, all in one command line interface.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-IPTables-Additional_Resources.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-IPTables-Additional_Resources.html
index 744ce04..1599f01 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-IPTables-Additional_Resources.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-IPTables-Additional_Resources.html
@@ -1,9 +1,9 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.9.6. Additional Resources</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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.5. IPTables and IPv6" /><link rel="next" href="sect-Security_Guide-Additional_Resources-Useful_IP_Tables_Websites.html" title="2.9.6.2. Useful IP Tables Websites" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe,
to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-IPTables-IPTables_and_IPv6.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Additional_Resources-Useful_IP_Tables_Websites.html"><strong>Next</strong></a></li></ul><div class="section" title="2.9.6. Additional Resources" id="sect-Security_Guide-IPTables-Additional_Resources"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.9.6. Additional Resources</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.9.6. Additional Resources</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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.5. IPTables and IPv6" /><link rel="next" href="sect-Security_Guide-Additional_Resources-Useful_IP_Tables_Websites.html" title="2.9.6.2. Useful IP Tables Websites" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, t
o view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-IPTables-IPTables_and_IPv6.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Additional_Resources-Useful_IP_Tables_Websites.html"><strong>Next</strong></a></li></ul><div class="section" title="2.9.6. Additional Resources" id="sect-Security_Guide-IPTables-Additional_Resources"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-IPTables-Additional_Resources">2.9.6. Additional Resources</h3></div></div></div><div class="para">
Refer to the following sources for additional information on packet filtering with <code class="command">iptables</code>.
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<a class="xref" href="sect-Security_Guide-Firewalls.html" title="2.8. Firewalls">Section 2.8, “Firewallsâ€</a> — Contains a chapter about the role of firewalls within an overall security strategy as well as strategies for constructing firewall rules.
- </div></li></ul></div><div class="section" title="2.9.6.1. Installed IP Tables Documentation" id="sect-Security_Guide-Additional_Resources-Installed_IP_Tables_Documentation"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.9.6.1. Installed IP Tables Documentation</h4></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ </div></li></ul></div><div class="section" title="2.9.6.1. Installed IP Tables Documentation" id="sect-Security_Guide-Additional_Resources-Installed_IP_Tables_Documentation"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Additional_Resources-Installed_IP_Tables_Documentation">2.9.6.1. Installed IP Tables Documentation</h4></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="command">man iptables</code> — Contains a description of <code class="command">iptables</code> as well as a comprehensive list of targets, options, and match extensions.
</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>Prev</strong>2.9.5. IPTables and IPv6</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Additional_Resources-Useful_IP_Tables_Websites.html"><strong>Next</strong>2.9.6.2. Useful IP Tables Websites</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-IPTables-Command_Options_for_IPTables.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-IPTables-Command_Options_for_IPTables.html
index 8f7c63c..0995a44 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-IPTables-Command_Options_for_IPTables.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-IPTables-Command_Options_for_IPTables.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.9.2. Command Options for IPTables</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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-Command_Options_for_IPTables-Command_Options.html" title="2.9.2.2. Command Options" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser o
r enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-IPTables.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Command_Options_for_IPTables-Command_Options.html"><strong>Next</strong></a></li></ul><div class="section" title="2.9.2. Command Options for IPTables" id="sect-Security_Guide-IPTables-Command_Options_for_IPTables"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.9.2. Command Options for IPTables</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.9.2. Command Options for IPTables</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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-Command_Options_for_IPTables-Command_Options.html" title="2.9.2.2. Command Options" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or
enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-IPTables.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Command_Options_for_IPTables-Command_Options.html"><strong>Next</strong></a></li></ul><div class="section" title="2.9.2. Command Options for IPTables" id="sect-Security_Guide-IPTables-Command_Options_for_IPTables"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-IPTables-Command_Options_for_IPTables">2.9.2. Command Options for IPTables</h3></div></div></div><div class="para">
Rules for filtering packets are created using the <code class="command">iptables</code> command. The following aspects of the packet are most often used as criteria:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<span class="emphasis"><em>Packet Type</em></span> — Specifies the type of packets the command filters.
@@ -12,10 +12,9 @@
Refer to <a class="xref" href="sect-Security_Guide-Command_Options_for_IPTables-IPTables_Match_Options.html" title="2.9.2.4. IPTables Match Options">Section 2.9.2.4, “IPTables Match Optionsâ€</a> and <a class="xref" href="sect-Security_Guide-Command_Options_for_IPTables-Target_Options.html" title="2.9.2.5. Target Options">Section 2.9.2.5, “Target Optionsâ€</a> for more information about specific options that address these aspects of a packet.
</div><div class="para">
The options used with specific <code class="command">iptables</code> rules must be grouped logically, based on the purpose and conditions of the overall rule, for the rule to be valid. The remainder of this section explains commonly-used options for the <code class="command">iptables</code> command.
- </div><div class="section" title="2.9.2.1. Structure of IPTables Command Options" id="sect-Security_Guide-Command_Options_for_IPTables-Structure_of_IPTables_Command_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.9.2.1. Structure of IPTables Command Options</h4></div></div></div><div class="para">
+ </div><div class="section" title="2.9.2.1. Structure of IPTables Command Options" id="sect-Security_Guide-Command_Options_for_IPTables-Structure_of_IPTables_Command_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Command_Options_for_IPTables-Structure_of_IPTables_Command_Options">2.9.2.1. Structure of IPTables Command Options</h4></div></div></div><div class="para">
Many <code class="command">iptables</code> commands have the following structure:
- </div><pre class="screen"><code class="computeroutput"> iptables [-t <em class="replaceable"><code><table-name></code></em>] <em class="replaceable"><code><command></code></em> <em class="replaceable"><code><chain-name></code></em> \ <em class="replaceable"><code><parameter-1></code></em> <em class="replaceable"><code><option-1></code></em> \ <em class="replaceable"><code><parameter-n></code></em> <em class="replaceable"><code><option-n></code></em></code>
-</pre><div class="para">
+ </div><pre class="screen"><code class="computeroutput"> iptables [-t <em class="replaceable"><code><table-name></code></em>] <em class="replaceable"><code><command></code></em> <em class="replaceable"><code><chain-name></code></em> \ <em class="replaceable"><code><parameter-1></code></em> <em class="replaceable"><code><option-1></code></em> \ <em class="replaceable"><code><parameter-n></code></em> <em class="replaceable"><code><option-n></code></em></code></pre><div class="para">
<em class="replaceable"><code><table-name></code></em> — Specifies which table the rule applies to. If omitted, the <code class="option">filter</code> table is used.
</div><div class="para">
<em class="replaceable"><code><command></code></em> — Specifies the action to perform, such as appending or deleting a rule.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-IPTables-IPTables_Control_Scripts.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-IPTables-IPTables_Control_Scripts.html
index ee5e648..fdc6a60 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-IPTables-IPTables_Control_Scripts.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-IPTables-IPTables_Control_Scripts.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.9.4. IPTables Control Scripts</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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.3. Saving IPTables Rules" /><link rel="next" href="sect-Security_Guide-IPTables-IPTables_and_IPv6.html" title="2.9.5. IPTables and IPv6" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade
your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-IPTables-Saving_IPTables_Rules.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-IPTables-IPTables_and_IPv6.html"><strong>Next</strong></a></li></ul><div class="section" title="2.9.4. IPTables Control Scripts" id="sect-Security_Guide-IPTables-IPTables_Control_Scripts"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.9.4. IPTables Control Scripts</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.9.4. IPTables Control Scripts</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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.3. Saving IPTables Rules" /><link rel="next" href="sect-Security_Guide-IPTables-IPTables_and_IPv6.html" title="2.9.5. IPTables and IPv6" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade
your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-IPTables-Saving_IPTables_Rules.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-IPTables-IPTables_and_IPv6.html"><strong>Next</strong></a></li></ul><div class="section" title="2.9.4. IPTables Control Scripts" id="sect-Security_Guide-IPTables-IPTables_Control_Scripts"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-IPTables-IPTables_Control_Scripts">2.9.4. IPTables Control Scripts</h3></div></div></div><div class="para">
There are two basic methods for controlling <code class="command">iptables</code> in Fedora:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<span class="application"><strong>Firewall Configuration Tool</strong></span> (<code class="command">system-config-securitylevel</code>) — A graphical interface for creating, activating, and saving basic firewall rules. Refer to <a class="xref" href="sect-Security_Guide-Firewalls-Basic_Firewall_Configuration.html" title="2.8.2. Basic Firewall Configuration">Section 2.8.2, “Basic Firewall Configurationâ€</a> for more information.
@@ -8,8 +8,7 @@
<code class="command">/sbin/service iptables <em class="replaceable"><code><option></code></em></code> — Used to manipulate various functions of <code class="command">iptables</code> using its initscript. The following options are available:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="command">start</code> — If a firewall is configured (that is, <code class="filename">/etc/sysconfig/iptables</code> exists), all running <code class="command">iptables</code> are stopped completely and then started using the <code class="command">/sbin/iptables-restore</code> command. This option only works if the <code class="command">ipchains</code> kernel module is not loaded. To check if this module is loaded, type the following command as root:
- </div><pre class="screen"><code class="command"> [root at MyServer ~]# lsmod | grep ipchains </code>
-</pre><div class="para">
+ </div><pre class="screen"><code class="command"> [root at MyServer ~]# lsmod | grep ipchains </code></pre><div class="para">
If this command returns no output, it means the module is not loaded. If necessary, use the <code class="command">/sbin/rmmod</code> command to remove the module.
</div></li><li class="listitem"><div class="para">
<code class="command">stop</code> — If a firewall is running, the firewall rules in memory are flushed, and all iptables modules and helpers are unloaded.
@@ -35,7 +34,7 @@
<code class="command">save</code> — Saves firewall rules to <code class="filename">/etc/sysconfig/iptables</code> using <code class="command">iptables-save</code>. Refer to <a class="xref" href="sect-Security_Guide-IPTables-Saving_IPTables_Rules.html" title="2.9.3. Saving IPTables Rules">Section 2.9.3, “Saving IPTables Rulesâ€</a> for more information.
</div></li></ul></div></li></ul></div><div class="note"><h2>Note</h2><div class="para">
To use the same initscript commands to control netfilter for IPv6, substitute <code class="command">ip6tables</code> for <code class="command">iptables</code> in the <code class="command">/sbin/service</code> commands listed in this section. For more information about IPv6 and netfilter, refer to <a class="xref" href="sect-Security_Guide-IPTables-IPTables_and_IPv6.html" title="2.9.5. IPTables and IPv6">Section 2.9.5, “IPTables and IPv6â€</a>.
- </div></div><div class="section" title="2.9.4.1. IPTables Control Scripts Configuration File" id="sect-Security_Guide-IPTables_Control_Scripts-IPTables_Control_Scripts_Configuration_File"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.9.4.1. IPTables Control Scripts Configuration File</h4></div></div></div><div class="para">
+ </div></div><div class="section" title="2.9.4.1. IPTables Control Scripts Configuration File" id="sect-Security_Guide-IPTables_Control_Scripts-IPTables_Control_Scripts_Configuration_File"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-IPTables_Control_Scripts-IPTables_Control_Scripts_Configuration_File">2.9.4.1. IPTables Control Scripts Configuration File</h4></div></div></div><div class="para">
The behavior of the <code class="command">iptables</code> initscripts is controlled by the <code class="filename">/etc/sysconfig/iptables-config</code> configuration file. The following is a list of directives contained in this file:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="command">IPTABLES_MODULES</code> — Specifies a space-separated list of additional <code class="command">iptables</code> modules to load when a firewall is activated. These can include connection tracking and NAT helpers.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-IPTables-IPTables_and_IPv6.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-IPTables-IPTables_and_IPv6.html
index 7401279..c775128 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-IPTables-IPTables_and_IPv6.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-IPTables-IPTables_and_IPv6.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.9.5. IPTables and IPv6</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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.4. IPTables Control Scripts" /><link rel="next" href="sect-Security_Guide-IPTables-Additional_Resources.html" title="2.9.6. Additional Resources" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it up
grade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-IPTables-IPTables_Control_Scripts.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-IPTables-Additional_Resources.html"><strong>Next</strong></a></li></ul><div class="section" title="2.9.5. IPTables and IPv6" id="sect-Security_Guide-IPTables-IPTables_and_IPv6"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.9.5. IPTables and IPv6</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.9.5. IPTables and IPv6</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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.4. IPTables Control Scripts" /><link rel="next" href="sect-Security_Guide-IPTables-Additional_Resources.html" title="2.9.6. Additional Resources" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upg
rade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-IPTables-IPTables_Control_Scripts.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-IPTables-Additional_Resources.html"><strong>Next</strong></a></li></ul><div class="section" title="2.9.5. IPTables and IPv6" id="sect-Security_Guide-IPTables-IPTables_and_IPv6"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-IPTables-IPTables_and_IPv6">2.9.5. IPTables and IPv6</h3></div></div></div><div class="para">
If the <code class="filename">iptables-ipv6</code> package is installed, netfilter in Fedora can filter the next-generation IPv6 Internet protocol. The command used to manipulate the IPv6 netfilter is <code class="command">ip6tables</code>.
</div><div class="para">
Most directives for this command are identical to those used for <code class="command">iptables</code>, except the <code class="command">nat</code> table is not yet supported. This means that it is not yet possible to perform IPv6 network address translation tasks, such as masquerading and port forwarding.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-IPTables-Saving_IPTables_Rules.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-IPTables-Saving_IPTables_Rules.html
index d79b30d..711e383 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-IPTables-Saving_IPTables_Rules.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-IPTables-Saving_IPTables_Rules.html
@@ -1,9 +1,8 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. Saving IPTables Rules</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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.2.6. Listing Options" /><link rel="next" href="sect-Security_Guide-IPTables-IPTables_Control_Scripts.html" title="2.9.4. IPTables Control Scripts" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an ifram
e, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Command_Options_for_IPTables-Listing_Options.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-IPTables-IPTables_Control_Scripts.html"><strong>Next</strong></a></li></ul><div class="section" title="2.9.3. Saving IPTables Rules" id="sect-Security_Guide-IPTables-Saving_IPTables_Rules"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.9.3. Saving IPTables Rules</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.9.3. Saving IPTables Rules</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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.2.6. Listing Options" /><link rel="next" href="sect-Security_Guide-IPTables-IPTables_Control_Scripts.html" title="2.9.4. IPTables Control Scripts" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe
, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Command_Options_for_IPTables-Listing_Options.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-IPTables-IPTables_Control_Scripts.html"><strong>Next</strong></a></li></ul><div class="section" title="2.9.3. Saving IPTables Rules" id="sect-Security_Guide-IPTables-Saving_IPTables_Rules"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-IPTables-Saving_IPTables_Rules">2.9.3. Saving IPTables Rules</h3></div></div></div><div class="para">
Rules created with the <code class="command">iptables</code> command are stored in memory. If the system is restarted before saving the <code class="command">iptables</code> rule set, all rules are lost. For netfilter rules to persist through a system reboot, they need to be saved. To save netfilter rules, type the following command as root:
- </div><pre class="screen"><code class="command"> /sbin/service iptables save </code>
-</pre><div class="para">
+ </div><pre class="screen"><code class="command"> /sbin/service iptables save </code></pre><div class="para">
This executes the <code class="command">iptables</code> init script, which runs the <code class="command">/sbin/iptables-save</code> program and writes the current <code class="command">iptables</code> configuration to <code class="filename">/etc/sysconfig/iptables</code>. The existing <code class="filename">/etc/sysconfig/iptables</code> file is saved as <code class="filename">/etc/sysconfig/iptables.save</code>.
</div><div class="para">
The next time the system boots, the <code class="command">iptables</code> init script reapplies the rules saved in <code class="filename">/etc/sysconfig/iptables</code> by using the <code class="command">/sbin/iptables-restore</code> command.
@@ -11,8 +10,7 @@
While it is always a good idea to test a new <code class="command">iptables</code> rule before committing it to the <code class="filename">/etc/sysconfig/iptables</code> file, it is possible to copy <code class="command">iptables</code> rules into this file from another system's version of this file. This provides a quick way to distribute sets of <code class="command">iptables</code> rules to multiple machines.
</div><div class="para">
You can also save the iptables rules to a separate file for distribution, backup or other purposes. To save your iptables rules, type the following command as 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">
+ </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">
If distributing the <code class="filename">/etc/sysconfig/iptables</code> file to other machines, type <code class="command">/sbin/service iptables restart</code> for the new rules to take effect.
</div></div><div class="note"><h2>Note</h2><div class="para">
Note the difference between the <code class="command">iptables</code> <span class="emphasis"><em>command</em></span> (<code class="command">/sbin/iptables</code>), which is used to manipulate the tables and chains that constitute the <code class="command">iptables</code> functionality, and the <code class="command">iptables</code> <span class="emphasis"><em>service</em></span> (<code class="command">/sbin/iptables service</code>), which is used to enable and disable the <code class="command">iptables</code> service itself.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-IPTables.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-IPTables.html
index fe92b40..731ec6d 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-IPTables.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-IPTables.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.9. IPTables</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="chap-Security_Guide-Securing_Your_Network.html" title="Chapter 2. Securing Your Network" /><link rel="prev" href="sect-Security_Guide-Additional_Resources-Related_Documentation.html" title="2.8.9.3. Related Documentation" /><link rel="next" href="sect-Security_Guide-IPTables-Command_Options_for_IPTables.html" title="2.9.2. Command Options for IPTables" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../..
/../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Additional_Resources-Related_Documentation.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-IPTables-Command_Options_for_IPTables.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" title="2.9. IPTables" id="sect-Security_Guide-IPTables" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.9. IPTables</h2></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.9. IPTables</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="chap-Security_Guide-Securing_Your_Network.html" title="Chapter 2. Securing Your Network" /><link rel="prev" href="sect-Security_Guide-Additional_Resources-Related_Documentation.html" title="2.8.9.3. Related Documentation" /><link rel="next" href="sect-Security_Guide-IPTables-Command_Options_for_IPTables.html" title="2.9.2. Command Options for IPTables" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../
../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Additional_Resources-Related_Documentation.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-IPTables-Command_Options_for_IPTables.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" title="2.9. IPTables" id="sect-Security_Guide-IPTables" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sect-Security_Guide-IPTables">2.9. IPTables</h2></div></div></div><div class="para">
Included with Fedora are advanced tools for network <em class="firstterm">packet filtering</em> — the process of controlling network packets as they enter, move through, and exit the network stack within the kernel. Kernel versions prior to 2.4 relied on <code class="command">ipchains</code> for packet filtering and used lists of rules applied to packets at each step of the filtering process. The 2.4 kernel introduced <code class="command">iptables</code> (also called <em class="firstterm">netfilter</em>), which is similar to <code class="command">ipchains</code> but greatly expands the scope and control available for filtering network packets.
</div><div class="para">
This chapter focuses on packet filtering basics, explains various options available with <code class="command">iptables</code> commands, and explains how filtering rules can be preserved between system reboots.
@@ -10,7 +10,7 @@
The default firewall mechanism in the 2.4 and later kernels is <code class="command">iptables</code>, but <code class="command">iptables</code> cannot be used if <code class="command">ipchains</code> is already running. If <code class="command">ipchains</code> is present at boot time, the kernel issues an error and fails to start <code class="command">iptables</code>.
</div><div class="para">
The functionality of <code class="command">ipchains</code> is not affected by these errors.
- </div></div><div class="section" title="2.9.1. Packet Filtering" id="sect-Security_Guide-IPTables-Packet_Filtering"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.9.1. Packet Filtering</h3></div></div></div><div class="para">
+ </div></div><div class="section" title="2.9.1. Packet Filtering" id="sect-Security_Guide-IPTables-Packet_Filtering"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-IPTables-Packet_Filtering">2.9.1. Packet Filtering</h3></div></div></div><div class="para">
The Linux kernel uses the <span class="application"><strong>Netfilter</strong></span> facility to filter packets, allowing some of them to be received by or pass through the system while stopping others. This facility is built in to the Linux kernel, and has three built-in <em class="firstterm">tables</em> or <em class="firstterm">rules lists</em>, as follows:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="option">filter</code> — The default table for handling network packets.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-IPTables_Match_Options-Additional_Match_Option_Modules.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-IPTables_Match_Options-Additional_Match_Option_Modules.html
index 67b3949..d82c5a1 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-IPTables_Match_Options-Additional_Match_Option_Modules.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-IPTables_Match_Options-Additional_Match_Option_Modules.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.9.2.4.4. Additional Match Option Modules</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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.2.4. IPTables Match Options" /><link rel="prev" href="sect-Security_Guide-IPTables_Match_Options-ICMP_Protocol.html" title="2.9.2.4.3. ICMP Protocol" /><link rel="next" href="sect-Security_Guide-Command_Options_for_IPTables-Target_Options.html" title="2.9.2.5. Target Options" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-IPTables_Match_Options-ICMP_Protocol.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Command_Options_for_IPTables-Target_Options.html"><strong>Next</strong></a></li></ul><div class="section" title="2.9.2.4.4. Additional Match Option Modules" id="sect-Security_Guide-IPTables_Match_Options-Additional_Match_Option_Modules"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.9.2.4.4. Additional Mat
ch Option Modules</h5></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.9.2.4.4. Additional Match Option Modules</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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.2.4. IPTables Match Options" /><link rel="prev" href="sect-Security_Guide-IPTables_Match_Options-ICMP_Protocol.html" title="2.9.2.4.3. ICMP Protocol" /><link rel="next" href="sect-Security_Guide-Command_Options_for_IPTables-Target_Options.html" title="2.9.2.5. Target Options" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe i
d="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-IPTables_Match_Options-ICMP_Protocol.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Command_Options_for_IPTables-Target_Options.html"><strong>Next</strong></a></li></ul><div class="section" title="2.9.2.4.4. Additional Match Option Modules" id="sect-Security_Guide-IPTables_Match_Options-Additional_Match_Option_Modules"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-Security_Guide-IPT
ables_Match_Options-Additional_Match_Option_Modules">2.9.2.4.4. Additional Match Option Modules</h5></div></div></div><div class="para">
Additional match options are available through modules loaded by the <code class="command">iptables</code> command.
</div><div class="para">
To use a match option module, load the module by name using the <code class="option">-m <em class="replaceable"><code><module-name></code></em></code>, where <em class="replaceable"><code><module-name></code></em> is the name of the module.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-IPTables_Match_Options-ICMP_Protocol.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-IPTables_Match_Options-ICMP_Protocol.html
index c8e0d7c..6cbffc9 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-IPTables_Match_Options-ICMP_Protocol.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-IPTables_Match_Options-ICMP_Protocol.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.9.2.4.3. ICMP Protocol</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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.2.4. IPTables Match Options" /><link rel="prev" href="sect-Security_Guide-IPTables_Match_Options-UDP_Protocol.html" title="2.9.2.4.2. UDP Protocol" /><link rel="next" href="sect-Security_Guide-IPTables_Match_Options-Additional_Match_Option_Modules.html" title="2.9.2.4.4. Additional Match Option Modules" /></head><body class="toc_embeded "><div id="tocdiv" class="toc
"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-IPTables_Match_Options-UDP_Protocol.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-IPTables_Match_Options-Additional_Match_Option_Modules.html"><strong>Next</strong></a></li></ul><div class="section" title="2.9.2.4.3. ICMP Protocol" id="sect-Security_Guide-IPTables_Match_Options-ICMP_Protocol"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.9.2.4.3. ICMP Protocol</h5></div></div>
</div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.9.2.4.3. ICMP Protocol</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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.2.4. IPTables Match Options" /><link rel="prev" href="sect-Security_Guide-IPTables_Match_Options-UDP_Protocol.html" title="2.9.2.4.2. UDP Protocol" /><link rel="next" href="sect-Security_Guide-IPTables_Match_Options-Additional_Match_Option_Modules.html" title="2.9.2.4.4. Additional Match Option Modules" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"
><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-IPTables_Match_Options-UDP_Protocol.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-IPTables_Match_Options-Additional_Match_Option_Modules.html"><strong>Next</strong></a></li></ul><div class="section" title="2.9.2.4.3. ICMP Protocol" id="sect-Security_Guide-IPTables_Match_Options-ICMP_Protocol"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-Security_Guide-IPTables_Match_Opti
ons-ICMP_Protocol">2.9.2.4.3. ICMP Protocol</h5></div></div></div><div class="para">
The following match options are available for the Internet Control Message Protocol (ICMP) (<code class="option">-p icmp</code>):
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="option">--icmp-type</code> — Sets the name or number of the ICMP type to match with the rule. A list of valid ICMP names can be retrieved by typing the <code class="command">iptables -p icmp -h</code> command.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-IPTables_Match_Options-UDP_Protocol.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-IPTables_Match_Options-UDP_Protocol.html
index 22ed178..0458d20 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-IPTables_Match_Options-UDP_Protocol.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-IPTables_Match_Options-UDP_Protocol.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.9.2.4.2. UDP Protocol</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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.2.4. IPTables Match Options" /><link rel="prev" href="sect-Security_Guide-Command_Options_for_IPTables-IPTables_Match_Options.html" title="2.9.2.4. IPTables Match Options" /><link rel="next" href="sect-Security_Guide-IPTables_Match_Options-ICMP_Protocol.html" title="2.9.2.4.3. ICMP Protocol" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id=
"tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Command_Options_for_IPTables-IPTables_Match_Options.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-IPTables_Match_Options-ICMP_Protocol.html"><strong>Next</strong></a></li></ul><div class="section" title="2.9.2.4.2. UDP Protocol" id="sect-Security_Guide-IPTables_Match_Options-UDP_Protocol"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.9.2.4.2. UDP Protocol</h5></div></div></div><div class="
para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.9.2.4.2. UDP Protocol</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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.2.4. IPTables Match Options" /><link rel="prev" href="sect-Security_Guide-Command_Options_for_IPTables-IPTables_Match_Options.html" title="2.9.2.4. IPTables Match Options" /><link rel="next" href="sect-Security_Guide-IPTables_Match_Options-ICMP_Protocol.html" title="2.9.2.4.3. ICMP Protocol" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="
tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Command_Options_for_IPTables-IPTables_Match_Options.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-IPTables_Match_Options-ICMP_Protocol.html"><strong>Next</strong></a></li></ul><div class="section" title="2.9.2.4.2. UDP Protocol" id="sect-Security_Guide-IPTables_Match_Options-UDP_Protocol"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-Security_Guide-IPTables_Match_Options-UDP_Protocol"
>2.9.2.4.2. UDP Protocol</h5></div></div></div><div class="para">
These match options are available for the UDP protocol (<code class="option">-p udp</code>):
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="option">--dport</code> — Specifies the destination port of the UDP packet, using the service name, port number, or range of port numbers. The <code class="option">--destination-port</code> match option is synonymous with <code class="option">--dport</code>.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-IPsec_Host_to_Host_Configuration-Manual_IPsec_Host_to_Host_Configuration.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-IPsec_Host_to_Host_Configuration-Manual_IPsec_Host_to_Host_Configuration.html
index 8a5a076..19ee4af 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-IPsec_Host_to_Host_Configuration-Manual_IPsec_Host_to_Host_Configuration.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-IPsec_Host_to_Host_Configuration-Manual_IPsec_Host_to_Host_Configuration.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.7.6.2. Manual IPsec Host-to-Host Configuration</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Host_to_Host_Configuration.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Network_to_Network_Configuration.html"><strong>Next</strong></a></li></ul><div class="section" title="2.7.6.2. Manual IPsec Host-to-Host Configuration" id="sect-Security_Guide-
IPsec_Host_to_Host_Configuration-Manual_IPsec_Host_to_Host_Configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.7.6.2. Manual <abbr class="abbrev">IPsec</abbr> Host-to-Host Configuration</h4></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.7.6.2. Manual IPsec Host-to-Host Configuration</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. I
Psec Network-to-Network Configuration" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Host_to_Host_Configuration.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Network_to_Network_Configuration.html"><strong>Next</strong></a></li></ul><div class="section" title="2.7.6.2. Manual IPsec Host-to-Host Configuration" id="sect-Security_Guide-I
Psec_Host_to_Host_Configuration-Manual_IPsec_Host_to_Host_Configuration"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><div class="para">
The IP address of each host
@@ -20,16 +20,13 @@
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">
+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">
+ </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">
+ </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.
@@ -42,8 +39,7 @@ IKE_METHOD=PSK
authentication_method pre_shared_key;
dh_group 2 ;
}
-}
-</pre><div class="para">
+}</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.
@@ -59,7 +55,7 @@ IKE_METHOD=PSK
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" title="2.7.6.2.1. The Racoon Configuration File" id="sect-Security_Guide-Manual_IPsec_Host_to_Host_Configuration-The_Racoon_Configuration_File"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.7.6.2.1. The Racoon Configuration File</h5></div></div></div><div class="para">
+ </div></dd></dl></div><div class="section" title="2.7.6.2.1. The Racoon Configuration File" id="sect-Security_Guide-Manual_IPsec_Host_to_Host_Configuration-The_Racoon_Configuration_File"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-Security_Guide-Manual_IPsec_Host_to_Host_Configuration-The_Racoon_Configuration_File">2.7.6.2.1. The Racoon Configuration File</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.
@@ -76,8 +72,7 @@ sainfo anonymous
authentication_algorithm hmac_sha1, hmac_md5 ;
compression_algorithm deflate ;
}
-include "/etc/racoon/X.X.X.X.conf";
-</pre><div class="para">
+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.
@@ -93,12 +88,10 @@ include "/etc/racoon/X.X.X.X.conf";
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">
+ </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>Prev</strong>2.7.6. IPsec Host-to-Host Configuration</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Network_to_Network_Configuration.html"><strong>Next</strong>2.7.7. IPsec Network-to-Network Configuration</a></li></ul></body></html>
+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>Prev</strong>2.7.6. IPsec Host-to-Host Configuration</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Network_to_Network_Configuration.html"><strong>Next</strong>2.7.7. IPsec Network-to-Network Configuration</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-IPsec_Network_to_Network_Configuration-Manual_IPsec_Network_to_Network_Configuration.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-IPsec_Network_to_Network_Configuration-Manual_IPsec_Network_to_Network_Configuration.html
index 414c19b..e969344 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-IPsec_Network_to_Network_Configuration-Manual_IPsec_Network_to_Network_Configuration.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-IPsec_Network_to_Network_Configuration-Manual_IPsec_Network_to_Network_Configuration.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.7.7.2. Manual IPsec Network-to-Network Configuration</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Network_to_Network_Configuration.html"><strong>Prev</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>Next</strong></a></li></ul><div class="section" title="2.7.7.2. Manual IPsec Network
-to-Network Configuration" id="sect-Security_Guide-IPsec_Network_to_Network_Configuration-Manual_IPsec_Network_to_Network_Configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.7.7.2. Manual <abbr class="abbrev">IPsec</abbr> Network-to-Network Configuration</h4></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.7.7.2. Manual IPsec Network-to-Network Configuration</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Network_to_Network_Configuration.html"><strong>Prev</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>Next</strong></a></li></ul><div class="section" title="2.7.7.2. Manual IPsec Network-
to-Network Configuration" id="sect-Security_Guide-IPsec_Network_to_Network_Configuration-Manual_IPsec_Network_to_Network_Configuration"><div class="titlepage"><div><div keep-together.within-column="always"><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="para">
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>.
@@ -13,8 +13,7 @@ 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">
+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">
Specifies the type of connection.
@@ -34,11 +33,9 @@ DST=<em class="replaceable"><code>X.X.X.X</code></em>
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">
+ </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">
+ </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.
@@ -56,8 +53,7 @@ sainfo anonymous
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">
+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;
@@ -68,26 +64,20 @@ include "/etc/racoon/<em class="replaceable"><code>X.X.X.X</code></em>.conf"
authentication_method pre_shared_key;
dh_group 2 ;
}
-}
-</pre><div class="para">
+}</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 class="listitem"><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 class="listitem"><div class="para">
Use the following command to enable the change:
- </div><pre class="screen">[root at myServer ~] # sysctl -p /etc/sysctl.conf
-</pre></li></ol></div><div class="para">
+ </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">
+ </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">
+ </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">
+ </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>Prev</strong>2.7.7. IPsec Network-to-Network Configuration</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</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>Next</strong>2.7.8. Starting and Stopping an IPsec Connection</a></li></ul></body></html>
+ (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>Prev</strong>2.7.7. IPsec Network-to-Network Configuration</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</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>Next</strong>2.7.8. Starting and Stopping an IPsec Connection</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Kerberos-Additional_Resources.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Kerberos-Additional_Resources.html
index 7f28a6a..fd6e91f 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Kerberos-Additional_Resources.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Kerberos-Additional_Resources.html
@@ -1,8 +1,8 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Setting Up Cross Realm Authentication" /><link rel="next" href="sect-Security_Guide-Additional_Resources-Useful_Kerberos_Websites.html" title="2.6.10.2. Useful Kerberos Websites" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src=".
./../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Kerberos-Setting_Up_Cross_Realm_Authentication.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Additional_Resources-Useful_Kerberos_Websites.html"><strong>Next</strong></a></li></ul><div class="section" title="2.6.10. Additional Resources" id="sect-Security_Guide-Kerberos-Additional_Resources"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.6.10. Additional Resources</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.6.10. Additional Resources</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Setting Up Cross Realm Authentication" /><link rel="next" href="sect-Security_Guide-Additional_Resources-Useful_Kerberos_Websites.html" title="2.6.10.2. Useful Kerberos Websites" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="..
/../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Kerberos-Setting_Up_Cross_Realm_Authentication.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Additional_Resources-Useful_Kerberos_Websites.html"><strong>Next</strong></a></li></ul><div class="section" title="2.6.10. Additional Resources" id="sect-Security_Guide-Kerberos-Additional_Resources"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Kerberos-Additional_Resources">2.6.10. Additional Resources</
h3></div></div></div><div class="para">
For more information about Kerberos, refer to the following resources.
- </div><div class="section" title="2.6.10.1. Installed Kerberos Documentation" id="sect-Security_Guide-Additional_Resources-Installed_Kerberos_Documentation"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.6.10.1. Installed Kerberos Documentation</h4></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ </div><div class="section" title="2.6.10.1. Installed Kerberos Documentation" id="sect-Security_Guide-Additional_Resources-Installed_Kerberos_Documentation"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><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 class="listitem"><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).
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Client.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Client.html
index 3d709b6..5a2140e 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Client.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Client.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.6.6. Configuring a Kerberos 5 Client</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html
">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Server.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Kerberos-Domain_to_Realm_Mapping.html"><strong>Next</strong></a></li></ul><div class="section" title="2.6.6. Configuring a Kerberos 5 Client" id="sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Client"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.6.6. Configuring a Kerberos 5 Client</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.6.6. Configuring a Kerberos 5 Client</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html"
>This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Server.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Kerberos-Domain_to_Realm_Mapping.html"><strong>Next</strong></a></li></ul><div class="section" title="2.6.6. Configuring a Kerberos 5 Client" id="sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Client"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Client">2.6.6. Configuring a Kerberos 5 Clie
nt</h3></div></div></div><div class="para">
Setting up a Kerberos 5 client is less involved than setting up a server. At a minimum, install the client packages and provide each client with a valid <code class="filename">krb5.conf</code> configuration file. While <code class="command">ssh</code> and <code class="command">slogin</code> are the preferred method of remotely logging in to client systems, Kerberized versions of <code class="command">rsh</code> and <code class="command">rlogin</code> are still available, though deploying them requires that a few more configuration changes be made.
</div><div class="procedure"><ol class="1"><li class="step" title="Step 1"><div class="para">
Be sure that time synchronization is in place between the Kerberos client and the KDC. Refer to <a class="xref" href="sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Server.html" title="2.6.5. Configuring a Kerberos 5 Server">Section 2.6.5, “Configuring a Kerberos 5 Serverâ€</a> for more information. In addition, verify that DNS is working properly on the Kerberos client before configuring the Kerberos client programs.
@@ -10,11 +10,9 @@
Before a workstation in the realm can use Kerberos to authenticate users who connect using <code class="command">ssh</code> or Kerberized <code class="command">rsh</code> or <code class="command">rlogin</code>, it must have its own host principal in the Kerberos database. The <code class="command">sshd</code>, <code class="command">kshd</code>, and <code class="command">klogind</code> server programs all need access to the keys for the <span class="emphasis"><em>host</em></span> service's principal. Additionally, in order to use the kerberized <code class="command">rsh</code> and <code class="command">rlogin</code> services, that workstation must have the <code class="filename">xinetd</code> package installed.
</div><div class="para">
Using <code class="command">kadmin</code>, add a host principal for the workstation on the KDC. The instance in this case is the hostname of the workstation. Use the <code class="command">-randkey</code> option for the <code class="command">kadmin</code>'s <code class="command">addprinc</code> command to create the principal and assign it a random key:
- </div><pre class="screen">addprinc -randkey host/<em class="replaceable"><code>blah.example.com</code></em>
-</pre><div class="para">
+ </div><pre class="screen">addprinc -randkey host/<em class="replaceable"><code>blah.example.com</code></em></pre><div class="para">
Now that the principal has been created, keys can be extracted for the workstation by running <code class="command">kadmin</code> <span class="emphasis"><em>on the workstation itself</em></span>, and using the <code class="command">ktadd</code> command within <code class="command">kadmin</code>:
- </div><pre class="screen">ktadd -k /etc/krb5.keytab host/<em class="replaceable"><code>blah.example.com</code></em>
-</pre></li><li class="step" title="Step 4"><div class="para">
+ </div><pre class="screen">ktadd -k /etc/krb5.keytab host/<em class="replaceable"><code>blah.example.com</code></em></pre></li><li class="step" title="Step 4"><div class="para">
To use other kerberized network services, they must first be started. Below is a list of some common kerberized services and instructions about enabling them:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="command">ssh</code> — OpenSSH uses GSS-API to authenticate users to servers if the client's and server's configuration both have <code class="option">GSSAPIAuthentication</code> enabled. If the client also has <code class="option">GSSAPIDelegateCredentials</code> enabled, the user's credentials are made available on the remote system.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Server.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Server.html
index 9f94829..e58f000 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Server.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Server.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.6.5. Configuring a Kerberos 5 Server</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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 and 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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an i
frame, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Kerberos-Kerberos_and_PAM.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Client.html"><strong>Next</strong></a></li></ul><div class="section" title="2.6.5. Configuring a Kerberos 5 Server" id="sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Server"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.6.5. Configuring a Kerberos 5 Server</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.6.5. Configuring a Kerberos 5 Server</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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 and 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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an if
rame, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Kerberos-Kerberos_and_PAM.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Client.html"><strong>Next</strong></a></li></ul><div class="section" title="2.6.5. Configuring a Kerberos 5 Server" id="sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Server"><div class="titlepage"><div><div keep-together.within-column="always"><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">
When setting up Kerberos, install the KDC first. If it is necessary to set up slave servers, install the master first.
</div><div class="para">
To configure the first Kerberos KDC, follow these steps:
@@ -14,13 +14,11 @@
Edit the <code class="filename">/etc/krb5.conf</code> and <code class="filename">/var/kerberos/krb5kdc/kdc.conf</code> configuration files to reflect the realm name and domain-to-realm mappings. A simple realm can be constructed by replacing instances of <em class="replaceable"><code>EXAMPLE.COM</code></em> and <em class="replaceable"><code>example.com</code></em> with the correct domain name — being certain to keep uppercase and lowercase names in the correct format — and by changing the KDC from <em class="replaceable"><code>kerberos.example.com</code></em> to the name of the Kerberos server. By convention, all realm names are uppercase and all DNS hostnames and domain names are lowercase. For full details about the formats of these configuration files, refer to their respective man pages.
</div></li><li class="step" title="Step 4"><div class="para">
Create the database using the <code class="command">kdb5_util</code> utility from a shell prompt:
- </div><pre class="screen">/usr/kerberos/sbin/kdb5_util create -s
-</pre><div class="para">
+ </div><pre class="screen">/usr/kerberos/sbin/kdb5_util create -s</pre><div class="para">
The <code class="command">create</code> command creates the database that stores keys for the Kerberos realm. The <code class="command">-s</code> switch forces creation of a <em class="firstterm">stash</em> file in which the master server key is stored. If no stash file is present from which to read the key, the Kerberos server (<code class="command">krb5kdc</code>) prompts the user for the master server password (which can be used to regenerate the key) every time it starts.
</div></li><li class="step" title="Step 5"><div class="para">
Edit the <code class="filename">/var/kerberos/krb5kdc/kadm5.acl</code> file. This file is used by <code class="command">kadmind</code> to determine which principals have administrative access to the Kerberos database and their level of access. Most organizations can get by with a single line:
- </div><pre class="screen">*/admin at EXAMPLE.COMÂ Â *
-</pre><div class="para">
+ </div><pre class="screen">*/admin at EXAMPLE.COMÂ Â *</pre><div class="para">
Most users are represented in the database by a single principal (with a <span class="emphasis"><em>NULL</em></span>, or empty, instance, such as <span class="emphasis"><em>joe at EXAMPLE.COM</em></span>). In this configuration, users with a second principal with an instance of <span class="emphasis"><em>admin</em></span> (for example, <span class="emphasis"><em>joe/admin at EXAMPLE.COM</em></span>) are able to wield full power over the realm's Kerberos database.
</div><div class="para">
After <code class="command">kadmind</code> has been started on the server, any user can access its services by running <code class="command">kadmin</code> on any of the clients or servers in the realm. However, only users listed in the <code class="filename">kadm5.acl</code> file can modify the database in any way, except for changing their own passwords.
@@ -28,13 +26,11 @@
The <code class="command">kadmin</code> utility communicates with the <code class="command">kadmind</code> server over the network, and uses Kerberos to handle authentication. Consequently, the first principal must already exist before connecting to the server over the network to administer it. Create the first principal with the <code class="command">kadmin.local</code> command, which is specifically designed to be used on the same host as the KDC and does not use Kerberos for authentication.
</div></div><div class="para">
Type the following <code class="command">kadmin.local</code> command at the KDC terminal to create the first principal:
- </div><pre class="screen">/usr/kerberos/sbin/kadmin.local -q "addprinc <em class="replaceable"><code>username</code></em>/admin"
-</pre></li><li class="step" title="Step 6"><div class="para">
+ </div><pre class="screen">/usr/kerberos/sbin/kadmin.local -q "addprinc <em class="replaceable"><code>username</code></em>/admin"</pre></li><li class="step" title="Step 6"><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 class="step" title="Step 7"><div class="para">
+/sbin/service krb524 start</pre></li><li class="step" title="Step 7"><div class="para">
Add principals for the users using the <code class="command">addprinc</code> command within <code class="command">kadmin</code>. <code class="command">kadmin</code> and <code class="command">kadmin.local</code> are command line interfaces to the KDC. As such, many commands — such as <code class="command">addprinc</code> — are available after launching the <code class="command">kadmin</code> program. Refer to the <code class="command">kadmin</code> man page for more information.
</div></li><li class="step" title="Step 8"><div class="para">
Verify that the KDC is issuing tickets. First, run <code class="command">kinit</code> to obtain a ticket and store it in a credential cache file. Next, use <code class="command">klist</code> to view the list of credentials in the cache and use <code class="command">kdestroy</code> to destroy the cache and the credentials it contains.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Kerberos-Domain_to_Realm_Mapping.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Kerberos-Domain_to_Realm_Mapping.html
index 6056652..b40d267 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Kerberos-Domain_to_Realm_Mapping.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Kerberos-Domain_to_Realm_Mapping.html
@@ -1,18 +1,16 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.6.7. Domain-to-Realm Mapping</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">Th
is is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Client.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Kerberos-Setting_Up_Secondary_KDCs.html"><strong>Next</strong></a></li></ul><div class="section" title="2.6.7. Domain-to-Realm Mapping" id="sect-Security_Guide-Kerberos-Domain_to_Realm_Mapping"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.6.7. Domain-to-Realm Mapping</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.6.7. Domain-to-Realm Mapping</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">Thi
s is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Client.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Kerberos-Setting_Up_Secondary_KDCs.html"><strong>Next</strong></a></li></ul><div class="section" title="2.6.7. Domain-to-Realm Mapping" id="sect-Security_Guide-Kerberos-Domain_to_Realm_Mapping"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Kerberos-Domain_to_Realm_Mapping">2.6.7. Domain-to-Realm Mapping</h3></div></div></div><div clas
s="para">
When a client attempts to access a service running on a particular server, it knows the name of the service (<span class="emphasis"><em>host</em></span>) and the name of the server (<span class="emphasis"><em>foo.example.com</em></span>), but because more than one realm may be deployed on your network, it must guess at the name of the realm in which the service resides.
</div><div class="para">
By default, the name of the realm is taken to be the DNS domain name of the server, upper-cased.
</div><div class="literallayout"><p>foo.example.org → EXAMPLE.ORG<br />
foo.example.com → EXAMPLE.COM<br />
foo.hq.example.com → HQ.EXAMPLE.COM<br />
-<br />
</p></div><div class="para">
In some configurations, this will be sufficient, but in others, the realm name which is derived will be the name of a non-existant realm. In these cases, the mapping from the server's DNS domain name to the name of its realm must be specified in the <span class="emphasis"><em>domain_realm</em></span> section of the client system's <code class="filename">krb5.conf</code>. For example:
</div><pre class="screen">[domain_realm]
.example.com = EXAMPLE.COM
-example.com = EXAMPLE.COM
-</pre><div class="para">
+example.com = EXAMPLE.COM</pre><div class="para">
The above configuration specifies two mappings. The first mapping specifies that any system in the "example.com" DNS domain belongs to the <span class="emphasis"><em>EXAMPLE.COM</em></span> realm. The second specifies that a system with the exact name "example.com" is also in the realm. (The distinction between a domain and a specific host is marked by the presence or lack of an initial ".".) The mapping can also be stored directly in DNS.
</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Client.html"><strong>Prev</strong>2.6.6. Configuring a Kerberos 5 Client</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Kerberos-Setting_Up_Secondary_KDCs.html"><strong>Next</strong>2.6.8. Setting Up Secondary KDCs</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Kerberos-How_Kerberos_Works.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Kerberos-How_Kerberos_Works.html
index 2f66749..68b5568 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Kerberos-How_Kerberos_Works.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Kerberos-How_Kerberos_Works.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.6.3. How Kerberos Works</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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 and PAM" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your brow
ser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Kerberos-Kerberos_Terminology.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Kerberos-Kerberos_and_PAM.html"><strong>Next</strong></a></li></ul><div class="section" title="2.6.3. How Kerberos Works" id="sect-Security_Guide-Kerberos-How_Kerberos_Works"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.6.3. How Kerberos Works</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.6.3. How Kerberos Works</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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 and PAM" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your brows
er or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Kerberos-Kerberos_Terminology.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Kerberos-Kerberos_and_PAM.html"><strong>Next</strong></a></li></ul><div class="section" title="2.6.3. How Kerberos Works" id="sect-Security_Guide-Kerberos-How_Kerberos_Works"><div class="titlepage"><div><div keep-together.within-column="always"><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 differs from username/password authentication methods. Instead of authenticating each user to each network service, Kerberos uses symmetric encryption and a trusted third party (a KDC), to authenticate users to a suite of network services. When a user authenticates to the KDC, the KDC sends a ticket specific to that session back to the user's machine, and any Kerberos-aware services look for the ticket on the user's machine rather than requiring the user to authenticate using a password.
</div><div class="para">
When a user on a Kerberos-aware network logs in to their workstation, their principal is sent to the KDC as part of a request for a TGT from the Authentication Server. This request can be sent by the log-in program so that it is transparent to the user, or can be sent by the <code class="command">kinit</code> program after the user logs in.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Kerberos-Kerberos_Terminology.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Kerberos-Kerberos_Terminology.html
index 91766f7..87c2546 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Kerberos-Kerberos_Terminology.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Kerberos-Kerberos_Terminology.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.6.2. Kerberos Terminology</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.
</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Kerberos.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Kerberos-How_Kerberos_Works.html"><strong>Next</strong></a></li></ul><div class="section" title="2.6.2. Kerberos Terminology" id="sect-Security_Guide-Kerberos-Kerberos_Terminology"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.6.2. Kerberos Terminology</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.6.2. Kerberos Terminology</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.<
/iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Kerberos.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Kerberos-How_Kerberos_Works.html"><strong>Next</strong></a></li></ul><div class="section" title="2.6.2. Kerberos Terminology" id="sect-Security_Guide-Kerberos-Kerberos_Terminology"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Kerberos-Kerberos_Terminology">2.6.2. Kerberos Terminology</h3></div></div></div><div class="para">
Kerberos has its own terminology to define various aspects of the service. Before learning how Kerberos works, it is important to learn the following terms.
</div><div class="variablelist"><dl><dt><span class="term">authentication server (AS)</span></dt><dd><div class="para">
A server that issues tickets for a desired service which are in turn given to users for access to the service. The AS responds to requests from clients who do not have or do not send credentials with a request. It is usually used to gain access to the ticket-granting server (TGS) service by issuing a ticket-granting ticket (TGT). The AS usually runs on the same host as the key distribution center (KDC).
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Kerberos-Kerberos_and_PAM.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Kerberos-Kerberos_and_PAM.html
index 8f38970..aedd855 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Kerberos-Kerberos_and_PAM.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Kerberos-Kerberos_and_PAM.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.6.4. Kerberos and PAM</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to v
iew it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Kerberos-How_Kerberos_Works.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Server.html"><strong>Next</strong></a></li></ul><div class="section" title="2.6.4. Kerberos and PAM" id="sect-Security_Guide-Kerberos-Kerberos_and_PAM"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.6.4. Kerberos and PAM</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.6.4. Kerberos and PAM</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to vi
ew it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Kerberos-How_Kerberos_Works.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Kerberos-Configuring_a_Kerberos_5_Server.html"><strong>Next</strong></a></li></ul><div class="section" title="2.6.4. Kerberos and PAM" id="sect-Security_Guide-Kerberos-Kerberos_and_PAM"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Kerberos-Kerberos_and_PAM">2.6.4. Kerberos and PAM</h3></div></div></div><div class="para">
Kerberos-aware services do not currently make use of Pluggable Authentication Modules (PAM) — these services bypass PAM completely. However, applications that use PAM can make use of Kerberos for authentication if the <code class="filename">pam_krb5</code> module (provided in the <code class="filename">pam_krb5</code> package) is installed. The <code class="filename">pam_krb5</code> package contains sample configuration files that allow services such as <code class="command">login</code> and <code class="command">gdm</code> to authenticate users as well as obtain initial credentials using their passwords. If access to network servers is always performed using Kerberos-aware services or services that use GSS-API, such as IMAP, the network can be considered reasonably safe.
</div><div class="important"><h2>Important</h2><div class="para">
Administrators should be careful not to allow users to authenticate to most network services using Kerberos passwords. Many protocols used by these services do not encrypt the password before sending it over the network, destroying the benefits of the Kerberos system. For example, users should not be allowed to authenticate to Telnet services with the same password they use for Kerberos authentication.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Kerberos-Setting_Up_Cross_Realm_Authentication.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Kerberos-Setting_Up_Cross_Realm_Authentication.html
index 7227c57..a12356f 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Kerberos-Setting_Up_Cross_Realm_Authentication.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Kerberos-Setting_Up_Cross_Realm_Authentication.html
@@ -1,13 +1,12 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.6.9. Setting Up Cross Realm Authentication</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is a
n iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Kerberos-Setting_Up_Secondary_KDCs.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Kerberos-Additional_Resources.html"><strong>Next</strong></a></li></ul><div class="section" title="2.6.9. Setting Up Cross Realm Authentication" id="sect-Security_Guide-Kerberos-Setting_Up_Cross_Realm_Authentication"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.6.9. Setting Up Cross Realm Authentication</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.6.9. Setting Up Cross Realm Authentication</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an
iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Kerberos-Setting_Up_Secondary_KDCs.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Kerberos-Additional_Resources.html"><strong>Next</strong></a></li></ul><div class="section" title="2.6.9. Setting Up Cross Realm Authentication" id="sect-Security_Guide-Kerberos-Setting_Up_Cross_Realm_Authentication"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Kerberos-Setting_Up_Cross_Realm_Authentication">2.6.9. Setting Up Cross Realm Authenti
cation</h3></div></div></div><div class="para">
<span class="emphasis"><em>Cross-realm authentication</em></span> is the term which is used to describe situations in which clients (typically users) of one realm use Kerberos to authenticate to services (typically server processes running on a particular server system) which belong to a realm other than their own.
</div><div class="para">
For the simplest case, in order for a client of a realm named <code class="literal">A.EXAMPLE.COM</code> to access a service in the <code class="literal">B.EXAMPLE.COM</code> realm, both realms must share a key for a principal named <code class="literal">krbtgt/B.EXAMPLE.COM at A.EXAMPLE.COM</code>, and both keys must have the same key version number associated with them.
</div><div class="para">
To accomplish this, select a very strong password or passphrase, and create an entry for the principal in both realms using 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"><code>kadmin -r B.EXAMPLE.COM</code></strong></code> <code class="computeroutput"><code class="prompt">kadmin:</code> <strong class="userinput"><code>add_principal krbtgt/B.EXA
MPLE.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">
+ </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"><code>kadmin -r B.EXAMPLE.COM</code></strong></code> <code class="computeroutput"><code class="prompt">kadmin:</code> <strong class="userinput"><code>add_principal krbtgt/B.EXA
MPLE.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></p></div><div class="para">
Use the <code class="command">get_principal</code> command to verify that both entries have matching key version numbers (<code class="literal">kvno</code> values) and encryption types.
</div><div class="important"><h2>Dumping the Database Doesn't Do It</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.
@@ -21,8 +20,7 @@
Now you face the more conventional problems: the client's system must be configured so that it can properly deduce the realm to which a particular service belongs, and it must be able to determine how to obtain credentials for services in that realm.
</div><div class="para">
First things first: the principal name for a service provided from a specific server system in a given realm typically looks like this:
- </div><div class="literallayout"><p>service/server.example.com at EXAMPLE.COM<br />
-</p></div><div class="para">
+ </div><div class="literallayout"><p>service/server.example.com at EXAMPLE.COM</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>).
@@ -77,7 +75,6 @@
D.EXAMPLE.COMÂ =Â C.EXAMPLE.COM<br />
}<br />
<br />
-<br />
</p></div><div class="para">
In this example, clients in the <code class="literal">A.EXAMPLE.COM</code> realm can obtain cross-realm credentials for <code class="literal">B.EXAMPLE.COM</code> directly from the <code class="literal">A.EXAMPLE.COM</code> KDC.
</div><div class="para">
@@ -90,5 +87,4 @@
Clients in the <code class="literal">A.EXAMPLE.COM</code> realm can obtain cross-realm credentials from <code class="literal">B.EXAMPLE.COM</code> realm directly. Without the "." indicating this, the client would instead attempt to use a hierarchical path, in this case:
</div><div class="literallayout"><p> A.EXAMPLE.COM → EXAMPLE.COM → B.EXAMPLE.COM<br />
<br />
-<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>Prev</strong>2.6.8. Setting Up Secondary KDCs</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Kerberos-Additional_Resources.html"><strong>Next</strong>2.6.10. Additional Resources</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Kerberos-Setting_Up_Secondary_KDCs.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Kerberos-Setting_Up_Secondary_KDCs.html
index 122162a..8a3c4bd 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Kerberos-Setting_Up_Secondary_KDCs.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Kerberos-Setting_Up_Secondary_KDCs.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.6.8. Setting Up Secondary KDCs</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Setting Up Cross Realm Authentication" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../to
c.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Kerberos-Domain_to_Realm_Mapping.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Kerberos-Setting_Up_Cross_Realm_Authentication.html"><strong>Next</strong></a></li></ul><div class="section" title="2.6.8. Setting Up Secondary KDCs" id="sect-Security_Guide-Kerberos-Setting_Up_Secondary_KDCs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.6.8. Setting Up Secondary KDCs</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.6.8. Setting Up Secondary KDCs</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Setting Up Cross Realm Authentication" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc
.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Kerberos-Domain_to_Realm_Mapping.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Kerberos-Setting_Up_Cross_Realm_Authentication.html"><strong>Next</strong></a></li></ul><div class="section" title="2.6.8. Setting Up Secondary KDCs" id="sect-Security_Guide-Kerberos-Setting_Up_Secondary_KDCs"><div class="titlepage"><div><div keep-together.within-column="always"><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">
For a number of reasons, you may choose to run multiple KDCs for a given realm. In this scenario, one KDC (the <span class="emphasis"><em>master KDC</em></span>) keeps a writable copy of the realm database and runs <code class="command">kadmind</code> (it is also your realm's <span class="emphasis"><em>admin server</em></span>), and one or more KDCs (<span class="emphasis"><em>slave KDCs</em></span>) keep read-only copies of the database and run <code class="command">kpropd</code>.
</div><div class="para">
The master-slave propagation procedure entails the master KDC dumping its database to a temporary dump file and then transmitting that file to each of its slaves, which then overwrite their previously-received read-only copies of the database with the contents of the dump file.
@@ -26,8 +26,7 @@ Entry for principal host/masterkdc.example.com with kvno 3, encryption type DES
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">
+<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>
@@ -49,18 +48,15 @@ Entry for principal host/slavekdc.example.com with kvno 3, encryption type DES w
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">
+<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 host/masterkdc.example.com at EXAMPLE.COM > /var/kerberos/krb5kdc/kpropd.acl</code></strong></code><br />
-</p></div><div class="para">
+ </div><div class="literallayout"><p> <code class="computeroutput"><code class="prompt">#</code> <strong class="userinput"><code>echo host/masterkdc.example.com at EXAMPLE.COM > /var/kerberos/krb5kdc/kpropd.acl</code></strong></code></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">
Ensure that the slave KDC's firewall allows the master KDC to contact it using TCP on port 754 (<span class="emphasis"><em>krb5_prop</em></span>), and start the <code class="command">kprop</code> service. Then, double-check that the <code class="command">kadmin</code> service is <span class="emphasis"><em>disabled</em></span>.
</div><div class="para">
Now perform a manual database propagation test by dumping the realm database, on the master KDC, to the default data file which the <code class="command">kprop</code> command will read (<code class="filename">/var/kerberos/krb5kdc/slave_datatrans</code>), and then use the <code class="command">kprop</code> command to transmit its contents to the slave KDC.
- </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">
+ </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></p></div><div class="para">
Using <code class="command">kinit</code>, verify that a client system whose <code class="filename">krb5.conf</code> lists only the slave KDC in its list of KDCs for your realm is now correctly able to obtain initial credentials from the slave KDC.
</div><div class="para">
That done, simply create a script which dumps the realm database and runs the <code class="command">kprop</code> command to transmit the database to each slave KDC in turn, and configure the <code class="command">cron</code> service to run the script periodically.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Kerberos.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Kerberos.html
index 8e64ef5..e79befe 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Kerberos.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Kerberos.html
@@ -1,22 +1,22 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.6. Kerberos</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="chap-Security_Guide-Securing_Your_Network.html" title="Chapter 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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe,
to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Additional_Resources-Related_Books.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Kerberos-Kerberos_Terminology.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" title="2.6. Kerberos" id="sect-Security_Guide-Kerberos" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.6. Kerberos</h2></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.6. Kerberos</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="chap-Security_Guide-Securing_Your_Network.html" title="Chapter 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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe,
to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Additional_Resources-Related_Books.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Kerberos-Kerberos_Terminology.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" title="2.6. Kerberos" id="sect-Security_Guide-Kerberos" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sect-Security_Guide-Kerberos">2.6. Kerberos</h2></div></div></div><div class="para">
System security and integrity within a network can be unwieldy. It can occupy the time of several administrators just to keep track of what services are being run on a network and the manner in which these services are used.
</div><div class="para">
Further, authenticating users to network services can prove dangerous when the method used by the protocol is inherently insecure, as evidenced by the transfer of unencrypted passwords over a network using the traditional FTP and Telnet protocols.
</div><div class="para">
Kerberos is a way to eliminate the need for protocols that allow unsafe methods of authentication, thereby enhancing overall network security.
- </div><div class="section" title="2.6.1. What is Kerberos?" id="sect-Security_Guide-Kerberos-What_is_Kerberos"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.6.1. What is Kerberos?</h3></div></div></div><div class="para">
- Kerberos is a network authentication protocol created by MIT, and uses symmetric-key cryptography<sup>[<a id="id3222359" href="#ftn.id3222359" class="footnote">14</a>]</sup> to authenticate users to network services, which means passwords are never actually sent over the network.
+ </div><div class="section" title="2.6.1. What is Kerberos?" id="sect-Security_Guide-Kerberos-What_is_Kerberos"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Kerberos-What_is_Kerberos">2.6.1. What is Kerberos?</h3></div></div></div><div class="para">
+ Kerberos is a network authentication protocol created by MIT, and uses symmetric-key cryptography<sup>[<a id="id2687557" href="#ftn.id2687557" class="footnote">14</a>]</sup> to authenticate users to network services, which means passwords are never actually sent over the network.
</div><div class="para">
Consequently, when users authenticate to network services using Kerberos, unauthorized users attempting to gather passwords by monitoring network traffic are effectively thwarted.
- </div><div class="section" title="2.6.1.1. Advantages of Kerberos" id="sect-Security_Guide-What_is_Kerberos-Advantages_of_Kerberos"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.6.1.1. Advantages of Kerberos</h4></div></div></div><div class="para">
+ </div><div class="section" title="2.6.1.1. Advantages of Kerberos" id="sect-Security_Guide-What_is_Kerberos-Advantages_of_Kerberos"><div class="titlepage"><div><div keep-together.within-column="always"><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">
Most conventional network services use password-based authentication schemes. Such schemes require a user to authenticate to a given network server by supplying their username and password. Unfortunately, the transmission of authentication information for many services is unencrypted. For such a scheme to be secure, the network has to be inaccessible to outsiders, and all computers and users on the network must be trusted and trustworthy.
</div><div class="para">
Even if this is the case, a network that is connected to the Internet can no longer be assumed to be secure. Any attacker who gains access to the network can use a simple packet analyzer, also known as a packet sniffer, to intercept usernames and passwords, compromising user accounts and the integrity of the entire security infrastructure.
</div><div class="para">
The primary design goal of Kerberos is to eliminate the transmission of unencrypted passwords across the network. If used properly, Kerberos effectively eliminates the threat that packet sniffers would otherwise pose on a network.
- </div></div><div class="section" title="2.6.1.2. Disadvantages of Kerberos" id="sect-Security_Guide-What_is_Kerberos-Disadvantages_of_Kerberos"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.6.1.2. Disadvantages of Kerberos</h4></div></div></div><div class="para">
+ </div></div><div class="section" title="2.6.1.2. Disadvantages of Kerberos" id="sect-Security_Guide-What_is_Kerberos-Disadvantages_of_Kerberos"><div class="titlepage"><div><div keep-together.within-column="always"><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">
Although Kerberos removes a common and severe security threat, it may be difficult to implement for a variety of reasons:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
Migrating user passwords from a standard UNIX password database, such as <code class="filename">/etc/passwd</code> or <code class="filename">/etc/shadow</code>, to a Kerberos password database can be tedious, as there is no automated mechanism to perform this task. Refer to Question 2.23 in the online Kerberos FAQ:
@@ -30,6 +30,6 @@
For an application to use Kerberos, its source must be modified to make the appropriate calls into the Kerberos libraries. Applications modified in this way are considered to be <em class="firstterm">Kerberos-aware</em>, or <em class="firstterm">kerberized</em>. For some applications, this can be quite problematic due to the size of the application or its design. For other incompatible applications, changes must be made to the way in which the server and client communicate. Again, this may require extensive programming. Closed-source applications that do not have Kerberos support by default are often the most problematic.
</div></li><li class="listitem"><div class="para">
Kerberos is an all-or-nothing solution. If Kerberos is used on the network, any unencrypted passwords transferred to a non-Kerberos aware service is at risk. Thus, the network gains no benefit from the use of Kerberos. To secure a network with Kerberos, one must either use Kerberos-aware versions of <span class="emphasis"><em>all</em></span> client/server applications that transmit passwords unencrypted, or not use <span class="emphasis"><em>any</em></span> such client/server applications at all.
- </div></li></ul></div></div></div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id3222359" href="#id3222359" class="para">14</a>] </sup>
+ </div></li></ul></div></div></div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id2687557" href="#id2687557" class="para">14</a>] </sup>
A system where both the client and the server share a common key that is used to encrypt and decrypt network communication.
</p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Additional_Resources-Related_Books.html"><strong>Prev</strong>2.5.5.3. Related Books</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Kerberos-Kerberos_Terminology.html"><strong>Next</strong>2.6.2. Kerberos Terminology</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-LUKS_Disk_Encryption-Links_of_Interest.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-LUKS_Disk_Encryption-Links_of_Interest.html
index 6fe3139..f809283 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-LUKS_Disk_Encryption-Links_of_Interest.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-LUKS_Disk_Encryption-Links_of_Interest.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.7.5. Links of Interest</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><i
frame id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-What_you_have_just_accomplished.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives.html"><strong>Next</strong></a></li></ul><div class="section" title="3.7.5. Links of Interest" id="sect-Security_Guide-LUKS_Disk_Encryption-Links_of_Interest"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.7.5. Links
of Interest</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.7.5. Links of Interest</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><if
rame id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-What_you_have_just_accomplished.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Encryption-7_Zip_Encrypted_Archives.html"><strong>Next</strong></a></li></ul><div class="section" title="3.7.5. Links of Interest" id="sect-Security_Guide-LUKS_Disk_Encryption-Links_of_Interest"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Securi
ty_Guide-LUKS_Disk_Encryption-Links_of_Interest">3.7.5. Links of Interest</h3></div></div></div><div class="para">
For additional information on LUKS or encrypting hard drives under Fedora please visit one of the following links:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<a href="http://clemens.endorphin.org/LUKS/">LUKS - Linux Unified Key Setup</a>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-Step_by_Step_Instructions.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-Step_by_Step_Instructions.html
index c138495..4c6f02c 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-Step_by_Step_Instructions.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-Step_by_Step_Instructions.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.7.3. Step-by-Step Instructions</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded
"><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories.html"><strong>Prev</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>Next</strong></a></li></ul><div class="section" title="3.7.3. Step-by-Step Instructions" id="sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-Step_by_Step_Instructions"><di
v class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.7.3. Step-by-Step Instructions</h3></div></div></div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.7.3. Step-by-Step Instructions</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded
"><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories.html"><strong>Prev</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>Next</strong></a></li></ul><div class="section" title="3.7.3. Step-by-Step Instructions" id="sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-Step_by_Step_Instructions"><div
class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><div class="para">
enter runlevel 1: <code class="code">telinit 1</code>
</div></li><li class="listitem"><div class="para">
unmount your existing /home: <code class="code"> umount /home</code>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-What_you_have_just_accomplished.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-What_you_have_just_accomplished.html
index f85bf5f..8151c99 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-What_you_have_just_accomplished.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-What_you_have_just_accomplished.html
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><i
frame id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-Step_by_Step_Instructions.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-LUKS_Disk_Encryption-Links_of_Interest.html"><strong>Next</strong></a></li></ul><div class="section" title="3.7.4. What you have just accomplished." id="sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-What_you_have_just_accomplished"><div class="titlepage"><div><div keep-togeth
er.within-column="always"><h3 class="title">3.7.4. What you have just accomplished.</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.7.4. What you have just accomplished.</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><if
rame id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-Step_by_Step_Instructions.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-LUKS_Disk_Encryption-Links_of_Interest.html"><strong>Next</strong></a></li></ul><div class="section" title="3.7.4. What you have just accomplished." id="sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories-What_you_have_just_accomplished"><div class="titlepage"><div><div keep-togethe
r.within-column="always"><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">
Congratulations, you now have an encrypted partition for all of your data to safely rest while the computer is off.
</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>Prev</strong>3.7.3. Step-by-Step Instructions</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-LUKS_Disk_Encryption-Links_of_Interest.html"><strong>Next</strong>3.7.5. Links of Interest</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories.html
index abae8f6..6f00662 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.7.2. Manually Encrypting Directories</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe
" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-LUKS_Disk_Encryption.html"><strong>Prev</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>Next</strong></a></li></ul><div class="section" title="3.7.2. Manually Encrypting Directories" id="sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.7.2. Manually Encrypti
ng Directories</h3></div></div></div><div class="warning"><h2>Warning</h2><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.7.2. Manually Encrypting Directories</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-LUKS_Disk_Encryption.html"><strong>Prev</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>Next</strong></a></li></ul><div class="section" title="3.7.2. Manually Encrypting Directories" id="sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-LU
KS_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">
If you are running a version of Fedora prior to Fedora 9 and want to encrypt a partition, or you want to encrypt a partition after the installation of the current version of Fedora, the following directions are for you. The below example demonstrates encrypting your /home partition but any partition can be used.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-LUKS_Disk_Encryption.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-LUKS_Disk_Encryption.html
index 09248e2..fe55df6 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-LUKS_Disk_Encryption.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-LUKS_Disk_Encryption.html
@@ -1,8 +1,8 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="chap-Security_Guide-Encryption.html" title="Chapter 3. Encryption" /><link rel="prev" href="Security_Guide-Encryption-Data_in_Motion-Secure_Shell.html" title="3.6. Secure Shell" /><link rel="next" href="sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories.html" title="3.7.2. Manually Encrypting Directories" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">
This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="Security_Guide-Encryption-Data_in_Motion-Secure_Shell.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" title="3.7. LUKS Disk Encryption" id="sect-Security_Guide-LUKS_Disk_Encryption" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">3.7. LUKS Disk Encryption</h2></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.7. LUKS Disk Encryption</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="chap-Security_Guide-Encryption.html" title="Chapter 3. Encryption" /><link rel="prev" href="Security_Guide-Encryption-Data_in_Motion-Secure_Shell.html" title="3.6. Secure Shell" /><link rel="next" href="sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories.html" title="3.7.2. Manually Encrypting Directories" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">T
his is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="Security_Guide-Encryption-Data_in_Motion-Secure_Shell.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-LUKS_Disk_Encryption-Manually_Encrypting_Directories.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" title="3.7. LUKS Disk Encryption" id="sect-Security_Guide-LUKS_Disk_Encryption" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sect-Security_Guide-LUKS_Disk_Encryption">3.7. LUKS Disk Encryption</h2></div></div></div>
<div class="para">
Linux Unified Key Setup-on-disk-format (or LUKS) allows you to encrypt partitions on your Linux computer. This is particularly important when it comes to mobile computers and removable media. LUKS allows multiple user keys to decrypt a master key which is used for the bulk encryption of the partition.
- </div><div class="section" title="3.7.1. LUKS Implementation in Fedora" id="sect-Security_Guide-LUKS_Disk_Encryption-LUKS_Implementation_in_Fedora"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.7.1. LUKS Implementation in Fedora</h3></div></div></div><div class="para">
+ </div><div class="section" title="3.7.1. LUKS Implementation in Fedora" id="sect-Security_Guide-LUKS_Disk_Encryption-LUKS_Implementation_in_Fedora"><div class="titlepage"><div><div keep-together.within-column="always"><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:
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Option_Fields-Access_Control.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Option_Fields-Access_Control.html
index 66c4014..92c236d 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Option_Fields-Access_Control.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Option_Fields-Access_Control.html
@@ -1,11 +1,10 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.5.2.2.2. Access Control</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../..
/../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-TCP_Wrappers_Configuration_Files-Option_Fields.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Option_Fields-Shell_Commands.html"><strong>Next</strong></a></li></ul><div class="section" title="2.5.2.2.2. Access Control" id="sect-Security_Guide-Option_Fields-Access_Control"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.5.2.2.2. Access Control</h5></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.5.2.2.2. Access Control</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../
../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-TCP_Wrappers_Configuration_Files-Option_Fields.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Option_Fields-Shell_Commands.html"><strong>Next</strong></a></li></ul><div class="section" title="2.5.2.2.2. Access Control" id="sect-Security_Guide-Option_Fields-Access_Control"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-Security_Guide-Option_Fields-Access_Control">2.5.2.2.2. Access Control</h5></div></div></div><div cla
ss="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">
+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>Prev</strong>2.5.2.2. Option Fields</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Option_Fields-Shell_Commands.html"><strong>Next</strong>2.5.2.2.3. Shell Commands</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Option_Fields-Expansions.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Option_Fields-Expansions.html
index c5a3c4c..6a8fd31 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Option_Fields-Expansions.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Option_Fields-Expansions.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.5.2.2.4. Expansions</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an i
frame, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Option_Fields-Shell_Commands.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd.html"><strong>Next</strong></a></li></ul><div class="section" title="2.5.2.2.4. Expansions" id="sect-Security_Guide-Option_Fields-Expansions"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.5.2.2.4. Expansions</h5></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.5.2.2.4. Expansions</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an if
rame, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Option_Fields-Shell_Commands.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd.html"><strong>Next</strong></a></li></ul><div class="section" title="2.5.2.2.4. Expansions" id="sect-Security_Guide-Option_Fields-Expansions"><div class="titlepage"><div><div keep-together.within-column="always"><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:
@@ -32,12 +32,10 @@
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">
+ : 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">
+: 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">Section 2.5.5, “Additional Resourcesâ€</a> for more information about TCP Wrappers.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Option_Fields-Shell_Commands.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Option_Fields-Shell_Commands.html
index 7455b43..eb3b8ca 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Option_Fields-Shell_Commands.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Option_Fields-Shell_Commands.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.5.2.2.3. Shell Commands</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Access Control" /><link rel="next" href="sect-Security_Guide-Option_Fields-Expansions.html" title="2.5.2.2.4. Expansions" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This i
s an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Option_Fields-Access_Control.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Option_Fields-Expansions.html"><strong>Next</strong></a></li></ul><div class="section" title="2.5.2.2.3. Shell Commands" id="sect-Security_Guide-Option_Fields-Shell_Commands"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.5.2.2.3. Shell Commands</h5></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.5.2.2.3. Shell Commands</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Access Control" /><link rel="next" href="sect-Security_Guide-Option_Fields-Expansions.html" title="2.5.2.2.4. Expansions" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is
an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Option_Fields-Access_Control.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Option_Fields-Expansions.html"><strong>Next</strong></a></li></ul><div class="section" title="2.5.2.2.3. Shell Commands" id="sect-Security_Guide-Option_Fields-Shell_Commands"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><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.
@@ -8,13 +8,11 @@
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 class="listitem"><div class="para">
+ : allow</pre></li><li class="listitem"><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">
+ : 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>Prev</strong>2.5.2.2.2. Access Control</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Option_Fields-Expansions.html"><strong>Next</strong>2.5.2.2.4. Expansions</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-PAM_Configuration_File_Format-Control_Flag.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-PAM_Configuration_File_Format-Control_Flag.html
index d90d3fc..cead3b5 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-PAM_Configuration_File_Format-Control_Flag.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-PAM_Configuration_File_Format-Control_Flag.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.4.3.2. Control Flag</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><
div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_File_Format.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-PAM_Configuration_File_Format-Module_Name.html"><strong>Next</strong></a></li></ul><div class="section" title="2.4.3.2. Control Flag" id="sect-Security_Guide-PAM_Configuration_File_Format-Control_Flag"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="ti
tle">2.4.3.2. Control Flag</h4></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.4.3.2. Control Flag</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><d
iv id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_File_Format.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-PAM_Configuration_File_Format-Module_Name.html"><strong>Next</strong></a></li></ul><div class="section" title="2.4.3.2. Control Flag" id="sect-Security_Guide-PAM_Configuration_File_Format-Control_Flag"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="tit
le" id="sect-Security_Guide-PAM_Configuration_File_Format-Control_Flag">2.4.3.2. Control Flag</h4></div></div></div><div class="para">
All PAM modules generate a success or failure result when called. Control flags tell PAM what do with the result. Modules can be stacked in a particular order, and the control flags determine how important the success or failure of a particular module is to the overall goal of authenticating the user to the service.
</div><div class="para">
There are four predefined control flags:
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-PAM_Configuration_File_Format-Module_Arguments.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-PAM_Configuration_File_Format-Module_Arguments.html
index edc467a..ce02595 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-PAM_Configuration_File_Format-Module_Arguments.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-PAM_Configuration_File_Format-Module_Arguments.html
@@ -1,12 +1,11 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.4.3.4. Module Arguments</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embed
ed "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-PAM_Configuration_File_Format-Module_Name.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Sample_PAM_Configuration_Files.html"><strong>Next</strong></a></li></ul><div class="section" title="2.4.3.4. Module Arguments" id="sect-Security_Guide-PAM_Configuration_File_Format-Module_Arguments"><div class="titlepage"><div><div keep-together.within-column="always
"><h4 class="title">2.4.3.4. Module Arguments</h4></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.4.3.4. Module Arguments</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embede
d "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-PAM_Configuration_File_Format-Module_Name.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Sample_PAM_Configuration_Files.html"><strong>Next</strong></a></li></ul><div class="section" title="2.4.3.4. Module Arguments" id="sect-Security_Guide-PAM_Configuration_File_Format-Module_Arguments"><div class="titlepage"><div><div keep-together.within-column="always"
><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 uses <em class="firstterm">arguments</em> to pass information to a pluggable module during authentication for some modules.
</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">
The following is a typical <code class="filename">pam_userdb.so</code> line in a PAM configuration. The <em class="replaceable"><code><path-to-file></code></em> is the full path to the Berkeley DB database file:
- </div><pre class="screen">auth required pam_userdb.so db=<em class="replaceable"><code><path-to-file></code></em>
-</pre><div class="para">
+ </div><pre class="screen">auth required pam_userdb.so db=<em class="replaceable"><code><path-to-file></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>Prev</strong>2.4.3.3. Module Name</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Sample_PAM_Configuration_Files.html"><strong>Next</strong>2.4.4. Sample PAM Configuration Files</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-PAM_Configuration_File_Format-Module_Name.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-PAM_Configuration_File_Format-Module_Name.html
index 2311c87..008771c 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-PAM_Configuration_File_Format-Module_Name.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-PAM_Configuration_File_Format-Module_Name.html
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><i
frame id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-PAM_Configuration_File_Format-Control_Flag.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-PAM_Configuration_File_Format-Module_Arguments.html"><strong>Next</strong></a></li></ul><div class="section" title="2.4.3.3. Module Name" id="sect-Security_Guide-PAM_Configuration_File_Format-Module_Name"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.4.3.3. Module Name</h4></div></div></div><d
iv class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.4.3.3. Module Name</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><if
rame id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-PAM_Configuration_File_Format-Control_Flag.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-PAM_Configuration_File_Format-Module_Arguments.html"><strong>Next</strong></a></li></ul><div class="section" title="2.4.3.3. Module Name" id="sect-Security_Guide-PAM_Configuration_File_Format-Module_Name"><div class="titlepage"><div><div keep-together.within-column="always"><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>Prev</strong>2.4.3.2. Control Flag</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-PAM_Configuration_File_Format-Module_Arguments.html"><strong>Next</strong>2.4.3.4. Module Arguments</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-PAM_and_Administrative_Credential_Caching-Common_pam_timestamp_Directives.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-PAM_and_Administrative_Credential_Caching-Common_pam_timestamp_Directives.html
index 7cc20b4..b120c41 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-PAM_and_Administrative_Credential_Caching-Common_pam_timestamp_Directives.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-PAM_and_Administrative_Credential_Caching-Common_pam_timestamp_Directives.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.4.6.2. Common pam_timestamp Directives</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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_Dev
ice_Ownership.html" title="2.4.7. PAM and Device Ownership" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Administrative_Credential_Caching.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Device_Ownership.html"><strong>Next</strong></a></li></ul><div class="section" title="2.4.6.2. Common pam_timestamp Directives" id
="sect-Security_Guide-PAM_and_Administrative_Credential_Caching-Common_pam_timestamp_Directives"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.4.6.2. Common pam_timestamp Directives</h4></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.4.6.2. Common pam_timestamp Directives</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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_Devi
ce_Ownership.html" title="2.4.7. PAM and Device Ownership" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Administrative_Credential_Caching.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Device_Ownership.html"><strong>Next</strong></a></li></ul><div class="section" title="2.4.6.2. Common pam_timestamp Directives" id=
"sect-Security_Guide-PAM_and_Administrative_Credential_Caching-Common_pam_timestamp_Directives"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><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).
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-PAM_and_Device_Ownership-Application_Access.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-PAM_and_Device_Ownership-Application_Access.html
index bb600bb..5c0ceaf 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-PAM_and_Device_Ownership-Application_Access.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-PAM_and_Device_Ownership-Application_Access.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.4.7.2. Application Access</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_em
beded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Device_Ownership.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Additional_Resources.html"><strong>Next</strong></a></li></ul><div class="section" title="2.4.7.2. Application Access" id="sect-Security_Guide-PAM_and_Device_Ownership-Application_Access"><div class="titlepage"><div><div keep-together.within-co
lumn="always"><h4 class="title">2.4.7.2. Application Access</h4></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.4.7.2. Application Access</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_emb
eded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Device_Ownership.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Additional_Resources.html"><strong>Next</strong></a></li></ul><div class="section" title="2.4.7.2. Application Access" id="sect-Security_Guide-PAM_and_Device_Ownership-Application_Access"><div class="titlepage"><div><div keep-together.within-col
umn="always"><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>.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Additional_Resources.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Additional_Resources.html
index e598311..4e4367a 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Additional_Resources.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Additional_Resources.html
@@ -1,8 +1,8 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="to
cframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-PAM_and_Device_Ownership-Application_Access.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Additional_Resources-Useful_PAM_Websites.html"><strong>Next</strong></a></li></ul><div class="section" title="2.4.8. Additional Resources" id="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Additional_Resources"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.4.8. Additional Resources</h3></div><
/div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.4.8. Additional Resources</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="toc
frame" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-PAM_and_Device_Ownership-Application_Access.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Additional_Resources-Useful_PAM_Websites.html"><strong>Next</strong></a></li></ul><div class="section" title="2.4.8. Additional Resources" id="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Additional_Resources"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Pluggable_Authent
ication_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" title="2.4.8.1. Installed PAM Documentation" id="sect-Security_Guide-Additional_Resources-Installed_PAM_Documentation"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.4.8.1. Installed PAM Documentation</h4></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ </div><div class="section" title="2.4.8.1. Installed PAM Documentation" id="sect-Security_Guide-Additional_Resources-Installed_PAM_Documentation"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><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 class="listitem"><div class="para">
<code class="command">pam</code> — Good introductory information on PAM, including the structure and purpose of the PAM configuration files.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Creating_PAM_Modules.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Creating_PAM_Modules.html
index 71f4373..514ff8b 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Creating_PAM_Modules.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Creating_PAM_Modules.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.4.5. Creating PAM Modules</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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 Credent
ial Caching" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Sample_PAM_Configuration_Files.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Administrative_Credential_Caching.html"><strong>Next</strong></a></li></ul><div class="section" title="2.4.5. Creating PAM Modules" id="sect-Security_Guide-Pluggable_Authentication_Modules_
PAM-Creating_PAM_Modules"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.4.5. Creating PAM Modules</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.4.5. Creating PAM Modules</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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 Credenti
al Caching" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Sample_PAM_Configuration_Files.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Administrative_Credential_Caching.html"><strong>Next</strong></a></li></ul><div class="section" title="2.4.5. Creating PAM Modules" id="sect-Security_Guide-Pluggable_Authentication_Modules_P
AM-Creating_PAM_Modules"><div class="titlepage"><div><div keep-together.within-column="always"><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.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_File_Format.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_File_Format.html
index 16a9c89..b417bd5 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_File_Format.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_File_Format.html
@@ -1,11 +1,10 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.4.3. PAM Configuration File Format</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" cl
ass="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_Files.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-PAM_Configuration_File_Format-Control_Flag.html"><strong>Next</strong></a></li></ul><div class="section" title="2.4.3. PAM Configuration File Format" id="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_File_Format"><div class="titlepage"><div><div keep-together.within-column="alway
s"><h3 class="title">2.4.3. PAM Configuration File Format</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.4.3. PAM Configuration File Format</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" cla
ss="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_Files.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-PAM_Configuration_File_Format-Control_Flag.html"><strong>Next</strong></a></li></ul><div class="section" title="2.4.3. PAM Configuration File Format" id="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_File_Format"><div class="titlepage"><div><div keep-together.within-column="always
"><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">
Each PAM configuration file contains a group of directives formatted as follows:
- </div><pre class="screen"><em class="replaceable"><code><module interface></code></em> <em class="replaceable"><code><control flag></code></em> <em class="replaceable"><code><module name></code></em> <em class="replaceable"><code><module arguments></code></em>
-</pre><div class="para">
+ </div><pre class="screen"><em class="replaceable"><code><module interface></code></em> <em class="replaceable"><code><control flag></code></em> <em class="replaceable"><code><module name></code></em> <em class="replaceable"><code><module arguments></code></em></pre><div class="para">
Each of these elements is explained in the following sections.
- </div><div class="section" title="2.4.3.1. Module Interface" id="sect-Security_Guide-PAM_Configuration_File_Format-Module_Interface"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.4.3.1. Module Interface</h4></div></div></div><div class="para">
+ </div><div class="section" title="2.4.3.1. Module Interface" id="sect-Security_Guide-PAM_Configuration_File_Format-Module_Interface"><div class="titlepage"><div><div keep-together.within-column="always"><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">
Four types of PAM module interface are currently available. Each of these corresponds to a different aspect of the authorization process:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="command">auth</code> — This module interface authenticates use. For example, it requests and verifies the validity of a password. Modules with this interface can also set credentials, such as group memberships or Kerberos tickets.
@@ -19,10 +18,9 @@
An individual module can provide any or all module interfaces. For instance, <code class="filename">pam_unix.so</code> provides all four module interfaces.
</div></div><div class="para">
In a PAM configuration file, the module interface is the first field defined. For example, a typical line in a configuration may look like this:
- </div><pre class="screen">auth required pam_unix.so
-</pre><div class="para">
+ </div><pre class="screen">auth required pam_unix.so</pre><div class="para">
This instructs PAM to use the <code class="filename">pam_unix.so</code> module's <code class="command">auth</code> interface.
- </div><div class="section" title="2.4.3.1.1. Stacking Module Interfaces" id="sect-Security_Guide-Module_Interface-Stacking_Module_Interfaces"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.4.3.1.1. Stacking Module Interfaces</h5></div></div></div><div class="para">
+ </div><div class="section" title="2.4.3.1.1. Stacking Module Interfaces" id="sect-Security_Guide-Module_Interface-Stacking_Module_Interfaces"><div class="titlepage"><div><div keep-together.within-column="always"><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">Section 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">
Stacking makes it easy for an administrator to require specific conditions to exist before allowing the user to authenticate. For example, the <code class="command">reboot</code> command normally uses several stacked modules, as seen in its PAM configuration file:
@@ -31,8 +29,7 @@
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 class="listitem"><div class="para">
+account required pam_permit.so</pre><div class="itemizedlist"><ul><li class="listitem"><div class="para">
The first line is a comment and is not processed.
</div></li><li class="listitem"><div class="para">
<code class="command">auth sufficient pam_rootok.so</code> — This line uses the <code class="filename">pam_rootok.so</code> module to check whether the current user is root, by verifying that their UID is 0. If this test succeeds, no other modules are consulted and the command is executed. If this test fails, the next module is consulted.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_Files.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_Files.html
index d7929a9..daff287 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_Files.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_Files.html
@@ -1,8 +1,8 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded
"><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_File_Format.html"><strong>Next</strong></a></li></ul><div class="section" title="2.4.2. PAM Configuration Files" id="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_Files"><div class="titlepage"><div><div keep-together.within-col
umn="always"><h3 class="title">2.4.2. PAM Configuration Files</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.4.2. PAM Configuration Files</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded
"><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_File_Format.html"><strong>Next</strong></a></li></ul><div class="section" title="2.4.2. PAM Configuration Files" id="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_Files"><div class="titlepage"><div><div keep-together.within-colu
mn="always"><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">
The <code class="filename">/etc/pam.d/</code> directory contains the PAM configuration files for each PAM-aware application. In earlier versions of PAM, the <code class="filename">/etc/pam.conf</code> file was used, but this file is now deprecated and is only used if the <code class="filename">/etc/pam.d/</code> directory does not exist.
- </div><div class="section" title="2.4.2.1. PAM Service Files" id="sect-Security_Guide-PAM_Configuration_Files-PAM_Service_Files"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.4.2.1. PAM Service Files</h4></div></div></div><div class="para">
+ </div><div class="section" title="2.4.2.1. PAM Service Files" id="sect-Security_Guide-PAM_Configuration_Files-PAM_Service_Files"><div class="titlepage"><div><div keep-together.within-column="always"><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">
Each PAM-aware application or <em class="firstterm">service</em> has a file in the <code class="filename">/etc/pam.d/</code> directory. Each file in this directory has the same name as the service to which it controls access.
</div><div class="para">
The PAM-aware program is responsible for defining its service name and installing its own PAM configuration file in the <code class="filename">/etc/pam.d/</code> directory. For example, the <code class="command">login</code> program defines its service name as <code class="command">login</code> and installs the <code class="filename">/etc/pam.d/login</code> PAM configuration file.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Administrative_Credential_Caching.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Administrative_Credential_Caching.html
index 8269775..00f2a13 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Administrative_Credential_Caching.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Administrative_Credential_Caching.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.4.6. PAM and Administrative Credential Caching</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Creating_PAM_Modules.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-PAM_and_Administrative_Credential_Caching-Common_pam_timestamp_Directives.html"><strong>Next</strong></a></li></ul><div class="section" title="2.4.6. PAM and Administrative Credential Caching" id="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PA
M_and_Administrative_Credential_Caching"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.4.6. PAM and Administrative Credential Caching</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.4.6. PAM and Administrative Credential Caching</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Creating_PAM_Modules.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-PAM_and_Administrative_Credential_Caching-Common_pam_timestamp_Directives.html"><strong>Next</strong></a></li></ul><div class="section" title="2.4.6. PAM and Administrative Credential Caching" id="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM
_and_Administrative_Credential_Caching"><div class="titlepage"><div><div keep-together.within-column="always"><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.
@@ -8,11 +8,11 @@
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"><div class="figure-contents"><div class="mediaobject"><img src="images/authicon.png" alt="The Authentication Icon" /><div class="longdesc"><div class="para">
+ </div><div class="figure" title="Figure 2.7. The Authentication Icon" 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>Figure 2.7. The Authentication Icon</h6></div><br class="figure-break" /><div class="section" title="2.4.6.1. Removing the Timestamp File" id="sect-Security_Guide-PAM_and_Administrative_Credential_Caching-Removing_the_Timestamp_File"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.4.6.1. Removing the Timestamp File</h4></div></div></div><div class="para">
+ </div></div></div></div><h6>Figure 2.7. The Authentication Icon</h6></div><br class="figure-break" /><div class="section" title="2.4.6.1. Removing the Timestamp File" id="sect-Security_Guide-PAM_and_Administrative_Credential_Caching-Removing_the_Timestamp_File"><div class="titlepage"><div><div keep-together.within-column="always"><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"><div class="figure-contents"><div class="mediaobject"><img src="images/auth-panel.png" width="444" alt="Dismiss Authentication Dialog" /><div class="longdesc"><div class="para">
+ </div><div class="figure" title="Figure 2.8. Dismiss Authentication Dialog" id="figu-Security_Guide-Removing_the_Timestamp_File-Dismiss_Authentication_Dialog"><div class="figure-contents"><div class="mediaobject"><img src="images/auth-panel.png" width="444" alt="Dismiss Authentication Dialog" /><div class="longdesc"><div class="para">
Illustration of the authentication dismissal dialog box.
</div></div></div></div><h6>Figure 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:
@@ -24,8 +24,7 @@
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 class="listitem"><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">
+ </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>.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Device_Ownership.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Device_Ownership.html
index 7ecab3d..3b7d80a 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Device_Ownership.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Device_Ownership.html
@@ -1,8 +1,8 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embe
ded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-PAM_and_Administrative_Credential_Caching-Common_pam_timestamp_Directives.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-PAM_and_Device_Ownership-Application_Access.html"><strong>Next</strong></a></li></ul><div class="section" title="2.4.7. PAM and Device Ownership" id="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Device_Ownership"><div class="titlepage"><div><div keep-
together.within-column="always"><h3 class="title">2.4.7. PAM and Device Ownership</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.4.7. PAM and Device Ownership</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embed
ed "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-PAM_and_Administrative_Credential_Caching-Common_pam_timestamp_Directives.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-PAM_and_Device_Ownership-Application_Access.html"><strong>Next</strong></a></li></ul><div class="section" title="2.4.7. PAM and Device Ownership" id="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_and_Device_Ownership"><div class="titlepage"><div><div keep-t
ogether.within-column="always"><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" title="2.4.7.1. Device Ownership" id="sect-Security_Guide-PAM_and_Device_Ownership-Device_Ownership"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.4.7.1. Device Ownership</h4></div></div></div><div class="para">
+ </div><div class="section" title="2.4.7.1. Device Ownership" id="sect-Security_Guide-PAM_and_Device_Ownership-Device_Ownership"><div class="titlepage"><div><div keep-together.within-column="always"><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.
@@ -21,10 +21,8 @@
</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">
+<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>Prev</strong>2.4.6.2. Common pam_timestamp Directives</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-PAM_and_Device_Ownership-Application_Access.html"><strong>Next</strong>2.4.7.2. Application Access</a></li></ul></body></html>
+ </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>Prev</strong>2.4.6.2. Common pam_timestamp Directives</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-PAM_and_Device_Ownership-Application_Access.html"><strong>Next</strong>2.4.7.2. Application Access</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Sample_PAM_Configuration_Files.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Sample_PAM_Configuration_Files.html
index 46b4a3e..27c338e 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Sample_PAM_Configuration_Files.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Sample_PAM_Configuration_Files.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.4.4. Sample PAM Configuration Files</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-PAM_Configuration_File_Format-Module_Arguments.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Creating_PAM_Modules.html"><strong>Next</strong></a></li></ul><div class="section" title="2.4.4. Sample PAM Configuration Files" id="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Sample_PAM_Configuration_Files"><div class="titlepage"><div><div keep-together.within-column=
"always"><h3 class="title">2.4.4. Sample PAM Configuration Files</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.4.4. Sample PAM Configuration Files</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv"
class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-PAM_Configuration_File_Format-Module_Arguments.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Creating_PAM_Modules.html"><strong>Next</strong></a></li></ul><div class="section" title="2.4.4. Sample PAM Configuration Files" id="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Sample_PAM_Configuration_Files"><div class="titlepage"><div><div keep-together.within-column="
always"><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">
The following is a sample PAM application configuration file:
</div><pre class="screen">#%PAM-1.0
auth required pam_securetty.so
@@ -9,8 +9,7 @@ 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 class="listitem"><div class="para">
+session required pam_unix.so</pre><div class="itemizedlist"><ul><li class="listitem"><div class="para">
The first line is a comment, indicated by the hash mark (<code class="command">#</code>) at the beginning of the line.
</div></li><li class="listitem"><div class="para">
Lines two through four stack three modules for login authentication.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Pluggable_Authentication_Modules_PAM.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Pluggable_Authentication_Modules_PAM.html
index 10ad465..fbee880 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Pluggable_Authentication_Modules_PAM.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Pluggable_Authentication_Modules_PAM.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.4. Pluggable Authentication Modules (PAM)</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="chap-Security_Guide-Securing_Your_Network.html" title="Chapter 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="to
c_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Single_Sign_on_SSO-Configuring_Firefox_to_use_Kerberos_for_SSO.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_Files.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" title="2.4. Pluggable Authentication Modules (PAM)" id="sect-Security_Guide-Pluggable_Authentication_Modules_PAM" lang="en-US"><div clas
s="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.4. Pluggable Authentication Modules (PAM)</h2></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.4. Pluggable Authentication Modules (PAM)</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="chap-Security_Guide-Securing_Your_Network.html" title="Chapter 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="toc
_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Single_Sign_on_SSO-Configuring_Firefox_to_use_Kerberos_for_SSO.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-PAM_Configuration_Files.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" title="2.4. Pluggable Authentication Modules (PAM)" id="sect-Security_Guide-Pluggable_Authentication_Modules_PAM" lang="en-US"><div class
="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sect-Security_Guide-Pluggable_Authentication_Modules_PAM">2.4. Pluggable Authentication Modules (PAM)</h2></div></div></div><div class="para">
Programs that grant users access to a system use <em class="firstterm">authentication</em> to verify each other's identity (that is, to establish that a user is who they say they are).
</div><div class="para">
Historically, each program had its own way of authenticating users. In Fedora, many programs are configured to use a centralized authentication mechanism called <em class="firstterm">Pluggable Authentication Modules</em> (<acronym class="acronym">PAM</acronym>).
@@ -8,7 +8,7 @@
PAM uses a pluggable, modular architecture, which affords the system administrator a great deal of flexibility in setting authentication policies for the system.
</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">Section 2.4.3, “PAM Configuration File Formatâ€</a> for more information.
- </div><div class="section" title="2.4.1. Advantages of PAM" id="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Advantages_of_PAM"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.4.1. Advantages of PAM</h3></div></div></div><div class="para">
+ </div><div class="section" title="2.4.1. Advantages of PAM" id="sect-Security_Guide-Pluggable_Authentication_Modules_PAM-Advantages_of_PAM"><div class="titlepage"><div><div keep-together.within-column="always"><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 offers the following advantages:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
a common authentication scheme that can be used with a wide variety of applications.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Secure_Installation-Utilize_LUKS_Partition_Encryption.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Secure_Installation-Utilize_LUKS_Partition_Encryption.html
index b6e6734..8aadb0d 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Secure_Installation-Utilize_LUKS_Partition_Encryption.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Secure_Installation-Utilize_LUKS_Partition_Encryption.html
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="chap-Security_Guide-Secure_Installation.html" title="Chapter 5. Secure Installation" /><link rel="prev" href="chap-Security_Guide-Secure_Installation.html" title="Chapter 5. Secure Installation" /><link rel="next" href="chap-Security_Guide-Software_Maintenance.html" title="Chapter 6. Software Maintenance" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is
an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security_Guide-Secure_Installation.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Security_Guide-Software_Maintenance.html"><strong>Next</strong></a></li></ul><div class="section" title="5.2. Utilize LUKS Partition Encryption" id="sect-Security_Guide-Secure_Installation-Utilize_LUKS_Partition_Encryption"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.2. Utilize LUKS Partition Encryption</h2></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.2. Utilize LUKS Partition Encryption</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="chap-Security_Guide-Secure_Installation.html" title="Chapter 5. Secure Installation" /><link rel="prev" href="chap-Security_Guide-Secure_Installation.html" title="Chapter 5. Secure Installation" /><link rel="next" href="chap-Security_Guide-Software_Maintenance.html" title="Chapter 6. Software Maintenance" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is
an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security_Guide-Secure_Installation.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Security_Guide-Software_Maintenance.html"><strong>Next</strong></a></li></ul><div class="section" title="5.2. Utilize LUKS Partition Encryption" id="sect-Security_Guide-Secure_Installation-Utilize_LUKS_Partition_Encryption"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sect-Security_Guide-Secure_Installation-Utilize_LUKS_Partition_Encryption">5.2. Utilize LUKS Partition Encryption</h2></div></d
iv></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><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security_Guide-Secure_Installation.html"><strong>Prev</strong>Chapter 5. Secure Installation</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="chap-Security_Guide-Software_Maintenance.html"><strong>Next</strong>Chapter 6. Software Maintenance</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_FTP-Anonymous_Access.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_FTP-Anonymous_Access.html
index 8d15c09..87be46d 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_FTP-Anonymous_Access.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_FTP-Anonymous_Access.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.6.2. Anonymous Access</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. User Accounts" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it
upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Server_Security-Securing_FTP.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_FTP-User_Accounts.html"><strong>Next</strong></a></li></ul><div class="section" title="2.2.6.2. Anonymous Access" id="sect-Security_Guide-Securing_FTP-Anonymous_Access"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.6.2. Anonymous Access</h4></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.6.2. Anonymous Access</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. User Accounts" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it u
pgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Server_Security-Securing_FTP.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_FTP-User_Accounts.html"><strong>Next</strong></a></li></ul><div class="section" title="2.2.6.2. Anonymous Access" id="sect-Security_Guide-Securing_FTP-Anonymous_Access"><div class="titlepage"><div><div keep-together.within-column="always"><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.
@@ -8,20 +8,16 @@
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" title="2.2.6.2.1. Anonymous Upload" id="sect-Security_Guide-Anonymous_Access-Anonymous_Upload"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.2.6.2.1. Anonymous Upload</h5></div></div></div><div class="para">
+ </div></div><div class="section" title="2.2.6.2.1. Anonymous Upload" id="sect-Security_Guide-Anonymous_Access-Anonymous_Upload"><div class="titlepage"><div><div keep-together.within-column="always"><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/upload
-</pre><div class="para">
+ </div><pre class="screen">mkdir /var/ftp/pub/upload</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/upload
-</pre><div class="para">
+ </div><pre class="screen">chmod 730 /var/ftp/pub/upload</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 upload
-</pre><div class="warning"><h2>Warning</h2><div class="para">
+ </div><pre class="screen">drwx-wx--- 2 root ftp 4096 Feb 13 20:05 upload</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>Prev</strong>2.2.6. Securing FTP</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_FTP-User_Accounts.html"><strong>Next</strong>2.2.6.3. User Accounts</a></li></ul></body></html>
+ </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>Prev</strong>2.2.6. Securing FTP</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_FTP-User_Accounts.html"><strong>Next</strong>2.2.6.3. User Accounts</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_FTP-Use_TCP_Wrappers_To_Control_Access.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_FTP-Use_TCP_Wrappers_To_Control_Access.html
index f1facd7..6bc4c3c 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_FTP-Use_TCP_Wrappers_To_Control_Access.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_FTP-Use_TCP_Wrappers_To_Control_Access.html
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. User Accounts" /><link rel="next" href="sect-Security_Guide-Server_Security-Securing_Sendmail.html" title="2.2.7. Securing Sendmail" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">Th
is is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_FTP-User_Accounts.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Server_Security-Securing_Sendmail.html"><strong>Next</strong></a></li></ul><div class="section" title="2.2.6.4. Use TCP Wrappers To Control Access" id="sect-Security_Guide-Securing_FTP-Use_TCP_Wrappers_To_Control_Access"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.6.4. Use TCP Wrappers To Control Access</h4></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.6.4. Use TCP Wrappers To Control Access</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. User Accounts" /><link rel="next" href="sect-Security_Guide-Server_Security-Securing_Sendmail.html" title="2.2.7. Securing Sendmail" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">Thi
s is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_FTP-User_Accounts.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Server_Security-Securing_Sendmail.html"><strong>Next</strong></a></li></ul><div class="section" title="2.2.6.4. Use TCP Wrappers To Control Access" id="sect-Security_Guide-Securing_FTP-Use_TCP_Wrappers_To_Control_Access"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Securing_FTP-Use_TCP_Wrappers_To_Control_Access">2.2.6.4. Use TCP Wrappers To Contr
ol 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">Section 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>Prev</strong>2.2.6.3. User Accounts</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Server_Security-Securing_Sendmail.html"><strong>Next</strong>2.2.7. Securing Sendmail</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_FTP-User_Accounts.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_FTP-User_Accounts.html
index 6a8e54a..631585d 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_FTP-User_Accounts.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_FTP-User_Accounts.html
@@ -1,11 +1,10 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.6.3. User Accounts</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../
../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_FTP-Anonymous_Access.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_FTP-Use_TCP_Wrappers_To_Control_Access.html"><strong>Next</strong></a></li></ul><div class="section" title="2.2.6.3. User Accounts" id="sect-Security_Guide-Securing_FTP-User_Accounts"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.6.3. User Accounts</h4></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.6.3. User Accounts</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../.
./../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_FTP-Anonymous_Access.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_FTP-Use_TCP_Wrappers_To_Control_Access.html"><strong>Next</strong></a></li></ul><div class="section" title="2.2.6.3. User Accounts" id="sect-Security_Guide-Securing_FTP-User_Accounts"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Securing_FTP-User_Accounts">2.2.6.3. User Accounts</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" title="2.2.6.3.1. Restricting User Accounts" id="sect-Security_Guide-User_Accounts-Restricting_User_Accounts"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.2.6.3.1. Restricting User Accounts</h5></div></div></div><div class="para">
+ </div><pre class="screen">local_enable=NO</pre><div class="section" title="2.2.6.3.1. Restricting User Accounts" id="sect-Security_Guide-User_Accounts-Restricting_User_Accounts"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-Security_Guide-User_Accounts-Restricting_User_Accounts">2.2.6.3.1. Restricting User Accounts</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. Disabling Root Using PAM">Section 2.1.4.2.4, “Disabling Root Using 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.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_NFS-Beware_of_Syntax_Errors.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_NFS-Beware_of_Syntax_Errors.html
index 7643731..c2cb76f 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_NFS-Beware_of_Syntax_Errors.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_NFS-Beware_of_Syntax_Errors.html
@@ -1,14 +1,11 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.4.2. Beware of Syntax Errors</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src=
"../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Server_Security-Securing_NFS.html"><strong>Prev</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>Next</strong></a></li></ul><div class="section" title="2.2.4.2. Beware of Syntax Errors" id="sect-Security_Guide-Securing_NFS-Beware_of_Syntax_Errors"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.4.2. Beware of Syntax Errors</h4></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.4.2. Beware of Syntax Errors</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="
../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Server_Security-Securing_NFS.html"><strong>Prev</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>Next</strong></a></li></ul><div class="section" title="2.2.4.2. Beware of Syntax Errors" id="sect-Security_Guide-Securing_NFS-Beware_of_Syntax_Errors"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Securing_NFS-Beware_of_Syntax_Errors">2.2.4.2. Beware of Synta
x 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">
+ </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">
+ </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>Prev</strong>2.2.4. Securing NFS</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</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>Next</strong>2.2.4.3. Do Not Use the no_root_squash Option</a></li></ul></body></html>
+ </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>Prev</strong>2.2.4. Securing NFS</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</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>Next</strong>2.2.4.3. Do Not Use the no_root_squash Option</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_NFS-Do_Not_Use_the_no_root_squash_Option.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_NFS-Do_Not_Use_the_no_root_squash_Option.html
index f87241b..cb97816 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_NFS-Do_Not_Use_the_no_root_squash_Option.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_NFS-Do_Not_Use_the_no_root_squash_Option.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.4.3. Do Not Use the no_root_squash Option</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" cl
ass="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_NFS-Beware_of_Syntax_Errors.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_NFS-NFS_Firewall_Configuration.html"><strong>Next</strong></a></li></ul><div class="section" title="2.2.4.3. Do Not Use the no_root_squash Option" id="sect-Security_Guide-Securing_NFS-Do_Not_Use_the_no_root_squash_Option"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.4.3. Do Not Use the <code class="command">n
o_root_squash</code> Option</h4></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>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" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" cla
ss="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_NFS-Beware_of_Syntax_Errors.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_NFS-NFS_Firewall_Configuration.html"><strong>Next</strong></a></li></ul><div class="section" title="2.2.4.3. Do Not Use the no_root_squash Option" id="sect-Security_Guide-Securing_NFS-Do_Not_Use_the_no_root_squash_Option"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Securing_NFS-Do_Not_Use_t
he_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.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_NFS-NFS_Firewall_Configuration.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_NFS-NFS_Firewall_Configuration.html
index 58ec6bc..6518161 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_NFS-NFS_Firewall_Configuration.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_NFS-NFS_Firewall_Configuration.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.4.4. NFS Firewall Configuration</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="to
c"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_NFS-Do_Not_Use_the_no_root_squash_Option.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Server_Security-Securing_the_Apache_HTTP_Server.html"><strong>Next</strong></a></li></ul><div class="section" title="2.2.4.4. NFS Firewall Configuration" id="sect-Security_Guide-Securing_NFS-NFS_Firewall_Configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.4.4. NFS Firewa
ll Configuration</h4></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.4.4. NFS Firewall Configuration</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc
"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_NFS-Do_Not_Use_the_no_root_squash_Option.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Server_Security-Securing_the_Apache_HTTP_Server.html"><strong>Next</strong></a></li></ul><div class="section" title="2.2.4.4. NFS Firewall Configuration" id="sect-Security_Guide-Securing_NFS-NFS_Firewall_Configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Gui
de-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 class="listitem"><div class="para">
<code class="command">MOUNTD_PORT</code> — TCP and UDP port for mountd (rpc.mountd)
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_NIS-Assign_Static_Ports_and_Use_iptables_Rules.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_NIS-Assign_Static_Ports_and_Use_iptables_Rules.html
index d77250a..2d1e13a 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_NIS-Assign_Static_Ports_and_Use_iptables_Rules.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_NIS-Assign_Static_Ports_and_Use_iptables_Rules.html
@@ -1,15 +1,13 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.3.4. Assign Static Ports and Use iptables Rules</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><
iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_NIS-Edit_the_varypsecurenets_File.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_NIS-Use_Kerberos_Authentication.html"><strong>Next</strong></a></li></ul><div class="section" title="2.2.3.4. Assign Static Ports and Use iptables Rules" id="sect-Security_Guide-Securing_NIS-Assign_Static_Ports_and_Use_iptables_Rules"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.3.
4. Assign Static Ports and Use iptables Rules</h4></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.3.4. Assign Static Ports and Use iptables Rules</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><i
frame id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_NIS-Edit_the_varypsecurenets_File.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_NIS-Use_Kerberos_Authentication.html"><strong>Next</strong></a></li></ul><div class="section" title="2.2.3.4. Assign Static Ports and Use iptables Rules" id="sect-Security_Guide-Securing_NIS-Assign_Static_Ports_and_Use_iptables_Rules"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sec
t-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">
+ </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">
+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">Section 2.8, “Firewallsâ€</a> for more information about implementing firewalls with iptables commands.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_NIS-Edit_the_varypsecurenets_File.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_NIS-Edit_the_varypsecurenets_File.html
index b7e06c1..c70a132 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_NIS-Edit_the_varypsecurenets_File.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_NIS-Edit_the_varypsecurenets_File.html
@@ -1,11 +1,10 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.3.3. Edit the /var/yp/securenets File</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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><b
ody class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_NIS-Use_a_Password_like_NIS_Domain_Name_and_Hostname.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_NIS-Assign_Static_Ports_and_Use_iptables_Rules.html"><strong>Next</strong></a></li></ul><div class="section" title="2.2.3.3. Edit the /var/yp/securenets File" id="sect-Security_Guide-Securing_NIS-Edit_the_varypsecurenets_File"><div class="titlepage"><div>
<div keep-together.within-column="always"><h4 class="title">2.2.3.3. Edit the <code class="filename">/var/yp/securenets</code> File</h4></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.3.3. Edit the /var/yp/securenets File</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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><bo
dy class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_NIS-Use_a_Password_like_NIS_Domain_Name_and_Hostname.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_NIS-Assign_Static_Ports_and_Use_iptables_Rules.html"><strong>Next</strong></a></li></ul><div class="section" title="2.2.3.3. Edit the /var/yp/securenets File" id="sect-Security_Guide-Securing_NIS-Edit_the_varypsecurenets_File"><div class="titlepage"><div><
div keep-together.within-column="always"><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">
+ </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.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_NIS-Use_Kerberos_Authentication.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_NIS-Use_Kerberos_Authentication.html
index 9f308f5..f49f123 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_NIS-Use_Kerberos_Authentication.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_NIS-Use_Kerberos_Authentication.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.3.5. Use Kerberos Authentication</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe"
class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_NIS-Assign_Static_Ports_and_Use_iptables_Rules.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Server_Security-Securing_NFS.html"><strong>Next</strong></a></li></ul><div class="section" title="2.2.3.5. Use Kerberos Authentication" id="sect-Security_Guide-Securing_NIS-Use_Kerberos_Authentication"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.3.5. Use Kerberos Authentication</h4></div></div></
div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.3.5. Use Kerberos Authentication</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" c
lass="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_NIS-Assign_Static_Ports_and_Use_iptables_Rules.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Server_Security-Securing_NFS.html"><strong>Next</strong></a></li></ul><div class="section" title="2.2.3.5. Use Kerberos Authentication" id="sect-Security_Guide-Securing_NIS-Use_Kerberos_Authentication"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Securing_NIS-Use_Kerberos_Authent
ication">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">Section 2.6, “Kerberosâ€</a> for more information about Kerberos.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_NIS-Use_a_Password_like_NIS_Domain_Name_and_Hostname.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_NIS-Use_a_Password_like_NIS_Domain_Name_and_Hostname.html
index d808574..ddea4bc 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_NIS-Use_a_Password_like_NIS_Domain_Name_and_Hostname.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_NIS-Use_a_Password_like_NIS_Domain_Name_and_Hostname.html
@@ -1,14 +1,12 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>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" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" cl
ass="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Server_Security-Securing_NIS.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_NIS-Edit_the_varypsecurenets_File.html"><strong>Next</strong></a></li></ul><div class="section" title="2.2.3.2. Use a Password-like NIS Domain Name and Hostname" id="sect-Security_Guide-Securing_NIS-Use_a_Password_like_NIS_Domain_Name_and_Hostname"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.3.2. Use a Password-like
NIS Domain Name and Hostname</h4></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>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" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" cla
ss="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Server_Security-Securing_NIS.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_NIS-Edit_the_varypsecurenets_File.html"><strong>Next</strong></a></li></ul><div class="section" title="2.2.3.2. Use a Password-like NIS Domain Name and Hostname" id="sect-Security_Guide-Securing_NIS-Use_a_Password_like_NIS_Domain_Name_and_Hostname"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Securi
ng_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">
+ </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">
+ </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.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_Portmap-Protect_portmap_With_iptables.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_Portmap-Protect_portmap_With_iptables.html
index 0467d7d..2239faf 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_Portmap-Protect_portmap_With_iptables.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_Portmap-Protect_portmap_With_iptables.html
@@ -1,14 +1,12 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.2.2. Protect portmap With iptables</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">Th
is is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Server_Security-Securing_Portmap.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Server_Security-Securing_NIS.html"><strong>Next</strong></a></li></ul><div class="section" title="2.2.2.2. Protect portmap With iptables" id="sect-Security_Guide-Securing_Portmap-Protect_portmap_With_iptables"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.2.2. Protect portmap With iptables</h4></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.2.2. Protect portmap With iptables</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">Thi
s is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Server_Security-Securing_Portmap.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Server_Security-Securing_NIS.html"><strong>Next</strong></a></li></ul><div class="section" title="2.2.2.2. Protect portmap With iptables" id="sect-Security_Guide-Securing_Portmap-Protect_portmap_With_iptables"><div class="titlepage"><div><div keep-together.within-column="always"><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">
+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">
+ </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">Section 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>Prev</strong>2.2.2. Securing Portmap</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Server_Security-Securing_NIS.html"><strong>Next</strong>2.2.3. Securing NIS</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_Sendmail-Mail_only_Users.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_Sendmail-Mail_only_Users.html
index 86f3e24..641b99f 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_Sendmail-Mail_only_Users.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_Sendmail-Mail_only_Users.html
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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 and 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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" cla
ss="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_Sendmail-NFS_and_Sendmail.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Server_Security-Verifying_Which_Ports_Are_Listening.html"><strong>Next</strong></a></li></ul><div class="section" title="2.2.7.3. Mail-only Users" id="sect-Security_Guide-Securing_Sendmail-Mail_only_Users"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.7.3. Mail-only Users</h4></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.7.3. Mail-only Users</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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 and 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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" clas
s="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_Sendmail-NFS_and_Sendmail.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Server_Security-Verifying_Which_Ports_Are_Listening.html"><strong>Next</strong></a></li></ul><div class="section" title="2.2.7.3. Mail-only Users" id="sect-Security_Guide-Securing_Sendmail-Mail_only_Users"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Securing_Sendmail-Mail_only_Users">2.2.7.3. Mail-onl
y 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>Prev</strong>2.2.7.2. NFS and Sendmail</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Server_Security-Verifying_Which_Ports_Are_Listening.html"><strong>Next</strong>2.2.8. Verifying Which Ports Are Listening</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_Sendmail-NFS_and_Sendmail.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_Sendmail-NFS_and_Sendmail.html
index 2a1d7ed..c8938cb 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_Sendmail-NFS_and_Sendmail.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Securing_Sendmail-NFS_and_Sendmail.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.7.2. NFS and Sendmail</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">T
his is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Server_Security-Securing_Sendmail.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_Sendmail-Mail_only_Users.html"><strong>Next</strong></a></li></ul><div class="section" title="2.2.7.2. NFS and Sendmail" id="sect-Security_Guide-Securing_Sendmail-NFS_and_Sendmail"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.7.2. NFS and Sendmail</h4></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.7.2. NFS and Sendmail</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">Th
is is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Server_Security-Securing_Sendmail.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_Sendmail-Mail_only_Users.html"><strong>Next</strong></a></li></ul><div class="section" title="2.2.7.2. NFS and Sendmail" id="sect-Security_Guide-Securing_Sendmail-NFS_and_Sendmail"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Securing_Sendmail-NFS_and_Sendmail">2.2.7.2. NFS and 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.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Security_Updates.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Security_Updates.html
index 2bd4463..b131f5a 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Security_Updates.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Security_Updates.html
@@ -1,10 +1,10 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.5. Security Updates</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="chap-Security_Guide-Security_Overview.html" title="Chapter 1. Security Overview" /><link rel="prev" href="sect-Security_Guide-Common_Exploits_and_Attacks.html" title="1.4. Common Exploits and Attacks" /><link rel="next" href="sect-Security_Guide-Updating_Packages-Verifying_Signed_Packages.html" title="1.5.2. Verifying Signed Packages" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.ht
ml">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Common_Exploits_and_Attacks.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Updating_Packages-Verifying_Signed_Packages.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" title="1.5. Security Updates" id="sect-Security_Guide-Security_Updates" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">1.5. Security Updates</h2></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.5. Security Updates</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="chap-Security_Guide-Security_Overview.html" title="Chapter 1. Security Overview" /><link rel="prev" href="sect-Security_Guide-Common_Exploits_and_Attacks.html" title="1.4. Common Exploits and Attacks" /><link rel="next" href="sect-Security_Guide-Updating_Packages-Verifying_Signed_Packages.html" title="1.5.2. Verifying Signed Packages" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.htm
l">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Common_Exploits_and_Attacks.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Updating_Packages-Verifying_Signed_Packages.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" title="1.5. Security Updates" id="sect-Security_Guide-Security_Updates" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sect-Security_Guide-Security_Updates">1.5. Security Updates</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" title="1.5.1. Updating Packages" id="sect-Security_Guide-Security_Updates-Updating_Packages"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">1.5.1. Updating Packages</h3></div></div></div><div class="para">
+ </div><div class="section" title="1.5.1. Updating Packages" id="sect-Security_Guide-Security_Updates-Updating_Packages"><div class="titlepage"><div><div keep-together.within-column="always"><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.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Server_Security-Securing_FTP.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Server_Security-Securing_FTP.html
index 69c23dd..7a877ad 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Server_Security-Securing_FTP.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Server_Security-Securing_FTP.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.6. Securing FTP</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Server_Security-Securing_the_Apache_HTTP_Server.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_FTP-Anonymous_Access.html"><strong>Next</strong></a></li></ul><div class="section" title="2.2.6. Securing FTP" id="sect-Security_Guide-Server_Security-Securing_FTP"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.2.6. Securing FTP</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.6. Securing FTP</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Server_Security-Securing_the_Apache_HTTP_Server.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_FTP-Anonymous_Access.html"><strong>Next</strong></a></li></ul><div class="section" title="2.2.6. Securing FTP" id="sect-Security_Guide-Server_Security-Securing_FTP"><div class="titlepage"><div><div keep-together.within-column="always"><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 provides three FTP servers.
@@ -12,21 +12,18 @@
<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" title="2.2.6.1. FTP Greeting Banner" id="sect-Security_Guide-Securing_FTP-FTP_Greeting_Banner"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.6.1. FTP Greeting Banner</h4></div></div></div><div class="para">
+ </div><div class="section" title="2.2.6.1. FTP Greeting Banner" id="sect-Security_Guide-Securing_FTP-FTP_Greeting_Banner"><div class="titlepage"><div><div keep-together.within-column="always"><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">
+ </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">
+ </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">Section 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">
+ </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">Section 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>Prev</strong>2.2.5. Securing the Apache HTTP Server</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_FTP-Anonymous_Access.html"><strong>Next</strong>2.2.6.2. Anonymous Access</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Server_Security-Securing_NFS.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Server_Security-Securing_NFS.html
index e47d2a0..99536e9 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Server_Security-Securing_NFS.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Server_Security-Securing_NFS.html
@@ -1,7 +1,7 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.4. Securing NFS</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html"
>This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_NIS-Use_Kerberos_Authentication.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_NFS-Beware_of_Syntax_Errors.html"><strong>Next</strong></a></li></ul><div class="section" title="2.2.4. Securing NFS" id="sect-Security_Guide-Server_Security-Securing_NFS"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.2.4. Securing NFS</h3></div></div></div><div class="important"><h2>Important</h2><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.4. Securing NFS</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">
This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_NIS-Use_Kerberos_Authentication.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_NFS-Beware_of_Syntax_Errors.html"><strong>Next</strong></a></li></ul><div class="section" title="2.2.4. Securing NFS" id="sect-Security_Guide-Server_Security-Securing_NFS"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Server_Security-Securing_NFS">2.2.4. Securing NFS</h3></div></div></div><div class="important"><h2>Importa
nt</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">Section 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" title="2.2.4.1. Carefully Plan the Network" id="sect-Security_Guide-Securing_NFS-Carefully_Plan_the_Network"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.4.1. Carefully Plan the Network</h4></div></div></div><div class="para">
+ </div></div><div class="section" title="2.2.4.1. Carefully Plan the Network" id="sect-Security_Guide-Securing_NFS-Carefully_Plan_the_Network"><div class="titlepage"><div><div keep-together.within-column="always"><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>Prev</strong>2.2.3.5. Use Kerberos Authentication</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_NFS-Beware_of_Syntax_Errors.html"><strong>Next</strong>2.2.4.2. Beware of Syntax Errors</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Server_Security-Securing_NIS.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Server_Security-Securing_NIS.html
index d24f46f..841b0c6 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Server_Security-Securing_NIS.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Server_Security-Securing_NIS.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.3. Securing NIS</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><i
frame id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_Portmap-Protect_portmap_With_iptables.html"><strong>Prev</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>Next</strong></a></li></ul><div class="section" title="2.2.3. Securing NIS" id="sect-Security_Guide-Server_Security-Securing_NIS"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.2.3. Securing NIS</h3></div></div></di
v><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.3. Securing NIS</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><if
rame id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_Portmap-Protect_portmap_With_iptables.html"><strong>Prev</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>Next</strong></a></li></ul><div class="section" title="2.2.3. Securing NIS" id="sect-Security_Guide-Server_Security-Securing_NIS"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Server_Security-Se
curing_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:
@@ -16,6 +16,6 @@
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">Section 2.2.2, “Securing Portmapâ€</a>, then address the following issues, such as network planning.
- </div><div class="section" title="2.2.3.1. Carefully Plan the Network" id="sect-Security_Guide-Securing_NIS-Carefully_Plan_the_Network"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.3.1. Carefully Plan the Network</h4></div></div></div><div class="para">
+ </div><div class="section" title="2.2.3.1. Carefully Plan the Network" id="sect-Security_Guide-Securing_NIS-Carefully_Plan_the_Network"><div class="titlepage"><div><div keep-together.within-column="always"><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>Prev</strong>2.2.2.2. Protect portmap With iptables</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</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>Next</strong>2.2.3.2. Use a Password-like NIS Domain Name and ...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Server_Security-Securing_Portmap.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Server_Security-Securing_Portmap.html
index 1d976ac..ffdb658 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Server_Security-Securing_Portmap.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Server_Security-Securing_Portmap.html
@@ -1,12 +1,12 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.2. Securing Portmap</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, t
o view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Server_Security.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_Portmap-Protect_portmap_With_iptables.html"><strong>Next</strong></a></li></ul><div class="section" title="2.2.2. Securing Portmap" id="sect-Security_Guide-Server_Security-Securing_Portmap"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.2.2. Securing Portmap</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.2. Securing Portmap</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to
view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Server_Security.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_Portmap-Protect_portmap_With_iptables.html"><strong>Next</strong></a></li></ul><div class="section" title="2.2.2. Securing Portmap" id="sect-Security_Guide-Server_Security-Securing_Portmap"><div class="titlepage"><div><div keep-together.within-column="always"><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" title="2.2.2.1. Protect portmap With TCP Wrappers" id="sect-Security_Guide-Securing_Portmap-Protect_portmap_With_TCP_Wrappers"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.2.1. Protect portmap With TCP Wrappers</h4></div></div></div><div class="para">
+ </div><div class="section" title="2.2.2.1. Protect portmap With TCP Wrappers" id="sect-Security_Guide-Securing_Portmap-Protect_portmap_With_TCP_Wrappers"><div class="titlepage"><div><div keep-together.within-column="always"><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.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Server_Security-Securing_Sendmail.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Server_Security-Securing_Sendmail.html
index fd6e04f..cd88f28 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Server_Security-Securing_Sendmail.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Server_Security-Securing_Sendmail.html
@@ -1,10 +1,10 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.7. Securing Sendmail</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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 and Sendmail" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../..
/toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_FTP-Use_TCP_Wrappers_To_Control_Access.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_Sendmail-NFS_and_Sendmail.html"><strong>Next</strong></a></li></ul><div class="section" title="2.2.7. Securing Sendmail" id="sect-Security_Guide-Server_Security-Securing_Sendmail"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.2.7. Securing Sendmail</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.7. Securing Sendmail</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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 and Sendmail" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../
toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_FTP-Use_TCP_Wrappers_To_Control_Access.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Securing_Sendmail-NFS_and_Sendmail.html"><strong>Next</strong></a></li></ul><div class="section" title="2.2.7. Securing Sendmail" id="sect-Security_Guide-Server_Security-Securing_Sendmail"><div class="titlepage"><div><div keep-together.within-column="always"><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" title="2.2.7.1. Limiting a Denial of Service Attack" id="sect-Security_Guide-Securing_Sendmail-Limiting_a_Denial_of_Service_Attack"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.7.1. Limiting a Denial of Service Attack</h4></div></div></div><div class="para">
+ </div><div class="section" title="2.2.7.1. Limiting a Denial of Service Attack" id="sect-Security_Guide-Securing_Sendmail-Limiting_a_Denial_of_Service_Attack"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><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.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Server_Security-Securing_the_Apache_HTTP_Server.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Server_Security-Securing_the_Apache_HTTP_Server.html
index 415fcbb..d08a41d 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Server_Security-Securing_the_Apache_HTTP_Server.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Server_Security-Securing_the_Apache_HTTP_Server.html
@@ -1,12 +1,10 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.5. Securing the Apache HTTP Server</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">Thi
s is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_NFS-NFS_Firewall_Configuration.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Server_Security-Securing_FTP.html"><strong>Next</strong></a></li></ul><div class="section" title="2.2.5. Securing the Apache HTTP Server" id="sect-Security_Guide-Server_Security-Securing_the_Apache_HTTP_Server"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.2.5. Securing the Apache HTTP Server</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.5. Securing the Apache HTTP Server</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_NFS-NFS_Firewall_Configuration.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Server_Security-Securing_FTP.html"><strong>Next</strong></a></li></ul><div class="section" title="2.2.5. Securing the Apache HTTP Server" id="sect-Security_Guide-Server_Security-Securing_the_Apache_HTTP_Server"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><pre class="screen">chown root <em class="replaceable"><code><directory_name></code></em>
-</pre></li><li class="listitem"><pre class="screen">chmod 755 <em class="replaceable"><code><directory_name></code></em>
-</pre></li></ol></div><div class="para">
+ </div><div class="orderedlist"><ol><li class="listitem"><pre class="screen">chown root <em class="replaceable"><code><directory_name></code></em></pre></li><li class="listitem"><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>.
@@ -15,8 +13,7 @@
</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><pre class="screen">UserDir enabled
-UserDir disabled root
-</pre><div class="para">
+UserDir disabled root</pre><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>Important</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.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Server_Security-Verifying_Which_Ports_Are_Listening.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Server_Security-Verifying_Which_Ports_Are_Listening.html
index 7e5c054..11c690b 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Server_Security-Verifying_Which_Ports_Are_Listening.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Server_Security-Verifying_Which_Ports_Are_Listening.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.8. Verifying Which Ports Are Listening</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, t
o view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_Sendmail-Mail_only_Users.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Single_Sign_on_SSO.html"><strong>Next</strong></a></li></ul><div class="section" title="2.2.8. Verifying Which Ports Are Listening" id="sect-Security_Guide-Server_Security-Verifying_Which_Ports_Are_Listening"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.2.8. Verifying Which Ports Are Listening</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.8. Verifying Which Ports Are Listening</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to
view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Securing_Sendmail-Mail_only_Users.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Single_Sign_on_SSO.html"><strong>Next</strong></a></li></ul><div class="section" title="2.2.8. Verifying Which Ports Are Listening" id="sect-Security_Guide-Server_Security-Verifying_Which_Ports_Are_Listening"><div class="titlepage"><div><div keep-together.within-column="always"><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.
@@ -8,8 +8,7 @@
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">
+ </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):
@@ -29,29 +28,23 @@ 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">
+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">
+ </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">
+ </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">
+ </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">
+ </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">
+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>Prev</strong>2.2.7.3. Mail-only Users</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Single_Sign_on_SSO.html"><strong>Next</strong>2.3. Single Sign-on (SSO)</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Server_Security.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Server_Security.html
index b601103..9c7d30e 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Server_Security.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Server_Security.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2. Server Security</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="chap-Security_Guide-Securing_Your_Network.html" title="Chapter 2. Securing Your Network" /><link rel="prev" href="chap-Security_Guide-Securing_Your_Network.html" title="Chapter 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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an ifr
ame, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security_Guide-Securing_Your_Network.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Server_Security-Securing_Portmap.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" title="2.2. Server Security" id="sect-Security_Guide-Server_Security" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.2. Server Security</h2></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2. Server Security</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="chap-Security_Guide-Securing_Your_Network.html" title="Chapter 2. Securing Your Network" /><link rel="prev" href="chap-Security_Guide-Securing_Your_Network.html" title="Chapter 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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an ifra
me, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security_Guide-Securing_Your_Network.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Server_Security-Securing_Portmap.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" title="2.2. Server Security" id="sect-Security_Guide-Server_Security" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><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:
@@ -12,7 +12,7 @@
Serve only one type of network service per machine whenever possible.
</div></li><li class="listitem"><div class="para">
Monitor all servers carefully for suspicious activity.
- </div></li></ul></div><div class="section" title="2.2.1. Securing Services With TCP Wrappers and xinetd" id="sect-Security_Guide-Server_Security-Securing_Services_With_TCP_Wrappers_and_xinetd"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.2.1. Securing Services With TCP Wrappers and xinetd</h3></div></div></div><div class="para">
+ </div></li></ul></div><div class="section" title="2.2.1. Securing Services With TCP Wrappers and xinetd" id="sect-Security_Guide-Server_Security-Securing_Services_With_TCP_Wrappers_and_xinetd"><div class="titlepage"><div><div keep-together.within-column="always"><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.
@@ -20,58 +20,51 @@
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">Section 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" title="2.2.1.1. Enhancing Security With TCP Wrappers" id="sect-Security_Guide-Securing_Services_With_TCP_Wrappers_and_xinetd-Enhancing_Security_With_TCP_Wrappers"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.1.1. Enhancing Security With TCP Wrappers</h4></div></div></div><div class="para">
+ </div><div class="section" title="2.2.1.1. Enhancing Security With TCP Wrappers" id="sect-Security_Guide-Securing_Services_With_TCP_Wrappers_and_xinetd-Enhancing_Security_With_TCP_Wrappers"><div class="titlepage"><div><div keep-together.within-column="always"><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" title="2.2.1.1.1. TCP Wrappers and Connection Banners" id="sect-Security_Guide-Enhancing_Security_With_TCP_Wrappers-TCP_Wrappers_and_Connection_Banners"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.2.1.1.1. TCP Wrappers and Connection Banners</h5></div></div></div><div class="para">
+ </div><div class="section" title="2.2.1.1.1. TCP Wrappers and Connection Banners" id="sect-Security_Guide-Enhancing_Security_With_TCP_Wrappers-TCP_Wrappers_and_Connection_Banners"><div class="titlepage"><div><div keep-together.within-column="always"><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">
+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" title="2.2.1.1.2. TCP Wrappers and Attack Warnings" id="sect-Security_Guide-Enhancing_Security_With_TCP_Wrappers-TCP_Wrappers_and_Attack_Warnings"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.2.1.1.2. TCP Wrappers and Attack Warnings</h5></div></div></div><div class="para">
+ </div><pre class="screen"><code class="command"> vsftpd : ALL : banners /etc/banners/ </code></pre></div><div class="section" title="2.2.1.1.2. TCP Wrappers and Attack Warnings" id="sect-Security_Guide-Enhancing_Security_With_TCP_Wrappers-TCP_Wrappers_and_Attack_Warnings"><div class="titlepage"><div><div keep-together.within-column="always"><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">
+ </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" title="2.2.1.1.3. TCP Wrappers and Enhanced Logging" id="sect-Security_Guide-Enhancing_Security_With_TCP_Wrappers-TCP_Wrappers_and_Enhanced_Logging"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.2.1.1.3. TCP Wrappers and Enhanced Logging</h5></div></div></div><div class="para">
+ </div></div></div><div class="section" title="2.2.1.1.3. TCP Wrappers and Enhanced Logging" id="sect-Security_Guide-Enhancing_Security_With_TCP_Wrappers-TCP_Wrappers_and_Enhanced_Logging"><div class="titlepage"><div><div keep-together.within-column="always"><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">
+ </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" title="2.2.1.2. Enhancing Security With xinetd" id="sect-Security_Guide-Securing_Services_With_TCP_Wrappers_and_xinetd-Enhancing_Security_With_xinetd"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.2.1.2. Enhancing Security With xinetd</h4></div></div></div><div class="para">
+ </div></div></div><div class="section" title="2.2.1.2. Enhancing Security With xinetd" id="sect-Security_Guide-Securing_Services_With_TCP_Wrappers_and_xinetd-Enhancing_Security_With_xinetd"><div class="titlepage"><div><div keep-together.within-column="always"><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" title="2.2.1.2.1. Setting a Trap" id="sect-Security_Guide-Enhancing_Security_With_xinetd-Setting_a_Trap"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.2.1.2.1. Setting a Trap</h5></div></div></div><div class="para">
+ </div><div class="section" title="2.2.1.2.1. Setting a Trap" id="sect-Security_Guide-Enhancing_Security_With_xinetd-Setting_a_Trap"><div class="titlepage"><div><div keep-together.within-column="always"><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">
+ </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">
+ </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">
+ </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:
@@ -79,7 +72,7 @@
It does not work against stealth scans.
</div></li><li class="listitem"><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" title="2.2.1.2.2. Controlling Server Resources" id="sect-Security_Guide-Enhancing_Security_With_xinetd-Controlling_Server_Resources"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.2.1.2.2. Controlling Server Resources</h5></div></div></div><div class="para">
+ </div></li></ul></div></div><div class="section" title="2.2.1.2.2. Controlling Server Resources" id="sect-Security_Guide-Enhancing_Security_With_xinetd-Controlling_Server_Resources"><div class="titlepage"><div><div keep-together.within-column="always"><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:
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Single_Sign_on_SSO-Configuring_Firefox_to_use_Kerberos_for_SSO.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Single_Sign_on_SSO-Configuring_Firefox_to_use_Kerberos_for_SSO.html
index d0e6c00..30fc422 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Single_Sign_on_SSO-Configuring_Firefox_to_use_Kerberos_for_SSO.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Single_Sign_on_SSO-Configuring_Firefox_to_use_Kerberos_for_SSO.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.3.5. Configuring Firefox to use Kerberos for SSO</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe
id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Login_Works.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM.html"><strong>Next</strong></a></li></ul><div class="section" title="2.3.5. Configuring Firefox to use Kerberos for SSO" id="sect-Security_Guide-Single_Sign_on_SSO-Configuring_Firefox_to_use_Kerberos_for_SSO"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.3.5.Â
Configuring Firefox to use Kerberos for SSO</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.3.5. Configuring Firefox to use Kerberos for SSO</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe i
d="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Login_Works.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM.html"><strong>Next</strong></a></li></ul><div class="section" title="2.3.5. Configuring Firefox to use Kerberos for SSO" id="sect-Security_Guide-Single_Sign_on_SSO-Configuring_Firefox_to_use_Kerberos_for_SSO"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><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.
@@ -19,7 +19,7 @@
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"><div class="figure-contents"><div class="mediaobject"><img src="images/fed-firefox_kerberos_SSO.png" width="444" alt="Configuring Firefox for SSO with Kerberos" /><div class="longdesc"><div class="para">
+ </div></li></ol></div><div class="figure" title="Figure 2.6. Configuring Firefox for SSO with Kerberos" 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" width="444" 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>Figure 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:
@@ -35,31 +35,26 @@ Valid starting Expires Service principal
renew until 10/26/06 23:47:54
Kerberos 4 ticket cache: /tmp/tkt10920
-klist: You have no tickets cached
-</pre><div class="section" title="2.3.5.1. Troubleshooting" id="sect-Security_Guide-Configuring_Firefox_to_use_Kerberos_for_SSO-Troubleshooting"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.3.5.1. Troubleshooting</h4></div></div></div><div class="para">
+klist: You have no tickets cached</pre><div class="section" title="2.3.5.1. Troubleshooting" id="sect-Security_Guide-Configuring_Firefox_to_use_Kerberos_for_SSO-Troubleshooting"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><div class="para">
Close all instances of Firefox.
</div></li><li class="listitem"><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 class="listitem"><div class="para">
+export NSPR_LOG_FILE=/tmp/moz.log</pre></li><li class="listitem"><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">
+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">
+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">
+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>Prev</strong>2.3.4. How Smart Card Login Works</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Pluggable_Authentication_Modules_PAM.html"><strong>Next</strong>2.4. Pluggable Authentication Modules (PAM)</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Single_Sign_on_SSO-Getting_Started_with_your_new_Smart_Card.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Single_Sign_on_SSO-Getting_Started_with_your_new_Smart_Card.html
index 6238fbb..30372cc 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Single_Sign_on_SSO-Getting_Started_with_your_new_Smart_Card.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Single_Sign_on_SSO-Getting_Started_with_your_new_Smart_Card.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.3.2. Getting Started with your new Smart Card</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src
="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Single_Sign_on_SSO.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Enrollment_Works.html"><strong>Next</strong></a></li></ul><div class="section" title="2.3.2. Getting Started with your new Smart Card" id="sect-Security_Guide-Single_Sign_on_SSO-Getting_Started_with_your_new_Smart_Card"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.3.2. Getting Started with your new Smart Card</h3></d
iv></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.3.2. Getting Started with your new Smart Card</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src=
"../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Single_Sign_on_SSO.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Enrollment_Works.html"><strong>Next</strong></a></li></ul><div class="section" title="2.3.2. Getting Started with your new Smart Card" id="sect-Security_Guide-Single_Sign_on_SSO-Getting_Started_with_your_new_Smart_Card"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Single_Sign_on_SSO-Getting_Starte
d_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.
@@ -10,8 +10,7 @@
Make sure you have the <code class="filename">nss-tools</code> package loaded.
</div></li><li class="step" title="Step 3"><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 class="step" title="Step 4"><div class="para">
+ </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 class="step" title="Step 4"><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 class="step" title="Step 5"><div class="para">
Enable Smart Card Login Support
@@ -61,9 +60,8 @@
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 class="step" title="Step 9"><div class="para">
Logout
- </div></li></ol></div><div class="section" title="2.3.2.1. Troubleshooting" id="sect-Security_Guide-Getting_Started_with_your_new_Smart_Card-Troubleshooting"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.3.2.1. Troubleshooting</h4></div></div></div><div class="para">
+ </div></li></ol></div><div class="section" title="2.3.2.1. Troubleshooting" id="sect-Security_Guide-Getting_Started_with_your_new_Smart_Card-Troubleshooting"><div class="titlepage"><div><div keep-together.within-column="always"><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">
+ </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>Prev</strong>2.3. Single Sign-on (SSO)</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Enrollment_Works.html"><strong>Next</strong>2.3.3. How Smart Card Enrollment Works</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Enrollment_Works.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Enrollment_Works.html
index b5ce5b2..8c3a32d 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Enrollment_Works.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Enrollment_Works.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.3.3. How Smart Card Enrollment Works</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class
="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Single_Sign_on_SSO-Getting_Started_with_your_new_Smart_Card.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Login_Works.html"><strong>Next</strong></a></li></ul><div class="section" title="2.3.3. How Smart Card Enrollment Works" id="sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Enrollment_Works"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="t
itle">2.3.3. How Smart Card Enrollment Works</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.3.3. How Smart Card Enrollment Works</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class=
"toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Single_Sign_on_SSO-Getting_Started_with_your_new_Smart_Card.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Login_Works.html"><strong>Next</strong></a></li></ul><div class="section" title="2.3.3. How Smart Card Enrollment Works" id="sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Enrollment_Works"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="ti
tle" 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 class="listitem"><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>).
@@ -8,6 +8,6 @@
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 class="listitem"><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"><div class="figure-contents"><div class="mediaobject"><img src="images/SCLoginEnrollment.png" width="444" alt="How Smart Card Enrollment Works" /><div class="longdesc"><div class="para">
+ </div></li></ol></div><div class="figure" title="Figure 2.4. How Smart Card Enrollment Works" 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" width="444" alt="How Smart Card Enrollment Works" /><div class="longdesc"><div class="para">
How Smart Card Enrollment Works.
</div></div></div></div><h6>Figure 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>Prev</strong>2.3.2. Getting Started with your new Smart Card</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Login_Works.html"><strong>Next</strong>2.3.4. How Smart Card Login Works</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Login_Works.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Login_Works.html
index 29f74cc..270e041 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Login_Works.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Login_Works.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.3.4. How Smart Card Login Works</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="to
cdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Enrollment_Works.html"><strong>Prev</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>Next</strong></a></li></ul><div class="section" title="2.3.4. How Smart Card Login Works" id="sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Login_Works"><div class="titlepage"><div><div keep-together.within-column="always"><h3
class="title">2.3.4. How Smart Card Login Works</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.3.4. How Smart Card Login Works</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="toc
div" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Enrollment_Works.html"><strong>Prev</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>Next</strong></a></li></ul><div class="section" title="2.3.4. How Smart Card Login Works" id="sect-Security_Guide-Single_Sign_on_SSO-How_Smart_Card_Login_Works"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><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.
@@ -8,7 +8,7 @@
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 class="listitem"><div class="para">
This is validated against the KDC and login granted.
- </div></li></ol></div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/SCLogin.png" width="444" alt="How Smart Card Login Works" /><div class="longdesc"><div class="para">
+ </div></li></ol></div><div class="figure" title="Figure 2.5. How Smart Card Login Works" 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" width="444" alt="How Smart Card Login Works" /><div class="longdesc"><div class="para">
How Smart Card Login Works.
</div></div></div></div><h6>Figure 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.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Single_Sign_on_SSO.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Single_Sign_on_SSO.html
index c0192db..b4ba0ac 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Single_Sign_on_SSO.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Single_Sign_on_SSO.html
@@ -1,10 +1,10 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.3. Single Sign-on (SSO)</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="chap-Security_Guide-Securing_Your_Network.html" title="Chapter 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="toc_embeded "><div id="
tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Server_Security-Verifying_Which_Ports_Are_Listening.html"><strong>Prev</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>Next</strong></a></li></ul><div xml:lang="en-US" class="section" title="2.3. Single Sign-on (SSO)" id="sect-Security_Guide-Single_Sign_on_SSO" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 clas
s="title">2.3. Single Sign-on (SSO)</h2></div></div></div><div class="section" title="2.3.1. Introduction" id="sect-Security_Guide-Single_Sign_on_SSO-Introduction"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.3.1. Introduction</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.3. Single Sign-on (SSO)</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="chap-Security_Guide-Securing_Your_Network.html" title="Chapter 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="toc_embeded "><div id="t
ocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Server_Security-Verifying_Which_Ports_Are_Listening.html"><strong>Prev</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>Next</strong></a></li></ul><div xml:lang="en-US" class="section" title="2.3. Single Sign-on (SSO)" id="sect-Security_Guide-Single_Sign_on_SSO" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class
="title" id="sect-Security_Guide-Single_Sign_on_SSO">2.3. Single Sign-on (SSO)</h2></div></div></div><div class="section" title="2.3.1. Introduction" id="sect-Security_Guide-Single_Sign_on_SSO-Introduction"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Single_Sign_on_SSO-Introduction">2.3.1. Introduction</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" title="2.3.1.1. Supported Applications" id="sect-Security_Guide-Introduction-Supported_Applications"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.3.1.1. Supported Applications</h4></div></div></div><div class="para">
+ </div><div class="section" title="2.3.1.1. Supported Applications" id="sect-Security_Guide-Introduction-Supported_Applications"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Introduction-Supported_Applications">2.3.1.1. Supported Applications</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 class="listitem"><div class="para">
Login
@@ -12,19 +12,19 @@
Screensaver
</div></li><li class="listitem"><div class="para">
Firefox and Thunderbird
- </div></li></ul></div></div><div class="section" title="2.3.1.2. Supported Authentication Mechanisms" id="sect-Security_Guide-Introduction-Supported_Authentication_Mechanisms"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.3.1.2. Supported Authentication Mechanisms</h4></div></div></div><div class="para">
+ </div></li></ul></div></div><div class="section" title="2.3.1.2. Supported Authentication Mechanisms" id="sect-Security_Guide-Introduction-Supported_Authentication_Mechanisms"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><div class="para">
Kerberos name/password login
</div></li><li class="listitem"><div class="para">
Smart card/PIN login
- </div></li></ul></div></div><div class="section" title="2.3.1.3. Supported Smart Cards" id="sect-Security_Guide-Introduction-Supported_Smart_Cards"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.3.1.3. Supported Smart Cards</h4></div></div></div><div class="para">
+ </div></li></ul></div></div><div class="section" title="2.3.1.3. Supported Smart Cards" id="sect-Security_Guide-Introduction-Supported_Smart_Cards"><div class="titlepage"><div><div keep-together.within-column="always"><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" title="2.3.1.4. Advantages of Fedora Single Sign-on" id="sect-Security_Guide-Introduction-Advantages_of_PROD_Single_Sign_on"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.3.1.4. Advantages of Fedora Single Sign-on</h4></div></div></div><div class="para">
+ </div></div><div class="section" title="2.3.1.4. Advantages of Fedora Single Sign-on" id="sect-Security_Guide-Introduction-Advantages_of_PROD_Single_Sign_on"><div class="titlepage"><div><div keep-together.within-column="always"><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:
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Software_Maintenance-Install_Signed_Packages_from_Well_Known_Repositories.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Software_Maintenance-Install_Signed_Packages_from_Well_Known_Repositories.html
index cb47f77..48aa5af 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Software_Maintenance-Install_Signed_Packages_from_Well_Known_Repositories.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Software_Maintenance-Install_Signed_Packages_from_Well_Known_Repositories.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.4. Install Signed Packages from Well Known Repositories</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="chap-Security_Guide-Software_Maintenance.html" title="Chapter 6. Software Maintenance" /><link rel="prev" href="sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates-Adjusting_Automatic_Updates.html" title="6.3. Adjusting Automatic Updates" /><link rel="next" href="chap-Security_Guide-References.html" title="Chapter 7. References" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><
iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates-Adjusting_Automatic_Updates.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Security_Guide-References.html"><strong>Next</strong></a></li></ul><div class="section" title="6.4. Install Signed Packages from Well Known Repositories" id="sect-Security_Guide-Software_Maintenance-Install_Signed_Packages_from_Well_Known_Repositories"><div class="titlepage"><div><div keep-together.within-colu
mn="always"><h2 class="title">6.4. Install Signed Packages from Well Known Repositories</h2></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.4. Install Signed Packages from Well Known Repositories</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="chap-Security_Guide-Software_Maintenance.html" title="Chapter 6. Software Maintenance" /><link rel="prev" href="sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates-Adjusting_Automatic_Updates.html" title="6.3. Adjusting Automatic Updates" /><link rel="next" href="chap-Security_Guide-References.html" title="Chapter 7. References" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><i
frame id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates-Adjusting_Automatic_Updates.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Security_Guide-References.html"><strong>Next</strong></a></li></ul><div class="section" title="6.4. Install Signed Packages from Well Known Repositories" id="sect-Security_Guide-Software_Maintenance-Install_Signed_Packages_from_Well_Known_Repositories"><div class="titlepage"><div><div keep-together.within-colum
n="always"><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.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates-Adjusting_Automatic_Updates.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates-Adjusting_Automatic_Updates.html
index de3f46c..fe28dfb 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates-Adjusting_Automatic_Updates.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates-Adjusting_Automatic_Updates.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.3. Adjusting Automatic Updates</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="chap-Security_Guide-Software_Maintenance.html" title="Chapter 6. Software Maintenance" /><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><bod
y class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Software_Maintenance-Install_Signed_Packages_from_Well_Known_Repositories.html"><strong>Next</strong></a></li></ul><div class="section" title="6.3. Adjusting Automatic Updates" id="sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates-Adjusting_Aut
omatic_Updates"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.3. Adjusting Automatic Updates</h2></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.3. Adjusting Automatic Updates</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="chap-Security_Guide-Software_Maintenance.html" title="Chapter 6. Software Maintenance" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Software_Maintenance-Install_Signed_Packages_from_Well_Known_Repositories.html"><strong>Next</strong></a></li></ul><div class="section" title="6.3. Adjusting Automatic Updates" id="sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates-Adjusting_Auto
matic_Updates"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates-Adjusting_Automatic_Updates">6.3. Adjusting Automatic Updates</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 -> Software Updates</code>. In KDE it is located at: <code class="code">Applications -> Settings -> Software Updates</code>.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates.html
index 9124ee6..6c1967f 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.2. Plan and Configure Security Updates</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="chap-Security_Guide-Software_Maintenance.html" title="Chapter 6. Software Maintenance" /><link rel="prev" href="chap-Security_Guide-Software_Maintenance.html" title="Chapter 6. Software Maintenance" /><link rel="next" href="sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates-Adjusting_Automatic_Updates.html" title="6.3. Adjusting Automatic Updates" /></head><body class="toc_embeded "><div id="tocdiv" class="toc
"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security_Guide-Software_Maintenance.html"><strong>Prev</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>Next</strong></a></li></ul><div class="section" title="6.2. Plan and Configure Security Updates" id="sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class
="title">6.2. Plan and Configure Security Updates</h2></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.2. Plan and Configure Security Updates</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="chap-Security_Guide-Software_Maintenance.html" title="Chapter 6. Software Maintenance" /><link rel="prev" href="chap-Security_Guide-Software_Maintenance.html" title="Chapter 6. Software Maintenance" /><link rel="next" href="sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates-Adjusting_Automatic_Updates.html" title="6.3. Adjusting Automatic Updates" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"
><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security_Guide-Software_Maintenance.html"><strong>Prev</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>Next</strong></a></li></ul><div class="section" title="6.2. Plan and Configure Security Updates" id="sect-Security_Guide-Software_Maintenance-Plan_and_Configure_Security_Updates"><div class="titlepage"><div><div keep-together.within-column="always"><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.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-TCP_Wrappers_Configuration_Files-Option_Fields.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-TCP_Wrappers_Configuration_Files-Option_Fields.html
index f723c99..47a9117 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-TCP_Wrappers_Configuration_Files-Option_Fields.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-TCP_Wrappers_Configuration_Files-Option_Fields.html
@@ -1,15 +1,13 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.5.2.2. Option Fields</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Access Control" /></head><body class="toc_embeded "><div id="tocdiv" class
="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers_Configuration_Files.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Option_Fields-Access_Control.html"><strong>Next</strong></a></li></ul><div class="section" title="2.5.2.2. Option Fields" id="sect-Security_Guide-TCP_Wrappers_Configuration_Files-Option_Fields"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.5.2.2. Option Fields</h4></div>
</div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.5.2.2. Option Fields</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Access Control" /></head><body class="toc_embeded "><div id="tocdiv" class=
"toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers_Configuration_Files.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Option_Fields-Access_Control.html"><strong>Next</strong></a></li></ul><div class="section" title="2.5.2.2. Option Fields" id="sect-Security_Guide-TCP_Wrappers_Configuration_Files-Option_Fields"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-TCP_Wrapper
s_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" title="2.5.2.2.1. Logging" id="sect-Security_Guide-Option_Fields-Logging"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.5.2.2.1. Logging</h5></div></div></div><div class="para">
+ </div><div class="section" title="2.5.2.2.1. Logging" id="sect-Security_Guide-Option_Fields-Logging"><div class="titlepage"><div><div keep-together.within-column="always"><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">
+ </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">
+ </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>Prev</strong>2.5.2. TCP Wrappers Configuration Files</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Option_Fields-Access_Control.html"><strong>Next</strong>2.5.2.2.2. Access Control</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-TCP_Wrappers_and_xinetd-Additional_Resources.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-TCP_Wrappers_and_xinetd-Additional_Resources.html
index 1312d82..92a4e30 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-TCP_Wrappers_and_xinetd-Additional_Resources.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-TCP_Wrappers_and_xinetd-Additional_Resources.html
@@ -1,8 +1,8 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class
="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Altering_xinetd_Configuration_Files-Resource_Management_Options.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Additional_Resources-Useful_TCP_Wrappers_Websites.html"><strong>Next</strong></a></li></ul><div class="section" title="2.5.5. Additional Resources" id="sect-Security_Guide-TCP_Wrappers_and_xinetd-Additional_Resources"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.5
.5. Additional Resources</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.5.5. Additional Resources</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class=
"toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Altering_xinetd_Configuration_Files-Resource_Management_Options.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Additional_Resources-Useful_TCP_Wrappers_Websites.html"><strong>Next</strong></a></li></ul><div class="section" title="2.5.5. Additional Resources" id="sect-Security_Guide-TCP_Wrappers_and_xinetd-Additional_Resources"><div class="titlepage"><div><div keep-together.within-column="always"><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" title="2.5.5.1. Installed TCP Wrappers Documentation" id="sect-Security_Guide-Additional_Resources-Installed_TCP_Wrappers_Documentation"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.5.5.1. Installed TCP Wrappers Documentation</h4></div></div></div><div class="para">
+ </div><div class="section" title="2.5.5.1. Installed TCP Wrappers Documentation" id="sect-Security_Guide-Additional_Resources-Installed_TCP_Wrappers_Documentation"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><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.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers_Configuration_Files.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers_Configuration_Files.html
index 8a68273..f3d94a6 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers_Configuration_Files.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers_Configuration_Files.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.5.2. TCP Wrappers Configuration Files</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../.
./toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-TCP_Wrappers_and_xinetd.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-TCP_Wrappers_Configuration_Files-Option_Fields.html"><strong>Next</strong></a></li></ul><div class="section" title="2.5.2. TCP Wrappers Configuration Files" id="sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers_Configuration_Files"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.5.2. TCP Wrappers Configuration Files</h3></div></div></div><div class="par
a">
+<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" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../..
/toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-TCP_Wrappers_and_xinetd.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-TCP_Wrappers_Configuration_Files-Option_Fields.html"><strong>Next</strong></a></li></ul><div class="section" title="2.5.2. TCP Wrappers Configuration Files" id="sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers_Configuration_Files"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers_Configuration_File
s">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 class="listitem"><div class="para">
<code class="filename">/etc/hosts.allow</code>
@@ -24,13 +24,11 @@
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" title="2.5.2.1. Formatting Access Rules" id="sect-Security_Guide-TCP_Wrappers_Configuration_Files-Formatting_Access_Rules"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.5.2.1. Formatting Access Rules</h4></div></div></div><div class="para">
+ </div><pre class="screen">warning: /etc/hosts.allow, line 20: missing newline or line too long</pre></div><div class="section" title="2.5.2.1. Formatting Access Rules" id="sect-Security_Guide-TCP_Wrappers_Configuration_Files-Formatting_Access_Rules"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><div class="para">
+ </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 class="listitem"><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. Operators">Section 2.5.2.1.4, “Operatorsâ€</a>) to allow greater flexibility.
</div></li><li class="listitem"><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. Operators">Section 2.5.2.1.4, “Operatorsâ€</a> to allow greater flexibility.
@@ -48,17 +46,15 @@
<a class="xref" href="sect-Security_Guide-TCP_Wrappers_Configuration_Files-Option_Fields.html" title="2.5.2.2. Option Fields">Section 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 : .example.com
-</pre><div class="para">
+ </div><pre class="screen">vsftpd : .example.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">
+ </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">Section 2.5.2.2, “Option Fieldsâ€</a> for a more detailed look at available options.
- </div><div class="section" title="2.5.2.1.1. Wildcards" id="sect-Security_Guide-Formatting_Access_Rules-Wildcards"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.5.2.1.1. Wildcards</h5></div></div></div><div class="para">
+ </div><div class="section" title="2.5.2.1.1. Wildcards" id="sect-Security_Guide-Formatting_Access_Rules-Wildcards"><div class="titlepage"><div><div keep-together.within-column="always"><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:
@@ -74,50 +70,42 @@
<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" title="2.5.2.1.2. Patterns" id="sect-Security_Guide-Formatting_Access_Rules-Patterns"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.5.2.1.2. Patterns</h5></div></div></div><div class="para">
+ </div></div></div><div class="section" title="2.5.2.1.2. Patterns" id="sect-Security_Guide-Formatting_Access_Rules-Patterns"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-Security_Guide-Formatting_Access_Rules-Patterns">2.5.2.1.2. Patterns</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 class="listitem"><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 : .example.com
-</pre></li><li class="listitem"><div class="para">
+ </div><pre class="screen">ALL : .example.com</pre></li><li class="listitem"><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 class="listitem"><div class="para">
+ </div><pre class="screen">ALL : 192.168.</pre></li><li class="listitem"><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">
+ </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 class="listitem"><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 class="listitem"><div class="para">
+ </div><pre class="screen">ALL : [3ffe:505:2:1::]/64</pre></li><li class="listitem"><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 : *.example.com
-</pre></li><li class="listitem"><div class="para">
+ </div><pre class="screen">ALL : *.example.com</pre></li><li class="listitem"><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">
+ </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" title="2.5.2.1.3. Portmap and TCP Wrappers" id="sect-Security_Guide-Formatting_Access_Rules-Portmap_and_TCP_Wrappers"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.5.2.1.3. Portmap and TCP Wrappers</h5></div></div></div><div class="para">
+ </div></div></div><div class="section" title="2.5.2.1.3. Portmap and TCP Wrappers" id="sect-Security_Guide-Formatting_Access_Rules-Portmap_and_TCP_Wrappers"><div class="titlepage"><div><div keep-together.within-column="always"><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" title="2.5.2.1.4. Operators" id="sect-Security_Guide-Formatting_Access_Rules-Operators"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.5.2.1.4. Operators</h5></div></div></div><div class="para">
+ </div></div><div class="section" title="2.5.2.1.4. Operators" id="sect-Security_Guide-Formatting_Access_Rules-Operators"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-Security_Guide-Formatting_Access_Rules-Operators">2.5.2.1.4. Operators</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">
+ </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">
+ </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>Prev</strong>2.5. TCP Wrappers and xinetd</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-TCP_Wrappers_Configuration_Files-Option_Fields.html"><strong>Next</strong>2.5.2.2. Option Fields</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd.html
index b585301..93356f1 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.5.3. xinetd</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This
is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Option_Fields-Expansions.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd_Configuration_Files.html"><strong>Next</strong></a></li></ul><div class="section" title="2.5.3. xinetd" id="sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.5.3. xinetd</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.5.3. xinetd</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This i
s an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Option_Fields-Expansions.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd_Configuration_Files.html"><strong>Next</strong></a></li></ul><div class="section" title="2.5.3. xinetd" id="sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd"><div class="titlepage"><div><div keep-together.within-column="always"><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.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd_Configuration_Files.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd_Configuration_Files.html
index fa4bb8c..89a7634 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd_Configuration_Files.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd_Configuration_Files.html
@@ -1,12 +1,12 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.5.4. xinetd Configuration Files</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. The /etc/xinetd.d/ Directory" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../
../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-xinetd_Configuration_Files-The_etcxinetd.d_Directory.html"><strong>Next</strong></a></li></ul><div class="section" title="2.5.4. xinetd Configuration Files" id="sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd_Configuration_Files"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.5.4. xinetd Configuration Files</h3></div></div></div><div class="p
ara">
+<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" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. The /etc/xinetd.d/ Directory" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../.
./../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-xinetd_Configuration_Files-The_etcxinetd.d_Directory.html"><strong>Next</strong></a></li></ul><div class="section" title="2.5.4. xinetd Configuration Files" id="sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd_Configuration_Files"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd_Configuration_Fi
les">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 class="listitem"><div class="para">
<code class="filename">/etc/xinetd.conf</code> — The global <code class="systemitem">xinetd</code> configuration file.
</div></li><li class="listitem"><div class="para">
<code class="filename">/etc/xinetd.d/</code> — The directory containing all service-specific files.
- </div></li></ul></div><div class="section" title="2.5.4.1. The /etc/xinetd.conf File" id="sect-Security_Guide-xinetd_Configuration_Files-The_etcxinetd.conf_File"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.5.4.1. The /etc/xinetd.conf File</h4></div></div></div><div class="para">
+ </div></li></ul></div><div class="section" title="2.5.4.1. The /etc/xinetd.conf File" id="sect-Security_Guide-xinetd_Configuration_Files-The_etcxinetd.conf_File"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-xinetd_Configuration_Files-The_etcxinetd.conf_File">2.5.4.1. The /etc/xinetd.conf File</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
{
@@ -16,8 +16,7 @@
log_on_failure = HOST
cps = 25 30
}
-includedir /etc/xinetd.d
-</pre><div class="para">
+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 class="listitem"><div class="para">
<code class="option">instances</code> — Specifies the maximum number of simultaneous requests that <code class="systemitem">xinetd</code> can process.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-TCP_Wrappers_and_xinetd.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-TCP_Wrappers_and_xinetd.html
index ae47445..3db6aaa 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-TCP_Wrappers_and_xinetd.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-TCP_Wrappers_and_xinetd.html
@@ -1,14 +1,14 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.5. TCP Wrappers and xinetd</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="chap-Security_Guide-Securing_Your_Network.html" title="Chapter 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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="t
ocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Additional_Resources-Useful_PAM_Websites.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers_Configuration_Files.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" title="2.5. TCP Wrappers and xinetd" id="sect-Security_Guide-TCP_Wrappers_and_xinetd" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.5. TCP Wrappers and xinetd
</h2></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.5. TCP Wrappers and xinetd</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="chap-Security_Guide-Securing_Your_Network.html" title="Chapter 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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="to
cframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Additional_Resources-Useful_PAM_Websites.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers_Configuration_Files.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" title="2.5. TCP Wrappers and xinetd" id="sect-Security_Guide-TCP_Wrappers_and_xinetd" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sect-Security_Guide-TCP_Wr
appers_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="Figure 2.9. Access Control to Network Services">Figure 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"><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">
+ </div><div class="figure" title="Figure 2.9. Access Control to Network Services" 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>Figure 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">Section 2.9, “IPTablesâ€</a> for information about using firewalls with <code class="command">iptables</code>.
- </div><div class="section" title="2.5.1. TCP Wrappers" id="sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.5.1. TCP Wrappers</h3></div></div></div><div class="para">
+ </div><div class="section" title="2.5.1. TCP Wrappers" id="sect-Security_Guide-TCP_Wrappers_and_xinetd-TCP_Wrappers"><div class="titlepage"><div><div keep-together.within-column="always"><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>.
@@ -20,8 +20,7 @@
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 <binary-name> | grep libwrap
-</pre><div class="para">
+ </div><pre class="screen">ldd <binary-name> | 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>.
@@ -29,8 +28,7 @@
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" title="2.5.1.1. Advantages of TCP Wrappers" id="sect-Security_Guide-TCP_Wrappers-Advantages_of_TCP_Wrappers"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.5.1.1. Advantages of TCP Wrappers</h4></div></div></div><div class="para">
+[root at myServer ~]#</pre></div><div class="section" title="2.5.1.1. Advantages of TCP Wrappers" id="sect-Security_Guide-TCP_Wrappers-Advantages_of_TCP_Wrappers"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><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.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Threats_to_Server_Security-Inattentive_Administration.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Threats_to_Server_Security-Inattentive_Administration.html
index 0ab8f23..9c351b0 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Threats_to_Server_Security-Inattentive_Administration.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Threats_to_Server_Security-Inattentive_Administration.html
@@ -1,9 +1,9 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.3.3.3. Inattentive Administration</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "
><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Threats_to_Server_Security-Unpatched_Services.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Threats_to_Server_Security-Inherently_Insecure_Services.html"><strong>Next</strong></a></li></ul><div class="section" title="1.3.3.3. Inattentive Administration" id="sect-Security_Guide-Threats_to_Server_Security-Inattentive_Administration"><div class="titlepage"><div><div keep-together.within-column="a
lways"><h4 class="title">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="id3470861" href="#ftn.id3470861" class="footnote">10</a>]</sup> This applies as much to inexperienced administrators as it does to overconfident or amotivated administrators.
+<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" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded ">
<div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Threats_to_Server_Security-Unpatched_Services.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Threats_to_Server_Security-Inherently_Insecure_Services.html"><strong>Next</strong></a></li></ul><div class="section" title="1.3.3.3. Inattentive Administration" id="sect-Security_Guide-Threats_to_Server_Security-Inattentive_Administration"><div class="titlepage"><div><div keep-together.within-column="al
ways"><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="id2879789" href="#ftn.id2879789" 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.id3470861" href="#id3470861" class="para">10</a>] </sup>
+ </div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id2879789" href="#id2879789" 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>Prev</strong>1.3.3.2. Unpatched Services</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Threats_to_Server_Security-Inherently_Insecure_Services.html"><strong>Next</strong>1.3.3.4. Inherently Insecure Services</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Threats_to_Server_Security-Inherently_Insecure_Services.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Threats_to_Server_Security-Inherently_Insecure_Services.html
index 0d47d3c..f213023 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Threats_to_Server_Security-Inherently_Insecure_Services.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Threats_to_Server_Security-Inherently_Insecure_Services.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.3.3.4. Inherently Insecure Services</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Threats_to_Server_Security-Inattentive_Administration.html"><strong>Prev</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>Next</strong></a></li></ul><div class="section" title="1.3.3.4. Inherently Insecure Services" id="sect-Security_Guide-Threats_to_Server_Security-Inherently_Ins
ecure_Services"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">1.3.3.4. Inherently Insecure Services</h4></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.3.3.4. Inherently Insecure Services</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Threats_to_Server_Security-Inattentive_Administration.html"><strong>Prev</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>Next</strong></a></li></ul><div class="section" title="1.3.3.4. Inherently Insecure Services" id="sect-Security_Guide-Threats_to_Server_Security-Inherently_Inse
cure_Services"><div class="titlepage"><div><div keep-together.within-column="always"><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.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Threats_to_Server_Security-Unpatched_Services.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Threats_to_Server_Security-Unpatched_Services.html
index 65d205f..3ca438c 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Threats_to_Server_Security-Unpatched_Services.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Threats_to_Server_Security-Unpatched_Services.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.3.3.2. Unpatched Services</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embe
ded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Server_Security.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Threats_to_Server_Security-Inattentive_Administration.html"><strong>Next</strong></a></li></ul><div class="section" title="1.3.3.2. Unpatched Services" id="sect-Security_Guide-Threats_to_Server_Security-Unpatched_Services"><div class="titlepage"><div><div keep-together.within-column="alw
ays"><h4 class="title">1.3.3.2. Unpatched Services</h4></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.3.3.2. Unpatched Services</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embed
ed "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Server_Security.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Threats_to_Server_Security-Inattentive_Administration.html"><strong>Next</strong></a></li></ul><div class="section" title="1.3.3.2. Unpatched Services" id="sect-Security_Guide-Threats_to_Server_Security-Unpatched_Services"><div class="titlepage"><div><div keep-together.within-column="alwa
ys"><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.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Threats_to_Workstation_and_Home_PC_Security-Vulnerable_Client_Applications.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Threats_to_Workstation_and_Home_PC_Security-Vulnerable_Client_Applications.html
index 3014643..988f298 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Threats_to_Workstation_and_Home_PC_Security-Vulnerable_Client_Applications.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Threats_to_Workstation_and_Home_PC_Security-Vulnerable_Client_Applications.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.3.4.2. Vulnerable Client Applications</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Common E
xploits and Attacks" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Workstation_and_Home_PC_Security.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Common_Exploits_and_Attacks.html"><strong>Next</strong></a></li></ul><div class="section" title="1.3.4.2. Vulnerable Client Applications" id="sect-Security_Guide-Threats_to_Workstation_and_Home_PC_Security-Vulnerable_Cli
ent_Applications"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">1.3.4.2. Vulnerable Client Applications</h4></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.3.4.2. Vulnerable Client Applications</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Common Ex
ploits and Attacks" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Attackers_and_Vulnerabilities-Threats_to_Workstation_and_Home_PC_Security.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Common_Exploits_and_Attacks.html"><strong>Next</strong></a></li></ul><div class="section" title="1.3.4.2. Vulnerable Client Applications" id="sect-Security_Guide-Threats_to_Workstation_and_Home_PC_Security-Vulnerable_Clie
nt_Applications"><div class="titlepage"><div><div keep-together.within-column="always"><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.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Updating_Packages-Applying_the_Changes.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Updating_Packages-Applying_the_Changes.html
index 5ed9438..ab7170b 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Updating_Packages-Applying_the_Changes.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Updating_Packages-Applying_the_Changes.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.5.4. Applying the Changes</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="sect-Security_Guide-Security_Updates.html" title="1.5. Security Updates" /><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="Chapter 2. Securing Your Network" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">Th
is is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Updating_Packages-Installing_Signed_Packages.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Security_Guide-Securing_Your_Network.html"><strong>Next</strong></a></li></ul><div class="section" title="1.5.4. Applying the Changes" id="sect-Security_Guide-Updating_Packages-Applying_the_Changes"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">1.5.4. Applying the Changes</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.5.4. Applying the Changes</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="sect-Security_Guide-Security_Updates.html" title="1.5. Security Updates" /><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="Chapter 2. Securing Your Network" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">Thi
s is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Updating_Packages-Installing_Signed_Packages.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-Security_Guide-Securing_Your_Network.html"><strong>Next</strong></a></li></ul><div class="section" title="1.5.4. Applying the Changes" id="sect-Security_Guide-Updating_Packages-Applying_the_Changes"><div class="titlepage"><div><div keep-together.within-column="always"><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.
@@ -16,15 +16,13 @@
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">
+ </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">SysV Services</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><service-name></code></em> restart</code>
-</pre><div class="para">
+ </div><pre class="screen"><code class="command">/sbin/service <em class="replaceable"><code><service-name></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"><code class="command">xinetd</code> Services</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.
@@ -34,16 +32,12 @@
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">
+ </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">
+ </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">
+ </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>Prev</strong>1.5.3. Installing Signed Packages</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="chap-Security_Guide-Securing_Your_Network.html"><strong>Next</strong>Chapter 2. Securing Your Network</a></li></ul></body></html>
+ </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>Prev</strong>1.5.3. Installing Signed Packages</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="chap-Security_Guide-Securing_Your_Network.html"><strong>Next</strong>Chapter 2. Securing Your Network</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Updating_Packages-Installing_Signed_Packages.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Updating_Packages-Installing_Signed_Packages.html
index 2e45ff9..53b8be3 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Updating_Packages-Installing_Signed_Packages.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Updating_Packages-Installing_Signed_Packages.html
@@ -1,17 +1,14 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.5.3. Installing Signed Packages</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="sect-Security_Guide-Security_Updates.html" title="1.5. Security Updates" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../
../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Updating_Packages-Verifying_Signed_Packages.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Updating_Packages-Applying_the_Changes.html"><strong>Next</strong></a></li></ul><div class="section" title="1.5.3. Installing Signed Packages" id="sect-Security_Guide-Updating_Packages-Installing_Signed_Packages"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">1.5.3. Installing Signed Packages</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.5.3. Installing Signed Packages</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="sect-Security_Guide-Security_Updates.html" title="1.5. Security Updates" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../.
./toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Updating_Packages-Verifying_Signed_Packages.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Updating_Packages-Applying_the_Changes.html"><strong>Next</strong></a></li></ul><div class="section" title="1.5.3. Installing Signed Packages" id="sect-Security_Guide-Updating_Packages-Installing_Signed_Packages"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Updating_Packages-Installing_Signed_Packages">1.5.3. Instal
ling 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">
+ </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">
+ </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">
+ </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.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Updating_Packages-Verifying_Signed_Packages.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Updating_Packages-Verifying_Signed_Packages.html
index e62519d..4e44d4e 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Updating_Packages-Verifying_Signed_Packages.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Updating_Packages-Verifying_Signed_Packages.html
@@ -1,25 +1,20 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.5.2. Verifying Signed Packages</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="sect-Security_Guide-Security_Updates.html" title="1.5. Security Updates" /><link rel="prev" href="sect-Security_Guide-Security_Updates.html" title="1.5. Security Updates" /><link rel="next" href="sect-Security_Guide-Updating_Packages-Installing_Signed_Packages.html" title="1.5.3. Installing Signed Packages" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an ifr
ame, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Security_Updates.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Updating_Packages-Installing_Signed_Packages.html"><strong>Next</strong></a></li></ul><div class="section" title="1.5.2. Verifying Signed Packages" id="sect-Security_Guide-Updating_Packages-Verifying_Signed_Packages"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">1.5.2. Verifying Signed Packages</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.5.2. Verifying Signed Packages</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="sect-Security_Guide-Security_Updates.html" title="1.5. Security Updates" /><link rel="prev" href="sect-Security_Guide-Security_Updates.html" title="1.5. Security Updates" /><link rel="next" href="sect-Security_Guide-Updating_Packages-Installing_Signed_Packages.html" title="1.5.3. Installing Signed Packages" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an ifra
me, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Security_Updates.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Updating_Packages-Installing_Signed_Packages.html"><strong>Next</strong></a></li></ul><div class="section" title="1.5.2. Verifying Signed Packages" id="sect-Security_Guide-Updating_Packages-Verifying_Signed_Packages"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Updating_Packages-Verifying_Signed_Packages">1.5.2. Verifying Signed Packages</h3></div></div></div><div clas
s="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">
+ </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">
+ </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">
+ </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">
+ </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">
+ </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.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Using_IPTables-Basic_Firewall_Policies.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Using_IPTables-Basic_Firewall_Policies.html
index c12b281..c0edbe9 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Using_IPTables-Basic_Firewall_Policies.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Using_IPTables-Basic_Firewall_Policies.html
@@ -1,17 +1,15 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.3.2. Basic Firewall Policies</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="sect-Security_Guide-Firewalls-Using_IPTables.html" title="2.8.3. Using IPTables" /><link rel="prev" href="sect-Security_Guide-Firewalls-Using_IPTables.html" title="2.8.3. Using IPTables" /><link rel="next" href="sect-Security_Guide-Using_IPTables-Saving_and_Restoring_IPTables_Rules.html" title="2.8.3.3. Saving and Restoring IPTables Rules" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../
../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Firewalls-Using_IPTables.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Using_IPTables-Saving_and_Restoring_IPTables_Rules.html"><strong>Next</strong></a></li></ul><div class="section" title="2.8.3.2. Basic Firewall Policies" id="sect-Security_Guide-Using_IPTables-Basic_Firewall_Policies"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.8.3.2. Basic Firewall Policies</h4></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.3.2. Basic Firewall Policies</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="sect-Security_Guide-Firewalls-Using_IPTables.html" title="2.8.3. Using IPTables" /><link rel="prev" href="sect-Security_Guide-Firewalls-Using_IPTables.html" title="2.8.3. Using IPTables" /><link rel="next" href="sect-Security_Guide-Using_IPTables-Saving_and_Restoring_IPTables_Rules.html" title="2.8.3.3. Saving and Restoring IPTables Rules" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../.
./../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Firewalls-Using_IPTables.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Using_IPTables-Saving_and_Restoring_IPTables_Rules.html"><strong>Next</strong></a></li></ul><div class="section" title="2.8.3.2. Basic Firewall Policies" id="sect-Security_Guide-Using_IPTables-Basic_Firewall_Policies"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Using_IPTables-Basic_Firewall_Policies">2.8.3.2. Basic Firewall Pol
icies</h4></div></div></div><div class="para">
Establishing basic firewall policies creates a foundation for building more detailed, user-defined rules.
</div><div class="para">
Each <code class="command">iptables</code> chain is comprised of a default policy, and zero or more rules which work in concert with the default policy to define the overall ruleset for the firewall.
</div><div class="para">
The default policy for a chain can be either DROP or ACCEPT. Security-minded administrators typically implement a default policy of DROP, and only allow specific packets on a case-by-case basis. For example, the following policies block all incoming and outgoing packets on a network gateway:
</div><pre class="screen">[root at myServer ~ ] # iptables -P INPUT DROP
-[root at myServer ~ ] # iptables -P OUTPUT DROP
-</pre><div class="para">
+[root at myServer ~ ] # iptables -P OUTPUT DROP</pre><div class="para">
It is also recommended that any <em class="firstterm">forwarded packets</em> — network traffic that is to be routed from the firewall to its destination node — be denied as well, to restrict internal clients from inadvertent exposure to the Internet. To do this, use the following rule:
- </div><pre class="screen">[root at myServer ~ ] # iptables -P FORWARD DROP
-</pre><div class="para">
+ </div><pre class="screen">[root at myServer ~ ] # iptables -P FORWARD DROP</pre><div class="para">
When you have established the default policies for each chain, you can create and save further rules for your particular network and security requirements.
</div><div class="para">
The following sections describe how to save iptables rules and outline some of the rules you might implement in the course of building your iptables firewall.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Using_IPTables-Saving_and_Restoring_IPTables_Rules.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Using_IPTables-Saving_and_Restoring_IPTables_Rules.html
index 72853ae..4db97d5 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Using_IPTables-Saving_and_Restoring_IPTables_Rules.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Using_IPTables-Saving_and_Restoring_IPTables_Rules.html
@@ -1,8 +1,7 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.3.3. Saving and Restoring IPTables Rules</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="sect-Security_Guide-Firewalls-Using_IPTables.html" title="2.8.3. Using IPTables" /><link rel="prev" href="sect-Security_Guide-Using_IPTables-Basic_Firewall_Policies.html" title="2.8.3.2. Basic Firewall Policies" /><link rel="next" href="sect-Security_Guide-Firewalls-Common_IPTables_Filtering.html" title="2.8.4. Common IPTables Filtering" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc
" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Using_IPTables-Basic_Firewall_Policies.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Firewalls-Common_IPTables_Filtering.html"><strong>Next</strong></a></li></ul><div class="section" title="2.8.3.3. Saving and Restoring IPTables Rules" id="sect-Security_Guide-Using_IPTables-Saving_and_Restoring_IPTables_Rules"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.8.3.3. Saving and Restoring IPTables Rules</h4></div></
div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.8.3.3. Saving and Restoring IPTables Rules</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="sect-Security_Guide-Firewalls-Using_IPTables.html" title="2.8.3. Using IPTables" /><link rel="prev" href="sect-Security_Guide-Using_IPTables-Basic_Firewall_Policies.html" title="2.8.3.2. Basic Firewall Policies" /><link rel="next" href="sect-Security_Guide-Firewalls-Common_IPTables_Filtering.html" title="2.8.4. Common IPTables Filtering" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc"
src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Using_IPTables-Basic_Firewall_Policies.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Firewalls-Common_IPTables_Filtering.html"><strong>Next</strong></a></li></ul><div class="section" title="2.8.3.3. Saving and Restoring IPTables Rules" id="sect-Security_Guide-Using_IPTables-Saving_and_Restoring_IPTables_Rules"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Using_IPTables-Saving_and_Restoring
_IPTables_Rules">2.8.3.3. Saving and Restoring IPTables Rules</h4></div></div></div><div class="para">
Changes to <code class="command">iptables</code> are transitory; if the system is rebooted or if the <code class="command">iptables</code> service is restarted, the rules are automatically flushed and reset. To save the rules so that they are loaded when the <code class="command">iptables</code> service is started, use the following command:
- </div><pre class="screen">[root at myServer ~ ] # service iptables save
-</pre><div class="para">
+ </div><pre class="screen">[root at myServer ~ ] # service iptables save</pre><div class="para">
The rules are stored in the file <code class="filename">/etc/sysconfig/iptables</code> and are applied whenever the service is started or the machine is rebooted.
</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Using_IPTables-Basic_Firewall_Policies.html"><strong>Prev</strong>2.8.3.2. Basic Firewall Policies</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Firewalls-Common_IPTables_Filtering.html"><strong>Next</strong>2.8.4. Common IPTables Filtering</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Virtual_Private_Networks_VPNs-Creating_an_IPsec_Connection.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Virtual_Private_Networks_VPNs-Creating_an_IPsec_Connection.html
index 5d49498..53c06f4 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Virtual_Private_Networks_VPNs-Creating_an_IPsec_Connection.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Virtual_Private_Networks_VPNs-Creating_an_IPsec_Connection.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.7.4. Creating an IPsec Connection</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src=
"../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Installation.html"><strong>Next</strong></a></li></ul><div class="section" title="2.7.4. Creating an IPsec Connection" id="sect-Security_Guide-Virtual_Private_Networks_VPNs-Creating_an_IPsec_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.7.4. Creating an <abbr class="abbrev">IPsec</abbr> C
onnection</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.7.4. Creating an IPsec Connection</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="
../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Installation.html"><strong>Next</strong></a></li></ul><div class="section" title="2.7.4. Creating an IPsec Connection" id="sect-Security_Guide-Virtual_Private_Networks_VPNs-Creating_an_IPsec_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Virtual_Private_Networks_VPNs-Cr
eating_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.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec.html
index 276af68..6a4df87 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.7.3. IPsec</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" c
lass="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-VPNs_and_PROD.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-Creating_an_IPsec_Connection.html"><strong>Next</strong></a></li></ul><div class="section" title="2.7.3. IPsec" id="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.7.3. IPsec</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.7.3. IPsec</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" cl
ass="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-VPNs_and_PROD.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-Creating_an_IPsec_Connection.html"><strong>Next</strong></a></li></ul><div class="section" title="2.7.3. IPsec" id="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec"><div class="titlepage"><div><div keep-together.within-column="always"><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.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Host_to_Host_Configuration.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Host_to_Host_Configuration.html
index 39c96a2..029cd8b 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Host_to_Host_Configuration.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Host_to_Host_Configuration.html
@@ -1,8 +1,8 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_
embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Installation.html"><strong>Prev</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>Next</strong></a></li></ul><div class="section" title="2.7.6. IPsec Host-to-Host Configuration" id="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Host_to_Host_Configuration"><div class="titlepage
"><div><div keep-together.within-column="always"><h3 class="title">2.7.6. IPsec Host-to-Host Configuration</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.7.6. IPsec Host-to-Host Configuration</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_e
mbeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Installation.html"><strong>Prev</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>Next</strong></a></li></ul><div class="section" title="2.7.6. IPsec Host-to-Host Configuration" id="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Host_to_Host_Configuration"><div class="titlepage"
><div><div keep-together.within-column="always"><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" title="2.7.6.1. Host-to-Host Connection" id="sect-Security_Guide-IPsec_Host_to_Host_Configuration-Host_to_Host_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.7.6.1. Host-to-Host Connection</h4></div></div></div><div class="para">
+ </div><div class="section" title="2.7.6.1. Host-to-Host Connection" id="sect-Security_Guide-IPsec_Host_to_Host_Configuration-Host_to_Host_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><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:
@@ -28,14 +28,12 @@
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">
+ </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">
+ 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 same LAN.
@@ -55,14 +53,13 @@
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 class="listitem"><div class="para">
+ </div><pre class="screen">[root at myServer ~]# service network restart</pre></li><li class="listitem"><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 class="listitem"><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="Figure 2.10. IPsec Connection">Figure 2.10, “IPsec Connectionâ€</a>.
- </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/fed-ipsec_host2host.png" width="444" alt="IPsec Connection" /><div class="longdesc"><div class="para">
+ </div><div class="figure" title="Figure 2.10. IPsec Connection" id="figu-Security_Guide-Host_to_Host_Connection-IPsec_Connection"><div class="figure-contents"><div class="mediaobject"><img src="images/fed-ipsec_host2host.png" width="444" alt="IPsec Connection" /><div class="longdesc"><div class="para">
IPsec Connection
</div></div></div></div><h6>Figure 2.10. IPsec Connection</h6></div><br class="figure-break" /><div class="para">
The following files are created when the <abbr class="abbrev">IPsec</abbr> connection is configured:
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Installation.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Installation.html
index f40f01a..bbda986 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Installation.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Installation.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.7.5. IPsec Installation</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><di
v id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-Creating_an_IPsec_Connection.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Host_to_Host_Configuration.html"><strong>Next</strong></a></li></ul><div class="section" title="2.7.5. IPsec Installation" id="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Installation"><div class="titlepage"><div><div keep-together.within-column="
always"><h3 class="title">2.7.5. IPsec Installation</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.7.5. IPsec Installation</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div
id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-Creating_an_IPsec_Connection.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Host_to_Host_Configuration.html"><strong>Next</strong></a></li></ul><div class="section" title="2.7.5. IPsec Installation" id="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Installation"><div class="titlepage"><div><div keep-together.within-column="a
lways"><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 class="listitem"><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.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Network_to_Network_Configuration.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Network_to_Network_Configuration.html
index 1dc997b..3b1ba9b 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Network_to_Network_Configuration.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Network_to_Network_Configuration.html
@@ -1,8 +1,8 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Ma
nual IPsec Network-to-Network Configuration" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-IPsec_Host_to_Host_Configuration-Manual_IPsec_Host_to_Host_Configuration.html"><strong>Prev</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>Next</strong></a></li></ul><div class="section" title="2.7.7. IPsec Network-to-Network Configurati
on" id="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Network_to_Network_Configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.7.7. IPsec Network-to-Network Configuration</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.7.7. IPsec Network-to-Network Configuration</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Man
ual IPsec Network-to-Network Configuration" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-IPsec_Host_to_Host_Configuration-Manual_IPsec_Host_to_Host_Configuration.html"><strong>Prev</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>Next</strong></a></li></ul><div class="section" title="2.7.7. IPsec Network-to-Network Configuratio
n" id="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec_Network_to_Network_Configuration"><div class="titlepage"><div><div keep-together.within-column="always"><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="Figure 2.11. A network-to-network IPsec tunneled connection">Figure 2.11, “A network-to-network <abbr class="abbrev">IPsec</abbr> tunneled connectionâ€</a> shows a network-to-network <abbr class="abbrev">IPsec</abbr> tunneled connection.
- </div><div class="figure"><div class="figure-contents"><div class="mediaobject"><img src="images/n-t-n-ipsec-diagram.png" width="444" alt="A network-to-network IPsec tunneled connection" /><div class="longdesc"><div class="para">
+ </div><div class="figure" title="Figure 2.11. A network-to-network IPsec tunneled connection" 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" width="444" 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>Figure 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.
@@ -20,13 +20,13 @@
A fixed encryption key or one automatically generated by <code class="command">racoon</code>
</div></li><li class="listitem"><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" title="2.7.7.1. Network-to-Network (VPN) Connection" id="sect-Security_Guide-IPsec_Network_to_Network_Configuration-Network_to_Network_VPN_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">2.7.7.1. Network-to-Network (<abbr class="abbrev">VPN</abbr>) Connection</h4></div></div></div><div class="para">
+ </div></li></ul></div><div class="section" title="2.7.7.1. Network-to-Network (VPN) Connection" id="sect-Security_Guide-IPsec_Network_to_Network_Configuration-Network_to_Network_VPN_Connection"><div class="titlepage"><div><div keep-together.within-column="always"><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="Figure 2.12. Network-to-Network IPsec">Figure 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"><div class="figure-contents"><div class="mediaobject"><img src="images/n-t-n-ipsec-diagram.png" width="444" alt="Network-to-Network IPsec" /><div class="longdesc"><div class="para">
+ </div><div class="figure" title="Figure 2.12. Network-to-Network IPsec" 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" width="444" alt="Network-to-Network IPsec" /><div class="longdesc"><div class="para">
Network-to-Network IPsec
</div></div></div></div><h6>Figure 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.
@@ -58,7 +58,7 @@
<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"><div class="figure-contents"><div class="mediaobject"><img src="images/fed-ipsec_n_to_n_local.png" width="444" alt="Local Network Information" /><div class="longdesc"><div class="para">
+ </div><div class="figure" title="Figure 2.13. Local Network Information" 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" width="444" alt="Local Network Information" /><div class="longdesc"><div class="para">
Local Network Information
</div></div></div></div><h6>Figure 2.13. Local Network Information</h6></div><br class="figure-break" /></li><li class="listitem"><div class="para">
On the <span class="guilabel"><strong>Remote Network</strong></span> page, enter the following information:
@@ -76,7 +76,7 @@
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"><div class="figure-contents"><div class="mediaobject"><img src="images/fed-ipsec_n_to_n_remote.png" width="444" alt="Remote Network Information" /><div class="longdesc"><div class="para">
+ </div><div class="figure" title="Figure 2.14. Remote Network Information" 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" width="444" alt="Remote Network Information" /><div class="longdesc"><div class="para">
Remote Network Information
</div></div></div></div><h6>Figure 2.14. Remote Network Information</h6></div><br class="figure-break" /></li><li class="listitem"><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>.
@@ -90,7 +90,6 @@
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 class="listitem"><div class="para">
Use the following command to enable the change:
- </div><pre class="screen">[root at myServer ~]# /sbin/sysctl -p /etc/sysctl.conf
-</pre></li></ol></div></li></ol></div><div class="para">
+ </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>Prev</strong>2.7.6.2. Manual IPsec Host-to-Host Configuration</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</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>Next</strong>2.7.7.2. Manual IPsec Network-to-Network Configur...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Virtual_Private_Networks_VPNs-Starting_and_Stopping_an_IPsec_Connection.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Virtual_Private_Networks_VPNs-Starting_and_Stopping_an_IPsec_Connection.html
index a3e5cf0..04a7116 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Virtual_Private_Networks_VPNs-Starting_and_Stopping_an_IPsec_Connection.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Virtual_Private_Networks_VPNs-Starting_and_Stopping_an_IPsec_Connection.html
@@ -1,13 +1,11 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.7.8. Starting and Stopping an IPsec Connection</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocd
iv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-IPsec_Network_to_Network_Configuration-Manual_IPsec_Network_to_Network_Configuration.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Firewalls.html"><strong>Next</strong></a></li></ul><div class="section" title="2.7.8. Starting and Stopping an IPsec Connection" id="sect-Security_Guide-Virtual_Private_Networks_VPNs-Starting_and_Stopping_an_IPsec_Connection"><div class="titlepage"><div><div keep-together.within
-column="always"><h3 class="title">2.7.8. Starting and Stopping an <abbr class="abbrev">IPsec</abbr> Connection</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.7.8. Starting and Stopping an IPsec Connection</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdi
v" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-IPsec_Network_to_Network_Configuration-Manual_IPsec_Network_to_Network_Configuration.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Firewalls.html"><strong>Next</strong></a></li></ul><div class="section" title="2.7.8. Starting and Stopping an IPsec Connection" id="sect-Security_Guide-Virtual_Private_Networks_VPNs-Starting_and_Stopping_an_IPsec_Connection"><div class="titlepage"><div><div keep-together.within-
column="always"><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">
+ </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">
To stop the connection, use the following command:
- </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>Prev</strong>2.7.7.2. Manual IPsec Network-to-Network Configur...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Firewalls.html"><strong>Next</strong>2.8. Firewalls</a></li></ul></body></html>
+ </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>Prev</strong>2.7.7.2. Manual IPsec Network-to-Network Configur...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Firewalls.html"><strong>Next</strong>2.8. Firewalls</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Virtual_Private_Networks_VPNs-VPNs_and_PROD.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Virtual_Private_Networks_VPNs-VPNs_and_PROD.html
index 717450a..269f739 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Virtual_Private_Networks_VPNs-VPNs_and_PROD.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Virtual_Private_Networks_VPNs-VPNs_and_PROD.html
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html
">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Virtual_Private_Networks_VPNs.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec.html"><strong>Next</strong></a></li></ul><div class="section" title="2.7.2. VPNs and Fedora" id="sect-Security_Guide-Virtual_Private_Networks_VPNs-VPNs_and_PROD"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.7.2. VPNs and Fedora</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.7.2. VPNs and Fedora</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html"
>This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Virtual_Private_Networks_VPNs.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec.html"><strong>Next</strong></a></li></ul><div class="section" title="2.7.2. VPNs and Fedora" id="sect-Security_Guide-Virtual_Private_Networks_VPNs-VPNs_and_PROD"><div class="titlepage"><div><div keep-together.within-column="always"><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 clas
s="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>Prev</strong>2.7. Virtual Private Networks (VPNs)</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-IPsec.html"><strong>Next</strong>2.7.3. IPsec</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Virtual_Private_Networks_VPNs.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Virtual_Private_Networks_VPNs.html
index 78acd0d..cf2e984 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Virtual_Private_Networks_VPNs.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Virtual_Private_Networks_VPNs.html
@@ -1,12 +1,12 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.7. Virtual Private Networks (VPNs)</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="chap-Security_Guide-Securing_Your_Network.html" title="Chapter 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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" cl
ass="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Additional_Resources-Useful_Kerberos_Websites.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-VPNs_and_PROD.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" title="2.7. Virtual Private Networks (VPNs)" id="sect-Security_Guide-Virtual_Private_Networks_VPNs" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.7. Virtual Private Networks (VP
Ns)</h2></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.7. Virtual Private Networks (VPNs)</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="chap-Security_Guide-Securing_Your_Network.html" title="Chapter 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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" cla
ss="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Additional_Resources-Useful_Kerberos_Websites.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Virtual_Private_Networks_VPNs-VPNs_and_PROD.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" title="2.7. Virtual Private Networks (VPNs)" id="sect-Security_Guide-Virtual_Private_Networks_VPNs" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sect-Security_Guide-Virtual_Pri
vate_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" title="2.7.1. How Does a VPN Work?" id="sect-Security_Guide-Virtual_Private_Networks_VPNs-How_Does_a_VPN_Work"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.7.1. How Does a VPN Work?</h3></div></div></div><div class="para">
+ </div><div class="section" title="2.7.1. How Does a VPN Work?" id="sect-Security_Guide-Virtual_Private_Networks_VPNs-How_Does_a_VPN_Work"><div class="titlepage"><div><div keep-together.within-column="always"><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.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Vulnerability_Assessment-Defining_Assessment_and_Testing.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Vulnerability_Assessment-Defining_Assessment_and_Testing.html
index de990cb..713e924 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Vulnerability_Assessment-Defining_Assessment_and_Testing.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Vulnerability_Assessment-Defining_Assessment_and_Testing.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.2.2. Defining Assessment and Testing</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Evaluating the Tools" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../
../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Vulnerability_Assessment.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Vulnerability_Assessment-Evaluating_the_Tools.html"><strong>Next</strong></a></li></ul><div class="section" title="1.2.2. Defining Assessment and Testing" id="sect-Security_Guide-Vulnerability_Assessment-Defining_Assessment_and_Testing"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">1.2.2. Defining Assessment and Testing</h3></div></div></div><div class
="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.2.2. Defining Assessment and Testing</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Evaluating the Tools" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../.
./../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Vulnerability_Assessment.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Vulnerability_Assessment-Evaluating_the_Tools.html"><strong>Next</strong></a></li></ul><div class="section" title="1.2.2. Defining Assessment and Testing" id="sect-Security_Guide-Vulnerability_Assessment-Defining_Assessment_and_Testing"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Vulnerability_Assessment-Defining_Assessment_and_
Testing">1.2.2. Defining Assessment and Testing</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.
@@ -30,7 +30,7 @@
Promotes growth and aids in developing staff expertise
</div></li><li class="listitem"><div class="para">
Abates financial loss and negative publicity
- </div></li></ul></div><div class="section" title="1.2.2.1. Establishing a Methodology" id="sect-Security_Guide-Defining_Assessment_and_Testing-Establishing_a_Methodology"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">1.2.2.1. Establishing a Methodology</h4></div></div></div><div class="para">
+ </div></li></ul></div><div class="section" title="1.2.2.1. Establishing a Methodology" id="sect-Security_Guide-Defining_Assessment_and_Testing-Establishing_a_Methodology"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Defining_Assessment_and_Testing-Establishing_a_Methodology">1.2.2.1. Establishing a Methodology</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.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Vulnerability_Assessment-Evaluating_the_Tools.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Vulnerability_Assessment-Evaluating_the_Tools.html
index 36722e3..5e3ee44 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Vulnerability_Assessment-Evaluating_the_Tools.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Vulnerability_Assessment-Evaluating_the_Tools.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.2.3. Evaluating the Tools</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Defining Assessment and Testing" /><link rel="next" href="sect-Security_Guide-Evaluating_the_Tools-Nessus.html" title="1.2.3.2. Nessus" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../
../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Vulnerability_Assessment-Defining_Assessment_and_Testing.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Evaluating_the_Tools-Nessus.html"><strong>Next</strong></a></li></ul><div class="section" title="1.2.3. Evaluating the Tools" id="sect-Security_Guide-Vulnerability_Assessment-Evaluating_the_Tools"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">1.2.3. Evaluating the Tools</h3></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.2.3. Evaluating the Tools</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. Defining Assessment and Testing" /><link rel="next" href="sect-Security_Guide-Evaluating_the_Tools-Nessus.html" title="1.2.3.2. Nessus" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../.
./../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-Vulnerability_Assessment-Defining_Assessment_and_Testing.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Evaluating_the_Tools-Nessus.html"><strong>Next</strong></a></li></ul><div class="section" title="1.2.3. Evaluating the Tools" id="sect-Security_Guide-Vulnerability_Assessment-Evaluating_the_Tools"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Vulnerability_Assessment-Evaluating_the_Tools">1.2.3. Ev
aluating the Tools</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.
@@ -8,14 +8,13 @@
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" title="1.2.3.1. Scanning Hosts with Nmap" id="sect-Security_Guide-Evaluating_the_Tools-Scanning_Hosts_with_Nmap"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">1.2.3.1. Scanning Hosts with Nmap</h4></div></div></div><div class="para">
+ </div><div class="section" title="1.2.3.1. Scanning Hosts with Nmap" id="sect-Security_Guide-Evaluating_the_Tools-Scanning_Hosts_with_Nmap"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-Evaluating_the_Tools-Scanning_Hosts_with_Nmap">1.2.3.1. Scanning Hosts with 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" title="1.2.3.1.1. Using Nmap" id="sect-Security_Guide-Scanning_Hosts_with_Nmap-Using_Nmap"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">1.2.3.1.1. Using Nmap</h5></div></div></div><div class="para">
+ </div><div class="section" title="1.2.3.1.1. Using Nmap" id="sect-Security_Guide-Scanning_Hosts_with_Nmap-Using_Nmap"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-Security_Guide-Scanning_Hosts_with_Nmap-Using_Nmap">1.2.3.1.1. Using 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">
+ </div><pre class="screen"><code class="command">nmap foo.example.com</code></pre><div class="para">
The results of a basic scan (which could take up to a few minutes, depending on where the host is located and other network conditions) should look similar to the following:
</div><pre class="screen">
Starting Nmap 4.68 ( http://nmap.org )
@@ -26,8 +25,7 @@ PORT STATE SERVICE
53/tcp open domain
70/tcp closed gopher
80/tcp open http
-113/tcp closed auth
-</pre><div class="para">
+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:
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Vulnerability_Assessment.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Vulnerability_Assessment.html
index f0c28ea..8c6a79f 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Vulnerability_Assessment.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-Vulnerability_Assessment.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.2. Vulnerability Assessment</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="chap-Security_Guide-Security_Overview.html" title="Chapter 1. Security Overview" /><link rel="prev" href="chap-Security_Guide-Security_Overview.html" title="Chapter 1. Security Overview" /><link rel="next" href="sect-Security_Guide-Vulnerability_Assessment-Defining_Assessment_and_Testing.html" title="1.2.2. Defining Assessment and Testing" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../.
./../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security_Guide-Security_Overview.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Vulnerability_Assessment-Defining_Assessment_and_Testing.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" title="1.2. Vulnerability Assessment" id="sect-Security_Guide-Vulnerability_Assessment" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">1.2. Vulnerability Assessment</h2></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.2. Vulnerability Assessment</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><link rel="home" href="index.html" title="Security Guide" /><link rel="up" href="chap-Security_Guide-Security_Overview.html" title="Chapter 1. Security Overview" /><link rel="prev" href="chap-Security_Guide-Security_Overview.html" title="Chapter 1. Security Overview" /><link rel="next" href="sect-Security_Guide-Vulnerability_Assessment-Defining_Assessment_and_Testing.html" title="1.2.2. Defining Assessment and Testing" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../..
/../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Security_Guide-Security_Overview.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Vulnerability_Assessment-Defining_Assessment_and_Testing.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" title="1.2. Vulnerability Assessment" id="sect-Security_Guide-Vulnerability_Assessment" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><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 class="listitem"><div class="para">
The expertise of the staff responsible for configuring, monitoring, and maintaining the technologies.
@@ -10,7 +10,7 @@
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" title="1.2.1. Thinking Like the Enemy" id="sect-Security_Guide-Vulnerability_Assessment-Thinking_Like_the_Enemy"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">1.2.1. Thinking Like the Enemy</h3></div></div></div><div class="para">
+ </div><div class="section" title="1.2.1. Thinking Like the Enemy" id="sect-Security_Guide-Vulnerability_Assessment-Thinking_Like_the_Enemy"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Security_Guide-Vulnerability_Assessment-Thinking_Like_the_Enemy">1.2.1. Thinking Like the Enemy</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.
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-xinetd_Configuration_Files-Altering_xinetd_Configuration_Files.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-xinetd_Configuration_Files-Altering_xinetd_Configuration_Files.html
index d36ee2e..9458ae5 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-xinetd_Configuration_Files-Altering_xinetd_Configuration_Files.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-xinetd_Configuration_Files-Altering_xinetd_Configuration_Files.html
@@ -1,8 +1,8 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. The /etc/xinetd.d/ Directory" /><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 c
lass="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-xinetd_Configuration_Files-The_etcxinetd.d_Directory.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Altering_xinetd_Configuration_Files-Access_Control_Options.html"><strong>Next</strong></a></li></ul><div class="section" title="2.5.4.3. Altering xinetd Configuration Files" id="sect-Security_Guide-xinetd_Configuration_Files-Altering_xinetd_Configuration_Files"><div class="titl
epage"><div><div keep-together.within-column="always"><h4 class="title">2.5.4.3. Altering xinetd Configuration Files</h4></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.5.4.3. Altering xinetd Configuration Files</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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. The /etc/xinetd.d/ Directory" /><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 cl
ass="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-xinetd_Configuration_Files-The_etcxinetd.d_Directory.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-Altering_xinetd_Configuration_Files-Access_Control_Options.html"><strong>Next</strong></a></li></ul><div class="section" title="2.5.4.3. Altering xinetd Configuration Files" id="sect-Security_Guide-xinetd_Configuration_Files-Altering_xinetd_Configuration_Files"><div class="title
page"><div><div keep-together.within-column="always"><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" title="2.5.4.3.1. Logging Options" id="sect-Security_Guide-Altering_xinetd_Configuration_Files-Logging_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">2.5.4.3.1. Logging Options</h5></div></div></div><div class="para">
+ </div><div class="section" title="2.5.4.3.1. Logging Options" id="sect-Security_Guide-Altering_xinetd_Configuration_Files-Logging_Options"><div class="titlepage"><div><div keep-together.within-column="always"><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:
diff --git a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-xinetd_Configuration_Files-The_etcxinetd.d_Directory.html b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-xinetd_Configuration_Files-The_etcxinetd.d_Directory.html
index 13dacf3..7256112 100644
--- a/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-xinetd_Configuration_Files-The_etcxinetd.d_Directory.html
+++ b/public_html/en-US/Fedora/13/html/Security_Guide/sect-Security_Guide-xinetd_Configuration_Files-The_etcxinetd.d_Directory.html
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.5.4.2. The /etc/xinetd.d/ Directory</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 1.99" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd_Configuration_Files.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-xinetd_Configuration_Files-Altering_xinetd_Configuration_Files.html"><strong>Next</strong></a></li></ul><div class="section" title="2.5.4.2. The /etc/xinetd.d/ Directory" id="sect-Security_Guide-xinetd_Configuration_Files-The_etcxinetd.d_Directory"><div class="titlepage"><div><
div keep-together.within-column="always"><h4 class="title">2.5.4.2. The /etc/xinetd.d/ Directory</h4></div></div></div><div class="para">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.5.4.2. The /etc/xinetd.d/ Directory</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.1" /><meta name="package" content="Fedora-Security_Guide-13-en-US-13.0-8" /><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="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Security_Guide-TCP_Wrappers_and_xinetd-xinetd_Configuration_Files.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Security_Guide-xinetd_Configuration_Files-Altering_xinetd_Configuration_Files.html"><strong>Next</strong></a></li></ul><div class="section" title="2.5.4.2. The /etc/xinetd.d/ Directory" id="sect-Security_Guide-xinetd_Configuration_Files-The_etcxinetd.d_Directory"><div class="titlepage"><div><d
iv keep-together.within-column="always"><h4 class="title" id="sect-Security_Guide-xinetd_Configuration_Files-The_etcxinetd.d_Directory">2.5.4.2. The /etc/xinetd.d/ Directory</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.
@@ -15,8 +15,7 @@
server = /usr/kerberos/sbin/telnetd
log_on_failure += USERID
disable = yes
-}
-</pre><div class="para">
+}</pre><div class="para">
These lines control various aspects of the <code class="command">telnet</code> service:
</div><div class="itemizedlist"><ul><li class="listitem"><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.
diff --git a/public_html/en-US/Fedora/13/pdf/Security_Guide/Fedora-13-Security_Guide-en-US.pdf b/public_html/en-US/Fedora/13/pdf/Security_Guide/Fedora-13-Security_Guide-en-US.pdf
index 9fdfbbf..c222832 100644
Binary files a/public_html/en-US/Fedora/13/pdf/Security_Guide/Fedora-13-Security_Guide-en-US.pdf and b/public_html/en-US/Fedora/13/pdf/Security_Guide/Fedora-13-Security_Guide-en-US.pdf differ
More information about the docs-commits
mailing list