karstenanderson at gmail.com
Wed Oct 4 11:25:17 CDT 2006
why not just implement the write to MBR? figure out how the copy
protector does it and just implement it. as long as you know what
you're doing and where the O/S stores its stuff you should be alright.
put a few warnings on the instaeller and whatnot that this might be
risky, and then let the user decide for himself :)
On 10/4/06, Stefan Dösinger <stefandoesinger at gmx.at> wrote:
> > what keeps some nosy haxx0r from looking in the MBR (or some blocks
> > later) if he wants to find out about the copy protection? if they store
> > data like this unprotected (e.g. crypting them) then this is just
> > security-by-obscurity (which is no security at all).
> Copy protection IS security by obscurity from a cryptography point of view ;-)
> The thing is that the user HAS to be able to decrypt the movie / game /
> whatever and use it, so in some form he HAS to have the keys. The only thing
> that can be hidden is the algorithm and the location of the keys(sort of part
> of the algorithm). This can't work from a mathematical point of view.
> What makes copy protection problematic to circumvent is not the math or the
> technical stuff, it is the laws protecting it :-(
More information about the wine-devel