Me too. Last time I checked, there was no handy solution with the DRM stuff.

I simply hate being spied on. I also can’t logically understand, why to pay for a product, while still losing privacy at the same time. Then I came to linux, and it does the best of both worlds: It can be used for free, while respecting privacy. I still donate to my distro though, but it doesn’t force me to.

You’re my hero! It now works.

[Unit]
Description=Nomadnet Service
After=network.target

[Service]
Type=simple
ExecStart=/home/admin/.local/bin/nomadnet --daemon
Restart=on-failure
User=admin
Group=admin

[Install]
WantedBy=multi-user.target

So, now the service runs as a daemon. Is it a problem to login via SSH and use the command nomadnet (no daemon), while the daemon-service is running? Because it seems to be working when I try it?

!surfacelinux@lemmy.sdf.org

Already opened a PeerTube account. From time to time I take a look whats going on there.

Hmm, doesn’t this undermine the whole purpose of encryption? If I understand that right, there will always be unencrypted stuff of me? Also when I completely shutdown?

Hehe, no stupid questions I guess! When googling about this type of stuff, I often stumble across some claims I simply cannot verify myself. Some people say it’s unsafe, some people say it slows down everything and so on and some answers are from >10 years ago, so I feel the need to clarify what’s the status quo. Thanks for your view on that!

Good to know. Turns out that linux users are not lost when it comes to this topic!

I will take that into consideration. I already encrypted my older laptop (hard drive) with LUKS. Is there something special, when it comes to encrypting SSD’s? Do you experience speed losses of SSD after doing so?

Sorry, but can you explain a little, how this is done exactly? What should I see, when everything worked correctly?

According to the upvotes, this seems to be the way. I will try that, thank you!

Let’s say the torrent started with a working DNS and the issue occured some hours later. Maybe the client wants to check for IP-updates then, but won’t find any, because DNS doesn’t work anymore. It will still keep the IP-adresses resolved at the beginning, right? Because then it would make sense, that I saw some working torrents, even though the issue already appeared.

Yeah, did that. Couldn’t DNS-resolve the website because of the issue, but going via direct IP of the “check-website” (found via who.is) made me at least check my IP, which turned out to be the VPN-IP. Torrent-IP-Checking won’t work, because torrents seem to need at least DNS-resolving at the beginning of download.

Yeah, it may be good. Unfortunately unpredictable things can happen…

It may not be ideal for torrenting, but it works for me I think. Maybe that’s a topic for another thread.

I guess I can rule that one out. FF has DNS-over-HTTPS but it’s turned off. The DNS from Mullvad is usually used in my case…

I understand the basic concept of DNS but I am just a little unsure in which part of the process it takes effect. Thanks for your point of view!

Yeah, I will investigate it further. Do you have similar issues?

Interesting!

So if I get it right: Only when starting a torrent, some DNS needs to be resolved? And when the torrent is already running not?

So in my case a possible DNS leak occurs somewhere in the middle of the night. Not right from the beginning.

Thought so too. As described above, I tried pinging 8.8.8.8., which worked out. Didn’t try reaching 8.8.8.8. via browser though.

I also have an alternative privacy-friendly DNS set up in my router. Not sure, if that can be a problem. Normally, the DNS of Mullvad is used.

But another question is: Could that be a privacy-risk? Torrenting works without DNS-resolving, doesn’t it?