<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Danoss777 on Medium]]></title>
        <description><![CDATA[Stories by Danoss777 on Medium]]></description>
        <link>https://medium.com/@danoss777?source=rss-779aba551497------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Rx2GxSz67vpUMZq3ajuRyA.png</url>
            <title>Stories by Danoss777 on Medium</title>
            <link>https://medium.com/@danoss777?source=rss-779aba551497------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 20:24:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@danoss777/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Xbox Controllers on Fedora Linux 2]]></title>
            <link>https://medium.com/@danoss777/xbox-controllers-on-fedora-linux-2-b04d39039e57?source=rss-779aba551497------2</link>
            <guid isPermaLink="false">https://medium.com/p/b04d39039e57</guid>
            <category><![CDATA[fedora-linux]]></category>
            <category><![CDATA[xbox-linux]]></category>
            <category><![CDATA[linux-gaming]]></category>
            <dc:creator><![CDATA[Danoss777]]></dc:creator>
            <pubDate>Mon, 30 Mar 2026 00:26:03 GMT</pubDate>
            <atom:updated>2026-03-30T00:26:03.656Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oux9yUXIoNlpexzVd5hRmg.png" /></figure><p>Revised and improved version of the original post: <a href="https://danoss.me/categories/linux/xbox-controllers-on-fedora-linux/">Xbox Controllers in Fedora Linux</a></p><p>Normally, Xbox Controllers (in my case, Xbox Core Wireless Gaming Controller — might upgrade in the future) works out of the box. However, if it doesn’t for any reason read below.</p><p>In my case, the Xbox Controller was working normally and stopped working after a major system upgrade. The OS could detect the device (udevadm monitor showed the connection) but Steam didn’t recognize any input from the Controller.</p><h3>Detecting the Problem</h3><ol><li>The controller pairs successfully via Bluetooth or connects via USB.</li><li>The kernel sees the device connecting and disconnecting (via udevadm monitor).</li><li>Steam shows no controller input at all.</li></ol><h3>How Linux Handles Xbox Controllers</h3><p>As everything in Linux, everything is handled through various layers.</p><h3>The Linux Input Stack</h3><p>When you connect a controller to a Linux system, the input goes through various subsystems before it reaches the game. Here’s what happens:</p><ul><li>The controller device connects via a transport layer (USB or Bluetooth)</li><li>The kernel loads the appropriate driver module (kernel module) for that specific device type.</li><li>The driver translates the raw device data into standard Linux input events, which are exposed through device nodes in <strong>/dev/input</strong>.</li><li>Apps like Steam read those device nodes and pass the data to games.</li></ul><p>If one of these layers fails (missing driver, wrong permissions, missing udev rules, etc.) the controller will not work, even if it’s detected by the kernel.</p><h3>USB vs Bluetooth Connections</h3><p>The driver your Xbox controller uses depends on how you connect it, this is important when knowing where to look when troubleshooting.</p><h3>Continue Reading</h3><p><a href="https://danoss.me/categories/linux/xbox-controllers-on-fedora-linux-2/#use-cases-and-drivers">https://danoss.me/categories/linux/xbox-controllers-on-fedora-linux-2</a></p><ul><li>USB vs Bluetooth Connections</li><li>The Input Event Pipeline</li><li>Why Fedora Upgrades Break Xbox Controller Support</li><li>Kernel Module Packaging on Fedora</li><li>What Happens During A System Upgrade?</li><li>Why “udevadm monitor” Is Misleading</li><li>The Fix</li><li>Use Cases and Drivers</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b04d39039e57" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Understanding VPNS Part 3]]></title>
            <link>https://medium.com/@danoss777/understanding-vpns-part-3-38b8ebbdbddd?source=rss-779aba551497------2</link>
            <guid isPermaLink="false">https://medium.com/p/38b8ebbdbddd</guid>
            <category><![CDATA[wireguard-vpn]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[mullvad-vpn]]></category>
            <category><![CDATA[vpn]]></category>
            <dc:creator><![CDATA[Danoss777]]></dc:creator>
            <pubDate>Mon, 30 Mar 2026 00:22:38 GMT</pubDate>
            <atom:updated>2026-03-30T00:22:38.806Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Part 3 of 4…or 5?</strong></p><p>This part is about how corporate or censorship networks use deep packet inspection (DPI) to detect and block VPN traffic and how to hide the fact you are using a VPN.</p><p>Next part will be more practical with use cases, devices, and specific configuration to circumvent censorship.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ohuTXIDsjPMJbdU9rfjpqQ.png" /></figure><blockquote><strong><em>Configuration and examples here are from Mullvad VPN (WireGuard) with Fedora Linux. In the future, I will add examples using Debian-related distros.</em></strong></blockquote><h3>DNS Leaks</h3><p>You installed Mullvad and the VPN is running, everything seems good. Or not?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*irU865PGlRAEKH1Yf8wgqg.png" /></figure><p>Even if you have your VPN up and running, a DNS leak can silently undo the privacy you think you have.</p><p><strong>A DNS leak</strong> happens when your device’s DNS queries bypass the VPN tunnel and are sent to your ISP or other 3rd-party DNS servers, potentially exposing the websites you visit. Your traffic is encrypted, your IP is hidden, but your DNS queries are still mapping your entire browsing session to your ISP’s logs.</p><p>When you visit a website, your device first resolves the domain name into an IP address. That resolution is a DNS query, and it needs to go somewhere. A properly configured VPN tunnels those queries through the encrypted interface and resolves them on the VPN provider’s DNS servers. Your ISP should never see which domains you’re hitting.</p><h3>Why DNS Leaks Happen</h3><p><strong>Culprit 1: systemd-resolved</strong></p><p>On Linux, the culprit is usually systemd-resolved not being configured correctly for the VPN interface.</p><p><strong>systemd-resolved</strong> is a system service built into most modern Linux distros that acts as a centralized DNS resolver for the whole OS. Rather than each application making its own DNS queries directly, they all go through systemd-resolved.</p><p>When the Mullvad app connects, it registers its DNS server (10.64.0.1) and the ~. routing domain with systemd-resolved (essentially telling it: <em>“for all domain lookups, use this interface”</em>). If that registration doesn’t happen correctly, systemd-resolved falls back to whatever DNS it got from DHCP, which is typically your router, which is typically your ISP.</p><p><strong>Continue Reading: </strong><a href="https://danoss.me/categories/security/understanding-vpns-part-3/#whats-next">https://danoss.me/categories/security/understanding-vpns-part-3/t</a></p><ul><li>How Networks Know You’re Using a VPN</li><li>Hiding the Fact You’re Using a VPN</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=38b8ebbdbddd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Understanding VPNs Part 2]]></title>
            <link>https://medium.com/@danoss777/understanding-vpns-part-2-0cab79e8056f?source=rss-779aba551497------2</link>
            <guid isPermaLink="false">https://medium.com/p/0cab79e8056f</guid>
            <category><![CDATA[wireguard]]></category>
            <category><![CDATA[vpn]]></category>
            <category><![CDATA[mullvad-vpn]]></category>
            <category><![CDATA[mullvad]]></category>
            <dc:creator><![CDATA[Danoss777]]></dc:creator>
            <pubDate>Sun, 15 Mar 2026 01:51:00 GMT</pubDate>
            <atom:updated>2026-03-15T01:51:00.224Z</atom:updated>
            <content:encoded><![CDATA[<p>Part 2 of a 3-part series on VPNs.</p><p>This part focuses more in depth on VPNs. I’ll use my actual Mullvad VPN setup on <strong>Fedora Linux</strong> to go through what happens when you connect, how the kernel handles traffic, etc.</p><p><em>This post is not an ad of </em><a href="https://mullvad.net/en"><em>Mullvad</em></a><em>, but just a writing from a happy user.</em></p><h3>What Happens When You Connect</h3><p>Here’s the flow of a normal internet connection vs. one going through a VPN:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PjSm_P6gbfb5oybCkYbAgQ.png" /></figure><p>Notice that with a VPN, traffic hits the wg0 interface first, gets encrypted, then goes to the real network interface as an encrypted packet. The ISP only sees the outer packet. Everything inside is encrypted.</p><p>Now let’s set this up.</p><h3>Installing Mullvad on Linux</h3><ul><li><strong>Virtual Network Interfaces (wg0-mullvad)</strong></li><li><strong>Tracing a Packet From Your Browser to the Wire</strong></li><li><strong>How Mullvad Handles Routing (fwmarks)</strong></li><li><strong>The Kill Switch Feature</strong></li><li><strong>The Next Part</strong></li></ul><p><strong>Continue reading: </strong><a href="https://danoss.me/categories/security/understanding-vpns-part-2/">https://danoss.me/categories/security/understanding-vpns-part-2/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0cab79e8056f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Understanding VPNs Part 1]]></title>
            <link>https://medium.com/@danoss777/understanding-vpns-part-1-d37604ed104d?source=rss-779aba551497------2</link>
            <guid isPermaLink="false">https://medium.com/p/d37604ed104d</guid>
            <category><![CDATA[vpn]]></category>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[mullvad-vpn]]></category>
            <category><![CDATA[protonvpn]]></category>
            <dc:creator><![CDATA[Danoss777]]></dc:creator>
            <pubDate>Sat, 07 Mar 2026 20:45:06 GMT</pubDate>
            <atom:updated>2026-03-07T20:45:06.342Z</atom:updated>
            <content:encoded><![CDATA[<p>What are VPNs?</p><p>A VPN (Virtual Private Network) is a must-use tool in today’s world, <strong>you either use or accept that your ISP, government, and every ad company on the world knows exactly what you do online</strong>.</p><p>This is Part 1 of a multi-part writing about VPNs. This one covers the basics: what is a VPN, how it protects you, what makes a good VPN provider, and why free VPNs are worse than using nothing at all.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*egO0DVU9frGyfiF1mUSVPg.png" /><figcaption><em>image source: </em><a href="https://howtofix.guide/vpn/"><em>https://howtofix.guide/vpn/</em></a><em>.</em></figcaption></figure><h3>Why Privacy Matters</h3><p>Internet privacy has been under attack for many years now. Governments want to know what you’re doing online to prevent protesters from rising up. ISPs (Internet Service Providers) want to sell and share what you’re doing online to make money. Advertisers want to profile what you’re doing online to show you relevant ads. And data brokers want to package all of the above and sell it to whoever pays.</p><p>A VPN won’t solve every privacy problem (nothing will), but it plugs a massive hole. It removes your ISP from spying on you by encrypting your Internet connection and routing it through a server you choose (like a forward proxy). Instead of your ISP seeing that you visited example.com, they see encrypted traffic going to a VPN server IP address. That’s it. They know you’re using a VPN, but they can’t see what’s inside the tunnel (the VPN provide can though, so choose wisely).</p><h3>What a VPN Actually Does</h3><p>A VPN creates an encrypted tunnel between your device and a VPN server. All of your internet traffic passes through this tunnel before reaching the public Internet.</p><p>When you connect to a VPN, several things happen. First, your VPN client in your device (computer, phone, etc.) establishes an encrypted connection to a VPN server using a protocol like WireGuard or OpenVPN. This involves a cryptographic handshake where your device and the server authenticate each other and agree on session encryption keys.</p><p>Once the tunnel is up, your device creates a virtual network interface and all outgoing traffic gets routed through this interface. The VPN client encrypts each packet, wraps it in a new UDP (or TCP) packet addressed to the VPN server, and sends it out through your real network interface. This is called encapsulation, you’re putting an encrypted packet inside a regular packet.</p><p>On the server side, the reverse happens. The VPN server receives the outer packet, strips the encapsulation, decrypts the inner packet, and forwards it to the destination on the public internet. The response follows the same path back: the destination server sends its response to the VPN server, the VPN server encrypts it, sends it through the tunnel to your device, and your device decrypts it.</p><p>So a VPN provides these benefits:</p><ul><li><strong>Your IP Address is Hidden:</strong> Websites and services you connect to see the VPN server’s IP address, not yours. This means they can’t determine your physical location or tie your activity to your home network.</li><li><strong>Your ISP Cannot See your Traffic:</strong> Your ISP can only see encrypted packets going to a VPN server IP. They don’t know what websites you’re visiting, what you’re downloading, or what services you’re using.</li><li><strong>DNS Queries go Through the Tunnel:</strong> A properly configured VPN routes your DNS lookups through the encrypted tunnel and resolves them on the VPN provider’s DNS servers (or a DNS server of your choosing). This prevents DNS leaks, which are one of the most common ways that VPN users accidentally expose their browsing activity. Without DNS leak protection, your browser might still send DNS queries to your ISP’s resolver even though your actual traffic goes through the VPN.</li><li><strong>All Traffic is Encrypted in Transit:</strong> Even if someone intercepts the packets between your device and the VPN server (for example, on a public Wi-Fi network), they see nothing but encrypted data.</li><li><strong>View Content From Any Location (Bonus):</strong> A bonus benefit is that you can connect to a VPN server in a different country and view content that is blocked in your own country.</li></ul><p><strong>Full post:</strong> <a href="https://danoss.me/categories/security/understanding-vpns-part-1/">https://danoss.me/categories/security/understanding-vpns-part-1/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d37604ed104d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Linux Security Hardening Part.3 — SELinux, Audit, Kernel Hardening, VPNs]]></title>
            <link>https://medium.com/@danoss777/linux-security-hardening-part-3-selinux-audit-kernel-hardening-vpns-7d000f86522a?source=rss-779aba551497------2</link>
            <guid isPermaLink="false">https://medium.com/p/7d000f86522a</guid>
            <category><![CDATA[linux-security]]></category>
            <category><![CDATA[selinux]]></category>
            <category><![CDATA[linux-hardening]]></category>
            <category><![CDATA[kernel-hardening]]></category>
            <dc:creator><![CDATA[Danoss777]]></dc:creator>
            <pubDate>Fri, 06 Feb 2026 21:53:46 GMT</pubDate>
            <atom:updated>2026-02-06T21:53:46.068Z</atom:updated>
            <content:encoded><![CDATA[<h3>Linux Security Hardening Part.3 — SELinux, Audit, Kernel Hardening, VPNs</h3><p>This part follows Linux security hardening with some system-level protections: kernel hardening parameters, SELinux access control, and audit logging that tracks everything that is happening on your system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*SaVkqGHRuGz-nJ0U9na9xw.png" /></figure><h3>SELinux Mandatory Access Control</h3><p>SELinux can be complicated but it’s a great kernel security feature that keeps blocking unauthorized actions on your system.</p><p>Even if it can be challenging to configure, SELinux has great defaults for most common applications, so for 90% of use cases you won’t even notice SELinux running. If SELinux is blocking something in a default configuration, you an add a policy exception to allow the action. Do not disable SELinux.</p><h3>Check SELinux Status</h3><p>First, verify SELinux is actually enabled and enforcing.</p><pre># Check current mode<br>getenforce<br># Should show &quot;Enforcing&quot;<br><br># Detailed status<br>sestatus<br># Shows: SELinux status, policy type, mode<br><br># Check if SELinux is denying anything<br>ausearch -m avc -ts recent</pre><p>Enforcing mode means SELinux actively blocks unauthorized actions. Permissive mode logs violations but doesn’t block them, which is useful for debugging but provides no actual protection.</p><h3>Understanding SELinux Contexts</h3><p>Every file, process, port, and user in SELinux has a security context (also called a “label”). These contexts determine what can access what. The format is user:role:type:level, but for most cases, you only care about the type field.</p><p>For example, web server files should have httpd_sys_content_t type, and the httpd process runs with httpd_t type. SELinux policy allows httpd_t processes to read httpd_sys_content_t files, but not user_home_t files (which are in user home directories). This means even if httpd is compromised and running as root, it still can’t access SSH keys in /root/.ssh/ because the SELinux policy denies it.</p><p>View file and process contexts.</p><pre># Show file context<br>ls -Z /var/www/html/index.html<br># Output: unconfined_u:object_r:httpd_sys_content_t:s0<br><br># Show process context<br>ps -eZ | grep httpd<br># Output: system_u:system_r:httpd_t:s0 1234 ? 00:00:00 httpd<br><br># Check context of running services<br>systemctl status httpd</pre><p>When you create or move files, they might inherit the wrong context. This is the most common cause of SELinux denials. For instance, if you copy a file from your home directory to /var/www/html/, it might keep the user_home_t context instead of getting httpd_sys_content_t.</p><h3>Fixing Context Issues</h3><p>The restorecon command restores default contexts based on file location.</p><p>Read the complete post in: <a href="https://danoss.me/categories/linux/linux-security-hardening-part-3/">https://danoss.me/categories/linux/linux-security-hardening-part-3/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7d000f86522a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Linux Security Hardening Part.2 — SSH, Firewall, and Services]]></title>
            <link>https://medium.com/@danoss777/linux-security-hardening-part-2-ssh-firewall-and-services-7cc0ce173800?source=rss-779aba551497------2</link>
            <guid isPermaLink="false">https://medium.com/p/7cc0ce173800</guid>
            <category><![CDATA[linux-hardening]]></category>
            <category><![CDATA[linux-security]]></category>
            <category><![CDATA[linux-firewall]]></category>
            <category><![CDATA[ssh-security]]></category>
            <dc:creator><![CDATA[Danoss777]]></dc:creator>
            <pubDate>Sat, 31 Jan 2026 05:02:51 GMT</pubDate>
            <atom:updated>2026-02-06T21:51:33.534Z</atom:updated>
            <content:encoded><![CDATA[<h3>Linux Security Hardening Part.2 — SSH, Firewall, and Services</h3><p>Part 2 of Linux security hardening, here I’ll talk about securing SSH, network-facing components, firewall configuration, and some good system maintenance options.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*SaVkqGHRuGz-nJ0U9na9xw.png" /></figure><h3>SSH Server Hardening</h3><p>Protecting SSH is key to prevent access to a system. Default SSH configurations are designed for convenience, not security. If not protected and exposed, many scripts/bots and will attempt to login to your system.</p><p>Disable password-based authentication entirely, restrict access to specific users, and add some basic rate limiting to reduce log noise from automated brute-force attacks.</p><h3>Disable Password Authentication</h3><p>Password authentication over SSH is insecure. Passwords can be brute-forced, phished, or leaked in data breaches. SSH key authentication, on the other hand, relies on keypairs which is much more secure.</p><p>The private key stays on your local machine and never leaves. The public key gets copied to the server. When you connect, the server challenges your client to prove it has the corresponding private key without ever transmitting the key itself. No password is sent over the network, and there’s nothing for an attacker to brute-force.</p><p>Generate an SSH key pair on your local machine (not the server).</p><pre># Ed25519 is the modern standard (shorter keys, better performance)w<br>ssh-keygen -t ed25519 -C &quot;your_email@example.com&quot;<br><br># If you need compatibility with older systems, use RSA with 4096-bit keys<br>ssh-keygen -t rsa -b 4096 -C &quot;your_email@example.com&quot;<br><br># Keys are saved to ~/.ssh/id_ed25519 (private) and ~/.ssh/id_ed25519.pub (public)</pre><p>Copy your public key to the server.</p><p>Read the full post in: <a href="https://danoss.me/categories/linux/linux-security-hardening-part-2/">https://danoss.me/categories/linux/linux-security-hardening-part-2/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7cc0ce173800" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Linux Hardening Part.1]]></title>
            <link>https://medium.com/@danoss777/linux-hardening-part-1-8a3b1ae7ff36?source=rss-779aba551497------2</link>
            <guid isPermaLink="false">https://medium.com/p/8a3b1ae7ff36</guid>
            <category><![CDATA[linux-hardening]]></category>
            <category><![CDATA[full-disk-encryption]]></category>
            <category><![CDATA[luks-encryption]]></category>
            <category><![CDATA[pam-configuration]]></category>
            <dc:creator><![CDATA[Danoss777]]></dc:creator>
            <pubDate>Sun, 25 Jan 2026 00:20:56 GMT</pubDate>
            <atom:updated>2026-01-25T00:21:30.581Z</atom:updated>
            <content:encoded><![CDATA[<p>Having basic security hygiene is essential, even though it’s a never ending process and perfect security doesn’t exist.</p><p>This topic is very extensive and is constantly evolving. So decided to split it into multiple parts. This part covers only full disk encryption, user account lockdown, and PAM configuration for user authentication.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/840/1*AUpOWwdfwi4zjMgCZUIDmA.png" /></figure><h3>Full Disk Encryption with LUKS</h3><p>Data-at-rest encryption is a must. If someone gets physical access to your hardware, full disk encryption is the only thing protecting your data from being read directly off the drive.</p><p>Linux uses <strong>LUKS (Linux Unified Key Setup)</strong> for disk encryption.</p><h3>What is LUKS?</h3><p>LUKS adds an encryption layer between the physical block device (the hard drive’s representation inside Linux) and the filesystem (ext4, xfs, btrfs…).</p><p>It uses the kernel’s device mapper to create a mapping between the encrypted physical drive and a decrypted logical volume. When you’re using your computer, applications see just a regular decrypted device in /dev/mapper/. They’re unaware of the encryption.</p><p>When you encrypt a drive, LUKS adds a <strong>header</strong> with metadata about the encryption (cipher, key size, key derivation function) and up to 32 key slots in LUKS2. These key slots can store passphrases or key files that unlock the same encrypted volume, so they can be used by multiple users to decrypt the drive using their own credentials stored in separate slots.</p><p>Keep in mind that to access a LUKS-encrypted volume, you need to decrypt it first. So data is only encrypted when the volume is closed (manually locked or when you shut down the computer). While you’re working with the volume, data is decrypted in memory.</p><p><strong>LUKS1 vs LUKS2</strong></p><p>In modern systems LUKS2 is the default, which provides more keyslots and some improvements.</p><ul><li>Up to 32 keyslots (vs 8 in LUKS1)</li><li>Argon2 key derivation (resistant to GPU-based attacks)</li><li>Authenticated encryption support</li><li>Better header resilience</li><li>Online re-encryption support (encrypt existing data without reformatting)</li></ul><p><strong>Key Derivation Functions</strong></p><p>The key derivation function determines how your passphrase is converted into an encryption key:</p><ul><li><strong>PBKDF2</strong> (LUKS1 default): Fast but vulnerable to GPU-accelerated brute-force attacks</li><li><strong>Argon2i</strong> (LUKS2 default): Memory-hard algorithm that resists GPU attacks and cache-timing attacks</li><li><strong>Argon2id</strong>: Hybrid approach with best overall protection against both GPU and side-channel attacks</li></ul><h3>Setting Up LUKS Encryption</h3><p>You cannot encrypt a drive that’s currently in use. You need either a new drive or if using an existing one, backup the data, format the drive, encrypt it, and then restore.</p><p>Most Linux distros offer LUKS setup during install (usually just by clicking a checkbox). You’ll just be asked to wipe the drive and enter a passphrase. This is the easiest approach.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/840/1*ROH3a5hMJi6JN6NfeLvgPA.png" /></figure><p><em>source: image found in fedoramagazine</em></p><p><strong>Encrypt a Drive After Install</strong></p><pre># Check if a device is already LUKS-encrypted<br>cryptsetup isLuks -v /dev/sdb1<br><br># Format the device with LUKS encryption (you&#39;ll be prompted for a passphrase)<br>cryptsetup luksFormat /dev/sdb1<br><br># Use specific cipher and key size for more control<br>cryptsetup luksFormat --cipher aes-xts-plain64 --key-size 512 /dev/sdb1<br><br># Specify key derivation function<br>cryptsetup luksFormat --type luks2 --pbkdf argon2id --pbkdf-memory 1048576 /dev/sdb1</pre><p><strong>Create LUKS Volume with Detached Header</strong></p><p>Storing the LUKS header separately is more secure. Without access to the external header file, the encrypted drive remains inaccessible…</p><p><strong>Continue reading:</strong> <a href="https://danoss.me/categories/linux/linux-hardening-part-1/">https://danoss.me/categories/linux/linux-hardening-part-1/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8a3b1ae7ff36" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Shell Escapes]]></title>
            <link>https://medium.com/@danoss777/shell-escapes-1c94c29f5a0b?source=rss-779aba551497------2</link>
            <guid isPermaLink="false">https://medium.com/p/1c94c29f5a0b</guid>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[shell-escape]]></category>
            <category><![CDATA[privilege-escalation]]></category>
            <dc:creator><![CDATA[Danoss777]]></dc:creator>
            <pubDate>Fri, 16 Jan 2026 19:29:56 GMT</pubDate>
            <atom:updated>2026-01-16T19:29:56.225Z</atom:updated>
            <content:encoded><![CDATA[<p>Something old, but still relevant to know to avoid a simple privilege escalation path is shell escapes.</p><h3>What are Shell Escapes?</h3><p>Shell escapes are a feature of many text-based programs that let you temporarily exit the program’s interface to execute shell commands without closing the application.</p><p>The problem is that shell escapes don’t just give you access to a shell, it gives you access to a shell with the permissions and environment of the parent program, so if you’re running vim with sudo, any shell escape you trigger runs with root privileges, creating a potential privilege escalation vector.</p><p>This is not a bug, just a feature that has been around for ages but that can be dangerous if not managed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/638/1*qqll92EzCoT9VNIqiQlvsQ.png" /></figure><h3>How Shell Escapes Work</h3><p><strong>Here’s how shell escapes work:</strong></p><ul><li>A user enters the vim text editor.</li><li>On the vim interface, the user triggers a shell escape (e.g., !/bin/sh) which instructs vim (the parent process) to invoke the fork() system call to create a new child process (the new shell).</li><li>This child process is an exact copy of the parent process (vim), including its current state, execution environment and privileges: Environment variables (PATH, HOME, USER, etc.), working directory (current location in filesystem), process permissions (UID/GID, supplementary groups), file descriptors (open files, network connections), resource limits (memory, CPU, file handles).</li><li>The child process then invokes the execve() system call to replace itself with a shell (e.g., /bin/sh).</li><li>The shell then starts execution with the inherited environment and permissions. So, if the parent process (e..g, vim) was executed with sudo privileges, the shell inherits these elevated privileges as well.</li><li>When the user exits the shell (via exit or Ctrl+D), the shell process terminates and control returns to the parent process (vim.</li><li>The parent process continues execution as if nothing happened.</li></ul><h3>Programs with Shell Escapes</h3><p><strong>Continue reading: </strong><a href="https://danoss.me/categories/linux/shell-escapes/">https://danoss.me/categories/linux/shell-escapes/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c94c29f5a0b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Automated Backups with Restic and Backblaze B2]]></title>
            <link>https://medium.com/@danoss777/automated-backups-with-restic-and-backblaze-b2-463c254ae35c?source=rss-779aba551497------2</link>
            <guid isPermaLink="false">https://medium.com/p/463c254ae35c</guid>
            <category><![CDATA[restic]]></category>
            <category><![CDATA[backup-linu]]></category>
            <category><![CDATA[backblaze]]></category>
            <category><![CDATA[b2-restic-backup]]></category>
            <dc:creator><![CDATA[Danoss777]]></dc:creator>
            <pubDate>Mon, 12 Jan 2026 23:32:39 GMT</pubDate>
            <atom:updated>2026-01-12T23:32:39.597Z</atom:updated>
            <content:encoded><![CDATA[<p>Today I was cleaning up some old files on my home computer and found my local backup setup script. I set it up more than a year ago using restic and <strong>Backblaze B2</strong> for cloud storage.</p><blockquote><strong>Restic</strong> is a fast, secure backup program for Linux that uses encryption and deduplication to create efficient snapshots of your files to local or remote storage.</blockquote><blockquote><strong>Backblaze B2</strong> is an S3-compatible cloud storage service designed for backups and archives, offers cheaper storage than AWS or Google Cloud.</blockquote><p>I’m a believer in the setup once and forget mentality. The script backs up selected files and directories from my computer to B2 cloud storage every 2 weeks and sends me a notification once the backup operation is done and the restic checks pass. Every 6 months or so I’ll poke at it to make sure backups are actually there and working.</p><p>Luckily I’ve never had to do a full restore, but the setup works and I’m not worried about losing my stuff if my hard drive dies tomorrow. This is just for my main computer, nothing server-related. Just personal files that I’d be annoyed to lose.</p><h3>Why Restic and B2?</h3><p>Yes, I could use Microsoft’s OneDrive, Google Drive, Dropbox, etc. but I don’t like their privacy practices and the fact they are constantly running. I just need a simple automated backup solution with minimal footprint on my machine.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*FmLea4warGJrHl-QyOR8dg.png" /></figure><p>Restic encrypts everything with AES-256, deduplicates data automatically, and works with basically any storage backend.</p><p>Backblaze B2 is I believe the cheapest cloud storage option (compared to Cloudflare R2, AWS S3, or Google Cloud) and is pretty reliable. I trust the Backblaze team. For personal backups where I’m hopefully never downloading anything, this works out great. First 3x your storage is free for downloads, then it’s $0.01/GB after that.</p><p>Plus B2 is S3-compatible, which means if I ever want to switch to Cloudflare R2 or whatever, I just change the repository URL. Same script, different backend (I’m not locked into any provider).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*fSFNAsdT5-UEvQM740VTxA.png" /></figure><h3>The Setup</h3><p>The setup is just a shell script that checks that config files exist, loads the credentials, and verifies the backup is done correctly by running restic check at the end.</p><p><strong>Continue reading:</strong> <a href="https://danoss.me/categories/linux/automated-backups-restic-and-backblaze-b2/">https://danoss.me/categories/linux/automated-backups-restic-and-backblaze-b2/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=463c254ae35c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Setting up Mullvad VPN and Tailscale on Linux]]></title>
            <link>https://medium.com/@danoss777/setting-up-mullvad-vpn-and-tailscale-on-linux-9b749f8c0759?source=rss-779aba551497------2</link>
            <guid isPermaLink="false">https://medium.com/p/9b749f8c0759</guid>
            <category><![CDATA[mullvad]]></category>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[vpn]]></category>
            <category><![CDATA[online-privacy]]></category>
            <dc:creator><![CDATA[Danoss777]]></dc:creator>
            <pubDate>Sun, 11 Jan 2026 17:52:56 GMT</pubDate>
            <atom:updated>2026-01-11T17:52:56.660Z</atom:updated>
            <content:encoded><![CDATA[<p>Having a VPN in today’s world is a must, and I can’t recommend <a href="https://mullvad.net/">Mullvad VPN</a> enough. I’ve been using it for years now and am very satisfied (not paid sponsor).</p><p>Mullvad VPN is serious about privacy, zero-knowledge, requires no email registration, and you can pay with crypto (and even better, Monero).</p><h4>Mullvad Clients</h4><p><strong>Linux Client:</strong> Mullvad has a Linux client that works great on Fedora (and any other distro). It’s simple to use and works great. Good GUI for normal configurations and a CLI client for advanced settings.</p><p><strong>Android Client:</strong> Mullvad also has a really good Android client app (don’t like Apple ecosystem jail), which works great, simple, and fully featured.</p><h4>Running Multiple VPNs</h4><p>Normally, you would use only one VPN for all traffic, however I need to use 2 VPNs at once.</p><ol><li>Mullvad to protect all my network traffic</li><li>Tailscale to access my private services available on a public VPS. The VPS runs a Headscale server that allows connections only from authenticated Tailscale clients.</li></ol><p>Usually, you would have issues running 2 VPNs simultaneously. One takes over routing, and the other breaks. Mullvad allows split tunneling to have a specific app traffic bypass the VPN and connect directly, but this is app-based, which doesn’t work with Tailscale.</p><h4>Using Both Mullvad and Tailscale</h4><p>I researched online for a solution and found that Tailscale offers a <a href="https://tailscale.com/mullvad">paid add-on</a> for allowing Tailscale traffic over Mullvad via exit nodes, so, I decided to create a simple nftables rule to allow both connections on Linux.</p><h4>How It Works</h4><p>Mullvad’s split tunneling feature uses nftables packet marking. It tags excluded traffic with:</p><p>Continue reading: <a href="https://danoss.me/categories/security/on-mullvad-vpn-and-linux-and-tailscale/">https://danoss.me/categories/security/on-mullvad-vpn-and-linux-and-tailscale/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9b749f8c0759" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>