Re: Stored procedure code no longer stored in v14 and v15, changed behaviour

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Pasi Oja-Nisula <pon(at)iki(dot)fi>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Stored procedure code no longer stored in v14 and v15, changed behaviour
Date: 2022-12-02 13:02:37
Message-ID: FB6242FD-C3DF-4830-B7CB-AD54D363D6A4@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> On 2 Dec 2022, at 14:00, Pasi Oja-Nisula <pon(at)iki(dot)fi> wrote:
>
> On Fri, 2 Dec 2022 at 02:24, raf <raf(at)raf(dot)org> wrote:
>> Same here. Accessing the loaded stored procedure source
>> is how I audit the state of stored procedures in the
>> database against the code in the code repository.
>
> Exactly. If our software is audited, how can I reliably prove to auditor
> that the running version of the procedure has not been tampered with
> either by customer, rogue developer or some malicious party?

How do you today prove that for other compiled programs in your system?

--
Daniel Gustafsson https://vmware.com/

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Pasi Oja-Nisula 2022-12-02 13:34:39 Re: Stored procedure code no longer stored in v14 and v15, changed behaviour
Previous Message Pasi Oja-Nisula 2022-12-02 13:00:09 Re: Stored procedure code no longer stored in v14 and v15, changed behaviour