Hi Gary,
Thanks for your comments and sorry for later reply because it
costed me some time to get more background knowledge about SMF
on Solaris. Basically we use the simplest service manifest file for the
acpihpd service and haven't defined any security relative properties
in the service manifest file.
Please also refer to inline comments below.
Thanks!
--Gerry
Gary Winiger <mailto:gww at eng.sun.com> wrote:
> Mike,
>
>> I'm working with Intel to answer your questions. Essentially we
>> want to provide the least amount of access possible for this daemon
>> to do its job.
>
> IIRC, my initial question had 3 parts: How does the project meet
> the SMF requirement for authorizations to manage? What is the
> Method Context used to start the service? The service is to be
We haven't defined any method_environment, method_profile,
method_credential or method_context properties in the manifest file.
So it should use the default configuration, is that OK?
> enabled only on the xxx platform - how is this done?
The service will be enabled on all x86 platforms. We provide an x86
specific package named SUNWacpihpd, which includes the service
manifest file for acpihpd. When installing the package, the acpihpd
service should be installed and enabled. So seems we don't need to
touch the platform profile file, is that true?
>
> I'd like to clarify the first part about authorizations. When
> we talked I may not have been complete.
> If there are no properties that configure the service as in
> a property group of type application, there is no need for
> value authorizations to manage them.
Currently acpihpd service doesn't define any properties of category
"application", so seems we don't need to define the "modify_authorization",
"value_authorization" and "read_authorization" security properties.
Is that true?
> If the service is never intended to be enabled/disabled by
> the administrator (but always enabled/started automatically
> at boot time and never disabled), there is no need for
> action/value authorizations to manage the service.
The service should always be enabled and not intended to be managed
by administrators.
> If both are true and there is no need for defining authorizations
> for the service, there is no need for a service related
> Rights Profile.
So, seems there is no security relative properties needed for such a service.
>
> HTH,
> Gary..
>>
>> For starting the daemon, I'm guessing that we'll have to create
>> something similar to
>> usr/src/cmd/svc/profile/platform_SUNW,SPARC-Enterprise.xml
>> for these x86 machines since we want the service to be enabled by
>> default on the platforms that support it. Does anyone have any
>> recommendation about who to talk to about how to get this done?
>>
>> Thanks,
>>
>> Mike
>>
>> On Tue, 2009-10-13 at 13:29 -0700, Gary Winiger wrote:
>>>> The acpihpd is started and stopped using the standard Solaris
>>>> service management facility. The acpihpd is an smf service, and
>>>> will only be enabled on the platforms which supports
>>>> IOH/CPU/memory hot plug.
>>>
>>> How is the SMF usage policy met?
>>> http://opensolaris.org/os/community/arc/policies/SMF-policy
>>> Specifically the authorizations, what Rights Profile the
>>> authorizations will be contained in, method context, ...
>>>
>>> How will this be enabled? Is it enabled from platform.xml?
>>>
>>> Gary..
Liu Jiang (Gerry)
OpenSolaris, OTC, SSG, Intel
