SQLite Encryption Extension

Second paragraph on that page (emphasis mine):

Some of the documentation on this website is open to viewing by the general public. However, access to the SEE source code and precompiled binaries requires a username and password, which is available only to licensees. Perpetual source-code licenses are available for purchase separately.

So, security by obscurity? Sorry, but that has a certain unwelcome smell. See Kerckhoffs's principle.

https://www.sqlite.org/see/doc/release/www/readme.wiki lists the following algorithms:

• RC4 with security enhancements
• AES-128 in OFB mode
• AES-128 in CCM mode
• AES-256 in OFB mode
• Simple XOR (in the text below the list)

XOR is explicitly documented as "demonstration module that does not do real encryption". Consider it broken.

RC4 is insecure, if not broken. Period. See RC4. There are no agreed "security enhancements".

AES-128 is probably still ok, if implemented correctly. But side channel attacks can be very efficient, recovering the entire 128-bit key using 6 to 7 blocks of encrypted content. See Advanced Encryption Standard.

AES-256 should be ok, if implemented correctly.

How can you check if AES is implemented correctly? How can you check the "security enhancemments" for RC4? Well, buy the pig in the poke, then look at what you bought. Security by obscurity.

Alexander