3 ms·
This essay is written to create the impression that it's imparting something profound, but it's really just identifying the existence of side channels. We enco
by AnthonyMouse 6y ago
This essay is written to create the impression that it's imparting something profound, but it's really just identifying the existence of side channels.
We encode bits in all kinds of things. You can store some bits on a flash drive. Then you can write some words on the outside of the flash drive. They're both just bits.
Whether you own a flash drive with some bits on it which is in a safety deposit box at a bank may depend on the bits in the bank's computer and not the bits on the flash drive, but it's still bits that it depends on.
The examples it uses aren't accurate:
> Maybe you were thinking about similar ideas to mine and happened to put the words together in a similar way. If so, fine. But maybe you wrote "your" article by cutting and pasting from "mine" - in that case, the words have the Colour that obligates you to follow quotation procedures and worry about "derivative work" status under copyright law and so on.
As it turns out copyright law doesn't really care about this, even if people might expect it to, because the law is too pragmatic for that. Proving that you came up with some particular phrasing is hard. Disproving it is hard too. So in practice the courts don't look at whether you actually copied the bits. They look at whether you could have copied them ("access"), which they then go on to assume is the case for anything widely disseminated (since establishing that would be hard too), and then whether the bits are similar ("substantial similarity"):
https://www.theiplawblog.com/2007/02/articles/copyright-law/the-complexity-of-proving-copyright-infringement/ https://www.theiplawblog.com/2007/02/articles/copyright-law/...
Whether you actually copied the bits doesn't come into consideration, apparently.
Because the courts can only take into consideration the information they have available to them. Which is all bits, because all information is bits.
> You take a file to which someone claims copyright, mix it up with a public file, and then the result, which is mixed-up garbage supposedly containing no information, is supposedly free of copyright claims even though someone else can later undo the mixing operation and produce a copy of the copyright-encumbered file you started with.
There is still no Colour here, and the essay is missing a rather decent practical attack on the "Colour theory" version of the copyright system.
Suppose Alice publishes R1 and Bob publishes R2. R1 is Alice's message xor Alice's one time pad. R2 is Bob's message xor Bob's one time pad. The one time pads are "random".
Then it's discovered that R1 xor R2 generates a third party copyrighted work. Which is statistically impossible unless either Alice or Bob (but not necessarily both) chose their one-time pad specifically in order to cause this.
According to "Colour theory" the one who chose their one-time pad specifically in order to cause this has given their ciphertext the "Colour" of the copyrighted work. But that's a real problem in practice when there is no way to tell which one it was. The other person may not even be in on it. So which one do you haul into court when you don't know that? Which one do you take down?
In real life if something like that becomes popular what happens is not that they figure out who it really was that created the derivative work, it's that they come up with some kind of disgusting hack like the DMCA takedown process which imposes no practical consequences on fraudulent takedowns, and hope that the innocent victims of the collateral damage don't have enough political clout to do anything about it.
It seems like the same fallacy as the model of the law that we teach to high school students. Computer scientists understand that it's wrong. Lawyers understand that it's wrong. But certain people benefit from pretending that it isn't in front of the general population because the misleading abstraction is prettier than what actually happens under the hood, and a better understanding of the latter would make people upset.
- goto11 6y ago> Suppose Alice publishes R1 and Bob publishes R2. R1 is Alice's message xor Alice's one time pad. R2 is Bob's message xor Bob's one time pad. The one time pads are "random". Then it's discovered that R1 xor R2 generates a third party copyrighted work. It is common among computer people to think the law can be hacked like an algorithm. It does not work like that. If you xor two apparently random files and they surprisingly produce the full text of the Harry Potter series, you do not have plausible deniability if you start distributing it.
- ziml77 6y agoI see it all the time and it's quite frustrating to see people being so naive. The law is not purely mathematical and algorithmic. I think a good example that moves outside of IP law is murder vs manslaughter. Two identical killings could fall under different charges simply due to what the killer was thinking at the time. And we want it that way. It would be unfair and not accomplish anything good to treat an accidental and an intentional killer the same way.
- goto11 6y agoI don't know why you were downvoted because you are exactly on point. In the GP example, two files can be xor'ed to yield some pirated document. The poster thinks this would require the judicial system to punish the creators of both files equally because both files contribute bits equally. But the judicial system looks at intent, and only one of the files was created with criminal intent.
- AnthonyMouse 6y agoYou're missing the attack in exactly the same way as the author does. The same person doesn't distribute both of the files. Two different people distribute two different files. One of them is totally innocent and the party distributing that file doesn't even have to be in on it or have any relationship with the other person, but there is no way to tell which one it is. The legal system is forced into either punishing and taking down the innocent file or not doing so for the infringing one. There is no other option when you can't distinguish between them. But it isn't supposed to do that to the one which is just an ordinary use of a one-time pad by an innocent independent third party who has e.g. posted it in a public place for the intended recipient of the non-infringing message to receive it without there being a direct one-to-one communication between sender and the recipient. Or because there are multiple intended recipients and only those with the correct pad can read the original message so it's safe to publish widely. The fact that some totally different person has come along and used your published file to encode an infringing one is not supposed to affect your legal status. But if nobody can tell which one is the original, the legal system has to choose between punishing the innocent and not punishing the guilty. It isn't an algorithmic problem, it's an evidentiary problem. There are two different sets of bits and one is supposed to have a different "Colour" but the legal system has no information as to which one it is. It's like someone discovering that the flashlight on certain phones is bright enough to blind surveillance cameras, and when someone points out that criminals could use this to prevent surveillance cameras from capturing their faces while they're committing their crimes, you respond that the legal system doesn't work like that because having an effective way to avoid being identified doesn't make your conduct legal. But that wasn't the original claim.