Re: Library for offload

[Javier Guerra Giraldez <javier@...>]

On Thu, Mar 18, 2010 at 2:37 PM, Max <petersonmaxx@googlemail.com> wrote:
> On Thu, Mar 18, 2010 at 8:09 PM, Sam Roberts <vieuxtech@gmail.com> wrote:
>>> Offload is storing files by XORing the file, that means, the chunks
>>> have no relation to the original file.
>>
>> Yes they do, they are an encrypted version of the original file. The
>> encryption key is the same size as the chunk, and the algorithm is
>> xor, but it's still an encrypted movie.
>>
>
> no it is not encypted, you just have an operation, which is 7-2 = 5
> so if you have the 5, you need the operation and the value,
> but the operation can be as well 3+2=5, so what will you do with the 5?
> You can implement 2 files into one block. and without the off-torrent
> you cannot resore the file.
> no one first can say, you restored it, and second, no one can say,
> which operation you do with 5.


some (most?) cyphers work by taking some constants, the user's key and
an algorithm to generate a long sequence of seemingly-random but
completely deterministic bytes, called the 'pad'.  Then it simply XORs
the data with the pad.

the novelty of this off-system is to use other data chunks as the pad.
 it's a clever twist, but it's just encryption.

and, of course, none of this matters to a lawyer. in their worldview
the fact remains that  "you didn't buy it, but you have it now, so you
stole it"

-- 
Javier