[opensc-user] Aladdin eToken Pro 64K and Aladdin eToken NG-OTP support?

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[opensc-user] Aladdin eToken Pro 64K and Aladdin eToken NG-OTP support?

Jan Schermer
Hi,
I just received one of each and was wondering whether it is/will be usable with opensc?

So far I only managed to erase both tokens, but pkcs15-init -C bails out with:

pkcs15-lib.c:2636:sc_pkcs15init_authenticate: path=3f00, op=3
card.c:531:sc_create_file: called; type=2, path=3f005015, size=2048
card-etoken.c:442:etoken_create_file: etoken_create_file(3F005015)
card-etoken.c:180:etoken_check_sw: invalid parameters in data field
card-etoken.c:518:etoken_create_file: returning with: Incorrect parameters in APDU
card.c:536:sc_create_file: returning with: Incorrect parameters in APDU
(both tokens)


>From what I've seen it looks like OpenCT supports these tokens, but OpenSC does not?

Is there something I can do to make it usable?

Thanks
-- 
Jan Schermer
Freelance UNIX Specialist

GSM: +420-608022225
email: [hidden email]
ICQ: 19466257
WWW: http://www.zviratko.net

CONFIDENTIALITY HAIKU:

This plaintext message
not alone in the network
notice for the lame

_______________________________________________
opensc-user mailing list
[hidden email]
http://www.opensc.org/cgi-bin/mailman/listinfo/opensc-user
Reply | Threaded
Open this post in threaded view
|

Re: Aladdin eToken Pro 64K and Aladdin eToken NG-OTP support?

Andreas Jellinghaus-2
On Monday 19 September 2005 19:14, Jan Schermer wrote:
> Hi,
> I just received one of each and was wondering whether it is/will be
> usable with opensc?

I have neither hardware, I asked Aladdin and Siemens for documentation,
and without NDA and/or paying money I can't get any.
 
>  From what I've seen it looks like OpenCT supports these tokens, but
> OpenSC does not?

that is correct. OpenCT is simply: it implements the usb stuff and aladdin
does little more than T=1 which is well documented. So it was easy to
implement that part.

But we cannot implement OpenSC support without full documentation and
hardware.

> Is there something I can do to make it usable?

Try to get the user manual for cardos 4.20/4.3b and implement the driver.
I guess the changes are quite small, so you could go through each function
in card-etoken and compare it to the new manual. maybe a changed bit here
and there, but I guess no bigger change. and because we can set flags
based on the atr and the code can have different paths depending on those
flags, it should be easy to add a few if / else contructs to adapt to the
changes siemens did.

Note: even if you do that work, aladdin still uses a proprietory and
undocumented structure, so you can use the keys and certificates only
with the software you used for initialization - either opensc or aladdins.

we implement pkcs#15 standard - they don't. we have code for adding
emulations, but we would need documentation on their format to do that.
so far no luck on getting any. if you have time, I was told it is possible
to reverse engineer their format.

Regards, Andreas
p.s. please start new threads only on one mailing list. either is fine.
_______________________________________________
opensc-devel mailing list
[hidden email]
http://www.opensc.org/cgi-bin/mailman/listinfo/opensc-devel