Jan,
Many thanks for your response - also all the others -
many thanks.
I agree that the error status indicates the length of
the APDU to wrong. However, the APDU in question that
is generated in the example code starts with the bytes
[00 08 00 00 1B <1B bytes>]. I already verified the
APDU size and the length 1B is correct.
Isn't it possible that this APDU is not know to the
Cyberflex Access card but to the Cyberflex 16k only?
The reason why I am asking this is that there is no
[00 08 00 ...] APDU documented in the Cyberflex Access
Software Developer's Kit 2 Release Notes (page 117f).
The other thing I do not understand a 100% yet is the
signing of the applet. Do I need to sign the applet
only or do I need to sign the whole container? What's
the key to use and what's the algorithm/tool to use?
(I am looking at the packages
opencard.opt.applet.mgmt.* and
com.slb.opencard.CyberflexAccess.* right now).
--- Jan Peter Hecking <[EMAIL PROTECTED]> wrote:
> On Thu, Mar 29, 2001 at 07:08:55AM -0800, Friendly
> Aless wrote:
> > makeLoadAPDU() [00 08 00 00 ...] is sent to the
> card.
> > The card simply returns 6700 - what does that
> mean?
>
> The status words returned by the card are defined in
> ISO 7816-4.
> Search the web to find the full document.
> 0x6700 means "Wrong length" so the Le (length
> expected) byte of your
> APDU seems to be incorrect.
__________________________________________________
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail.
http://personal.mail.yahoo.com/?.refer=text
***************************************************************
Linux Smart Card Developers - M.U.S.C.L.E.
(Movement for the Use of Smart Cards in a Linux Environment)
http://www.linuxnet.com/smartcard/index.html
***************************************************************
