I apologize if this has been asked before - I’ve searched the forum and the docs and am not totally sure how to implement this because I am unfortunately very stupid. I have a Qube specifically for discord and I want to limit its connection so it can only access discord for the purposes of sending and receiving messages + accessing discord servers, nothing else. Is this possible?
You can limit the domain names/IPs that the Qube can contact using the Qubes Firewall (the GUI should be enough for your case)
As far as the domains for Discord are concerned, you can try looking them up on the Internet or install Wireshark in your Discord qube (or any proxyvm along the way) and check which servers Discord contacts. You can also use the browser console (Network tab) with Discord open in the browser.
Disclaimer: it may not be possible to achieve full functionality, as if I recall correctly, Discord calls are partially P2P, so it may not be fully possible to have that functionality.
If you manage to achieve your goal, I’d gladly see the list of domains/IPs you used, as this is a use case I wanted to implement for some time, but I haven’t ever gotten around to that.
You need this if you need a tight control URL filtering HTTPS proxy
@Atrate
That’s what I tried, although in my infinite wisdom, I just put in “discord.com”, nothing else, and expected it to work. I’m doing some testing right now based on your advice, and I will definitely post the full list for you and other users if I end up succeeding.
@solene Thank you! Your guides have been immeasurably helpful to me for quite a while. Once I figure out the domains, I’ll try implementing this.
The proxy will report the domains in the logs (whether they are allowed or blocked) so you can easily build the list until it works.
No one has mentioned the ports - I think you need to restrict to TCP 80 and
443. If you want voice, I think that uses UDP 50000-60000. (Check this)
I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.