Enable reading of keyring

[Furisto]

Description

Enable reading and writing to the keyring in the workspace.

Summary generated by Copilot

🤖 Generated by Copilot at f8304e2

Update seccomp profile for ws-daemon to support encrypted overlayfs. Remove unnecessary tracing of keyctl.

Related Issue(s)

Fixes ENG-743

How to test

• Open workspace in preview environment
• Install keyutils sudo apt update && sudo apt install keyutils
• keyctl link @us @s
• keyctl add user test payload @us
• keyctl request user test (should return keyid e.g. 90174234)
• keyctl read 90174234
• keyctl describe @us

Documentation

Preview status

Gitpod was successfully deployed to your preview environment.

• 🏷️ Name - fo-allow-keyctl
• 🔗 URL - fo-allow-keyctl.preview.gitpod-dev.com/workspaces.
• 📚 Documentation - See our internal documentation for information on how to interact with your preview environment.
• 📦 Version - fo-allow-keyctl-gha.15992

Build Options

Build

• /werft with-werft
  Run the build with werft instead of GHA
• leeway-no-cache
• /werft no-test
  Run Leeway with --dont-test

Publish

• /werft publish-to-npm
• /werft publish-to-jb-marketplace

Installer

• analytics=segment
• with-dedicated-emulation
• workspace-feature-flags
  Add desired feature flags to the end of the line above, space separated

Preview Environment / Integration Tests

• /werft with-local-preview
  If enabled this will build install/preview
• /werft with-preview
• /werft with-large-vm
• /werft with-gce-vm
  If enabled this will create the environment on GCE infra
• with-integration-tests=all
  Valid options are all, workspace, webapp, ide, jetbrains, vscode, ssh. If enabled, with-preview and with-large-vm will be enabled.
• with-monitoring

/hold