More seriously, perhaps namespaces in 1.7.0
November 7, 2026 at 1:39 AM
More seriously, perhaps namespaces in 1.7.0
Taming Autonomous AI Agents with Rootless Docker
How rootless Docker, Linux user namespaces, and cgroups v2 contain autonomous AI coding agents without escalating to host root privileges.
#hackernews #news
How rootless Docker, Linux user namespaces, and cgroups v2 contain autonomous AI coding agents without escalating to host root privileges.
#hackernews #news
Taming Autonomous AI Agents with Rootless Docker
How rootless Docker, Linux user namespaces, and cgroups v2 contain autonomous AI coding agents without escalating to host root privileges.
hackernoon.com
November 7, 2026 at 10:45 PM
Taming Autonomous AI Agents with Rootless Docker
How rootless Docker, Linux user namespaces, and cgroups v2 contain autonomous AI coding agents without escalating to host root privileges.
#hackernews #news
How rootless Docker, Linux user namespaces, and cgroups v2 contain autonomous AI coding agents without escalating to host root privileges.
#hackernews #news
How rootless Docker, Linux user namespaces, and cgroups v2 contain autonomous AI coding agents without escalating to host root privileges. #rootlessdocker
Taming Autonomous AI Agents with Rootless Docker
hackernoon.com
November 6, 2026 at 3:00 PM
How rootless Docker, Linux user namespaces, and cgroups v2 contain autonomous AI coding agents without escalating to host root privileges. #rootlessdocker
Rebranding without functional changes still breaks hardcoded IAM policy strings referencing service namespaces.
November 10, 2026 at 2:40 AM
Rebranding without functional changes still breaks hardcoded IAM policy strings referencing service namespaces.
The Linux kernel stole some of its ideas about filesystems and namespaces, such as /proc. But Plan 9’s main legacy is something you use all the time and don’t notice it.
November 8, 2026 at 9:51 AM
The Linux kernel stole some of its ideas about filesystems and namespaces, such as /proc. But Plan 9’s main legacy is something you use all the time and don’t notice it.
I used Renderware before they bought it and then saw the bones that were left after joining EA. Only thing that remained were some code namespaces and none of the actual rendering lib anymore
November 6, 2026 at 3:55 AM
I used Renderware before they bought it and then saw the bones that were left after joining EA. Only thing that remained were some code namespaces and none of the actual rendering lib anymore
Time to bring back XML namespaces and repurpose them for custom elements
November 3, 2026 at 2:50 PM
Time to bring back XML namespaces and repurpose them for custom elements
It all comes down to:
Namespaces and cgroups. That’s really all you need to know.
Namespaces and cgroups. That’s really all you need to know.
November 9, 2026 at 2:30 PM
It all comes down to:
Namespaces and cgroups. That’s really all you need to know.
Namespaces and cgroups. That’s really all you need to know.
does anyone know a good method to deduplicate DWARF type info (because structs get re-encoded per compilation-unit) that takes a trust-but-verify approach (they could indeed differ) to matching by type name (unreliable, anonymous namespaces exist, etc.)
November 8, 2026 at 3:36 PM
does anyone know a good method to deduplicate DWARF type info (because structs get re-encoded per compilation-unit) that takes a trust-but-verify approach (they could indeed differ) to matching by type name (unreliable, anonymous namespaces exist, etc.)
Birdcage is a Rust crate that restricts filesystem and network access using namespaces on Linux and Seatbelt on macOS. But caveats from its README: it covers only those two, isn't a full sandbox, is GPL-3.0, and the repo was archived in July 2026.
November 10, 2026 at 2:59 AM
Birdcage is a Rust crate that restricts filesystem and network access using namespaces on Linux and Seatbelt on macOS. But caveats from its README: it covers only those two, isn't a full sandbox, is GPL-3.0, and the repo was archived in July 2026.
I am the nascent Proxmox user who just discovered namespaces on the Backup Server. We're better able to segregate the backup from difference clusters making our lives just that much easier.
To quote the venerable Tim Peters - "Namespaces are one honking great idea – let's do more of those!"
To quote the venerable Tim Peters - "Namespaces are one honking great idea – let's do more of those!"
November 9, 2026 at 3:22 PM
I am the nascent Proxmox user who just discovered namespaces on the Backup Server. We're better able to segregate the backup from difference clusters making our lives just that much easier.
To quote the venerable Tim Peters - "Namespaces are one honking great idea – let's do more of those!"
To quote the venerable Tim Peters - "Namespaces are one honking great idea – let's do more of those!"
Maybe science needs to develop a better system for namespaces.
(In my hard sf game setting a running joke is that the IAU AI name assignment system went off the rails sometime in early interstellar colonisation, producing really embarassing naming of many solar systems.)
(In my hard sf game setting a running joke is that the IAU AI name assignment system went off the rails sometime in early interstellar colonisation, producing really embarassing naming of many solar systems.)
November 9, 2026 at 3:02 PM
Maybe science needs to develop a better system for namespaces.
(In my hard sf game setting a running joke is that the IAU AI name assignment system went off the rails sometime in early interstellar colonisation, producing really embarassing naming of many solar systems.)
(In my hard sf game setting a running joke is that the IAU AI name assignment system went off the rails sometime in early interstellar colonisation, producing really embarassing naming of many solar systems.)
How do you keep entitlements from multiplying into their own ops headache once agents start composing calls across namespaces?
November 8, 2026 at 8:04 AM
How do you keep entitlements from multiplying into their own ops headache once agents start composing calls across namespaces?
I really want to do standard ML, and elisp/lazy (a much simpler language), and namespaces, and full prolog, and…
but I should actually release this thing at some point! even without all that stuff, it has a lot of value
but I should actually release this thing at some point! even without all that stuff, it has a lot of value
November 7, 2026 at 11:58 AM
I really want to do standard ML, and elisp/lazy (a much simpler language), and namespaces, and full prolog, and…
but I should actually release this thing at some point! even without all that stuff, it has a lot of value
but I should actually release this thing at some point! even without all that stuff, it has a lot of value
CVE-2026-124440
Kyverno versions from 1.19.1 up to but not including 1.19.2 let a user inside one Kubernetes namespace send requests that affect other namespaces or the whole cluster. This can be used to read data from…
Too many irrelevant or confusing CVEs? Use stackflag.com
#CVE #infosec
Kyverno versions from 1.19.1 up to but not including 1.19.2 let a user inside one Kubernetes namespace send requests that affect other namespaces or the whole cluster. This can be used to read data from…
Too many irrelevant or confusing CVEs? Use stackflag.com
#CVE #infosec
CVE-2026-124440: Kyverno 1.19.1–1.19.2 lets tenants access other namespaces
Kyverno versions from 1.19.1 up to but not including 1.19.2 let a user inside one Kubernetes namespace send requests that affect other namespaces or the.
stackflag.com
November 8, 2026 at 2:40 PM
CVE-2026-124440
Kyverno versions from 1.19.1 up to but not including 1.19.2 let a user inside one Kubernetes namespace send requests that affect other namespaces or the whole cluster. This can be used to read data from…
Too many irrelevant or confusing CVEs? Use stackflag.com
#CVE #infosec
Kyverno versions from 1.19.1 up to but not including 1.19.2 let a user inside one Kubernetes namespace send requests that affect other namespaces or the whole cluster. This can be used to read data from…
Too many irrelevant or confusing CVEs? Use stackflag.com
#CVE #infosec
📰 **[$] User namespaces + file capabilities = trouble**
User namespaces are a key part of the kernel's toolkit for assembling containers; processes within a user namespace can appear to have full root access to the system while gaining no extra privileg...
📰 Source: LWN.net
🔗 Link […]
User namespaces are a key part of the kernel's toolkit for assembling containers; processes within a user namespace can appear to have full root access to the system while gaining no extra privileg...
📰 Source: LWN.net
🔗 Link […]
Original post on igeek.gamer-geek-news.com
igeek.gamer-geek-news.com
November 7, 2026 at 2:44 PM
📰 **[$] User namespaces + file capabilities = trouble**
User namespaces are a key part of the kernel's toolkit for assembling containers; processes within a user namespace can appear to have full root access to the system while gaining no extra privileg...
📰 Source: LWN.net
🔗 Link […]
User namespaces are a key part of the kernel's toolkit for assembling containers; processes within a user namespace can appear to have full root access to the system while gaining no extra privileg...
📰 Source: LWN.net
🔗 Link […]
November 5, 2026 at 3:00 PM
Maybe I should build some ontologies for com.atproto and app.bsky namespaces and see where I end up 👀
November 7, 2026 at 1:15 AM
Maybe I should build some ontologies for com.atproto and app.bsky namespaces and see where I end up 👀
The exploit chained a bug in the Linux kernel's checksum offload handling to escape. Several people pointed out that Firecracker's jailer—using seccomp and namespaces—is meant to blunt this, but relying on defense-in-depth feels fragile when local privilege escalations keep landing. #linux 2/4
November 7, 2026 at 10:00 PM
The exploit chained a bug in the Linux kernel's checksum offload handling to escape. Several people pointed out that Firecracker's jailer—using seccomp and namespaces—is meant to blunt this, but relying on defense-in-depth feels fragile when local privilege escalations keep landing. #linux 2/4
Sobre mudar para c++.
É mais por questão de organização do projeto
namespaces, name mangling e templates.
Evitarei utilizar headers C++.
É mais por questão de organização do projeto
namespaces, name mangling e templates.
Evitarei utilizar headers C++.
November 7, 2026 at 4:30 AM
Sobre mudar para c++.
É mais por questão de organização do projeto
namespaces, name mangling e templates.
Evitarei utilizar headers C++.
É mais por questão de organização do projeto
namespaces, name mangling e templates.
Evitarei utilizar headers C++.
Building a Kubernetes Operator for Workload Identity Federation Across AWS and GCP
myceliam turns Kubernetes Namespaces and ServiceAccounts into the source of truth for identity, create counterpart resources in IDPs and cloud providers.
#hackernews #news
myceliam turns Kubernetes Namespaces and ServiceAccounts into the source of truth for identity, create counterpart resources in IDPs and cloud providers.
#hackernews #news
Building a Kubernetes Operator for Workload Identity Federation Across AWS and GCP
myceliam turns Kubernetes Namespaces and ServiceAccounts into the source of truth for identity, create counterpart resources in IDPs and cloud providers.
hackernoon.com
November 10, 2026 at 12:09 AM
Building a Kubernetes Operator for Workload Identity Federation Across AWS and GCP
myceliam turns Kubernetes Namespaces and ServiceAccounts into the source of truth for identity, create counterpart resources in IDPs and cloud providers.
#hackernews #news
myceliam turns Kubernetes Namespaces and ServiceAccounts into the source of truth for identity, create counterpart resources in IDPs and cloud providers.
#hackernews #news
📘 Learn++ C++ Lesson 51: Nested Namespaces.
🧩 Practice defining Outer::Inner and calling display() through the full path in Learn++
🔗 https://learnplusplus.online/news/lesson51-cpp-nested-namespaces-2026-11-05.html
#learnplusplus #cplusplus #learncpp
🧩 Practice defining Outer::Inner and calling display() through the full path in Learn++
🔗 https://learnplusplus.online/news/lesson51-cpp-nested-namespaces-2026-11-05.html
#learnplusplus #cplusplus #learncpp
November 5, 2026 at 8:03 AM
📘 Learn++ C++ Lesson 51: Nested Namespaces.
🧩 Practice defining Outer::Inner and calling display() through the full path in Learn++
🔗 https://learnplusplus.online/news/lesson51-cpp-nested-namespaces-2026-11-05.html
#learnplusplus #cplusplus #learncpp
🧩 Practice defining Outer::Inner and calling display() through the full path in Learn++
🔗 https://learnplusplus.online/news/lesson51-cpp-nested-namespaces-2026-11-05.html
#learnplusplus #cplusplus #learncpp
myceliam turns Kubernetes Namespaces and ServiceAccounts into the source of truth for identity, create counterpart resources in IDPs and cloud providers. #kubernetesoperators
Building a Kubernetes Operator for Workload Identity Federation Across AWS and GCP
hackernoon.com
November 9, 2026 at 5:00 AM
myceliam turns Kubernetes Namespaces and ServiceAccounts into the source of truth for identity, create counterpart resources in IDPs and cloud providers. #kubernetesoperators
Write a container runtime and you learn: a container is a host process fenced in by namespaces and cgroups, an image is a folder it chroots into, runc needs a C shim.
Docker's creator turned the HN thread into an AMA.
https://codeandcake.dev/posts/2026-10-22-docker-is-weird
Docker's creator turned the HN thread into an AMA.
https://codeandcake.dev/posts/2026-10-22-docker-is-weird
November 9, 2026 at 12:10 AM
Write a container runtime and you learn: a container is a host process fenced in by namespaces and cgroups, an image is a folder it chroots into, runc needs a C shim.
Docker's creator turned the HN thread into an AMA.
https://codeandcake.dev/posts/2026-10-22-docker-is-weird
Docker's creator turned the HN thread into an AMA.
https://codeandcake.dev/posts/2026-10-22-docker-is-weird