Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • P polkit
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 121
    • Issues 121
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 19
    • Merge requests 19
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • polkit
  • polkit
  • Merge requests
  • !102

Merged
Created Jan 04, 2022 by Dan Nicholson@dbnContributor

backend: Check for subject's primary group when expanding admin group

  • Overview 2
  • Commits 1
  • Pipelines 4
  • Changes 1

The group database entries as returned by getgrgid do not contain users who are members of the group as their primary group. In order to find all members of a group, the primary group of all users must be checked.

Since it could be expensive to read through all passwd entries on large multiuser systems, a compromise is to just check if the group is the subject user's primary group. This may not provide all possible admin identities to the authentication agent, but it should ensure that any user in an admin group can authenticate as themselves.

Fixes: #131 (closed)

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: primary-group-alt