Does Android support APDUConnection as known from JSR 177?

by Neil.Young » Mon, 23 Feb 2009 05:15:36 GMT


Sponsored Links
 Simple question. More answers?

Regards


--~--~---------~--~----~------------~-------~--~----~



Does Android support APDUConnection as known from JSR 177?

by Anders Rundgren » Mon, 23 Feb 2009 20:10:49 GMT


 I don't know but JSR 177 seems to be a J2ME-related JSR.
Android has (in theory) a JCE-based API that does what JSR 177 does
and more.
The problem is really that there is no link between the JCE and the
SIM if that's what you are looking for.
Personally I think using the SIM with JSR 177 is a bad idea, SIM TK
solutions are the only generally available.

You may be interested in  http://android-keystore-v2.webpki.org 

BTW, are you the "real" Neil Young? :-)  I'm a true fan!

Rgds
AR



--~--~---------~--~----~------------~-------~--~----~


Sponsored Links


Does Android support APDUConnection as known from JSR 177?

by spongebob.squarepants » Tue, 24 Feb 2009 01:32:34 GMT


 Hi Anders,

many thanks for answering. I don't know what happened, but over the
weekend I seemed to blow my rather old account Neil.Young, so it is
BANNED now (I did never appear such things :() and I don't know, why.
What went wrong with my subscription?

So I'm forced to use this rediculous account to proceed :) Neil and
Spongebob, what a difference ;)

OK, back to the problem: JCE based API, hmm. Could you please be a bit
more specific? What I wanted to achieve is to gain access to the SIM
card, especially to the authentication algorithms.

Please don't let our conversation stop, you are my only contact to
this group... I was a very active member in the beginning of Android,
but shifted my focus in 2008. The only thing, I wanted, was to
return... But I was BANNED, thanks...

Regards






--~--~---------~--~----~------------~-------~--~----~



Does Android support APDUConnection as known from JSR 177?

by Anders Rundgren » Tue, 24 Feb 2009 13:47:57 GMT


 Hi Neil,
Sorry about the banning.
Now to the SIM issues.  I have been working with mobile phone auth
solutions since 1998 and it has been said that the SIM is the way to
go.  For various reasons, and in particular due to a lack of a
business model, operators have often used the cheapest SIMs they could
find  I.e. SIM are often wihout RSA capability.   Anyway, since the
SIM is owned, reserved, andcontrolled by the operators, the handset
makers haven't done very much to make SIMs usable except trough SIM
ToolKit.  In the EU there are large deployments of SIM TK auth
solutions.  These solutuions are all horrible and not integrated with
the phone apps.

I started my project to get rid of SIM dependencies.

Anders

On Feb 23, 2:12pm, "spongebob.squarepants"




--~--~---------~--~----~------------~-------~--~----~



Does Android support APDUConnection as known from JSR 177?

by Spongebob.Squarepants » Tue, 24 Feb 2009 16:50:54 GMT


 Hi Anders,

thanks for the answer. On the other hand there are things like "Remote 
SIM Access" in the Nokia world, which allow one to ask the SIM for PIN 
verification, call the AUTHENTICATE algorithms and attach the SIM phone 
book. And there are various SIM card reader solutions out, which give 
access to the EFs, so not all hope is lost.

The SIM TK you mentioned: Is something similar available with Android? 
What about rSAP? (Remote SIM Access protocol)

Regards

--~--~---------~--~----~------------~-------~--~----~



Other Threads

1. Android Camera Garbage Collection.

Hey All,
      I am developing a camera application , where the frame rate is
important. However, camera uses a preview callback function which
allocates a byte[] array of 230400 bytes, which makes it necessary for
the garbage collection to step in. Can someone suggest me a way to
avoid garbage collection stepping in ?
Thanks in advance.
Regards,
Karan.


--~--~---------~--~----~------------~-------~--~----~

2. ERROR: Application requires API version 2. Device API version is 1

You're running Android 1.0 on the device, which is API version 1.
Unless you think your target audience is still on 1.0 for one reason
or another, I'd recommend you update your device to at least 1.1, or
better yet, straight to 1.5. They have version numbers 2 and 3
respectively.
Now if you absolutely need to cover 1.0, you have to drop
minSdkVersion to 1.




--~--~---------~--~----~------------~-------~--~----~

3. Starting services on Android Boot

4. ERROR: Application requires API version 2. Device API version is 1

5. How to get Streaming Videos?

6. Finding Device (and android version) from code

7. Problem while streaming amr file