|
|
|
|
|
by mgerdts
1487 days ago
|
|
I think the key criticism here is that since they deliver the code (javascript) that handles the keys, they could easily replace the code with a version that leaks/harvests your private key. Once your private key is known by someone that also has your ciphertext, that party can get the plaintext. |
|
While this argument undeniably makes sense, I guess it boils down to what assumptions are made about the user.
Like, if we assume that the user is this paranoid, then why couldn't they just check the JS file/bundle with a local copy that is verified? Think of a Chrome extension or whatever.
We still run the JS locally on our own computers.