OK. Thank you.
2013/7/19 Richard Hipp <d...@sqlite.org> > On Fri, Jul 19, 2013 at 9:20 AM, Sqlite Dog <sqlite...@gmail.com> wrote: > > > > > > > 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. > > > > > > > > > Suppose there are two databases, one is RC-4 encrypted and the other is > > AES-256 encrypted. > > What happens on open? SEE will use default algorithm and fail? Or it will > > try all algorithms in cycle? > > > > It will use the default algorithm and succeed. But then later when you try > to query the database you'll get back an SQLITE_CORRUPT error. > > -- > D. Richard Hipp > d...@sqlite.org > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > -- Regards, SqliteDog support team _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
