Re: [Opensc-devel] Crypto Chip Support imaginable ?

[Marx, P. <Pet...@kn...>]

Hi Alex,

we don’t have a tight resource limit – It’s much more horsepower than e.g. Raspberry. It’s a NXP T1042 CPU, so no chance to leverage the discussed INTEL features.

Native Java would be preferred, but JNI wrapped C/C++ Code is a 2nd option.


Regards

Peter

From: Alexander Gostrer [mailto:ago...@gm...]
Sent: Wednesday, June 15, 2016 9:20 PM
To: Marx, Peter
Cc: Douglas E Engert; ope...@li...
Subject: Re: [Opensc-devel] Crypto Chip Support imaginable ?

Hi Peter,

From your explanation my understanding is that you are limited with resources (CPU speed, memory, etc). Did you consider using C/C++ rather than Java?

Regards,
Alex.

On Wed, Jun 15, 2016 at 9:37 AM, Marx, Peter <Pet...@kn...<mailto:Pet...@kn...>> wrote:
Hi Alex,

I’m aware of this engine, see requirement #1. That indeed can cover the provisioning process, combined with certmonger’s getcert via SCEP -> EJBCA PKI solution.
But the Java apps are not aware of this store, as they expect to access the store via PKCS#11…

Thanks

Peter


Knorr-Bremse IT-Services GmbH
Sitz: Muenchen
Geschaeftsfuehrer: Helmut Draxler (Vorsitzender), Harald Jessen, Harald Schneider
Registergericht Muenchen, HR B 167 268

This transmission is intended solely for the addressee and contains confidential information.
If you are not the intended recipient, please immediately inform the sender and delete the message and any attachments from your system. 
Furthermore, please do not copy the message or disclose the contents to anyone unless agreed otherwise. To the extent permitted by law we shall in no way be liable for any damages, whatever their nature, arising out of transmission failures, viruses, external influence, delays and the like.