qubes os

Some tools support delegation of services to a remote address, but sometimes they try to resolve DNS themselves using the local DNS resolver. The resolver would get an onion address and issue a DNS error because it doesn’t know how to resolve .onion, even if the machine itself is torified. You can use socat to create a local interface that binds a local port to an onion address, so that the tool won’t try to resolve the domain.

This guide will help you create an authenticated service for managing Qubes OS remotely

By design it will be:

• Encrypted
• Authenticated (with a key)
• Over Tor
• Works behind NAT/CGNAT
• No open ports required
• Accessible from any computer with a Tor Browser / Tails / Whonix

I found a way to use GPU in your QubesOS VMs. Now cracking/rendering on Qubes might be more realistic than ever.

This is a repost of a beautiful parulin’s post with minor additions. Helpful if your phone doesn’t mount to the VMs using standard options

This is how to automate and sync your backups across devices.

QubesOS is amazing for security, and equally amazing at making CTFs 10x harder than they need to be. It’s the firewall’s fault.

The reason why audio won’t work out of the box in minimal templates (debian-12-minimal, fedora-41-minimal) is that the package responsible for sending audio from VMs to your host (dom0 or sys-audio), pipewire-qubes, isn’t included in them by default.

When you try to run FreeRDP 3, you will likely get the BadAtom error.

QubesOS is built on the principle of isolation, and GPUs aren’t designed to meet the strict isolation requirements QubesOS demands because they prioritize performance instead.

Nix is great for keeping your system clean and your sanity slightly intact. But thanks to how QubesOS handles templates and persistence, it’s not plug-and-play.