|
sl@0
|
1 |
;
|
|
sl@0
|
2 |
; This security policy file is used by the DBMS security tests.
|
|
sl@0
|
3 |
; There are 5 different DBMS tests:
|
|
sl@0
|
4 |
; (1) - A test application with capabilities, which satisfy database's schema security policy.
|
|
sl@0
|
5 |
; (2) - A test application with capabilities, which satisfy database's write security policy.
|
|
sl@0
|
6 |
; (3) - A test application with capabilities, which satisfy read security policy of table "A".
|
|
sl@0
|
7 |
; (4) - A test application with capabilities, which satisfy write security policy of table "B", although they cannot satisfy (UID: WRITE) policy.
|
|
sl@0
|
8 |
; (5) - A test application without capabilities.
|
|
sl@0
|
9 |
;
|
|
sl@0
|
10 |
[database]
|
|
sl@0
|
11 |
read
|
|
sl@0
|
12 |
capability = None
|
|
sl@0
|
13 |
write
|
|
sl@0
|
14 |
capability = WriteUserData
|
|
sl@0
|
15 |
schema
|
|
sl@0
|
16 |
capability = NetworkServices
|
|
sl@0
|
17 |
|
|
sl@0
|
18 |
[table]
|
|
sl@0
|
19 |
name = A
|
|
sl@0
|
20 |
read
|
|
sl@0
|
21 |
capability = PowerMgmt
|
|
sl@0
|
22 |
|
|
sl@0
|
23 |
[table]
|
|
sl@0
|
24 |
name = B
|
|
sl@0
|
25 |
write
|
|
sl@0
|
26 |
capability = WriteDeviceData
|
|
sl@0
|
27 |
|
|
sl@0
|
28 |
;Table C
|
|
sl@0
|
29 |
; It has explicitly specified security policies, so the database R/W security policies
|
|
sl@0
|
30 |
; will be used when table C is accessed.
|