|
|
| (26 intermediate revisions by 9 users not shown) |
| Line 1: |
Line 1: |
| {{header|docs}} | | {{header|docs}}{{Docs_beat_open}} |
|
| |
|
| = <span style="color:red;">Warning - Beat Converted</span> =
| | <title>Crypto Policy</title> |
| {{admon/warning| Beat has already been converted to XML|Be sure to set Wiki Good to '''*''' and In Publican to '''0''' if this beat is modified}}
| |
|
| |
|
| | <para>Beginning in Fedora 21, a system-wide crypto policy will be available for users to quickly setup the cryptographic options for their systems. Users that must meet certain cryptographic standards can make the policy change in <filename>//etc/crypto-policies/config</filename>, and run update-crypto-policies. At this point applications that utilize the default set of ciphers in the GnuTLS and OpenSSL libraries will follow the policy requirements.</para> |
|
| |
|
| == Password Quality Checking ==
| | <para>The available options are: (1) <literal>LEGACY</literal>, which ensures compatibility with legacy systems - 64-bit security, (2) <literal>DEFAULT</literal>, a reasonable default for today's standards - 80-bit security, and (3) <literal>FUTURE</literal>, a conservative level that is believed to withstand any near-term future attacks - 128-bit security. These levels affect SSL/TLS settings, including elliptic curve, signature hash functions, and ciphersuites and key sizes.</para> |
|
| |
|
| 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 /etc/security/pwquality.conf configuration file.
| | <para>Additional information on this new feature can be found on the <ulink url="https://fedoraproject.org/wiki/Changes/CryptoPolicy">CryptoPolicy Changes wiki page</ulink>.</para> |
|
| |
|
| Developers wishing to call this API from their applications will find the API description in the pwquality.h file provided by the ''libpwquality-devel'' package. A python wrapper, ''python-pwquality'', is also provided.
| |
|
| |
|
| |
| == SELinux Deny Ptrace ==
| |
|
| |
| 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''.
| |
|
| |
| 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:
| |
|
| |
| # setsebool -P deny_ptrace 1
| |
|
| |
| To disable the protection provided by the ''deny_ptrace'' boolean temporarily, execute the following command as root:
| |
|
| |
| # setsebool deny_ptrace 0
| |
|
| |
|
| |
| == 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:
| |
|
| |
| [Service]
| |
| PrivateTmp=true
| |
|
| |
|
| |
| == 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 ''sandbox'', install the ''libvirt-sandbox'' package.
| |
|
| |
|
| |
| === krb5-workstation ===
| |
|
| |
| Fedora 17 upgrades the Kerberos authentication system to version 1.10. This adds support for changing passwords over a NAT and support for localization. The kswitch command is added to switch between credential caches. Additional cache support has been added to other commands. Credential choice can be controlled with the file $HOME/.k5identity.
| |
|
| |
|
| [[Category:Docs Project]] | | [[Category:Docs Project]] |
| [[Category:Draft documentation]] | | [[Category:Draft documentation]] |
| [[Category:Documentation beats]] | | [[Category:Documentation beats]] |
Beat is open
This beat is now ready to have Fedora 25 content added by the beat writer
<title>Crypto Policy</title>
<para>Beginning in Fedora 21, a system-wide crypto policy will be available for users to quickly setup the cryptographic options for their systems. Users that must meet certain cryptographic standards can make the policy change in <filename>//etc/crypto-policies/config</filename>, and run update-crypto-policies. At this point applications that utilize the default set of ciphers in the GnuTLS and OpenSSL libraries will follow the policy requirements.</para>
<para>The available options are: (1) <literal>LEGACY</literal>, which ensures compatibility with legacy systems - 64-bit security, (2) <literal>DEFAULT</literal>, a reasonable default for today's standards - 80-bit security, and (3) <literal>FUTURE</literal>, a conservative level that is believed to withstand any near-term future attacks - 128-bit security. These levels affect SSL/TLS settings, including elliptic curve, signature hash functions, and ciphersuites and key sizes.</para>
<para>Additional information on this new feature can be found on the <ulink url="https://fedoraproject.org/wiki/Changes/CryptoPolicy">CryptoPolicy Changes wiki page</ulink>.</para>
