# gnu linux A free Unix-like operating system combining the GNU system with the Linux kernel. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Cellular Network Infrastructure - August 2026 Osmocom CNI releases DevFeed: [Cellular Network Infrastructure - August 2026 Osmocom CNI releases]() Original publisher: [Read original article]() Author: pespin Published: 2026-08-20T15:47:26Z Content type: release Language: en Sources: [Open Source Mobile Communications: News]() Topics: [releases](), [Software](), [Vulnerabilities](), [Debian](), [Ubuntu](), [gnu linux]() Tags: [2026](), [bug](), [changelog](), [cni](), [debian](), [gnu-linux](), [issue](), [network](), [releases](), [security-vulnerabilities](), [tracker](), [ubuntu](), [update](), [version]() ### AI overview The Osmocom project released version 202608 of its Cellular Network Infrastructure software, covering components including OsmoTRX, OsmoBTS, OsmoPCU, OsmoBSC, OsmoMGW, OsmoMSC, OsmoHLR, OsmoSGSN, OsmoGGSN, OsmoSTP, and OsmoSIPConnector. The release includes several months of changes, with new features, extensive bug fixes, and fixes for multiple security vulnerabilities. An osmo-mgw 1.16.1 patch release corrected a Debian dependency issue. ### Source excerpt The Osmocom project has released new version 202608 of the CNI (Cellular Network Infrastructure) software, including OsmoTRX, OsmoBTS, OsmoPCU, OsmoBSC, OsmoMGW, OsmoMSC, OsmoHLR, OsmoSGSN, OsmoGGSN, OsmoSTP, OsmoSIPConnector, and others. Those new tagged/released versions contain up to 6-8 months of work since the previous versions released through December 2025 and February 2026. Some projects already got some intermediate releases since then. This set of releases contain some new features, but mostly lots of bug fixing, including multiple fixes for security vulnerabilities. See below for more detailed information. You can find pre-compiled binary packages of our latest release for a variety of Debian and Ubuntu GNU/Linux versions at Binary Packages. UPDATE: A new osmo-mgw patch release 1.16.1 was made on top of release 1.16.0 in order to fix a debian/control typo which was creating a dependency issue. Versions of newly released projects¶ Project Version Changelog libasn1c 0.9.39 https://gitea.osmocom.org/cellular-infrastructure/libasn1c/src/tag/0.9.39/debian/changelog libsmpp34 1.14.6 https://gitea.osmocom.org/cellular-infrastructure/libsmpp34/src/tag/1.14.6/debian/changelog libosmo-asn1-tcap 0.3.0 https://gitea.osmocom.org/ss7-in-c/libosmo-asn1-tcap/src/tag/0.3.0/debian/changelog libosmocore 1.14.2 https://gitea.osmocom.org/osmocom/libosmocore/src/tag/1.14.2/debian/changelog libosmo-netif 1.8.0 https://gitea.osmocom.org/osmocom/libosmo-netif/src/tag/1.8.0/debian/changelog libosmo-abis 2.2.0 https://gitea.osmocom.org/osmocom/libosmo-abis/src/tag/2.2.0/debian/changelog libosmo-pfcp 0.7.0 https://gitea.osmocom.org/osmocom/libosmo-pfcp/src/tag/0.7.0/debian/changelog libosmo-sigtran, osmo-stp 2.3.0 https://gitea.osmocom.org/osmocom/libosmo-sigtran/src/tag/2.3.0/debian/changelog osmo-e1d 0.8.0 https://gitea.osmocom.org/retronetworking/osmo-e1d/src/tag/0.7.1/debian/changelog osmo-pcap 0.8.1 https://gitea.osmocom.org/osmocom/osmo-pcap/src/tag/0.8.1/debian/changelog osmo ## GNU Guix 1.5.0 released DevFeed: [GNU Guix 1.5.0 released]() Original publisher: [Read original article]() Author: Noé Lopez Published: 2026-01-23T14:00:00Z Content type: release Language: en Sources: [GNU Guix -- Blog]() Topics: [Package manager](), [gnu linux](), [Open Source](), [Linux](), [pull-requests]() Tags: [gnu-linux](), [images](), [installation](), [iso](), [linux](), [new-features](), [open-source](), [pull-requests](), [release](), [releases](), [update](), [virtual-machine-images]() ### AI overview GNU Guix 1.5.0 has been released with ISO installation images, virtual machine images, and tarballs for installing the package manager on GNU/Linux. The release follows three years of development and includes ecosystem changes such as a new consensus-based decision-making process, migration to Codeberg, and an annual release cycle. ### Source excerpt We are pleased to announce the release of GNU Guix version 1.5.0! The release comes with ISO-9660 installation images, virtual machine images, and with tarballs to install the package manager on top of your GNU/Linux distro, either from source or from binaries--check out the download page . Guix users can update by running guix pull . It's been 3 years since the previous release . That's a lot of time, reflecting both the fact that, as a rolling release , users continuously get new features and update by running guix pull ; but it also shows a lack of... ## Cross-Compiling NixOS images DevFeed: [Cross-Compiling NixOS images]() Original publisher: [Read original article]() Author: Jacek Galowicz Published: 2025-12-20T00:00:00Z Content type: tutorial Language: en Sources: [Nixcademy Blog]() Topics: [Nix](), [Cross-Compilation](), [gnu linux](), [systemd]() Tags: [article](), [compilation](), [cross-compilation](), [how-to](), [learn](), [linux](), [systemd]() ### AI overview Part four of a series explaining how to cross-compile NixOS appliance images for other platforms while retaining Nix's declarative and composable configuration model. ### Source excerpt Part 4 of our NixOS appliance image series - Learn how to cross-compile NixOS images without losing declarativity and composability ## Minimizing NixOS images DevFeed: [Minimizing NixOS images]() Original publisher: [Read original article]() Author: Jacek Galowicz Published: 2025-10-21T00:00:00Z Content type: tutorial Language: en Sources: [Nixcademy Blog]() Topics: [Nix](), [gnu linux](), [build performance](), [iteration]() Tags: [article](), [build](), [capabilities](), [how-to](), [iteration]() ### AI overview Part two of a four-part series that explains how to reduce a NixOS appliance image from 1.5 GB to around 360 MB. It covers using Nix tools to inspect dependencies and applying configuration techniques to create smaller system images. ### Source excerpt Part 2 of our NixOS appliance image series - Learn how to use native Nix tools to shrink the size of your NixOS system images with quick iteration cycles! ## docker-stafwag-unbound v2.1.0 released: Use unbound as an DNS-over-TLS resolver and authoritative DNS server DevFeed: [docker-stafwag-unbound v2.1.0 released: Use unbound as an DNS-over-TLS resolver and authoritative DNS server]() Original publisher: [Read original article]() Author: Staf Wagemakers Published: 2025-05-04T15:01:01Z Content type: release Language: en Sources: [stafwag Blog]() Topics: [Docker](), [Debian](), [gnu linux]() Tags: [container](), [debian](), [dns](), [docker](), [linux](), [resolver](), [stubby](), [unbound](), [version]() ### AI overview This release updates the docker-stafwag-unbound container to version 2.1.0. The update moves the base image to Debian Bookworm, generates a default certificate with unbound-control-setup, and updates the documentation. The article also explains using Unbound as an authoritative DNS server and for DNS-over-TLS. ### Source excerpt Unbound is a popular DNS resolver, that has native DNS-over-TLS support. Unbound and Stubby were among the first resolvers to implement DNS-over-TLS. I wrote a few blog posts on how to use Stubby on GNU/Linux and FreeBSD. https://blog.wagemakers.be/blog/2018/09/09/dns-privacy-with-stubby-part1-gnulinux/ https://blog.wagemakers.be/blog/2018/10/07/dns-privacy-with-stubby-part-2-freebsd/ The implementation status of DNS-over-TLS and other DNS privacy options is available at: https://dnsprivacy.org/. See https://dnsprivacy.org/implementation_status/ for more details. It's less known that it can also be used as authoritative DNS server (aka a real DNS server). Since I discovered this feature and Unbound got native DNS-over-TLS support I started to it as my DNS server. I created a docker container for it a couple of years back to use it as an authoritative DNS server. I recently updated the container, the latest version (2.1.0) is available at: https://github.com/stafwag/docker-stafwag-unbound ChangeLog Version 2.1.0 Upgrade to debian:bookworm Updated BASE_IMAGE to debian:bookworm Add ARG DEBIAN_FRONTEND=noninteractive Run unbound-control-setup to generate the default certificate Documentation updated ## Attacking UNIX Systems via CUPS, Part I DevFeed: [Attacking UNIX Systems via CUPS, Part I]() Original publisher: [Read original article]() Author: Simone Margaritelli Published: 2024-09-26T14:51:30Z Content type: article Language: en Sources: [evilsocket]() Topics: [vulnerability](), [Security](), [Unix](), [Exploit](), [gnu linux](), [systems]() Tags: [bugs](), [cups](), [cups-browsed](), [cve](), [cve-2024-47076](), [cve-2024-47175](), [cve-2024-47176](), [cve-2024-47177](), [cybersecurity](), [disclosure](), [exploit](), [gnu-linux](), [hacking](), [ipp](), [lan](), [linux-security](), [mdns](), [no-authentication](), [port](), [print-services](), [printer](), [printers](), [printing](), [rce](), [responsible-disclosure](), [security](), [udp](), [unauthenticated-access](), [unix](), [vulnerability-research](), [zeroconf]() ### AI overview A security writeup describes multiple vulnerabilities in CUPS components affecting GNU/Linux and other UNIX systems. It reports that remote unauthenticated attackers may replace printer IPP URLs and trigger arbitrary command execution when a print job starts, with attacks possible over the public internet or via spoofed LAN advertisements. ### Source excerpt Hello friends, this is the first of two, possibly three (if and when I have time to finish the Windows research) writeups. We will start ## How "Meet the PinePhone Pro" was made DevFeed: [How "Meet the PinePhone Pro" was made]() Original publisher: [Read original article]() Published: 2021-10-27T00:00:00Z Content type: article Language: en Sources: [Community blog on PINE64]() Topics: [Pinephone-Pro](), [blender](), [Pine64](), [Open Source](), [Graphics](), [gnu linux]() Tags: [blender](), [community](), [cuda](), [gnu-linux](), [graphics](), [open-source](), [pine64](), [pinephone-pro](), [raytracing]() ### AI overview This article explains how the "Meet the PinePhone Pro" trailer and product renderings were produced. It describes the volunteer community's workflow, including modelling, scene creation, animation, storytelling, music, voice recording, editing, and rendering with Blender and other free and open source tools. ### Source excerpt As PINE64's flagship mainline GNU/Linux smartphone, the PinePhone Pro, was about to be announced, a trailer and some nice renderings showcasing the phone and its features had to be produced. The groundwork for the trailer was started in February 2021 and took all the way up to a few days before the trailer was released at October 15th 2021. The work for the trailer included making the material and models, creating the scene and the surroundings, animating the scenes, establishing a story in the video, finding fitting music, cutting it and adding sound details, writing and recording the text and cutting the video, which took many hours of work until the following trailer was released: https://www.youtube.com/watch?v=wP2-6Z74W44 The trailer is almost entirely made with free and open source software - modelling, the scenes, animations and final cut including the music is all done in Blender, vector graphics and some smaller graphical edits for the screen contents are done in Inkscape and Gimp. The trailer is made by volunteers from the community. The visuals The general idea of the trailer was to tell a story: visually we wanted to lead the viewer from the history of the PinePhone, to the introduction of the PinePhone Pro including its features, to the actual usage. Not only did we want to tell the story of PINE64 making shipping such a device real but also point the viewer to what was achieved so far and what the user can achieve using the phone. We selected a darker setting for the intro part of the video and we tried to go for brighter settings mixed with realistic settings for the PinePhone Pro introduction part of the video. For product renderings typically Blender Cycles is used, which has the downside that the raytracing can take a very long time to achieve a fine rendering quality, unlike Blender's Eevee architecture using rasterization instead of raytracing (especially used effects such as depth of field and other makes raytracing a must here). That means even