Summary: | Allow trusted applications to provide details | ||
---|---|---|---|
Product: | PolicyKit | Reporter: | David Zeuthen (not reading bugmail) <zeuthen> |
Component: | daemon | Assignee: | David Zeuthen (not reading bugmail) <zeuthen> |
Status: | RESOLVED FIXED | QA Contact: | David Zeuthen (not reading bugmail) <zeuthen> |
Severity: | normal | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
David Zeuthen (not reading bugmail)
2009-04-06 14:01:02 UTC
Thinking more about it, it is probably more elegant to do it this way - the authentication agent provides a preferred locale when registering with the polkit daemon - CheckAuthorization() takes a hash table of key/value pairs; e.g. "device-file" -> "/dev/sdb1" "mount-point" -> "/media/EOS_DIGITAL" "device-label" -> "EOS_DIGITAL" that depends on the action. If the caller of CheckAuthorization() is not trusted (e.g. not uid 0) we just error out with FAILED. - the provider of the action supply a .so file (e.g. a GIOModule) along with the .policy that provides one or more extension points to handle the translation / formatting. If the set of key/value pairs are empty (e.g. caller of CheckAuthorzation is not trusted) we fall back to the message in the .policy file. Otherwise we call into the code in the .so file to get the translated messages (with LANG set to whatever we need) This was implemented some time ago. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.