[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 03:52:30 +0000 (03:52 +0000)
commit7257937531b5a9165f58e377eafffae175259665
treebb9a9b101af07c1a126feda502f78525f888dd01
parentdc5ce01c137d023418d31d9cfa1de2c34051b53d
[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>
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