Skip to content

Security & Package Signing

Built-In Security Controls

  • Standard TLS transport. Inter-node streams run over gRPC/HTTP2 inside standard TLS 1.2/1.3 — zero custom cryptography.
  • Unified port 443/tcp listener. Relay streams, ControlPlane RPCs, and regular HTTPS web serving share a single port and TLS stack, with background connection rotation (6m ± 60s). Unauthenticated HTTP requests receive an ordinary static site or reverse-proxy response rather than fingerprinting errors.
  • Hashed Bearer tokens. Every peer authenticates with a 256-bit random Bearer token; the master and policy files store only its SHA-256 digest. Tokens are verified on every RPC and can be revoked or rotated instantaneously.
  • Per-node anti-abuse rate limiting. More than 10 failed authentication attempts from an IP within 1 hour ban that source IP for 24 hours in local process memory on each node independently.
  • Pre-dial BitTorrent / P2P filtering. Enabled by default in cluster policy (block_bittorrent: true) to protect cloud exit nodes from P2P abuse notices without impacting normal TLS, QUIC, HTTP, SSH, or WebRTC traffic.
  • Least privilege & systemd isolation. Runs as unprivileged user ololo-relay (/usr/sbin/nologin) with scoped Linux capabilities (cap_net_admin, cap_net_bind_service, cap_net_raw) and ProtectSystem=strict, ProtectHome=true, NoNewPrivileges=true.

Repository GPG Key

All .deb / .rpm packages and repository metadata are signed with a single release key:

  • Fingerprint: 7996 8800 C963 EE63 2443 8ADA 2E81 F9E2 E462 1CF2
  • Key ID: 2E81F9E2E4621CF2
  • UID: ololo-relay repo <repo@ololo.tech>
  • Valid until: 2028-05-22

Download public key: repo.ololo.tech/pubkey.asc.

Verify fingerprint manually:

curl -fsSL https://repo.ololo.tech/pubkey.asc | gpg --show-keys

Artifact Verification

  • .deb packages — signed APT Release / InRelease metadata verified automatically by apt.
  • .rpm packages — signed RPM headers (rpm --addsign) plus signed repodata/repomd.xml.asc, both checked by dnf.
  • Windows builds — published alongside SHA256SUMS on repo.ololo.tech and GitHub Releases.

Vulnerability Disclosure

Report security issues in ololo-relay or any other ololo project responsibly to security@ololo.tech (include package version, distro/kernel version, reproduction steps, and expected vs. actual behavior).