2008-07-30 17:15:55 +00:00
|
|
|
== SQLite Cipher Introduction ==
|
|
|
|
|
|
|
|
|
|
SQLite Cipher is an SQLite extension that provides transparent 256 bit AES encryption of database files.
|
|
|
|
|
Pages are encrypted before being written to disk and are decrypted when read back.
|
|
|
|
|
|
|
|
|
|
Encryption is provided by the OpenSSL crypto library.
|
|
|
|
|
|
|
|
|
|
Static linking (replace /opt/local/lib with the path to libcrypto.a)
|
|
|
|
|
./configure --disable-amalgamation CFLAGS="-DSQLITE_HAS_CODEC" LDFLAGS="/opt/local/lib/libcrypto.a"
|
|
|
|
|
make
|
|
|
|
|
|
|
|
|
|
Dynamic linking
|
|
|
|
|
./configure --disable-amalgamation CFLAGS="-DSQLITE_HAS_CODEC -lcrypto"
|
|
|
|
|
make
|
|
|
|
|
|
2008-07-30 17:33:57 +00:00
|
|
|
SQLite Cipher was developed by Stephen Lombardo at Zetetic LLC.
|
|
|
|
|
sjlombardo at zetetic.net
|
|
|
|
|
http://zetetic.net
|
|
|
|
|
|
|
|
|
|
This code is released under the same public domain terms as SQLite itself.
|
|
|
|
|
|
|
|
|
|
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
|
|
|
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
|
|
|
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
|
|
|
|
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
|
|
|
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
|
|
|
|
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
|
|
|
|
|
THE SOFTWARE.
|
|
|
|
|
|
2008-07-30 17:15:55 +00:00
|
|
|
== End Introduction ==
|
|
|
|
|
|
2008-07-30 13:15:43 +00:00
|
|
|
This directory contains source code to
|
|
|
|
|
|
|
|
|
|
SQLite: An Embeddable SQL Database Engine
|
|
|
|
|
|
|
|
|
|
To compile the project, first create a directory in which to place
|
|
|
|
|
the build products. It is recommended, but not required, that the
|
|
|
|
|
build directory be separate from the source directory. Cd into the
|
|
|
|
|
build directory and then from the build directory run the configure
|
|
|
|
|
script found at the root of the source tree. Then run "make".
|
|
|
|
|
|
|
|
|
|
For example:
|
|
|
|
|
|
|
|
|
|
tar xzf sqlite.tar.gz ;# Unpack the source tree into "sqlite"
|
|
|
|
|
mkdir bld ;# Build will occur in a sibling directory
|
|
|
|
|
cd bld ;# Change to the build directory
|
|
|
|
|
../sqlite/configure ;# Run the configure script
|
|
|
|
|
make ;# Run the makefile.
|
|
|
|
|
make install ;# (Optional) Install the build products
|
|
|
|
|
|
|
|
|
|
The configure script uses autoconf 2.61 and libtool. If the configure
|
|
|
|
|
script does not work out for you, there is a generic makefile named
|
|
|
|
|
"Makefile.linux-gcc" in the top directory of the source tree that you
|
|
|
|
|
can copy and edit to suit your needs. Comments on the generic makefile
|
|
|
|
|
show what changes are needed.
|
|
|
|
|
|
|
|
|
|
The linux binaries on the website are created using the generic makefile,
|
|
|
|
|
not the configure script.
|
|
|
|
|
The windows binaries on the website are created using MinGW32 configured
|
|
|
|
|
as a cross-compiler running under Linux. For details, see the ./publish.sh
|
|
|
|
|
script at the top-level of the source tree.
|
|
|
|
|
|
|
|
|
|
Contacts:
|
|
|
|
|
|
|
|
|
|
http://www.sqlite.org/
|
