Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)MI
Posts
86
Comments
1,927
Joined
2 yr. ago

  • Not having an opt-out toggle should definitely be a cause of concern. Not everyone is running Debian just for the FOSS-only firmware, but there's definitely a sizeable number of people doing so. Letting the user choose whether they want to install proprietary firmware or not is absolutely an important choice.

    This is assuming there really isn't an opt-out somewhere in the install menu.

    Edit: it may be that I am running something without FOSS drivers for it. I happened to forget about it. So what? I'd rather it not run (unless it's critical), and I definitely want to be prompted that a proprietary driver is recommended to run the specific device because no FOSS driver is available. Not doing so is taking away my choice in the matter, and if Debian is really doing that, then I will personally have to rethink my options, including my donations

  • Except that I will not necessarily be connecting to the exact same IPs over time, just going to do so in specific ranges which the VPS/colo owns. There's plenty of people who are going to be renting VPSes and will have their traffic originate from the same IP range as mine, which means that if everybody using TCP had their traffic anonymized like so, the third party wouldn't actually know that MigratingToLemmy specifically was connecting to AWS at a certain time and from a certain location, so to speak. This hypothesis doesn't include correlation through other data in the threat model. But it could definitely prevent correlation with traffic across locations, which is similar to what Mullvad states

  • If I were to send packets to a single entity over time, I'd have no use for DAITA. I agree with you on this.

    However, let's say that I run a bunch of VPN endpoints across VPSes, and the entity trying to track me doesn't know about all of these IP ranges. I could be renting from a colo, the cloud and even a a bunch of friends who have their ports open. If I were to mix this in with my usual internet traffic, it becomes significantly harder for third-parties to figure out what I'm doing connecting to all of these different IPs. A state actor could put the resources behind it, but the average third-party will have a hard time with it. I can certainly see use-cases for it.

  • Considering that VPNs are Point-to-point too (home->VPN), I was wondering if one could use DAITA with TCP directly instead of having to use a VPN. Imagine if TCP had DAITA baked in.