Fedora 33 Release

Today, October 27, Fedora 33 was released.

Various options are available for installation: the classic Fedora
Workstation and Fedora Server, Fedora for ARM, the new edition of Fedora IoT, Fedora
Silverblue, Fedora Core OS, and numerous Fedora Spins with curated software for
addressing specialized tasks.

Installation images have been published on the website https://getfedora.org/. There you
can also find recommendations and instructions for installing the appropriate version.

What’s New?

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

However, it is worth mentioning several of the most notable changes:

• BTRFS! In this new release, BTRFS
  has been selected as the default filesystem for Fedora Workstation. Compared to
  previous attempts at implementation, many improvements have been made, thanks in part to
  engineers at Facebook who shared their significant experience
  in using BTRFS on 'production' servers.

• nano Many have been waiting for this, and many opposed it, but it has happened: the default console text editor in Fedora Workstation is now nano.

• LTO Most packages have been built using
  link-time optimization
  (LTO) which should provide a performance boost.,
  Strict cryptography

• More stringent policies have been established for cryptography, specifically prohibiting a number of weak ciphers and hashes (e.g., MD5, SHA1). This
  change may complicate operations with outdated servers using old
  and insecure algorithms. These systems are recommended to be updated as soon as possible
  to supported versions.
  The system DNS resolver is now

• systemd-resolved systemd-resolved, which supports functions such as DNS caching,
  the use of different resolvers for different connections, and also supports
  DNS-over-TLS (DNS encryption is disabled by default until Fedora 34, but
  can be enabled manually).
  Canonical recently updated keys for Secure Boot in

Known Issues

• Ubuntu, without coordinating with other distributions. As a result, booting
  Fedora 33 or any other distribution with Secure Boot enabled on
  a system with Ubuntu installed may lead to an ACCESS DENIED error. The update has already been reverted in Ubuntu, but you may still encounter its consequences.
  To resolve the issue, you can reset the Secure Boot signing keys using UEFI BIOS.

  Details can be found in

  Common Bugs Common Bugs.

• There is a known issue with logging back into KDE. It occurs when logging in and out of the system multiple times in a very short
  period, see
  . details.

Russian-speaking support

• Matrix chats: https://ru.fedoracommunity.org/stories/matrix/
• Telegram channel: https://t.me/russianfedora

Source: linux.org.ru