Re: jcop 4 driver --test

--===============2616871143872045250==
Content-Type: multipart/alternative; boundary="00000000000025f0a5064f936806"

--00000000000025f0a5064f936806
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, Apr 16, 2026 at 2:25=E2=80=AFPM AlanCui4080 <[email protected]> wrote:

> I don't really know what's a driver for JCOP 4, JCOP is an implemention o=
f
> JavaCard
> or OS developed by NXP, You can, and have to install applets to make it
> "useful".
>

I' unsure about the correct naming (driver,applet,..) but here is what I
know:

- the old implementation in OpenSC had the name card-jcop.c

card-jcop.c implements the APDU Manual for BlueZ PKCS#15, the pdf is
available here:

 https://public.dhe.ibm.com/software/pervasive/info/BlueZ-PKCS15.pdf

This was implemented in 2003, NXP took this Manual and made proprietary
extensions.
So maybe I have a JCOP 4.x card, with a NXP Applet which is mostly
compatible to BlueZ?

Now I have this initialized card, which I can read with this old driver,
but the
tests do not work and I don't have this proprietary NXP APDU Manual.

I think I will give it a bit more time and try to make a few tests work.
The porting up to now was rather quick (less than two days), so with a bit
of luck I can
make a read-only driver.

best regards,

Martin

--00000000000025f0a5064f936806
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote g=
mail_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Apr 16,=
 2026 at 2:25=E2=80=AFPM AlanCui4080 &lt;<a href=3D"mailto:[email protected]">m=
[email protected]</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddin=
g-left:1ex">I don&#39;t really know what&#39;s a driver for JCOP 4, JCOP is=
 an implemention of JavaCard<br>
or OS developed by NXP, You can, and have to install applets to make it &qu=
ot;useful&quot;.<br></blockquote><div><br></div><div>I&#39; unsure about th=
e correct naming (driver,applet,..) but here is what I know:</div><div><br>=
</div><div>- the old implementation=C2=A0in OpenSC had the name card-jcop.c=
</div><div><br></div><div>card-jcop.c implements the APDU Manual for BlueZ =
PKCS#15, the pdf is available here:</div><div><br></div><div>=C2=A0<a href=
=3D"https://public.dhe.ibm.com/software/pervasive/info/BlueZ-PKCS15.pdf">ht=
tps://public.dhe.ibm.com/software/pervasive/info/BlueZ-PKCS15.pdf</a></div>=
<div><br></div><div>This was implemented in 2003, NXP took this Manual and =
made proprietary extensions.</div><div>So maybe I have a JCOP 4.x card, wit=
h a NXP Applet which is mostly compatible to BlueZ?</div><div><br></div><di=
v>Now I have this initialized card, which I can read with this old driver, =
but the=C2=A0</div><div>tests do not work and I don&#39;t=C2=A0have this pr=
oprietary NXP APDU Manual.</div><div><br></div><div>I think I will give it =
a bit more time and try to make a few tests work.</div><div>The porting up =
to now was rather quick (less than two days), so with a bit of luck I can</=
div><div>make a read-only driver.</div><div><br></div><div>best regards,</d=
iv><div><br></div><div>Martin</div></div></div>

--00000000000025f0a5064f936806--


--===============2616871143872045250==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


--===============2616871143872045250==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Opensc-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensc-devel

--===============2616871143872045250==--