|
|
| (59 intermediate revisions by 13 users not shown) |
| Line 1: |
Line 1: |
| {{header|docs}} | | {{header|docs}}{{Docs_beat_open}} |
| {{Docs_beat_open}} | |
| {{Draft|
| |
| Pick up a sub-beat and sign your name}}
| |
|
| |
|
| | <title>Crypto Policy</title> |
|
| |
|
| {|- style="width: 40%; margin: auto;"
| | <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> |
| ! style="width: 70%;" |Toool || style="width: 10%; text-align: center;" | To do || Writer
| |
| |-
| |
| |style="text-align: left;" | [[Features/DynamicFirewall | Dynamic Firewall]] || yes || [[User:lewis41|Luigi Votta]]
| |
| |-
| |
| |style="text-align: left;"| [[Features/DNSSEC_on_workstations | DNSSEC on workstations]] || yes ||
| |
| |-
| |
| |style="text-align: left;" | [[Features/RemoveSETUID |Remove SETUID]] (for pkgs maintainers)|| yes/no ||
| |
| |-
| |
| |style="text-align: left;"| [http://0pointer.de/public/systemd-man/pam_systemd.html pam_systemd] (systemd related) ????? || yes/no ||
| |
| |-
| |
| |style="text-align: left;"| freeipa (F15) || yes ||
| |
| |-
| |
| |style="text-align: left;"| OpenSCAP (secstat, firstaidkit) || yes/no || [[User:lewis41|Luigi Votta]]
| |
| |-
| |
| |style="text-align: left;"| DogTag Certificate System (PKI-*) || yes/no ||
| |
| |-
| |
| |style="text-align: left;"| SELinux Enhancements || yes/no ||
| |
| |-
| |
| |style="text-align: left;"| polkit-qt || yes/no ||
| |
| |-
| |
| |style="text-align: left;"| sectool || yes/no ||
| |
| |-
| |
| |style="text-align: left;"| dnssec-tools & dnssec-config || yes/no ||
| |
| |-
| |
| |}
| |
|
| |
|
| = Security =
| | <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> |
| This section describes the security changes and enhancements available in Fedora 15.
| |
|
| |
|
| == Dynamic Firewall ==
| | <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> |
| Fedora 15 adds support for the optional firewall daemon (FirewallD), providing a dynamic firewall management with a D-Bus interface.
| |
| | |
| The previous firewall model with system-config-firewall, was static and required a full firewall restart for all changes, even simple ones. The dynamic firewall mode, makes it possible to change firewall settings without the need to restart the firewall for persistent connections. At this stage, it supports iptables, ip6table and ebtables. In Fedora 15 a simple tray applet shows the firewall state, enabling/disabling firewall services
| |
| | |
| For more details, consult the Fedora wiki pages, [[Features/DynamicFirewall | Fedora 15: Dynamic Firewall]] and [[FirewallD/ | FirewallD]].
| |
| | |
| | |
| == DNSSEC on workstations ==
| |
| In Fedora 15 comes in a new security feature that protects the end users and their workstations exposition against various DNS spoofing and DNS cache-poisoning attacks.
| |
| | |
| '''DNSSEC''' is an environment full tested in Fedora, as all major DNS servers in Fedora run with '''DNSSEC''' validation enabled by default since Fedora 11, giving to the Fedora Project a lot of experience from server environment. '''DNSSEC''' is aimed to secure all DNS traffic. <code>NetworkManager</code> uses the BIND nameserver as a DNSSEC resolver and all received DNS responses are proved to be correct. In case a particular domain is signed and failed to validate then resolver returns SERFVAIL instead of invalidated response, which means something is wrong.
| |
| | |
| For all details view [[Features/DNSSEC_on_workstations | DNSSEC on workstations]] om the Fedora wiki.
| |
| | |
| == OpenSCAP ==
| |
| First introduced in Fedora 14, OpenSCAP is a set of open source libraries providing an easier path for integration of the SCAP line of standards, managed by NIST and created to provide a standardized approach to maintaining the security of enterprise systems, such as automatically verifying the presence of patches, checking system security configuration settings, and examining systems for signs of compromise.
| |
| | |
| In Fedora 15, '''openscap''', the set of open source libraries enabling integration of the SCAP line of standards, has been upgraded from version 0.6.3 to 0.6.8. During these development stage there has been introduced full support for perl regular expression by default, OVAL float type support, XSL transformation improvements and Dublin Core support, added OVAL schemas version 5.6 and improved XCCDF reporting.
| |
| | |
| '''secstate''', the Security State Configuration Tool, has been rebuilt in Fedora 15 against version 0.4.1.
| |
|
| |
| '''firstaidkit''', the System Rescue Tool that automates simple and common system recovery tasks, has been upgraded from 0.2.17 to version 0.2.18.
| |
| | |
| For more informations visit [http://www.open-scap.org/page/Main_Page http://www.open-scap.org/page/Main_Page].
| |
|
| |
|
|
| |
|
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>
