> > queries are just stored as normal string constants in C++ so it is easy to > be decoded via reverse engineering method.
Is the normal "reverse engineering method": 1. a hexdump of your executable? 2. debugging your executable? A trivial cipher could be used to encode the strings prior to storing in C++ and then decoded on the fly. That would protect against the strings be obvious in a casual hexdump, but would provide no protection against a determined adversary who could guess the likely cipher (from reverse engineering your Google searches or likely reference books). "Show me your flowcharts and conceal your tables, and I shall continue to be mystified. Show me your tables, and I won?t usually need your flowcharts; they?ll be obvious." Fredrick Brooks, Mythical Man-Machine Month, page p. 102-3 https://en.wikiquote.org/wiki/Fred_Brooks Jim Callahan Orlando, FL On Thu, Feb 25, 2016 at 1:01 AM, <admin at shuling.net> wrote: > Hi, > > In my C++ program, I will invoke SQLite to execute SQL queries. But these > queries are just stored as normal string constants in C++ so it is easy to > be decoded via reverse engineering method. Does SQLite provide a good way > to > encrypt the SQL query strings while does not affect the performance when > executing the queries? > > Thanks > > > > _______________________________________________ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users >
