- should be done in eggdbus; e.g.
- D-Bus XML --(eggdbus-binding-tool)--> DocBook --(gtk-doc)--> HTML
- - document the GObject API
-
- - local files authority backend
- - split out AuthorizationStore into separate class
- - split out AuthenticationAgent and AuthenticationSession to separate classes
+ - properly document the GObject API
- maybe rename .policy to .action for policy XML files
- provide a polkit-validate-action-file-1 tool to check/validate
.policy/.action XML files
- - check / validate all incoming arguments
- - and other security/paranoia code
-
- write a couple of introductory sections detailing the system architecture
- a developer-audience; and
- a system administrator audience
- write a PolicyKit 0.9.x -> polkit 1.0 porting guide
- - use a GIO extension point to decide what authority backend to use
-
- expose a public ObtainAuthorization() method
- separate core API (e.g. CheckAuthorization()) from the administration API
(e.g. AddAuthorization()) both in the D-Bus interface and in the GObject
client libraries
+ - guard off administration API with I_KNOW_THIS_API_IS_SUBJECT_TO_CHANGE_ETC
+
+ - guard off backend API with I_KNOW_THIS_API_IS_SUBJECT_TO_CHANGE_ETC
+
- provide a way to tweak the defaults for actions (or maybe not)
- do we need negative authorizations? If so, implement code for it, otherwise
- make sure simple operations work when no system bus is present
- e.g. %post RPM scripts adding/removing authorizations to identities
+Backend TODO items
+------------------
+
+ - use a GIO extension point to decide what authority backend to use
+
+ - check / validate all incoming arguments
+ - and other security/paranoia stuff
+
+ - local files authority backend
+ - split out AuthorizationStore into separate class
+ - split out AuthenticationAgent and AuthenticationSession to separate classes
+
+
polkit-gnome TODO items
-----------------------