Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
  • This project
    • Loading...
  • Sign in / Register
L
lxc
  • Project
    • Overview
    • Details
    • Activity
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 0
    • Issues 0
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Chen Yisong
  • lxc
  • Repository

Switch branch/tag
  • lxc
  • config
  • selinux
  • lxc.te
Find file
BlameHistoryPermalink
  • Maximilian Blenk's avatar
    container.conf: Add option to set keyring SELinux context · 4fef78bc
    Maximilian Blenk authored Jan 29, 2020
    lxc set's up a new session keyring for every container by default.
    If executed on an SELinux enabled system, by default, the keyring
    inherits the label of the creating process. If executed with the
    currently available SELinux policy, this means that the keyring
    is labeled with the lxc_t type. Applications inside the container,
    however, might expect that the keyring is labeled with a certain
    context (and will fail to access the keyring if it's not explicitly
    allowed in the global policy). This patch introduces the config
    option lxc.selinux.context.keyring which enables to specify the
    label of the newly created keyring. That is, the keyring can be
    labeled with the label expected by the started application.
    Signed-off-by: 's avatarMaximilian Blenk <Maximilian.Blenk@bmw.de>
    4fef78bc
lxc.te 2.8 KB
EditWeb IDE
×

Replace lxc.te

Attach a file by drag & drop or click to upload


Cancel
A new branch will be created in your fork and a new merge request will be started.