Rob Meijer wrote:
quoted text
> What may be even more relevant are those concepts that couldn't be done
> in SELinux, and how proposals that come from the theory of alternative
> access controll models (like object capability modeling) are dismissed
> by the aparently largely MLS/MAC oriented people on the list.
Clearly what is needed here is for someone to actually implement an
object capability LSM module. None of SELinux, SMACK, LIDS, AppArmor,
MultiADM, or TOMOYO can implement object capabilities, so there is clear
justification for building such a module. I would argue strongly to
include it.

quoted text
> Thus IMHO it may be a good idea to instead of a maintainer for LSM
> modules as proposed, alternatively a maintainer for each formal model
> may be more appropriate. This also would require module builders to first
> think about what formal model they are actualy using, thus resulting in
> cleaner module design.
>   
I *really* dislike this idea. It seems to set up the situation that the
only acceptable modules are those that follow some "formal" model. Problems:

    * What qualifies as a formal model? This becomes an arbitrary litmus
      test, depending on whether the model was originally published in a
      sufficiently snooty forum.
    * What if someone invents a new model that has not been "formalized"
      yet? Should Linux be forced to wait until the idea has been
      through the academic mill before we allow someone to try
      implementing a module for the idea?
    * The proposal only allows a single implementation of each formal
      model. In theory, theory is just like practice, but in practice it
      is not. SMACK and SELinux follow substantially similar formal
      models (not exactly the same) so should we exclude one and keep
      the other? No, of course not, because in practice they are very
      different.

Crispin

-- 
Crispin Cowan, Ph.D.               http://crispincowan.com/~crispin
CEO, Mercenary Linux		   http://mercenarylinux.com/
	       Itanium. Vista. GPLv3. Complexity at work

-
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/