Kernel prepatch 7.4-rc2

Post Syndicated from jake original https://lwn.net/Articles/1106300/

Linus Torvalds has released the 7.4-rc2
prepatch
and it will come as no surprise that it is a large one (“a
big -rc2 to go with the largest ever -rc1
“). Much of the size was made
up of some automated Coccinelle updates that were spread out all over the
tree; once those are factored out, the rest looks fairly normal:

When masking that noise out from the diffstat, the shape of it changes
– not spread out over thousands of files any more. But it does not
look unusual: a third is drivers (gpu, networking and sound account
for most of it, but there’s a bit of everything), another third is
networking and bpf, and the final third is “the rest” (mostly
filesystems, mm, arch updates).

And yes, much of this was driven by various AI fixes. I think I’ll
stop repeating that, and we can just take it for granted. But this
time around Alexei [Starovoitov] claims that on the bpf side at least the fixes are
now coming in faster than the new reports, and that sounds lovely if
true.

OpenIndiana 2026.10 released

Post Syndicated from jzb original https://lwn.net/Articles/1106285/

Version
2026.10
of the OpenIndiana operating
system has been released. OpenIndiana is based on Illumos, which in turn was
based on OpenSolaris
after Oracle discontinued it.

Notable changes in this release include UEFI framebuffer support for the live
image, updates to many applications and development tools, as well as the
inclusion of new applications such as TeX Live 2026, the Foliate ebook reader,
and more.

Защита на децата от рисковете на социалните мрежи

Post Syndicated from Bozho original https://blog.bozho.net/blog/4638

В цялата Европа се обсъжда решаването на проблема с вредното влияние на социалните мрежи върху децата. За съжаление, подходът, който са избрали от Европейската комисия, не е най-подходящия – проверка на възрастта.

Ние внесохме законопроект с друг подход – използване на приложения за родителски контрол. И вчера говорих на тази тема на OpenFest. Прилагам слайдовете тук:

Също така изпратих писмо на Европейската комисия, с което критикувам подхода с проверка на възрастта и предлагам алтернативния подход:

Материалът Защита на децата от рисковете на социалните мрежи е публикуван за пръв път на БЛОГодаря.

Security updates for Monday

Post Syndicated from jzb original https://lwn.net/Articles/1106282/

Security updates have been issued by Debian (cjose, kernel, libreoffice, rsync, ruby3.3, telegram-desktop, vim, and zlib), Fedora (bind, composer, copyparty, dnf5, elixir, fasterxml-oss-parent, gnome-remote-desktop, goose, jackson-annotations, jackson-bom, jackson-core, jackson-databind, jackson-jaxrs-providers, jackson-modules-base, jackson-parent, java-21-openjdk, java-21-openjdk-portable, jupyterlab, kryoptic, luksmeta, mingw-cfitsio, mingw-expat, mingw-freetype, mingw-glib-networking, mingw-harfbuzz, mingw-qt5-qtbase, mingw-qt5-qtdeclarative, mingw-qt5-qtwebkit, mingw-qt6-qtbase, mtools, NetworkManager-l2tp, nginx, nginx-mod-brotli, nginx-mod-fancyindex, nginx-mod-headers-more, nginx-mod-js-challenge, nginx-mod-modsecurity, nginx-mod-naxsi, nginx-mod-vts, nodejs-pnpm12, pcre2, perl-Spreadsheet-XLSX, pie, python-boto3, python-botocore, python-joserfc, python-jupyter-builder, python-jupyterlab-server, python-jupytext, python-nbdime, python-notebook, python-s3transfer, python3.12, rccl, rsync, rust-blake2b_simd, rust-blake3, rust-constant_time_eq, rust-lzma-rust2, rust-ppmd-rust, rust-regorus, rust-sccache, rust-totp-rs, rust-typed-path, rust-zip, rust-zip0.6, rust-zip2, sofia-sip, suricata, wordpress, and xen), Mageia (gimp, python-gitpython, and suricata), Red Hat (osbuild-composer), Slackware (httpd), SUSE (bind, brotli, ca-certificates-mozilla, chromedriver, containerized-data-importer1.65-api, corepack24, docker-compose, flatpak, fuse-overlayfs, git-lfs, gitoxide, go1.27, google-cloud-sap-agent, google-guest-agent, gotosocial, kubevirt1.8, kubevirt1.8-container-disk, kubevirt1.9-container-disk, libmariadbd-devel, libntpc1, libopenscap33, libsndfile-devel, libspice-server-devel, libtirpc-devel, matomo, mihomo, mozilla-nss, nano, nmap, nodejs22, perl-Mozilla-CA, python-Brotli, python-CairoSVG, python-certifi, python313-Pillow, rsyslog, stgit, and thunderbird), and Ubuntu (python-tornado).

