History log of /system/security/keystore-engine/eng_keystore.cpp
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
938a991106a9bd064eb2ede1fb46d9c2ef94c1be 16-Aug-2012 Kenny Root <kroot@google.com> Clear out ENGINE flags when initializing

We don't need our engine to be copied when initialized with
ENGINE_by_id, so just make sure our flags are cleared when we
initialize.

Change-Id: Ie75fad37c2f78a769c425889c1d0661b468cd0c7
/system/security/keystore-engine/eng_keystore.cpp
a8c703d9fdd98e3caefb6e74cd03c2878cecd0a1 17-Jul-2012 Brian Carlstrom <bdc@google.com> Handle keynames with special characters such as - and .

Bug: http://code.google.com/p/android/issues/detail?id=34577
Bug: 6837950

(cherry-picked from 0114bd9f9bbc2458ca77bf3508e7c15992a432b1)

Change-Id: I0c265fe73c1b2c430ffd196a21691264f8f3b555
/system/security/keystore-engine/eng_keystore.cpp
bef8083783df4b06972f33b468eccf941e335864 03-May-2012 Kenny Root <kroot@google.com> Only initialize ex_data if not already

ENGINE_by_id will load up multiple copies of the engine which will
create a new ex_data index each time it's called. This change makes sure
the ex_data index is only initialized once.

Change-Id: I5e197faf6273ec3b3cafcbeadf7da8ec04a4f50b
/system/security/keystore-engine/eng_keystore.cpp
98c2f8fcc1263a9d94adac66994fffc96c0df699 28-Mar-2012 Colin Cross <ccross@android.com> use UniquePtr.h from frameworks/native

Use the UniquePtr.h include from frameworks/native/include/utils
to fix the pdk build.

Change-Id: Ic415b43d2eb8c0b7ef54b6f3f75b7fa0d5f7a058
/system/security/keystore-engine/eng_keystore.cpp
70e3a86abd2c412d602a018967c01c177eb6cf4e 16-Feb-2012 Kenny Root <kroot@google.com> Add keymaster to keystore with soft implementation

Add hardware crypto capabilities to keystore. This allows hardware
escrow of private key material.

There is also an OpenSSL engine that connects to keystore to allow use
of the keystore keys from native code built into the platform.

This includes a software implementation of keymaster using OpenSSL
as the backend. This is just as insecure as the previous solution,
but it's needed so devices without hardware support can continue
to operate in the new scheme without a lot of compatibility code.

Change-Id: I2bc67766e1f633ef1cbbd2874a65962074e84f4f
/system/security/keystore-engine/eng_keystore.cpp