361
Zen browser had a backdoor enabled by default
(github.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 22 Mar 2025
361 points (100.0% liked)
Technology
73450 readers
3562 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
I didn't see anything about a backdoor at the link.
It's weird link to this issue with that title, since the problem is only referenced in the discussion. The actual backdoor issue is here.
Fuuuuck. I wouldn’t eat a sandwich made by this person let alone a web browser. Forking and mucking around in a code base they clearly don’t understand. I get the feeling they’re one of those
chmod -R 777people.I agree. That response made me lose any trust I had and I actually went to check that I didn't still have Zen browser installed from some earlier test run. He sounds like a script kiddie.
He was obviously very amateur by reading his posts on Reddit. Zen is more of a skin than a real browser, but I guess that’s essentially what a fork is at some point.
Fuck me, tell me someone else has risen to effective project lead since then?
His last comment is from 7 minutes ago so I would say no x)
You volunteering?
who in their right mind would hand over project leadership to a random person on a forum who he knows nothing about
https://github.com/zen-browser/desktop/issues/5947#issuecomment-2741902234
It's a link to a previous issue that was fixed, but it's an egregious one.