3 ms·
> If you can't look at the code doing the encrypting, it's simply encoded. Not sure it being open source is required to be considered "encryption". Besides, ev
by barbazoo 1y ago
> If you can't look at the code doing the encrypting, it's simply encoded.
Not sure it being open source is required to be considered "encryption". Besides, even if you can look at the code you don't know if that's what's running on the server.
- SV_BubbleTime 1y agoI gave a charitable reading to that comment as “in terms of trust”.
- robmccoll 1y agoIf I can look at the code, decide I trust the implementations of the primitives being used, how they're being used, how identity is established, and how initial key exchange works, I don't need to know what's running on the server. That's sort of the point of end to end encryption.
- lenerdenator 1y agoOf course it's a requirement to be considered encryption. Let's take this "encrypted" copy of the text in your reply: " Klq prob fq ybfkd lmbk plrozb fp obnrfoba ql yb zlkpfaboba "bkzovmqflk". Ybpfabp, bsbk fc vlr zxk illh xq qeb zlab vlr alk'q hklt fc qexq'p texq'p orkkfkd lk qeb pbosbo." I'm telling you that I applied state-of-the-art, uncrackable encryption to that. Why should you believe me? What evidence do you have that I didn't just take your text, throw it in some Caesar Cipher generator, and copy-paste it into this text box? Well, none. It just happens to look like I did that, and if that were data you wanted to keep secret but that a hacker had obtained without permission, you can bet that they would say "looks like a Caesar Cipher, I'll try a combination of decryption parameters until it makes sense". And in this case, they'd be absolutely correct.