# apt APT is a package management tool. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Loongson loong64 packages on apt.postgresql.org DevFeed: [Loongson loong64 packages on apt.postgresql.org]() Original publisher: [Read original article]() Author: Apt Postgresql Org Published: 2026-08-19T00:00:00Z Content type: news Language: en Sources: [PostgreSQL news]() Topics: [apt](), [PostgreSQL](), [cpu](), [Geographic Information System](), [Exception]() Tags: [apt](), [architecture](), [community](), [postgresql]() ### AI overview apt.postgresql.org now provides PostgreSQL packages for the Loongson loong64 architecture. The GIS package stack is still awaiting the next PostGIS release. ### Source excerpt We have a new architecture on apt.postgresql.org: Loongson loong64, a Chinese processor architecture. The build host for the architecture is running on a Loongson 3B6000 board provided by the loongfans.cn community. Bootstrapping the PostgreSQL packages was completed earlier this month and everything is in place to be used via apt.postgresql.org. The exception is the GIS stack of packages (postgis, pgrouting, mobilitydb, pgsql-ogr-fdw) which are currently still waiting for the next postgis release. Enjoy, Christoph ## How to Install and Configure UniFi Controller on Raspberry Pi? DevFeed: [How to Install and Configure UniFi Controller on Raspberry Pi?]() Original publisher: [Read original article]() Author: Patrick Fromaget Published: 2026-08-13T02:01:39Z Content type: tutorial Language: en Sources: [RaspberryTips]() Topics: [Network](), [configuration](), [Linux](), [Debian](), [apt](), [Software](), [Web](), [Hardware]() Tags: [apt](), [article](), [debian](), [devices](), [guide](), [hardware](), [how-to](), [how-to-tutorials](), [linux](), [network](), [networks](), [raspberry-pi](), [software](), [unifi](), [web-interface]() ### AI overview A practical guide to installing and configuring the UniFi Network Application on a Raspberry Pi using a Debian repository or .deb package, apt, and a web interface. It also explains how the application manages multiple access points and wireless devices. ### Source excerpt I've managed access points for years as a sysadmin, and once you have 10+ devices connected, it can quickly become a nightmare. UniFi solved that problem for us, but its dedicated gateways can be expensive. The good news is that a Raspberry Pi can handle the controller role instead. Here's how to set it up.... ## Create Python GUI Apps on Raspberry Pi With PyQt DevFeed: [Create Python GUI Apps on Raspberry Pi With PyQt]() Original publisher: [Read original article]() Author: Patrick Fromaget Published: 2026-07-30T01:34:44Z Content type: tutorial Language: en Sources: [RaspberryTips]() Topics: [Python](), [GUI](), [Qt](), [apt](), [Terminal](), [Programming](), [Linux](), [C++]() Tags: [apt](), [c-plus-plus](), [cheat-sheet](), [gui](), [how-to](), [linux](), [programming](), [programming-language](), [python](), [raspberry-pi](), [raspberry-pi-os](), [systems](), [user-interface]() ### AI overview A practical tutorial on creating Python GUI applications with PyQt on Raspberry Pi. It introduces PyQt and Qt, then covers installation through APT or pip on Raspberry Pi OS. ### Source excerpt I use Python for many Raspberry Pi projects, especially when working with GPIO pins or automating simple tasks. But running a script in the terminal is one thing; giving it a clean, user-friendly interface is another. PyQt is one of the easiest ways to build this. PyQt is a library that can be used to... ## Fix the 'externally-managed-environment' Error on Raspberry Pi DevFeed: [Fix the 'externally-managed-environment' Error on Raspberry Pi]() Original publisher: [Read original article]() Author: Robert Lopez Published: 2026-07-01T05:00:00Z Content type: tutorial Language: en Sources: [RaspberryTips]() Topics: [pip](), [Python](), [apt](), [Debian](), [Cheat sheet]() Tags: [apt](), [debian](), [guide](), [guides](), [how-to](), [programming](), [python](), [raspberry-pi](), [tutorial]() ### AI overview This guide explains why pip installation can fail with an "externally-managed-environment" error on Raspberry Pi systems running Debian 12 or newer. It describes the role of APT in managing system Python packages and helps readers choose an appropriate installation method without damaging the system setup. ### Source excerpt Many older Raspberry Pi tutorials still show a simple pip install command to add Python packages. It worked for years, but on recent operating systems, it can now fail with an "externally-managed-environment" error. If this is the first time you've seen it, here's what changed and how to fix it. The externally-managed-environment error appears when... ## Sednit reloaded: Back in the trenches DevFeed: [Sednit reloaded: Back in the trenches]() Original publisher: [Read original article]() Author: ESET Research Published: 2026-03-10T09:58:00Z Content type: article Language: en Sources: [WeLiveSecurity]() Topics: [apt](), [Cloud](), [obfuscation](), [PowerShell](), [Code](), [Network](), [Open Source]() Tags: [apt](), [attacks](), [backdoor](), [cloud](), [code](), [department-of-justice](), [eset-research](), [network](), [obfuscation](), [open-source](), [powershell](), [us]() ### AI overview This article examines the resurgence of Sednit, also known as APT28, and its modern espionage toolkit. It describes the BeardShell and Covenant implants, their use of legitimate cloud providers for command and control and resilience, PowerShell execution, obfuscation, and links to Sednit's earlier tools and operations. ### Source excerpt The resurgence of one of Russia's most notorious APT groups ## ESET Research: Sandworm behind cyberattack on Poland's power grid in late 2025 DevFeed: [ESET Research: Sandworm behind cyberattack on Poland's power grid in late 2025]() Original publisher: [Read original article]() Author: ESET Research Published: 2026-01-23T16:58:26Z Content type: article Language: en Sources: [WeLiveSecurity]() Topics: [ESET research](), [Critical Infrastructure](), [apt](), [Malware](), [data]() Tags: [analysis](), [apt](), [critical-infrastructure](), [energy](), [eset-research](), [history](), [infrastructure](), [malware](), [research](), [security]() ### AI overview ESET Research attributes a late-2025 cyberattack on Poland's power grid to the Russia-aligned Sandworm APT group with medium confidence. The attack used data-wiping malware named DynoWiper, although no successful disruption has been identified. The article places the incident in the context of Sandworm's history of attacks on critical infrastructure, including the 2015 Ukrainian power-grid blackout. ### Source excerpt The attack involved data-wiping malware that ESET researchers have now analyzed and named DynoWiper ## Disable the pager for apt search DevFeed: [Disable the pager for apt search]() Original publisher: [Read original article]() Author: Tom Published: 2026-01-19T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gฤ…gor]() Topics: [apt](), [Debian](), [configuration](), [systems]() Tags: [apt](), [apt-cache](), [bash](), [command-line](), [configuration](), [debian](), [how-to](), [less](), [linux](), [pager](), [terminal](), [ubuntu]() ### AI overview This tutorial explains how to disable the pager used for apt search results on Debian-based systems. It compares older search commands and an environment-variable setting, then recommends a permanent configuration-file change that keeps colorized output. ### Source excerpt Learn how to disable the annoying pager for apt search results on Debian-based systems, and find the best permanent solution. ## Code And Let Live DevFeed: [Code And Let Live]() Original publisher: [Read original article]() Published: 2026-01-09T00:00:00Z Content type: opinion Language: en Sources: [The Fly Blog]() Topics: [Cloud](), [Linux](), [apt](), [Amazon EC2](), [Network](), [ssh](), [Docker]() Tags: [apt](), [cdn](), [close-to-users](), [cloud](), [code](), [deploy-app-servers](), [docker](), [elixir](), [fly](), [fly-io](), [heroku-alternative](), [heroku-competitor](), [hosting](), [i](), [linux](), [network](), [networking](), [postgresql-clusters](), [servers](), [ssh]() ### AI overview Fly.io presents Sprites as durable, rapidly created cloud computers designed to replace ephemeral, read-only sandboxes. A Sprite provides a persistent Linux environment with substantial storage, automatic sleep, checkpoint and restore, networking, and low-cost operation at scale. ### Source excerpt The state of the art in agent isolation is a read-only sandbox. At Fly.io, we've been selling that story for years, and we're calling it: ephemeral sandboxes are obsolete. Stop killing your sandboxes every time you use them. My argument won't make sense without showing you something new we've built. We're all adults here, this is a company, we talk about what we do. Here goes. So, I want to run some code. So what I do is, I run sprite create. While it operates, I'll explain what's happening behind the-- Wrap text Copy to clipboard โœ“ Created demo-123 sprite in 1.0s โ— Connecting to console... sprite@sprite:~# Shit, it's already there. That's a root shell on a Linux computer we now own. It came online in about the same amount of time it would take to ssh into a host that already existed. We call these things "Sprites". Let's install FFmpeg on our Sprite: Wrap text Copy to clipboard sudo apt-get install -y ffmpeg >/dev/null 2>&1 Unlike creating the Sprite in the first place, installing ffmpeg with apt-get is dog slow. Let's try not to have to do that again: Wrap text Copy to clipboard sprite@sprite:~# sprite-env checkpoints create # ... {"type":"complete","data":"Checkpoint v1 created successfully", "time":"2025-12-22T22:50:48.60423809Z"} This completes instantly. Didn't even bother to measure. I step away to get coffee. Time passes. The Sprite, noticing my inactivity, goes to sleep. I meet an old friend from high school at the coffee shop. End up spending the day together. More time passes. Days even. Returning later: Wrap text Copy to clipboard > $ sprite console sprite@sprite:~# ffmpeg ffmpeg version 7.1.1-1ubuntu1.3 Copyright (c) 2000-2025 the FFmpeg developers Use -h to get full help or, even better, run 'man ffmpeg' sprite@sprite:~# Everything's where I left it. Sprites are durable. 100GB capacity to start, no ceremony. Maybe I'll keep it around a few more days, maybe a few months, doesn't matter, just works. Say I get an application up on its legs. Install more pa ## Blog: GPG Key Rotation for Falco Packages (2026) DevFeed: [Blog: GPG Key Rotation for Falco Packages (2026)]() Original publisher: [Read original article]() Published: 2025-12-12T00:00:00Z Content type: release Language: en Sources: [Falco - Falco](), [Falco - The Falco blog]() Topics: [Falco](), [Security](), [Package manager](), [releases](), [apt]() Tags: [announcements](), [apt](), [falco](), [import](), [installation](), [releases](), [rotation](), [rsa](), [security]() ### AI overview Falco maintainers are rotating the 4096-bit RSA GPG key used to sign official RPM and DEB packages because the existing key expires on January 17, 2026. The transition uses a soft launch followed by a hard cut-over, and existing users should update their keyrings before January 12, 2026. ### Source excerpt The GPG key used to sign official Falco packages (RPM and DEB) is set to expire on January 17, 2026. To ensure the security and continuity of our software distribution, the Falco maintainers will be rotating to a new 4096-bit RSA key. We have designed a two-phase "Soft Launch" strategy to make this transition as smooth as possible, providing a one-month transition window before the old key is retired. The Rotation Plan To avoid immediate disruption, we are rolling out the new key in two distinct phases. You can follow the detailed progress in our tracking issue #3750. Phase 1: Soft Launch (Dec 12, 2025) What happens: The new GPG key has been published and added to our repository configuration. Dev Builds: Will begin using the New Key immediately. Stable Builds: No stable releases are planned for this phase. If any hotfixes are released, they will be signed with New Key as well. Key Bundle: The official key URL has been updated to serve a bundle containing both the Old (valid) and New (valid) keys. Phase 2: Hard Cut-Over (Jan 12-17, 2026) What happens: This is the maintenance window where we fully switch to the new key. Mass Resign: All existing stable packages on download.falco.org will be resigned with the New Key. Revocation: The Old Key will be officially revoked and removed from the active bundle. Impact: If you have not updated your keyring by this date, your package manager (apt or yum) will reject updates with a signature verification error. Action Items for Users We strongly recommend all users update their GPG keyring before January 12, 2026 to avoid interruption. New Users If you are installing Falco for the first time following our Install on a host (DEB,RPM) instructions, no action is required. The installation process will guide you to fetch the new key bundle, ensuring you are ready for both phases. Existing Users If you have an existing Falco installation, you must manually import the new key. We have updated the key file at our standard URL to includ ## How to Identify the Package Manager of a Linux System DevFeed: [How to Identify the Package Manager of a Linux System]() Original publisher: [Read original article]() Author: Umara Mushtaq Published: 2025-07-14T02:13:11Z Content type: tutorial Language: en Sources: [Baeldung - Linux]() Topics: [Package Management](), [Linux](), [apt](), [Bash](), [Scripting, bash](), [Ubuntu](), [Automation](), [Debian](), [Arch Linux](), [dnf](), [Fedora](), [pacman]() Tags: [apt](), [automation](), [bash](), [debian](), [dependency](), [dnf](), [efficiency](), [errors](), [how-to](), [installation](), [linux](), [linux-how-to](), [package-management](), [package-management-scripting-apt-dnf-pacman-snap-yum](), [pacman](), [scripting](), [snap](), [ubuntu]() ### AI overview This tutorial explains how to identify the package manager used by a Linux system. It covers inferring the manager from the distribution, checking distribution metadata with /etc/os-release or lsb_release, verifying an installed manager with which, and using Bash scripts to detect package managers in automated or multi-distribution environments. ### Source excerpt Learn different ways to guess or identify the default package manager of a Linux system. The post How to Identify the Package Manager of a Linux System first appeared on Baeldung on Linux. Related Stories How to Check for Available Package Updates in Linux How to Properly Install Valgrind? Background Jobs in a Loop in Bash ## Using \`make\` to compile C programs (for non-C-programmers) DevFeed: [Using \`make\` to compile C programs (for non-C-programmers)]() Original publisher: [Read original article]() Author: Julia Evans Published: 2025-06-10T00:00:00Z Content type: tutorial Language: en Sources: [Julia Evans]() Topics: [C](), [make](), [Compiler](), [Package manager](), [gcc](), [apt](), [Xcode](), [C++]() Tags: [apt](), [building](), [c](), [c-plus-plus](), [command-line](), [compiler](), [debian](), [dependencies](), [gcc](), [libraries](), [linux](), [mac](), [make](), [packages](), [xcode]() ### AI overview A beginner-oriented guide to compiling C programs from source, covering compiler installation, dependency discovery, and build tools on Ubuntu and macOS. ### Source excerpt I have never been a C programmer but every so often I need to compile a C/C++ program from source. This has been kind of a struggle for me: for a long time, my approach was basically "install the dependencies, run make, if it doesn't work, either try to find a binary someone has compiled or give up". "Hope someone else has compiled it" worked pretty well when I was running Linux but since I've been using a Mac for the last couple of years I've been running into more situations where I have to actually compile programs myself. So let's talk about what you might have to do to compile a C program! I'll use a couple of examples of specific C programs I've compiled and talk about a few things that can go wrong. Here are three programs we'll be talking about compiling: paperjam sqlite qf (a pager you can run to quickly open files from a search with rg -n THING | qf) step 1: install a C compiler This is pretty simple: on an Ubuntu system if I don't already have a C compiler I'll install one with: sudo apt-get install build-essential This installs gcc, g++, and make. The situation on a Mac is more confusing but it's something like "install xcode command line tools". step 2: install the program's dependencies Unlike some newer programming languages, C doesn't have a dependency manager. So if a program has any dependencies, you need to hunt them down yourself. Thankfully because of this, C programmers usually keep their dependencies very minimal and often the dependencies will be available in whatever package manager you're using. There's almost always a section explaining how to get the dependencies in the README, for example in paperjam's README, it says: To compile PaperJam, you need the headers for the libqpdf and libpaper libraries (usually available as libqpdf-dev and libpaper-dev packages). You may need a2x (found in AsciiDoc) for building manual pages. So on a Debian-based system you can install the dependencies like this. sudo apt install -y libqpdf-dev libpaper-dev ## Mobian Security Update #1 DevFeed: [Mobian Security Update #1]() Original publisher: [Read original article]() Author: Mobian team Published: 2023-08-31T02:00:00Z Content type: release Language: en Sources: [Mobian's Blog]() Topics: [Security](), [vulnerability](), [apt](), [Package manager](), [upgrade]() Tags: [apt](), [packages](), [permissions](), [root](), [security](), [update](), [vulnerability]() ### AI overview The Mobian Team released a security update for a local vulnerability in Bookworm images. Some files had global write permissions, including files managing apt configuration, creating a possible privilege-escalation path to root for a local user with access to an unlocked or already compromised device. Mobian users should upgrade the specified mobian-tweaks-common package. ### Source excerpt The Mobian Team have recently released a security update fixing a local vulnerability caused by a bug in our Bookworm images. User Action Required Mobian users must install the following package in order to address the issues described in this post. A normal upgrade which can be done using sudo apt update && sudo apt upgrade or via Gnome Software will take care of this. For Bookworm users: mobian-tweaks-common, version 0.5.6+deb12u1 For Trixie and Staging users: mobian-tweaks-common, version 0.5.9 These packages include an install script which fixes the permissions on the effected files. They are currently in the staging and bookworm-updates repositories and will migrate to trixie and bookworm in the coming week. Summary The Bookworm images released earlier this year had a small number of files with global write permissions. As two of these files manage the configuration of the apt package manager, they provide an attacker with a useful privilege escalation method. This issue seems to only affect the released Bookworm images, though a full audit of weekly images has not been undertaken. Users who installed on Trixie were likely never effected. Impact These files could allow a local user to gain root access to the device by modifying them and waiting for the user to install an attacker provided update. This attack would require access to an unlocked or otherwise already compromised device as a standard user. There is no way to carry this attack out remotely or on a locked device. Indicators of Compromise Users can verify the current configuration of their system by checking the relevant files. Changes to these files to not immediately mean the device has been compromised, but may warrant further investigation. /etc/apt/sources.list.d/mobian.list should contain (potentially with a different distribution): deb http://repo.mobian.org/ main non-free-firmware /etc/apt/trusted.gpg.d/mobian.gpg can be verified using the command shasum -c checksum.txt aganist ## Using WSL and Let's Encrypt to create Azure App Service SSL Wildcard Certificates DevFeed: [Using WSL and Let's Encrypt to create Azure App Service SSL Wildcard Certificates]() Original publisher: [Read original article]() Author: Scott Hanselman Published: 2023-06-27T17:17:25Z Content type: tutorial Language: en Sources: [Scott Hanselman]() Topics: [Azure](), [Windows Subsystem for Linux](), [SSL](), [openssl](), [apt](), [pip]() Tags: [apt](), [azure](), [certificates](), [dns](), [install](), [openssl](), [password](), [private-key](), [ssl](), [windows](), [wsl]() ### AI overview This tutorial explains how to use Certbot in Windows Subsystem for Linux with Let's Encrypt to create a wildcard certificate, convert it to a password-protected PFX containing the certificate chain, and upload it to Azure App Service. It also describes importing and exporting the certificate in Windows before updating the App Service binding. ### Source excerpt There are many let's encrypt automatic tools for azure but I also wanted to see if I could use certbot in wsl to generate a wildcard certificate for the azure Friday website and then upload the resulting certificates to azure app service. Azure app service ultimately needs a specific format called dot PFX that includes the full certificate path and all intermediates. Per the docs, App Service private certificates must meet the following requirements: Exported as a password-protected PFX file, encrypted using triple DES. Contains private key at least 2048 bits long Contains all intermediate certificates and the root certificate in the certificate chain. If you have a PFX that doesn't meet all these requirements you can have Windows reencrypt the file. I use WSL and certbot to create the cert, then I import/export in Windows and upload the resulting PFX. Within WSL, install certbot: sudo apt update sudo apt install python3 python3-venv libaugeas0 sudo python3 -m venv /opt/certbot/ sudo /opt/certbot/bin/pip install --upgrade pip sudo /opt/certbot/bin/pip install certbot Then I generate the cert. You'll get a nice text UI from certbot and update your DNS as a verification challenge. Change this to make sure it's two lines, and your domains and subdomains are correct and your paths are correct. sudo certbot certonly --manual --preferred-challenges=dns --email YOUR@EMAIL.COM --server https://acme-v02.api.letsencrypt.org/directory --agree-tos --manual-public-ip-logging-ok -d "azurefriday.com" -d "*.azurefriday.com" sudo openssl pkcs12 -export -out AzureFriday2023.pfx -inkey /etc/letsencrypt/live/azurefriday.com/privkey.pem -in /etc/letsencrypt/live/azurefriday.com/fullchain.pem I then copy the resulting file to my desktop (check your desktop path) so it's now in the Windows world. sudo cp AzureFriday2023.pfx /mnt/c/Users/Scott/OneDrive/Desktop Now from Windows, import the PFX, note the thumbprint and export that cert. Import-PfxCertificate -FilePath "AzureFriday2023.pfx" - ## How to Upgrade Proxmox 7 to 8 DevFeed: [How to Upgrade Proxmox 7 to 8]() Original publisher: [Read original article]() Author: Techno Tim Published: 2023-06-24T15:00:00Z Content type: tutorial Language: en Sources: [Techno Tim]() Topics: [Proxmox](), [Debian](), [apt](), [Linux](), [Kernel](), [qemu](), [ceph](), [x86](), [Text-based user interface]() Tags: [apt](), [debian](), [how-to](), [kernel](), [linux](), [new-features](), [proxmox](), [qemu](), [upgrade](), [virtual-machines](), [x86]() ### AI overview A practical guide to upgrading a Proxmox server from version 7 to version 8. It covers backups, checking the installed version, running upgrade checks, applying current updates, and updating Debian and Proxmox apt repositories to Bookworm. ### Source excerpt Proxmox 8.0 has been released (June, 22, 2023) and includes several new features and a Debian version upgrade. Among the changes are: Debian 12 "Bookworm", but using a newer Linux kernel 6.2 QEMU 8.0.2, LXC 5.0.2, ZFS 2.1.12 Optional Text mode installer (TUI) New default CPU type x86-64-v2-AES for VMs Ceph Quincy 17.2.6 and a new, stable Ceph Enterprise repository Authentication r... ## The non-free-firmware repository DevFeed: [The non-free-firmware repository]() Original publisher: [Read original article]() Author: Mobian team Published: 2023-03-11T12:00:00Z Content type: tutorial Language: en Sources: [Mobian's Blog]() Topics: [Debian](), [apt]() Tags: [config](), [debian](), [devices](), [firmware](), [free-software](), [install](), [network](), [packages](), [upgrade](), [usb]() ### AI overview Mobian users of PinePhone and PinePhone Pro should update their Debian APT configuration to include the non-free-firmware repository section. Debian moved firmware packages there, including Wi-Fi firmware packages needed by these devices. The article also explains how to update the system and manually install firmware if network access is unavailable. ### Source excerpt PinePhone and PinePhonePro Owners (and others), please change your config PinePhonePro users might get nagging messages about packages being held back right now... TL;DR: Please add the non-free-firmware section to the Debian repository line in /etc/apt/sources.list. Introducing the non-free-firmware section UPDATE: slightly reworded first paragraph. Piggybacking on Debian is great, but it also means we need to track changes that occur in Debian. The Debian project has decided to include non-free-firmware in their installer images for hardware enablement reasons and a better out of the box user experience. Therefore firmware file have been moved out of the non-free section and into the new non-free-firmware section in the debian repository. Why does this matter to Mobian users? The Wifi firmware for the PinePhone and PinePhonePro has migrated to the upstream Debian repository and the firmware-realtek-rtl8723cs-bt (PinePhone) and firmware-brcm80211 (PinePhone Pro) packages are now in the new non-free-firmware section. This means at least PinePhonePro users need to add that section now, but it does not hurt for other devices too and we recommend everyone to make this change. So mobian users, head over to the file /etc/apt/sources.list and edit the line starting with deb http://deb.debian.org. It should end with (some of) the sections main non-free. Just change non-free to non-free-firmware, or add non-free-firmware (delimited by a space) at the end of that line if you still want access to non-free software which are not only firmware packages. Finally, apt update && apt upgrade and you should be on the latest firmware on the upstream Debian repository. If you've lost network access on your PinePhone Pro, you can download the package manually using the above link (or apt download firmware-brcm80211 on another Debian Bookworm machine), transfer the file to your phone over USB and install it manually with dpkg -i firmware-brcm80211_20230210-2_all.deb. ## Analysis of Malware Distributed Through Matrix Rooms to Mobile Linux Users DevFeed: [Analysis of Malware Distributed Through Matrix Rooms to Mobile Linux Users]() Original publisher: [Read original article]() Author: Mobian team Published: 2022-02-11T00:00:00Z Content type: article Language: en Sources: [Mobian's Blog]() Topics: [Malware](), [Mobile](), [Security](), [vulnerability](), [Matrix](), [apt]() Tags: [apt](), [malware](), [matrix](), [mobile](), [security](), [vulnerability]() ### AI overview This article analyzes malware distributed through Matrix rooms as installable packages for postmarketOS, Mobian, and Arch/Manjaro. It examines the Debian package variant, its metadata and post-install script, and explains how execution with root privileges enables the malware to copy files and run its payload. ### Source excerpt As you may be aware, a malicious person tried to spread malware through many Matrix rooms used by mobile Linux users and developers, partly taking advantage of a known vulnerability in the stock modem firmware. Here's a quick analysis of how this malware was supposed to operate. Disclaimer: while being enthusiastic nerds, none of the Mobian developers is a security expert. We hope this post will provide interesting information to the community but it shouldn't be considered an exhaustive security report. Please also note this was by no means a Mobian-only effort: in this post, we're reporting the findings of the mobile Linux community as a whole, not claiming we did it all by ourselves. A bit of context The malware was uploaded to Matrix chat rooms in the form of an installable binary package: .apk for postmarketOS .deb for Mobian .pkg.tar.zst for Arch/Manjaro Multiple variants were posted such as coathanger or pp-tweaks but, a few cosmetic differences aside, they all work in the same way and embed the same malicious payload. In the rest of this post, we'll take a closer look at the .deb package (obviously) of the pp-tweaks variant. This file is an actual package suitable for installation using dpkg or apt. Its package metadata look valid and contain the following description: Description: Tweaks for PinePhone and PinePhone Pro as well as various other devices such as the Oneplus 6 and the Poco F1 Although it's obvious that the package has been handcrafted rather than generated using the usual Debian packaging tools (no checksums included in the package metadata, for example), and except for the contents of the Maintainer field (layla289, maybe an Eric Clapton fan?), the package doesn't look harmful at this point. The following files are installed from this package: /usr/bin/pp-tweaks-gtk /usr/lib/pp-tweaks-postinstall It also contains the following post-install script, automatically run by dpkg once the package files have been installed to the system: #!/bin/sh /us ## Mobian recommends upgrading from Debian Bullseye to Bookworm DevFeed: [Mobian recommends upgrading from Debian Bullseye to Bookworm]() Original publisher: [Read original article]() Author: Mobian team Published: 2021-12-24T00:00:00Z Content type: release Language: en Sources: [Mobian's Blog]() Topics: [Debian](), [upgrade](), [apt](), [Software]() Tags: [apt](), [debian](), [good](), [updates](), [upgrade]() ### AI overview Mobian recommends that users upgrade from Debian Bullseye to Bookworm to access newer software, including GTK4, Megapixels 1.3, and GNOME 41. The article explains the apt configuration changes and cautions users to back up their home directory and review package changes during the upgrade. ### Source excerpt Now that the dust has settled on Debian's new testing repository we are focusing our efforts on Bookworm. This long overdue blog post is a summary of what to expect in the coming updates to Mobian. New Software As we outlined in To Bullseye and Beyond, Bookworm is where Mobian and Debian will be focusing their efforts for new software. To date, this has resulted in the introduction of GTK4 and, most importantly for PinePhone users, Megapixels 1.3 which brings a fully hardware-accelerated camera viewfinder. Additionally, Debian moved to GNOME 41 over the past few months, which provides newly adaptive versions of core software such as GNOME Software and GNOME Control Center. The latter reduces significantly the number of overflowing panels and starts significantly faster. All of these goodies either come directly from upstream Debian or rely on newer packages not available in Bullseye. The Mobian team will not be backporting these, so we recommend upgrading to Bookworm to get access to them. How do I get access to these new packages The good news is, if you have already switched to Bookworm, these updates are just an apt upgrade away. If you've been waiting for the dust to settle on the Bullseye release, now would be a good time to move forward. While the turnover of new packages in Debian Testing is always high, the major post-Bullseye transitions (such as GNOME and libc) have completed, mostly smoothly. If you would like to upgrade, simply replace bullseye with bookworm in both /etc/apt/sources.list and /etc/apt/sources.list.d/mobian.list. Then, the usual apt update and apt dist-upgrade combo will pull in all the latest packages and upgrade your device to Bookworm. We highly recommend you backup your home directory prior to performing the upgrade. In case you originally flashed your device with an image older than April 26th, 2021, you will have to edit /etc/apt/sources.list.d/extrepo_mobian.sources instead of /etc/apt/sources.list.d/mobian.list, replacing Suites: m ## Install Docker Engine, containerd, and Docker Compose on Ubuntu DevFeed: [Install Docker Engine, containerd, and Docker Compose on Ubuntu]() Original publisher: [Read original article]() Author: Techno Tim Published: 2021-08-14T16:00:00Z Content type: tutorial Language: en Sources: [Techno Tim]() Topics: [Docker](), [Docker Compose](), [Ubuntu](), [apt]() Tags: [apt](), [compose](), [docker](), [how-to](), [install](), [ubuntu]() ### AI overview A tutorial for installing Docker Engine, containerd, and Docker Compose on Ubuntu. It advises removing an existing Docker installation first and includes repository setup and version-checking steps. ### Source excerpt This guide will walk you through how to Install Docker Engine, containerd, and Docker Compose on Ubuntu. If you have an existing version of Docker install, it is best to remove it first.See the Cleaning Up If you're installing this on Debian, see Docker's Debian Install Guide Install Set up Docker's apt repository. # Add Docker's official GPG key: sudo apt-get update sudo apt-get install c... ## The staging Mobian distro DevFeed: [The staging Mobian distro]() Original publisher: [Read original article]() Author: Mobian team Published: 2021-03-15T00:00:00Z Content type: tutorial Language: en Sources: [Mobian's Blog]() Topics: [Debian](), [apt]() Tags: [apt](), [debian](), [distro](), [packages](), [repository](), [stable](), [staging](), [switching](), [testing]() ### AI overview This tutorial explains Mobian staging, a newer Mobian package repository layered over Debian bullseye. It describes how to switch to the staging repository and distinguish packages from Mobian and Debian. ### Source excerpt Most of us just want their phone to be working. But some like to be more on the edge of things, trying out the newest bugsfeatures. The recently announced staging distribution allows users to do just that. Read further to learn its purpose and how to enable it. Mobian is an overlay over the regular Debian bullseye repository. Its package source is configured in /etc/apt/sources.list with a single line: deb http://deb.debian.org/debian bullseye main. 1 Currently the (relatively) stable Mobian overlay is configured in /etc/apt/sources.list.d/mobian.list containing the following: deb http://repo.mobian.org/ bullseye main non-free If you had flashed your device with an image older than April 26th, 2021, you may have a file named /etc/apt/sources.list.d/extrepo_mobian.sources instead, containing the following: Types: deb Architectures: amd64 arm64 armhf Uris: http://repo.mobian.org/ Suites: mobian Components: main non-free Signed-By: /var/lib/extrepo/keys/mobian.asc Recently we introduced Mobian staging, in which we include packages that are pretty new and/or might need a bit more testing. Mobian staging is a full Mobian repository, so it includes everything that the "normal" repository includes and a bit more (and some packages a bit newer). By switching to it, you agree to name your firstborn Debian and to never eat cookies again after 3pm! So think twice before you do it! The easiest way you can switch to using this repository is by simply changing the word bullseye to staging in /etc/apt/sources.list.d/mobian.list, or the line Suites: mobian to Suites: staging in /etc/apt/sources.list.d/extrepo_mobian.sources. This way, you will be getting all your Mobian packages from https://repo.mobian.org/dists/staging instead of https://repo.mobian.org/dists/mobian. Some of the packages you install will be from the staging Mobian repo and most will be coming directly and unmodified from one of the Debian mirrors. How do I find out if a package comes from Debian or Mobian? Great ## Issues and hurdles when performing the initial upgrade DevFeed: [Issues and hurdles when performing the initial upgrade]() Original publisher: [Read original article]() Author: Mobian team Published: 2021-02-09T12:53:19Z Content type: tutorial Language: en Sources: [Mobian's Blog]() Topics: [upgrade](), [apt](), [Authentication](), [Package manager](), [Mobile](), [Terminal](), [Debian](), [screen]() Tags: [apt](), [authentication](), [changes](), [debian](), [dependencies](), [error](), [installation](), [pitfalls](), [terminal](), [upgrade]() ### AI overview This Mobian post explains pitfalls during the initial upgrade of a PinePhone. It describes a PAM issue that can temporarily prevent PIN unlocking before rebooting and recommends rebooting after the upgrade. It also recommends using a manual terminal update with Debian's apt package manager because the graphical Software application may fail with unmet-dependency errors during the initial update. ### Source excerpt Dear Mobian CE owners, congratulations on receiving your mobile phone. We hope you will like Mobian and we hope that you will be helping us to make it even better. We are writing this post as the initial upgrade is rather tricky and there are a few pitfalls when performing it. We do know that real men and women don't read manuals, but please read this post carefully in order to not lock yourself permanently out of your phone (just an example of what can happen if you don't read this...). Most importantly, we want to inform you, that there is a minor issue with PAM (pluggable authentication module) when upgrading the preflashed image. It was upgraded in an incompatible manner, and when the lockscreen of your phone is invoked after upgrading but before rebooting, it will not accept your PIN anymore (fortunately in most cases, a simple reboot makes it work again). So do not worry, your installation is not broken! Therefore: After upgrading your pinephone for the first time it is highly recommended to reboot the device after the upgrade has finished. And keeping the screen unlocked during the initial upgrade by: touching the screen frequently (get used to the feeling :-)) or temporarily disabling the automatic lockscreen in the settings. Otherwise you run the risk of not being able to unlock your device once the screen has been locked. The second major issue during the initial upgrade is related to the graphical software updater, called "Software". The Software application can usually keep the software on your pinephone up-to-date and will prompt you to reboot after an update. On the initial update with currently more than 600 package changes compared to the factory image, it chokes and struggles, though. You will get some mysterious "Cannot update due to unmet dependencies" error in the software app if you try. So for the initial update, we recommend performing a manual update in the terminal (a great way to familiarize yourself with the terminal and Debian's package man ## Set up and update Ansible for SSH-based automation DevFeed: [Set up and update Ansible for SSH-based automation]() Original publisher: [Read original article]() Author: Techno Tim Published: 2020-12-26T14:00:00Z Content type: tutorial Language: en Sources: [Techno Tim]() Topics: [Ansible](), [Automation](), [DevOps](), [ssh](), [apt]() Tags: [ansible](), [apt](), [automation](), [devops](), [homelab](), [quick-start](), [ssh]() ### AI overview A tutorial on setting up Ansible, checking its installed version, updating it when necessary, and using it for automation over SSH without installing agents or clients. ### Source excerpt Ansible.Need I say more? Well, maybe, if you've never heard of it. Ansible is a simple IT / DevOps automation that anyone can use.You can Automate anything with an SSH connection and WITHOUT installing any agents or clients. Join me as we set up, configure and start automating with Ansible! ๐Ÿ“บ Watch Video install sudo apt update sudo apt install ansible sudo apt install sshpass Note: ... ## Initial Linux Server Setup: Updates, Security, Tools and Configuration DevFeed: [Initial Linux Server Setup: Updates, Security, Tools and Configuration]() Original publisher: [Read original article]() Author: Techno Tim Published: 2020-10-31T14:00:00Z Content type: tutorial Language: en Sources: [Techno Tim]() Topics: [Linux](), [configuration](), [Security](), [apt]() Tags: [apt](), [config](), [homelab](), [linux](), [tutorial]() ### AI overview A tutorial covering initial Linux server setup steps, including updates, unattended-upgrades configuration, user and SSH key setup, static IP configuration, storage resizing, and time zone checks. ### Source excerpt After setting up my Linux servers, there are a few things I do before I use them for their intended purpose.This ranges from security, to tools, to config.Join me as we set up our first Linux server in this tutorial and walk through setting it up proper (and maybe some bonus items sprinkled in). ๐Ÿ“บ Watch Video Update sudo apt-get update sudo apt-get upgrade Reconfigure unattended-upgrade... ## Running Pi-hole on Docker and Kubernetes with Rancher DevFeed: [Running Pi-hole on Docker and Kubernetes with Rancher]() Original publisher: [Read original article]() Author: Techno Tim Published: 2020-05-30T14:00:00Z Content type: tutorial Language: en Sources: [Techno Tim]() Topics: [Pi-hole](), [Docker](), [Kubernetes](), [rancher](), [Ubuntu](), [apt]() Tags: [apt](), [docker](), [how-to](), [install](), [kubernetes](), [password](), [rancher](), [self-hosted](), [ubuntu]() ### AI overview A tutorial on running Pi-hole with Docker and Kubernetes using Rancher, including Ubuntu setup, DNS configuration, and password setup. ### Source excerpt We know you've heard of Pihole and we know you are probably aware of how to install it but... have you tried running it on Docker and Kubernetes using Rancher? Have you configured it for pfSense? Don't worry, I figured out all the hard stuff for you.So let's consolidate some hardware and services. ๐Ÿ“บ Watch Video Ubuntu Fix sudo apt-get update sudo apt-get install resolvconf sudo nano /e... ## Upgrading Python and Pip and VirtualEnv on Ubuntu DevFeed: [Upgrading Python and Pip and VirtualEnv on Ubuntu]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2020-04-03T00:00:00Z Content type: tutorial Language: en Sources: [Scott Johnson]() Topics: [Python](), [Ubuntu](), [pip](), [apt]() Tags: [apt](), [install](), [python](), [ubuntu](), [upgrade]() ### AI overview A brief tutorial on upgrading Python, pip, and virtualenv on Ubuntu after a Python package installation ends with a segmentation fault. ### Source excerpt I found myself this morning trying to get a Python stack running on an Ubuntu instance only to hit this crap: Installing collected packages: numpy, pytz, six, python-dateutil, pandas, nltk, pyparsing, cycler, kiwisolver, matplotlib, kafka-python, pyyaml, murmurhash, zipp, importlib-metadata, catalogue, plac, tqdm, setuptools, srsly, cymem, preshed, blis, wasabi, thinc, idna, urllib3, certifi, chardet, requests, spacy, pluggy, attrs, py, more-itertools, wcwidth, packaging, pytest, langdetect, spacy-langdetect, editorconfig, jsbeautifier, docutils, jmespath, botocore, s3transfer, boto3, torch, dataclasses, tokenizers, click, joblib, regex, sacremoses, filelock, sentencepiece, transformers, scipy, scikit-learn, gunicorn, WebOb, firefly-python, pycparser, cffi, zstandard, lefthook, termcolor, fire, redis, sseclient, absl-py, protobuf, markdown, pyasn1, pyasn1-modules, cachetools, rsa, google-auth, tensorboard-plugin-wit, werkzeug, grpcio, wheel, oauthlib, requests-oauthlib, google-auth-oauthlib, tensorboard, future, pytorch-lightning Segmentation fault (core dumped) So I guess it is time to do the Python upgrade dance. Here you go: pip3 install --upgrade pip sudo apt-get update && sudo apt-get upgrade sudo apt-get install python3.7 sudo pip3 install --upgrade virtualenv Stack Overflow References Pip upgrade. Python Upgrade [Next page]()