this post was submitted on 25 Mar 2022
60 points (98.4% liked)
Privacy
34612 readers
693 users here now
A place to discuss privacy and freedom in the digital world.
Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.
In this community everyone is welcome to post links and discuss topics related to privacy.
Some Rules
- Posting a link to a website containing tracking isn't great, if contents of the website are behind a paywall maybe copy them into the post
- Don't promote proprietary software
- Try to keep things on topic
- If you have a question, please try searching for previous discussions, maybe it has already been answered
- Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
- Be nice :)
Related communities
much thanks to @gary_host_laptop for the logo design :)
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Skimming their website, I noticed two issues with their dependencies.
First, https://berty.tech/docs/protocol/ says
Clicking through to ed25519/extra25519, one can see that the upstream author replaced that code two years ago with a readme that says "This repository is unmaintained" and "Uncared for code is not a foundation to build upon". (The part that was merged in to golang's standard crypto library does not include the "extra25519" code that this project requires.)
Second, I see that their Go-Tor-Transport relies on go-libtor which currently is using a year-old snapshot of the -dev branch of upstream tor. (I haven't yet discerned if Tor is fundamental to their design or if it is an optional thing, but i suspect the latter?)
They do say it is early days still and not fully dependable V1.0. So there is work in progress, and they still want to have an independent security audit done. I think they are pretty open and forthcoming about what is not yet done. They were quite clear to state the product is not ready yet for the Ukraine war for example, and state people should not consider it for that use.
Certainly in principle one does not want to build on unmaintained code (different from code that has not requited an update for any good reason for a while).
So it is really a proof of concept now that is usable, but not yet declared finished as far as the security side goes (implying some of those loose ends mentioned). I gather from that we should not yet be judging it as a finished or production ready product.