Documentation Security Beat: Difference between revisions

Revision as of 02:59, 28 August 2015

Beat is open
This beat is now ready to have Fedora 25 content added by the beat writer

Disable SSL 3.0 and RC4

The SSL 3.0 protocol and the RC4 cipher are considered insecure and vulnerable to attacks. As such, these two are disabled by default for all Fedora components that use the system-wide crypto policies. This includes gnutls and openssl libraries, and all the applications based on them.

Applications or environments that require SSL 3.0 or RC4 can use update-crypto-policies to globally switch to the LEGACY policy to enable SSL 3.0 and RC4.

Note (Use note tag) - All applications that use TLS from NSS are not affected by this change.

OpenSSH 7.1

The OpenSSH project continues to improve the security of network communication with the release of OpenSSH version 7.1. Details of the release are available at http://www.openssh.com/txt/release-7.1

Package Hardening

Packages compiled for Fedora 23 will be compiled with a position-independent code flag enabled by default. This was an optional setting that as a default will protect users from certain potential security vulnerabilities.

Standardized Passphrase Policy

A common password policy is being utilized to provide a set of consistent rules for password policies. These rules can be modified locally to fit user needs.

@@ Line 1: / Line 1: @@
-{{header|docs}}
+{{header|docs}}{{Docs_beat_open}}
-{{Docs_beat_open}}
-== Password Quality Checking ==
+== Disable SSL 3.0 and RC4 ==
-Fedora now has a single configurable library, ''[https://fedorahosted.org/libpwquality libpwquality]'', for checking the quality of new passwords used for system accounts. The system wide password quality checks provided by this library are configured by modifying the <code>/etc/security/pwquality.conf</code> configuration file.
+The SSL 3.0 protocol and the RC4 cipher are considered insecure and vulnerable to attacks. As such, these two are disabled by default for all Fedora components that use the system-wide crypto policies.  This includes gnutls and openssl libraries, and all the applications based on them.
-Developers wishing to call this API from their applications will find the API description in the <code>pwquality.h</code> file provided by the ''libpwquality-devel'' package. A python wrapper, ''python-pwquality'', is also provided.
+Applications or environments that require SSL 3.0 or RC4 can use [https://github.com/nmav/fedora-crypto-policies/blob/master/crypto-policies.8.txt update-crypto-policies] to globally switch to the LEGACY policy to enable SSL 3.0 and RC4.
-<!-- http://fedoraproject.org/wiki/Features/PasswordQualityChecking -->
+'''Note (Use note tag)''' - All applications that use TLS  from NSS are not affected by this change.
-== SELinux Deny Ptrace ==
+== OpenSSH 7.1 ==
+The OpenSSH project continues to improve the security of network communication with the release of OpenSSH version 7.1.  Details of the release are available at http://www.openssh.com/txt/release-7.1
-A new SELinux boolean, ''deny_ptrace'', has been added. It is recommended that users who do not plan to debug applications on their machine turn this boolean on. The boolean prevents rogue processes from being able to read the memory of, or otherwise attack, other processes using debugging tools including ''ptrace'' and ''gdb''.
+== Package Hardening ==
+Packages compiled for Fedora 23 will be compiled with a position-independent code flag enabled by default. This was an optional setting that as a default will protect users from certain potential security vulnerabilities.
-Such attacks are prevented even where the rogue process is running as the root user or attacking a process running with the same SELinux context and label. To permanently enable the protection provided by the ''deny_ptrace'' boolean, execute the following command as root:
+== Standardized Passphrase Policy  ==
+A common password policy is being utilized to provide a set of consistent rules for password policies. These rules can be modified locally to fit user needs.
-<code># setsebool -P deny_ptrace 1</code>
-To disable the protection provided by the ''deny_ptrace'' boolean temporarily, execute the following command as root:
-<code># setsebool deny_ptrace 0</code>
-<!-- https://fedoraproject.org/wiki/Features/SELinuxDenyPtrace -->
-== Services Private /tmp ==
-A number of services managed by ''systemd'' have been modified to make use of its ability to provide them with a private ''/tmp'' directory. Privileged services using ''/tmp'' and ''/var/tmp'' have previously been found to be open to being interfered with by unprivileged users, potentially leading to privilege escalation. Using private ''/tmp'' directories for services prevents this style of exploit.
-The directive added to the ''systemd'' unit files for the modified services is:
-<pre>[Service]
-PrivateTmp=true</pre>
-<!-- http://fedoraproject.org/wiki/Features/ServicesPrivateTmp -->
-== Secure Containers ==
-A new tool, ''sandbox'', has been created to streamline creation of secure ''libvirt'' containers. When provided with an executable ''sandbox'' determines the mount points  and ''libvirt'' container information required to run the application in a container. The container is then launched by ''libvirt'' with an SELinux context that will prevent it interacting with other processes on the system, including other containers, while still being able to share system data.
-This allows an administrator to run multiple instances of a service simultaneously, while preventing them from breaking the host machine or other processes on the system, even when run as ''root''. To use ''sandboxcontainer'', install the ''libvirt-sandbox'' package.
-<!-- http://fedoraproject.org/wiki/Features/Securecontainers -->
-[[Category:Docs Project]]
-[[Category:Draft documentation]]
-[[Category:Documentation beats]]

Search