The wolfSSL embedded SSL/TLS library is a lightweight SSL library written in ANSI standard C and targeted for embedded and RTOS environments – primarily because of its small size, speed, and feature set. It is commonly used in standard operating environments as well because of its royalty free pricing and cross platform support. wolfSSL supports industry standards up to the current TLS 1.2 level, is up to 20 times smaller than OpenSSL, and offers progressive ciphers such as HC-128, RABBIT, and NTRU. User benchmarking and feedback reports dramatically better performance when using wolfSSL over OpenSSL. It is available under both GPLv2 and commercial licenses, like MySQL, making it ideal for a wide variety of projects.

Guardship disassembles your .NET code and then compiles the MSIL code of your executable into native unmanaged application by generating two pieces: 1. Start module [Your_App_Name].com; 2. Library [Your_App_Name].lib
Your applications (WinForms, WPF, etc.) that target the .NET Framework are compiled to intermediate language (IL). At run time, the just-in-time (JIT) compiler translates the IL to native code. Guardship translates your .NET executable to native code to make it hidden. When you run the protected executable it has all features and functionalities of managed application performing in PC memory. But .NET assembly browsers and decompilers will not be able to read your protected .NET executables.
Why does Guardship convert to unmanaged executable?
There are a few disassemblers for decompiling unmanaged executables written in ASM, C, or C++. However none of them will manage to produce readable enough code to worth the effort. You will spend more time trying to read the decompiled source with assembler blocks inside, than writing the same-functioning application from scratch.
In fact, any executable module can be disassembled and explored. The easiness with which a decipherer can reverse-engineer your application source code depends on how complete metadata about the app’s source code presents inside the exe module. May the decipherer figure out the original class names, methods, work flows, structures, etc.? A compiler basically compacts app’s source code, transforming the output into a format which is much compliant to machine runtime execution. It could be a native machine code or IL byte code that is treated by CLR intermediate runtime. However by and large, a lot of information about your application source code (debugging, comments, etc.) is simply can be lost during the compact compilation.

Automated 3D object model creation SDK. 3D scanning performed from sets of photos taken with regular smartphone or still camera.

The technology performs several steps of object model creation. A point cloud is created at first. A mesh (wireframe model) is generated based on the point cloud. A texture is recreated from the captured object surface and applied to the generated model, so the final model has realistic look. SentiSculpt allows to save the generated object model in widely used file formats so the model can be used by most 3D graphics and CAD applications.

The SDK includes programming samples in C, C++, C# and Visual Basic .NET.