And here is a copy of my answer posted at stackoverflow (which assumes the
context of the question):
A see a few problems here.
1.
The first SQL statement (CREATE TABLE ...) is malformed due to an extra
comma between the last column and the closing parenthesis.
2.
The third SQL
On Sat, Feb 27, 2016 at 10:49 PM, Simon Slavin wrote:
>
> On 28 Feb 2016, at 5:47am, Keith Medcalf wrote:
>
> > I do not see a link ... do you see a link?
>
> I saw no link.
>
> The OP may not actually be posting to this mailing list. He may be using
> a web interface which does the posting
I do not see a link ... do you see a link?
> -Original Message-
> From: sqlite-users-bounces at mailinglists.sqlite.org [mailto:sqlite-users-
> bounces at mailinglists.sqlite.org] On Behalf Of Christoforus Surjoputro
> Sent: Saturday, 27 February, 2016 21:12
> To: SQLite mailing list
>
?
On Thu, 25 Feb 2016 14:01:31 +0800
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
On 27 Feb 2016, at 3:20pm, Dave Baggett wrote:
> It would be interesting to contemplate running all of SQLite on an HSM, as
> this would allow you to perform database transactions while ensuring the
> database itself was kept hidden from the host computing device. I'm not aware
> of any
Hi Simon.
I've post it in stackoverflow link I gave before. About run ANALYZE, SQLite
still choose their own index instead Index that I've made. Thank you.
On Saturday, February 27, 2016 12:49 AM, Simon Slavin wrote:
On 26 Feb 2016, at 5:45pm, Christoforus Surjoputro
wrote:
> I've
As others have pointed out, since SQLite must ultimately execute the query, it
has to be unencrypted in memory at some point. In general, there is no way to
protect data from prying eyes if that data must be used by a running program,
because a competent adversary can inspect the program as
No links seen from you, ever, on this thread.
SQLite automatically chooses the best index from those available. The index it
is choosing is probably better than the one you want it to use002E
> -Original Message-
> From: sqlite-users-bounces at mailinglists.sqlite.org
Hello Admin,
I have all my important strings encrypted using AES. They get
decrypted at runtime. Well, they get decrypted at run time just when
used and then get over-written by other decrypted strings. It's a
circular queue of strings.
I just run a post process step on one of my
>
> 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
On 2/26/16, Vince Scafaria wrote:
> I am using System.Data.SQLite in .NET and encountering "database is locked"
> with wal using multiple threads from the same process running simple select
> statements with (separate) read-only connections.
The first database connection (in any process) that
> at some
> point the encrypted SQL wiill have to be decrypted before SQLite
> interprets it.
Perhaps we could achieve some level of obfuscation by "pre-preparing" at
compile time the set of all statements that the program uses, and storing the
SQLite prepared statement objects in the
On 02/27/2016 12:49 AM, Jo?o Ramos wrote:
> I'm using SQLite 3.8.10.2 and the following query illustrates the problem:
>
> WITH
> tA(id, name) AS
> (
> SELECT 1, "a" UNION ALL SELECT 2, "b"
> ),
> tB(name) AS
> (
> SELECT "a" UNION ALL SELECT "b"
> )
> SELECT tB.id FROM tA INNER JOIN tB
14 matches
Mail list logo
