GrapheneOS warns Pixel 11 drops hardware memory tagging security feature

·1 views

The GrapheneOS project has flagged that Google's Pixel 11 will no longer support Memory Tagging Extension (MTE), a hardware-level security feature. MTE helps detect memory safety vulnerabilities such as buffer overflows and use-after-free bugs at the hardware level. GrapheneOS, a privacy and security-focused Android fork, raised the concern via a post on Bluesky. The removal is notable because MTE has been a key hardware security capability on recent Pixel devices. This change may have implications for users and projects that rely on hardware-enforced memory safety protections.

Read the full story at Hacker News

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

GKE Launches VPA Decision Logs to Improve Kubernetes Autoscaling Visibility

Google Kubernetes Engine (GKE) has launched a Public Preview of Vertical Pod Autoscaler (VPA) Logs, available on clusters running version 1.36.0-gke.1601000 or newer. Previously, VPA decisions were difficult to audit because standard Kubernetes events expired after roughly an hour, leaving engineers unable to diagnose unexpected pod evictions or failed in-place resizes. The new feature streams structured VPA decision events directly into Cloud Logging under the destination container.googleapis.com/vpa-controller, creating a permanent audit trail. Logs are categorized across four operations — updating recommendations, evicting pods, applying recommendations on eviction, and applying recommendations in place — each tagged with a success, skipped, or failed status. Combined with existing Horizontal Pod Autoscaler logging, GKE operators now have unified visibility across both horizontal and vertical autoscaling dimensions.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How to Structure an Elixir Project Using Mix: A Practical Guide

As Elixir projects grow beyond a few modules, managing code in IEx sessions becomes impractical due to redefinition warnings and name collisions. Mix, Elixir's built-in build tool, solves this by generating a standard project skeleton that handles compilation, testing, and dependency management. A typical Mix project organizes application code under lib/, with file paths and directory names mirroring module names — for example, LearningElixir.TodoList maps to lib/learning_elixir/todo_list.ex. Non-code assets go in priv/, while config/ separates environment-specific settings for dev, test, and prod. Although the Elixir compiler does not enforce these conventions, virtually all Elixir projects follow them, making the codebase easier to navigate and maintain as it scales.

0 comments Read more at DEV Community

ProgrammingHacker News ·

Opinion: The Modern Internet Has Become Exploitative and Toxic

A blog post by Stephen Diehl argues that the contemporary internet has devolved into a predatory environment for users. The piece, shared on Hacker News, attracted 26 upvotes and sparked discussion among readers. Diehl's essay examines how online platforms and digital ecosystems have shifted toward exploitative practices. The post reflects growing public concern about the commercialization and manipulation embedded in today's internet experience.

0 comments Read more at Hacker News

ProgrammingDEV Community ·

Why Organisational Constraints Often Matter More Than Technology Choices

Technology challenges in organisations rarely stem from technical limitations alone, according to observations from advisory firm Cralgo. Slow delivery, shifting priorities, and poor decision-making are frequently rooted in unclear ownership, misaligned teams, and weak governance rather than inadequate tools or platforms. Investments in cloud, AI, and automation only deliver value when the organisation surrounding them can effectively direct and use that capability. As companies scale, informal context-sharing breaks down, causing the original intent behind decisions to erode before reaching execution. The critical gap, the article argues, lies in the connective layer between strategy and delivery, where sound judgement must be carried consistently into action.

0 comments Read more at DEV Community