summaryrefslogtreecommitdiff
path: root/kadmin/kadmin.1
diff options
context:
space:
mode:
authorCy Schubert <cy@FreeBSD.org>2022-03-28 17:02:13 +0000
committerCy Schubert <cy@FreeBSD.org>2022-03-28 17:02:13 +0000
commit49af073ed77202a54dfdd773cbcbbf7835c75baf (patch)
treeb180dbeab238a3d30b8d99d05c9cf0e30fbadd5a /kadmin/kadmin.1
parentd684f11da759490a8d98d7b790796106285f4084 (diff)
heimdal: Vendor import 7.7.0vendor/heimdal/7.7.0
Diffstat (limited to 'kadmin/kadmin.1')
-rw-r--r--kadmin/kadmin.110
1 files changed, 8 insertions, 2 deletions
diff --git a/kadmin/kadmin.1 b/kadmin/kadmin.1
index ef5c87e434c1..296f9f8004f2 100644
--- a/kadmin/kadmin.1
+++ b/kadmin/kadmin.1
@@ -250,7 +250,7 @@ kadmin -l modify -a -disallow-proxiable user
Changes the password of an existing principal.
.Ed
.Pp
-.Nm password-quality
+.Nm verify-password-quality
.Ar principal
.Ar password
.Bd -ragged -offset indent
@@ -258,7 +258,13 @@ Run the password quality check function locally.
You can run this on the host that is configured to run the kadmind
process to verify that your configuration file is correct.
The verification is done locally, if kadmin is run in remote mode,
-no rpc call is done to the server.
+no rpc call is done to the server. NOTE: if the environment has
+verify-password-quality configured to use a back-end that stores
+password history (such as heimdal-history), running
+verify-quality-password will cause an update to the password
+database meaning that merely verifying the quality of the password
+using verify-quality-password invalidates the use of that
+principal/password in the future.
.Ed
.Pp
.Nm privileges