-------- Original message --------From: Jens Alfke <j...@mooseyard.com> Date:
07/09/2017 19:32 (GMT+00:00) To: SQLite mailing list
<firstname.lastname@example.org> Subject: Re: [sqlite] Proof that a line
has been modified
> On Sep 7, 2017, at 10:24 AM, Igor Tandetnik <i...@tandetnik.org> wrote:
> "Device will refuse to install" is precisely an instance of "security built
> in at the OS level".
Yes, but that's beside the point; it wasn't the relevant part of the example.
Any software, privileged or not, can verify the signature and detect whether
the binary has been modified. That's what the OP wants.
That's fine for an unchanging binary signed in a secure environment and
released to the world; what the OP wants is a similar level of security but for
an ever-changing file (where the private keys must be accessible for "normal
sqlite-users mailing list