An Organisation with Two Machines
An organisation gives each of your machines a certificate for its name and groups. A service admits a group; a client names the machine it wants. Every session between them is end to end encrypted, and the relay can forge none of it.
Goal
Two machines of your account, home-server and work-laptop, in one organisation; home-server runs a command on work-laptop that admits only the group home.
Prerequisites
- Two machines with the
nfltrCLI, each enrolled in your account withnfltr config login. Herehome-server(it keeps the organisation and stays on) andwork-laptop.
1. Make the organisation
On home-server, make the organisation with one group, home. It asks for a new passphrase for the organisation's root, then twice more as the root signs; the recovery key goes to a file that you then move offline:
$ nfltr org init --groups home --recovery-out recovery.key
New passphrase of the organisation root (~/.config/nfltr/org/root-org.key, at least 12 characters):
The passphrase again:
Passphrase of the organisation root, to make the organisation's root and its issuer (30 days):
Passphrase of the organisation root, to make the organisation's root and its issuer (30 days):
organisation o-dg4lusupegx2eytlh7m6xcccmi
root sha256:19b8ba4a8f21afa2626b3fd9eb884262dfda28701a2da2488867c970d0e34960 (file)
recovery sha256:b343a8935d14b3b1e34b588cb9aa06cb714fda51ddf5c11fc5ead82e601eaee4
issuer groups home, until 2026-12-11T17:15:54Z
The recovery key is in recovery.key: move it offline now. It alone rotates the root (nfltr org rotate).
enrolled as home-server (groups home) until 2026-11-20T17:15:56Z
home-server joins in the group home. Note the two fingerprints, root and recovery: every machine that joins checks them. Below they are $ROOT and $RECOVERY.
2. Keep the issuer running
The issuer on home-server answers enrolments, renews certificates and signs the revocation list every hour. Leave it running in a terminal of its own:
$ nfltr org serve
level=INFO msg="org issuer: serving enrolments, renewals, the CRL and the root through the relay"
nfltr org status says whether the issuer is served (it exits 1 when it is not, for a monitor) and prints the two fingerprints again:
$ nfltr org status
organisation o-dg4lusupegx2eytlh7m6xcccmi
root sha256:19b8ba4a8f21afa2626b3fd9eb884262dfda28701a2da2488867c970d0e34960
recovery sha256:b343a8935d14b3b1e34b588cb9aa06cb714fda51ddf5c11fc5ead82e601eaee4
…
served: yes (nfltr node or nfltr org serve on this machine)
3. Join the second machine
On home-server, make a single-use token for work-laptop in the group home:
$ nfltr org token --name work-laptop --group home > work-laptop.token
Carry work-laptop.token to work-laptop yourself (scp, a USB stick); it enrols that one name, once, within an hour. On work-laptop:
$ nfltr org join --root "$ROOT" --recovery "$RECOVERY" --token-file work-laptop.token
enrolled as work-laptop (groups home) until 2026-11-20T17:16:33Z
4. A session by name
On work-laptop, serve one command that admits only machines of the group home:
$ nfltr cat serve hello --exec --allow-group home -- echo "hello from work-laptop"
On home-server, name the machine and its service:
$ nfltr cat pipe work-laptop.work-laptop/hello
hello from work-laptop
The session is TLS between the two machines' certificates: home-server checks that it reached work-laptop, and work-laptop checks that the client is in home. A machine outside the group is refused, and so is a revoked one (nfltr org revoke on home-server).
5. Clean up
Press Ctrl+C in the nfltr cat serve terminal on work-laptop. Keep nfltr org serve running on home-server: once nothing serves the issuer for an hour, every organisation session is refused until it runs again.
# Ctrl+C in the nfltr cat serve terminal
Next
- Organisations: groups, revocation, moving the issuer and rotating the root.
- Send files and messages:
cat cp,cat pipeand--execbetween machines of an organisation. - SSH to a machine behind NAT: ssh with the organisation's host certificates.