Anyone know what OID 1.3.656.840.100.2.1.3 maps to?
I've been playing around with a JCOP41v221 card and I was able to dump the card
information file (GET DATA command with tag 0x66). What I get is an ASN1
encoded blob. Dumping the blob, I get the values below.I was able to find
the regist
Ismael Valladolid Torres wrote:
We're trying to add cryptographic support to GSM cards. What we're thinking is
> hacking some cryptographic application so it reads wirelessly its support
files
> from a card inserted in a mobile phone and registered into the network.
At first what we need is
Sebastian Hans ha scritto:
Moreover Musclecard reports being available to Java cards, which
include current GSM cards. Does this mean Musclecard don't make use
of the filesystem in any way?
yes what makes sense if you have your keys and other credential
defined as Java objects.
Also, please con
On 6/22/07, Ismael Valladolid Torres <[EMAIL PROTECTED]> wrote:
Also, Musclecard implements PKCS #11 where OpenSC implements PKCS #15. What are
the differences from a practical point of view between #11 and #15?
pkcs11 is standart for universal application use of smartcards etc...
pkcs15 is sta
Ismael Valladolid Torres wrote:
We're trying to add cryptographic support to GSM cards. What we're thinking is
hacking some cryptographic application so it reads wirelessly its support files
from a card inserted in a mobile phone and registered into the network.
If you want to run your appli
We're trying to add cryptographic support to GSM cards. What we're thinking is
hacking some cryptographic application so it reads wirelessly its support files
from a card inserted in a mobile phone and registered into the network.
At first what we need is to make clear the scope where OpenSC is
