45c028a2fb
* Allow specifying multiple allowed SSH key lengths In the ssh secrets engine, only a single allowed key length was allowed for each algorithm type. However, many algorithms have multiple safe values (such as RSA and ECDSA); allowing a single role to have multiple values for a single algorithm is thus helpful. On creation or update, roles can now specify multiple types using a list or comma separated string of allowed values: allowed_user_key_lengths: map[string][]int{"rsa": []int{2048, 4096}} Signed-off-by: Alexander Scheel <alex.scheel@hashicorp.com> * Add changelog entry Signed-off-by: Alexander Scheel <alex.scheel@hashicorp.com> * Break out ssh upgrade logic into separate function Signed-off-by: Alexander Scheel <alex.scheel@hashicorp.com> * Update parseutil for optional lists of integers go get -u github.com/hashicorp/go-secure-stdlib/parseutil go mod tidy Signed-off-by: Alexander Scheel <alex.scheel@hashicorp.com> * Simplify parse logic using new parseutil The newly introduced parseutil.ParseIntSlice handles the more complicated optional int-like slice logic for us. Signed-off-by: Alexander Scheel <alex.scheel@hashicorp.com> |
||
---|---|---|
.. | ||
cmd/ssh | ||
backend.go | ||
backend_test.go | ||
communicator.go | ||
linux_install_script.go | ||
path_config_ca.go | ||
path_config_ca_test.go | ||
path_config_zeroaddress.go | ||
path_creds_create.go | ||
path_fetch.go | ||
path_keys.go | ||
path_lookup.go | ||
path_roles.go | ||
path_sign.go | ||
path_verify.go | ||
secret_dynamic_key.go | ||
secret_otp.go | ||
util.go |