On Fri, Jul 19, 2013 at 3:21 AM, Sqlite Dog <sqlite...@gmail.com> wrote:
> > Our database manager is developed using Delphi (Pascal). Thus it is not > possible to statically link SQLite library, SQLite.dll is used. Is there > some other way to support SEE in our project? > Yes. You can ship it as a DLL and use a special pragma to enable the encryption feature. We ask that you rename the DLL to something that does not contain the words "SQLite" or "SEE" or anything similar, to disguise its purpose. > > SEE supports several various encryption algorithms. If a database is > already encrypted does it automatically choose needed algorithm? How to > specify algorithm for a new database if a version of SEE is used which > supports all of them? Or is it always using most "powerful" one (AES-256)? > There is no way to detect which encryption algorithm is used. Indeed, the encryption is so thorough that there is no way to tell whether or not the file you are trying to open is an encrypted database file or just a file of white noise. The default algorithm is the fastest algorithm (AES-128). I suggest you stick to that one algorithm unless you have a compelling reason to use another. That way, you never need to worry which algorithm is being used. -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
