0

I want to fully migrate the last computers in my reach to Kubuntu but i hit a another roadblock.
You can run a lot of applications that people are used to with wine.
The issue comes from applications that have geo-blocking in place for content.
On Windows there is a nice little graphic tool called Proxifier.
This allows you to limit the proxification to certain applications and even only specific hosts that are required to trick the app
and get around the limitation.
There is redsocks , there is transsocks but they are not flexible and they are not that nice to configure.
Therefore i would love to see a graphical utility that would allow a user to configure redirects for certain hosts&apps to a proxy with a few simple clicks
without having to dive into the command line.

Doesn't it make more sense to place such applications into a virtual machine or a docker container so that you have the full power of network management on your finder tips?
I'd say this makes especially sense to applications based on a Wine environment, since those are typically ClosedSource blobs with all their issues...

I think a virtual machine or docker container is too heavy for rerouting a few connection and a single application.
As a virtual machine you would also need a license to run inside that.

nineo wrote:I think a virtual machine or docker container is too heavy for rerouting a few connection and a single application.

Docker poses nearly no overhead compared to a native execution of an application. Yes, an initial setup is required, but that is a one time addition which can even be mostly automated. And something you'd have to do too when using some "proxification solution".

nineo wrote:As a virtual machine you would also need a license to run inside that.

Why that? What kind of "license" would you need? Where is the difference if you use a software in the host system or inside some virtual machine?

arkascha wrote:Docker poses nearly no overhead compared to a native execution of an application. Yes, an initial setup is required, but that is a one time addition which can even be mostly automated. And something you'd have to do too when using some "proxification solution".

Why that? What kind of "license" would you need? Where is the difference if you use a software in the host system or inside some virtual machine?

The end goal is to get rid of the windows license completely so running windows inside a virtual machine is not an option.