You can now validate for WGA downloads using wine and the Microsoft WGA validation tool, and you'll get a thank you message from Microsoft for using Microsoft genuine downloads. Also the anti wine checks appear to be disabled as the tool works in both windows 2000 and windows 98 mode, however the wine registry key string is still in the binary, maybe it's just disabled. In any case some EU officials have already expressed an interest in these checks, so if they enable them someone may end up getting another super fine.
Ivan.
On Fri, 5 Aug 2005, Ivan Leo Puoti wrote: [...]
Also the anti wine checks appear to be disabled as the tool works in both windows 2000 and windows 98 mode, however the wine registry key string is still in the binary, maybe it's just disabled.
IIRC it's checking the location of the old Wine config registry key. This has all moved as part of the config file removal (and as was planned long before WPA came around).
No doubt they will update their WPA checks at some point...
Hi,
On Fri, Aug 05, 2005 at 12:18:32PM +0200, Francois Gouget wrote:
On Fri, 5 Aug 2005, Ivan Leo Puoti wrote: [...]
Also the anti wine checks appear to be disabled as the tool works in both windows 2000 and windows 98 mode, however the wine registry key string is still in the binary, maybe it's just disabled.
IIRC it's checking the location of the old Wine config registry key. This has all moved as part of the config file removal (and as was planned long before WPA came around).
WGA! ("Windows Genuine Disadvantage", not XP's "Windows Product Activation")
No doubt they will update their WPA checks at some point...
Hmm, let's hope they know what to do or not do, also in light of the EU investigation reports, then...
Andreas Mohr
Francois Gouget wrote:
On Fri, 5 Aug 2005, Ivan Leo Puoti wrote: [...]
Also the anti wine checks appear to be disabled as the tool works in both windows 2000 and windows 98 mode, however the wine registry key string is still in the binary, maybe it's just disabled.
IIRC it's checking the location of the old Wine config registry key. This has all moved as part of the config file removal (and as was planned long before WPA came around).
No doubt they will update their WPA checks at some point...
Would it be wiser to implement a wine feature to block a particular application from seeing a particular registry key. We could then only allow the key to be visable to the application it would actually be useful for. I think the MS windows registry already has this feature in order to provide security for certain registry entries.
James
James Courtier-Dutton wrote:
Would it be wiser to implement a wine feature to block a particular application from seeing a particular registry key. We could then only allow the key to be visable to the application it would actually be useful for. I think the MS windows registry already has this feature in order to provide security for certain registry entries.
Blocking wine would probably be against anti trust laws so I don't see the point. I'd prefer to see them forced to remove anti wine stuff by a court rather than work around stuff like that.
Ivan.
James Courtier-Dutton wrote:
IIRC it's checking the location of the old Wine config registry key. This has all moved as part of the config file removal (and as was planned long before WPA came around).
No doubt they will update their WPA checks at some point...
Would it be wiser to implement a wine feature to block a particular application from seeing a particular registry key.
I disagree. If Windows has such a feature and/or it's somehow useful in other situations it could be implemented but doing this to get around their Wine detection is just silly - we couldn't win that race as there are zillions of methods to detect Wine and most of them can't be avoided (the first thing that comes to my mind which can't be worked around in userspace is doing a unix syscall for example).
Felix