qubes-tunnel
Contents
qubes-tunnel | Contents | |
---|---|---|
5 | 85 | |
20 | 253 | |
- | -0.4% | |
3.6 | 6.3 | |
8 months ago | 6 months ago | |
Shell | Shell | |
GNU Lesser General Public License v3.0 only | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
qubes-tunnel
- VPN qube
-
Qubes 4.1 / Fedora 35 VPN Qube Issues
Github Source
-
Help with getting Wireguard to work in QubesOS
I've tried using both with qubes-vpn-support and qubes-tunnel. Both of the setup instructions seem about the same. As I've read on a few forums, if I follow this guide but replace the Mullvad conf file with the one I was given above, it should work just as well.
-
Setting up the network with a VPN,
Use qubes-tunnel; the setup is much easier.
-
Problems with setting up a ProxyVM
Try qubes-tunnel-service instead, it should work a lot better out of the box. (Dunno if it has IVPN support, but, if IVPN support OpenVPN it should be fine).
Contents
-
QubesOS – A reasonably secure operating system
I've been using Qubes for the past 2 years while going to school, and I found it really fun and helpful. A lot of professors had me download random closed source software from random websites during the pandemic, and it was easier to download it to a VM than to convince them about Free Software. More than that though it's been really helpful just for my own workflow. I can hit a keybind and start working from essentially a fresh linux install. It's easier to stay on task when each VM is designed to only do one kind of task. It's also nice having debian, fedora, windows, kali, and whonix all easily accessible on the same machine.
The main sticking point for me is that Qubes is reasonably secure from _myself_. I make mistakes. I first started using linux with an Ubuntu install that I broke a year later because I accidentally added in a space when typing `rm -rf ~/Arduino` which made it `rm -rf ~ /Arduino`. On Qubes I can `sudo rm -rf /` on the VM I'm using right now and not break a sweat. I have a keybind to spawn a disposable "airgapped" VM to deal with sensitive or untrusted data, and it helps knowing that even if I mess up with whatever I'm doing, the VM will keep everything reasonably contained.
Some cool things that Qubes has outside of just VMs are its features enabled by the communication between VMs. Notable ones are Split GPG (https://www.qubes-os.org/doc/split-gpg/) which let you use a VM as if it were a smartcard for GPG and Split SSH (https://github.com/Qubes-Community/Contents/blob/master/docs...) which let you isolate your private SSH keys from your VM running your SSH client.
There are some sticking points around Qubes. For instance, I use Tailscale to connect my computers to each other from anywhere. Tailscale's install scripts add their keys to my VM's package manager for updates and installs. The proper way to do this in Qubes is to clone a TemplateVM, run Tailscale's install script, update, install, and then base an AppVM off of it. But that creates an entire new OS taking up storage and requiring updates. You can hack a way around this in an AppVM which saves a considerable amount of space, but it takes a lot of upfront time to do and requires you to manually update it.
Another sticking point is hardware acceleration. The desktop environment has access to hardware acceleration, so it runs fine, but opening videos in AppVMs is all software decoded. I'm on a Thinkpad T580 and it can run 1080p videos, but the fans turn on and can't do 4K. When I want to game or do something GPU heavy I either stream from my tower or completely switch over.
Overall, I'm really happy with Qubes and I'm planning to stick with it on my laptops.
- Installing Windows 10 as a Qube. The install crashes at 10% in the "Getting files ready for installation" stage
-
GPU passthrough on Qubes?
I can't speak to 17+ GPUs - but have successfully passed through a single high-end GPU for gaming via following these instructions: https://github.com/Qubes-Community/Contents/blob/master/docs/customization/gaming-hvm.md
- Qubes OS new templates?
- Installer crashes at last moment ?
- Dual-booting Qubes and a Debian distro?
- ArchQubes?
-
Windows 7, 10, or 11 vm in Qubes-Os
Yes its possible. But check here under "Audio Support", also says at the bottom that windows 7, 10 & 11 are fully supported. As for how to install Windows, here. And installing Windows 11 by disabling the TPM check: https://forum.qubes-os.org/t/windows-11-in-qubes/6759/8.
- ISO download for HVM failing on all VMs
-
VPN Killswitch?
Follow this guide https://github.com/Qubes-Community/Contents/blob/master/docs/configuration/vpn.md
What are some alternatives?
Qubes-vpn-support - VPN configuration in Qubes OS
algo - Set up a personal VPN in the cloud
proton-bridge - Proton Mail Bridge application
qubes-app-split-browser - Tor Browser (or Firefox) in a Qubes OS disposable, with persistent bookmarks and login credentials
bitmap-fonts - Monospaced bitmap fonts for X11, good for terminal use.
qubes-windows-tools-cross - Qubes Windows Tools build with mingw, wine and qubes-builder
qubes-issues - The Qubes OS Project issue tracker
dotfiles - :computer: my ricing configs.
bubblejail - Bubblewrap based sandboxing for desktop applications
dangerzone - Take potentially dangerous PDFs, office documents, or images and convert them to safe PDFs
Qubes-VM-hardening - Fend off malware at Qubes VM startup