--> But it does work with System.Data.SQLite. Would that entail a mandatory reconstruction of the System.Data.SQLite project to utilize SEE for compatibility on the C++ side as well?
Adding to both would be a good idea as Mike N suggested, but for clarity to the superiors, I would like confirmation on the congruent encryption/decryption methods used on the publicly available System.Data.SQLite V/r, Ryan -----Original Message----- From: sqlite-users-bounces at mailinglists.sqlite.org [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On Behalf Of Richard Hipp Sent: Tuesday, May 17, 2016 11:57 AM To: SQLite mailing list Subject: Re: [sqlite] Accessing an encyrpted Sqlite Database On 5/16/16, Ryan Irwin <rirwin at hrsi.com> wrote: > > I am aware of the SEE but am lead to believe that it may be > proprietary and would not match the encryption method used by the > DotNet and SQLite.Interop. > SEE is indeed proprietary. (http://www.hwaci.com/sw/sqlite/see.html). But it does work with System.Data.SQLite. -- D. Richard Hipp drh at sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users at mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
