Dear Brian,
Thank you, it is usefull information.
I do not know yet.
But I guess it is my own risk.
Brian Carlstrom wrote:
>since the keystore is not a public API, the implementation isn't
>guaranteed to have the same behavior on all devices. the low level
>interface has been changing signific
since the keystore is not a public API, the implementation isn't
guaranteed to have the same behavior on all devices. the low level
interface has been changing significantly in JellyBean.
-bri
On Mon, Jun 10, 2013 at 3:15 AM, Kouji Ishikawa wrote:
> Dear Brian,
>
> Thank you for your advice.
> I
Dear Brian,
Thank you for your advice.
I try to make some original approach to use keystore, because the program
is not a normal app
but built in service program (for example /system/bin/sdcard) .
If it is difficult to use, my program will have original data store.
2013/6/10 Brian Carlstrom
App's currently have two choices:
1.) install their key into system key chain
2.) manage the data themselves in the app directory
there is work to allow apps to install their own data into the key store
for their own use in AOSP in
frameworks/base/keystore/java/android/security/AndroidKeyStore.jav
Dear Brian,
> It means on purpose, working as intended, this is not a bug, and won't be
changed.
I understand.
Normal apps can use KeyChain APIs.
And apps do not have to use private key directory, if there is signing and
verification API.
When a developer make raw program module that uses it's
On Sat, Jun 8, 2013 at 4:26 PM, Kouji Ishikawa wrote:
> By the way, what does it mean "by design".
>
It means on purpose, working as intended, this is not a bug, and won't be
changed.
> It is no library, no public info about communicating keystore ?
>
the code is all in AOSP. but the public A
Dear Brian,
By the way, what does it mean "by design".
It is no library, no public info about communicating keystore ?
Or any protection of security ?
I can challenge to access the keystore if it is not protected by security.
How about is it ?
--
You received this message because you are subscr
Thanks Brian,
OK, I try KeyChain API via JNI.
2013年6月7日金曜日 14時08分37秒 UTC+9 Brian Carlstrom:
>
> You can no longer get the private key in raw form by design. The
> PrivateKeys returned by the KeyChain delegate their operations back to the
> keystore. From native code the supported API is use JNI
You can no longer get the private key in raw form by design. The
PrivateKeys returned by the KeyChain delegate their operations back to the
keystore. From native code the supported API is use JNI to make calls using
PrivateKeys using return by the KeyChain API. I believe chromium has some
code show
Dear all,
I have a problem to get private key from keystore with C/C++ program module.
Above version ICS, certifications are just stored in the keystore.
And the keystore_cli program can get list and some certification from
keystore.
And in Java, the KeyChain API can get private key like this s
10 matches
Mail list logo
