Skip to content
GitLab Next
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • apparmor apparmor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 116
    • Issues 116
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 26
    • Merge requests 26
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • AppArmorAppArmor
  • apparmorapparmor
  • Merge requests
  • !387

[2.12+2.13] make abstractions/postfix-common compatible with latest postfix profiles

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Christian Boltz requested to merge cboltz/apparmor:cboltz-postfix-name into apparmor-2.13 Jun 13, 2019
  • Overview 0
  • Commits 1
  • Pipelines 0
  • Changes 1

Even if we don't backport the latest postfix profiles (in extras) to 2.12 and 2.13, making the abstraction compatible with them (by adding peer=postfix-master rules in addition to the path-based ones) makes things much easier for people who want to use the latest profiles.

Note: master has only peer=postfix-master and already dropped the path-based rules.

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: cboltz-postfix-name