Nice writeup as always. I always wondered about Session but it seems like they have the same "I rolled my own" crypto nonsense as Telegram has; and we all know how bad that one actually is as it's not correctly implemented at all; even if the underlying protocol is otherwise good.
this post was submitted on 15 Jan 2025
89 points (98.9% liked)
Privacy Guides
17145 readers
83 users here now
In the digital age, protecting your personal information might seem like an impossible task. We’re here to help.
This is a community for sharing news about privacy, posting information about cool privacy tools and services, and getting advice about your privacy journey.
You can subscribe to this community from any Kbin or Lemmy instance:
Check out our website at privacyguides.org before asking your questions here. We've tried answering the common questions and recommendations there!
Want to get involved? The website is open-source on GitHub, and your help would be appreciated!
This community is the "official" Privacy Guides community on Lemmy, which can be verified here. Other "Privacy Guides" communities on other Lemmy servers are not moderated by this team or associated with the website.
Moderation Rules:
- We prefer posting about open-source software whenever possible.
- This is not the place for self-promotion if you are not listed on privacyguides.org. If you want to be listed, make a suggestion on our forum first.
- No soliciting engagement: Don't ask for upvotes, follows, etc.
- Surveys, Fundraising, and Petitions must be pre-approved by the mod team.
- Be civil, no violence, hate speech. Assume people here are posting in good faith.
- Don't repost topics which have already been covered here.
- News posts must be related to privacy and security, and your post title must match the article headline exactly. Do not editorialize titles, you can post your opinions in the post body or a comment.
- Memes/images/video posts that could be summarized as text explanations should not be posted. Infographics and conference talks from reputable sources are acceptable.
- No help vampires: This is not a tech support subreddit, don't abuse our community's willingness to help. Questions related to privacy, security or privacy/security related software and their configurations are acceptable.
- No misinformation: Extraordinary claims must be matched with evidence.
- Do not post about VPNs or cryptocurrencies which are not listed on privacyguides.org. See Rule 2 for info on adding new recommendations to the website.
- General guides or software lists are not permitted. Original sources and research about specific topics are allowed as long as they are high quality and factual. We are not providing a platform for poorly-vetted, out-of-date or conflicting recommendations.
Additional Resources:
- EFF: Surveillance Self-Defense
- Consumer Reports Security Planner
- Jonah Aragon (YouTube)
- r/Privacy
- Big Ass Data Broker Opt-Out List
founded 2 years ago
MODERATORS
Cliff notes: end to end encryption is borked.
So borked in fact that the author's fursona face-palmed in response.
I weren't even aware it was a Signal fork! What kept me away was their heavy integration of the Oxen crypto token (now apparently replaced with their own "Session token" instead). Anything that deep into web3 is a red flag to me, but the security flaws discussed in the above blog post look white hot.
the Oxen crypto token
Oxen is the company behind Session, for anybody unfamiliar. They were a crypto company that made (well, cloned) a messaging app to promote this token.
And Oxen itself was a clone of Monero.
Strong agree. Session is not security focused it's marketing focused. Last I checked they still use central servers for file uploads.
Use simplex.
That's nice you're mentioning SimpleX but its design is way too complicated compared to alternatives (e.g. Signal) that no one will use it.
Even as a tech-savvy person, I was shocked that I have to scan a QR code to chat. I can't imagine how it feels for non-tech people.
As a result, who will you actually chat with? 🙂
It would be nice to read the basic points of your statement, then if someone wants to go in detail, there's the link to your article.
it's not my article.
Ops. However a small TL;DR would be useful instead of just copying/pasting links.
Jesus Christ, get fucked
TL;DR from oss-security:
At a glance, what I found is the following:
- Session only uses 128 bits of entropy for Ed25519 keys. This means their ECDLP is at most 64 bits, which is pretty reasonably in the realm of possibility for nation state attackers to exploit.
- Session has an Ed25519 verification algorithm that verifies a signature for a message against a public key provided by the message. This is amateur hour.
- Session uses an X25519 public key as the symmetric key for AES-GCM as part of their encryption for onion routing.
Additional gripes about their source code were also included in the blog post.
Thanks for the notice!
Regular Signal for lyfe.