Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
Thank you, I will need to read up more on this. Could you describe how the networking with the proxy will work with respect to the firewall on the side of the host, involving the proxy?
If I understood your question correctly, you'd run the proxy application (which might be Squid or Apache or some other program) either on the host computer outside the VM or elsewhere on your network. (I'm not well versed on all the ins and outs of setting Firefox up to communicate through a proxy; I just know it can be done.) The proxy would listen for incoming traffic on a specific port you configure. You then tell Firefox (in its network settings) to communicate with the specific IP and port of the proxy instead of talking to web servers directly.
To prevent other programs from communicating, you'd firewall off the VM with iptables (or maybe ufw or something else depending on what you use on your system). You'd set it to drop all traffic going to/from the VM's network except packets going to or coming from the specific IP/port combinations you want to allow.
This isn't a bulletproof way to block other apps from talking to the internet -- anything that knows about the proxy (or which can hijack/manipulate a program like Firefox that you've told about the proxy) could communicate with web servers via the proxy, but depending on your specific concerns it may be good enough.
I see, it's simply disallowing everything except a specific port on that IP.
Considering that it will likely be a base Windows install, I don't think other applications will be able to hijack that specific port so swiftly. With that said, can I possibly only allow traffic to and fro from the proxy through my firewall? Assuming that I'll be running an HTTP proxy, I should be able to (in theory) inspect traffic too, although I don't know how far that will take me.
Yes. That is what I suggested. If you configure the firewall to only allow traffic to/from the specific IP and port combination of your proxy, other traffic will be blocked.
You can do content filtering via a proxy like that, yes. A similar sort of configuration is used on school computers to do things like block adult content, with varying degrees of success. Some ad-blocking techniques work on similar principles.
I was wondering if I could label the traffic to and from the proxy, and not have to rely on ports for filtering
You can whitelist both the proxy and the ip, blacklist everything else.
I see. Thanks!