this post was submitted on 10 Dec 2023
23 points (92.6% liked)

Linux

48200 readers
1081 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
AgreeableLandscape@lemmy.ml
nooter692@lemmy.ml
MarcellusDrum@lemmy.ml
cypherpunks@lemmy.ml
cyclohexane@lemmy.ml
d3Xt3r@lemmy.nz
23
Privacy DNS Chooser Script v1.0 "Snow Breeze" (kbin.social)
submitted 11 months ago* (last edited 11 months ago) by Baritone5371@kbin.social to c/linux@lemmy.ml
18 comments fedilink hide all child comments
 

Disclaimer : I'm the author of this project.

🚀 Privacy DNS Chooser Script v1.0 "Snow Breeze" Release!

Project source code : https://github.com/rollsicecream/privacy-dns-chooser

Dear Community,

I'm thrilled to announce the official release of the Privacy DNS Chooser Script v1.0, code-named "Snow Breeze"! This marks a significant milestone in my journey to simplify the process of enabling DNS-over-TLS with privacy-focused DNS providers on Linux systems using systemd-resolved.

Key Highlights:

  • User-Friendly Setup: Easily configure DNS-over-TLS with a seamless and intuitive CLI Interface
  • Privacy-Focused Providers: Choose from trusted DNS providers like Quad9, Mullvad DNS, and NextDNS (more coming soon!)
  • Enhanced Security: DNS-over-TLS is enabled by default for a more secure online experience.

How to Get Started:

  1. Ensure you have systemd-resolved installed on your Linux system.
  2. Download the script from GitHub.
  3. Run the script with sudo to set up your preferred DNS provider.

Your Feedback Matters:

We value your feedback! Share your experience, report issues, or suggest improvements on GitHub Issues. Your insights help us refine and enhance the Privacy DNS Chooser Script.

Spread the Word:

Help us reach more users by sharing the news! Talk about it, share on your favorite forums, and let your community know about the release.

Thank you!

you are viewing a single comment's thread
view the rest of the comments
[–] Baritone5371@kbin.social 2 points 11 months ago* (last edited 11 months ago) (1 children)

Ok. I will see that! If you have a GitHub account. You can make an issue right now, so tracking the issue would be better for me. Or I could do that myself.

Edit : I have made a prototype that I could release it soon as an alpha. When it gets released, your goal is to test in a place where captive portals are present. Sadly, the script won't be automatic but requires user interaction.

Edit 2 : it is now available as alpha on the releases page.

[–] Pantherina@feddit.de 1 points 11 months ago (2 children)

Cool!

[–] _s10e@feddit.de 2 points 11 months ago (1 children)

Have you looked into how existing software handles captive portals. I believe, both Ubuntu (or Gnome or Network-Manager) and Firefox do check for such portals and detect real internet access. (They simple poll some URL http://detectportal.vendor.com and check for the expected return code. Portals usually redirect.)

Now I'm thinking, what if this check could trigger a change to the DNS configuration. That is use DoT when internet is available, otherwise fall back to DHCP announced DNS

[–] Pantherina@feddit.de 2 points 11 months ago

That is neat! It is a specific response so it should work.

#!/bin/bash

# Function to set insecure DNS
function insecure-dns() {
  # Backup the original resolved.conf file
  cp /etc/systemd/resolved.conf /etc/systemd/resolved.conf.bak

  # Modify resolved.conf to disable custom DNS, DoT, and DNSSEC
  sed -i 's/^DNS=.*/#DNS=/; s/^Domains=.*/#Domains=/; s/^DNSOverTLS=.*/#DNSOverTLS=/; s/^DNSSEC=.*/#DNSSEC=/' /etc/systemd/resolved.conf

  # Restart systemd-resolved
  systemctl restart systemd-resolved
}

# Function to set secure DNS
function secure-dns() {
  # Restore the original resolved.conf file
  mv /etc/systemd/resolved.conf.bak /etc/systemd/resolved.conf

  # Restart systemd-resolved
  systemctl restart systemd-resolved
}

while true; do
  response=$(curl -sI captive.test.com | head -n 1 | cut -d' ' -f2)

  if [ "$response" == "200" ]; then
    insecure-dns
    xdg-open captive.test.com
    sleep 30
    # something to wait until window is closed, otherwise spam!
  else
    secure-dns
  fi

  sleep 5
done

This should work. What would be needed is to track the process of the login and only continue when the window is closed again.

[–] Baritone5371@kbin.social 1 points 11 months ago* (last edited 11 months ago)

I have edited the release page for the alpha. I have modified the file to correct a bug and add the deletion of the backup file when the operation is finished and also restart systemd-resolved service.