Hi,

I have downloaded the latest Sentinel HASP 5.10 and started to evaluate its functionality. As per the documents that came within the package downloaded, it is capable of protecting Java executables, namely .jar files. Using its Envelope feature, I've tried protecting some of the .jar files that resides within the installed directory of our product.

First we protected the lax.jar file which is sort of the bootstrap module that does the heavy lifting part of our platform, which in its module loading phase, all .jar dependency are loaded onto memory. When we protected this lax.jar per se, the application launches after pressing "OK" when the "Please note that this program is only protected with a Sentinel HASP demo key" message dialog prompts. However, when I protected one of its dynamically loaded jar module as well, the application launches but terminates when it reaches the point where this protected modules starts to being loaded, throwing the following Java Runtime Exception.

1. java.lang.IllegalArgumentException: wrong number of arguments
2. at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
3. at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
4. at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
5. at java.lang.reflect.Method.invoke(Method.java:597)
6. at com.aladdin.nemesis.a.do(uc:73)
7. at com.aladdin.nemesis.d.b.do(k:344)
8. at com.aladdin.nemesis.d.a.do(j:80)
9. at com.aladdin.nemesis.JANemsis.aldn_1989undnochda_mwtbdltr(vc:119)
10. at com.appresso.ds.kernel.modules.mgr.launch.DataSpiderLaunchManagerImpl.setModuleContext(DataSpiderLaunchManagerImpl.java)
11. at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
12. at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
13. at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
14. at java.lang.reflect.Method.invoke(Method.java:597)
15. at com.appresso.ds.kernel.BeanInstance.invoke(BeanInstance.java:265)
16. at com.appresso.ds.kernel.BeanInstance.invoke(BeanInstance.java:259)
17. at com.appresso.ds.kernel.ModuleInstance.invoke(ModuleInstance.java:199)
18. at com.appresso.ds.kernel.ModuleInstance.invoke(ModuleInstance.java:185)
19. at com.appresso.ds.kernel.ModuleInstance.load(ModuleInstance.java:71)
20. at com.appresso.ds.kernel.DataSpiderKernel.register(DataSpiderKernel.java:389)
21. at com.appresso.ds.kernel.DataSpiderKernel.registerChildren(DataSpiderKernel.java:372)
22. at com.appresso.ds.kernel.DataSpiderKernel.register(DataSpiderKernel.java:417)
23. at com.appresso.ds.kernel.DataSpiderKernel.registerChildren(DataSpiderKernel.java:372)
24. at com.appresso.ds.kernel.DataSpiderKernel.start(DataSpiderKernel.java:316)
25. at com.appresso.ds.kernel.Bootstrap.start(Bootstrap.java:109)
26. at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
27. at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
28. at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
29. at java.lang.reflect.Method.invoke(Method.java:597)
30. at com.appresso.ds.boot.main.BeanInstance.invoke(BeanInstance.java:141)
31. at com.appresso.ds.boot.main.BeanInstance.invoke(BeanInstance.java:86)
32. at com.appresso.ds.boot.main.BeanInstance.invoke(BeanInstance.java:81)
33. at com.appresso.ds.boot.main.DataSpiderServerMain.main(DataSpiderServerMain.java:22)
34. at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
35. at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
36. at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
37. at java.lang.reflect.Method.invoke(Method.java:597)
38. at com.appresso.ds.boot.Main.run(Main.java:124)
39. at com.appresso.ds.boot.Main.main(Main.java:50)
40. at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    

My concern is whether it is possible to protect each module that are loaded as aforementioned using Sentinel HASP SL.

What is the best practice for such case?
We cannot create a large one-jar executable due to the application design and 3rd party libraries that we include.

Thank you for your kind attention, 

Haruhiko Nishi