|
|
Log in / Subscribe / Register

Distributions

What's coming in Fedora 23

By Jonathan Corbet
August 12, 2015
The Fedora 23 schedule calls for an alpha release on August 11, followed, eventually, by the final release on October 27. It is traditional for Fedora schedules to slip, but that hasn't happened yet — Fedora 23 alpha came out right on schedule. As usual, a lot has been happening in the Fedora community; here we'll look at some of the highlights from this development cycle.

Security-related changes

There are a few security-oriented changes in this release; the first of them is a one-line change, but it has a wide impact. The RPM build rules have been tweaked to cause all packages to be built as position-independent code. That allows address-space layout randomization to be performed when the resulting binaries are executed, making those programs more resistant to canned exploit attempts. Position-independent builds have been recommended for some time, but many packagers did not follow that recommendation; the new build flags are a way of strengthening that recommendation.

There were some concerns about runtime performance penalties associated with this change, but that does not appear to be a real issue. The benefit remains to be seen; the feature page optimistically suggests that "Fedora users might notice less successful attacks on their systems", but, unless the current security situation is far worse than the Fedora community has let on, that's the one thing users are highly likely not to notice.

Another simple change disables the use of the SSL3 protocol and RC4 cipher in the GnuTLS and OpenSSL libraries. Hopefully there are few systems out there using these obsolete and insecure features; those that are will not work properly under Fedora 23 and should be updated.

Finally, and most controversially, the distribution will have a new standardized password policy. The password-strength issue came up earlier this year, when the Anaconda installer started requiring "strong" passwords to be set during the installation phase. The Fedora developers backed off in response to the ensuing outcry and started on the task of figuring out what the password policy should be. Now we are seeing the results of that work.

Technically, the new scheme does not require strong passwords; instead, it puts in place a mechanism for describing requirements on passwords so that every application that deals with them applies the same policy. The actual policy decisions are left to the various working groups. There is a default policy, though; it requires at least eight characters and a passing score from libpwquality. That is the same requirement as the one that caused a fuss back in January.

The Workstation group is in charge of the desktop version of the distribution, so its policies are likely to be especially visible to a broad range of Fedora users. This group has, as announced by Michael Catanzaro, begun to establish a policy that will differ somewhat from the default. In particular, while the quality requirements will not go away altogether, it looks like they will be weakened a bit. The guiding philosophy is:

In Fedora Workstation, we expect passwords to be used to provide good security against nontechnical human beings with physical access to the computer, physically typing away at the keyboard. By default, they aren't intended to protect against sophisticated adversaries. We therefore want to allow users to set much weaker passwords than are currently permitted by libpwquality, since longer passwords don't provide any practical benefit to most of our users.

So the length requirement may be shortened, and the libpwquality check may be disabled entirely. There is talk of somehow requiring stronger passwords before the SSH service can be turned on, but it is not clear what the requirements would be or how they would be enforced. As Michael notes: "Keep in mind that we've established that pwquality is not very good at rating password strength" — not exactly a ringing endorsement.

What the other Fedora flavors will do regarding passwords is not yet entirely clear.

Other changes of note

One change that is likely to be visible to many Fedora users is the shift to Python 3 as the default version of the Python language. That means that, if a shipped Fedora release only has one version of Python, it will be Python 3; Python 2 will be an add-on if needed. The plan calls for the Workstation release, among others, to have Python 3 as the only Python interpreter. For that to happen, all Python-using applications shipped with the distribution should use Python 3; requiring Python 2 is seen as a bug (albeit one that cannot yet be fixed for many important applications). Python 2 will remain available, of course, and, if /usr/bin/python exists, it will point to Python 2. Support for the older version of the language will not be going away anytime soon, but the focus is slowly shifting to Python 3.

The Python shift was one of the driving forces behind the DNF package manager; it works with Python 3, while Yum does not. In Fedora 23, DNF will gain the ability to perform full system upgrades, absorbing the "Fedup" tool in the process. DNF has had a few teething problems, so the prospect of using it for system upgrades may be unnerving for some, but, in your editor's experience, the tool seems to be solid and is getting better.

