veeos-1x.git/src/validators/base64, branch currentVyOS command definitions, scripts, and utilities (mirror of https://github.com/vyos-contrib/veeos-1x.git)
https://git.amelek.net/vyos-contrib/veeos-1x.git/atom?h=current2025-03-20T21:00:10+00:00wireguard: T7246: verify Base64 encoded 32byte boundary on keys2025-03-20T21:00:10+00:00Christian Breunigchristian@breunig.cc2025-03-20T21:00:10+00:00urn:sha1:8021bdd62e4142caf4a5e82000c8ca3da99fcae4
Not 31 bytes or 33 bytes, but exactly 32. This matters, because 32 does not
divide evenly by .75, so there's a padding character and the penultimate
character does not include the whole base64 alphabet.
Extend the base64 validator with an optional argument to define the length
to match of the decrypted Base64 encoded string.
Source: https://lists.zx2c4.com/pipermail/wireguard/2020-December/006222.html
ssh: T3789: add custom validator for base64 encoded CLI data2021-08-31T10:20:05+00:00Christian Poessingerchristian@poessinger.com2021-08-31T10:20:05+00:00urn:sha1:00efce716912680354d47a2dca9769cd8c5c89ae
SSH keys used for remote login are supplied as base64 encoded data on the CLI.
The key is not validated, thus an invalid copy/pasted key will render the login
useless. This commit adds a custom and re-usable validator which check if the
data is properly base64 encoded.