Ah, so that's how securelevel will be done.
Might it not be even more interesting to make securelevel a directory with
each file corresponding to a certain ability, in each of which you could
only increase the level ? That way the several abilities would be more
orthogonal.
(of course, your script that sets up securelevels should warn if unexpectedly
files got added when booting a newer kernel. These files probably default to
very permissive, and might be enough to fight securelevel (e.g. an ability
to load modules allows you to write a module that hunts down secure level
variables in core and change them there.))
Ton
-------------------
There is no place like ~
.