> grained policy checks by a user-level policy daemon. This case has Micro
> binding and the timer is set for next Wednesday Feb 20th.
> This fasttrack defines the following "Consolidation Private" interfaces
What's meant by a Micro binding?
> INTERFACES
> +-----------------------+------------------+------------------------+
> | Interface | Classification | Comments |
> +-----------------------+------------------+------------------------+
> | <klpd.h> | Consolidation | |
> | klpd_create | Private | libc.so, SUNWprivate |
> | klpd_getpath | | |
> | klpd_getport | | |
> | klpd_getucred | | |
> | klpd_register | | |
> | klpd_register_id | | |
> | klpd_unregister | | |
> | klpd_unregister_id | | |
> | | | |
> | PRIV_XPOLICY | | <sys/priv.h> |
> | (flag to setpflags) | | |
> | | | |
> | ppriv(1) -x | | New option |
> +-----------------------+------------------+------------------------+
> The intention is to fully document and publish the final versions of
> these interfaces in a future case, once the project team has had sufficient
> time to experiment with them and receive feedback from the community.
I'm unclear on what is actually being delivered by this case.
Is there a policy daemon delivered? If so, what policies (privileges)
does it support? If not, why is this case being brought at this
time? Is it just too hard to keep the kernel in sync with prototyping
of FGAP? Are there some OS.O dependences that can't be met with a
project consolidation/gate? If this is dormant functionality, how
will it be tested from build to build?
What administrative interfaces are part of this case?
Gary..
