From: Dongsun Lee <ds73.lee@samsung.com>
Date: Sat, 27 Jun 2015 06:27:54 +0000 (+0900)
Subject: add a solution in case for no password set
X-Git-Tag: accepted/tizen/mobile/20150629.000431~1
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;ds=inline;h=07537558404c671d2bb26101ae87fe37bc9706e5;p=platform%2Fcore%2Fsecurity%2Fkey-manager.git

add a solution in case for no password set

Change-Id: Ie7d65c5165a2d0e162b4e990240c84e12d6227ed
Signed-off-by: Dongsun Lee <ds73.lee@samsung.com>
---

diff --git a/src/manager/service/ckm-service.cpp b/src/manager/service/ckm-service.cpp
index 644e1c4..3a21a64 100644
--- a/src/manager/service/ckm-service.cpp
+++ b/src/manager/service/ckm-service.cpp
@@ -166,6 +166,14 @@ RawBuffer CKMService::ProcessStorage(Credentials &cred, MessageBuffer &buffer)
     buffer.Deserialize(command);
     buffer.Deserialize(msgID);
 
+    // This is a workaround solution for locktype=None in Tizen 2.2.1
+    // When locktype is None, lockscreen app doesn't interfere with unlocking process.
+    // Therefor lockscreen app cannot notify unlock events to key-manager when locktype is None.
+    // So, to unlock user data when lock type is None, key-manager always try to unlock user data with null password.
+    // Even if the result is fail, it will be ignored.
+    Password nullPassword("");
+    m_logic->unlockUserKey(cred.clientUid, nullPassword);
+
     LogDebug("Process storage. Command: " << command);
 
     switch(static_cast<LogicCommand>(command)) {