🤣🤣🤣😂
Bruv, before Signal launched they posted an entire whitepaper detailing their protocol, the working mechanisms of the system, and source code. So to reply to your 3 points:
- No, this is stupid and easily verified by watching network traffic from any device. Signal is secretly sending plaintext messages anywhere.
- No, it’s not impossible to tell this at all. That’s what source code is. The executable code. Not only have NUMEROUS security audits been done on Signal by everyone from Academia, to for-profit security researchers and governments, you can easily verify that what you’re running on your phone is the same source code as what is published publicly because the fingerprint hashes for builds are also published. This means the same fingerprint you’d get building it yourself from source should also be the same as what is publicly published.
- See my point above, but also when two users exchange keys on Signal (or in any other cryptographic sense), these keys are constantly verified. If changed, the session becomes invalid. Verifying these keys between two users is a feature of Signal, but moreover, the basics of cryptography functioning can, and have been proven, during the independent audits of Signal. Go read any of the numerous papers dating back to 2016.
If you don’t understand how any of this works, it’s just best not to comment.
RIotingPacifist@lemmy.world 3 weeks ago
Why would any message be plaintext?
Fair you could have just said they have reproducible builds or linked to the docs: github.com/signalapp/Signal-Android/…/README.md
Again you are missing the point of the attack
Back at you, even if you are right that signal is secure, the attack is not what you think it is.
just_another_person@lemmy.world 3 weeks ago
What in the world are you talking about here, bud? Your comments are making zero sense.
Look, seriously, if my comment is being upvoted, it’s because I responded to yours, and people understand what I am saying in response.
You, unfortunately, clearly do not understand what I’m saying because you do not grasp how any of this works.
RIotingPacifist@lemmy.world 3 weeks ago
Lmao, sure buddy pat yourself on the back because you got upvotes.
You’re talking about E2E encryption as if it prevents side-channel attacks, but sure morons will upvotes because they also don’t understand real world security.
The only useful thing you’ve pointed out in your deluge of spam, is that Signal builds are reproducible which does protect against the attack described (as long as there isn’t a backdoor in the published code)
wonderingwanderer@sopuli.xyz 3 weeks ago
That’s literally what E2E encryption does. In order to attack it from outside you would have to break the encryption itself, and modern encryption is so robust that it would require quantum computing to break, and that capability hasn’t been developed yet.
The only reason the other commenter’s words sound like spam to you is because you don’t understand it, which you plainly reveal when you say "(as long as there isn’t a backdoor in the published [audited] code)
just_another_person@lemmy.world 3 weeks ago
Do you know what size channel attacks are? Because nothing you’ve even tried to bring up describes one at all, or how it applies to your original comments.