Fix: match exact privilege for priv lookup
RAKP message 1 must match exact privilege, when Username/privilege
lookup bit is set as per IPMI specification. This fixes the bug
of allowing session setup if the requested privilege is less than
user privilege, which is allowed for name-only lookup.
Unit-test:
After creating a user with operator privilege verified that following
command works
ipmitool -I lanplus -H xx.xx.xx.xx -U <user> -P <passord> raw 6 1 -L user
following command failed to estabilish session
ipmitool -I lanplus -H xx.xx.xx.xx -U <user> -P <passord> raw 6 1 -L user+
Change-Id: I90a2f841b3190e95bb23ba2a368aa134c7a7aea9
Signed-off-by: Richard Marian Thomaiyar <richard.marian.thomaiyar@linux.intel.com>
diff --git a/command/rakp12.cpp b/command/rakp12.cpp
index 594a8fe..2854716 100644
--- a/command/rakp12.cpp
+++ b/command/rakp12.cpp
@@ -194,10 +194,10 @@
session->curPrivLevel = static_cast<session::Privilege>(minPriv);
}
// For username / privilege lookup, fail with UNAUTH_NAME, if requested
- // max privilege is greater than the user privilege.
+ // max privilege does not match user privilege
if (((request->req_max_privilege_level & userNameOnlyLookupMask) ==
userNamePrivLookup) &&
- ((request->req_max_privilege_level & session::reqMaxPrivMask) >
+ ((request->req_max_privilege_level & session::reqMaxPrivMask) !=
userAccess.privilege))
{
log<level::INFO>(