qrexec-policy-graph.rst 2.2 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273
  1. .. program:: qrexec-policy-graph
  2. :program:`qrexec-policy-graph` -- Graph qrexec policy
  3. =====================================================
  4. Synopsis
  5. --------
  6. :command:`qrexec-policy-graph` [-h] [--include-ask] [--source *SOURCE* [*SOURCE* ...]] [--target *TARGET* [*TARGET* ...]] [--service *SERVICE* [*SERVICE* ...]] [--output *OUTPUT*] [--policy-dir POLICY_DIR] [--system-info SYSTEM_INFO]
  7. Options
  8. -------
  9. .. option:: --help, -h
  10. show this help message and exit
  11. .. option:: --include-ask
  12. Include `ask` action in graph. In most cases produce unreadable graphs
  13. because many services contains `$anyvm $anyvm ask` rules. It's recommended to
  14. limit graph using other options.
  15. .. option:: --source
  16. Limit graph to calls from *source*. You can specify multiple names.
  17. .. option:: --target
  18. Limit graph to calls to *target*. You can specify multiple names.
  19. .. option:: --service
  20. Limit graph to *service*. You can specify multiple names. This can be either
  21. bare service name, or service with argument (joined with `+`). If bare
  22. service name is given, output will contain also policies for specific
  23. arguments.
  24. .. option:: --output
  25. Write to *output* instead of stdout. The file will be overwritten without
  26. confirmation.
  27. .. option:: --policy-dir
  28. Look for policy in *policy-dir*. This can be useful to process policy
  29. extracted from other system. This option adjust only base directory, if any
  30. policy file contains `$include:path` with absolute path, it will try to load
  31. the file from that location.
  32. See also --system-info option.
  33. .. option:: --system-info
  34. Load system information from file instead of querying local qubesd instance.
  35. The file should be in json format, as returned by `internal.GetSystemInfo`
  36. qubesd method. This can be obtained by running in dom0:
  37. qubesd-query -e -c /var/run/qubesd.internal.sock dom0 \
  38. internal.GetSystemInfo dom0 | cut -b 3-
  39. .. option:: --skip-labels
  40. Do not include service names on the graph. Also, include only a single
  41. connection between qubes if any service call is allowed there.
  42. Authors
  43. -------
  44. | Marek Marczykowski-Górecki <marmarek at invisiblethingslab dot com>
  45. .. vim: ts=3 sw=3 et tw=80