Dom0 compromized? Just swap it with an uncompromized version from the repository

Keep preaching the Ops sec gospel, hopefully we can all learn from this. Thanks, :v:

What is the recommendation of just re-installing everything -every ??? months?

Just to be sure.

That’s a good question. I wish I could do it every day automatically as most servers can automate this activity. This issue is I am not complete confident that my backups will occur because of the screen lock timer. So by default, I need to stay alert so that the screen doesn’t stop during the time required to backup. Please, keep in mind the time required for backups increase as make you more VMs.

I have no idea what would be a good way to automate the function as I cringe every time I think of making a backup.
That’s just my opinion, I am sure there are others out there that have way more experience in this activity and may provide you better insight as to how to best manage it.

But if you make a schedule, make it simple yet rigid to build in discipline by repetition.

Good luck!

I guess when you do a fresh install, specially if you use a usb drive (usual, I think) you can expose the machine to USB atacks. So, I do not know it tha is good idea.

The backup/restore GUI are very simple wrappers around qvm-backup and
qvm-backup-restore. Get familiar with those and write your own scripts.
This way you can:

  1. run backup unattentded
  2. if no error, verify backup unattended
  3. if no error, shutdown or do whatever else you want to automate

Also with your own script calling qvm-backup you can do things like:

  • backup every qube into it’s own backup file
  • backup some qubes more often then others
  • backup templates only if they changed
  • … etc
1 Like

Thanks for the suggestion. It’s on my weekend todo list. Thanks,

Why would you think that? :confused:

If the screen locks during a backup, why not just… unlock it?

I wish the GUI was more user-friendly, so people would not have to learn too many CLI tools.

I wish the GUI was more user-friendly

The OP was asking for ways to automate, I don’t think that’s a valid
context to criticize the GUI. It does in fact expose almost all options
the command line gives you sans the dangerous one (e.g. backup without
encryption).

Also luckily @adw picked up on the real head scratcher here. Why does
the OP feel the need to keep the screen unlocked? This may interest
@ninavizz too.

1 Like

I did not know that screenlockers did not interrupt background processes, until I was told as much. Yes, users will assume what may seem irrational to folks that understand how the internals work. We need to respect that, and improve how we communicate with non-technical users. :slight_smile:

@fsflover We’re working on it! We really are. Qubes’ funding today is very modest, and we can only do so much. Please bear with us.

1 Like