Repository navigation
pvewarden 0.1.6
From a code review; no new features.
- Upgrading needs 0.1.3 or newer. The code that migrated installs from 0.1.0 to 0.1.2 is gone
(shared guest SSH key, unrecorded ownership of the pool, role and user, the old enroll.conf, the
pip-installed server, guest clients withoutservices). To upgrade an older install: uninstall
and install again. - Fix: the install refused an agent name with spaces or dots only after the container existed (the
config could not hold it). It is now checked when it is asked, likepvewarden-setup tokendoes. - Fix: the install left
umask 077in effect after writing the server config, so the host's files
written after it (enroll.conf, /opt/pvewarden) were readable by root only. pvewarden-setup renew-certturns HTTPS on with the newpvewarden config enable-tlsin the
container, which validates the config before writing it, instead of sed. The certificate is now
in place before the config names it.- The upgrade's question about enrolling the guests again says what it does today: it updates the
guest client (each guest gets a fresh key; permissions and automatic updates stay). - Docs are tool-neutral: docs/wireguard.md became docs/vpn.md, a guide for any VPN with WireGuard
as one example; docs/clients.md describes proxies that add credentials in general. The service
no longer orders itself afterwg-quick@wg0: it retries every 10 s until its address exists,
whatever the VPN. - Smaller code: shared helpers in pvewarden-setup (installing the server code, restarting the
service, the MCP address, the install check) and in the server (snapshot confirmations, the
update check, HTTP responses).