Downing, Thomas wrote:
> How does the server _know_ that the BIOS is what it says it is? Again,
> what's the protocol? Saying that they 'have a chat' is bypassing
> the hard bits.
>
> If I have the BIOS, any secrets it holds are now knowable to me.
> This means that any protocol that relies on a secret in the BIOS is
> broken from the start. So now you need to define a protocol which
> does not rely on any secret being known to the BIOS. What is this
> protocol?
What makes you think you can read the BIOS?
> The proposed 'end-to-end' copy protection schemes for entertainment
> media etc, rely on proprietary _hardware_.
Yes, that's the severe version of DRM that we're talking about, for
the game server scenario.
> This is still beatable, although at a higher cost. Nor is the
> problem quite parallel. The broadcast problem is 'how do we keep
> content encrypted till the last possible moment?' and 'how do we
> keep the decryption engine tamper proof reverse engineering proof'.
> The first part is easy. The second part is not possible in an
> absolute sense. It can only be made more or less dificult. Hence
> the DMCA etc.
We don't know for sure that it's not possible to make something
reverse engineering proof. Although all current CPUs require code to
be decrypted at some point, there may be modules of computation that
don't require that, so there would be no way to extract the secret key
or decryption process in a useful way even when you can see every
electronic signal in a device. The jury is out on it, despite what
slashdotters believe.
-- Jamie
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Apr 30 2003 - 22:00:18 EST