Linked by Thom Holwerda on Tue 25th May 2010 21:37 UTC
Permalink for comment 426582
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
More News »
Sponsored Links



Member since:
2006-03-20
This seems like an idea:
http://psivision.blogspot.com/2010/03/data-operations-in-encryption...
That is, the target data is encrypted, as are your commands/operators. The only plain text space is within your perimeter.
This means if someone has access to the target data, it is meaningless. Similarly, what you do with it (transform, query, reduce, etc) is also meaningless as the operations/programs are encrypted too, even while they operate on the encrypted data.
This would solve some of the security fears around cloud computing.
Nice idea - could it be implemented? Or is there a theoretical reason this can't be done?
[plain text, my machine]
|
|
|
===== encrypt/decrypt at perimeter ================
@
@ encrypted command/program/operator
@
@
[encrypted data space]