Find similar content

Google is throwing #Chromium browser under the bus, as it is removing the Sync support from it and removing the API keys which it gave to Linux distributions. https://hackaday.com/2021/01/26/whats-the-deal-with-chromium-on-linux-google-at-odds-with-package-maintainers/

http://sahandsaba.com/understanding-asyncio-node-js-python-3-4.html I spent this summer working on a #web_platform running on #Node.js. This was the first time I worked full-time with Node.js and one thing that became quite apparent after a few weeks of working with it was that many developers, including myself at the time, lack clarify on exactly how the #asynchronous features of Node.js work, and how they are implemented at a lower level. Since I believe the only way to use a platform efficiently is to have a clear understanding of how it works, I decided to dig deeper. This curiosity also made me start playing around with implementing similar asynchronous features in other languages, in particular Python, it being my go-to language for experimenting and learning. This led me to Python 3.4's asynchronous IO library asyncio in particular, which intersected with my already existing interest in coroutines (see my post on combinatorial generation using coroutines in Python.) This post is about exploring the questions and answers that came up while I was learning more about this subject, which I hope can help clarify and answer some questions for others as well.

Take the following quiz about the #Linux command line (20 questions) and see how much you would score in these very basic questions! https://quiz.fosspost.org/quiz/introduction-to-linux-command-line-quiz/

Take the following quiz about software management in #Linux! Learn the basics of apt/dnf/zypper/rpm/dpkg in few minutes: https://quiz.fosspost.org/quiz/software-management-from-the-command-line/

Linux Kernel 5.9 was released, get to know the new features from Kernel Newbies website: https://kernelnewbies.org/Linux_5.9 #Linux

Cool Chrome DevTools tips and tricks you wish you knew already. #article#tutorial#chrome#coding @thedevs https://kutt.it/mtt3bx

#Linux devices have a unique identifier called machine-id. Here is how to change it. Posted on February 24, 2021 What is a machine-id, and why should you randomize it? From the machine-id man pages, it is defined as: This ID uniquely identifies the host. It should be considered “confidential”, and must not be exposed in untrusted environments, in particular on the network. If a stable unique identifier that is tied to the machine is needed for some application, the machine ID or any part of it must not be used directly. https://www.man7.org/linux/man-pages/man5/machine-id.5.html In an effort to promote privacy, having a unique and unchanging identifier tied to your device seems like the wrong approach. It’s quite possible that poorly coded or even maliciously coded software could fetch this ID from your system. Let’s make sure that even if that does happen, that the value is constantly changing so that your device can not be uniquely identified as your device. This is an incredibly simple and quick adjustment to your default Linux system. What we’re doing is showing you how to either adjust this value manually by hand, or by running a cronjob to change this value every minute with a new, randomized value. Before we begin, a disclaimer: We’ve tested this on our own work desktops and development environments and I’ve tested it on my daily driver desktop. We have not found that anything has ‘broken’ because of this, but this is untested in many environments and may not be suitable for your use. It’s always reversible if you later wish to continue with a single, uniquely identifying ID attached to your device(s). Debian / Ubuntu systems To check your machine-id, open up your terminal and enter the following: cat /etc/machine-id The output should look a little something like this: a9976154f0084a3782892638656ad9fd You’ll note that this value is also stored in /var/lib/dbus/machine-id and that a symlink between the two exist. Any change to one file, will be reflected in the other. me@virtbox-testing:~$ cat /etc/machine-id a9976154f0084a3782892638656ad9fd me@virtbox-testing:~$ cat /var/lib/dbus/machine-id a9976154f0084a3782892638656ad9fd If you reboot your device, you’ll notice that this value remains unchanged. So, let’s change it ourselves! Method 1: Manually. Method 2 is automatically, every minute, as ran by a cron-job. If you don’t want to fully commit to that, you can change your machine-id by hand manually whenever you feel like it. Step 1, remove the old machine-id file. sudo rm /etc/machine-id Step 2, recreate the machine-id file. sudo systemd-machine-id-setup Step 3, confirm that /etc/machine-id (and /var/lib/dbus/machine-id) now show a new value, different from the original. cat /etc/machine-id && cat /var/lib/dbus/machine-id That’s it! You should see two lines in your output with matching IDs that differ from the original machine-id you had in the beginning. me@virtbox-testing:~$ cat /etc/machine-id && cat /var/lib/dbus/machine-id a78badce3e73beced163bbef7e55232a a78badce3e73beced163bbef7e55232a You’ve changed your device’s uniquely identifying machine-id. This change will survive device reboots and will remain the same until you create a new one. Method 2: Changing every 1 minute, automatically. If the above didn’t satisfy your needs, than feel free to automate the creation of a new machine-id by creating a cronjob entry that will generate a new ID every minute. Step 1, open up your crontab file. sudo crontab -e Step 2, enter at the bottom of the file the following: */1 * * * * sudo rm /etc/machine-id && sudo systemd-machine-id-setup Save and Exit. Step 3, wait a minute and confirm that your machine-id value has changed: cat /etc/machine-id && cat /var/lib/dbus/machine-id You should see two new matching values, that differs from the original value you had at the start. Wait a minute and run the step 3 command again, and you’ll see that these values have changed.

https://archive.is/0OLMG how to change #linux machine-id

🚨 QLNX, a previously undocumented #Linux RAT, is targeting developers and DevOps systems to steal npm, PyPI, AWS, Kubernetes, Docker, and CI/CD credentials. The malware uses fileless execution, PAM backdoors, eBPF rootkits, and 58 remote commands to maintain covert access and hijack software supply chains. Learn more about QLNX here: https://thehackernews.com/2026/05/quasar-linux-rat-steals-developer.html

⚠️ A new #Linux flaw is now under active exploitation. CISA added CVE-2026-31431 to its KEV list. The bug lets low-privilege users gain full root access. Patches released. Fix deadline: May 15, 2026. Read: https://thehackernews.com/2026/05/cisa-adds-actively-exploited-linux-root.html