3 ms·
Javascript replacement is a problem with every single scheme that relies on the browser being an active participant. I know this because I designed such a sche
by jacques_chester 14y ago
Javascript replacement is a problem with every single scheme that relies on the browser being an active participant.
I know this because I designed such a scheme and it was hilariously, fantastically broken.
- xur17 14y agoThis is the problem I have with Lastpass - someone could hack their servers, replace the javascript encryption file to send the decryption password to their server, and get all of your passwords.
- gws 14y agoyou are talking about web access from a public computer I suppose? if you are connecting from your computer then I suppose the decryption happens in the browser extension and you are safe from the scenario you describe, or am I missing something?
- xur17 14y agoI am talking about either situation. Someone could hack their site (angry employee, outside person, etc), and modify the code to send the decryption password to their server. This would work for either situation since the person could push an update out for the browser extension. I'm sure they are very careful about the security of their system, but they are still one step away from having all of your passwords (a simple extension update, or site javascript modification). If I use a program like keepassx, I know when it's updated, and can verify that it doesn't attempt to communicate with a remote server.
- infodroid 14y agoDo you think this can be remedied by moving the code out of the web container? Cryptocat moved away from delivering its crypto code over JS to a browser plugin: http://www.forbes.com/sites/jonmatonis/2012/07/30/cryptocat-increases-security-in-move-away-from-javascript-encryption/ http://www.forbes.com/sites/jonmatonis/2012/07/30/cryptocat-... Do you think a dedicated native client would work? Something like a lightweight site-specific browser with Crypton libs. The same way you can appify sites with Chrome.
- jacques_chester 14y ago> Do you think this can be remedied by moving the code out of the web container? That's what I did in my own design. My protocol's purpose is different from cryptocat's, but the problem that in-browser javascript is untrustworthy is the same. I designed my protocol so that it needn't be embedded in the browser at all -- or for that matter, piggybacked on HTTP.