clavitor-cli init
init connects clavitor-cli to your vault with the enrollment blob and key from a client you created in the vault page (see Agent setup). It also checks, for IPv4 and IPv6, that the vault answers this machine, so an agent isn't refused the day your system uses the other one.
Usage
clavitor-cli init '<blob>'
Put the blob in quotes; spaces and line breaks a paste adds are dropped. The key is never on the command line: init asks for it at the Enrollment key: prompt, with the echo off. A script can pipe both, the blob first:
printf '%s\n%s\n' "$CLAVITOR_BLOB" "$CLAVITOR_KEY" | clavitor-cli init
clavitor-proxy init works the same way.
What it does
init writes the connection to ~/.config/clavitor/config, then makes one read over IPv4 and one over IPv6, for each of the two your machine has a route for. The read is a search for a title no entry carries, so it reads nothing and costs no quota. You see:
$ clavitor-cli init '<blob>' … → IPv4: reached the vault → IPv6: reached the vault
A client you created without an IP list is tied to the first IPv4 address and the first IPv6 address the vault sees from it. Because init reaches the vault over both, both are tied from the start. Before 1.7.8, a machine with both often had only one tied, and the first command over the other was refused.
When a line says something else
→ IPv6: not on this client's IP list: the client has an IP list you gave it when you created it, and it doesn't hold this kind of address. Your list stands. Open the client in your vault's Clients, add the address, and save.→ IPv6: check failed: <error>: the check failed for another reason, and the error says which. Enrollment stands either way.- No line for a family: this machine has no route for it.