[$] Progress on no-GIL CPython

Back at the end of July, the Python steering council announced
its intention to approve the proposal to make the global interpreter lock
(GIL) optional over the next few Python releases. The details of that
acceptance are still being decided on, but work on the feature is
proceeding—in discussion form at least. Beyond that, though, there are
efforts underway to solve that hardest of problems in computer
science, naming, for the no-GIL version.

Source: LWN.net – [$] Progress on no-GIL CPython

Smooth Sailing and Continued Growth at All Things Open 2018

Between now and the opening of All Things Open 2023 on October 15, which will begin the conference’s second decade, FOSS Force is each day taking a look at an individual year in ATO’s history. In today’s article we’re looking at All Things Open 2018, which was the conference’s sixth outing.

The post Smooth Sailing and Continued Growth at All Things Open 2018 appeared first on FOSS Force.



Source: FOSS Force – Smooth Sailing and Continued Growth at All Things Open 2018

A remote code execution vulnerability in GNOME

The GitHub blog describes
a vulnerability in the libcue library
(which is used by the GNOME
desktop) that can be exploited by a remote attacker to run code on a
desktop system if the target can be convinced to click on a malicious link.

The video shows me clicking a link in a webpage, which causes a cue
sheet to be downloaded. Because the file is saved to ~/Downloads,
it is then automatically scanned by tracker-miners. And because it
has a .cue filename extension, tracker-miners uses libcue to parse
the file. The file exploits the vulnerability in libcue to gain
code execution and pop a calculator.



Source: LWN.net – A remote code execution vulnerability in GNOME

ATO 2017 – Comfortably In the Groove

Between now and the opening of All Things Open 2023 on October 15, which will begin the conference’s second decade, FOSS Force is each day taking a look at an individual year in ATO’s history. In today’s article we’re looking at All Things Open 2017, which was the conference’s fifth outing.

The post ATO 2017 – Comfortably In the Groove appeared first on FOSS Force.



Source: FOSS Force – ATO 2017 – Comfortably In the Groove

Incus 0.1 released

The Linux Containers project has
announced
the release version 0.1 of the Incus system container and
virtual-machine manager, which is a community-led fork of Canonical’s LXD. Incus 0.1 “is roughly
equivalent to LXD 5.18 but with a number of breaking changes on top of the
obvious rename
“. There have been some changes made in the two months
since the fork:

With this initial release of Incus, we took the opportunity to remove a lot
of unused or problematic features from LXD. Most of those changes are
things we would have liked to do in LXD but couldn’t due to having strong
guarantees around backward compatibility.

Incus will be similarly strict with backward compatibility in the future,
but as this is the first release of the fork, it was our one big
opportunity to change things.

That said, the API and CLI are still extremely close to what LXD has,
making it trivial if not completely seamless to port from LXD to Incus.

There is an online
version of Incus
for those interested in giving it a try.

Source: LWN.net – Incus 0.1 released

[$] Rethinking multi-grain timestamps

One of the significant features added to the mainline kernel during the 6.6
merge window was multi-grain timestamps, which allow the kernel to
selectively store file modification times with higher resolution without
hurting performance. Unfortunately, this feature also caused some
surprising regressions, and was quickly ushered back out of the kernel as a
result. It is instructive to look at how this feature went wrong, and how
the developers involved plan to move forward from here.

Source: LWN.net – [$] Rethinking multi-grain timestamps