kuhyx/testsAndMisc
1
0
Fork 0
mirror of https://github.com/kuhyx/testsAndMisc.git synced 2026-11-12 08:51:01 +01:00
Code Issues Actions 6 Packages Projects Releases Wiki Activity
015eb48714
testsAndMisc/linux_configuration/scripts/periodic_background/digital_wellbeing/llm-notes/vulns-and-troubleshooting.md
Krzysztof kuhy Rudnicki 346eb1f00b Bring every markdown file under the cap 
Twelve prose violations to zero. Eight files split into per-topic
subdirectories with the original left as an index; both SKILL.md files
keep their frontmatter so discovery still works, with detail moved to
references/.

Deleted docs/cleanup-2026-05/ (7 files) and linux_configuration/docs/
VERIFICATION.md on the user's ruling: unreferenced records of finished
work whose rules are now enforced by the polling, shellcheck and shfmt
hooks. PACMAN_WRAPPER_SECURITY.md was split instead - unlike those, it
documents live guarantees.

Every split verified by a sorted diff against HEAD: zero content lines
lost, only the new headings and index links added.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011w2Pj4Ek3ZNMQVYcFHgXDY
2026-08-16 19:25:59 +02:00

1.4 KiB
Raw Blame History

Known vulnerabilities, troubleshooting and hard stops

KNOWN VULNERABILITIES

  1. Information Disclosure: Error messages tell user exactly how to bypass
  2. Unlock Script Discoverable: Path mentioned in error messages
  3. Timer Monitor Killable: User can stop the monitor then the timer
  4. Check Script Unprotected: /usr/local/bin/day-specific-shutdown-check.sh can be edited

TODO:

  • Remove helpful bypass instructions from error messages
  • Rename unlock script to obscure name
  • Protect check script with integrity verification

Troubleshooting

Timer not firing

systemctl status day-specific-shutdown.timer
systemctl list-timers | grep shutdown

Config not being enforced

# Check path watcher
systemctl status shutdown-schedule-guard.path

# Manually trigger enforcement
sudo /usr/local/sbin/enforce-shutdown-schedule.sh

Wrong time shown in i3blocks

# Verify config
cat /etc/shutdown-schedule.conf

# Check i3blocks config
cat ~/.config/i3blocks/config | grep shutdown

DO NOT

  1. ❌ Edit setup script constants to make schedule later (will be blocked)
  2. ❌ Delete canonical config (breaks restoration)
  3. ❌ Stop shutdown-timer-monitor.service (timer will be re-enabled anyway)
  4. ❌ Modify check script to skip shutdown (defeats purpose)
  5. ❌ Lower MORNING_END_HOUR (always blocked, shortens shutdown window)