3 ms·
> since no one knows what encrypted fragment they hold But they do, since they have the key to it. The encryption is just feel-good obfuscation.
by okasaki 12y ago
> since no one knows what encrypted fragment they hold
But they do, since they have the key to it. The encryption is just feel-good obfuscation.
- icebraining 12y agoNo, they only have they key if they have the address of the content, which may not even be publicly known. https://wiki.freenetproject.org/Plausible_deniability https://wiki.freenetproject.org/Plausible_deniability
- okasaki 12y agoI guess it was changed. When I ran a node a years ago the only option was to encrypt the entire store with one key.
- sanity31415 12y agoI think you're referring to something different. The "request key" is what you request from Freenet, but it transformed into a "store key" (not official Freenet terminology) before the request is sent out over the network. If you have the encrypted content you only see the "store key", but the "request key" is required if you actually want to decrypt it. This means that, to see what content you're actually storing, you'd need to go to a lot of trouble (basically a dictionary attack on the store key). Not impossible, but enough for plausible deniability.
- pgeorgi 12y agothe data within the store is encrypted separately. (depending on the scheme used,) The URIs consist of an ID and the key, but the store only knows the locator. So you might know you have CHK@???,ID in your store, but to understand what it is you're hosting, you need to be aware of its full URI CHK@key,ID. (some details left out on purpose)