On Oct 16, 2007, at 5:09 PM, Garrett D'Amore wrote:
> I think this may warrant promotion to a fast track.
>
> In particular, the interface that the LMS exports to the rest of the
> system (perhaps just acting as an HTTP proxy) warrants some basic
> review.
>
> The questions I'd like to see answered in a fasttrack are:
>
> 1) does LMS export any interface over the network? (If its a web
> proxy....)
>
> 2) what is the administrative interface to manage the LMS service?
> (SMF? properties for managing what port it binds to, etc?)
>
> 3) how does this fit within secure-by-default? Does the service
> listen only to IN_ADDR_ANY, or does it open up a port accessible to
> the
> entire network?
Furthermore...
4) What access control does LMS provide (IP ACLs, AAA, Kerberos)
5) Fault management is a purpose of AMT. Should AMT be
considered for integration with Solaris's existing fault management
framework, FMA? Do the two really need to be separate which
necessitates distinct management methods/infrastructure?
6) Why /usr/lib/lms and not /usr/lib/amt/lmsd ?
/dale
