No, it is not a goal of the Yggdrasil project to provide anonymity. Direct peers over the Internet will be able to see your IP address and may be able to use this information to determine your location or identity. Multicast-discovered peerings on the same network will typically expose your device MAC address. Other nodes on the network may be able to discern some information about which nodes you are peered with.
I should note that I’m not relying on Yggdrasil for anonymity inside the network, rather more for anonymity towards observations from outside the network. And also mostly anonymity towards what I’m communicating when observed from outside the network.
If you’re taking part in transmitting a torrent over Yggdrasil, then people you’ve peered with in the swarm will definitely see your Yggdrasil IP - which is based off of the encryption key you generate (and you can change whenever you wish) for the connection to the mesh.
Regarding obfuscation of what you’re accessing inside something like the bittorrent DHT, that could likely be done with multiple Yggdrasil connections and torrent clients - so each address only associates with one torrent, it’s just not a core feature of the network itself.
The Yggdrasil network really isn’t meant to provide perfect internal anonymity between two directly communicating peers, it’s instead built to be an easy-to-use, end-to-end encrypted, mesh network - with great performance.
It’s there to protect the content and target of your communications from anyone beside you and said target, without adversely affecting the delivery of said content. Not to protect you from your communication target, though it can do a passable job at that too.
My main use of Yggdrasil has actually been as an easily setup alternative route into NATed systems, seeing as I can easily hit 600Mbit and get below 15ms of latency over it, which I quite often use to run VNC or SSH (and SCP/rsync) over. And since the mesh can be established as long as you can reach a node, it becomes ridiculously easy to get a functional link over it.
Transmitting DC++ traffic without my ISP being able to detect any of that is just a bonus.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !piracy@lemmy.dbzer0.com
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Doesn’t seem to be anonymous (emphasis mine)
I hope you aren’t relying on it for anonymity.
I should note that I’m not relying on Yggdrasil for anonymity inside the network, rather more for anonymity towards observations from outside the network. And also mostly anonymity towards what I’m communicating when observed from outside the network.
Understood. So, like torrents, anybody within the “swarm” would know what you’re accessing?
If you’re taking part in transmitting a torrent over Yggdrasil, then people you’ve peered with in the swarm will definitely see your Yggdrasil IP - which is based off of the encryption key you generate (and you can change whenever you wish) for the connection to the mesh.
Regarding obfuscation of what you’re accessing inside something like the bittorrent DHT, that could likely be done with multiple Yggdrasil connections and torrent clients - so each address only associates with one torrent, it’s just not a core feature of the network itself.
The Yggdrasil network really isn’t meant to provide perfect internal anonymity between two directly communicating peers, it’s instead built to be an easy-to-use, end-to-end encrypted, mesh network - with great performance.
It’s there to protect the content and target of your communications from anyone beside you and said target, without adversely affecting the delivery of said content. Not to protect you from your communication target, though it can do a passable job at that too.
My main use of Yggdrasil has actually been as an easily setup alternative route into NATed systems, seeing as I can easily hit 600Mbit and get below 15ms of latency over it, which I quite often use to run VNC or SSH (and SCP/rsync) over. And since the mesh can be established as long as you can reach a node, it becomes ridiculously easy to get a functional link over it.
Transmitting DC++ traffic without my ISP being able to detect any of that is just a bonus.