https://bugs.winehq.org/show_bug.cgi?id=44661
Bug ID: 44661 Summary: Add networking feature to wine configuration Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: zakhar.nasimov@gmail.com Distribution: ---
This particular feature requests for simple networking options in particular to disable or enable wine and all wine software to internet connectivity. Currently gimmicks and workarounds are required to enforce this functionality. It may be implemented as a tab in wine configurations editor, were Libraries, Graphics, Audio, Drives along with other items are tabs, adding Network would make wine more feature complete and far more usable. It also adds a layer of security for any installed malware disabling its connectivity to the internet if it a form of such malware.
https://bugs.winehq.org/show_bug.cgi?id=44661
--- Comment #1 from Zakhar zakhar.nasimov@gmail.com --- Security isn't the prime motive for this feature, although it is an added bonus, its main focus is simply providing users the freedom to know installed software isn't able to access the internet for any reason.
https://bugs.winehq.org/show_bug.cgi?id=44661
--- Comment #2 from Zakhar zakhar.nasimov@gmail.com --- It doesn't need to be per software option, best would be globally enable or disable for all installed software.
https://bugs.winehq.org/show_bug.cgi?id=44661
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|major |enhancement CC| |dark.shadow4@web.de
--- Comment #3 from Fabian Maurer dark.shadow4@web.de --- I agree this would be very useful. If not meant for airtight security, at least to prevent applications from phoning home (and doing automatic updates for example).
https://bugs.winehq.org/show_bug.cgi?id=44661
--- Comment #4 from Zakhar zakhar.nasimov@gmail.com --- Get to work elves, or I will make your kernels panic.
https://bugs.winehq.org/show_bug.cgi?id=44661
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com
--- Comment #5 from Zebediah Figura z.figura12@gmail.com --- Does this in fact fall within Wine's scope?
In particular this seems to me like the kind of thing that should be solved on a different layer, for example, with Linux' network namespaces.
https://bugs.winehq.org/show_bug.cgi?id=44661
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |austinenglish@gmail.com Keywords| |download
https://bugs.winehq.org/show_bug.cgi?id=44661
--- Comment #6 from Rosanne DiMesio dimesio@earthlink.net --- (In reply to Zebediah Figura from comment #5)
In particular this seems to me like the kind of thing that should be solved on a different layer, for example, with Linux' network namespaces.
I think that's probably too difficult for most users to configure.
https://bugs.winehq.org/show_bug.cgi?id=44661
--- Comment #7 from Alexandre Julliard julliard@winehq.org --- (In reply to Zebediah Figura from comment #5)
Does this in fact fall within Wine's scope?
In particular this seems to me like the kind of thing that should be solved on a different layer, for example, with Linux' network namespaces.
That would be a better place for it, yes.
https://bugs.winehq.org/show_bug.cgi?id=44661
--- Comment #8 from Zakhar zakhar.nasimov@gmail.com --- Is this feature in a roadmap?
https://bugs.winehq.org/show_bug.cgi?id=44661
--- Comment #9 from Zebediah Figura z.figura12@gmail.com --- (In reply to Zakhar from comment #8)
Is this feature in a roadmap?
It is not, mostly because Wine doesn't have roadmaps, but also because it's not clear this feature in particular is desirable. Wine isn't a sandbox; if you want to sandbox Wine, then run it inside a sandbox. I don't see how that's infeasible in this case.
-
wine-bugs＠winehq.org