| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
[Problem]
* EVP_Digest parameter type is unsigned int
* size_t is differ between 32bit and 64bit
[Solution]
* Use unsigned int instead of size_t
Change-Id: Ib398532c7148bcd9d736c7282e0b74c8042a2ede
Signed-off-by: sangwan.kwon <sangwan.kwon@samsung.com>
|
|
For migrated web app, we need to more fields in cache e.g., IV and
is_migrated flag to handle it separately.
Because cipher algorithm, iv and key size could be different between old
secure storage, it depends on product implementation. So this
architecture needs more flexibility.
A lot of code changed because of the principle data structure is added
from the bottom.
Change-Id: Id6a10b9f707f4da25016dd928ab4049be619a610
Signed-off-by: Kyungwook Tak <k.tak@samsung.com>
|
|
Change-Id: I60d574d8813637077fa1e278a3d72dbfed07333c
Signed-off-by: Kyungwook Tak <k.tak@samsung.com>
|
|
secure-storage is removed since Tizen platform version 3.0.
downloaded web apps encryption works based on different key from lower
than 3.0. secure-storage used DUK(device unique key with seed(pkgid)) as DEK.
If downloaded app cannot find DEK when decrypt, it's considered as
encrypted lower than 3.0 case. So webappenc creates DEK and uses algorithm
which had been used lower than 3.0 in secure-storage.
For now it's hard to save newly created old key in key-manager because
migrated web app is considered as global app and the case would be found
in decryption time (by web app launcher) who don't have permission to save
in system db of key-manager with "/System" label.
Permission policy of system db of key-manager should be changed OR
migrated app should not be global app (it should be downloaded normal
app) to save created key in key-manager.
Change-Id: I9b8516184cce9f43b328e290c15127151e5c861e
Signed-off-by: Kyungwook Tak <k.tak@samsung.com>
|
