lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <176114872374.8.14068467571033879083.966530839@simplelogin.com>
Date: Wed, 22 Oct 2025 15:58:38 +0000
From: sender.ovzss@...plelogin.com
To: linux-kernel@...r.kernel.org
Subject: Kernel and Anti-Cheat Suggestions

Hello Linux Kernel Developers Team,

I'm not sure if I'm emailing the right place. What is the probability that what I'm writing will happen?

For all games to run flawlessly and receive official support on Linux, several key technical, structural, and economic changes would need to happen.

A unified and standardized Linux gaming platform

Currently, there are hundreds of Linux distributions (Ubuntu, Arch, Fedora, Debian, Pop!_OS, Manjaro, etc.), each with different kernels, drivers, and libraries. This makes consistent performance and stability difficult for developers.

A single standardized runtime layer—such as Valve’s SteamOS and Proton combination—would make it easier to target one common environment. If all major distros aligned under a “SteamOS-compatible” certification, developers could build once and support all users more easily.

Kernel-level secure sandbox or anti-cheat API

Anti-cheat systems like Riot Vanguard, BattleEye, and Easy Anti-Cheat require kernel-level access to verify system integrity. On Linux, differences in kernel modules and root permissions create security and compatibility issues.

A secure kernel interface or sandbox API designed for anti-cheat systems (similar to Windows’s Protected Game Mode or macOS’s System Integrity Protection) would allow anti-cheats to safely verify the system without intrusive kernel drivers. This would eliminate one of the biggest barriers to Linux gaming support.

Unified and stable GPU driver ecosystem

Games behave differently on NVIDIA, AMD, and Intel hardware due to varying driver quality and compatibility. Closed-source NVIDIA drivers often break after kernel updates.

To solve this, GPU vendors need to fully support the same modern graphics API—Vulkan—and maintain a stable ABI (Application Binary Interface) between the kernel and drivers. Consistent and open GPU support would make Linux gaming as reliable as Windows.

Official DirectX to Vulkan compatibility (or full DX12 support)

Most Windows games use DirectX 11 or 12, while Linux primarily uses Vulkan or OpenGL. Compatibility layers like Proton and DXVK translate these calls, but not perfectly.

If Microsoft provided an official Vulkan backend for DirectX, or if game engines like Unreal, Unity, and RE Engine made Vulkan their default renderer, games could run natively on Linux with little or no translation. Once the DirectX–Vulkan bridge is seamless, there will be no real “Windows-only” barrier.

Official Linux Game SDK and testing infrastructure

Developers currently face a fragmented testing environment: different distros, drivers, and libc versions.

An official Linux Game SDK—similar to Xbox GDK—would give developers a stable target, such as “Linux Game SDK 1.0 (kernel 6.10+, Vulkan 1.4+).” If Valve, Canonical, Red Hat, and System76 collaborated to provide this along with automated CI/CD testing support, developing for Linux would become as simple as developing for Windows or consoles.

Economic incentives and market growth

Only around 2–3% of gamers use Linux, according to Steam statistics. Studios are hesitant to invest in porting and support for such a small market.

However, the rise of Steam Deck and Proton is expanding Linux’s share. If the Linux gaming market surpasses 10%, developers will begin to support it naturally. Valve and other major players could also offer funding, visibility, or certification incentives for Linux-native games.

Standardized security and integrity verification (Secure Boot + TPM)

Anti-cheat systems must verify that a system’s boot process and kernel haven’t been tampered with. Linux distributions differ widely in bootloaders (GRUB, systemd-boot) and Secure Boot/TPM configurations.

If Linux standardized kernel module signing, TPM-based integrity, and Secure Boot behavior for “gaming mode,” anti-cheat systems would finally be able to trust the Linux environment without special exceptions.

In summary:

To make Linux a first-class gaming platform where all games run smoothly and securely, the following conditions are needed:

A unified Linux runtime or standard platform (like SteamOS)

A secure kernel-level API for anti-cheats

Stable, unified GPU drivers with Vulkan as the main API

Full DirectX–Vulkan interoperability

An official Linux SDK and CI infrastructure

A larger player base with developer incentives

A standardized Secure Boot and TPM verification chain

Once these areas mature, Linux could reach full parity with Windows in gaming—both technically and commercially.

Good Jobs Dear Linux Kernel Developers Team


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