From: Todd C. Miller <Todd.Miller@courtesan.com>
Date: Sun, 28 Nov 2004 21:05:38 +0000 (+0000)
Subject: verifypw when used in a boolean TRUE context should be "all", not "any".
X-Git-Tag: SUDO_1_7_0~780
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=f5c359ee06aed727e89f6f344c0e59a3fc3ca94c;p=sudo

verifypw when used in a boolean TRUE context should be "all", not "any".
---

diff --git a/def_data.c b/def_data.c
index 7b1200519..19d734eee 100644
--- a/def_data.c
+++ b/def_data.c
@@ -15,8 +15,8 @@ static struct def_values def_data_listpw[] = {
 
 static struct def_values def_data_verifypw[] = {
     { "never", never },
-    { "any", any },
     { "all", all },
+    { "any", any },
     { "always", always },
     { NULL, 0 },
 };
diff --git a/def_data.in b/def_data.in
index 81b616f1e..b055febe2 100644
--- a/def_data.in
+++ b/def_data.in
@@ -172,7 +172,7 @@ listpw
 verifypw
 	T_TUPLE|T_BOOL
 	"When to require a password for 'verify' pseudocommand: %s"
-	never any all always
+	never all any always
 noexec
 	T_FLAG
 	"Preload the dummy exec functions contained in 'noexec_file'"