pub fn validate_service_name(name: &str) -> Result<()>Expand description
Per-service credential directory layout:
credentials/
ca-key # CA private key (policy service only)
ca-pubkey # CA verifying key (public, all services)
ca-mldsa-pubkey # CA derived ML-DSA-65 verifying key (public, all services)
{service}/
signing-key # service's own Ed25519 private key
signing-key.pub # service's Ed25519 verifying key (public sidecar, 0644)
service-pubkey.hybrid # hybrid bootstrap entry (public sidecar, 0644)
service-jwt # CA-signed JWT certificate
bootstrap-pubkeys # JSON: { "policy": "base64...", "discovery": "base64..." }Load or generate an independent Ed25519 signing key for a specific service.
Each service gets its own randomly-generated keypair stored in
credentials/{service_name}/signing-key. This is NOT derived from the root
key — it’s an independent key that the CA (PolicyService) certifies via a
service JWT.
§Arguments
credentials_dir— Base credentials directory (e.g.,~/.config/hyprstream/credentials)service_name— Service name (e.g., “model”, “discovery”)
Validate a service name for use in filesystem paths.
Rejects names containing path separators, .., or characters
outside [a-z0-9-]. Prevents directory traversal when service
names are used in path construction.