Launching the Vite Ecosystem Fund

Post Syndicated from Michael Dong original https://blog.cloudflare.com/launching-vite-ecosystem-fund/

Cloudflare is distributing the first $301,300 of the Vite Ecosystem Fund to 44 projects and maintainers across the Vite ecosystem.

When VoidZero joined Cloudflare, we committed $1 million to strengthen the open source ecosystem around Vite. This round is just the start.

Sponsoring open source has always mattered, but now AI has made funding urgent.

AI is changing open source

AI has made open source more valuable while triggering more maintainer burnout. Previously, contributing to a project through either an issue or pull request meant you cared about it. In return, maintainers would review and provide feedback. AI changed the social contract of open source. Anyone can now create and submit AI-authored pull requests.

The most visible result is the influx of pull requests. As the number of PRs has gone up, the number of maintainers reviewing them has stayed constant. So each maintainer’s workload has grown.

During reviews, maintainers often find themselves speaking with an agent and not a person like they used to. If that’s the case, then why not cut out the middleman? Maintainers now have their own agents they can prompt to produce better results since they have more knowledge of the codebase.

AI has raised the pressure to produce. It’s made it easier for maintainers to ship features, performance improvements, and bug fixes that would not have been done otherwise. But it’s also made it easy for other projects to do the same. When another project adds overlapping features using AI, maintainers feel a need to keep up using AI. It can become a grinding cycle, where each project pushes the other to move faster. Along the way, some projects have grown in scope and lost sight of their original goals.

Maintainer burnout and sustainability have always been a problem — and now AI has accelerated those issues. That’s why sponsoring open source projects and supporting maintainers is so important in this moment.

One of the Vite Ecosystem Fund’s first recipients is e18e, a community focused on improving performance across the JavaScript ecosystem. Its lead, James Garbutt, has a long history in open source, and his work at e18e has helped make popular tools like Svelte, Storybook, and Nx faster. "Sponsorships make a huge difference and allow maintainers to dedicate more of their time to the things we all rely on," Garbutt says.

Fund distribution

The recipients of the Vite Ecosystem Fund were selected by a panel of core team members from Vite stack projects (Vite, Vitest, Rolldown, Oxc, Vite+), including maintainers not employed by Cloudflare.

The funding is allocated through Cloudflare's Open Collective as a combination of:

  • Contributions to ecosystem recipients
  • Stipends to core maintainers

We’re proud that Cloudflare has committed to making the open source ecosystem we rely on stronger and more sustainable. No project thrives in isolation.

We'll continue to distribute and draw down the committed amount every quarter.

Contributions to ecosystem recipients

This first round of sponsorships prioritized dependencies, ecosystem critical plugins, significant contributors, and projects that moved the ecosystem forward.

Andrew Gallant

Andrey Sitnik

Anthony Fu Fund

Ari Perkkiö

Artem Zakharchenko

Babel

Bart Waardenburg

Benjamin E. Coe

Brandon Roberts

Chai

David Ortner

David Tolnay

Denis Bardadym

Devon Govett

Divyansh Singh

e18e

ESlint

Giorgio Boa

Guy Bedford

Jessica Sachs

Jonas Kruckenberg

Luigi Pinca

Máximo Mussini

Michael Cousins

Mickael Jeanroy

Misha Kaletsky

Mock Service Worker

Mohammad Bagher Abiyat

Nicholas Rayburn

Paul Miller

Pig Fang

pnpm

Polka

PostCSS

Prettier

Ralf Jung

Rollup

Sindre Sorhus

Terser

typescript-eslint

Verite

universal-deploy (Vike)

Younes Jaaidi

Yuki Okushi

Stipends to core maintainers

The core maintainers of the Vite stack are eligible for a stipend of up to $4,000 per calendar month. Each maintainer can invoice at a rate of $50 per hour contributed that month.

