PureBasic Forums - English

There are a few plugins for SQLite that supports database encryption - could one of them be added to the Database library?

I see only CEROD, this cost 2000 US $ and you can't ship the static lib, only the final exe.

Have you some links to other plugins?

This looks free: http://sqlcipher.net/

Okay, but i see some other problems. If Fred compile a static lib for PB, the compiler have always add the OpenSSL.lib,
so all executables that use SQLite a bigger. I see no way to make this optional, PB can't recompile the C-Source.
The other problem, is the Source always actual to the original SQLite-Source?

Okay, we will see what Fred says, if he says anything

ts-soft wrote:Okay, but i see some other problems. If Fred compile a static lib for PB, the compiler have always add the OpenSSL.lib,
so all executables that use SQLite a bigger. I see no way to make this optional, PB can't recompile the C-Source.
The other problem, is the Source always actual to the original SQLite-Source?

Okay, we will see what Fred says, if he says anything

Well there's the possibility of making it a new DB plugin, separate to the standard SQLite

But then you'd have to find someone to maintain it, and pray they don't go missing or abandon it.

Polo wrote:This looks free: http://sqlcipher.net/

Is here someone who managed to compile it and test with PureBasic?

Wxsqlite is very good , that can be encrypt , I hope pb package it

Wxsqlite is very good , that can be encrypt , I hope pb package it

........but that is an sqlite wrapper for wxWidgets!

IdeasVacuum wrote:........but that is an sqlite wrapper for wxWidgets!

incidentally , that good to Wrapper the wxWidgets in PB

You can wrap it if you wanna, the PB gadget library is good enough for most of us
(and that's not what this request is about )

Just offering some thoughts on this.

It is my understanding that the SQlite source must be modified to be included within PB in the first place. So I don't see why adding encryption support should be a huge problem for users (not commenting on the programming aspect of adding it, I don't know what Fred knows). You could add it as a totally separate library, or you could integrate it into existing SQLite support in PB, by adding some additional parameters to the Procedures that are used for SQlite.. A master boolean toggle for encryption on/off and it can decide when/if to include the extra encryption stuff into the compiled program?

Alternatively, would it be possible for Fred to add encryption as a generic feature of the PB database library itself, rather than for a specific database engine (SQLite)?

Not exactly sure how it would be done, I'll leave the API/implementation details to Fred and the other gurus here, but if we could flag either all columns or just specific columns to be encrypted - that would be slick.

Then the ability to encrypt data would be automatically applicable to ALL databases that PB supports, including any DBs supported in the future.

I have to believe this would be incredibly inefficient?
Wouldn't it be faster to only compress/encrypt certain fields in your table design?

skywalk wrote:Wouldn't it be faster to only compress/encrypt certain fields in your table design?

USCode wrote:... or just specific columns to be encrypted ...