v0.1.4

--enroll checks the certificate you have

Up to 0.1.3, svxconnect --enroll with a certificate that looks valid said "nothing to do" and asked nobody. Now it logs in and asks the reflector:

• accepted — it says so;
• refused (revoked or removed on the reflector, or the clocks disagree) — it requests a new certificate with the same key and waits for the sysop, never offering the refused one again;
• no answer — nothing changes, and it says it could not check.

It takes the shared run lock before logging in, and leaves the check to another SVXConnect that is connected. A replacement for a refused certificate is no longer held to the refused one's expiry date, here and in the running client.

Also in 0.1.3 (no separate GitHub release was published for 0.1.2 or 0.1.3)

• a microphone or speaker that starts but never runs is detected and reopened, instead of transmitting silence until a restart;
• the client certificate renews itself when the reflector pushes the new one, and the banner warns before it expires;
• disconnect, reconnect and PTT while connecting never block, and TCP connect and the TLS handshake have timeouts;
• the reason a connection dropped is kept, and a silent control channel or UDP audio path is noticed;
• a thread-safe log sink, a private control FIFO, no fsync every second, no GCM nonce reuse; beeps that play when made; an app that never started no longer reads stdin.

sudo pacman -U https://github.com/Guru-RF/SVXConnect-CLI/releases/download/v0.1.4/svxconnect-0.1.4-1-x86_64.pkg.tar.zst