Any time spent improving or supporting the project in some way counts towards this stipend: writing code, writing documentation, triaging issues, offering support in our Discord servers, attending meetings or meetups, contributing to our upstream dependencies, and so on.

Maintainers who are already being paid for or employed for this work do not receive stipends — for example, VoidZero employees are ineligible.

Cloudflare supports open source

Cloudflare’s mission is to help build a better Internet. Supporting open source falls squarely within that mission. The Vite Ecosystem Fund is only part of it.

Cloudflare committed an additional $1 million to sponsor open source projects in our Community Engineers Fund. We also provide Cloudflare credits to open source projects via Project Alexandria.

The Vite ecosystem has come this far because of all the maintainers and contributors who came together to build a community. These sponsorships are a small thank-you for all this hard work.

Letter To The European Commission About Age Verification And Social Networks

Post Syndicated from Bozho original https://techblog.bozho.net/letter-to-the-european-commission-about-age-verification-and-social-networks/

My previous post here in August was about the age verification plans of the European Commission. Since then the EC has proposed the EU KIDS Act, which implements the idea of age verification.

Yesterday I presented the alternative approach – heavily relying on parental control apps – on the OpenFest conference. Apart from proposing a local legislation in Bulgarian parliament, I’ve sent a letter the the European Commission. You can find it here. The text is as follows:


Dear President von der Leyen,
Dear Executive Vice-President Virkkunen,

Subject: The right approach to protecting children from the negative effects of social media

I’m writing this letter as a member of parliament from Bulgaria, as a former minister for digital transformation, as a technical expert and as a father.

Protecting children online has become a priority for the European Commission and for many EU governments, and rightly so. The threats online, the negative psychological effects of addictive designs and the algorithms that prioritize virality over quality have significant negative effects on children.

The European Commission has started addressing the addictive design problem, analyzes algorithmic bias and has undertaken an age verification initiative, in addition to long-term measures against CSAM, online crimes against children, etc.

While we all see the good intentions behind these initiatives, they sometimes lack the technical depth and the ambition to achieve swift results. My focus in this letter will be age verification, as the measure that is the most polarizing and may have significant negative side effects if done wrong. And I’m concerned that the currently selected approach by the European Commission is the wrong one.

The idea sounds simple – “social networks are proven to be detrimental to children’s mental health, and so they must not be allowed to use it. The way to do it is to add an age check before registration, so that only adults can use the service”. While simple to formulate, it’s much more difficult to implement, if not impossible.

There is an inherent paradox – if a solution is fully privacy-preserving, it’s ineffective. If it’s effective, it bears significant risks to privacy, as it will require every citizen to prove their identity online in order to use everyday services.

The European Commission has made a well-meaning attempt to design and implement a proper zero-knowledge proof of age. It’s a great tool, with proper cryptography, complex-yet-elegant. It has “just” one problem – it doesn’t account for the actual “threat actor” in this scenario – the user, who would try many things to circumvent the age limitation. As security consultant Paul Moore has brilliantly shown, you don’t have to compromise the age verification app in order to circumvent the flow – by a simple relay attack, where you just present someone else’s verified age credentials in order to use a service. The proof of concept was implemented as a chrome extension which relays age checks to 3rd party service, backed by an over-18 person’s device, which sends the proof to the service. That way a single adult can verify the accounts of all minors, and because of the necessary privacy guarantees, the relying party (the social network) won’t even know.

This is very likely to happen – “age verification as a service” providers will certainly pop-up to help minors get into social networks. What’s worse – some of these providers may collect children’s personal data, including phone number or social network account ID, in order to provide them with the much coveted proof of age. That data, purposefully or after an inevitable data breach, may be used by sex predators to target children. There are completely realistic nightmare scenarios, born from the good intention to limit the negative effects of social networks.

Even in a school context, a single over-18 (or over-16) student can lend their age verification app to help younger children register profiles. What are policy makers going to do then? Issue administrative fines for sharing age tokens/attestations? Criminalize it?

Any attempt to fix that technically, breaks the privacy guarantees; any attempt to fix it legally, is doomed to fail in enforcement.

My advice, in all my capacities listed in the beginning of this letter, is to abandon that approach and focus on a different approach – rely on parental control apps.

