I've noticed this because after updating to the latest version, kes will no longer start with the existing config.
The error message differs between the last two releases and the current state on master.
Releases 2023-10-27T22-05-35Z and 2023-10-24T20-26-51Z will fail with Error: listen tcp :443: bind: permission deniedafter printing config values that indicate that the address was parsed correctly.
master fails with Error: missing port in address.
How to reproduce:
curl -ssL https://raw.githubusercontent.com/minio/kes/master/kesconf/testdata/fs.yml > config.yml
kes identity new --key server.key --cert server.cert --ip 127.0.0.1 localhost
kes server --config ./config.yml
Adding the --addr flag solves this, whereas removing the address value from the config.yml file does not. Interestingly enough, according to the config values kes prints on startup, the address is evaluated. But when it's time to actually start the server and listen, it falls back to port 443.
Bug describtion
I've noticed this because after updating to the latest version, kes will no longer start with the existing config.
The error message differs between the last two releases and the current state on master.
Error: listen tcp :443: bind: permission denied
after printing config values that indicate that the address was parsed correctly.Error: missing port in address
.How to reproduce:
Adding the
--addr
flag solves this, whereas removing theaddress
value from the config.yml file does not. Interestingly enough, according to the config values kes prints on startup, the address is evaluated. But when it's time to actually start the server and listen, it falls back to port 443.Here's the config I'm downloading above:
Expected behavior
The
address
attribute in the config should be evaluated correctly.Additional context
What version of Go are you using (
go version
)? 1.21.4What operating system and processor architecture are you using (
go env
)?Anything else that is important? Nope. It's trivial to reproduce.