Documentation Security Beat

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(removed sub-task table)
(remove note on private /tmp via systemd)
(44 intermediate revisions by 11 users not shown)
Line 1: Line 1:
 
{{header|docs}}
 
{{header|docs}}
 
{{Docs_beat_open}}
 
{{Docs_beat_open}}
{{Draft|
 
  
= Security =
+
[[Category:Docs Project]]
This section describes the security changes and enhancements available in Fedora 15. 
+
[[Category:Draft documentation]]
 +
[[Category:Documentation beats]]
  
== Dynamic Firewall ==
+
== Hardlink and symlink restrictions ==
Fedora 15 adds support for the optional firewall daemon (FirewallD), providing a dynamic firewall management with a D-Bus interface.
+
  
The previous firewall model with system-config-firewall, was static and required a full firewall restart for all changes, even simple ones. This resulted in termination of filtered connections.
+
A long-standing class of security issues is the link-based time-of-check-time-of-use race, most commonly seen in world-writable directories like /tmp. The common method of exploitation of this flaw is to cross privilege boundaries when following a given link (i.e. a root process follows a link belonging to another user). In Fedora 19,  we permit links to only be followed when outside a sticky world-writable directory, or when the uid of the link and follower match, or when the directory owner matches the link's owner.  In previous releases, this was enforced by SELinux policy and in this release, we have enabled these restrictions via the following sysctl settings in /usr/lib/sysctl.d/00-system.conf as an additional layer of protection:
Firewalld can modify the firewall dynamically and no firewall recreation is needed. At this stage, it supports iptables, ip6tables and ebtables. In Fedora 15 a simple tray applet shows the firewall state, and firewall services can be enabled and disabled.
+
  
For more details, visit the Fedora wiki pages, https://fedoraproject.org/wiki/Features/DynamicFirewall and https://fedoraproject.org/wiki/Features/FirewallD/ .
+
fs.protected_hardlinks = 1
 +
fs.protected_symlinks = 1
  
== DNSSEC on workstations  ==
+
Refer to http://lwn.net/Articles/503660/ and https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=800179c9b8a1e796e441674776d11cd4c05d61d7 for more detailed information about this changeNote that in addition to this,
In Fedora 15 comes in a new security feature that protects the end users and their workstations exposition against various DNS spoofing and DNS cache-poisoning attacks.
+
 
+
'''DNSSEC''' is an environment full tested in Fedora, as all major DNS servers in Fedora run with '''DNSSEC''' validation enabled by default since Fedora 11, giving to the Fedora Project a lot of experience from server environment. '''DNSSEC''' is aimed to secure all DNS traffic. <code>NetworkManager</code> uses the BIND nameserver as a DNSSEC resolver and all received DNS responses are proved to be correct. In case a particular domain is signed and failed to validate then resolver returns SERFVAIL instead of invalidated response, which means something is wrong.
+
 
+
For all details please refer to https://fedoraproject.org/wiki/Features/DNSSEC_on_workstations on the Fedora wiki.
+
 
+
'''dnssec-tools''' version 1.8 in Fedora 15 is the tool used to improve this feature.
+
 
+
 
+
== OpenSCAP ==
+
First introduced in Fedora 14, OpenSCAP is a set of open source libraries providing an easier path for integration of the SCAP line of standards, managed by NIST and created to provide a standardized approach to maintaining the security of enterprise systems, such as automatically verifying the presence of patches, checking system security configuration settings, and examining systems for signs of compromise.
+
 
+
In Fedora 15, '''openscap''', the set of open source libraries enabling integration of the SCAP line of standards, has been upgraded from version 0.6.3 to 0.6.8. During these development stage there has been introduced full support for perl regular expression by default, OVAL float type support, XSL transformation improvements and Dublin Core support, added OVAL schemas version 5.6 and improved XCCDF reporting.
+
 
+
'''secstate''', the Security State Configuration Tool, has been rebuilt in Fedora 15 against version 0.4.1.
+
+
'''firstaidkit''', the System Rescue Tool that automates simple and common system recovery tasks, has been upgraded from 0.2.17 to version 0.2.18.
+
 
+
For more informations visit this page [http://www.open-scap.org/page/Main_Page http://www.open-scap.org/page/Main_Page] .
+
 
+
 
+
== authoconfig ecryptfs ==
+
 
+
Fedora 15 brings in improved support for eCryptfs, a stacked cryptographic filesystem for Linux. Now when a '''ecryptfs''' user logs in, <code>authconfig</code> will automatically mount his private encrypted part of the home directory.
+
 
+
For details please refer to the wiki page https://fedoraproject.org/wiki/Features/EcryptfsAuthConfig .
+
 
+
== setroubleshoot ==
+
 
+
The user interface of setroubleshoot has been redesigned to make it easier to diagnose SELinux problems. In the current setroubleshooter the "best" match is returned for a solution to the customer. In the new redesign, all matches will be returned. For example if samba tried to read content that it is not allowed, we would like to tell the admin that he could label the content samba_share_t or he could set up SELinux to allow samba to share all content Read Only, or Read Write, or samba should not be trying to read this content, it could be a bug or an attack.
+
 
+
The interface has also been simplified with easier to explain definitions, like
+
 
+
  if you want samba to share the entire system read/only, then you need to tell
+
SELinux system about this, by setting the samba_export_all_ro boolean. Execute
+
the following command as root. setsebool -P samba_export_all_ro=1
+
 
+
 
+
== For Package Maintainers ==
+
('''perhaps don't include in the RN''')
+
 
+
Another feature that makes the applications and the Operating System more secure. Fedora 15 removes setuid applications and instead specifically assigns the capabilities required by an application, modifing the spec files of most applications that include a setuid application to remove the setuid flag and change to file capabilities.
+
 
+
Please refer to https://fedoraproject.org/wiki/Features/RemoveSETUID for all details.
+
 
+
[[Category:Docs Project]]
+
[[Category:Draft documentation]]
+
[[Category:Documentation beats]]
+

Revision as of 14:10, 20 March 2013

DocsProject Header docTeam1.png
Note.png
Beat is open
This beat is now ready to have Fedora 21 content added by the beat writer

Hardlink and symlink restrictions

A long-standing class of security issues is the link-based time-of-check-time-of-use race, most commonly seen in world-writable directories like /tmp. The common method of exploitation of this flaw is to cross privilege boundaries when following a given link (i.e. a root process follows a link belonging to another user). In Fedora 19, we permit links to only be followed when outside a sticky world-writable directory, or when the uid of the link and follower match, or when the directory owner matches the link's owner. In previous releases, this was enforced by SELinux policy and in this release, we have enabled these restrictions via the following sysctl settings in /usr/lib/sysctl.d/00-system.conf as an additional layer of protection:

fs.protected_hardlinks = 1
fs.protected_symlinks = 1

Refer to http://lwn.net/Articles/503660/ and https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=800179c9b8a1e796e441674776d11cd4c05d61d7 for more detailed information about this change. Note that in addition to this,