Archived
💬 Discussion | Experimental mesh/mixnets? (Yggdrasil & Cjdns/Hyperboria) #685
Closed
opened 2018-12-22 20:49:54 +00:00 by Mikaela
·
5 comments
No Branch/Tag Specified
master
dependabot/bundler/nokogiri-1.13.6
dependabot/bundler/addressable-2.8.0
freddy-m-patch-3
pr-add_RemoveMyPhone_sponsor
pr-browser_cleanup_1257_1328_1430
freddy-m-patch-2
freddy-m-patch-1
pr-vpn_hated_one_video
cdn
update-nitrohorse-image
promote-metager-to-card
hardware
pr-add_azirevpn
pr-add_mailfence
shop
1673
pr/1658
i18n-simple
sponsorship-edits-nov2019
i18n
ipfs
blacklight447-ptio-patch-3
blog
remove-windows-icons
pr/1147
i18n-testing
add-beautify
No results found.
Labels
Clear labels
:mag:🤖 Search Engines
approved
dependencies
duplicate
feedback wanted
high priority
I2P
iOS
low priority
OS
Self-contained networks
Social media
stale
streaming
todo
Tor
WIP
wontfix
XMPP
[m]
₿ cryptocurrency
ℹ️ help wanted
↔️ file sharing
⚙️ web extensions
✨ enhancement
❌ software removal
💬 discussion
🤖 Android
🐛 bug
💢 conflicting
📝 correction
🆘 critical
📧 email
🔒 file encryption
📁 file storage
🦊 Firefox
💻 hardware
🌐 hosting
🏠 housekeeping
🔐 password managers
🧰 productivity tools
🔎 research required
🌐 Social News Aggregators
🆕 software suggestion
👥 team chat
🔒 VPN
🌐 website issue
🚫 Windows
👁️ browsers
🖊️ digital notebooks
🗄️ DNS
🗨️ instant messaging (im)
🇦🇶 translations
approved, waiting for a PR
Pull requests that update a dependency file
The Invisible Internet Project (I2P)
Operating Systems
A label for stalebot if it gets added
Anything related to media streaming.
Anything covering the Tor network
active work in progress, do not merge or PR (yet)!
Issues or bugs that will not be fixed and/or do not have significant impact on the project.
Extensible Messaging and Presence Protocol
Matrix protocol
Browser Extension related issues
Correction of content on the website
Firefox & forks, about:config etc.
Anything primarily related to site cleanup.
Virtual Private Network
*Technical* issues with the website.
Domain Name System
Anything covering a translated version of the site
Milestone
No items
No Milestone
No due date set.
Dependencies
No dependencies set.
Reference: privacyguides/privacytools.io#685
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I am not sure if this is the correct category, but I thought I would at least bring them to attention of this issue tracker. (This is also the last issue I am going to open for now, sorry about the "spam" 😄.)
The website includes Self-contained networks and I wonder if Cjdns and Yggdrasil would be within scope. They wish to eventually replace the internet, but currently most of people are just linking (peering) over the internet to form a self-contained network. I think they are both currently considered as more or less experimental.
I am personally using them to access devices I have behind NAT or that have static IP as it's faster than Tor, supports UDP, everything is end-to-end encrypted, everything supporting IPv6 should be supported and the addresses are stable based on node keys.
Considering that this repository is about privacy tools, it's probably important to mention that neither attempts to be anonymous, your direct peers will know your clearnet address (even if Yggdrasil currently supports Tor/I2P (socks) peers, there is talk about removing that when they are stable).
The main difference between the two projects is their routing method, Cjdns requires supernodes being a bit more centralised and in my opinion disconnects more frequently, but Yggdrasil is newer and smaller (at the time of writing there are 109 nodes online).
URLs:
EDIT/Disclaimer?: I looked at the interactive Yggdrasil map (only within Yggdrasil http://y.yakamo.org:3000/ has the link) and having 8 nodes under my name, two of them public peers (+ 3 I am root on), I should probably mention that. I don't consider myself as an important figure or anything though, but I am activeish chatter there. I was originally attracted there by prebuild packages and a Debian repository they run and simpler config syntax.
What are the benefits of using such networks at this point (when they run over the internet)?
I2P and Tor are both anonymous (I prefer I2P because I like the idea of self-contained networks and for Tor it seems like hidden services are its secondary use at this moment -- with the primary being clearnet anonymity). Since the networks you mentioned aren't anonymous, what are the practical uses in terms of privacy?
They can provide static addressing and connectivity to devices behind carrier grade NAT (I have two locations behind CGN and one NAT VPS that I am accessing over them), like Tor hidden services or I2P eepsites. The main benefits over Tor (and possibly I2P, I don't know if it supports UDP?) are speed and UDP support (e.g. mosh doesn't work over Tor), while there is the tradeoff of anonymity. They are also end-to-end encrypted even if http or plaintext IRC was used within.
I think they can be called as public intranet VPNs, as you can install a node anywhere, connect to some public peers and then you can reach everything inside.
Sorry about the bad formatting.
You mean similar use to how I use my VPN to forward ports, since I'm behind a NAT?
In what way is it a privacy tool?
I think that way would mainly be the end to end encryption also encrypting unencrypted traffic such as http, plaintext IRC or telnet within the network.
I could also ask in what way is IPFS a privacy tool considering how it leaks all IP addresses the system has, doesn't support Tor or I2P, everything there is public (or unlisted until detected by https://ipfs-search.com/ (which picks it up from DHT even if the file is never linked anywhere if I have understood correctly)) and it's still listed on the website as worth mentioning, even if it does link to an important privacy notice (https://github.com/privacytoolsIO/privacytools.io/pull/361#issuecomment-344414022 which doesn't mention the file publicity though)?
I think I am closing this as out of scope. Now at least the search for these software will bring this issue up in case anyone will think about it in the future and the problems of IPFS would probably require a separate issue that I don't have interest opening.