Re:Client-Side Encryption: The Right Security Model for the ...
by jimktrains2 on Monday November 16, 2015 @11:39PM
(#10579200)
1) The problem with that is trusting the code you download to actually encrypt the data. If it could be linked with the file upload button or some such functionality solely reliant on the browser to get right, it could work.
2) You mean something like keygen[1]? (yes, I know it was removed from the standard.)
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/ke... (
Re:Client-Side Encryption: The Right Security Model for the ...
by toyg on Tuesday November 17, 2015 @11:42AM
(#10582223)
1) Exactly. Also, the more crypto you move into the browser, the easier it becomes to inspect downloaded code and isolate misbehaving developers.
2) Exactly. I don't follow the standard process these days, but it's sad that we're not really making any progress in such a critical area. We now have pretty progress bars, but we're still as vulnerable as 20 years ago.
2. client certificate distribution is still a mess. At a minimum, there should be a standard way for servers to generate certificates and install them in the browser (with user visibility but without requiring user interaction).