Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • G gnome-keyring
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 94
    • Issues 94
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 13
    • Merge requests 13
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GNOMEGNOME
  • gnome-keyring
  • Merge requests
  • !34

Update libcap-ng capability handling v2

  • Review changes

  • Download
  • Email patches
  • Plain diff
Closed Steven Grubb requested to merge sgrubb/gnome-keyring:libcap-ng-update into master Nov 20, 2020
  • Overview 3
  • Commits 2
  • Pipelines 2
  • Changes 1

There is a change in libcap-ng-0.8.1 that causes gnome-keyring to not work correctly. The capng_apply function now returns an error if it cannot change the bounding set. Previously this was ignored. Which means now gnome-keyring exits when it shouldn't.

The new patch adds troubleshooting info to the error messages. And it checks to see if we have CAP_SETPCAP. If we do not, then we cannot change the bounding set and just set capabilities. On the setuid side, it now drops the bounding set and clears any supplemental groups that may be left over as an accident.

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: libcap-ng-update