From: Staffan T. <sta...@gm...> - 2012-09-14 20:48:48
|
The source for SQLCipher consists of individual program files instead of an amalgamation file, with a few of them modified to provide the necessary hooks for the encryption to take place. As SQLite already is prepared for encryption, the amount of modifications required is as far as I understand minimal, most is controlled by the SQLITE_HAS_CODEC flag. RexxSQL access to SQLCipher? Interesting thought, the problem is that one have to pay to find out :( For me the biggest problem with RexxSQL is that the latest version 2.6 with thread support doesn't have a binary version for SQLite. Staffan On Fri, Sep 14, 2012 at 10:23 PM, Mark Miesfeld <mie...@gm...> wrote: > On Fri, Sep 14, 2012 at 12:52 PM, Mark Miesfeld <mie...@gm...> > wrote: > > On Fri, Sep 14, 2012 at 11:09 AM, Staffan Tylen <sta...@gm...> > wrote: > > > >> Mark, thanks for your quick feedback. The main reason for not using the > >> binaries at this stage is that I'm in a research phase to see what > options I > >> have available for database encryption. I'm not aware of a binary > solution > >> that supports encrypted SQLite under ooRexx. So I'm looking at the > >> feasibility of putting something together using for example source code > for > >> ooSQLite and SQLCipher. If there in fact is a binary solution I would > >> clearly look at that first. > > > > > > If there was a standard extension to SQLite that did encryption, I > > could be tempted into doing a standard ooSQLite build that included > > that extension. > > Sorry, I should have looked as SQLCipher first, before I said > anything. SQLCipher is a completely different library than the SQLite > library. It has different licensing that makes it not attractive to > me for ooRexx. > > You will not be able to use SQLCipher with the approach you are > taking. You will have to replace the SQLite source code completely > with the SQLCipher source code in the source tree. Unless the > SQLCiper source code files are a one-to-one relation with the SQLite > source files, you will then need to change the make file to build and > link the correct object files. > > Most of the Rexx bindings in the ooSQLite class file will probably > work, but you might have to change a few things. > > You wouldn't have to, but you should change the name of the DLL > produced by your build to something different. And change the .cls > file to load that DLL. Otherwise you may end up using the wrong DLL. > > You end up with a different database engine and your own native > extension. Certainly there is no reason why you can't do that based > on the current work for ooSQLite. But, I'm not sure it is something > someone unfamiliar with C / C++ will have an easy time doing. > > RexxSQL doesn't give you access to SQLCipher does it? > > -- > Mark Miesfeld > > > ------------------------------------------------------------------------------ > Got visibility? > Most devs has no idea what their production app looks like. > Find out how fast your code is with AppDynamics Lite. > http://ad.doubleclick.net/clk;262219671;13503038;y? > http://info.appdynamics.com/FreeJavaPerformanceDownload.html > _______________________________________________ > Oorexx-users mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-users > |