Hello Damien,
I use the "encrypt specific fields" method of encrypting data in
sqlite. For you to use that with Basic you'd probably have to find
or write a wrapper DLL which handled the field encryption. So your
basic would only see unencrypted data after it sent a password to the
> On Oct 7, 2016, at 10:46 PM, Damien Sykes-Lindley
> wrote:
>
> I cannot see any means of password protecting the database without either
> buying a commercial extension to do this, or recompiling SQLite with the
> authentication extension.
I’m surprised no one
If you are trying to protect against casual snooping, you could probably
zip the sqlite data with a password then have your application unzip the
data to a temp location on open, then re-zip at the end, deleting the
unzipped file. Your application then would be able to use the normal
sqlite
sity so it appears that encrypting
> the data from the application itself is also not an option. So I think at
> this point I am stuck
> Cheers.
> Damien.
> -Original Message- From: R Smith
> Sent: Saturday, October 08, 2016 10:02 AM
> To: sqlite-users@mailinglists.sqlite.org
On 2016/10/08 1:12 PM, Damien Sykes-Lindley wrote:
Hi Ryan,
I think there may have been some misunderstanding here. The
application is a local application and thus needs no server, at least
on the data side. But multiple people may have access to the same
machine. So while user control is
@mailinglists.sqlite.org
Subject: Re: [sqlite] Protecting databases
Hi Damien,
We are obviously all fans of SQLite and keen to involve more people in
what is one of the best DB systems in existence and most widely used DB
in the World.
But...
SQLite answers a need that is quite specific (though
the database when you don't want them to.
Kind regards,
Damien.
-Original Message- From: Darren Duncan
Sent: Saturday, October 08, 2016 6:54 AM
To: SQLite mailing list
Subject: Re: [sqlite] Protecting databases
On 2016-10-07 10:46 PM, Damien Sykes-Lindley wrote:
Hi there,
My name is Damien
Damien,
At 09:18 08/10/2016, you wrote:
Password protecting it is also good on many levels - if the database
is to be used online then it is needless to say that authentication
would be required for various people to view it.
SQLite can't be put "online" per se. It will then be the duty of
To: SQLite mailing list
Subject: Re: [sqlite] Protecting databases
On 2016-10-07 10:46 PM, Damien Sykes-Lindley wrote:
Hi there,
My name is Damien Lindley, and I am, among other things, an independent,
hobbiest programmer. I have been blind since birth and thus all my computer
work relies on screenreader
, there is the
possibility that anyone sharing the computer or network may peruse the database
when you don't want them to.
Kind regards,
Damien.
-Original Message- From: Darren Duncan
Sent: Saturday, October 08, 2016 6:54 AM
To: SQLite mailing list
Subject: Re: [sqlite] Protecting databases
, there is the possibility that anyone sharing the computer or network
may peruse the database when you don't want them to.
Kind regards,
Damien.
-Original Message-
From: Darren Duncan
Sent: Saturday, October 08, 2016 6:54 AM
To: SQLite mailing list
Subject: Re: [sqlite] Protecting
On 2016-10-07 10:46 PM, Damien Sykes-Lindley wrote:
Hi there,
My name is Damien Lindley, and I am, among other things, an independent,
hobbiest programmer. I have been blind since birth and thus all my computer
work relies on screenreader software and keyboard.
I have only just come through
Hi there,
My name is Damien Lindley, and I am, among other things, an independent,
hobbiest programmer. I have been blind since birth and thus all my computer
work relies on screenreader software and keyboard.
I have only just come through the brink of scripting into compiled programming
and so
13 matches
Mail list logo