On 26 May 2019, at 2:27pm, Karl Sanders <[email protected]> wrote:
> I'd like to ask a few questions about the SEE extension. > > - Are tables (virtual and real) used by the various extensions (in > particular by the FTS5 and R*Tree modules) encrypted? The entire database file is encrypted, block by block, including the header block, blocks describing the schema, and blocks containing freespace. If you don't understand how to decrypt it you can't tell how many tables it holds, what part of the file is tables, or what part is indexes. > - Are there any pragmas or compile-time options that don't work with > encryption? Any program which doesn't have the SEE extension compiled into it will not be able to open the database file. So, for instance, you won't be able to use the downloadable sqlite3 shell tool. The SEE source code includes source code for a special version of the shell tool which includes the SEE extension and adds extra features useful for managing encryption. There are similar concerns about utilities like the sqlite3_analyzer. > - Is there any functionality that is available in a limited way, or > not at all, while using an encrypted database? I don't think so, since if you can read any part of the database you can read all the database. _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
