From 4ccc18bc3ddc49d0fd0d2de00ec91c0fa44c53a8 Mon Sep 17 00:00:00 2001 From: Greg Hudson Date: Wed, 23 Oct 2013 11:55:19 -0400 Subject: Use active master key in update_princ_encryption kdb5_util update_princ_encryption should update to the active master key version, not the most recent. ticket: 6507 target_version: 1.12 tags: pullup --- doc/admin/admin_commands/kdb5_util.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'doc') diff --git a/doc/admin/admin_commands/kdb5_util.rst b/doc/admin/admin_commands/kdb5_util.rst index 2d7636ef1..f9fcd0afe 100644 --- a/doc/admin/admin_commands/kdb5_util.rst +++ b/doc/admin/admin_commands/kdb5_util.rst @@ -324,8 +324,8 @@ update_princ_encryption Update all principal records (or only those matching the *princ-pattern* glob pattern) to re-encrypt the key data using the -active database master key, if they are encrypted using older -versions, and give a count at the end of the number of principals +active database master key, if they are encrypted using a different +version, and give a count at the end of the number of principals updated. If the **-f** option is not given, ask for confirmation before starting to make changes. The **-v** option causes each principal processed to be listed, with an indication as to whether it -- cgit