[redhat-lspp] LSPP/RBACPP requirements v.002

[Steve Grubb]

On Wednesday 28 September 2005 14:20, Stephen Smalley wrote:
> - is the context of the peer socket the right context in which to run
> the service (at the very least, for the TE type, the answer is no)?

No.

> - does xinetd have enough information to compute the right context in
> which to ultimately run the service, since it doesn't handle user
> authentication itself?

xinetd's purpose in life is to start apps with the right environment & 
permissions. The admin would have to configure the context that the program 
would start in. Anything other than this is not really what xinetd does.

> - if xinetd transitions to a context based on the peer socket, and the
> service then wants to transition to a context based on the authenticated
> user, how do these transitions interact with one another (e.g. can the
> latter fail due to the former; should the latter be based off the former
> in some way)?

People misconfigure it all the time. This is just another way to shoot 
yourself in the foot.

> - do you trust the client to supply the context in which to run the
> service?

I would think the admin configures it in the /etc/xinetd.d/service-name file.

> - what happens when the client and server have different context/policy
> definitions?

I'd say you have the same problem with any networking app.

-Steve