The cosmos generator linked a consumer to its provider only through an '<role>' in group_names reference or an explicit provides: name. A hard dependency has neither -- pinning the provider on unconditionally is exactly what removes the Jinja reference the generator was reading -- so web-svc-asset's bond to web-svc-file vanished from the diagram the moment it became binding. Match a service key against the provider's own primary key from the registry, in both directions. Services the role turns off drew a solid 1:1 edge, claiming a mandatory relationship for something that carries nothing at deploy time. They now render as a red 0..0 edge; edge merging gained a real precedence so a provider consumed through two keys stays live when only one is off. Named colour, not hex: a '#' opens an entity code in the mermaid lexer and turns the whole diagram into a parse error on GitHub. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2.8 KiB
sshd
Description
This Ansible role configures the OpenSSH daemon (sshd) by deploying a templated sshd_config file. It applies secure, best-practice settings to harden remote access and reduce the risk of misconfiguration or lockout. Settings include disabling root login, enforcing public-key authentication, and setting appropriate logging levels.
Overview
- Renders
sshd_config.j2into/etc/ssh/sshd_configwith customizable options - Sets file ownership (
root:root) and permissions (0644) - Automatically reloads and restarts the SSH service via a systemd handler
- Uses a
run_once_sys_svc_sshdfact to ensure idempotent execution
Key variable: SYS_SVC_SSHD_PASSWORD_AUTHENTICATION (default: false) enables password authentication when explicitly required by controlled environments such as local E2E test targets.
Cosmos
The diagram places sshd in the Infinito.Nexus cosmos: the components it deploys (capabilities), the central services it consumes (dependencies), and its outward reach (federation and bridged external networks).
flowchart LR
subgraph role [sys-svc-sshd 💻]
svc_svc_sshd["svc-sshd"]
end
Solid 1:1 edges are fixed relationships; dashed 0..1 edges are conditional (enabled only in matching deployments); red 0..0 edges are turned off in this role. Node markers show the role's deploy modes (💻 host, 🐳 compose, 🐝 swarm); ❌ marks a service that is explicitly turned off, and ⚙️ an Ansible role dependency declared in meta/main.yml.
Features
- Templated Configuration: Delivers a Jinja2-based
sshd_configwith variables for debug logging, PAM support, and password-auth overrides. - Security Defaults: Disables password authentication and root login; enforces public-key authentication; conditionally sets
LogLeveltoDEBUG3whenMODE_DEBUGis true. - Systemd Integration: Handles daemon reload and service restart seamlessly on configuration changes.
- Idempotency: Ensures tasks run only once per play by setting the
run_once_sys_svc_sshdfact.
Further Resources
- sshd_config manual
- Ansible Template Module
- Ansible handler best practices
- OpenSSH security recommendations
Credits
Implemented by Kevin Veen-Birkenbach. Part of the Infinito.Nexus Project and maintained by Kevin Veen-Birkenbach. Licensed under the Infinito.Nexus Community License (Non-Commercial).