What is it?

Driverless hardware-based protection uses a physical device, commonly known as piggy-back internally attach to GPIO Raspberry Pi. Rapid & simple implementation, by compiling your code with available library you can use the unique hardware serial number to verify

Why did you make it?

Hardware internal authentication discourages hardware cloning. Protect multiple applications with one device.

What makes it special?

Easy plug & play for Linux code protection.

Step-by-step

• 1) Switch off your Raspberry Pi;
• 2) Attach device to GPIO according with image (device uses the GPIO Pins from 17 to 26);
• 3) Power on your Raspberry Pi;
• 4) Use set_key application to set up your private key;
• ---> e.g.: set_key A3768BF214E4CC897D901AA22FF69A34
• 5) Change the key_array, of file serial_check.h, according with previous key;
• 6) Function serial_number_check_procedure will check if stored serial match with input parameter sys_serial;
• 7) Compile your application linking with libCrypt_hw_serial.a
• ---> e.g.: gcc test.c -o test -L. -lCrypt_hw_serial