Language Selection

English French German Italian Portuguese Spanish

Linux 4.16 Now in Release Candidate Mode

Filed under
Linux
  • Linux 4.16-rc1

    Two weeks have passed, -rc1 is out there, and the merge window is thus over.

    I don't want to jinx anything, but things certainly look a lot better
    than with 4.15. We have no (known) nasty surprises pending, and there
    were no huge issues during the merge window. Fingers crossed that this
    stays fairly calm and sane.

    As usual, I'm only appending my mergelog, because while this is not
    shaping up to be a particularly huge release, none of our recent
    releases have been small enough to describe with the shortlogs I use
    for later rc's.

    The actual diff is dominated by drivers, and once again the GPU
    patches stand out - this time some AMD GPU header files. Happily, this
    time the bulk of those lines is actually *removal* due to cleanups and
    getting rid of some unused headers.

    But there really is changes all over. Drivers may be the bulk (GPU,
    networking, staging, media, sound, infiniband, scsi and misc smaller
    subsystems), but we have a fair amount of arch updates (spectre and
    meltdown fixes for non-x86 architectures, but also some further x86
    work, and just general arch updates). And there's networking,
    filesystem updates, documentation, tooling..

    There's a little bit for everybody, in other words.

    Go out and test,

    Linus

  • Linux 4.16-rc1 Kernel Released With Many Changes

    Just like clockwork, the first release candidate of Linux 4.16 is now available.

    Linux 4.16-rc1 was tagged just minutes ago and remains under the "Fearless Coyote" codename that has been happening for several cycles now. Over the Linux v4.15 stable release, the Linux 4.16 merge window up to RC1 brings 11340 files changed, 491295 insertions(+), 305085 deletions(-). Yes, that's another hearty merge window.

    To learn about all of the changes for this next kernel version, see my thorough Linux 4.16 feature overview that I finished up this morning. Linux 4.16 is bringing a lot more work on Spectre/Meltdown mitigation, AMDGPU DC multi-display synchronization, better Intel Cannonlake support, VirtualBox Guest Driver is now mainline, many CPU/scalability improvements, AMD SEV encrypted virtualization support for KVM, file-system improvements, new ARM board support, and a wide range of other improvements as outlined in the aforelinked article.

  • A Look At The Plethora Of Linux 4.16 Kernel Features & Changes

    After the lengthy Linux 4.15 kernel cycle, the past two weeks have marked the Linux 4.16 merge window. Yet again it's been another heavy feature period for the kernel. There is still a lot of mitigation work going on for most CPU architectures surrounding Spectre and also Meltdown, the open-source graphics drivers have continued getting better, various CPU improvements are present, the VirtualBox Guest driver was mainlined, and dozens of other notable changes for Linux 4.16. Take a look.

    Here's our usual kernel feature overview from our original reporting the past two weeks in closely monitoring the Linux kernel mailing list and Git repository. Linus Torvalds is expected to mark the end of the merge window today by releasing Linux 4.16-rc1.

More in Tux Machines

Browsing the web with Min, a minimalist open source web browser

Does the world need another web browser? Even though the days of having a multiplicity of browsers to choose from are long gone, there still are folks out there developing new applications that help us use the web. One of those new-fangled browsers is Min. As its name suggests (well, suggests to me, anyway), Min is a minimalist browser. That doesn't mean it's deficient in any significant way, and its open source, Apache 2.0 license piques my interest. Read more

Security: Patches, FUD and Voting Machines

  • libssh 0.8.4 and 0.7.6 security and bugfix release

    libssh versions 0.6 and above have an authentication bypass vulnerability in the server code. By presenting the server an SSH2_MSG_USERAUTH_SUCCESS message in place of the SSH2_MSG_USERAUTH_REQUEST message which the server would expect to initiate authentication, the attacker could successfully authentciate without any credentials.

  • A Cybersecurity Weak Link: Linux and IoT [Ed: Blaming "Linux" for companies that put default passwords on all their products? Windows has back doors.]
  • Undetectably bypass voting machines' anti-tamper mechanism with a bit of a soda-can

    But University of Michigan grad student Matt Bernhard has demonstrated that he can bypass the tamper-evident seals in seconds, using a shim made from a slice of a soda can. The bypass is undetectable and doesn't damage the seal, which can be resecured after an attacker gains access to the system.

  • Security Seals Used to Protect Voting Machines Can Be Easily Opened With Shim Crafted from a Soda Can

    Bernhard, who is an expert witness for election integrity activists in a lawsuit filed in Georgia to force officials to get rid of paperless voting machines used in that state, said the issue of security ties and seals came up in the lawsuit earlier this year when Fulton County Elections Director Richard Barron told the court that his Georgia county relies on tamper-evident metal and plastic ties to seal voting machines and prevent anyone with physical access to the machines from subverting them while they sit in polling places days before an election.

    [...]

    He noted that defeating ties and seals in non-tamper-evident ways isn’t the only method to wreak havoc on an election in Michigan. The state has a unique law that prohibits ballots from being used in a recount if the number of voters doesn't match the number of ballots cast at a precinct or if the seal on a ballot box is broken or has a different serial number than what it should have. Someone who wanted to wreak havoc on an election or alter an election outcome in Michigan could purposely tamper with ballot box seals in a way that is evident or simply replace them with a seal bearing a different serial number in order to get ballots excluded from a recount. The law came into sharp relief after the 2016 presidential election when Green Party candidate Jill Stein sought to get a statewide recount in Michigan and two other critical swing states and found that some precincts in Wayne County couldn't be recounted because the number of voters who signed the poll books—which get certified with a seal signed by officials—didn't match the number of ballots scanned on the voting machines.

OSS: Hedera Hashgraph, Service Providers, and Renaming the Bro Project

  • Hedera Hashgraph Distributed Ledger Technology Shares New Open-Source SDK [Ed: Hedera needs to delete GitHub, however, as the new head of GitHub killed Java projects like Hedera's]
    Hedera Hashgraph, one of the DApp facilitators within the blockchain industry recently announced that it has released its Software Development Kit (SDK) in Java.
  • Service Providers Should Adapt to Open Source World
    Finding differing opinions on open source with the telecom industry isn't hard to do, especially where orchestration is concerned. That's why a panel discussion on open source and MANO at the Light Reading NFV-Carrier SDN event in Denver seemed an odd place to find such outspoken agreement on that topic, but there it was. Four smart guys, none shy with their opinions, all seemed to agree on key points around open source, the need for standards, the role of vendors and the lack of internal software skills. But they also agreed that telecom service providers are struggling a bit to understand how to proceed in an open source world and still need some fundamental internal changes.
  • Renaming the Bro Project
    More than 20 years ago I chose the name "Bro" as "an Orwellian reminder that monitoring comes hand in hand with the potential for privacy violations", as the original Bro paper put it. Today that warning is needed more than ever ... but it's clear that now the name "Bro" is alas much more of a distraction than a reminder. On the Leadership Team of the Bro Project, we heard clear concerns from the Bro community that the name "Bro" has taken on strongly negative connotations, such as "Bro culture". These send a sharp, anti-inclusive - and wholly unintended and undesirable - message to those who might use Bro. The problems were significant enough that during BroCon community sessions, several people have mentioned substantial difficulties in getting their upper management to even consider using open-source software with such a seemingly ill-chosen, off-putting name.

Back End: Apache Kafka, 'Serverless'