Re:Ask HN: Why isn't a content addressable cache built into ...
by devicenull on Tuesday March 01, 2011 @07:13PM
(#2277893)
How do you do any sort of security on this? I doubt any copyright holder is going to be happy when anyone with a list of hashes can download their movie. Using most types of encryption is out, so there goes most DRM solutions. Using IP or host based access lists defeats the purpose of the caching system, so that's out as well.
[ Parent
| on HN ]
Re:Ask HN: Why isn't a content addressable cache built into ...
by mckoss on Wednesday March 02, 2011 @01:14AM
(#2278646)
The content producers could encrypt their data so the hashes would only give access to encrypted blocks. They would still have the issue of distributing keys securely.
Re:Ask HN: Why isn't a content addressable cache built into ...
by invertd on Tuesday March 01, 2011 @09:18PM
(#2278200)
Check out CCNx (Content Centric Networking) project from PARC/Xerox leaded by Van Jacobson - the security seems to be baked in the design. Here is an intro: http://www.slideshare.net/PARCInc/contentbased-security
Re:Ask HN: Why isn't a content addressable cache built into ...
by mckoss on Wednesday March 02, 2011 @09:35AM
(#2279653)
Why implement something complex, when something simple will do? This cache should be (in my mind), DRM-agnostic. Just put your DRM around your hash lists, just as you would around your original content. DRM can be a layer above the caching layer.