Re: [Oorexx-users] ooSQLite and encryption (continued)

[Mark M. <mie...@gm...>]

On Mon, Oct 15, 2012 at 9:53 AM, Staffan Tylen <sta...@gm...>wrote:


> In case someone is still interested in this subject I wish to mention that
> a more straight forward solution compared to SQLCipher could be to use an
> open source project called botanSQLite3 (
> https://github.com/OlivierJG/botansqlite3). The implementation seems very
> simple, a tiny change to the SQLite3 amalgamation source, a few compile and
> link and that should be it. To be honest I've spent too much time trying to
> get this done but my lack of C/C++ experience won't let me reach the target
> so I'm hoping someone else might give it a try. The only change to SQLite
> will be two new APIs, sqlite_key() and sqlite_rekey(), which should be easy
> enough to add to ooSQLite. The solution however requires access to the
> botan libraries (http://botan.randombit.net/) which even I managed to
> build from source using MinGW. Both botan and botansqlite3 have the same
> distribution license, which appear to be the same as the one for ooRexx.
> Anyone who wants to have a go?
>
>

Staffan,

The RFE you opened prompted me to take a closer look at this.  Stumbling
blocks would be the ability to compile and link using VC++ and the license.

Botan itself is readily compiled using VC++.  Plus they have a way of
generating a single amalgamation file that can be embedded in a
application.  This would work well with ooSQLite.

It is not so easy to tell if the botansqlite3 code will compile under VC++,
but looking through the code, I do not see any obvious reason why it
wouldn't.

The license looks okay.

All in all, it looks like there is reason to expect it to be doable.  At
this point, I think I will give it a shot around Christmas time.  I'd
rather not get started on something new until I finish up what I am
currently working on, an ooDialog 4.2.1 release and an ooSQLite 1.0.0
release with complete documentation.  I may try to get a build to work
before than if I have some time.

--
Mark Miesfeld