[rsbac] Trusted Path Execution and scripts
jens at igraltist.dyndns.org
Wed Jul 19 13:51:12 CEST 2006
why you set not on all directorys a rc-type and on all important files l
like /etc and /var.
through this, exclude all user wich has no map_exec or read right or execute
or what is nessesary.
to get access the user must in a rc-role and assign the rc-type to this
all other i think get to complicatet, wich is a security file or system file
so no removing expilzit the rights form a file or binary, when is get the
rc-type it will by defautl get nothing.
than you can build policies for each rc-role , whom allow what.
and if is an a script after some upgrad then you can easy apply this.
this policy will also grow quickly, so a good design is recommend. :)
Am Mittwoch 19 Juli 2006 09:17 schrieb tazok:
> normal_binaries, secoff_binaries, root_binaries and
> whatever_you_want_binaries, the same with libraries. This types will be the
> unique to get access to MAP_EXEC and EXECUTE privileges. For now all is
> correct. The problem begins when the binaries perl, python and bash arrives
> and their scripts (untrusted scripts). The solution I thought was marking
> those binaries with a new forced role as perl_role or something like it and
> remove all READ_OPEN and possibly all READ and READ_WRITE_OPEN privileges
More information about the rsbac