hardlinks to system libraries make system unbootable due to SELinux (?)
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.7k
- Forks
- 662
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 2
Description
After running rr as root and recording some stuff that used libraries like libselinux.so, I was unable to boot, apparently because loading some system libraries was being blocked by SELinux. This may have been because rr created hardlinks to system libraries and changed their SELinux contexts.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the report with rr running as root while recording activity involving libselinux.so, then inspect whether hardlinks are created and whether SELinux contexts change. Determine the smallest safe fix that prevents system-library context changes and verify that the system remains bootable after recording.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, linux
- Domain
- operating-systems, security
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100