From 36f8dee00316080e4f54f5df5a12a0fedd634d2c Mon Sep 17 00:00:00 2001 From: Hitoshi Mitake Date: Mon, 20 Apr 2020 01:18:54 +0900 Subject: [PATCH] Documentation: note on password strength --- Documentation/op-guide/authentication.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Documentation/op-guide/authentication.md b/Documentation/op-guide/authentication.md index f836f0f96bc..3a8a5311b23 100644 --- a/Documentation/op-guide/authentication.md +++ b/Documentation/op-guide/authentication.md @@ -174,3 +174,5 @@ As of version v3.2 if an etcd server is launched with the option `--client-cert- As of version v3.3 if an etcd server is launched with the option `--peer-cert-allowed-cn` or `--peer-cert-allowed-hostname` filtering of inter-peer connections is enabled. Nodes can only join the etcd cluster if their TLS certificate identity match the allowed one. See [etcd security page](https://github.com/etcd-io/etcd/blob/master/Documentation/op-guide/security.md) for more details. +## Notes on password strength +`etcdctl` command line interface and etcd API don't check a strength (length, coexistence of numbers and alphabets, etc) of the password during creating a new user or updating password of an existing user. An administrator needs to care about a requirement of password strength by themselves.