Cathy Zhou wrote: > Darren.Reed at Sun.COM wrote: > >> Cathy Zhou wrote: >> >>> Today, all network drivers (including physical network device >>> drivers and pseudo drivers like aggr) have the same device policy - >>> net_rawaccess for both read and write. However, Solaris allows the >>> device policy to be changed on the per-driver basis using add_drv(1m). >>> >>> My question is whether anyone knows there is any real case making >>> use of the per-driver device policy for any good effect, and whether >>> we could only apply the default policy, but remove[1] the ability to >>> set per-device policy rules, without hurting anyone. >> >> >> >> To reach out into left field... >> >> Consider a case where the base machine is using eri0 for its >> primary network interface but it has a card with bge's or bce's >> in it. You want to use zones and with zones you want to use >> IP instances with an exclusive stack instance per zone and >> those zones get bge/bce devices. >> > This seems that we need to provide a per-device policy instead of > per-driver policy.
What you're seeing with add_drv is a an architecture that allows different drivers to specify different policies even though they may be part of the same subsystem in Solaris. Your question therefore, to me, sounds like you want to exempt networking drivers from part of the general security architecture in Solaris, correct? Whilst advances in Solaris may now mean that we need to be able to specify the policy on a per-link or per-device basis for it to make more sense, that is an enhancement for the future. Darren
