オープンソース・ソフトウェアの開発とダウンロード

Subversion リポジトリの参照

Diff of /trunk/1.7.x/ccs-patch/README.ccs

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1010 by kumaneko, Fri Feb 29 14:11:41 2008 UTC revision 1052 by kumaneko, Mon Mar 24 03:50:04 2008 UTC
# Line 1256  Fix 2008/02/29 Line 1256  Fix 2008/02/29
1256    
1257        You can silently terminate a process who requested execve()        You can silently terminate a process who requested execve()
1258        that is not permitted by policy.        that is not permitted by policy.
1259    
1260    Fix 2008/03/03
1261    
1262        @ Add "force_alt_exec" keyword.
1263    
1264          To be able to fully utilize "alt_exec" feature,
1265          I added "force_alt_exec" keyword so that
1266          all execute requests are replaced by the execute request of a program
1267          specified by alt_exec feature.
1268    
1269          If this keyword is specified for a domain, the domain no longer
1270          executes any programs regardless of the mode of file access control
1271          (i.e. the domain won't execute even if MAC_FOR_FILE=0 ).
1272          Instead, the domain executes the program specified by alt_exec feature
1273          and the program specified by alt_exec feature validates the execute
1274          request and executes it if it is appropriate to execute.
1275    
1276          If you can tolerate that there is no chance to return an error code
1277          to the caller to tell the execute request was rejected,
1278          this is more flexible approach than in-kernel execve() parameter
1279          checking because we can do argv[] and envp[] checking easily.
1280    
1281    Fix 2008/03/04
1282    
1283        @ Use string for access control mode.
1284    
1285          An integer expression for access control mode sometimes confuses
1286          administrators because profile number is also an integer expression.
1287          To avoid confusion between profile number and access control mode,
1288          I introduced a string expression for access control mode.
1289    
1290            Modes which take an integer between 0 and 3.
1291    
1292              0 -> disabled
1293              1 -> learning
1294              2 -> permissive
1295              3 -> enforcing
1296    
1297            Modes which take 0 or 1.
1298    
1299              0 -> disabled
1300              1 -> enabled
1301    
1302    Fix 2008/03/10
1303    
1304        @ Rename "force_alt_exec" keyword to "preferred_execute_handler".
1305    
1306          To be able to use different programs for validating execve() parameters,
1307          I moved the location to specify the program's pathname from profile
1308          to domain policy.
1309    
1310          The "preferred_execute_handler" keyword takes one pathname which is
1311          invoked whenever execve() request is issued. Thus, any "allow_execute"
1312          keywords in a domain with "preferred_execute_handler" are ignored.
1313          This keyword is designed for validating expected/desirable execve()
1314          requests in userspace, although there is no way to tell the caller
1315          that the execve() request was rejected.
1316    
1317        @ Rename "alt_exec" keyword to "default_execute_handler".
1318    
1319          The "default_execute_handler" keyword takes one pathname which is
1320          invoked only when execve() request was rejected. In other words,
1321          this program is invoked only when the following conditions are met.
1322    
1323            (1) None of "allow_execute" keywords in the domain didn't match.
1324            (2) The execve() request was rejected in enforcing mode.
1325            (3) "preferred_execute_handler" keyword is not used by the domain.
1326    
1327          This keyword is designed for handling unexpected/undesirable execve()
1328          requests, to redirect the process issuing such requests to somewhere.
1329    
1330    Fix 2008/03/18
1331    
1332        @ Fix wrong/redundant locks in pre-vfs functions.
1333    
1334          lock_kernel()/unlock_kernel() in pre_vfs_rename() were redundant for
1335          2.6 kernels.
1336    
1337          Locking order in pre_vfs_link() and pre_vfs_unlink() for 2.4 kernels
1338          after 2.4.33 were different from before 2.4.32 .

Legend:
Removed from v.1010  
changed lines
  Added in v.1052

Back to OSDN">Back to OSDN
ViewVC Help
Powered by ViewVC 1.1.26