[PR #6719] [MERGED] modif: keep /dev/tpmrm devices if keep-dev-tpm is used #6138

Closed
opened 2026-05-05 10:51:28 -06:00 by gitea-mirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/netblue30/firejail/pull/6719
Author: @kmk3
Created: 4/26/2025
Status: Merged
Merged: 4/29/2025
Merged by: @kmk3

Base: masterHead: modif-keep-tpmrm


📝 Commits (1)

  • 488fc83 modif: keep /dev/tpmrm devices if keep-dev-tpm is used

📊 Changes

3 files changed (+5 additions, -4 deletions)

View changed files

📝 src/firejail/fs_dev.c (+1 -0)
📝 src/man/firejail-profile.5.in (+2 -2)
📝 src/man/firejail.1.in (+2 -2)

📄 Description

Treat them like /dev/tpm[0-9]* devices.

It seems that /dev/tpm[0-9]* allows direct access to the TPM device
while /dev/tpmrm[0-9]* mediates access through a "resource manager"
inside of the kernel (for example, to facilitate concurrent access).
Alternatively, it looks like the resource management can be done in
userspace through tpm2-abrmd, the "TPM2 Access Broker & Resource
Management Daemon", which also supports older kernels (Linux 3.x vs
4.12) [1] [2] [3].

udev rules from tpm2-tss 4.1.3[4]:

# tpm devices can only be accessed by the tss user but the tss
# group members can access tpmrm devices
KERNEL=="tpm[0-9]*", TAG+="systemd", MODE="0660", OWNER="tss"
KERNEL=="tpmrm[0-9]*", TAG+="systemd", MODE="0660", GROUP="tss"

This is a follow-up to #6718.

Misc: This was noticed on #6700.

Relates to #6390.

[1] https://github.com/tpm2-software/tpm2-abrmd
[2] https://github.com/tpm2-software/tpm2-abrmd/issues/830
[3] https://github.com/tpm2-software/tpm2-tss-engine/issues/149
[4] https://github.com/tpm2-software/tpm2-tss/blob/4.1.3/dist/tpm-udev.rules


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/netblue30/firejail/pull/6719 **Author:** [@kmk3](https://github.com/kmk3) **Created:** 4/26/2025 **Status:** ✅ Merged **Merged:** 4/29/2025 **Merged by:** [@kmk3](https://github.com/kmk3) **Base:** `master` ← **Head:** `modif-keep-tpmrm` --- ### 📝 Commits (1) - [`488fc83`](https://github.com/netblue30/firejail/commit/488fc839bc59b81631cd40004f12f415a640381a) modif: keep /dev/tpmrm devices if keep-dev-tpm is used ### 📊 Changes **3 files changed** (+5 additions, -4 deletions) <details> <summary>View changed files</summary> 📝 `src/firejail/fs_dev.c` (+1 -0) 📝 `src/man/firejail-profile.5.in` (+2 -2) 📝 `src/man/firejail.1.in` (+2 -2) </details> ### 📄 Description Treat them like `/dev/tpm[0-9]*` devices. It seems that `/dev/tpm[0-9]*` allows direct access to the TPM device while `/dev/tpmrm[0-9]*` mediates access through a "resource manager" inside of the kernel (for example, to facilitate concurrent access). Alternatively, it looks like the resource management can be done in userspace through tpm2-abrmd, the "TPM2 Access Broker & Resource Management Daemon", which also supports older kernels (Linux 3.x vs 4.12) [1] [2] [3]. udev rules from tpm2-tss 4.1.3[4]: # tpm devices can only be accessed by the tss user but the tss # group members can access tpmrm devices KERNEL=="tpm[0-9]*", TAG+="systemd", MODE="0660", OWNER="tss" KERNEL=="tpmrm[0-9]*", TAG+="systemd", MODE="0660", GROUP="tss" This is a follow-up to #6718. Misc: This was noticed on #6700. Relates to #6390. [1] https://github.com/tpm2-software/tpm2-abrmd [2] https://github.com/tpm2-software/tpm2-abrmd/issues/830 [3] https://github.com/tpm2-software/tpm2-tss-engine/issues/149 [4] https://github.com/tpm2-software/tpm2-tss/blob/4.1.3/dist/tpm-udev.rules --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
gitea-mirror 2026-05-05 10:51:28 -06:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#6138
No description provided.