oiaohm wrote: > Again presuming far too much andreaplanet if wine is sandbox by system security the Z:\ does not tell you go every where so any detection that path will fail. > > You are correct in the statement that Z:\ does NOT exist with each and every Wine installation. Some users have disabled it or even moved it to prevent bad things from happening. > I was not talking about secuirty through obscurity as such. We provide a detect path we are able to limited so cannot remove it. If we find an attacker using a detect path we have to have the right to remove it we can limit the damage that can do. This is where the problem comes in with all the forms of detect so far. You are going to hook to something that we one day may remove. So then we get yelled at if we say do that. > > There is a really dirty way to detect wine and it is the most dependable by the way. Try to run .exe.so if it runs it wine or another emulator base off wine. If it don't run it not wine or the wrong platform type. You can catch this failure by the way. Again can be secuirty filtered against to stop it from functional operation. You could also allow the file to be removed if missing going on as if you are on windows. So meeting our requirements. This kind of support is not going to be removed because someone decides to abuse detecting wine. We already have a built in counter measure. dll overrides settings. Flip the default if dll is not listed as builtin don't allow it to be loaded as builtin. So detect would be dead as door nail if we ever had to kill it. Yet restore able by altering winecfg libs for the application. > > Basically at some point you many have to tell user how to enable the extras anyhow. So why not just be up front and ask them. Simpler by the way don't have to include .exe.so for linux bsd mac os solarias... Detecting wine is the hard path. > Here is what we are trying to tell you and andreaplanet: Help us make Wine better. If there is a function you absolutely have to have, let us know. We are here to help you the developer. In turn, this makes Wine better. This is what Wine is all about in the first place. It started as a project, a long time ago to get one or two programs to run on Linux (and before that OS/2). Windows is definitely a 'moving target' and we all have to work towards that target. Windows95/98 as old as they are, are still targets. More recently, WindowsXP. The project needs to fill in many blanks. Some exist on MSDN, some in more obscure places and some have no documentation at all. That is why we need your help as program developers to advise what is and is not working right for your program. Then we can fill in the blanks and also test what functions we do know about properly. The goal is to reproduce the Windows API as best we can without violating Microsoft code (and maybe in the process, fix a few Windows bugs.) James McKenzie
