[Bug 58299] New: [Feature request] Some sort of way of disabling internet connection per prefix.
http://bugs.winehq.org/show_bug.cgi?id=58299 Bug ID: 58299 Summary: [Feature request] Some sort of way of disabling internet connection per prefix. Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fatihbakal7(a)protonmail.com Distribution: --- Wine doesn't have its own networking settings and instead relies on the host Linux system's configuration. That said, I was wondering if there's a way to disable internet access on a per-prefix basis without implementing an entirely new networking layer within Wine. I'm asking this because Wine’s current approach to networking allows VPNs like Hamachi to function seamlessly with Windows applications running on Linux. Related issue: https://github.com/Winetricks/winetricks/issues/2379 Edit: Apologies if this isn't the appropriate place to suggest feature requests. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=58299 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |austinenglish(a)gmail.com -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=58299 mata <sutupud(a)yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sutupud(a)yahoo.com --- Comment #1 from mata <sutupud(a)yahoo.com> --- That's something commonly needed to run containers, where the solution is to use network namespaces to isolate networks. The same should also work here, specially in this case if the goal is to *not* have network access: unshare --net --map-current-user wine ... Actually setting up a working isolated network configuration would be more involved, but the tools for that already exist too, like slirp4netns or passt/pasta. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=58299 Ken Sharp <imwellcushtymelike(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|unspecified |10.8 --- Comment #2 from Ken Sharp <imwellcushtymelike(a)gmail.com> --- Windows doesn't have this, I don't think Wine should. You can already use a netns (unshare already mentioned). You could also simply disable certain DLLs and see if that works.
I'm asking this because Wine’s current approach to networking allows VPNs like > Hamachi to function seamlessly with Windows applications running on Linux
Is this a typo? Why is this a bad thing? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=58299 Zeb Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WONTFIX CC| |z.figura12(a)gmail.com Status|UNCONFIRMED |RESOLVED --- Comment #3 from Zeb Figura <z.figura12(a)gmail.com> --- This sort of thing has been requested before and rejected as being out of Wine's scope. Use external sandboxing tools like network namespaces is the prescribed solution here. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
WineHQ Bugzilla