Find similar content

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

#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

⚠️ A new #Linux flaw mirrors Dirty Pipe—but adds cross-container impact. “Copy Fail” (CVE-2026-31431) lets any local user overwrite cached system files and run them as root. No race condition. Works across major Linux distros since 2017. 🔗 Read → https://thehackernews.com/2026/04/new-linux-copy-fail-vulnerability.html

🚨 China-linked APT UAT-9244 has been targeting telecom networks in South America since 2024. Cisco Talos uncovered 3 new implants across Windows, #Linux, and edge devices—used for persistence, command control, and large-scale brute-force scanning. 🔗 Inside TernDoor, PeerTime, and BruteEntry → https://thehackernews.com/2026/03/china-linked-hackers-use-terndoor.html

#Linux 🛡 AdGuard Home 安装及使用指北 📝 阅读原文：博客 | 少数派 一个好产品，需要广而告之，才能活下去，一部好影片，需要广而告之，才有好的票房。从口口相传发展到千人千面，广告已从单向的传播形式发展成为基于个人喜好专门投放，用户的接受权由主动变为被动 但当广告时时刻刻充斥在我们的生活，新闻有贴片广告，朋友圈有互动广告，电视剧有片头广告，小网站上还有~~性感荷官~~在线发牌，如果你有在多设备上对去除广告的需求，AdGuard Home 或许是一个不错的选择，它能够给你带来一个清爽的网络世界 以往我们习惯在电脑浏览器上使用 AdBlock Plus、AdGuard、Ghostery、uBlock Origin 之类的广告拦截与隐私防护插件，从而去除网页上扰人的广告。对于 Android 与 iOS，受限于系统权限、过滤模式，想在手机上「找到一块净土」，需要花费一番功夫 AdGuard Home 是 AdGuard 开源的一个私人 DNS 服务端，只需在网关部署，即可实现全局域网的广告拦截与隐私反追踪。在 DNS 解析的过程中，匹配规则库内的 Url 进行拦截，同时在客户端中，还可以通过自定义过滤规则实现网页 DOM 的拦截 👉 文章目录 - 广告拦截 / 反追踪插件是如何起作用的 - 如何安装与配置 AdGuard Home - 推荐的过滤规则与上游 DNS 服务器 - 在安装与使用过程中的常见问题 📘 关联阅读 1️⃣AdGuard Home Wiki 2️⃣想获得「干净」的网页浏览体验？你需要这份全平台去广告指南 3️⃣The Coalition for Better Ads - Better Ads Standards 频道：@NewlearnerChannel

#linux Pandoc - Markdown界的瑞士军刀 可以将 Markddown 转换成各个格式的文档 可以调整输出文档时的字体大小 可以调整输出文档时的图片大小 …… 安装: brew install pandoc 官网 https://pandoc.org 使用参考：http://zhouyichu.com/misc/Pandoc/