JavacardOS will not accept order any more, please contact our partner Feitian online Store:
https://ftsafe.en.alibaba.com/index.html
https://ftsafe.en.alibaba.com/index.html
Search found 12 matches
- Thu Jul 06, 2017 6:17 am
- Forum: Questions & Answers
- Topic: Secure Messaging
- Replies: 3
- Views: 10900
Re: Secure Messaging
I have tried but it return with 6E00( Class not supported). I guess SELECT command is sent in plain outside the secure channel.
- Wed Jul 05, 2017 3:16 am
- Forum: Questions & Answers
- Topic: Secure Messaging
- Replies: 3
- Views: 10900
Secure Messaging
I am using SCP01 with static key 40 41 42..4F to protect the READ BINARY APDU. And the external authentication is successful. But I always got error status word 6982 (Security condition not satisfied). Could anyone figure out the reason? Thank you. >> 80 50 00 00 08 00 00 00 00 00 00 00 00 << 00 00 ...
- Wed Apr 12, 2017 11:16 pm
- Forum: Questions & Answers
- Topic: Native methods on javacard
- Replies: 2
- Views: 9483
Native methods on javacard
Hey all,
Can I perform Native java methods in java card?
Thanks®ards,
Rasiand
Can I perform Native java methods in java card?
Thanks®ards,
Rasiand
- Fri Nov 25, 2016 1:46 am
- Forum: Questions & Answers
- Topic: Different performance under different protocol
- Replies: 1
- Views: 7291
Different performance under different protocol
Hi everyone in here, I am experiencing a strange problem now . When I sent "8060000004" command, the applet performed differently under T0 and T1 protocol. T0 protocol: It threw"6F00" while running into this code line short le = apdu.setOutgoing(); T1 protocol: It can return test...
- Fri Sep 30, 2016 3:55 am
- Forum: Questions & Answers
- Topic: Failed to read data from the card
- Replies: 2
- Views: 7331
Re: Failed to read data from the card
I can successfully write and read a smaller data from the card using extended length apdu.
- Thu Sep 29, 2016 11:48 pm
- Forum: Questions & Answers
- Topic: Failed to read data from the card
- Replies: 2
- Views: 7331
Failed to read data from the card
Hello!
I can write a large data into the card successfully by sending extended length APDU. But When I try to read the same length data back from the card, it always failed.
Does anyone know the reason?
I can write a large data into the card successfully by sending extended length APDU. But When I try to read the same length data back from the card, it always failed.
Does anyone know the reason?
- Thu Jun 30, 2016 3:23 am
- Forum: Questions & Answers
- Topic: the max size of atomic transaction buffer
- Replies: 3
- Views: 9805
Re: the max size of atomic transaction buffer
wousim wrote:It‘s set by the card manufacturer.
There are several methods in the JCSystem class that can do this - getMaxCommitCapacity and getUnusedCommitCapacity.
If I know nothing about the max size of this buffer, Can I just beginTransaction and never invoke commitTransaction ?
- Wed Jun 29, 2016 4:36 am
- Forum: Questions & Answers
- Topic: the max size of atomic transaction buffer
- Replies: 3
- Views: 9805
the max size of atomic transaction buffer
As we all know, atomic transaction buffer is used to log changes in order to help JCRE rollback in case of failed command. But I don't know the max size of this buffer. Could I just beginTransaction and never invoke commitTransaction ?
Thanks
Thanks
- Wed Jun 15, 2016 5:20 am
- Forum: Questions & Answers
- Topic: RuntimeException v.s. Exception
- Replies: 2
- Views: 8349
Re: RuntimeException v.s. Exception
This is just my understanding.
RuntimeException is there to specify normal exceptions.
Exception is there to handle bigger scope, with all types of exception.
RuntimeException is there to specify normal exceptions.
Exception is there to handle bigger scope, with all types of exception.
- Wed Jun 15, 2016 2:02 am
- Forum: Questions & Answers
- Topic: RuntimeException v.s. Exception
- Replies: 2
- Views: 8349
RuntimeException v.s. Exception
Could any one clarify the difference between RuntimeException and Exception? In my opinion, every exception must happen at run time, and therefore, I think we only need RuntimeException. There is no need for Exception.