​

docs/tools/HOWTO-SETUP-DSOM-CONTROL-NODE.md

Standard: DSOM For My AI Protocol v6.1 | OS Hardening Tools: setup-dsom-control-node.sh Platforms: Linux / AlmaLinux 10 (WSL2 / Bare Metal)

​

1. Purpose

• Provision the standard dsom-admin service user (UID 2001).
• Install the DSOM toolstack: ansible, git, rsync, and python3-pip.
• Configure wsl.conf for systemd support and optimized disk mounting metadata.
• Generate a project-specific ED25519 SSH keypair.
• Set up the global ~/.ansible.cfg for high-concurrency pipe-lining.

• tools/setup-dsom-control-node.sh

​

2. Prerequisites

​

3. Usage

​

3.1 Targeted WSL Deployment

# Run as root inside the WSL instance

bash tools/setup-dsom-control-node.sh

​

4. Configuration Changes

​

4.1 Identity Management

• Creates group dsom-admin (GID 2001).
• Creates user dsom-admin (UID 2001).
• Adds user to the wheel group.
• Configures passwordless sudo via /etc/sudoers.d/dsom-admin.

​

4.2 WSL Interoperability (/etc/wsl.conf)

• Sets default=dsom-admin.
• Enables systemd=true.
• Disables appendWindowsPath=false (to prevent PATH pollution).
• Mounts /mnt/c with metadata options enabled (improves permission handling).

​

4.3 SSH Hardening

• Generates ~/.ssh/id_ed25519 for the dsom-admin user.
• Sets strict permission 700/600 on the .ssh directory.

​

5. Reading the Output & Status Codes

​

6. Security Advisory

[!WARNING]
This script disables appendWindowsPath in WSL. This means Windows executables (like code.exe or git.exe from T1) will no longer be in your Linux PATH. This is intentional to ensure your T2 Ansible operations are purely deterministic and isolated.

​

7. Related Documents