amended section on combining authentication mechanisms

diff --git a/INSTALL b/INSTALL
index 1dd50fc084a24e744a7ad26abb90d5881df289a5..e955e876e6f2b083f89405290e4f3eebd7749fc0 100644 (file)
--- a/INSTALL
+++ b/INSTALL
@@ -158,11 +158,12 @@ Mixing password authentication schemes
 ======================================
 
 It is possible to build sudo with support for several authentication
-schemes, including shadow passwords, kerberos, s/key, AFS, DCE,
-and normal UN*X passwords into a single binary.  User validation
-will take slightly longer, of course, but it may be valuable
-to have a single sudo binary that is distributed among systems
-with varying authentication mechanisms.
+schemes, including shadow passwords, kerberos, s/key, AFS, DCE and
+normal UN*X passwords into a single binary.  User validation will
+take slightly longer, of course, but it may be valuable to have a
+single sudo binary that is distributed among systems with varying
+authentication mechanisms.  The exception to this rule is SecurID
+which must be the only authentication mechanism used.
 
 OS dependent notes
 ==================