oracle / oracle/ktls-utils

Have systemd populate keyrings at boot from UEFI-stored material

Open
#58 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
C
Stars
50
Forks
36
Avg merge
3d 22h
Merged PRs (30d)
2

Description

Systemd has the capability of extracting blobs from UEFI and stuffing them onto a keyring: systemd. TLS-enabled storage tools can then direct tlshd to a particular key and/or keyring to obtain authentication material instead of tlshd reading it from a file.

Related to #30

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Read the systemd BOOT documentation linked in the issue and review related issue #30 to understand the expected UEFI-to-keyring flow. Then identify the tlshd integration points for selecting a key or keyring; done should mean TLS-enabled storage tools can use authentication material populated from UEFI at boot.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, linux
Domain
authentication, operating-systems, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.