End-to-end encryption

>end-to-end encryption

Attached: 1542334044264.png (416x435, 114K)

Other urls found in this thread:

en.wikipedia.org/wiki/Cryptanalysis
twitter.com/NSFWRedditGif

>end-to-zuckerberg-to-end encryption

>end-it-all encryption

>ass-to-ass

Attached: Quotass+to+assquot+_a87c651d6708cef1a01cca428da64181.jpg (349x237, 11K)

aka, whatsapp.
Long story short, if the code is not open, you cannot trust it to encrypt your communications without mining them first.

Attached: opensource.png (1200x1200, 81K)

kek I'm going to start saying this

>if the code is not open, you cannot trust it to encrypt your communications without mining them first
Objectively not true. Just inspect your network traffic and you can easily verify whether your communications were encrypted or not.
I'm all for open source code, but don't make up bullshit ass excuses.

how do you check if the encryption used does not have a backdoor that let's zuckerberg to read your messages?

en.wikipedia.org/wiki/Cryptanalysis

What's wrong with E2E?

It's disgusting how widespread whatsapp is.

>who needs security? nothing to hide nothing to fear.

Attached: proud npc.png (843x500, 195K)

peer-to-peer internet

Marketing gimmick

>onion-to-onion encryption

Attached: pedobear.png (125x203, 16K)

t. George W. Bush just before passing the Patriot Act

It totally disregards what happens in between you and your recipient as if it doesn't exist and you shouldn't give two shits about it because they told you it's irrelevant in this day and age.

Do you own anything between you and the recipient. Then botnet

You can cripple a cryptosystem very subtly. You could introduce a side channel vuln, you could use sometimes not-so-random IVs and such. A careful examination of the code to confirm that you're implementing a well examined algorithm in a sane way is critical. Otherwise it could be a decade before anyone discovers the "flaw".

lol

this

Attached: the hacker known as 4chan.webm (1280x720, 1.99M)