Documentation Security Beat: Difference between revisions

Revision as of 07:03, 4 June 2014

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>

@@ Line 1: / Line 1: @@
-{{header|docs}}
+{{header|docs}}{{Docs_beat_open}}
-== firewalld ==
+<title>Crypto Policy</title>
-Fedora 18 uses '''firewalld''' instead of '''iptables''' as the default firewall service. Using '''firewalld''' will allow for changes to be made to policy without restarting the service. In addition, current status and changes will be available via D-Bus. This improves support for dynamic environments like libvirtd.
+<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>
-== Secure Boot ==
+<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>
-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.
+<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>
-== rngd ==
-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.
-== usermode ==
-'''usermode''', a wrapper to provide superuser privileges to unprivileged users, is being phased out in favor of '''polkit'''.
-== 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.
 [[Category:Docs Project]]
 [[Category:Draft documentation]]
 [[Category:Documentation beats]]

Search

Documentation Security Beat: Difference between revisions

Revision as of 07:03, 4 June 2014