[key-manager]Remove description about user login. This feature was disabled by default.

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

diff --git a/org.tizen.guides/html/native/security/secure_key_n.htm b/org.tizen.guides/html/native/security/secure_key_n.htm
index c7c52ca..ca2833b 100644 (file)
--- a/org.tizen.guides/html/native/security/secure_key_n.htm
+++ b/org.tizen.guides/html/native/security/secure_key_n.htm
@@ -74,18 +74,6 @@
        <li>If a client provides a password when storing data, the data is encrypted with the password. This password must be provided when getting the data from the key manager.</li></ul></li>
        </ul>
 </li>
-<li>User login
-
-<p>The user login control is implemented as follows:</p>
-
-<ul>
-<li>A user&#39;s database file is encrypted by the user&#39;s DKEK (domain key encryption key). The user DKEK is randomly generated and stored encrypted with a user password when a user logs in for the first time.</li>
-<li>When a user logs in, the key manager decrypts the user DKEK with a user password. During the login session, any client can access the data which is protected by a user password. When a user logs out, the key manager removes the user DKEK from the memory.</li>
-<li>When a user logs in, logs out, or changes their password, the key manager must be notified. Only privileged applications, such as LockScreen or Setting, can notify the key manager.</li>
-<li>When a user changes their password, the key manager re-encrypts the user DKEK with the new password.</li>
-</ul>
-</li>
-
 <li>Data access control
 
 <p>By default, only the data owner can access the data. If the owner grants access to other applications, those applications can read or delete the data from the key manager database.</p>
@@ -1044,4 +1032,4 @@ var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga
 </script>
 
 </body>
-</html>
\ No newline at end of file
+</html>

diff --git a/org.tizen.guides/html/web/security/secure_key_w.htm b/org.tizen.guides/html/web/security/secure_key_w.htm
index b748983..7007632 100644 (file)
--- a/org.tizen.guides/html/web/security/secure_key_w.htm
+++ b/org.tizen.guides/html/web/security/secure_key_w.htm
@@ -67,18 +67,6 @@
     <li>If a client provides a password when storing data, the data is encrypted with the password. This password must be provided when getting the data from the key manager.</li></ul></li>
     </ul>
 </li>
-<li>User login
-
-<p>The user login control is implemented as follows:</p>
-
-<ul>
-<li>A user&#39;s database file is encrypted by the user&#39;s DKEK (domain key encryption key). The user DKEK is randomly generated and stored encrypted with a user password when a user logs in for the first time.</li>
-<li>When a user logs in, the key manager decrypts the user DKEK with a user password. During the login session, any client can access the data which is protected by a user password. When a user logs out, the key manager removes the user DKEK from the memory.</li>
-<li>When a user logs in, logs out, or changes their password, the key manager must be notified. Only privileged applications, such as LockScreen or Setting, can notify the key manager.</li>
-<li>When a user changes their password, the key manager re-encrypts the user DKEK with the new password.</li>
-</ul>
-</li>
-
 <li>Data access control
 
 <p>By default, only the data owner can access the data. If the owner grants access to other applications, those applications can read or delete the data from the key manager database.</p>