frick at sc-networks.de
Wed Oct 4 10:17:52 CDT 2006
On Wed, Oct 04, 2006 at 09:41:16AM -0500, Tom Spear wrote:
> I should add that I just thought about this and realized that we
> _could_ always just encrypt the contents of the file as it is written
> and read, so that we can actually get somewhere, and not be exposing
> sensitive data at the same time, but it's just a thought. Anyone care
> to comment on that?
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). the difference in
the people able to read this data is just "total fool" to "fool" ;)
on the other hand you have your point with the way a court might sees
i think there is more of a problem with data theft. once i grab your
.wine/drives/c:/.windows-mbr file i might end up with your ps/dw/...
keys. its not even a problem to guess the location of that file.
assuming that the key is there stored directly - finding WINE users with
a legal and running copy of this software and the machine WFO to grab
it... i guess i a better off with a hit-and-run in the local software
store to get the software or just install some crack.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 163 bytes
Desc: not available
Url : http://www.winehq.org/pipermail/wine-devel/attachments/20061004/256592d9/attachment.pgp
More information about the wine-devel