Qvm-connect-tcp to Kicksecure 18 distro-morphed from debian-13-minimal

[ephile]

@gasull

Does Kicksecure or minimal templates disable qvm-connect-tcp?

I suspect it has to do with Kicksecure, since I have never had any trouble using qvm-connect-tcp with debian-13-minimal qubes. Even though it doesn’t touch on Kicksecure, when it comes to digging into the issue, you may find something useful in the following thread:

Understanding how qvm-connect-tcp works under the hood

qvm-connect-tcp plays an important role in Qubes, so I’m trying to understand it more fully. In particular, I’m confused about how it works to expose a service with a simple port binding. Any insight into the following would be appreciated and hopefully of value to the forum at large. In general, exposing a service with socat in a server-client setup would look something like user@server$ socat TCP-LISTEN:55555,reuseaddr,fork,bind=server TCP:localhost:55555 enabling user@client to call on the…