Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • apparmor apparmor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 146
    • Issues 146
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 28
    • Merge requests 28
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
    • Model experiments
  • 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
  • Issues
  • #195
Closed
Open
Issue created Sep 09, 2021 by John Johansen@jjohansenOwner

not all af families supported when built against old kernel headers

If the parser is built against old kernel headers then it will only support address families that are present in those headers, making it fail on newer policy that contains rules with those af names.

We need to update the parser to do what it is doing for capability names.

  1. Have a static list in the parser that can be updated.
  2. Generate a list at build time and compare to the static list so that the build can fail/warn when the internal list is missing an af
  3. All user to add unknown afs via config, as work around for new afs that are unknown
  4. Export from kernel set of af's
  5. Have the parser check the set of af's exported by kernel, so that it can properly map policy to kernel, sizing tables dropping rules, or mapping as necessary.

Unlike capabilities backmapping of afs is probably not necessary but should be investigated.

Assignee
Assign to
Time tracking