Compromised via qvm-move/qvm-copy?

xl dump-core <qube-name> /path/to/file

Can create a memory dump of infected qube, but command create dump file in dom0 storage space.
Anyone have an idea how to steam this output to network gap qube “forensic storage”?
maybe,qvm-run --pass-io

Few ideas regrading topic:

  1. Check if qvm-pause <qube_name> --suspendsupported for templates and qubes you use.
  2. In order to use dom0 as last resort for snapshots of infected qube, consider to increase varlibqubes path size: No diskspace in varlibqubes for installing templates - #3 by rustybird (Keep in mind: Malware capable of escaping archives without user interaction does exist. Never assume archived files are safe simply because they haven’t been opened.)
  3. Replacing passwordless root with a dom0 prompt can be used with limited to dispapp only. In step [root@dom0 /]# echo "@anyvm dom0 ask,default_target=dom0" \
    >/etc/qubes-rpc/policy/qubes.VMAuthreplace @anyvmwith @type:DispVM.
  4. Use qvm-run -u rootfor management of network isolated qubes, templates and disposable templates, but not for AppVM’s and named disposables (for templates configured with dom0 prompt)
1 Like