News for hackers. Stuff that matters.
Re:Client-Side Encryption: The Right Security Model for the ... by toyg on Monday November 16, 2015 @09:51PM (#10578896)
I keep wondering: Browsers have been dealing with some of these issues for quite some time now, both for SSL purposes and password storage. They should agree on common interfaces to expose safe crypto functions to client code, so that users could be relatively sure that servers will never get, say, a plaintext password. Is it terribly hard?

It would likely be safer than hamfisted attempts at JS cryptography which can be compromised down the wire.

Re:Client-Side Encryption: The Right Security Model for the ... by austerity on Tuesday November 17, 2015 @02:05AM (#10579599)
Also that would probably greatly simplify key management as opposed to having 10 apps all wanting you to use their own mechanism every time you move to another device.

Unfortunately so far things are moving in the opposite direction. After Chrome dropped Java support it appears there's no cross-browser way to do reasonably reliable crypto right now.

Re:Client-Side Encryption: The Right Security Model for the ... by gruez on Monday November 16, 2015 @10:15PM (#10578953)
What you describe already exists. It's called client certificates.
Re:Client-Side Encryption: The Right Security Model for the ... by toyg on Monday November 16, 2015 @10:30PM (#10579000)
1. client certificates only replace passwords, not arbitrary encrypted data.

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).

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.