fix(vpn): make the WireGuard peer key's prefix URL-safe
get_vpn_tunnels keyed a peer as wireguard-<iface>-<pubkey[:8]>. Base64 uses "/" and "+", and the key is used as a URL path segment; a "/" breaks the route even percent-encoded. The prefix now maps "+" to "-" and "/" to "_", as napalm-opnsense does (NAPALM/napalm-opnsense#32). Affected peers change their key once. Closes #43
This commit is contained in:
1 parent
eaa08ae7e3
commit
df4f4b0e4d
3 files changed
+33
-3
No files matched your search
@@ -52,6 +52,11 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
||||
`uninstall_package()` already does (#4). It used to search the output for words like
|
||||
"failed": an install whose postinst merely mentioned a failure read as failed, and a
|
||||
failure that used none of the words read as success.
|
||||
- `get_vpn_tunnels()` makes the public-key prefix in a WireGuard peer's key URL-safe
|
||||
(`+` becomes `-`, `/` becomes `_`), as napalm-opnsense does (#43). A key with `/`
|
||||
could not be used as a URL path segment, so such a tunnel could not be edited in
|
||||
netOrk. The key of a peer whose first eight key characters hold `+` or `/` changes
|
||||
once; `public_key` is reported unchanged.
|
||||
|
||||
## [0.15.1] - 2026-10-23
|
||||
|
||||
|
||||
Reference in new issue
Block a user