| ... | ... | @@ -2,10 +2,10 @@ This would apply for Qbert Configuration Settings and future tablet revisions |
|
|
|
|
|
|
|
| Uri Path | Read Permission | Write Permission | Table contents |
|
|
|
|
|---|---|---|---|
|
|
|
|
/handshake | normal | signature | All Values from Configuration soap call not marked as secure |
|
|
|
|
/settings | normal | normal | all values marked as 'public' in Configuration soap call, plus any values stored by an application. basically a free-for-all |
|
|
|
|
/handshake | signature | signature | All Values from Configuration soap call not marked as secure |
|
|
|
|
/settings | normal | signature | all values marked as 'public' in Configuration soap call, plus any values stored by an application. Shareable to 3rdParties, but curated by us |
|
|
|
|
/secure | signature | signature | only values marked as 'secure' in Config soap call, plus all values from the provision call
|
|
|
|
/session | normal | normal | Tablet Session data, free-for-all where data is cleared on session end.
|
|
|
|
/session | normal | normal | Tablet Session data, basically a free-for-all for sharing name/value pairs among apks where data is cleared on session end.
|
|
|
|
|
|
|
|
|
|
|
|
It's possible to apply per-setting permissions, if the exact names are designated as a content uri (eg content://settings/network-timeout ) but the hope is that by isolated content by table we can assert a relative degree of security at a less involved cost. |
