I'm also using wine for some windows program tests. I think the problem for the common usablity is, that often programs replace the original windows files by customized ones. Also there are many versions and wine can only have one. Most setup's handle this for native windows versions. Wine has the problem, that the dll's and others from the programs need the right version of the simulated dll's. That is the cause for most of my problems with wine. The unimplemented functions are often in the log, but mostly it works without them, when the dll seetings are right. For someone not knowing much about windows internals, it's hard to get the right settings. When all this works, yes, you have the problem, that even simple programs, are very slow. Don't know why.
You have to keep the policy of your SE Linux installation up to date and customize it for your needs. I've found, it's a time consuming job to do so. If you haven't too much time, I would suggest to wait, until there is a tight default policy for more packages and it is integrated in the actual stable linux kernel. Also SE Linux is only a small part of security. For the average user, a personal packet firewall, JavaScript and co. filter and stack smashing protection (e.g. supported by Open BSD AFAIK), should be more helpful.
Slashdot Mirror
I'm also using wine for some windows program tests. I think the problem for the common usablity is, that often programs replace the original windows files by customized ones. Also there are many versions and wine can only have one. Most setup's handle this for native windows versions. Wine has the problem, that the dll's and others from the programs need the right version of the simulated dll's. That is the cause for most of my problems with wine. The unimplemented functions are often in the log, but mostly it works without them, when the dll seetings are right. For someone not knowing much about windows internals, it's hard to get the right settings. When all this works, yes, you have the problem, that even simple programs, are very slow. Don't know why.
You have to keep the policy of your SE Linux installation up to date and customize it for your needs. I've found, it's a time consuming job to do so. If you haven't too much time, I would suggest to wait, until there is a tight default policy for more packages and it is integrated in the actual stable linux kernel. Also SE Linux is only a small part of security. For the average user, a personal packet firewall, JavaScript and co. filter and stack smashing protection (e.g. supported by Open BSD AFAIK), should be more helpful.