kuhyx/testsAndMisc
1
0
Fork 0
mirror of https://github.com/kuhyx/testsAndMisc.git synced 2026-11-10 18:07:06 +01:00
Code Issues Actions 6 Packages Projects Releases Wiki Activity
4f2b0ccdf7
testsAndMisc/linux_configuration/docs/security-hardening/01-current-state.md
Krzysztof kuhy Rudnicki 4f2b0ccdf7 Dissolve linux_configuration/scripts/ and single_use/ 
Two levels of pure taxonomy carrying no information, and a 2-directory
cap leaves no room for them. Categories now sit directly under
linux_configuration/: features, fixes, utils, misc, fresh-install,
installers, diagnostics, gaming, boot_recovery, periodic_background, lib,
meta, tests. A script's own lib/ and tests/ are exempt from the cap, so
those stay put.

Depth violations 248 -> 139; roughly 40 of the remainder are inside
digital_wellbeing and hosts, deferred until the guard-lib repoint.

The moves are the easy half. What breaks is every path that counted
levels, and three classes of it had to be found by resolving paths rather
than reading diffs:

  - 52 relative `source` lines for lib/common.sh and lib/android.sh. The
    correct prefix differs per file: 40 were ../../ and 12 were ../../../,
    so a blanket replace would have fixed one set and broken the other.
  - REPO_ROOT in 7 fixes/lib/tests harnesses and setup_syncyomi_guard.sh,
    each walking up four levels from a directory now two levels shallower.
    This caused a real regression -- the fixes suite went red with
    "log_warn: command not found" -- caught by running it and comparing
    against the pre-move baseline worktree.
  - conftest.py's sys.path entries, which took the pytest gate down with
    14 collection errors, and the `# shellcheck source=` directives, which
    took shellcheck down with SC1091.

16 symlinks in $HOME broke, including the entire i3blocks bar. All
repointed, and cpu_monitor/memory/disk/time/volume were run to confirm
they emit real output rather than merely resolving.

Verified: 1798 tests pass at 100% coverage, 8 of 9 lib/tests suites pass
(the ninth needs the coverage jail, identically at baseline), pre-commit
is clean, and the two untracked secret configs are still ignored after
their gitignore paths changed.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PJrqKERAo5QUeEHWS5Asgp
2026-08-23 18:53:30 +02:00

5.0 KiB
Raw Blame History

Part 1: Current State Analysis

1. /etc/hosts Protection System

Files involved:

Current Protection Layers:

  1. ✅ Immutable attribute (chattr +i)
  2. ✅ Canonical copy at /usr/local/share/locked-hosts
  3. ✅ Path watcher (hosts-guard.path) auto-restores on modification
  4. ✅ Read-only bind mount (hosts-bind-mount.service)
  5. ✅ Custom entries protection (blocks removal of blocked domains)
  6. ✅ Shell history suppression for unlock-hosts command

CRITICAL VULNERABILITY IDENTIFIED:

  • ❌ NO protection for /etc/nsswitch.conf - A user can simply edit nsswitch.conf and remove files from the hosts: line, completely bypassing ALL /etc/hosts protections without touching the hosts file itself!

Example bypass:

# Original: hosts: mymachines resolve [!UNAVAIL=return] files myhostname dns
# Tampered: hosts: mymachines resolve [!UNAVAIL=return] myhostname dns
# Result: /etc/hosts is completely ignored by the system

2. Midnight Shutdown System

Files involved:

Current Protection Layers:

  1. ✅ Immutable attribute on /etc/shutdown-schedule.conf
  2. ✅ Canonical copy at /usr/local/share/locked-shutdown-schedule.conf
  3. ✅ Path watcher restores config if tampered
  4. ✅ Schedule protection blocks making schedule more lenient
  5. ✅ Unlock script with psychological delay

VULNERABILITIES IDENTIFIED:

  • ❌ The unlock script explicitly tells users how to bypass: "sudo /usr/local/sbin/unlock-shutdown-schedule"
  • ❌ The schedule change logic is communicated in the error message
  • ❌ No protection against stopping/disabling the timer services
  • ❌ No protection against modifying the check script at /usr/local/bin/day-specific-shutdown-check.sh

3. Screen Locker (Python - External Repo)

File: /home/kuhy/testsAndMisc/python_pkg/screen_locker/screen_lock.py

Current Workout Types:

  1. Running - distance, time, pace validation
  2. Strength - exercises, sets, reps, weights, total calculation
  3. Table Tennis - duration, sets, points won/lost

VULNERABILITIES IDENTIFIED:

  • ❌ Running option too easy to fake - just enter plausible numbers
  • ❌ Table Tennis lacks real verification - no mathematical cross-check
  • ❌ Users can close the window via keyboard shortcuts (Alt+F4, etc.)
  • ❌ The unlock mechanism is too simple once you know the forms
  • ❌ Shutdown time adjustment is a REWARD for working out (can be exploited)

4. Pacman Wrapper

Files involved:

Current Protection:

  1. ✅ Policy file integrity verification (SHA256)
  2. ✅ Blocked keywords list
  3. ✅ Greylist with challenge
  4. ✅ VirtualBox hardcoded check (cannot bypass via policy files)
  5. ✅ Steam weekend-only restriction

VULNERABILITIES IDENTIFIED:

  • ❌ Google Chrome not blocked - google-chrome and google-chrome-stable missing from blocked list
  • ❌ No automatic LeechBlock installation when browsers are detected
  • ❌ User can download .deb/.tar.gz and install manually

5. Block Compulsive Opening

File: periodic_background/digital_wellbeing/block_compulsive_opening.sh (507 lines)

Current Behavior:

  • Records first open per hour in state file
  • Blocks subsequent launches within same hour
  • Shows notification when blocked

CRITICAL VULNERABILITY:

  • ❌ App stays running indefinitely - User can:
    1. Open app once per hour (allowed)
    2. Minimize/hide the window
    3. Keep it running forever in background
    4. Compulsive checking still happens, just via Alt+Tab instead of launcher

6. YouTube Music Wrapper

File: periodic_background/digital_wellbeing/youtube-music-wrapper.sh

Current Behavior:

  • Checks if focus apps (VSCode, games, etc.) are running
  • Blocks YouTube Music launch if focus app detected

REQUESTED ENHANCEMENT:

  • When Steam is open → Block ALL browsers, close any open browsers
  • When browsers open → Block Steam, close Steam if running
  • This creates mutual exclusion between gaming and browsing