[Ideas] Template/Guest OS/domU Security Goals

I’ve seen a recent uptick in requests for more security in domUs (templates, mainly), but most if not all have been vague and uninformed. I’d like this, but the first step in asking them to work on this is to present clear, concrete goals.

If you want more template security, then give your reasons here.

  • What, specifically, do you want better protected?
  • What current protections are not enough?
  • What things are you trying to defend against?
  • What do you hope to accomplish?
1 Like

This would be better discussed on GitHub :slight_smile: This is more likely to end up into something real.

What do you mean by “on Github”? Because…

Where’s the best place to discuss Qubes?

That would be the Qubes Forum and the qubes-users mailing list. Please have a look at our discussion guidelines before diving in. Enjoy!

1 Like

Since I don’t see anything else that could be additionally protected against of that’s not already included in the stock minimals and Qubes as general, and I can’t imagine anything else beside compartmentalizing as much as possible the templates for the purposes m threat model is defined of, Iam all eager to hear what I’m missing.