JAVA Toolkit
| home | contact



News Menu

Latest News

IAIK-JCE 5.52 and iSaSiLk 5.2 released!

27/08/2018

The new versions of IAIK-JCE and iSaSiLk follow up the recently released new version of IAIK-ECCelerateTM (5.0). IAIK-JCE 5.52 brings some fixes and additions, and iSaSiLk 5.2 adds support for x25519 and x448 ECDHE key exchange and EdDSA signing using Curve25519 and Curve448. Furthermore iSaSiLk now supports RSA-PSS signatures.

ECCelerate 5.0 released!

12/07/2018

We proudly present a new maintenance release of our IAIK ECCelerate™ elliptic curve library! Version 5.0 adds support EdDSA using Curve25519 and Curve448, ECDH using X25519 and X448, and RFC6979. IAIK ECCelerate™ is based on Java 6 technology and has been thoroughly optimized for speed. Currently, it supports ECDSA, EdDSA, ECDH, X25519/448, ECIES and optionally ECMQV.

References

Our Clients


Errors

 

Q:

When running some of the samples which try to generate keys, I get an iaik.pkcs.pkcs11.wrapper.PKCS11Exception: CKR_TEMPLATE_INCOMPLETE. What is wrong?

A:

Your specified key template seems to miss some attributes. For example an AES template must have set the attribute valueLen (cka_value_length).

Q:

When running some of the samples which try to generate keys, I get an iaik.pkcs.pkcs11.wrapper.PKCS11Exception: CKR_ATTRIBUTE_VALUE_INVALID. What is wrong?

A:

Some PKCS#11 modules restrict changing of certain attributes or setting of certain combinations (e.g. key value and key length). Please consult your module's documentation for further details.

Q:

 When running some of the samples which try to generate keys, I get an iaik.pkcs.pkcs11.wrapper.PKCS11Exception: CKR_ATTRIBUTE_TYPE_INVALID. What is wrong?
 

A:

Some PKCS#11 modules do not support certain attributes or modifying certain attributes (e.g. object class or key type). As workaround you can try to set the class and key-type attributes as not present. This may look like this:

     secretEnrcyptionKeyTemplate.getObjectClass().setPresent(false);
     secretEnrcyptionKeyTemplate.getKeyType().setPresent(false);

maybe the driver accepts the key template if you try this.

Q:

Why do I always get an java.lang.UnsatisfiedLinkError: no pkcs11wrapper in java.library.path?

A:

 It seems that you do not have the pkcs11wrapper.dll (or libpkcs11wrapper.so under Unix) in you search path. You can provide such a path directly to the Java™ VM setting the java.library.path system property like:
 

java -Djava.library.path==../bin/<windows|unix>/<platform>/release;. 
   -cp classes;../bin/iaikPkcs11Wrapper.jar demo.pkcs.pkcs11.GetInfo cryptoki.dll

 where ../bin/ <windows|unix >/ <platform >/release is the path where the pkcs11wrapper.dll (or libpkcs11wrapper.so under unix) file is. You can also place the file in the folder for binary files of you Java™ Runtime Environment; e.g. the jre/bin folder. Alternatively, you can also place the file pkcs11wrapper.dll in the system directory of Windows. On Unix systems you can place the libpkcs11wrapper.so in a lib directory of the system.
 


 
print    tip a friend
back to previous page back  |  top to the top of the page