shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2025-01-10 05:18:17 +03:00
Code

update TODO

Browse Source
This commit is contained in:
Lennart Poettering 2023-11-22 10:59:57 +01:00
parent 641489e257
commit 604cfd1e4a
1 changed files with 0 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
TODO
View File

@ -931,10 +931,6 @@ Features:
file system paths to enable on start. file system paths to enable on start.
• make systemd-fstab-generator look for a system credential encoding root= or • make systemd-fstab-generator look for a system credential encoding root= or
usr= usr=
• systemd-homed: when initializing, look for a credential
systemd.homed.register or so with JSON user records to automatically
register if not registered yet. Use case: deploy a system, and add an
account one can directly log into.
• in gpt-auto-generator: check partition uuids against such uuids supplied via • in gpt-auto-generator: check partition uuids against such uuids supplied via
sd-stub credentials. That way, we can support parallel OS installations with sd-stub credentials. That way, we can support parallel OS installations with
pre-built kernels. pre-built kernels.
@ -2259,11 +2255,6 @@ Features:
- support new FS_IOC_ADD_ENCRYPTION_KEY ioctl for setting up fscrypt - support new FS_IOC_ADD_ENCRYPTION_KEY ioctl for setting up fscrypt
- maybe pre-create ~/.cache as subvol so that it can have separate quota - maybe pre-create ~/.cache as subvol so that it can have separate quota
easily? easily?
- add a switch to homectl (maybe called --first-boot) where it will check if
any non-system users exist, and if not prompts interactively for basic user
info, mimicking systemd-firstboot. Then, place this in a service that runs
after systemd-homed, but before gdm and friends, as a simple, barebones
fallback logic to get a regular user created on uninitialized systems.
- store PKCS#11 + FIDO2 token info in LUKS2 header, compatible with - store PKCS#11 + FIDO2 token info in LUKS2 header, compatible with
systemd-cryptsetup, so that it can unlock homed volumes systemd-cryptsetup, so that it can unlock homed volumes
- maybe make all *.home files owned by `systemd-home` user or so, so that we - maybe make all *.home files owned by `systemd-home` user or so, so that we