Search

tay00000

I am not sure if any manufacturer have successfully moved beyond JC 3.0.4 officially despite JC 3.0.5 and JC 3.1 specifications being generally available in the public.

tay00000

Note that there's a difference between chip level certification and COS level certification. If both chip and COS are certified, it is even better. Regarding sensitive data storage on the COS level, you should be doing encryption of highly sensitive data manually unless the chip specs specially ment...

tay00000

Firstly, what is this ? SecP256K1.newKeyPair() and how did you derive that ? This is not a default JavaCard API and it seems like some class you made or you imported. We will need more information on that if you can comfortably provide it. This seems to be crucial as it determines how the SECP-256K1...

tay00000

Solved by passing the output byte array using the APDU buffer. Why does the APDU buffer work ? Because it is the default global byte array buffer that is allowed to cross between the applet firewall by the JCRE and thus is a natural candidate. APDU buffer also has the advantage of the JCRE automatic...

tay00000

C based programmable smart cards are highly limited as 95% of the cards available in the industry is made up of JavaCard. You are better off using JavaCard as JavaCard is the industry standard for smart cards and almost every specification for card systems these days seems to revolve around JavaCard...

tay00000

Table - New Features in Java Card API Specification New Feature...........|.....Description ------------------------------------------------------------------- AES ciphering modes.....................Added support for AES-CFB mode for stream ciphering and AES-XTS mode for secure storage. -----------...

tay00000

If the SAM card already contains an applet, you will NOT be able to extract the applet codes and data from the SAM card. It is very insecure to allow extraction of code from a SAM/SIM/Smart card so this option is definitely not available at all. The SAM card's purpose is to prevent cloning so the an...

tay00000

Signature.ALG_AES_CMAC_128 is only available from JC 3.0.5 and up.

If you want to implement it yourself, please look at this old forum thread which contains one of our member's source code (https://javacardos.com/javacardforum/vi ... php?t=1114).

tay00000

Just adding additional points which @owlstead has done a good job in pointing. Here's a couple of extra problems I noticed in the OP's source code. byte [] buffer = new byte [32]; buffer = apdu.getBuffer(); Do you know that by doing that, you will create a persistent memory object with a 32 byte byt...

tay00000

Is there any programming API to create applets for the JuBiter card ?

Search found 135 matches: re:

Re: JC 3.1

Re: question confused me about key data storage?

Re: ECDSA (secp256k1) Signature Verification Fails

Re: How to get object working over Shareable Interface

Re: C++ programmable smartcard

Re: JC 3.1

Re: SAM Card Decompile

Re: Is there a good way to implement an AES-CMAC encryption on Java Cards?

Re: Combine two byte array and encrypt them togethor

Re: Feitian JuBiter Blade

Board Disclaimer