Difference between revisions of "SVirt/TODO"

From SELinux Wiki
Jump to: navigation, search
(Post v1.00)
Line 56: Line 56:
=== Post v1.00 ===
=== Post v1.00 ===
* Support for session mode (not just system mode)
* Support for session mode (not just system mode)\
** Integrate with RBAC/UBAC ?
* Make DOI configurable
* Make DOI configurable

Revision as of 00:55, 11 December 2008

sVirt To Do List

For v0.30

  • Fix SELinux build configuration
  • Convert existing storage labeling
  • MCS dynamic labeling for simple isolation

Before v1.00

  • Identify which tools and related docs need to be made sVirt-aware
  • Security review by KVM and core virt folk
  • Review overall policy to ensure e.g. all command-line tools catered for, things like memory peek don't breach design etc.
  • Policy for save/dump/restore
  • Integration with GUI tools (virt-manager etc.)
  • General OS integration
  • Basic storage labeling support (investigate labeling for non-image devices, e.g. mapping UUID, HAL etc.)
    • Possibly include context-mount labeling of NFS bind mounts for remote images
  • Have domains run in separate directories to allow persistent labeling of resources (e.g. at rest, use MCS c0). (Check with danpb to see what the plans are here)
  • Find owner for Fedora (dwalsh or danpb ?) and add to feature wiki
  • Investigate generator.py for new API calls
  • Make autostart work properly
  • Policy for /dev/kvm (and similar)
  • Policy for control sockets, virtual console, vnc access, shared devices, parent/child communications etc.
  • Placement and policy for VM log files
  • Debug integration with audit subsystem
  • Add testcases to libvirt test framework
  • Handle qemud restart
  • Integration with oVirt ?
  • libvirtd config: require enforcing mode option ?

Post v1.00

  • Support for session mode (not just system mode)\
    • Integrate with RBAC/UBAC ?
  • Make DOI configurable
  • Migrate isolated domains between security models
  • Deployment of labeled appliances via virt-image etc.
  • Migration of labeled domains
  • Integration with virtual firewalling
  • Integration with Labeled Networking/IPSec/Labeled NFS (e.g. use of overlay VPNs for networks on host)
  • Extensive device labeling support
    • Labeling for all kinds of devices
    • Boot from network storage
  • Strong binding of resources to domains, via e.g. crypto, TPM, vTPM etc.
  • Support virtualization in policy generation wizard
  • Support for other security models (SMACK)