xtea | XTea encrypt decrypt esp8266 | Encryption library

StoreCipherKey Function:

I made a mistake in the build script:

You don't format at all, just write raw bytes. You are reading raw bytes using

Maybe someone will come in handy. The library “golang.org/x/crypto/xtea” does not include the XTEA algorithm with the ECB model because of its insecurity, therefore I wrote my own version:

It seems Botan support for building Android binaries on Windows hosts is limited. You will have to use dark magic to make this work.

The build process consists of two phases, the configuration phase and the make phase.

The Android-specific instructions in the documentation you linked do not cover the whole build process, only the configuration phase. For the make phase, you then have to follow the Windows-specific instructions (link).

You will need the following binaries, adjust the paths to your machine:

• clang++ (note the .cmd at the end): C:\Development\android-ndk-r19c-windows-x86_64\android-ndk-r19c\toolchains\llvm\prebuilt\windows-x86_64\bin\armv7a-linux-androideabi28-clang++.cmd

• ar: C:\Development\android-ndk-r19c-windows-x86_64\android-ndk-r19c\toolchains\llvm\prebuilt\windows-x86_64\bin\arm-linux-androideabi-ar.exe

In the Botan folder, run the configure command:

Your issue is caused by an integer overflow. A unint32_t is an integer of fixed size 2^32 bits. 0x9e3779b9 * 15 is 39816536535 which is approx 2^35.

This means you get an overflow as the memory location is simply not big enough to hold your number. Javascript does not have this problem as its not statically typed and the size allocated in memory will increase dynamically to hold it.

Use a larger datatype for C++, like an unsigned long or size_t (alias for unsigned long on most systems). Preferably use auto to let the compiler decide for you: