Thank you Clemens!

Clemens Ladisch <mailto:clem...@ladisch.de>
7 septembre 2017 à 10:34

Something like <https://en.wikipedia.org/wiki/Linked_timestamping>.

See git or fossil, where the current state of the entire repository is
identified by a hash over all data and all previous changes; once a hash
value has been published, it is not possible to change anything without
changing the hash value. (You need to save the hash values of the
interesting revisions somewhere else to be able to check them.)

These tools work on files, not on database objects. But you could put
the entire database file in the repository.


Regards,
Clemens
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
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