No edit summary |
Immanetize (talk | contribs) (openssh) |
||
| Line 8: | Line 8: | ||
'''Note (Use note tag)''' - All applications that use TLS from NSS are not affected by this change. | '''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 == | == Package Hardening == | ||
Revision as of 02:59, 28 August 2015
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.