Re:A modest update to Qubes OS
by katehikes88 on Sunday February 25, 2024 @10:14AM
(#39501394)
>multi-user support is planned
The github issues are nothing more than a wishlist. There doesn't seem to be any serious plans for this feature and no one seems interested in working on it. Limiting the user would require rewriting a large portion of the Qubes tools since they assume that the user has unrestricted access to the Xen API. I have looked at the feasibility of doing this myself in hopes of using Qubes in a corporate context but after looking into the architecture it became clear that I would never have time for such an undertaking.
>in the future a "qube" will be able to run on independent hardware
Qubes Air is vaporware and not under active development. There isn't much more to it beyond that blog post.
> Qubes Air is vaporware and not under active development
This is not exactly true, see the proof of concept:
Re:A modest update to Qubes OS
by katehikes88 on Sunday February 25, 2024 @02:21PM
(#39503863)
I suppose you didn't see the reply from a developer right under the post you linked.
I did. It's jut not true that it's vaporware. There was some progress.
Re:A modest update to Qubes OS
by katehikes88 on Sunday February 25, 2024 @04:09PM
(#39504790)
A proof of concept after five years and no serious plans going forward. There are plenty of vaporware with more to show.
> Qubes OS is designed to be a single-user desktop operating system
At the moment, it's true but multi-user support is planned: https://github.com/QubesOS/qubes-issues/issues/8958
> Note that the Qubes website and documentation tend to use the term "VM" and "qube" interchangeably
This is because in the future a "qube" will be able to run on independent hardware: https://www.qubes-os.org/news/2018/01/22/qubes-air. Then, VM and qube will not necessarily be the same thing.
> For example, installing software on a Fedora desktop is usually as simple as "dnf install package". But installing software to use within a Fedora-based qube requires several additional steps on Qubes OS, plus restarting VMs
If the software is installed from the main repo, you do the same "dnf install package" in a template. There are no other steps apart from restarting the App VM (which can also be avoided if necessary).
> Then again, it's also not encouraged—Bluetooth isn't considered secure, so why focus on making it easier to configure?
You can use Bluetooth securely on Qubes OS (but it does require some effort to set up): https://github.com/QubesOS/qubes-issues/issues/7750#issuecom...