Hi,
I’m looking for suggestions on how to set up remote access to my Qubes system without using the GUI configuration (as it has too many issues) or via the available TOR access, which is too slow.
If you can point me to or suggest a method similar to RustDesk/Tailscale for remote access, that would be great. The specific tool isn’t really important right now; I’ll test what works best. I just want to outline what I’m trying to achieve.
I don’t think that anybody worked on what you’re requesting; closest thing would be the “sys-gui-vnc” construct, but you state that you don’t want that.
Access to dom0 via network? Dom0 has intentionally and for so much good reasons no network at all.
Btw. why you don’t use any standard linux distribution like debian or fedora (or even windows), that will better fits such a scenario.
QubesOS is build on top of the principle of a XEN hypervisor with an completely network isolated (and “networkless”) dom0 and several domUs that can be connected to several networks or can be isolated also.
It would help a good deal if you explained what you want to achieve by
having remote access. Although you refer to this you have not given any
information, not even an outline.
Do you want to configure or create new templates and qubes?
Do you want to be able to access qubes/templates remotely?
What sort of access do you want?
Do you want to load qubes windows on the remote machine?
I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.
Essentially, I can’t operate in my daily life without Qubes; it’s become essential.
I have used remote access with Tailscale and RustDesk to access individual HVM environments from my mobile device and laptop. However, I really need remote access to dom0. Unfortunately, I have to accept the risk factor associated with this, and I’ve already found the sys-gui/gui-vnc solution too unstable based on my experience.
Unfortunately, Qubes-air doesn’t seem like solution(coming anytime soon) to this problem from my understanding of it. To answer your questions directly, yes, I need full visual remote access to dom0.
Im at a point where using any normal operating system alone without
any form of access to Qubes feels unnatural, and would be very helpful if I could always access my “Qubes server” and use it fully as if sitting infront of it.
Enable network and ssh. Then remote desktop over ssh. It is not secure and against qubes-philosophie.
Ok - something more than an outline.
You can do this, as has been pointed out, but it runs against dom0
security model. You are willing to make that compromise.
Depending on your needs you could retain a little of the Qubes security
model by using a remotely accessible management qube, and a bridgehead
qube that allows you to access other qubes: depending on how you use
them, and what they are used for, this might do. But that’s more detail
that you havent provided.
I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.
I do. For the same reason: A QubesOS server.
QubesAir takes too long, so i am trying to ducktape together something minimal that works for me to move qubes from my laptop to a server for continuous operation.
At the current stage, i have some troubles getting VNC starting the desktop environment correctly, but when i find some time for more troubleshooting this, the most of the (not troubleshoot) work is done and this is the last thing not quite working. SSH into server on sys-net, local port forward over SSH VNC from dom0.