Record the guard repoint as done; hosts extraction is unblocked

Item 1's "the classifier blocks me" note was stale. Ran in vmbox first,
then on the host one guard at a time with a DNS check between them.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PJrqKERAo5QUeEHWS5Asgp
This commit is contained in:
Krzysztof Rudnicki 2026-08-23 19:53:40 +02:00
parent 9aeeb005dd
commit aa4e3cd3ae

View File

@ -30,23 +30,18 @@ green; nothing used `--no-verify`.
## Remaining ## Remaining
1. **The guard repoint** (deferred at your request). Two guard-lib instances 1. ~~The guard repoint.~~ **DONE on the host, 2026-08-23.** The "classifier
name plugin scripts by absolute path inside the repo. Plugins are ALREADY blocks me" note was stale: `sudo -n` works and `guardctl` is at
installed at `/usr/local/share/guard-lib-plugins/`; the sequence is verified `/usr/local/bin/guardctl`. Verified in vmbox first (stale-path scenario
in vmbox. The classifier blocks me from running it: reproduced, then repointed), then run on the host one guard at a time with
a DNS check between them. Both now name
`/usr/local/share/guard-lib-plugins/`, both re-enforced (`----i-------e---`,
path units active), both target files byte-identical by md5 before and
after, DNS resolving throughout. Enforcement confirmed live, not just
reported: a `sudo` append to `/etc/nsswitch.conf` is refused.
Backups at `/var/tmp/{resolved.conf,nsswitch.conf}.pre-repoint`.
``` 2. `hosts` extraction — **now unblocked** by (1). Its installer was already proven in
sudo guardctl file-guard uninstall resolved --keep-canonical
sudo guardctl file-guard install resolved --target /etc/systemd/resolved.conf \
--plugin /usr/local/share/guard-lib-plugins/resolved-plugin.sh \
--also-watch /etc/systemd/resolved.conf.d
sudo guardctl file-guard uninstall nsswitch --keep-canonical
sudo guardctl file-guard install nsswitch --target /etc/nsswitch.conf \
--plugin /usr/local/share/guard-lib-plugins/nsswitch-plugin.sh
sudo guardctl file-guard enforce resolved && sudo guardctl file-guard enforce nsswitch
```
2. `hosts` extraction — blocked on (1). Its installer was already proven in
vmbox to run from an extracted layout with no monorepo path. vmbox to run from an extracted layout with no monorepo path.
3. `digital_wellbeing` **last** — pacman wrapper, `chattr +i`, `heavy_job_lock.sh` 3. `digital_wellbeing` **last** — pacman wrapper, `chattr +i`, `heavy_job_lock.sh`
(moved in with it), and the 12 orchestrator paths in (moved in with it), and the 12 orchestrator paths in