> > The types could be automatically generated from a template, and > > managed by libvirt in much the same way it presently > manages categories. > > > > In any event, he can do the same thing by use of categories rather > > than introducing an incomparable set of sensitivities, and that > > wouldn't require any changes to the policy toolchain or > kernel security server. > > > > Well yes, but currently svirt can support out of the box > ~500,000 svirt instances, If we when with a type system, > this would probably some problems adding a couple of million > types. I don't think we want svirt recompiling and loading > policy every time it launches a virtual machine. > :^) > > Reserving a pool of categories at might be the way to go. > But at what security level? s15 or s0? Also what about > shared data between the virtual machines, read only content. > Currently that is just labeled s0. > I would suggest some level in between s0 and s15. I would agree with Stephen that dynamic types would be preferred. I guess it just depends on the reason you are using the MLS policy. -Chad -- This message was distributed to subscribers of the selinux mailing list. If you no longer wish to subscribe, send mail to majordomo@xxxxxxxxxxxxx with the words "unsubscribe selinux" without quotes as the message.
