Adding cap check after smack_have_access in security-server and displaying logs
authorMarcin Niesluchowski <m.niesluchow@samsung.com>
Mon, 19 Aug 2013 14:15:20 +0000 (16:15 +0200)
committerBartlomiej Grzelewski <b.grzelewski@samsung.com>
Thu, 6 Feb 2014 16:13:21 +0000 (17:13 +0100)
commitc24a550f54c29abc8cf5ff64f8844cd6abd1117a
treeeacdeb7b6c3b0f3fd5aa7010af7ecd3ea76045f8
parentb4c5cf948cebb19496c92e33d7ba4d7d9d24a301
Adding cap check after smack_have_access in security-server and displaying logs
regarding this call.

[Issue#]        SSDWSSP-454
[Bug/Feature]   SECURE_SLOG* macros used after smack_have_access() and its wrapper
                don't write messages to dlog and CAP_MAC_OVERRIDE is not checked.
[Cause]         SECURE_SLOG* macros depend on TIZEN_ENGINEER_MODE flag in dlog.h
                which is turned off.
[Solution]      Changing SECURE_SLOG* to SEC_SVR_* and Log* macros and adding check for
                CAP_MAC_OVERRIDE after smack_have_access.
[Verification]  Check dlogutil for those logs.

Change-Id: I167dea72f9c1bcbcc2c4ea7008eea3a6bbbd9c82
src/server2/service/privilege-by-pid.cpp
src/util/security-server-util-common.c