1 mike  1.1.2.1 ########################################################################
 2               ##                                                                    ##
 3               ##               CIM Server Policy Configuration File                 ##
 4               ##                                                                    ##
 5               ########################################################################
 6                
 7               ########################################################################
 8               #                                                                      #
 9               # This file is only applicable to Pegasus releases that were built     #
10               # with privilege separation support. This file contains policy rules   #
11               # that restrict the set of out-of-process provider modules that may be #
12               # loaded by the server. The general form of an rule is:                #
13               #                                                                      #
14               #     <modulename>:<username>                                          #
15               #                                                                      #
16               # The modulename field is the name of the provider module used when    #
17               # registering the provider.                                            #
18               #                                                                      #
19               # The username field names a system user that the provider module is   #
20               # permitted to run as.                                                 #
21               #                                                                      #
22 mike  1.1.2.1 # The server permits a module to run as a given user if it finds ANY   #
23               # matching rule.                                                       #
24               #                                                                      #
25               # Either the modulename or the username field may contain an asterisk, #
26               # indicating that there is no restriction on that field.               #
27               #                                                                      #
28               # The most permissive policy configuration file would contain the      #
29               # following rule:                                                      #
30               #                                                                      #
31               #     *:*                                                              #
32               #                                                                      #
33               # This rule permits ANY provider module to run as ANY user.            #
34               #                                                                      #
35               # For obvious reasons, this file should only be writable by the        #
36               # administrator.                                                       #
37               #                                                                      #
38               ########################################################################
39               *:*