Nvidia to Cease Regular GeForce Driver Updates for Windows 10 After October 2026
Nvidia will end regular driver support for Windows 10 in its GeForce Game Ready and Nvidia Studio lines in October 2026. The first driver release that drops Windows 10 compatibility is scheduled for November 2026.
The company notes that it is outlasting Microsoft by one year. The base lifecycle of Windows 10 officially concluded on 14 October 2025. After that point, Nvidia will gradually phase out full driver development for the older operating system.
GeForce cards running Windows 10 will not become unusable. Installed games and applications will continue to work, and Nvidia will still issue quarterly patches addressing critical vulnerabilities until October 2029.
However, users will no longer receive full driver packages that include optimizations for new titles, corrections for graphics bugs, or the latest GPU features. Emerging technologies such as DLSS may also bypass Windows 10 entirely.
For gamers this means a measured transition rather than an immediate cutoff. Legacy projects will keep running, yet each major new release will increasingly signal the need to move to a current version of Windows.
Related articles
redb.Identity Adds gRPC Transport for OpenID Server Alongside Existing HTTP Facade
redb.Identity has introduced a second transport layer using gRPC next to its existing HTTP interface, sharing the same core routes, client registry, token store, and authorization logic. The new facade exposes standard OAuth and OpenID Connect operations such as Token, Introspect, Revoke, UserInfo, Discovery, and Jwks through protobuf-defined methods under identity.v1.Identity. Both transports enforce identical verdicts based on a single centralized scope table located behind direct-vm addresses, ensuring that a client authorized via HTTP receives the same result when calling gRPC. Error handling on gRPC uses status codes and trailers to carry machine-readable OAuth error codes and retry-after values, preserving compatibility with existing interceptors and tracing. Browser-facing flows, DPoP proofs, and user self-service remain on HTTP, while administrative operations are available on a separate management port. The implementation was validated through 64 unit tests, cross-language interop with @grpc/grpc-js clients, and a conformance run against the official OpenID Foundation suite.
Rospotrebnadzor Introduces Age-Based Screen Time Limits for Russian School Students
Russia's consumer protection agency Rospotrebnadzor has established recommended maximum durations for schoolchildren working with computers and interactive whiteboards during lessons. The limits vary by grade, ranging from 20 minutes for first and second graders up to 35 minutes for students in grades 10 and 11. Separate rules apply to interactive boards, capping usage at 20 minutes for children under 10 and 30 minutes for older students. Schools must ensure students perform eye exercises when electronic devices are used, while traditional paper-based classes require such exercises only during breaks. Starting September 1 2026, a nationwide ban on mobile phones during lessons will also take effect, with individual schools deciding rules for recess periods.
From Root CA to User Authorization in nginx and Apache: Client Certificate Login Explained
This is the third installment in a detailed tutorial series covering the deployment of a two-tier PKI infrastructure with Root CA and intermediate CAs for Person, Server, and Code. The article provides comprehensive configuration guidance for enabling mTLS in nginx and Apache, including full references for all ssl_client_* variables and SSL directives. It explains the differences between password-based and certificate-based authentication, the TLS handshake steps involving CertificateRequest and CertificateVerify, and the importance of proper extendedKeyUsage settings such as clientAuth. Readers learn how to issue client certificates, package them in PKCS#12 format, enforce revocation checks via CRL and OCSP, and safely pass certificate fields to backend applications while mitigating risks from header spoofing. The guide also covers scenarios where the application itself terminates TLS without a reverse proxy and demonstrates login flows protected against CSRF using one-time tokens.
Honeytoken Traps for Detecting Compromised Backends in Encryption Key Services
The article details a honeytoken-based detection system designed to identify when a trusted backend has been compromised and is abusing its signing key to request encryption keys for arbitrary documents. A secret set of fake user and document identifiers is stored only inside the key service using keyed HMAC-SHA256 hashes, ensuring the backend itself cannot discover or bypass the canaries. Any signed request touching these identifiers triggers an alarm, audit logging, and optional emergency lock that wipes master keys from memory. The check is deliberately placed after signature validation but before envelope decryption to avoid false positives from unauthenticated attackers while keeping performance cost low. Two types of canaries address different attack patterns: document canaries catch bulk scraping while user canaries detect forged grants for non-existent principals. The mechanism has been deployed in production, with live tests confirming silent failure responses externally and clear canary_trip plus emergency_lock events internally. Limitations include inability to catch targeted extraction of a single real user’s documents and the fact that detection occurs after a canary key has already been issued.