11–20 of 29 posts
Two projects for client-side encrypted cloud data: https://css.csail.mit.edu/mylar/ https://css.csail.mit.edu/cryptdb/ Microsoft also released a homomorphic encryption project for bioinformatics last week: http://research.microsoft.com/apps/pubs/default.aspx?id=2584...
Client side encryption is definitely the way to go, soon enough computation will become possible on the encrypted data. Maybe there will be homomorphically encrypted virtual machines/ containers.
I thought this article was interesting because the author talked about how encryption can be used to "delete" data from distributed systems instantly, by just removing the key. Not really a new idea, I don't think, but not one that gets surfaced much when people talk about client-side crypto.
Mobile operating systems often use that as a quick and solid-state-storage friendly way to clear devices.
https://github.com/ereyes01/cryptohelper
As far as the secure part, I'd appreciate eyes on the code (which there isn't a whole lot of) to verify this works well. This library could also possibly be enhanced to support other encryption methods, such as AES. An easy interface with sensible defaults to Go's AES interfaces would be nice.
Two projects for client-side encrypted cloud data: https://css.csail.mit.edu/mylar/ https://css.csail.mit.edu/cryptdb/ Microsoft also released a homomorphic encryption project for bioinformatics last week: http://research.microsoft.com/apps/pubs/default.aspx?id=2584...
Earlier quoted context omitted.
I like that you're using NaCl. I'm earmarking this for review later. :D
It's quite a coincidence that you posted this while I was writing up my own post evangelizing the virtues of NaCl :)
(https://developer.chrome.com/native-client vs. http://nacl.cr.yp.to)
I don't worry so much about encryption, since I am really not into keeping secrets, but I agree about the client-side part. ...and now a brief word from our corporate sponsors... Haha, not really :) I'm just trying to get the thing that I've been working on "out there". It's an operating system that runs in a web browser. How's that for client-side awesomeness? The current project I'm hawking is called "The Native Cl…
And for that matter, will you be at Chrome Dev Summit tomorrow?
Earlier quoted context omitted.
It's quite a coincidence that you posted this while I was writing up my own post evangelizing the virtues of NaCl :)
Different NaCl. Yes, the naming collision is unfortunate. ( https://developer.chrome.com/native-client vs. http://nacl.cr.yp.to )
It would likely be safer than hamfisted attempts at JS cryptography which can be compromised down the wire.