this post was submitted on 27 Jan 2026
991 points (99.6% liked)
Technology
79355 readers
4201 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Well, no. At least not by default as you are running a compiled version of it. Someone could inject code you don't know anything about before compilation that for example leaked your keys.
One way to be more confident no one has, would be to have predictable builds that you can recreate and then compare the file fingerprints. But I do not think that is possible, at least on android, as google holds they signature keys to apps.
Signal is also on F-Droid, so it should be verifiable
Signal has reproducible builds and here's the instruction how to check it on Android https://github.com/signalapp/Signal-Android/blob/main/reproducible-builds/README.md
If they have, then good. Wasn't sure it was doable with current google's signing process. Highly unlikely someone hasn't tampered with them then (far easier to target the site displaying the "correct" fingerprint).
However, my original point still stands. Just because it is open source doesn't in itself mean that a bad actor can't tamper with it.