[Wine] Re: creating built-in firewall for Wine

Boriso wineforum-user at winehq.org
Fri Apr 8 12:59:17 CDT 2011


oiaohm wrote:
> 
> > 
> > Anyway, I got many useful information from this topic. I also tested my idea about chaging ws2_32.c and it works fine. Now I'm going to examine Wine deeper.
> 
> 
> Don't expect this integrated.  Your path is purely the wrong way.  For the simple reason there is no requirement in wine design for future network interface features to pass through ws2_32.c.   You are basically setting self up for bruising.   Wine dll.so files only have to use windows path pf dlls above them to perform tasks if programs could be effected.   So mshtml emulation lot of places that could be coded going directly to the Linux network stack.  So ws2_32.c would not see those requests.

I'm using Ubuntu for several months and haven't installed Wine before because I had no understanding how it works and what are advantages for me. Now I tried to solve one problem and predicted that Wine could help and firewall was just a single point. Eventually I tried to do something and became more familiar with Wine.



oiaohm wrote:
> 
> Boriso wrote:
> > 
> > I looked through http://wiki.winehq.org/CategoryToDo and found no firewall or something similar, but here http://wiki.winehq.org/WineReleaseCriteria?action=show&redirect=WineReleasePlan one could find that "Wine add-ons" are already suggested and this is great. I think that Wine add-ons could made contributions more intensive.
> > 
> 
> Reason zero point.   Native firewall is good enough for what they provide.  Wine transparency to native system firewalls could be improved.     Native firewall uses does not leave flaws particular if it used how I directed.

Thank you for your directions, I'll try because security important even without Wine. But I have no experience before in IP Tables configuration. I also find on another forum a configuration file for AppArmor to prevent Wine for particular PREFIX access folders that are not belong to an installed application. I think that some kind of script or internal Wine command would be great if it could create new Wine prefix and configure some restrictions in IPTables and/or AppArmor. In this case security of Wine itself would increase.
Anyway, your explanation must be placed somewhere in wiki here, so it would become real tutorial someday.



oiaohm wrote:
> 
> > 
> > In my opinion Wine is open but not very friendly with sharing information about the project. For example, there are many TODOs, wishlists, information about architecture, user manuals and so on. But there could be some pdf booklet or presentation (even in flash) that explains how Wine works, what are pros and cons, what is left to do. 
> > This is kind of a marketing, but good external package is also important. In case you are talking about people who already know everything about Linux, Wine they do not need anything more, but for novices (like me) and ordinary desktop Linux users it is also important. 
> > 
> 
> There is the wine users guide.  Documentation is a problem.  We are desperately short of technical writers.   We don't have the personal to write the PDF or create presentations and keep them upto date.  We have enough trouble keeping the http://www.winehq.org/docs/wineusr-guide/index staffed as well as keeping the FAQ correct
> 
> Lots of the pro and cons we really don't know how long they will stay true.
> 
> wishlists most developers don't read.  Better as feature requests in the bugzilla.
> 
> What left todo at least the 6000+ open bugs to close is what left todo.

I still don't see a main target of the Wine Project.
Would you become happy if I say that now only 5000 open bugs are left? And what to do when there would be no bugs left?
Could you provide any milestone dates and bugs decreasing prediction?
Maybe these bugs could be left and movement started to the REAL target? Of course if process for process is not the main target. 

I just want to understand how to estimate the distance between current and desired situations.

`Would you tell me, please, which way I ought to go from here?'
`That depends a good deal on where you want to get to,' said the Cat.
`I don't much care where--' said Alice.
`Then it doesn't matter which way you go,' said the Cat. 







More information about the wine-users mailing list