Skip to content

System Artifacts

Installing ololo-relay via apt or dnf creates the following filesystem objects:

  • /usr/bin/ololo-relay — server relay node binary (root:root, 0755).
  • /lib/systemd/system/ololo-relay.service — systemd unit (Type=simple, runs as user ololo-relay, ExecReload=/bin/kill -HUP $MAINPID for zero-downtime certificate reload, TimeoutStopSec=35s for connection draining; 0644).
  • /etc/ololo-relay/node.yaml — node bootstrap config marked noreplace so package upgrades never overwrite local edits (root:root, 0644).
  • /etc/ololo-relay/initial-policy.yaml.example — starter policy template for cold-start master or standalone local_policy setups (0644).
  • /var/lib/ololo-relay/ — state directory holding policy.bbolt (master database), policy.snapshot (cached policy snapshot for offline restarts), and optional static/ web root (ololo-relay:ololo-relay, 0750).

Desktop Admin Artifacts (ololo-relay-admin)

On Linux, ololo-relay-admin installs:

  • /opt/ololo-relay-admin/ — self-contained ololo-relay-admin application bundle and .proto schemas;
  • /usr/bin/ololo-relay-admin — update-alternatives symlink for terminal launch;
  • /etc/apparmor.d/ololo-relay-admin — AppArmor user-namespace profile on Ubuntu 24.04+;
  • /usr/share/applications/ololo-relay-admin.desktop and application icon under /usr/share/icons/hicolor/512x512/apps/ololo-relay-admin.png.

System User & Linux Capabilities

The package creates an unprivileged system account ololo-relay (useradd --system, shell /usr/sbin/nologin, home /var/lib/ololo-relay/) and grants minimal file capabilities via setcap:

  • cap_net_admin — TUN device creation and policy routing management;
  • cap_net_bind_service — binding to privileged ports (443/tcp);
  • cap_net_raw — ICMP handling.

systemd Sandboxing

NoNewPrivileges=true
ProtectSystem=strict
ProtectHome=true
PrivateTmp=true
ReadWritePaths=/var/lib/ololo-relay
RestrictAddressFamilies=AF_INET AF_INET6 AF_UNIX AF_NETLINK

The entire filesystem outside /var/lib/ololo-relay/ is mounted read-only, /tmp is private, and /home is inaccessible.

What Post-Install Intentionally Does Not Do

  • Does not start or enable the service before /etc/ololo-relay/node.yaml is configured.
  • Does not modify firewall rules (ufw, firewalld, nftables stay under administrator control).
  • Does not provision TLS certificates (bring Let’s Encrypt, corporate PKI, or internal CA certs).