Documentation Security Beat

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(openssh)
 
(26 intermediate revisions by 9 users not shown)
Line 1: Line 1:
{{header|docs}}
+
{{header|docs}}{{Docs_beat_open}}
  
== Active Directory made easy ==
+
== Disable SSL 3.0 and RC4 ==
=== GNOME gets along with AD ===
+
Fedora should be able to be used on an Active Directory domain (or other kerberos realms, such as IPA) out of the box. It should be easy to configure domain logins on a Fedora machine, and then it should be intuitive and uneventful to login with those credentials.
+
  
These improvements will also increase reliability and ease usage for any Kerberos realm, not just active directory. Improvement has been made in much of the login and authentication stack, which now includes realmd and adcli.  
+
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.
  
The GNOME "User Accounts" Settings GUI features support for enterprise logins.
+
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.
  
=== IPA improves AD Support ===
+
'''Note (Use note tag)''' - All applications that use TLS from NSS are not affected by this change.
With Fedora 18 it would be possible to create a trust relationship between an IPA and an Active Directory domain which would allow users from one domain to access resource of the other domain. The FreeIPA project has documented the feature at http://freeipa.org/page/IPAv3_testing_AD_trust.
+
  
== Secure Boot ==
+
== 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
  
UEFI Secure Boot will be supported in Fedora 18. This will allow Fedora to boot on systems that have Secure Boot enabled. Tools are available for administrators to create custom certificates to sign local changes to GRUB or the kernel.
+
== 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.
  
== rngd ==
+
== 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.  
Random number generation is improved by enabling rngd by default.
+
 
+
== Secure Containers ==
+
 
+
Using SELinux and '''virt-sandbox''', services can be run in secure sandboxes, even as root. The '''virt-sandbox-service''' package will create mount points and a libvirt container.
+
 
+
== SELinux boolean renaming ==
+
 
+
In order to clarify the purpose of SELinux booleans, all settings that begin with "allow" will be renamed to reflect their domain. Existing policy booleans will continue to be supported.
+
 
+
== SELinux Systemd Access Control ==
+
 
+
Support has been added to '''systemd''' to check unit files against SELinux settings before allowing a process to start or stop the service.
+
 
+
== System calls restricted ==
+
` The libseccomp library is now available, which provides applications with an easy way to reduce the potential damage of exploits, leveraging kernel syscall filters. Virtual machines benefit from this as QEMU/KVM now uses libseccomp.
+
 
+
 
+
== usermode ==
+
 
+
'''usermode''', a wrapper to provide superuser privileges to unprivileged users, is being phased out in favor of '''polkit'''.
+
 
+
== Kerberos credentials moved and improved ==
+
Fedora 18 changes the standard location of Kerberos credential caches to /run/user/$UID in order to increase security and simplify locating the caches for NFSv4.
+
Fedora's Kerberos support will now allow users to maintain credentials for multiple identities and for the GSSAPI client code to automatically select credentials based on the target service and hostname.
+
 
+
== halt, poweroff, reboot Configuration Moved ==
+
The ability to use halt(8), poweroff(8) and reboot(8) commands by unprivileged users is now controlled using <code>polkit</code>, see the actions in <code>/usr/share/polkit-1/actions/org.freedesktop.login1.policy</code> .  The PAM configuration files <code>/etc/pam.d/{halt,poweroff,reboot}</code> are no longer used and their content, if any, is ignored.
+
  
  

Latest revision as of 02:59, 28 August 2015

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


Contents

[edit] 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.

[edit] 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

[edit] 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.

[edit] 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.