core-admin/qubespolicy
Marek Marczykowski-Górecki 6c3410377d
rpc-window: adjust for qubespolicy API
- drop qid usage - it isn't really needed, especially for to-be-created
  DispVMs
- use "domains_info" dict as input, instead of loading qubes.xml
  directly
- nicely format "Disposable VM" entries
- simplify whitelist/blacklist handling - since qrexecpolicy always
  provide a list of allowed choices, use just that

Important note: there are two names concepts:
1. Display name - name of VM, or in case of to-be-created DispVMs - a
string "Disposable VM (name-of-base-vm)"
2. API name - as in qrexec policy - $dispvm:name-of-base-vm for new
DispVMs

Externally at API level (allowed targets list, return value), API name
is used, but internally VMListModeler._entries is still indexed with
display names. This is done for more efficient (and readable) GUI
handling - because most of the time it's searched for what user have
entered.

QubesOS/qubes-issues#910
2017-04-07 17:07:29 +02:00
..
glade Import new rpc confirmation window code 2017-04-07 17:07:28 +02:00
tests rpc-window: adjust for qubespolicy API 2017-04-07 17:07:29 +02:00
__init__.py qubesd: add second socket for in-dom0 internal calls 2017-04-07 17:07:28 +02:00
cli.py policy: qrexec-policy cli tool 2017-04-06 15:43:17 +02:00
gtkhelpers.py rpc-window: adjust for qubespolicy API 2017-04-07 17:07:29 +02:00
rpcconfirmation.py rpc-window: adjust for qubespolicy API 2017-04-07 17:07:29 +02:00
utils.py rpc-window: code style adjustments 2017-04-07 17:07:28 +02:00