Project Atomic is an effort to create an operating system for containerized applications. Fedora has supported this effort via the "Fedora Atomic Host" variant of the distribution for the last year, but there is a problem: the six-month Fedora release cycle is far too slow for the fast-moving Atomic project. So, perhaps even before the Fedora 23 release is out, the Fedora project will start making Atomic releases every two weeks. At some point, the Atomic releases might become the primary product from the Cloud working group, but Atomic is apparently too fast-moving and focused for that now. This release probably will become the base upon which the Atomic project does its development work.

There will also be a new version of Fedora built as a layered image for Docker deployments.

Fans of the Cinnamon desktop environment will be glad to see that, with Fedora 23, there will be a separate spin that sets up Cinnamon from the outset. The Unicode 8 standard will be supported, bringing the latest in emoji (and more) to Fedora users. Work continues on getting Wayland ready for use, but it will not be replacing X11 in this release. Almost everything else in the distribution will be updated, as is usual with Fedora.

To summarize: the Fedora developers have been busy in this development cycle. Fedora 23 appears to be another in a long series of releases adding interesting new functionality and, for better or for worse, pushing users toward more secure practices. For the next couple of months, the project will be looking for users to test this release and report bugs so that they can be fixed. Should the project surprise us all and not slip its schedule, Fedora 23 final will be ready at the end of October.

Comments (11 posted)

Brief items

Distribution quote of the week

It's software -- it's all broke... we just don't know exactly how yet. :)
-- Matthew Miller

Comments (none posted)

CentOS Linux 6.7 released

CentOS Linux 6.7 has been released for x86 and x86_64. "There are many fundamental changes in this release, compared with the past CentOS Linux 6 releases, and we highly recommend everyone study the upstream Release Notes as well as the upstream Technical Notes about the changes and how they might impact your installation. (See the 'Further Reading' section of the CentOS release notes)."

Full Story (comments: none)

FreedomBox 0.5 Released

FreedomBox is a "community project to develop, design and promote personal servers running free software for private, personal, communications". Version 0.5 has been released. See the release notes for details.

Full Story (comments: 1)

Kali Linux 2.0 released

Kali Linux is a Debian-based distribution oriented toward penetration testing and related tasks; the 2.0 release is now available. "There’s a new 4.0 kernel, now based on Debian Jessie, improved hardware and wireless driver coverage, support for a variety of Desktop Environments (gnome, kde, xfce, mate, e17, lxde, i3wm), updated desktop environment and tools – and the list goes on. But these bulletpoint items are essentially a side effect of the real changes that have taken place in our development backend. Ready to hear the real news? Take a deep breath, it’s a long list." At the top of that list is that Kali is now a rolling distribution.

Comments (3 posted)

Ubuntu 14.04.3 LTS released

The third update to the 14.04 Long Term Support release is available for Desktop, Server, Cloud, and Core products, as well as other flavors of Ubuntu with long-term support. "We have expanded our hardware enablement offering since 12.04, and with 14.04.3, this point release contains an updated kernel and X stack for new installations to support new hardware across all our supported architectures, not just x86."

Full Story (comments: none)

Distribution News

CentOS

New CentOS releases

CentOS has released the live CD/DVD of CentOS 6.7. "The CentOS-6.7 LiveDVD and LiveCD are meant to be a Linux environment suited to be run directly from either Optical media or USB storage devices. It does not need any persistent storage on a machine, which also makes it a suitable recovery environment."

CentOS 7-1507 has also been released. "The rolling builds are a point in time snapshot of a given CentOS version including all updates on mirror.centos.org. This includes all all security, bugfix, enhancement and general updates for CentOS Linux, in this case they include updates up to and including July 28th, 2015."

Comments (none posted)

Debian GNU/Linux

Bits from the Debian Installer release manager

Cyril Brulebois has a few bits about the Debian "Stretch" installer. "Many components are used to build the installer, but some of them are not specific to it (e.g. cairo, libx11, xorg-server); they just happen to build one or more udeb packages (packages to be used within the installer). Since the release process of the installer usually takes some days to get everything ready, it is both possible and likely to have a few such packages migrating to testing while details are being polished. Such updates sometimes cause behavorial changes or even regressions. While those are being documented/fixed, some more packages can be sneaking into testing, causing more surprises, and longer cycles. That's why I'm going to use “block-udeb” hints to prevent the migration of all udeb-producing packages during the final preparation of the installer releases."

Full Story (comments: none)

Newsletters and articles of interest

Page editor: Rebecca Sobol
Next page: Development>>


Copyright © 2015, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds