I will be able to make a checksum calculated on all the columns of the row AND on the checksum of the previous row. So if you go back up in the table and recalculate all checksums, you could check that a line has been modified or deleted.


But of course, someone who knows this checksum and its salt could make changes on the table and recalculate all checksums. :-(

Paxdo <mailto:pa...@mac.com>
7 septembre 2017 à 10:16

Hi all!

For security reasons, a customer wants to be sure that a database line cannot be modified after its initial insertion (or unmodified without being visible, with proof that the line has been modified). Including by technicians who can open the database (SQLITE of course).

Is there a solution to that?

I thought of a hash calculated and recorded only when the line was inserted (calculated on all columns of the line, and stored in a column of that line).

Or a trigger that would prevent any modification.

But these solutions can be easily bypassed, right?

Do you have any advice?

Thank you!

Tom
(Sorry for my bad english)
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to