Conversation

Notices

1. Embed this notice
   Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Saturday, 19-Aug-2023 22:45:21 JST Haelwenn /элвэн/ :triskell:

   • Affe Null
   @affe_null
   - Polkit: I don't think this software is trustworthy at all, I think it ought to be deprecated hard with the goal of removing it
   - Restrict API access based on groups: This one seems the best choice, with like a small privileged program that only gives restricted access (suid I guess, would make sense to ask mobile linux distros on this)
   - As the user, restrict RTC access based on groups: So permission changes… wouldn't that give too much access? Specially given that it's going to be with the normal user and not like a dedicated one right?
   - As the user, restrict RTC access with uaccess tags: Same issues as group-access I guess
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Sunday, 20-Aug-2023 05:09:07 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • Affe Null
     @affe_null To me running daemon as root or a slightly privileged user is roughly the same thing, except I guess if you need dbus or to be sure that stuff like cleanups are done.
   • Embed this notice
     Affe Null (affe_null@mt.abscue.de)'s status on Sunday, 20-Aug-2023 05:09:12 JST Affe Null

     in reply to

     @lanodan I agree with this, especially regarding Polkit! I'd like to point though that the second option doesn't require setuid. By "system-wide", I mean running the daemon as root or as a dedicated user with necessary permissions, so the daemon would expose its D-Bus API on the system bus and access would just be restricted to a certain group. The setuid thing is another option that's closer to "as the user" but avoids assigning permissions directly.