Parental control apps remain rudimentary, and perhaps there are reasons for this. They are not widely used and are often unintuitive and unreliable. However, they can be regulated and improved. They can also incorporate government-mandated lists of apps and domains restricted for children according to age. For example, a child protection agency could publish a list that parental control apps would be required to import automatically. Legislators could also require these apps to be pre-installed on every phone sold in their country. Parents would remain in control and could adjust the settings if they considered their children ready to use particular services responsibly.

Certain apps can be banned for under-14, others for under-16 and others – for under-18. Governments would have much better control over the exact services they deem risky for children, without the need for any changes on the service’s side. Or, if an app vendor wants to have it whitelisted, they may have to implement children-friendly versions.

Going further, this may eventually lead to platform-level parental control APIs, so that each app can read parental control settings, and on the other hand export parental control configuration options to be used in the parental control app.

What’s even better about this approach, is that VPNs can’t be used to circumvent it – it’s a device-level limitation, not service-level limitation, which needs to figure out the country of the user, which can only be done by their IP address.

And It’s completely privacy-preserving, as users don’t have to show or prove anything to anyone.
Of course, the harder part is making sure every child and parent has a parental control app installed. Information campaigns and teachers can help with that, and I’m sure it will achieve much better results than what we are seeing in Australia for example.
Even if the right age limitation measures are implemented, the efforts to limit the addictiveness and so-called “brainrot” on online platforms should continue.
We have proposed national legislation to implement the approach above. But in order to avoid fragmentation in the digital single market, and in order to have a working, cross-border model, where the experience of each country improves the model EU-wide, a solution should be discussed on a EU-level.

Yours sincerely,
Bozhidar Bozhanov,
Member of parliament of the Republic of Bulgaria

The post Letter To The European Commission About Age Verification And Social Networks appeared first on Bozho's tech blog.

AI Security

Post Syndicated from Bruce Schneier original https://www.schneier.com/blog/archives/2026/11/ai-security.html

Two weeks ago, I attended the [un]prompted AI security conference in San Francisco. It was an excellent event: three days of very dense talks about all aspects of AI security. (My talk was about integrous AI, and I will post it when it is online.)

AI security can be divided into three broad topics. It’s important for researchers to understand which one they are working on. And it’s important for us as a community to work on them all. They are: security of AI, security with AI, and security from AI. [un]prompted had good talks about all three.

Dell PowerEdge R770AP Review One Fast Intel Xeon 6 Server

Post Syndicated from Patrick Kennedy original https://www.servethehome.com/dell-poweredge-r770ap-review-one-fast-intel-xeon-6-server/

Today we are taking a look at Dell’s PowerEdge R770AP. The 2U server goes all-in on performance with a dual-socket Xeon 6 setup and 24 channels of DDR5 memory

The post Dell PowerEdge R770AP Review One Fast Intel Xeon 6 Server appeared first on ServeTheHome.

ASRock Rack DMRD16-2L+ Spotted with 16 DDR5 Slots for Diamond Rapids

Post Syndicated from John Lee original https://www.servethehome.com/asrock-rack-dmrd16-2l-plus-diamond-rapids-ocp-summit-2026/

We check out the ASRock Rack DMRD16-2L+ which is a 16-channel Intel Diamond Rapids Xeon motherboard with 128x PCIe Gen6 lanes over MCIO

The post ASRock Rack DMRD16-2L+ Spotted with 16 DDR5 Slots for Diamond Rapids appeared first on ServeTheHome.

Asahi Linux 7.3 progress report

Post Syndicated from corbet original https://lwn.net/Articles/1105936/

The Asahi Linux developers have put out a new report
on their progress toward a Linux distribution for Apple devices.

Some time ago, we were made aware of multiple attempts to exploit
our permissive licensing to hijack our work, with a direct view to
replacing the project and aggressively monetising Linux on Apple
Silicon. In some extreme cases, in-development feature code was
being lifted straight out of our personal forks and published
without attribution or lazily rewritten with LLM assistance to
obfuscate its origin. The MIT licence explicitly allows this, and
has no carveouts to protect against bad faith actors.

As such, we made the difficult decision to begin the process of
transitioning all of our repositories to the GNU General Public
License version 2 or later. Going forward all Asahi Linux code will
be licenced under strong copyleft licences only. Those who do not
learn from history are doomed to repeat it.

The collective thoughts of the interwebz