> I was under the impression that is how SEE works. Hooking the SQLite > Virtual File System interface seems like a very straight forward method. > All you really need to do is splice your code between the VFS that > the SQLite engine sees and the native VFS layer that comes with the > distribution, adding a bit of extra code to xRead() and xWrite() to > munge the data. I've never tried it but the documentation makes it > look like something you could do without modification to the core > source and with very little code other than the actual encrypt/decrypt > routines, plus the interfaces required to configure them. No actual > file system code, nor any OS specific code. > > In theory. 8-) > > http://sqlite.org/c3ref/vfs.html > http://sqlite.org/c3ref/io_methods.html > > > No, it is probably more correct to say that the SEE plugs into the pager. It does not layer the VFS. Look where the CODEC1 and CODEC2 macros are used.
Mr. Kreibich should contact DRH and ask about the encryption extension. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
