SmartDongle Java Native Interface for libusb

Download

• SmartDongle JNI Examples.zip

Contents

• Example 1: Simple method to check for valid SmartDongle
  
  

• Example 2a: Write some application data to a SmartDongle

• Example 2b: Read the application data written in Example2a
  
  

  If you store data on a SmartDongle you may wish to encrypt the data transmitted over the USB bus.
  

  Examples 3 below use AES encryption. A developer could use example3a.c as a utility to write passwords, serial numbers, etc to a SmartDongle that can be read back and used in an application as demonstrated by example3b.c

• Example 3a: Utility to encrypt a user string using AES and write this string to a SmartDongle

• Example 3b: An application that reads and decrypt the secret written in Example3a
  
  

  Example 4 below takes advantage of Java Object Serialization.

• Example 4a: Utility to initialize a user's Properties Object, serialize the object, encrypt the serial stream, then write this stream to a SmartDongle

• Example 4b: An application that retrieves the user's Properties Object that was serialized and encrypted in Example 4a
  
  

• Read SmartDongle serial number

Note

If SmartDongle access returns error codes 41 or 42, the problem may be that the mode of the dynamic SmartDongle device files in /proc/bus/usb/ and /dev/bus/usb/ do not allow user access.
As of linux kernel version 2.6.x, permissions can be set with hal facilities.
Refer to src/HAL/README.txt

Building the Examples

1. You must have Java Platform Standard Edition Development Kit and Java Standard Edition Runtime Environment installed.

2. Download and unzip: SmartDongle JNI Examples.zip

3. Edit the example code to use your unique key values, for example:
   private final static long p1 = 0xEC6CC589AEFD1E75L;
   private final static long p2 = 0xFCEC0A6A82747B3FL;

4. Edit build.cmd file in the corresponding example's directory:

   • This variable corresponds to your main class name
     MAIN_CLASSNAME=Example1

   • This variable corresponds to your full qualified class name
     FULLY_QUALIFIED_CLASSNAME=Java_Example1
     The fully qualified class name is required for the JNI function names. If this is an incorrect fully qualified classname, executing example1 will produce this error:
     Exception in thread "main" java.lang.UnsatisfiedLinkError: smartDongleWrite

   • Edit these paths:

     The absolute path to the project directory such as: WORKING_DIR="/home/your_home_directory/SmartDongle JNI Examples"

     Path Java Development kit binaries
     JAVA_HOME=/opt/sun-jdk-1.5.0.13

     Path to GNU gcc complier:
     CC=/usr/bin/gcc

5. Running build.cmd script, this will automate these steps:

   • Initial compilation of the main class and creation of JNI C header file.
   • SmartDongle interface source files are processed and SmartDongle JNI library (libuskjni.so) is compiled using your fully qualified class name (FULLY_QUALIFIED_CLASSNAME).
   • Computation of SHA fingerprint of libuskjni.so
   • The SmartDongle code in the main class file is updated with the SHA fingerprint.
   • The main class is then recompiled.