Reticulum Is Unstoppable Networks for the People(reticulum.network)
reticulum.network
Reticulum Is Unstoppable Networks for the People
https://reticulum.network/
45 comments
https://github.com/markqvist/Reticulum/tree/6ded42edd7ae203e...
I am struggling to understand who the overlap between people who can accurately assess the risk of each of these implementations and correctly find them ok (graduate level cryptography?) and people who cannot get pyca or openssl to compile is.
For offline operation maybe a case could be made that timing side channels aren't an issue in practice, but this is explicitly network software.
I am struggling to understand who the overlap between people who can accurately assess the risk of each of these implementations and correctly find them ok (graduate level cryptography?) and people who cannot get pyca or openssl to compile is.
For offline operation maybe a case could be made that timing side channels aren't an issue in practice, but this is explicitly network software.
I was taking a closer look at the EdDSA to see if I could get a practical exploit going, and it looks like it might be safe, for now.
Per https://minerva.crocs.fi.muni.cz/,
> The EdDSA scalar multiplication code in libgcrypt was leaking, however due to the way it was used, it was likely not exploitable. It did not reduce the scalar which was a SHA512 digest by the curve order, but used the digest directly, thus the leakage did not represent the bit-length of the reduced scalar.
(Extended discussion: https://blog.cr.yp.to/20191024-eddsa.html)
Reticulum's implementation is similar in that it doesn't reduce the scalar.
Per https://minerva.crocs.fi.muni.cz/,
> The EdDSA scalar multiplication code in libgcrypt was leaking, however due to the way it was used, it was likely not exploitable. It did not reduce the scalar which was a SHA512 digest by the curve order, but used the digest directly, thus the leakage did not represent the bit-length of the reduced scalar.
(Extended discussion: https://blog.cr.yp.to/20191024-eddsa.html)
Reticulum's implementation is similar in that it doesn't reduce the scalar.
If you're going to rewrite every networking protocol, why stop there? Might as well rewrite the crypto protocols too.
I wish they would stop using complete hyperbole like this:
Please stick to the actual facts.
From a users perspective, Reticulum allows the creation of applications that respect and empower the autonomy and sovereignty of communities and individuals. Reticulum provides secure digital communication that cannot be subjected to outside control, manipulation or censorship.
Please stick to the actual facts.
Even if you control everything about your crypto setup from the atomic level to the software, unless you have a way to live self-sufficiently, you are still subject to outside control. There are many ways to apply pressure in the meat-space world that can lead to manipulation and censorship. Just ask any big tech provider _exactly_ how many National Security Letters they've responded to this month.
I'd like to see a doc that outlines how Reticulum handles standard network failures and attacks. Ok, the network just got partitioned, what happens? Ok someone is spamming announce messages trying to eat the 2% bandwidth allocation of everyone on the network, what happens?
That would help me quickly understand the properties of this system.
That would help me quickly understand the properties of this system.
> Reticulum does not use source addresses. No packets transmitted include information about the address, place, machine or person they originated from.
So there is no way to reply to a packet? Sounds useless except for some very rare usecases and spam.
So there is no way to reply to a packet? Sounds useless except for some very rare usecases and spam.
Upper layer on top of the packet has to include any destinations expecting replies.
I suppose one is expected to overlay IP on top of it
Even then you would need a table correlating the IP and reticulum addresses somewhere. Otherwise you arrive at the same problem, that your IP replies go nowhere...
"cannot be subjected to outside control, manipulation or censorship"
Even in China? When I used to live there, I'd sometimes hear about some fancy anti-censorship software or service and it invariably didn't actually work and turned out only to be meant for comfortable free places like America.
Even in China? When I used to live there, I'd sometimes hear about some fancy anti-censorship software or service and it invariably didn't actually work and turned out only to be meant for comfortable free places like America.
Reticulum (noticing similarities to old UUCP here) doesn't need the Internet, TCP/IP, or even Ethernet to work - networks can be built over serial lines. Therefore a possible link could be a modem link over an international phone call. I am curious if/how and sure that various countries monitor/scrape PSTN for data though. Other weird ideas off the top of my head: satellite phone, 2 shortwave channels with appropriate hardware (one for Tx other for Rx - I don't really know anything about shortwave).
Oh. I didn't know that. The page is pretty vague about what physical channels it uses so I just assumed it was on top of the internet. None of that stuff would have enough bandwidth for regular internet use, and clandestinely broadcasting on shortwave is going to cause you far more trouble with the authorities no matter what data you send!
China is the only authoritarian country I know of with the internet filtering capabilities to oppress their citizens when they use new protocols. From what I have read online, it seems like countries like Iran use a combination of network-routing-fuckery and/or enterprise middleboxes to do traffic monitoring.
For many authoritarian countries, the challenge isn't "how do I get the information out", but rather "how do I not get arrested for spreading this". Tor, with the necessary oppression proxies, works remarkably well, but is easily recognisable.
For many authoritarian countries, the challenge isn't "how do I get the information out", but rather "how do I not get arrested for spreading this". Tor, with the necessary oppression proxies, works remarkably well, but is easily recognisable.
Is it too late to change the name of this project? If it isn't too late, I urge the founders to consider it.
My guess it is a reference to a neal stephenson novel, anathem
https://anathem.fandom.com/wiki/Reticulum
https://anathem.fandom.com/wiki/Reticulum
A reticulum is a netlike structure, seems good to me. Ain't you never reticulated splines?
What’s wrong with it? It just means network.
Why, what is wrong with it?
When reading fast, we tend to read first/last letters and the 'pattern' of the whole word and not really read the spelling. In this case, Reticulum is not very common or a familiar word and most folks would first read (or rather 'see') the word 'rectum'!
https://pubmed.ncbi.nlm.nih.gov/23089042/ https://www.dictionary.com/e/typoglycemia/
https://pubmed.ncbi.nlm.nih.gov/23089042/ https://www.dictionary.com/e/typoglycemia/
You described the phenomenon much better than I would have.
At first glance the word looks a lot like “rectum”.
I thought it meant "small rectum" as a diminutive[1] :D
[1] https://en.wikipedia.org/wiki/Diminutive
[1] https://en.wikipedia.org/wiki/Diminutive
Why?
would second the suggestion…
I feel like I'm missing something, is there a dual meaning here?
It uses data amoeba for routing? As in societal structures and habbits? If a state actor ennulates the routing structure can he peel the cryptography?
As a developer, when I see an interesting project like this and would like to dig a little deeper, the first thing I want to know is what language/platform/framework does it use? When that isn't clearly stated on the "Get Started" page, it's kind of off-putting.
So is this a Python-only, Linux-only project? It appears that way from what I can see so far, but it's far from clear.
So is this a Python-only, Linux-only project? It appears that way from what I can see so far, but it's far from clear.
there is an active reimplementation in C++ https://github.com/attermann/microReticulum
Writing network protocols in Python is an odd choice indeed
[deleted]
I tried to get this working based on the other articles presented today on hn, but was unable to connect to a peer. Can anyone explain how to get this up and running?
You have to know the public key of the destination. Then it's supposed to route automatically.
Unless you know someone else using this, there's no one to talk to.
Try setting up two nodes, and get them talking to each other.
Someone could set up a directory server with a well known destination address, and then there would be a way to find destinations that will talk to you. Not finding anything like that yet. This seems to be intended for private comms within a group, such as your militia or drug cartel. They went so far in the privacy direction that there's nobody to talk to.
Try Reddit's "r/reticulum". Maybe someone will offer to talk to you.
Someone could set up a directory server with a well known destination address, and then there would be a way to find destinations that will talk to you. Not finding anything like that yet. This seems to be intended for private comms within a group, such as your militia or drug cartel. They went so far in the privacy direction that there's nobody to talk to.
Try Reddit's "r/reticulum". Maybe someone will offer to talk to you.
Why didn't they set up a global DHT to find peers, like bittorrent?
You are the first peer, probably. Congratulations!
[deleted]
"without any need for hierarchical or beaureucratic structures"
How does it solve name collisions?
The days before NickServ were a pain in IRC.
How does it solve name collisions?
The days before NickServ were a pain in IRC.
> How does it solve name collisions?
Destination IDs are randomly chosen large values, like UUIDs and crypto addresses.
Destination IDs are randomly chosen large values, like UUIDs and crypto addresses.
I love that they use my (or a similar 3270 font) for their logo.
Definitely gives it a serious tone.
Definitely gives it a serious tone.
[deleted]
These implementations are not secure against side-channels, for example, here's their AES implementation indexing an array with a secret index: https://github.com/markqvist/Reticulum/blob/6ded42edd7ae203e...
Their ed25519 implementation doesn't even attempt to be constant-time: https://github.com/markqvist/Reticulum/blob/6ded42edd7ae203e...
Their X25519 implementation tries to be constant time by using... time.sleep() https://github.com/markqvist/Reticulum/blob/6ded42edd7ae203e...
There are also pure-python implementations of sha256 and sha512, which I haven't looked at closely, but they're already available as part of hashlib (part of the standard library, and already used as a dependency), so they serve no practical purpose.
Ditto for hmac.