The Platform Security Model imposes certain read/write restrictions on applications accessing data from the Comms Database. Each table, column and record is guarded by the default capabilities for the whole database, though a range of capabilities can be used to guard the data. In addition, each element can have extra levels of access control.
The capabilities required to read or write an element of data in the Comms Database can be set at phone build time, by licensees, and can be changed at run time by a well trusted process.
All the tables, columns and record has access control settings with a combination of one or more settings:
Normal data in the Comms Database available for read/write purposes, available to all applications.
The data that does not generally need to be visible to the applications.
The applications generally do not modify this type of data but can set and read them. This type is supported for compatibility of CommDb.
This type of data is not readable by general applications: for example data such as a private pin number or similar.
This type of data can be read by any applications but only privileged applications can set, modify or delete the data.
The choice of the capabilities is left to the licensee to decide, however Symbian sets a range of capabilities that can be used to guard the access to the data in the database . The following table explains the various capability requirements for accessing the Comms Database:
|