On 31 Oct 2011, at 8:07am, Eugene N wrote:
> For your .NET application to use the, DB it must first decrypt it; That
> means, storing the plain version in ram; A memory dump will pronto show the
> contents of this sqlite database;
Physical possession of the hardware concerned is always an end to
Bernd wrote:
> This may not be really SQLite specific, but as it's at least SQLite
> related I thought I asked here.
> Our program ships with an encrypted SQLite database that has to be
> opened by the application to process some other data. As it's a .NET
> application, it's very easy to peek ins
Hello Bernd!
I have a very limited knowledge about such matters, but it seems to me
there is a caveat in the whole area of using encrypted data on a end-user
pc;
For your .NET application to use the, DB it must first decrypt it; That
means, storing the plain version in ram; A memory dump will pro
This may not be really SQLite specific, but as it's at least SQLite
related I thought I asked here.
Our program ships with an encrypted SQLite database that has to be
opened by the application to process some other data. As it's a .NET
application, it's very easy to peek inside the source code (
4 matches
Mail list logo