Search

chico0609

Because the byte[] in the install method is the global buffer. You will need to defer this call until the process method has been invoked.

chico0609

Acctually, it's not a good idea to use the global platform secure channel.
If the keys are compromised, an attacker can then manage the card.

So donot use the GP secure channel for application security.

chico0609

It seems that it is wrong TLV-coded data.

chico0609

When you have a byte that is greater than 0x7F and meanwhile you want to make it an unsigned value, you can use the following to prevent the sign extension:

Code: Select all


short a = (short) (b & 0xFF);

chico0609

Try to use AES instead.

chico0609

It seems that your problem has something to do with DES weak key. Do you use weak key?

chico0609

Yes, if you use new statement, the key objects will be stored in persistent memory.

You just need to write once and then you can read many times.

chico0609

buildKey is not used to generate a key. And what type of memory is used by the genKeyPair() method, Transient or Persistent ? From my understanding, it is common for a smart cards to have RAM dedicated to cryptographic operations. In fact, as much of the operation as possible is done in transient RA...

chico0609

JCIDE doesn't support HMAC.

chico0609

There is an option under "Build" - "Property". On the property sheet, just disable "- debug" option. Then your final cap file will not include debug.cap.

JCIDE_configuration.png

Search found 59 matches

Re: How to use APDU instance in install method

Re: secure channel security question

Re: How to decode the response data

Re: How to get big number

Re: cipher/ decipher with 3DES alg

Re: cipher/ decipher with 3DES alg

Re: Difference between KeyBuilder and KeyPair

Re: Difference between KeyBuilder and KeyPair

Re: Does JCIDE support HMAC?

Re: Exclude debug.cap in JCIDE

Board Disclaimer