[IOT-1514] Always log sensitive data at DEBUG level
authorKevin Kane <kkane@microsoft.com>
Fri, 4 Nov 2016 19:58:37 +0000 (12:58 -0700)
committerRandeep Singh <randeep.s@samsung.com>
Tue, 15 Nov 2016 08:35:20 +0000 (08:35 +0000)
commitb1f177268a10c0563548a0eb986a5e327ebb3030
tree496b663244b3c85bd10b8371cc700aa400b604a1
parentcfc23d4cfeb1f9ca71155989ea6d1ebc5d38da12
[IOT-1514] Always log sensitive data at DEBUG level

Some sensitive data is logged at levels other than DEBUG. Having
all of these at DEBUG can help ensure in release builds secret
data isn't inadvertently leaked through logging.

Change-Id: I58aa4ebc8e8dcdbc9d267d7eef3135a21e6daa0b
Signed-off-by: Kevin Kane <kkane@microsoft.com>
Reviewed-on: https://gerrit.iotivity.org/gerrit/14085
Tested-by: jenkins-iotivity <jenkins-iotivity@opendaylight.org>
Reviewed-by: Dave Thaler <dthaler@microsoft.com>
Reviewed-by: Dan Mihai <Daniel.Mihai@microsoft.com>
Reviewed-by: Uze Choi <uzchoi@samsung.com>
Reviewed-by: Randeep Singh <randeep.s@samsung.com>
(cherry picked from commit 7257937531b5a9165f58e377eafffae175259665)
Reviewed-on: https://gerrit.iotivity.org/gerrit/14321
resource/csdk/security/provisioning/src/multipleownershiptransfermanager.c
resource/csdk/security/provisioning/src/ownershiptransfermanager.c
resource/csdk/security/src/directpairing.c
resource/csdk/security/src/dpairingresource.c