ProHoster > Blog > internet news > Fedora 33 release

Fedora 33 release


Fedora 33 release

Today, October 27, Fedora 33 was released.

There are a variety of options for installation: the already classic Fedora
Workstation and Fedora Server, Fedora for ARM, new edition of Fedora IoT, Fedora
Silverblue, Fedora Core OS and many Fedora Spins options with software selections for
solving specialized problems.

Installation images are published on the website https://getfedora.org/. There you are
You can find recommendations and instructions for installing the appropriate option.

What's new?

The full list of changes is extensive and is available on the page:
https://fedoraproject.org/wiki/Releases/33/ChangeSet (English)

However, it is worth mentioning a few of the most noticeable changes:

  • BTRFS! In the new release of BTRFS
    is selected as the system default for Fedora Workstation. Compared with
    previous implementation attempts, much was improved and corrected in that
    including with the help of Facebook engineers who shared their considerable experience
    using BTRFS on β€œcombat” servers.

  • dwarf Many expected it, and many opposed it, but it happened: nano becomes the default console text editor in Fedora Workstation.

  • LTO Most packages were assembled using technology
    interprocedural optimizations
    (LTO)    ,
    which should give an increase in performance.

  • Strong cryptography Stricter policies have been established for cryptography,
    in particular, a number of weak ciphers and hashes (for example MD5, SHA1) are prohibited. This
    The change may make it more difficult to work with legacy servers using old ones
    and insecure algorithms. It is recommended to update these systems as soon as possible
    to supported versions.

  • systemd-resolved Now available as a system DNS resolver
    systemd-resolved, which supports features such as DNS caching,
    use of different resolvers for different connections, and also supports
    DNS-over-TLS (DNS encryption was disabled by default until Fedora 34, but
    can be enabled manually).

Known Issues

  • Canonical recently updated the keys for Secure Boot in
    Ubuntu, without harmonizing it with other distributions. In this regard, loading
    Fedora 33 or any other distribution with Secure Boot enabled on
    system with Ubuntu installed may result in an ACCESS DENIED error. The update has already been rolled back in Ubuntu, but you may still face its consequences.

    To solve the problem, you can reset the Secure Boot signing keys using the UEFI BIOS.

    Details Common Bugs.

  • There is a known issue with re-logging into KDE. It occurs if the input
    and logout occurs multiple times in too short a time
    time, see Details.

Russian language support

Source: linux.org.ru