blob: ff04630cbe4b886cf8481f060b539669d6ba15c0 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
|
== Problem: Activity Permissions == #2009
Rainbow needs to grok activity permissions.
Situation:
We've got a preliminary example of a how required permissions might be
specified by a bundle.
Caveat: this attempt was designed while only thinking about code-carrying
bundles, so its reasoning may be invalid for data-only bundles and or
extended bundles.
Plan:
Start locking down containers, then accrete permissions and their semantics
on a couple of sample activities.
Followup:
F1. We need to think hard about how error handling is going to interact with
permissions. How on earth is a user going to find out that their activity
isn't working because of a permissions misconfiguration?
|
